Oracle® Fusion Middleware

Error Messages

12c (12.2.1.1)

E75423-01

May 2016

Oracle Fusion Middleware Error Messages, 12c (12.2.1.1)

E75423-01

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

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

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

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

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

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

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

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

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Conventions

1 ADFC-00001 to ADFC-14031

2 ADFDI-00100 to ADFDI-55516

3 ADFSHARE-00002 to ADFSHARE-00300

4 B2B-EVT-10001 to B2B-EVT-10003

5 B2B-50006 to B2B-53104

6 BAM-00101 to BAM-04999

7 BEA-000001 to BEA-2194839

8 BRW-15000 to BRW-16976

9 CAPTURE-10000 to CAPTURE-10151

10 CFGFWK-20836 to CFGFWK-64276

11 CLONE-20200 to CLONE-92302

12 DFW-40000 to DFW-40210

13 DMS-50700 to DMS-58075

14 DVT-02012 to DVT-26021

15 EDQ-00300 to EDQ-10722

16 ES-07001 to ES-07017

17 ESS-00001 to ESS-09408

18 FRC-60003 to FRC-60107

19 FRM-41838 to FRM-99999

20 FMWPLATFORM-00001 to FMWPLATFORM-020010

21 GGSTU-60000 to GGSTU-65036

22 HC-50006 to HC-53104

23 INST-01000 to INST-10117

24 J2EE HTTPC-00004 to J2EE HTTPC-12011

25 JBO-24000 to JBO-80008

26 JPS-00001 to JPS-90642

27 MAPVIEWER-00001 to MAPVIEWER-09007

28 MDS-00001 to MDS-92010

29 MFT-02001 to MFT-08500

30 ODI-01100 to ODI-999999

31 ODL-52001 to ODL-52816

32 OTD-68176 to OTD-68408

33 OGGV-00001 to OGGV-600013

34 OHS-03506 to OHS-04533

35 OJRF-00001 to OJRF-00008

36 ORABPEL-00006 to ORABPEL-22005

37 ORACLESTATE-COMMON-00001 to ORACLESTATE-COMMON-00001

38 ORACLESTATE-INMEMORY-00001 to ORACLESTATE-INMEMORY-00001

39 ORACLESTATE-INMEMORYRA-00001 to ORACLESTATE-INMEMORYRA-00003

40 ORAMED-01001 to ORAMED-09001

41 OWS-00016 to OWS-60003

42 PKI-01001 to PKI-07022

43 RCU-06000 to RCU-07005

44 REP-00001 to REP-80012

45 SDP-25001 to SDP-26551

46 SOA-06000 to SOA-67028

47 SOAPWS-BUF-00001 to SOAPWS-BUF-00005

48 SOAPWS-DATABIND-221200 to SOAPWS-DATABIND-221600

49 SOAPWS-JMS-225010 to SOAPWS-JMS-225012

50 TOP-00001 to TOP-28007

51 UCM-CS-000001 to UCM-CS-800280

52 UPG-OHS-00001 to UPG-OHS-00012

53 UPGAST-00001 to UPGAST-05005

54 WC-05319 to WC-05370

55 WCC-ADF-10000 to WCC-ADF-30002

56 WCS-03051 to WCS-90200

57 WLS-WSEE-CORE-00001 to WLS-WSEE-CORE-00007

58 WLS-WSEE-MC-00001 to WLS-WSEE-MC-00016

59 WLS-WSEE-00002 to WLS-WSEE-00116

60 WLS-WSEE-PERSIST-00001 to WLS-WSEE-PERSIST-00007

61 WLS-WSEE-SENDER-00001 to WLS-WSEE-SENDER-00006

62 WLS-WSEE-WSAT-00001 to WLS-WSEE-WSAT-00117

63 WSEE-RM-00001 to WSEE-RM-00019

64 WSM-00001 to WSM-09029

Preface

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

Audience

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

Documentation Accessibility

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

Access to Oracle Support

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

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

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

italic

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

monospace

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

1 ADFC-00001 to ADFC-14031

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, DataControlFrame name=''{0}'', owning taskFlowId=''{1}''.

Cause: The ADF Controller was unable to find the model layer DataControlFrame for a task flow.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00010: A DataControlFrame savepoint handle does not exist.

Cause: Restore of a DataControlFrame savepoint was attempted when a savepoint handle did not exist. Savepoint handle can become null after an ADFc save for later savepoint was restored.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00011: The ADF Controller is unable to create an MDSSession. See exception for details.

Cause: The ADF Controller requires an MDSSession to locate metadata. An attempt to create an MDSSession failed. This could be caused by a number of problems.

Action: See the accompanying exception.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00012: The ADF Controller is unable to parse configuration file adf-config.xml.

Cause: An unspecified error occurred while parsing configuration file adf-config.xml.

Action: See the accompanying exception.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00013: Configuration file adf-config.xml has too many ''{0}'' elements.

Cause: Configuration file adf-config.xml contained more instances of the specified element than are allowed.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00014: Configuration file adf-config.xml contains duplicate phase-listener ''{0}'' registrations.

Cause: One or more phase-listeners had the same listener-id value.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00015: Configuration file adf-config.xml contains duplicate phase-listener ''{0}'' in either ''before-id-set'' or ''after-id-set''.

Cause: A phase-listener was specified twice in the same set.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00016: Configuration file adf-config.xml contains an invalid value: [element, value] = [''{0}'', ''{1}''].

Cause: Configuration file adf-config.xml contained invalid XML.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00017: Configuration file adf-config.xml does not contain mandatory element ''{0}''.

Cause: Configuration file adf-config.xml contained invalid XML.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00018: EL expression for UrlParameterConverter is null.

Cause: An attempt was made to convert a URL parameter, but the converter EL expression was null.

Action: Correct the metadata for the converter.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00019: An incorrect object is specified by EL expression ''{0}'' for a URL parameter converter.

Cause: An object was specified by the EL expression that did not implement the oracle.adf.controller.UrlParameterConverter interface.

Action: Specify an object that implements the oracle.adf.controller.UrlParameterConverter interface.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00020: Task flow ''{0}'' requires a new transaction, but a transaction is already open on the frame.

Cause: A new transaction could not be started on the frame because a transaction was already open.

Action: Correct the application's flow or the task flow's metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00021: Task flow ''{0}'' requires a shared DataControlFrame but parent frame is null.

Cause: The task flow is configured to share its DataControl scope with its parent. The parent DataControlFrame is null.

Action: Correct the application's flow or the task flow's metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00022: Unable to create logger ''{0}''.

Cause: An attempt was made to create a logger with a null name.

Action: Contact your Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADFC-00023: The ControllerContext is null.

Cause: The ControllerContext was found to be null when expected to be non-null.

Action: Contact your Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Programmatic

ADFC-00024: No ExternalContext could be found.

Cause: No ExternalContext value could be found.

Action: Contact your Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Programmatic

ADFC-00025: The ADF controller has not been successfully initialized.

Cause: The ADF controller has not been successfully initialized, probably due to a configuration error.

Action: Contact the system administrator and inspect the server logs for information on why the initialization failed.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00026: Attempt made to unlock a request lock that is not locked.

Cause: Attempt made to unlock a request lock that is not locked.

Action: Contact the system administrator and inspect the server logs.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00027: Attempt to modify a request lock by another request.

Cause: Attempt to modify a request lock by another request.

Action: Contact the system administrator and inspect the server logs.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00028: The ADF controller encountered an error while parsing the /WEB-INF/web.xml file.

Cause: The ADF controller encountered an error while parsing the /WEB-INF/web.xml file.

Action: Review the /WEB-INF/webg.xml file and inspect the server logs for information on why the parsing failed.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00029: Attempt to acquire the root view port request lock failed due to a timeout.

Cause: Typically caused by another thread holding the request lock for to long, possible due to a deadlock.

Action: Contact the system administrator and inspect the server logs.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00030: The ADF Page Flow functionality requires the full ADF Faces runtime which does not appear to be present, application configuration is invalid.

Cause: The ADF Page Flow feature was not able to verify a fully functional ADF Faces runtime is present.

Action: Update the application's deployment configuration to include the full ADF Faces runtime.
Level: 2

Type: ERROR

Impact: Installation

ADFC-00031: ADF Controller is unable to create an Oracle DFW Incident.

Cause: ADF Controller called Oracle DFW to create an incident report and that call failed.

Action: See associated exception.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00032: ADF Controller encountered a serious error.

Cause: ADF Controller reported an INCIDENT_ERROR.

Action: See associated incident directory for details.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00033: ADF Controller failed to report an incident for this exception.

Cause: ADF Controller failed to create an incident report for this exception.

Action: See exceptions in log.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00034: Invalid event type passed to RemoteEventProducer.

Cause: A remote taskflow is raising an event to be passed to the consumer and the internal state is invalid.

Action: File a bug.
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: User ''{0}'' does not have ''{1}'' permission on ''{2}''.

Cause: An attempt was made to access a task flow without appropriate privilege.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Security

ADFC-00620: Parameter value is invalid.

Cause: The value provided for one of the parameters failed validation.

Action: Check the parameter value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00621: The ADF Controller is unable to make a view bookmarkable.

Cause: The ADF Controller was unable to make a view bookmarkable.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00622: Attempt to set view port view ID outside of INVOKE_APPLICATION phase.

Cause: The view ID of a view port may only be set during the INVOKE_APPLICATION phase of the request lifecycle.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00623: Task flow ID EL expression ''{0}'' for region ''{1}'' evaluated to null.

Cause: The EL expression for a region's task flow ID evaluated to null.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00624: Task flow ID EL expression ''{0}'' for region ''{1}'' evaluated to invalid object type ''{2}''.

Cause: The EL expression for a region's task flow ID evaluated to an invalid type of object.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00625: A new session URL may only be requested during the RENDER_RESPONSE phase.

Cause: A request for a new session URL was made during an incorrect phase of the request lifecycle.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00626: ADF does not support calling ConfigurableNavigationHandler.performNavigation() after the INVOKE_APPLICATION phase has completed.

Cause: A call to ConfigurableNavigationHandler.performNavigation() was made during an incorrect phase of the request lifecycle.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00627: ADF Controller was unable to issue a sendError() call.

Cause: Something triggered a response.sendError() call, and that call failed.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00628: ADF Controller was unable to update a bookmark URL.

Cause: Something triggered a response.sendError() call, and that call failed.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00629: ADF Controller is unable to trigger authentication.

Cause: A permission check failed, and the user is not yet authenticated. ADFc cannot redirect to the authentication service.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Security

ADFC-00630: ADF Controller received an invalid remote task flow return request.

Cause: A remote task flow call return request was sent to the server when a remote call was not outstanding.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00631: This viewport does not support executing an activity of type ''{0}''.

Cause: An attempt was made to execute an activity type that is not supported by this viewport.

Action: Contact the application developer.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02000: The ADF Controller is not able to initialize the metadata service.

Cause: The ADF Controller was unable to initialize the metadata service.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-02001: The ADF Controller cannot find ''{0}''.

Cause: An attempt was made to load metadata that cannot be found.

Action: Verify that all required files are available.
Level: 2

Type: ERROR

Impact: Files

ADFC-02002: The ADF Controller cannot parse the task flow metadata.

Cause: The metadata did not represent a valid task flow.

Action: See the associated exceptions. Validate the metadata.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02003: Default activity must be specified in task flow definition ''{0}''.

Cause: The ADF Controller was unable to find task flow default activity in the task flow definition.

Action: Add a default activity to the task flow definition.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02004: Default activity ID ''{0}'' is invalid.

Cause: The ADF Controller was unable to construct the default activity ID.

Action: Correct the default activity ID.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02005: Task flow definition is not found: ''{0}''.

Cause: An attempt was made to read the specified task flow. The task flow cannot be found.

Action: Verify that the required file is available.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02006: A task flow ID is not found in the URL.

Cause: The specified task flow ID was requested and could not be found.

Action: Verify that the task flow reference is correct. Verify that all required files can be found.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02007: A task flow document is not found in the URL.

Cause: An attempt was made to access a task flow using URL parameters. The specified document could not be found.

Action: Correct the value for the document parameter.
Level: 2

Type: ERROR

Impact: Browser

ADFC-02008: The value for 'documentName' cannot be null or empty.

Cause: An attempt was made to reference a task flow using a null value for 'documentName'.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02009: The value for 'localTaskFlowId' cannot be null or empty.

Cause: An attempt was made to reference a task flow using a null value for 'localTaskFlowId'.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02010: The value for 'localTaskFlowId' cannot be '#'.

Cause: An attempt was made to reference a task flow using an invalid value for 'localTaskFlowId'.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02011: The value for 'localActivityId' cannot be null or empty.

Cause: An attempt was made to construct an oracle.adf.controller.internal.metadata.ActivityId using an invalid value for 'localActivityId'.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02012: The activity ID string cannot be null or empty.

Cause: An attempt was made construct an oracle.adf.controller.internal.metadata.ActivityId using an invalid value.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02013: Unable to get metadata for activity ''{0}''.

Cause: An attempt was made to access an activity that has no metadata defined.

Action: Validate the task flow document.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02014: No activity implementation is available for activity type ''{0}''.

Cause: An attempt was made to access an activity that is not a known activity type.

Action: Validate the task flow document.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02015: Task flow ID ''{0}'' in document ''{1}'' is invalid.

Cause: The ADF Controller was unable to construct the task flow ID.

Action: Correct the task flow ID.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02016: A possible cyclic reference to template ''{0}'' is detected when parsing ''{1}''.

Cause: The task flow metadata references a template that is already referenced by this task flow.

Action: Verify that the task flow templates do not reference each other in a cyclic manner.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02017: The value for 'url' cannot be null or empty.

Cause: An attempt was made to reference a URL view activity using a null value for 'url'.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Browser

ADFC-02018: Root tag ''{0}'' in ''{1}'' does not match <adfc-config>.

Cause: A document with an invalid root tag was referenced.

Action: Correct the root tag.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02019: No activities are specified in task flow definition ''{0}''.

Cause: The task flow definition did not contain any activities.

Action: Add activities to the task flow definition.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02020: Cannot find default activity ''{0}'' in task flow definition ''{1}''.

Cause: The ADF Controller was unable to find a default activity in the task flow definition.

Action: Add a default activity.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02021: Customization of the documents that appear multiple times on the classpath is not supported. Document name: ''{0}''.

Cause: A document appears multiple times on the classpath.

Action: Remove multiple documents.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02022: Either 'parent-outcome' or 'root-outcome' has to be specified.

Cause: An attempt was made to parse a parent action activity with neither 'parent-outcome' and nor 'root-outcome' specified.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Browser

ADFC-04000: The value of PagePhaseListener cannot be null.

Cause: An attempt was made to use a PagePhaseListener with a null value.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04001: The value of a listener ID string cannot be null or empty.

Cause: An attempt was made to identify a PagePhaseListener using a null listener ID.

Action: Use a nonempty string for the listener ID.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04002: A PagePhaseListener with the listener ID of ''{0}'' already exists.

Cause: Each PagePhaseListener should be registered with a unique listener ID.

Action: Use a listener ID that does not already exist.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04003: The PagePhaseListener of type ''{0}'' with listener ID of ''{1}'' cannot be registered because it is part of the internal API.

Cause: The ADF Controller was unable to register an internal PagePhaseListener using the public API.

Action: Use a PagePhaseListener that is not internal.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04004: The value 'any_public_listener' is not allowed.

Cause: The value 'any_public_listener' was part of the afterSet or beforeSet parameter.

Action: Do not use 'any_public_listener' as the listener ID for beforeSet or afterSet.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04005: The PagePhaseListener with ID ''{0}'' is internal and cannot be removed.

Cause: A failed attempt was made to remove an internal PagePhaseListener. This operation is not supported.

Action: Ensure that a PagePhaseListener is public, not internal, before attempting to remove it.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04006: The value of LifecycleContext cannot be null.

Cause: An attempt was made to create a PagePhaseEvent with a null LifecycleContext.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04007: The FacesPageLifecycleContext does not exist yet.

Cause: An attempt was made to retrieve the FacesPageLifecycleContext before it was created.

Action: Wait until the RestoreView phase of the JavaServer Faces lifecycle to retrieve the FacesPageLifecycleContext.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04008: The BindingContext on the session is null.

Cause: The BindingContext retrieved from the session was null.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06000: The ADF Controller caught exception ''{0}'' while performing control flow routing. See the stack trace for details.

Cause: An unhandled exception occurred while the ADF Controller was executing the application's control flow.

Action: See the associated exception. Verify that the navigation rules are correctly specified. Verify that the correct outcome was generated to trigger routing.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06001: TaskFlowId ''{0}'' is invalid.

Cause: An attempt was made to construct a TaskFlowId using an invalid string.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06002: unhandled exception

Cause: The ADF Controller encountered an exception. Either no exception handler activity was defined or the ADF Controller and task flow were not configured to catch this exception.

Action: See the associated exception. Verify that the exception handler activity is correctly defined. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06003: TaskFlowId for a child view port must be specified.

Cause: An attempt was made to create a child view port using a null value for TaskFlowId.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06004: Invalid transport ''{0}'' used. Task flows require ''{1}''.

Cause: An attempt was made to access a task flow without using the required transport.

Action: Use the appropriate transport. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Security

ADFC-06005: The ADF Controller is unable to invoke URL parameter validator.

Cause: A view activity defines one or more parameter validators. Invoking the parameter validator failed.

Action: See the associated exception. Verify that the metadata refers to the correct class and method.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06006: An exception occurred when evaluating method expression ''{0}'' specified for ''{1}'' defined in ''{2}''.

Cause: A view activity defines a bookmark method. Invoking the specified method failed.

Action: See the associated exception. Verify that the metadata refers to the correct class and method.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06007: The ADF Controller is unable to copy task flow input parameters. Objects must be serializable.

Cause: The task flow call activity specifies one or more input parameters. The ADF Controller was unable to copy the specified values.

Action: See the associated exception. Verify that the metadata refers to the correct class and method. Verify that the specified objects are serializable.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06008: Router case expression ''{0}'' did not evaluate to a boolean value, type of result = ''{1}''.

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

Action: Correct the expression.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06009: The ADF Controller is unable to encode a URL.

Cause: The ADF Controller was unable to encode a URL.

Action: See the associated exception. Correct the metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06010: The ADF Controller is unable to encode remote task flow URL: ''{0}''.

Cause: The ADF Controller was unable to invoke a task flow using a URL.

Action: See the associated exception. Correct the metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06011: The ADF Controller is unable to encode remote process return URL: ''{0}''.

Cause: The task flow metadata specified an invalid return URL.

Action: See the associated exception. Correct the metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06012: Task flow ID returned from a remote call does not match the called task flow''s ID, calledId= ''{0}'', returnedId= ''{1}''.

Cause: The task flow ID returned from a remote task flow call did not match the ID of the task flow that was called.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06013: The ADF Controller is unable to encode bookmark parameter ''{0}''.

Cause: The ADF Controller was unable to encode a bookmark parameter.

Action: See the associated exception.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06014: An exception occurred when invoking a task flow finalizer.

Cause: Execution of the task flow finalizer raised an exception.

Action: See the associated exception. Verify that the metadata references the correct class and method.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06015: An exception occurred when invoking a task flow initializer.

Cause: Execution of the task flow initializer raised an exception.

Action: See the associated exception. Verify that the metadata references the correct class and method.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06016: Task flow reentry is not allowed: ''{0}''.

Cause: A failed attempt was made to reenter a task flow where reentry is prohibited.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06017: Task flow ID is null.

Cause: The task flow ID for a remote taskflow call is null.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06018: Task flow ID EL expression ''{0}'' on activity ''{1}'' evaluated to null.

Cause: The EL expression for a remote task flow ID evaluated to null.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06019: Router case expression ''{0}'' evaluated to a null value.

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

Action: Correct the expression to return a non-null boolean value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08000: The ADF Controller is unable to obtain the view state for the savepoint operation.

Cause: An attempt to save or restore the UIViewRoot failed.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08001: The ADF Controller is unable to commit the savepoint database transaction.

Cause: The ADF Controller was unable to commit a savepoint to the database.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08002: The ADF Controller is unable to log in to the database or obtain a database connection.

Cause: The ADF Controller was unable to log in to the database.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08003: The ADF Controller is unable to delete all savepoint records for user ''{0}'' from the database.

Cause: The ADF Controller was unable to delete all specified savepoints.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08004: The ADF Controller is unable to delete savepoint record ''{0}'' from the database.

Cause: The ADF Controller was made to delete the specified savepoint.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08005: Exception occured when evaluating an expression used for savepoint ID.

Cause: The task flow contains at least one save point restore activity. An attempt to evaluate the value for savepoint ID failed.

Action: See the associated exception. Check the task flow metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08006: The ADF Controller was unable to get the savepoint with ID = ''{0}''.

Cause: The ADF Controller was unable to retrieve the specified savepoint.

Action: Verify that the correct ID was specified. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08007: The savepoint ID is empty.

Cause: An attempt was made to create or get a savepoint with a null ID.

Action: Specify a valid savepoint ID.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08008: The ADF Controller is unable to insert a savepoint record for ID ''{0}''.

Cause: The ADF Controller was unable to insert a savepoint into the database.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08009: The ADF Controller was unable to registering JDBC driver ''{0}''.

Cause: The ADF Controller was unable to establish a JDBC connection.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08010: The ADF Controller was unable to find the JOC-based state manager implementation.

Cause: The ADF Controller was unable to use the Java Object Cache to store savepoints.

Action: Make sure that the JOC is available. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08011: The JNDI connection name is not specified in configuration file adf-config.xml.

Cause: An attempt was made to establish a JDBC connection.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08012: The specified data source JNDI name, ''{0}'', could not be found.

Cause: An attempt was made to establish a database connection.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08013: The ADF Controller is unable to query the database for the current user's savepoint IDs.

Cause: The ADF Controller was unable to query the database for the set of savepoints.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08014: The ADF Controller is unable to execute the save point restore activity.

Cause: The task flow contains a savepoint restore activity. An attempt to execute that activity failed.

Action: See the associated exception. Verify that the metadata is correct. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08015: Cannot restore the savepoint. The savepoint ID is null.

Cause: An attempt was made to restore a null savepoint.

Action: Verify that the task flow metadata is correct. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08016: The ADF Controller is unable to retrieve savepoint ''{0}'' from the database.

Cause: The ADF Controller was unable to retrieve the specified savepoint from the database.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08017: The ADF Controller is unable to save the savepoint.

Cause: The ADF Controller was unable to save the savepoint to the persistence manager.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08018: The ADF Controller is unable to create or execute a SQL statement: ''{0}''.

Cause: The ADF Controller generated SQL that is was unable to create or execute.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08019: The ADF Controller is unable to find the transaction manager.

Cause: The ADF Controller attempted to suspend or resume a transaction.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08020: The ADF Controller is unable to resume a transaction.

Cause: The ADF Controller was unable to resume the transaction.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08021: The ADF Controller is unable to suspend a transaction.

Cause: The ADF Controller was unable to suspend the transaction.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08022: The ADF Controller is unable to update the savepoint record for ID ''{0}''.

Cause: The ADF Controller was unable to update a savepoint.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08023: The ADF Controller is encountering an error while invoking a savepoint restore finalizer.

Cause: The task flow specifies a savepoint restore finalizer. Execution of the finalizer raised an exception.

Action: See the associated exception. Verify that the metadata references the correct class and method.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08024: The savepoint ID ''{0}'' is not valid.

Cause: An attempt was made to create or use a savepoint with an invalid ID.

Action: Specify a valid savepoint ID conforming to the UUID format.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08025: The ADF Controller is unable to serialize the savepoint.

Cause: The ADF Controller was unable to serialize the savepoint.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08026: The ADF Controller is unable to deserialize the savepoint.

Cause: The ADF Controller was unable to deserialize the savepoint.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08027: The ADF Controller is unable to close the database connection.

Cause: The ADF Controller was unable to close the database connection.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08028: The ADF Controller is unable to restore the savepoint with ID = ''{0}''.

Cause: The ADF Controller is unable to restore a non existing savepoint.

Action: Verify that the savepoint ID is correct. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08029: The ADF Controller is unable to find in memory savepoint created before dialog window was shown.

Cause: An attempt to create save point failed.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08030: Savepoints are not supported on a page with a remote region.

Cause: The application attempted to create a savepoint while displaying a page with a remote region.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10000: Cannot find class ''{0}'' for a method parameter.

Cause: A method call activity attempted to call the specified class and could not find it.

Action: Correct the classpath. Verify that the metadata refers to the correct class.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10001: Cannot instantiate class ''{0}''.

Cause: The task flow specifies a managed bean. Instantiation of this managed bean failed.

Action: Verify that the metadata for the managed bean is correct. Verify that the class has a default constructor.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10002: Cannot get a value from value binding expression ''{0}''.

Cause: Task flow metadata references a managed bean. Bean instantiation failed.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10003: Cannot set a null value into array of ''{0}''.

Cause: The task flow specifies a managed bean of type 'LIST'. An attempt was made to set a null value.

Action: Change the bean type or modify the code that is attempting to set the bean value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10004: Cannot set managed bean property ''{0}''.

Cause: An attempt was made to set the property in a managed bean.

Action: See the associated exception. Validate the task flow metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10005: Cannot find MethodExpression for ''{0}''.

Cause: Task flow metadata references a method binding. Invoking the specified method failed.

Action: See the associated exception. Verify that the metadata is correct. Correct the specified method.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10006: An exception occurred when evaluating an expression ''{0}'' specified for ''{1}''.

Cause: Task flow metadata refers to an EL expression. Evaluation of this expression failed.

Action: See the associated exception. Correct the expression.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10007: A possible cyclic reference to managed bean ''{0}'' is detected.

Cause: The task flow metadata referenced a managed bean that was already referenced by this task flow.

Action: Verify that the managed bean is not already specified in a referenced template.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10008: Outcome to-string metadata cannot be specified for a method call activity that points to a void Java method. Activity ID: ''{0}''.

Cause: The method call activity outcome metadata specified to-string.

Action: Change the method outcome metadata to use fixed-outcome, or change the Java to return a java.lang.String value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10009: An exception occurred during invocation of ''{0}'' method.

Cause: Annotated managed bean method cannot be invoked.

Action: Check method implementation.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10010: No name specified for bean class ''{0}''.

Cause: A property name was null.

Action: Pass in a not null bean property name.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10011: No bean specified.

Cause: A bean object was null.

Action: Pass in a not null bean.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10012: Unknown property ''{0}'' on class ''{1}''.

Cause: The bean does not have the specified property.

Action: Check property access methods.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10013: Property ''{0}'' has no setter method in class ''{1}''.

Cause: The bean does not have the write method for the specified property.

Action: Check property name.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10014: Property ''{0}'' has no getter method in class ''{1}''.

Cause: The bean does not have the read method for the specified property.

Action: Check property name.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10015: Cannot invoke ''{0}'' on bean class ''{1}''- argument type mismatch - had objects of type ''{2}'' but expected signature ''{3}''.

Cause: The bean property has a different type than specified.

Action: Check property name.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12000: State ID in request is invalid for the current session.

Cause: The request contained a state instance ID, but it did not exist in the session, nor was this a request for a bookmarked resource. This might be due to a session timeout.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12001: The ADF Controller is attempting to pop last entry from page flow scope stack.

Cause: The ADF Controller attempted to pop the top task flow off the task flow stack.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12002: The ADF Controller is unable to pop the top-level ADF unbounded task flow from the page flow stack.

Cause: The ADF Controller attempted to pop the unbounded task flow off the page flow stack.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12003: The page flow scope stack is empty.

Cause: The ADF Controller attempted to get the current task flow

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12004: Page flow stack ID ''{0}'' is invalid.

Cause: The ADF Controller attempted to calculate the delta between two page flow stacks. The specified stack ID is invalid.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12005: The ADF Controller cannot find a common page flow stack element.

Cause: The ADF Controller attempted to calculate the delta between two page flow stacks. The two stacks have no elements in common.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12006: The scope of the referenced object ''{0}'' is shorter than the referring object ''{1}''.

Cause: An attempt was made to access a managed bean outside its scope.

Action: See the associated exception. Verify that the managed bean is correctly defined and that the reference is valid.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12007: Page flow scope instance ID ''{0}'' is invalid.

Cause: The ADF Controller attempted to get the unbounded task flow for this instance ID.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12008: The ADF Controller request state is missing or invalid.

Cause: A missing or invalid ADF Controller request state was detected.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12009: An application is accessing the page flow scope prematurely.

Cause: An application attempted to access the page flow scope early in the request lifecycle, before the page flow scope was available.

Action: Modify the application to access the page flow scope later in the request lifecycle.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12010: A null window ID is detected in a situation where it should never be null.

Cause: A null window ID is detected in a situation where it should never be null.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12011: Window ID ''{0}'' is invalid.

Cause: A window ID was submitted that was not a valid window ID generated during the current HTTP session.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12012: The request has an invalid state ID, and the session timed out.

Cause: The request contained a state instance ID, but the session was created during the current request.

Action: Return to the start page of the application.
Level: 2

Type: ERROR

Impact: Session

ADFC-12013: Controller state has not been initialized for the current request.

Cause: Controller request initialization has not been performed on the current request.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12014: Attempted access to an object that has already been released, object type: ''{0}''.

Cause: Attempted access to an object that has already been released.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12015: Null backingBeanScope ID.

Cause: Null backingBeanScope ID detected.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12016: Attempt to add the ADF Controller state to URL failed.

Cause: Attempt to add the ADF Controller state to URL failed.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12017: A non-ADF scope was specified is a place where only an ADF scope is permitted.

Cause: A non-ADF scope was specified is a place where only an ADF scope is permitted.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12018: A null ADF controller state was encountered.

Cause: The ADF controller state was found to be null when it should not be.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12019: Window ''{0}'' has already been closed.

Cause: The ADF controller received a request from a window that has already been reported closed.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12020: The ADF controller received a request to open a dialog when no dialog request was pending.

Cause: The ADF controller received a request to open a dialog when no dialog request was pending..

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12021: The state ID for this request has been released.

Cause: The request contained a state instance ID, but the corresponding objects have already been released. ADF Controller limits the number of active root view ports based on the value set in adf-config.xml. Once that limit is exceeded then the least-recently-used root view port is released.

Action: Return to the start page of the application.
Level: 2

Type: ERROR

Impact: Session

ADFC-12022: No view scope is available because the window has been closed.

Cause: A request was made for a view scope in a window that has already been closed.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12023: No page flow scope is available because the window has been closed.

Cause: A request was made for a page flow scope in a window that has already been closed.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14000: View port ID ''{0}'' is invalid.

Cause: A reference was made to an invalid view port ID.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14001: The ADF Controller cannot create a child view port.

Cause: No root view port was created.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14002: The ADF Controller is unable to set a view port hierarchy that has no root view port.

Cause: The ADF Controller was unable to set the hierarchy of view ports with no root view port.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14003: Region does not have or cannot reach a view activity.

Cause: The region specified a task flow where no view activities could be reached.

Action: Verify that the correct task flow is specified. Verify that the task flow has at least one navigable view.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14004: The ADF Controller cannot execute task flow ''{0}'' that uses page fragments in the root view port.

Cause: The task flow definition declares this task flow as using page fragments. The root viewport can only run task flows that use pages, not page fragments.

Action: Remove the use-page-fragments flag from the task flow definition ''{0}''.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14005: Unused

Cause:

Action:
Level: 1

Type: Error

Impact: Other

ADFC-14006: Client ID ''{0}'' already exists.

Cause: Attempt to create child view port with a client ID that's already in use.

Action: Circular references to regions are not supported. Remove the region from the page.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14007: Display name ''{0}'' must evaluate to java.lang.String.

Cause: An EL expression for the display-name property must evaluate to a java.lang.String.

Action: Fix the EL expression.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14008: Task flow call activity cannot invoke remote task flow inside a region.

Cause: An attempt was made to invoke a remote task flow from inside a region.

Action: Fix the application.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14009: No RegionData stack was found was found while executing pop operation.

Cause: The RegionStack did not exist or was empty when attempting a pop operations, possibly the results of a pop without a push.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14010: Attempt to suspend a task flow context that's already suspended.

Cause: Attempt to suspend a task flow context that's already suspended.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14011: Attempt to resume a task flow context that has not been suspended.

Cause: Attempt to resume a task flow context that has not been suspended.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14012: Attempt to set the request's submitted view ID on a region's view port.

Cause: Attempt to set the request's submitted view ID on a region's view port.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14013: Task flow binding 'active' attribute is not a boolean value, binding=''{0}'', expression=''{1}''.

Cause: The 'active' attribute of a task flow binding did not evaluate to a boolean value.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14014: Task flow binding ''active'' attribute evaluated to null, binding=''{0}''.

Cause: The 'active' attribute of a task flow binding evaluated to null.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14015: Task flow binding ''active'' attribute was not specified, binding=''{0}''.

Cause: The 'active' attribute must be specified when activation="conditional" is used.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14016: Unknown value for task flow binding attribute ''activation'', binding=''{0}'', value=''{1}''.

Cause: An unknown value for the task flow binding attribute 'activation' was encountered.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14017: Invalid value returned by expression ''{0}'' for multi task flow binding with id ''{1}''.

Cause: The expression for the taskFlowList attribute either does not evaluate to an object of type java.util.List or one of the element in the list not of type oracle.adf.controller.TaskFlowBindingAttributes or is null.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14018: The taskFlowList attribute for multi task flow binding with id ''{0}'' contains a taskflow binding with a null id attribute.

Cause: The expression of the taskFlowList attribute evaluate to a list that contain an element with a null id attribute.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14019: Remote taskFlowId of ''{0}'' requested from ''{1}'' does not refer to a known task flow.

Cause: The requested task flow does not exist in the producer application.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14020: Remote taskFlowId of ''{0}'' requested from ''{1}'' is not remote invocable.

Cause: The requested task flow does not support being remotely invoked.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14021: Remote taskFlowId of ''{0}'' requested from ''{1}'' has a shared data control scope which is not supported.

Cause: The requested task flow uses a shared data control scope which is not supported between consumer and producer applications.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14022: Remote taskFlowId of ''{0}'' requested from ''{1}'' requires an existing transaction which is not supported.

Cause: The requested task flow requires an existing transaction which is not supported between consumer and producer applications.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14023: Remote task flow input parameter value is not serializable, binding=''{0}'', paramType=''{1}'', paramName=''{2}'', taskFlowId=''{3}'', remoteURL=''{4}''.

Cause: An attempt was made to pass a non-serializable input parameter value to a remote task flow, remote task flow parameters must be serializable.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14024: Contextual event payload passed between remote task flows is not serializable, binding=''{0}'', eventName=''{1}'', eventProducer=''{2}'', payloadType=''{3}''.

Cause: An attempt was made to pass a non-serializable contextual event payload between remote task flows.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14025: A RemoteTaskFlowProducer connection was not specified for remote task flow binding ''{0}''.

Cause: An attempt was made to execute a remote task flow but no connection name was provided for the binding.

Action: Verify the task flow binding in the consumer's pageDef is defined correctly.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14026: Failed to find a RemoteTaskFlowProducer with name ''{0}''.

Cause: An attempt was made to execute a remote task flow but no connection with the specified name was found.

Action: Verify the application's connection.xml contains the named RemoteTaskFlowProducer connection.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14027: RemoteTaskFlowProducer with name ''{0}'' does not specify an invoke URL.

Cause: The named RemoteTaskFlowProducer does not include a URL for invoking task flows on the producer.

Action: Edit the RemoteTaskFlowProducer connection and supply an invoke URL value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14028: Connection with name ''{0}'' is not of type ''{1}''.

Cause: The named connection is not the correct type of connection.

Action: Redefine the connection as the correct type.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14029: Attempt to nest a remote task flow inside another remote task flow.

Cause: A remote task flow tried to include another remote task flow which is unsupported.

Action: Redefine the application structure to prevent nesting remote task flows.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14030: Failed to find a DCTaskFlowBinding with name ''{0}''.

Cause: A region model failed to find its corresponding DCTaskFlowBinding object.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14031: A required task flow input parameter value was not specified.

Cause: An attempt was made to either call a task flow or execute one in a region without providing all of the required input parameter values..

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

2 ADFDI-00100 to ADFDI-55516

ADFDI-00100: Unable to send a request for BindingContext: a DIRemoteServlet call is already in progress.

Cause: A request to DIRemoteServlet was attempted while another one is already in progress.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00101: unexpected value found in attribute metadata: {0}

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00103: Unable to locate start element: BindingContainer in response stream.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00105: invalid child element <{0}> encountered within <{1}> element

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00106: missing end element: </{0}>

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00107: row limit exceeded

Cause: Too many rows exist in result set.

Action: Refine your query in order to reduce the number of matching rows.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00108: user session required

Cause: A valid user session is required to communicate with server.

Action: Log in to server and retry request.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00109: invalid GetResourceBundle response

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00110: unable to locate element {0} or parse its contents

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00111: unable to create request object

Cause: Unable to establish a connection to the DIRemoteServlet.

Action: Verify that the DIRemoteServlet URL is specified properly and retry request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00112: unable to create XmlTextWriter

Cause: An unexpected error occurred while sending a request to the DIRemoteServlet.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00113: unable to get request stream

Cause: An unexpected error occurred while sending a request to the DIRemoteServlet.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00114: The DIRemoteServlet returned an unrecognized value for element {0}, attribute {1}: {2}.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00115: The DIRemoteServlet returned an unexpected element type in the response XML: {0}

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00116: The DIRemoteServlet returned invalid XML: unexpected end of response.

Cause: An unexpected error occurred while reading the DIRemoteServlet response.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00117: An unexpected error occurred while reading the server response. Consult the logs for more information.

Cause: An unexpected error occurred while reading the DIRemoteServlet response.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00118: The DIRemoteServlet returned an error. A subsequent error occurred reading the error details from the response.

Cause: An unexpected error occurred while reading the DIRemoteServlet response.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00119: The DIRemoteServlet returned an error. A subsequent error occurred reading the error details from the response: unexpected element type: {0}.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00120: The DIRemoteServlet returned an error. A subsequent error occurred reading the error details from the response: unexpected element name: {0}.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00121: The expected XML element {0} was not found. Instead, the element {1} of type {2} was found.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00122: An unexpected XML element name was encountered (expected: {0}, found {1}).

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00123: The expected XML end element {0} was not found. Instead, the element {1} of type {2} was found.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00124: The expected XML end element {0} was not found. Instead, the element {1} was found.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00125: The expected XML attribute {0} for element {1} was not found.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00126: An attempt was made to set the row position for control binding {0} to {1}. Iterator has {2} rows.

Cause: Row index out of bounds.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00127: A version mismatch was detected for {0}. Version {1} was found, version {2} was expected.

Cause: The servlet version did not match the required level for the client.

Action: Upgrade the client and/or server so that compatible versions are in use.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00128: unable to locate the column metadata for column with ID: {0}

Cause: The binding container metadata did not match the data returned from the server.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00129: invalid Encode URL response

Cause: The response received from the server for this request could not be processed. It may be caused by an exception in the server component.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00130: The size of requested resource bundle ({1}) exceeds the maximum allowable limit: {0} bytes.

Cause: The size of the resource bundle exceeded the supported size.

Action: Reduce the size of the resource bundle.
Level: 1

Type: WARNING

Impact: Files

ADFDI-00131: The connection attempt has been canceled.

Cause: The attempt to connect to the server was canceled.

Action: Retry the current action.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00132: unable to execute Wininet method {0}; error code: {1}

Cause: The Wininet library was unable to provide the requested service.

Action: Retry the current action, confirm connectivity, and/or consult the client logs for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00133: The user session has changed.

Cause: The user session timed out or was otherwise invalid.

Action: Retry the current action, re-login, or re-establish a valid user session.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00134: An attempt to connect to the web application has failed.

Cause: The web application may not have been running or may not have been configured to allow client connections.

Action: Confirm that the web application is accepting connections from a web browser.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00135: The server-side list is not positioned as expected.

Cause: The server-side list was not positioned as expected.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00136: A server side certificate could not be verified. Open Internet Explorer, visit the site that your workbook is attempting to reach, install the certificate, and retry the current action.

Cause: A server side certificate could not be verified.

Action: Open Internet Explorer, visit the site that your workbook is attempting to reach, install the certificate and retry the current action.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00137: The client and server versions are not compatible. Contact the system administrator and ensure that the client and server versions match.

Cause: The version of the server was not compatible with the version of the client.

Action: Contact the system administrator and ensure that the client and server versions match.
Level: 1

Type: ERROR

Impact: Deployment

ADFDI-00138: The current user is not authorized to access the binding container.

Cause: The current user did not have the necessary permissions to access the binding container.

Action: Log out and log back in as a different user, or contact the system administrator to request the necessary permissions.
Level: 1

Type: ERROR

Impact: Security

ADFDI-00139: The setup action has failed unexpectedly. Review the server log files for more information.

Cause: The specified setup action failed to execute as expected.

Action: Review the server logs for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-00140: An error was encountered while connecting to or communicating with the web application. Details: {0} ({1}: {2}).

Cause: The client encountered an error when attempting to communicate with the web application.

Action: Review the server logs for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00141: An attempt to establish a user session with the web application has failed.

Cause: Something has prevented the client from establishing a valid user session with the web application.

Action: Review the server logs for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00142: The transaction size limit was exceeded.

Cause: Too much data was sent to the server without committing any changes to the database.

Action: Reduce the amount of pending changes and retry the current action.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-00143: Failed to locate metadata.

Cause: The server could not find the metadata requested by the client.

Action: Contact the system administrator to make sure the workbook metadata is correctly deployed.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-00144: Invalid metadata key

Cause: The key used to reference the client metadata was invalid.

Action: Contact the workbook developer to correct the metadata key.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-00145: A server-side error has occurred when loading metadata.

Cause: A server-side error occurred that prevented the client from loading metadata.

Action: Review the server logs for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-00146: Invalid ClientMetadata response

Cause: The XML response returned from the DIRemoteServlet was invalid.

Action: Review the server logs for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00147: Create savepoint failed

Cause: An unexpected error occurred while creating a savepoint.

Action: Review the server logs for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00148: Restore savepoint failed

Cause: An unexpected error occurred while restoring a savepoint.

Action: Review the server logs for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00149: An unexpected exception occurred on the server. Review the server logs for more details on the cause of the failure.

Cause: An unexpected error occurred while the server handled a client request.

Action: Review the server logs for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-00150: Unexpected java data type. Name: {0}

Cause: An attempt was made to use an unsupported Java data type.

Action: Replace the unsupported data type with a supported type.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-00500: unable to execute Wininet method {0}; error code: {1}

Cause: The Wininet library was unable to provide the requested service.

Action: Retry the current action, confirm connectivity, and/or consult the client logs for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00501: An unexpected status: {0} ({1}) was returned from the server while requesting the URL: {2}

Cause: The client was unable to complete its request to the server for the given URL. The server returned an unexpected status code.

Action: Retry the current action, confirm connectivity, and/or consult the client logs for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00502: The client was unable to establish an unauthenticated session with the web application.

Cause: An unexpected problem prevented the client from establishing a valid, unauthenticated session with the web application.

Action: Retry the current action, confirm the authentication configuration and connectivity, and/or consult the client logs and exception details for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00505: Unexpected exception

Cause: There was an unexpected error during the current operation.

Action: Review configuration and installation. Then, retry the operation.
Level: 1

Type: ERROR

Impact: Other

ADFDI-01001: A validation error occurred for metadata property {0}. Detail: {1}

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

Action: Correct the specified property.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-01002: A validation warning occurred for metadata property {0}. Detail: {1}

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

Action: Correct the specified property.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-04000: {0} is installed on this computer with an incompatible installer. Please uninstall the currently installed version and retry the installation with the new installer.

Cause: The product was previously installed with an installation method that is not compatible with the current one.

Action: Remove the previous installation.
Level: 1

Type: ERROR

Impact: Installation

ADFDI-04001: The .NET Framework 4.0 is not installed.

Cause: The .NET Framework 4.0 prerequisite was not installed.

Action: Install the .NET Framework 4.0.
Level: 1

Type: ERROR

Impact: Installation

ADFDI-04002: The Visual Studio 2010 Tools for Office Runtime is not installed.

Cause: The Visual Studio 2010 Tools for Office Runtime prerequisite was not installed.

Action: Install Visual Studio 2010 Tools for Office Runtime.
Level: 1

Type: ERROR

Impact: Installation

ADFDI-05002: unable to locate page definition element in {0}

Cause: The root element was missing from the page definition file.

Action: Ensure that the page definition file is well formed.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05006: A component already exists at origin {0}.

Cause: An attempt was made to insert or move a component to a cell that is already in use as the origin of another component.

Action: Choose a different destination cell for the insertion or move operation.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05011: unable to move the component to new position; a component already exists at that position: {0}

Cause: An attempt was made to move a component to a cell that is already in use as the origin of another component.

Action: Choose a different destination cell for the move operation.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05012: Unable to locate or open the page definition: {0}. Control bindings are not available for this worksheet. File: {1}.

Cause: An attempt was made to load the file specified. Either some portion of the file path was invalid, the file did not exist, or the user had insufficient permissions to open the file.

Action: Ensure that the relevant properties are configured correctly.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05013: There is no page definition selected. Control bindings are not available for this worksheet.

Cause: User canceled the operation of selecting a page definition.

Action: Select a valid page definition to associate with the current worksheet.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05015: An error occurred while updating the client registry

Cause: The attempt to update the client registry was unsuccessful.

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

Type: ERROR

Impact: Session

ADFDI-05016: The workbook, {0}, is missing one or more required settings: ApplicationHomeFolder, WebPagesFolder.

Cause: The specified workbook was missing one or more settings required for publishing.

Action: Provide valid values for all settings required for publishing.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-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-05021: The destination workbook name, {0}, is already being used by an open workbook. The published workbook name cannot be the same as an open workbook even if the directories are different.

Cause: The published workbook name was the same as a workbook that was currently open.

Action: Choose a different name or close the open workbook.
Level: 1

Type: ERROR

Impact: Files

ADFDI-05022: An unexpected exception has occurred. The workbook {0} cannot be published.

Cause: An unexpected exception occurred while attempting to publish the workbook.

Action: Verify settings, installation, and configuration. Then, retry the operation.
Level: 1

Type: ERROR

Impact: Other

ADFDI-05023: There is a mismatch between the destination file extension, {0}, and source file extension, {1}. The workbook cannot be converted during publication.

Cause: The publish destination and source workbooks did not have the same file extension.

Action: Publish the workbook to a file with the same extension. Or, convert the workbook to the desired type before publishing.
Level: 1

Type: ERROR

Impact: Files

ADFDI-05024: This workbook cannot be published because the format is not supported. Use a supported format like 'Excel Workbook (*.xlsx)'.

Cause: The source workbook was not a supported file type.

Action: Convert the workbook to a supported type.
Level: 1

Type: ERROR

Impact: Files

ADFDI-05025: The destination file path exceeds the Excel limit of 219 characters. File path: {0}

Cause: The file path length exceeded the length limitation imposed by Microsoft Excel.

Action: Reduce the length of the path and retry the publish operation.
Level: 1

Type: ERROR

Impact: Files

ADFDI-05026: Cannot publish a customizable workbook to the destination: {0}

Cause: The customizable workbook was published to a invalid destination.

Action: Publish the customizable workbook to a location under the public_html directory of the project associated with current workbook.
Level: 1

Type: ERROR

Impact: Files

ADFDI-05500: error restoring server data context

Cause: A failed attempt was made to re-establish the server state for a new user session.

Action: Check the configuration of the workbook to ensure that the attributes and actions used to reestablish the server state are defined correctly. Check the server to determine whether data has been deleted.
Level: 1

Type: ERROR

Impact: Data

ADFDI-05501: value does not match for attribute {0}

Cause: The value in the cache was not equal to the attribute value.

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

Type: ERROR

Impact: Data

ADFDI-05502: unable to locate control binding {0} in binding container {1}

Cause: A failed attempt was made to locate the binding information of a UI component.

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

Type: ERROR

Impact: Programmatic

ADFDI-05503: An incorrect binding type, {0}, exists for the control binding {1} in the binding container {2}.

Cause: The binding type of the component differed from the binding type defined in the binding container.

Action: Check the configuration of the workbook and retry the operation. Ensure that the control binding type is defined correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05504: unable to find attribute: {0}

Cause: A failed attempt was made to find an attribute in the data context cache.

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

Type: ERROR

Impact: Programmatic

ADFDI-05505: unable to find action: {0}

Cause: A failed attempt was made to find a restore data context action in the data context cache.

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

Type: ERROR

Impact: Programmatic

ADFDI-05506: unable to find list control binding: {0}

Cause: A failed attempt was made to locate the list control binding.

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

Type: ERROR

Impact: Programmatic

ADFDI-05507: invalid list control binding: {0}

Cause: The binding type of the list control was not valid.

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

Type: ERROR

Impact: Programmatic

ADFDI-05509: unable to find component: {0}

Cause: A failed attempt was made to find the binding of the component.

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

Type: ERROR

Impact: Programmatic

ADFDI-05510: unable to insert column; column out-of-bounds

Cause: A failed attempt was made to insert a dynamic column into the Table because the column was not within the named range.

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

Type: ERROR

Impact: Programmatic

ADFDI-05511: unable to remove column; column out-of-bounds

Cause: A failed attempt was made to delete a dynamic column into the Table because the column was not within the named range.

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

Type: ERROR

Impact: Programmatic

ADFDI-05513: cannot find record

Cause: A failed attempt was made to locate the record flagged for deletion.

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

Type: ERROR

Impact: Data

ADFDI-05517: unable to find control {0}

Cause: A failed attempt was made to locate the control in the binding container.

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

Type: ERROR

Impact: Programmatic

ADFDI-05518: unable to set expression value for read-only expression

Cause: A failed attempt was made to set the value for a read-only expression.

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

Type: ERROR

Impact: Programmatic

ADFDI-05519: unable to find component method, {0}, to invoke.

Cause: A failed attempt was made to invoke the specified component method.

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

Type: ERROR

Impact: Programmatic

ADFDI-05524: unable to position on current table row

Cause: A failed attempt was made to update the row position in a table for the purpose of invoking an action set on the row.

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

Type: ERROR

Impact: Programmatic

ADFDI-05529: unable to load binding container metadata

Cause: A failed attempt was made to load the metadata that defines the binding container.

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

Type: ERROR

Impact: Data

ADFDI-05530: unable to initialize worksheet: {0}

Cause: A failed attempt was made to initialize a worksheet.

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

Type: ERROR

Impact: Session

ADFDI-05531: one or more rows could not be uploaded

Cause: A failed attempt was made to upload data to the web application.

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

Type: ERROR

Impact: Session

ADFDI-05535: one or more flagged rows could not be deleted

Cause: A failed attempt was made to delete flagged rows.

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

Type: ERROR

Impact: Session

ADFDI-05537: The integrity of the workbook integration could not be determined. This workbook cannot be used safely. The integration will now terminate.

Cause: The server was unable to read the client registry.

Action: Verify/correct the client registry in the web application.
Level: 1

Type: ERROR

Impact: Session

ADFDI-05538: The workbook integration has been altered after publishing. It can no longer be used safely. The integration will now terminate.

Cause: The tampering check has determined that the workbook has been altered.

Action: Obtain a fresh, unaltered copy of the published workbbook.
Level: 1

Type: ERROR

Impact: Session

ADFDI-05555: Required property {0} missing for component {1}.

Cause: Required component property not defined.

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

Type: ERROR

Impact: Programmatic

ADFDI-05557: inserted row data must first be refreshed from server

Cause: The row was successfully inserted to the database, but the row data has not been updated in the worksheet.

Action: First perform a Download or DownloadFlaggedRows operation, then retry the DeleteFlaggedRows operation.
Level: 1

Type: ERROR

Impact: Data

ADFDI-05558: CacheDataContext must specify an action and at least one attribute.

Cause: The metadata for this worksheet contains one or more invalid CacheDataContext definitions.

Action: Review and resolve CacheDataContext configuration issues and retry.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05559: Row cache data is invalid.

Cause: The row data cached for an ADF Table component is not valid.

Action: Re-download ADF Table data.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05561: Failed to read multi-sync response as expected.

Cause: The number of multi-sync responses did not match the number of multi-sync requests.

Action: Check your configuration and try the operation again.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05562: Dependent list component has been misconfigured.

Cause: The developer has incorrectly configured a list component that depends on another list component.

Action: Enable verbose logging on the client and review log for additional details on the specific configuration issue.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05563: Restore Server Data Context Cache is corrupted

Cause: The hidden cache of data was not in the expected format

Action: Obtain a new version of the workbook or Clear All Data
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05564: The list binding "{0}" has {1} values. Only the first {2} items are stored in the cache.

Cause: The number of items in the list exceeded the allowable limit.

Action: Reduce the number of items in the list. Or, configure the workbook to use a web page dialog for selecting an item from a large list of values.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05565: unable to retrieve values for the list binding "{0}"

Cause: A failed attempt was made to retrieve list values from the server.

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

Type: ERROR

Impact: Programmatic

ADFDI-05566: unable to retrieve values for the list binding "{0}", or for one or more of its dependent lists

Cause: A failed attempt was made to retrieve list values from the server.

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

Type: ERROR

Impact: Programmatic

ADFDI-05567: Unable to restore server state. This condition is an unrecoverable error. You will now be logged out of your current session.

Cause: The attempt to restore server state failed.

Action: Log in to the application and retry the operation. Examine the server logs for additional information.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05568: Failed to initialize cache for List binding: {0} in component/column: {1}, owned by type: {2} (in table: {3}).

Cause: A failed attempt was made to retrieve and cache list values from the server.

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

Type: WARNING

Impact: Programmatic

ADFDI-05569: Unable to report table status: status column is not visible.

Cause: The table was configured so that the Status column is not visible.

Action: Configure the table so that the Status column is visible.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-05570: The Automation API encountered an unexpected condition. Details: {0}

Cause: The Automation API encountered an unexpected condition.

Action: Check the configuration of the workbook and/or the automation scripts.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05571: Failed to find resource. Alias: {0} Key: {1}

Cause: The specified alias-key combination could not be located.

Action: Check the configuration of the workbook and/or resource files.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-05572: Failed to find resource bundle. Alias: {0}

Cause: The specified resource bundle could not be located.

Action: Check the configuration of the workbook and/or resource files.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-05573: Unable to perform the requested action because the worksheet protection could not be changed.

Cause: A failed attempt was made to temporarily remove protection from the worksheet.

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

Type: ERROR

Impact: Configuration

ADFDI-05574: You have modified cells in the key column. This operation can lead to data corruption. Your change will now be reverted.

Cause: An attempt was made to modify cells in the key column of an ADF Table.

Action: Do not modify cells in the key column.
Level: 1

Type: WARNING

Impact: Data

ADFDI-05575: Unable to revert the changes to cells in the key column. The affected table(s) should be considered corrupt. You should revert to a previous version.

Cause: A failed attempt was made to revert changes to the key column.

Action: Obtain a fresh copy of the integrated workbook and re-attempt the operation without modifying cells in the key column.
Level: 1

Type: ERROR

Impact: Other

ADFDI-05576: The action, {0}, cannot be invoked in this context.

Cause: An attempt was made to invoke a row-level action in a non-row-level action set.

Action: Remove this action from this action set.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05577: Failed to retrieve table row data from the server.

Cause: A failed attempt was made to retrieve table row data from the server.

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

Type: ERROR

Impact: Data

ADFDI-05578: The reserved table named range, '{0}', cannot be found or is invalid.

Cause: A failed attempt was made to access the reserved named range for the table component.

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

Type: ERROR

Impact: Configuration

ADFDI-05579: An unexpected exception occurred while performing an operation on the table identified by: {0}. Close the workbook without saving it and retry the operation.

Cause: A failed attempt was made to execute a table operation.

Action: Close the workbook without saving it and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05580: unable to bind expression part: {0}

Cause: A failed attempt was made to bind the expression part.

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

Type: ERROR

Impact: Configuration

ADFDI-05581: Unable to write component data into worksheet: {0}

Cause: A failed attempt was made to write component data to the worksheet.

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

Type: ERROR

Impact: Programmatic

ADFDI-05582: Unable to download flagged rows because the table structure has changed.

Cause: The DownloadFlaggedRows action was invoked on a table and the column structure is different from when rows were last downloaded.

Action: Check the configuration of the worksheet.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05584: Unable to convert: '{0}' to the target time zone. Close the workbook without saving it and retry the operation.

Cause: An unexpected failure has occurred while converting date time values from one time zone to another.

Action: Close the workbook without saving it and retry the operation.
Level: 1

Type: ERROR

Impact: Data

ADFDI-05585: The {0} element in the dialog page {1} should be a <span> element; the type <{2}> is not supported.

Cause: The html tag used for the reserved element in the dialog page was not supported.

Action: Contact the developer of this dialog page to use <span> tag for the reserved element
Level: 1

Type: Warning

Impact: Configuration

ADFDI-05586: Fail to hook event handler to the {0} element due to {1}. Closing the dialog with client side scripts is disabled.

Cause: Unable to hook an event handler to the reserved html element in the dialog page.

Action: Close the dialog manually if it is not closed automatically. The developer of this dialog page should avoid using client side scripts to change the value of the reserved element.
Level: 1

Type: Warning

Impact: Other

ADFDI-05587: The client and server versions do not match. Using this version of the client may result in unexpected behavior or errors.

Cause: The client and server versions did not match.

Action: Install a client that matches the server version.
Level: 1

Type: Warning

Impact: Upgrade

ADFDI-05588: The number of resource bundles ({1}) exceeds the supported limit of {0}.

Cause: The number of resource bundles exceeded the supported limit.

Action: Reduce the number of resource bundles in this workbook.
Level: 1

Type: WARNING

Impact: Files

ADFDI-05589: You are not authorized to use this worksheet for interacting with the web application.

Cause: The current user did not have the necessary permissions to access the page definition file associated with this worksheet.

Action: Log out and log back in as a different user, or contact the system administrator to request the necessary permissions.
Level: 1

Type: ERROR

Impact: Security

ADFDI-05591: The user session has changed. Re-try the operation.

Cause: The user session changed during the execution of an action set.

Action: The end-user should re-try the operation.
Level: 1

Type: ERROR

Impact: Session

ADFDI-05592: Too much changed data was uploaded.

Cause: The amount of changed data that was uploaded exceeds the web application limit.

Action: Retry the operation with less changed data.
Level: 1

Type: ERROR

Impact: Data

ADFDI-05593: The operation ({0}) was canceled.

Cause: The end-user canceled the operation.

Action: None required. The end-user may continue to interact with the worksheet and if desired, retry the operation.
Level: 1

Type: WARNING

Impact: Other

ADFDI-05594: Failed to load the client metadata

Cause: A failure occured when loading the client metadata

Action: Check the client and server logs for details about the failure.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-05595: DownloadForInsert action ignored (InsertRowEnabled is false) for table: {0}.

Cause: DownloadForInsert action was included in an action-set, but was not applicable since InsertRowEnabled was false.

Action: The developer should remove the action, or alter the table so that InsertRowEnabled is true.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05597: Dynamic columns are always visible. Ignoring Visible expression: {0}

Cause: The workbook configuration specified a Visible expression for a dynamic column

Action: The developer should adjust the configuration: remove the Visible expression or set Dynamic to True.
Level: 1

Type: WARNING

Impact: Metadata

ADFDI-05598: TableRowErrorsCache '{0}' is out of space. All previous entries will be purged.

Cause: The worksheet storing error message details was out of space.

Action: No action required.
Level: 1

Type: WARNING

Impact: Other

ADFDI-05599: The source scheme is not supported: {0}.

Cause: The specified URL had an unsupported scheme.

Action: The workbook developer should use a URL with a supported scheme.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05600: The URL is invalid: {0}.

Cause: The specified URL was incorrectly formatted.

Action: The developer should verify and correct the URL.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05601: Invalid binding attribute {0} in ADF Input Date component/column: {1}.

Cause: The datatype of binding attribute was not date or datetime.

Action: Use ADF Input Date only for attributes with date or datetime type.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05602: Unable to capture server state.

Cause: The attempt to save the current 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-05603: Unable to create a temporary row.

Cause: The attempt to create a temporary row 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-05604: Unable to launch the update web page in the default web browser. Check the default browser settings and try again.

Cause: The default web browser could not successfully be launched.

Action: Check the default browser settings.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05605: Unable to evaluate a nested custom property in EL.

Cause: A custom property string value referenced in EL was found to contain custom property EL within its value.

Action: The developer needs to modify the custom property value to remove nested custom property EL.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05606: Status initialized row(s) downloaded into table {0} will be ignored since InsertRowEnabled is false.

Cause: One or more status initialized rows were downloaded into the table, but would be ignored since InsertRowEnabled is false.

Action: The workbook developer should ensure that no status initialized rows are downloaded, or alter the table so that InsertRowEnabled is true.
Level: 1

Type: WARNING

Impact: Programmatic

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-06005: The source workbook filepath is relative: {0}

Cause: The source workbook path provided was relative, not absolute.

Action: Provide a fully-qualified file path.
Level: 1

Type: ERROR

Impact: Configuration

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 installation of {1}.

Cause: An attempt was made to open a design-time or test mode workbook using the add-in installed for runtime use.

Action: Use only published workbooks with the add-in installed for runtime use. Enable the designer tools in order to use workbooks in other modes.
Level: 1

Type: ERROR

Impact: Installation

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-07541: Unable to write metadata to file: {0}

Cause: There was an unexpected exception while attempting to write the XML to the specified file.

Action: Review the inner exception details to determine root cause.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07542: Unable to import workbook configuration metadata.

Cause: There was an unexpected exception while attempting to load the workbook configuration metadata into the current workbook.

Action: Review the inner exception details to determine root cause.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07543: Unable to import workbook configuration metadata due to schema validation failures.

Cause: The attempt to import workbook configuration metadata failed due to XML schema validation failures.

Action: Review the client logs for detailed information on the schema validation failures and correct the XML.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07544: Unexpected exception during write to metadata cache. The workbook may be corrupted.

Cause: The attempt to write workbook configuration metadata failed while writing to the cache.

Action: Discard the workbook and review the inner exception details to determine root cause.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07545: Unable to display help file.

Cause: The attempt to display the help file failed unexpectedly.

Action: Check the local browser and network settings. Then, retry the operation.
Level: 1

Type: ERROR

Impact: Other

ADFDI-07546: Duplicate component id detected during import: {0}. Replacing with {1}.

Cause: A duplicate component id was found.

Action: Review and update any dependencies on the old component id.
Level: 1

Type: WARNING

Impact: Other

ADFDI-07547: Unable to save diagnostic report: {0}.

Cause: There was an unexpected exception while attempting to save diagnostic report to the specified file.

Action: Review the inner exception details to determine root cause.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07548: 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-07549: Unable to load add-in {0} because an incompatible installation was detected.

Cause: Multiple copies of the add-in were installed with incompatible installers.

Action: Uninstall all but one of the add-ins.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-07550: There was a problem loading the user settings file.

Cause: An unexpected problem prevented the program from properly reading or parsing the user settings file.

Action: Check whether the file is accessible or has become corrupted. Delete the file and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-07551: There was a problem writing to the user settings file.

Cause: An unexpected problem prevented the program from properly creating and/or writing to the user settings file.

Action: Check whether the file is accessible and that sufficient disk space is available. Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-07553: This workbook contains features that are incompatible with this version of {0}. This workbook will now be disabled.

Cause: This workbook was edited by a newer version of ADFdi and includes new features that are incompatible with earlier versions. In rare cases, this condition might be the result of a corrupted workbook.

Action: Install a newer version of the client and re-open the workbook.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07554: The specified path, file name, or both are too long.

Cause: The operation was attempted with a path or file name that exceeded limits.

Action: Re-attempt the operation with a shorter path or file name.
Level: 1

Type: ERROR

Impact: Files

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

Cause: Unable to find the desired key in the bundle.

Action: Review the server logs for additional detail on the underlying cause.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-55000: An unexpected exception occurred on the server. Consult the server logs for more detail.

Cause: An unexpected condition arose while handling the desktop integration request.

Action: Review the server logs for additional detail on the underlying cause.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55001: XML element {0} missing required attribute {1}

Cause: Invalid request XML was received.

Action: Review the server logs to ensure that only supported clients are accessing the ADFdi Remote Servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55002: The object, {0}, is not available.

Cause: An expected object was not found or was unavailable.

Action: Ensure that both the client and server metadata are configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-55003: The object, {0}, is not available. Name: {1}

Cause: An expected object was not found or was unavailable.

Action: Ensure that both the client and server metadata has been configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-55004: invalid GetResourceBundle request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55005: invalid SyncModel request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55006: unexpected value specified for XML element {0}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55007: invalid request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55008: invalid request method: {0}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55009: user session unavailable

Cause: The user was not authenticated.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Session

ADFDI-55010: expected XML element {0}; current element is {1}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55011: unexpected end-of-file in XML input stream

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55012: invalid XML element: {0}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55013: expected XML reader state {0}; current state is {1}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55014: invalid child XML element {1} within XML element {0}

Cause: The XML request sent by the client was invalid.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55017: The current row count exceeds the configured limit.

Cause: The maximum number of rows requested by the client was exceeded.

Action: Submit a new request that conforms to the limit.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55018: exception occurred while reading an XML request

Cause: A malformed request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55019: exception occurred while writing the XML response

Cause: Details about the underlying cause of the error are contained in the server logs.

Action: Review the server logs for details about additional steps to take.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55021: A version mismatch was detected for {0}. Version {1} was found, version {2} was expected.

Cause: The client version does not match the required level for the DIRemoteServlet.

Action: Upgrade the client and/or server so that compatible versions are in use.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55022: invalid SessionStatus request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55023: invalid MultiSyncModel request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55025: The control binding definition for item {0} is incorrect or incompatible. {1}

Cause: The control binding definition has been misconfigured, or an incompatible control binding has been encountered.

Action: Check the control binding definition and ensure that only supported control bindings are used.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55026: invalid TamperCheck request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55027: invalid EncodeURL request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55028: unexpected value specified for XML element {0}: {1}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55030: Cannot find the client registry file: {0}

Cause: System could not find the client registry file in the web-inf location.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55031: An error occurred while trying to read client registry file

Cause: While trying to read the client registry file, an I/O error occurred.

Action: Check logs for details of I/O error and address root case to enable file access.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55032: Unable to set attribute {0} (row object unavailable: {1})

Cause: Client attempted to set an attribute value when no server row is available.

Action: Refresh the client data and retry the operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55033: {0}: cannot convert the input value ({1}) to the expected data type ({2}).

Cause: The input values were not consistent with expected data type.

Action: Correct input values according to data type.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55034: Tamper check is disabled.

Cause: The servlet was configured to disable the tamper check feature.

Action: Adjust servlet initialization parameters as desired.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-55035: Tamper check did not succeed. Result: {0}

Cause: Tamper check was unable to match the hashcode of the client to the expected value.

Action: Adjust the configuration of tamper check or obtain a new copy of the workbook.
Level: 1

Type: WARNING

Impact: Data

ADFDI-55036: Received a request with unexpected content type: {0}

Cause: A request with an unexpected content type was received.

Action: Use only supported content types.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55037: Tamper check is configured to allow missing entries.

Cause: The tamper check feature was configured to allow missing entries.

Action: Adjust servlet initialization parameters as desired.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-55038: The region binding includes an unsupported control type: {0}

Cause: The page definition was configured to use an unsupported control type.

Action: Remove the unsupported type.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-55039: Unexpected servlet failure

Cause: The servlet has failed due to an unexpected condition.

Action: Review the server logs for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55040: Unable to read requested resource bundle: {0}

Cause: An attempt was made to load a resource bundle that was not available.

Action: Review the configuration to ensure that the resource bundle is available.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-55041: Aborting the commit action for a transaction.

Cause: The commit action was aborted for the transaction due to error in the binding container.

Action: Clear the error conditions and retry the operation.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55042: Unable to set position for {0} with value {1}

Cause: A failed attempt was made to position a control binding by attribute value.

Action: Refresh the client data and retry the operation or review the server logs for more information.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55043: Unable to locate parameter {0} for binding container {1}

Cause: A failed attempt was made to set a parameter.

Action: Review the configuration to ensure that the parameter is available.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-55044: user session has changed

Cause: The client user session timed out or was otherwise invalid.

Action: Establish a valid user session.
Level: 1

Type: ERROR

Impact: Session

ADFDI-55045: unable to set position to row {0}

Cause: A failed attempt was made to position a control binding by row index value.

Action: Refresh the client data and retry the operation or review the server logs for more information.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55046: A value is required for {0}.

Cause: An attempt was made to set an empty value for a mandatory attribute.

Action: Provide a non-empty value for this property.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55047: retry failed for batch request #{0}

Cause: A failed attempt was made to retry a successful batch request after restoring to datacontrol savepoint.

Action: Review the server logs for more details about the cause of the failure.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55048: The current user is not authorized to access the binding container: {0}

Cause: The current user did not have the necessary permissions to access the binding container.

Action: Log out and log back in as a different user, or contact the system administrator to request the necessary permissions.
Level: 1

Type: ERROR

Impact: Security

ADFDI-55049: unable to run the setup action: {0}

Cause: The specified setup action was either unavailable on the server or failed with an exception.

Action: Review the configuration to ensure the setup action id is correct, and see server logs for more details on the cause of failure.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-55051: The transaction size limit was exceeded

Cause: Too much data was sent to the server without committing any changes to the database.

Action: Reduce the amount of pending changes and retry the current action.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55052: invalid client metadata request

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55053: Row changes could not be applied: resubmit the changes.

Cause: Some other errors prevented the changes for this row from being applied.

Action: Correct the other errors and retry the operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55054: Unable to position a range paging rowset with pending changes.

Cause: An attempt was made to navigate a rowset in range paging mode when the rowset has pending changes.

Action: Commit or rollback pending changes before navigating.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55055: Authorization enforcement has been disabled for this instance of {0}

Cause: The web application was configured so that authorization will not be enforced by ADF Desktop Integration.

Action: Configure the web application so that authorization is enforced by ADF Desktop Integration.
Level: 1

Type: WARNING

Impact: Security

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

3 ADFSHARE-00002 to ADFSHARE-00300

ADFSHARE-00002: For more information, enable logging for oracle.adf.share.ADFContext.leak at SEVERE level.

Cause:

Action:
Level: 1

Type: Error

Impact: Other

ADFSHARE-00002: Found {0} sticking to oldContext, while the current application is {1}

Cause:

Action:
Level: 1

Type: Error

Impact: Other

ADFSHARE-00010: An exception is encountered.

Cause: An unknown problem caused an exception.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00020: Config XML parsing error.

Cause: Encountered error while parsing the config XML.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00030: Callback parsing error

Cause: Encountered error.

Action: See the associated exceptions.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00040: Close config stream error

Cause: Error encountered while closing the inputStream to remove reference to the adf-config.xml file so that it undeploys successfully.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00050: Config XML syntax error. Error at Column number: {0}, Line number: {1}.

Cause: Encountered error while parsing the config XML.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00110: MDS Exception encountered in parse ADF Configuration

Cause: Error encountered while parsing ADF Configuration. {0}

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00120: Error encountered while creating the MDS Session. Application state will be reset. Please logout and log back in if problem persists.

Cause: Encountered error {0}.

Action: See the associated exceptions.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00130: Error while building the MDS customization configuration

Cause: Encountered error {0}.

Action: See the associated exceptions.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00140: Error while creating MDS tenant instance

Cause: Encountered error while creating MDS tenant instance. {0}

Action: See the associated exceptions.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00150: MDS Configuration Exception encountered in parse ADF Configuration

Cause: Encountered MDS exceptions while parsing the ADF Configuration. {0}

Action: See the associated exceptions and correct the contents of the file.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00160: ADF Session Options edit rev number mismatch: old = {0}, new = {1}.

Cause: Since this session/browser tab processed its last request, another session/browser tab changed session options. Hence this session/brower tab is stale, and must perform application reset.

Action: Perform application reset.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00170: MDS label cannot be changed while in sandbox.

Cause: This session is in sandbox. The MDS label associated with the sandbox is in effect. You are not allowed to change this label.

Action: Avoid setting MDS label when sandbox is in effect.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00180: MDS label {0} is not found.

Cause: MDS label by that name is not found.

Action: Check the label name and make sure the label exists.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00190: Trimming Customization Class to invalid name or value: {0}

Cause: Customization Class name or value not found in application configuration.

Action: Check that the CC name and value are correct and that the CC is in the adf-config.xml CC list.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00200: The operation {0} is not permitted in ADFSO while {1} Mode is in place. Sandbox Name: {2}

Cause: The operation you tried to perform is not permitted within a sandbox when {1} Mode is in place.

Action: To preview CustomizationClass changes, please call setMode(ADFSessionOptions.Mode.PREVIEW, ADFSessionOptions.CLEVEL_CHECK_AND_CHANGE). To enter another sandbox, please call unsetSandboxSettings(ADFSessionOptions.CLEVEL_CHECK_AND_CHANGE) first.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00210: The CustomizationClass name in SandboxSettings for Sandbox {2} does not match the one stored by ADF or MDS. {3}

Cause: The CustomizationClass name is already set in either ADFSessionOptions or MDS SandboxMetadata for that sandbox, and does not match the one provided to setSandboxSettings.

Action: Make sure the CC name is not being set differently somewhere else.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00220: Sandbox name mismatch: current = {0}, expected = {1}.

Cause: The name of the Sandbox found active in MDS does not match the one set by ADF at the beginning of the request.

Action: Make sure the MDS session initialized by ADF is not being replaced during the request.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00230: Label name mismatch: current = {0}, expected = {1}.

Cause: The name of the Label found active in MDS does not match the one set by ADF at the beginning of the request.

Action: Make sure the MDS session initialized by ADF is not being replaced during the request.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00240: Customization Class list trimming mismatch: current = {0}, expected = {1}.

Cause: The customization classes found active in MDS do not match the trimming set by ADF at the beginning of the request.

Action: Make sure the MDS session initialized by ADF is not being replaced during the request.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00250: Definition {0} has unresolved merge conflicts.

Cause: Not all merge conflicts have been resolved. This exception indicates that some merge conflicts were not resolved, and another round of merge conflict resolution is necessary.

Action: Merge conflict resolution must be performed.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00250: Definitions {0} have unresolved merge conflicts.

Cause: Not all merge conflicts have been resolved. This exception indicates that some merge conflicts were not resolved, and another round of merge conflict resolution is necessary.

Action: Merge conflict resolution must be performed.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00260: Merge for definition {0} failed for elem {1}. Inserted elem [{2} -> {3}] was deleted by another user.

Cause: During object merge, found a metadata element which was marked for insertion by the current user, but was deleted by another transaction committed or published by another user.

Action: Resolve this metadata merge conflict.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00270: Merge for definition {0} failed for elem {1}. Updated elem [{2} -> {3}] was deleted by another user.

Cause: During object merge, found a metadata element which was marked for update by the current user, but was deleted by another transaction committed or published by another user.

Action: Resolve this metadata merge conflict.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00280: Merge for definition {0} failed for elem {1}. Inserted elem [{2} -> {3}] was inserted by another user.

Cause: During object merge, found a metadata element which was marked for insertion by the current user, but was inserted by another transaction committed or published by another user.

Action: Resolve this metadata merge conflict.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00290: Merge for definition {0} failed for elem {1}. Updated elem [{2} -> {3}] was updated by another user.

Cause: During object merge, found a metadata element which was marked for update by the current user, but was updated by another transaction committed or published by another user.

Action: Resolve this metadata merge conflict.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00300: Merge for definition {0} failed for elem {1}. Unresolvable conflict on elem {2}, value: {3}

Cause: During object merge, found a metadata element which was updated through another transaction. However, this change caused an unresolve conflict.

Action: Resolve this metadata merge conflict.
Level: 2

Type: ERROR

Impact: Programmatic

4 B2B-EVT-10001 to B2B-EVT-10003

B2B-EVT-10001: Message Parsing Failed on endpoint and Parse failure exceeded limit. Disabling the endpoint

Cause: Failed to parse the incoming MLLP Message.

Action: Endpoint disabled. Enable the Endpoint and check the payload to make sure it is valid.
Level: 1

Type: ERROR

Impact: Process

B2B-EVT-10002: Pausing the endpoint. Nack received and skip threshold exceeded for endpoint

Cause: Pausing the endpoint. Nack received and skip threshold exceeded for endpoint

Action: Resume the endpoint
Level: 1

Type: ERROR

Impact: Process

B2B-EVT-10003: Resetting the connection. Message Parsing Failed on endpoint and Parse failure exceeded limit

Cause: Resetting the connection. Message Parsing Failed on endpoint and Parse failure exceeded limit

Action: Make sure the payload is valid.
Level: 1

Type: ERROR

Impact: Process

5 B2B-50006 to B2B-53104

B2B-50006: Exception Received

Cause: B2B received an exception message from the trading partner.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50007: Notification of failure received

Cause: B2B received a notification of failure - out of band exception from trading partner

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50008: Document level retry count is exhausted.

Cause: Maximum number of document level retries has been reached.

Action: Increase the maximum number of document level retries
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50009: Failed to Send

Cause: B2B cannot send message to the trading partner

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50010: Trading partner agreement identification error

Cause: B2B cannot identify an agreement using the current details

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50011: Message Correlation Error

Cause: B2B cannot correlate the message

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50012: Pack/Unpack Error

Cause: Error in packaging

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50013: Security Error

Cause: Error in security validation

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50014: General Error

Cause: Internal error in engine

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50015: In-band notification error

Cause: Internal engine error

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50021: User request to set error for all pending batch messages with same batch id [{0}]. The Message IDs are {1}

Cause: User request to set error for all pending batch messages with same batch id [{0}].

Action: User request to set error for all pending batch messages with same batch id [{0}]. This error is expected, hence no action is necessary
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50025: Repository error

Cause: Error accessing metadata repository

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50026: Repository error

Cause: Error accessing stream data store

Action: Review the diagnostic log to verify the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50027: Failed to write data into output stream.

Cause: Failed to write data into output stream.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50028: Failed to read data from input stream.

Cause: Failed to read data from input stream.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50029: B2B runtime error

Cause: A runtime error has occurred.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50030: B2B Negative Ack Received

Cause: B2B has received a negative acknowledgement

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50031: B2B general error

Cause: A general error has occurred

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50032: B2B exchange protocol negative acknowledge received

Cause: Received a negative exchange acknowledge message.

Action: Review the negative exchange acknowledge message to determine the cause, or check with the trading partner.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50033: B2B functional acknowledgment processing error

Cause: An error occurred during functional acknowledgment processing.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50034: B2B negative functional acknowledgment

Cause: A negative functional acknowledgment is received.

Action: Review the negative functional acknowledge message to determine the cause or check with the trading partner.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50035: B2B exception message processing error

Cause: An error occurred during exception message processing.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50036: B2B trading partner agreement identification error

Cause: An error had occurred during identify trading partner agreement.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50037: B2B inbound message processing error

Cause: An error occurred during incoming message processing.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50038: B2B outbound app message input {0} header processing error

Cause: An error occurred during outbound {0} input processing.

Action: Review the input properties sent for outbound message processing. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50039: Negative Interchange acknowledgment received

Cause: A negative Interchange acknowledgment is received.

Action: Review the negative Interchange acknowledge message to determine the cause or check with the trading partner.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50040: Unable to correlate the received Functional Ack

Cause: A Functional Ack received for unknown message.

Action: Review the control number of the incoming message
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50041: TopLink server session initialization error

Cause: An error occurred during TopLink server session initialization.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50042: B2B trace context initialization error

Cause: An error occurred during trace context initialization.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50043: Functional acknowledgement received for errored business message with id {0}

Cause: Functional acknowledgement received for errored business message.

Action: Review the control number of the original business in the incoming FA payload.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50044: Exception Message Received from backend

Cause: An Exception Message Received from backend.

Action: Review the payload from the Exception message.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50050: Engine initialization error.

Cause: An error occurred during engine initialization.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. If the problem persists, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50051: Failed to shut down the B2B engine.

Cause: An error occurred during engine shut down.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. If the problem persists, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50052: Engine already initialized.

Cause: Attempt made to initialize B2B engine which has been initialized already.

Action: Ensure that the engine is stopped before attempting to initialize
Level: 1

Type: NOTIFICATION

Impact: Process

B2B-50059: Error in starting B2B Server.

Cause: An error has occurred while starting the server.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INTERNAL_ERROR

Impact: Process

B2B-50060: Error in stopping B2B Server

Cause: An error has occurred while stopping the server.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50075: Error loading document or exchange plug-in.

Cause: Error loading document or exchange plug-in.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50076: Error loading packaging plug-in.

Cause: Error loading packaging plug-in.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50077: Cannot Initialize Transport.

Cause: Cannot Initialize Transport.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50078: Cannot shut down transport.

Cause: Cannot shut down transport.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50079: Transport error

Cause: An error has occurred in transport layer

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50080: Exchange protocol identification error.

Cause: Failed to identify the exchange protocol of the message.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50081: Duplicate exchange protocol message error

Cause: Duplicate exchange protocol message generated by the trading partner.

Action: Report this error to the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-50082: Duplicated Control Number error

Cause: Message received with duplicate control number {0}.

Action: Report this error to the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-50083: Document protocol identification error.

Cause: Failed to identify the document protocol for the message.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50084: No service found

Cause: Requested service was not registered in system

Action: Check requested web service URL
Level: 1

Type: ERROR

Impact: Process

B2B-50085: Duplicated transaction number error for xpath {0} with value {1}. The message id : {2}

Cause: Message received with duplicate transaction number error for xpath {0} with value {1}. The message id : {2}

Action: Check the xpath value of the message
Level: 1

Type: ERROR

Impact: Process

B2B-50086: Error during the identification of Group segment in payload. {0}

Cause: Failed to identify the document protocol for the message.

Action: Check the group segment in the payload.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50087: Error during the identification of Interchange segment in payload. {0}

Cause: Failed to identify the document protocol for the message.

Action: Check the group segment in the payload.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50545: An agreement {0} has expired or is not in force as yet. The effective From/To dates are {1} - {2}.

Cause: An agreement effective From/To dates are invalid.

Action: Change the agreement effective From/To dates.
Level: 1

Type: ERROR

Impact: Process

B2B-50546: Information given to identify an agreement is insufficient: FromTP {0}, ToTP {1}, document type {2}.

Cause: Failed to identify the agreement

Action: Make sure From/To TP and document information is not Null.
Level: 1

Type: ERROR

Impact: Process

B2B-50547: Agreement not found for trading partners: FromTP {0}, ToTP {1} with document type {2}.

Cause: Failed to identify the trading partner agreement from the given input values.

Action: Make sure there is an agreement configured for the From/To trading partner and document information that presents in the message.
Level: 1

Type: ERROR

Impact: Process

B2B-50548: Agreement {0} not in active state.

Cause: Agreement was not in active state.

Action: Make sure the agreement is deployed and it is in Active state.
Level: 1

Type: ERROR

Impact: Process

B2B-50549: Cannot uniquely identify the trading partner. The trading partners {0} have the same set of identifications.

Cause: The trading partners {0} have the same set of identifications

Action: Make sure the trading partners have unique identifications
Level: 1

Type: ERROR

Impact: Process

B2B-50550: Cannot find the trading partner for the given identification type {0} and value {1}

Cause: The trading partner was not exist for the given identification type and value.

Action: Create or update the trading partner with the given identification type and value.
Level: 1

Type: ERROR

Impact: Process

B2B-50601: Agreement found but the certificate used for client authentication may not represent the Trading Partner {0} whom it claims to be.

Cause: Certificate used for client authentication may not belong to the Trading Partner.

Action: Please make sure Trading partner alias has been configured correctly against Security Identifier. If it is not, then it is a serious security error, please consult your security administrator for further course of action.
Level: 1

Type: ERROR

Impact: Process

B2B-50602: Keystore not available to validate the incoming certificate over SSL.

Cause: Keystore may not be properly configured in B2B to validate the incoming SSL client certificate.

Action: Please make sure keystore has been configured correctly in B2B.
Level: 1

Type: ERROR

Impact: Process

B2B-50603: Agreement found but authenticated principal(user) over http do not represent the Trading Partner {0} whom it claims to be.

Cause: Authenticated user may not represent the Trading Partner.

Action: Please make sure the Security Identifier configuration in B2B against the Trading Partner is correct. If the value is correct, then it is serious security error, please consult your security administrator for further course of action.
Level: 1

Type: ERROR

Impact: Process

B2B-50651: Agreement not found for trading partners: FromTP {0}, ToTP {1} with {2}.

Cause: Failed to match the service, action, servicetype for the trading partner agreement from the message.

Action: Make sure there is an agreement that contains a matching service, action, servicetype in the CPA configured for the From/To, service,action, servicetype information that is present in the message.
Level: 1

Type: ERROR

Impact: Process

B2B-50701: The agreement {0} cannot be activated because a similar agreement {1} found in active state

Cause: Similar agreement found in active state. There cannot be two agreements with the same trading partners, document type, version, and direction.

Action: Make inactive existing active agreement which has the same trading partners, document type, version, and direction.
Level: 1

Type: ERROR

Impact: Process

B2B-50702: {0} does not exist in the repository.

Cause: {0} does not exist in the repository.

Action: Channel/TPName does not exist in the repository. Get the latest list of channels.
Level: 1

Type: ERROR

Impact: Process

B2B-50703: Endpoint {0} does not exist in the group.

Cause: Endpoint {0} does not exist in the group.

Action: Endpoint does not exist in the group. Get the latest list of endpoints.
Level: 1

Type: ERROR

Impact: Process

B2B-50704: Group {0} does not exist in the repository.

Cause: Group {0} does not exist in the repository.

Action: Group does not exist in the repository. Get the latest list of group.
Level: 1

Type: ERROR

Impact: Process

B2B-50705: Duplicate Endpoint {0}.

Cause: Endpoint {0} already exist in the repository

Action: Endpoint already exist in the repository.Can not create same name endpoint
Level: 1

Type: ERROR

Impact: Process

B2B-50706: No callout for internal delivery channel.

Cause: Callout can not be set for internal delivery channel.

Action: Remove callout from internal delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-50707: Endpoint Validation Error

Cause: Endpoint validation error.

Action: Endpoint validation error.Check the diagnostic log for more details.
Level: 1

Type: ERROR

Impact: Process

B2B-50708: Mandatory parameter value missing.

Cause: Mandatory Parameter can not be null.

Action: Provide the mandatory parameter value.
Level: 1

Type: ERROR

Impact: Process

B2B-50709: Endpoint Disablement Failed.

Cause: Endpoint can not disabled

Action: Endpoint Disablement Failed. Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

B2B-50710: Document Protocol {0} does not supported

Cause: Document Protocol {0} not supported.

Action: Document Protocol does not supported.
Level: 1

Type: ERROR

Impact: Process

B2B-50711: Document definition {0} not exists

Cause: Document definition {0} does not exists.

Action: Document definition does not exists.
Level: 1

Type: ERROR

Impact: Process

B2B-50712: Error in removing document.

Cause: Error while removing document from endpoint.

Action: There is error while removing document from endpoint. Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

B2B-50713: Internal Delivery Channel is used in endpoint document

Cause: Internal Delivery Channel is used in endpoint document

Action: Internal Delivery Channel is used in endpoint document. Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

B2B-50714: IDREF_KEY Missing.

Cause: IDREF_KEY Missing in configuration.

Action: IDREF_KEY Missing in configuration. Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

B2B-50715: No document attached to endpoint

Cause: There is no document attached to endpoint.

Action: There is no document attached to endpoint.There should be at least one document attached to enable the endpoint.Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

B2B-50716: FTP Sequencing Parameters missing

Cause: timestamp_format,timestamp_offset,timestamp_source values are must for FTP if Sequencing is enabled

Action: Provide timestamp_format,timestamp_offset,timestamp_source values for FTP endpoint.
Level: 1

Type: ERROR

Impact: Process

B2B-50717: Block characters missing

Cause: Block characters parameters values are missing.

Action: Provide the Block characters parameters.
Level: 1

Type: ERROR

Impact: Process

B2B-50718: Channel is associated with {0} TradingPartner(s) and associated TradingPartner(s) are {1}

Cause: Channel is associated with {0} TradingPartner(s) and associated TradingPartner(s) are {1}

Action: Make sure channel is not associated with any TradingPartner(s).
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50741: WS-HTTP transport protocol must have WSDL Artifacts.

Cause: WS-HTTP transport protocol did not have WSDL Artifacts.

Action: make sure WS-HTTP transport protocol has WSDL Artifacts.
Level: 1

Type: ERROR

Impact: Process

B2B-50742: Service parameter are not well formed in WS-HTTP channel.

Cause: service parameter did not have namespace encloses with curly braces in WS-HTTP Channel.

Action: Make sure service parameter has namespace encloses with curly braces in WS-HTTP channel.
Level: 1

Type: ERROR

Impact: Process

B2B-50743: Invalid Payload received for Sync Request from Backend. Payload is null

Cause: Either Back-end composite is a One-Way composite, or it is not configured properly to return a response.

Action: Make sure Composite is configured to send a response
Level: 1

Type: ERROR

Impact: Process

B2B-50744: Keystore details missing or invalid.

Cause: Keystore details have not been provided or are invalid.

Action: Provide Keystore details.If provided then check the validity of keystore location and password.
Level: 1

Type: ERROR

Impact: Process

B2B-50801: No input value is specified. At least one input value is needed: From/To trading partner or Document or Action

Cause: Missing input values

Action: Specify input values such as From/To trading partner or Document or Action
Level: 1

Type: ERROR

Impact: Process

B2B-50901: Failed to find a business message with B2BMessageId {0}.

Cause: Failed to find a business message with B2BMessageId.

Action: Review the UI report to verify that a message exists with B2BMessageId.
Level: 1

Type: ERROR

Impact: Process

B2B-50902: Failed to find a wire message with B2BMessageId {0}.

Cause: Failed to find a wire message with B2BMessageId.

Action: Review the UI report to verify that a message exists with B2BMessageId.
Level: 1

Type: ERROR

Impact: Process

B2B-50903: Message {0} retry count is zero.

Cause: The maximum number of message retries has been reached.

Action: Increase the maximum number of retries in delivery channel.
Level: 1

Type: NOTIFICATION

Impact: Process

B2B-50904: ReferTo message not found.

Cause: The message ID specified in the header RefToMessageID not found.

Action: It is possible that the original message was purged. Try resubmitting the original message.
Level: 1

Type: ERROR

Impact: Process

B2B-50906: Failed to retrieve value for the given XPATH.

Cause: Error occurred while extracting XPATH value.

Action: Make sure XPATH in document definition is correct and applicable for the payload
Level: 1

Type: ERROR

Impact: Process

B2B-51000: General packaging Error

Cause: Packaging details were incorrect.

Action: Correct the packaging details in delivery channel.
Level: 1

Type: INTERNAL_ERROR

Impact: Process

B2B-51001: Packaging fail

Cause: Packaging information were insufficient.

Action: Correct the packaging details in delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-51002: Unpacking fail

Cause: Packaging headers were incorrect.

Action: Correct the packaging details in delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-51003: Encoding failed

Cause: Encoding type was incorrect.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51004: Decoding failed

Cause: Decoding type was incorrect.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51005: Validating packaging metadata failed.

Cause: Packaging metadata was insufficient.

Action: Verify packaging metadata to pack the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51006: Invalid input parameter

Cause: Packaging input parameters were invalid.

Action: Verify the packaging parameters and packaging metadata.
Level: 1

Type: ERROR

Impact: Process

B2B-51007: Missing packaging metadata information.

Cause: Missing few packaging metadata.

Action: Verify the packaging metadata.
Level: 1

Type: ERROR

Impact: Process

B2B-51008: Circular dependency in packaging metadata.

Cause: Circular dependency found in packaging metadata.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51009: Missing one or more packaging elements in packaging metadata.

Cause: Missing one or more packaging elements in packaging metadata.

Action: Verify packaging metadata has packaging elements.
Level: 1

Type: ERROR

Impact: Process

B2B-51010: Missing composite packaging element in packaging metadata.

Cause: None of the composite packaging elements exist in the Multipart message.

Action: Make sure Multipart message has at least one composite packaging element.
Level: 1

Type: ERROR

Impact: Process

B2B-51011: Invalid packaging metadata.

Cause: Message has more than one simple part. Hence, failed to package the message.

Action: Verify MIME message has only one simple part.
Level: 1

Type: ERROR

Impact: Process

B2B-51012: Missing list of message components.

Cause: Missing list of message component in the message.

Action: Verify the message has list of component.
Level: 1

Type: ERROR

Impact: Process

B2B-51013: Missing one or more message components in the list of message components.

Cause: Protocol components did not have all the required components while packaging information.

Action: Verify the protocol components and set all the required components for packaging the information.
Level: 1

Type: ERROR

Impact: Process

B2B-51014: Missing data for message component.

Cause: Invalid data for message component.

Action: Verify message has component data.
Level: 1

Type: ERROR

Impact: Process

B2B-51015: Missing security information.

Cause: Invalid security information.

Action: Verify security information is exist in packaging.
Level: 1

Type: ERROR

Impact: Process

B2B-51016: Missing signature information.

Cause: Invalid digital signature information.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51017: Missing encryption information.

Cause: Required envelope information did not exist.

Action: Verify the required envelope information available in packaging.
Level: 1

Type: ERROR

Impact: Process

B2B-51018: Message is not digitally signed.

Cause: Message was not digitally signed.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51019: Message is not encrypted.

Cause: Message was not encrypted.

Action: Verify the message which has to be encrypted.
Level: 1

Type: ERROR

Impact: Process

B2B-51020: Signature protocol is not supported.

Cause: Signature protocol was not Secure Multipurpose Internet Mail Extensions (S/MIME).

Action: Use Secure Multipurpose Internet Mail Extensions (S/MIME) as a signature protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-51021: Encryption protocol is not supported.

Cause: Encryption protocol was not a Secure Multipurpose Internet Mail Extensions (S/MIME).

Action: Use Secure Multipurpose Internet Mail Extensions (S/MIME) as a encryption protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-51022: Digest algorithm does not match.

Cause: Invalid digest algorithm.

Action: Verify digest algorithm.
Level: 1

Type: ERROR

Impact: Process

B2B-51023: Required signature information are already set for message.

Cause: Attempt made to set the signature information when it already has been set.

Action: Remove the existing signature information before attempting to set this new signature information.
Level: 1

Type: ERROR

Impact: Process

B2B-51024: Required envelope information is already set for message.

Cause: Attempt made to set envelope information when it has already been set.

Action: Remove the existing envelope information before attempting to set this new envelope information.
Level: 1

Type: ERROR

Impact: Process

B2B-51025: Keystore resource location incorrect

Cause: Incorrect keystore location specified.

Action: Specify correct keystore location.
Level: 1

Type: ERROR

Impact: Process

B2B-51026: Encoding type is not supported

Cause: Encoding type was not supported.

Action: Verify supported encoding type as any one of base64, quoted-printable, 7bit, 8bit, or binary.
Level: 1

Type: ERROR

Impact: Process

B2B-51050: MIME Content-Types do not match.

Cause: Mismatched MIME body part and MIME type.

Action: Verify the Content-Types in MIME body part.
Level: 1

Type: ERROR

Impact: Process

B2B-51051: MIME Content-Type parameter lists do not match.

Cause: While creating MIME body part, MIME Content-Type parameter lists mismatch.

Action: Verify the MIME Content-Type parameters list.
Level: 1

Type: ERROR

Impact: Process

B2B-51052: Invalid MIME Content-Type header or information.

Cause: Missing MIME Content-Type and value.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51053: Invalid MIME content disposition header or information.

Cause: Missing MIME content disposition header value.

Action: Verify MIME header content disposition.
Level: 1

Type: ERROR

Impact: Process

B2B-51054: Missing MIME Content-Type header information.

Cause: MIME Content-Type information was not exist.

Action: Verify MIME Content-Type header exist.
Level: 1

Type: ERROR

Impact: Process

B2B-51055: Missing information for message component.

Cause: Information were not exist for message component.

Action: Verify the message component information.
Level: 1

Type: ERROR

Impact: Process

B2B-51056: Missing or unable to read data from message.

Cause: Failed to read data from message.

Action: Verify the message data.
Level: 1

Type: ERROR

Impact: Process

B2B-51057: Invalid or corrupted message.

Cause: Invalid message format.

Action: Verify the message format.
Level: 1

Type: ERROR

Impact: Process

B2B-51075: Missing signer certificate.

Cause: Signer certificate not found.

Action: Provide the certificate to sign the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51076: Missing encryption certificate.

Cause: Encryption certificate not found.

Action: Provide the certificate to encrypt the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51077: Missing certificate chain.

Cause: Invalid certificate chain was exist.

Action: Provide the proper certificate with certificate chain.
Level: 1

Type: ERROR

Impact: Process

B2B-51078: Message has invalid digest information.

Cause: Failed to digest message or message corrupted.

Action: Provide appropriate digest for message.
Level: 1

Type: ERROR

Impact: Process

B2B-51079: S/MIME version is not supported.

Cause: Unsupported S/MIME version.

Action: Verify the S/MIME version should be either 2.0 or 3.0.
Level: 1

Type: ERROR

Impact: Process

B2B-51080: Signature algorithm {0} is not supported.

Cause: Unsupported signature algorithm specified.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51081: Digest algorithm {0} is not supported.

Cause: Unsupported digest algorithm specified.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: ERROR

Impact: Process

B2B-51082: Encryption algorithm {0} is not supported.

Cause: Unsupported encryption algorithm specified.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51083: General failure creating S/MIME digital signature.

Cause: A failure has occurred when creating the S/MIME digital signature.

Action: Verify that the keystore has the correct private key and certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51084: General failure verifying S/MIME digital signature.

Cause: A general failure has occurred when attempting to verify the S/MIME digital signature.

Action: 1. Use correct certificate to verify the signature. 2. Message might have been corrupted. Check with the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51085: General failure encrypting S/MIME message.

Cause: A general failure has occurred when attempting to encrypt the S/MIME digital signature.

Action: Use valid trading partner certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51086: General failure while decrypting S/MIME message.

Cause: General failure while decrypting S/MIME message.

Action: 1. Use correct Key Pair to decrypt the message. 2. Message might have been corrupted. Check with the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51087: Could not create digest data for S/MIME digital signature {0}.

Cause: Creating digest data for S/MIME digital signature failed {0}.

Action: Use the supported algorithm as per the S/MIME standard or as per the exchange protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-51088: Creating S/MIME digital signature failed {0}.

Cause: Failed to create S/MIME digital signature.

Action: Check the signing credentials.
Level: 1

Type: ERROR

Impact: Process

B2B-51089: Unable to verify S/MIME digital signature.

Cause: Verifying S/MIME digital signature failed {0}.

Action: Use correct certificate to verify the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51090: Unable to create S/MIME message recipient.

Cause: Creating S/MIME message recipient list failed {0}.

Action: Check the recipient certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51091: Unable to add a recipient to S/MIME message recipient list {0}.

Cause: Adding recipient to S/MIME message recipient list failed {0}.

Action: Check the recipient certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51092: Encrypting S/MIME message failed {0}.

Cause: Failed to encrypt S/MIME message.

Action: Check the certificate used to encrypt the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51093: Decrypting S/MIME message failed {0}.

Cause: Message encrypted using a wrong certificate.

Action: Check the key-pair used to decrypt the message or verify with the trading partner that the certificate used to encrypt the message is correct.
Level: 1

Type: ERROR

Impact: Process

B2B-51094: Processing signature information for S/MIME message failed.

Cause: Failed to Process signature information for S/MIME message.

Action: Request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51095: Processing envelope information for S/MIME message failed.

Cause: Failed to process envelope information for S/MIME message.

Action: Request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51096: Cannot include more than one signer in the S/MIME digital signature.

Cause: More than one signer in the S/MIME digital signature was not supported.

Action: Ask the trading partner to send the message with the single signer.
Level: 1

Type: ERROR

Impact: Process

B2B-51097: Found empty packaging IDs list during packaging plug-in initialization.

Cause: An empty packaging IDs list is passed for packaging plug-in initialization.

Action: Make sure correct packaging is mentioned.
Level: 1

Type: ERROR

Impact: Process

B2B-51098: Invalid Content-Type {0} in packaging metadata.

Cause: Packaging metadata contains invalid Content-Type.

Action: Make sure correct packaging details are mentioned.
Level: 1

Type: ERROR

Impact: Process

B2B-51099: An incorrect RosettaNet version has been found in the message.

Cause: Not a RosettaNet 1.1 message.

Action: Verify the packaging version.
Level: 1

Type: ERROR

Impact: Process

B2B-51105: Unsupported algorithm

Cause: Algorithm used was not supported by the S/MIME or exchange protocol.

Action: Use correct algorithm as specified by the exchange protocol or S/MIME standard.
Level: 1

Type: ERROR

Impact: Process

B2B-51107: Digest mismatch

Cause: Document might have been corrupted during transport.

Action: Request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51108: Failed to digest the message.

Cause: Failed to create the digest for the message.

Action: Check the payload or digest algorithm.
Level: 1

Type: ERROR

Impact: Process

B2B-51112: An invalid CRL has been found in the incoming message.

Cause: Invalid CRL.

Action: Check with the trading partner that CRL is correct and request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51114: CRL missing issuer

Cause: Issuer not found in CRL.

Action: Check with the trading partner that CRL issuer is correct and request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51120: Invalid Content-Type

Cause: Content-Type of the signed/encrypted message was not correct.

Action: Request a re-send from the partner or resend the message with correct Content-Type.
Level: 1

Type: ERROR

Impact: Process

B2B-51121: Empty recipient list

Cause: No recipient list was exist in the encrypted message.

Action: Check with the trading partner and request a re-send with recipient list.
Level: 1

Type: ERROR

Impact: Process

B2B-51122: Certificate decode error

Cause: Certificate was not correct.

Action: Check if the certificate is in correct format.
Level: 1

Type: ERROR

Impact: Process

B2B-51124: Failed to create certificate chain

Cause: Unable to create certificate chain while generating the message.

Action: Check if the certificate used is a trusted certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51125: No certificate to sign

Cause: Certificate used to sign the message was not available in the keystore.

Action: Check if the certificate is available in the keystore.
Level: 1

Type: ERROR

Impact: Process

B2B-51128: Certificate missing issuer

Cause: The certificate that is being used was missing issuer information.

Action: Use a trusted certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51143: Certificate expired

Cause: The certificate has expired.

Action: 1. Make sure host and trading partner has selected the local time zone, 2. If the time zone is correct request the trading partner to generate a new certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51145: Certificate is not valid yet.

Cause: Certificate was not valid. Because the certificate creation date was later than current system date.

Action: 1. Make sure Host and trading partner has selected the local time zone 2. System current date is later than certificate creation date.
Level: 1

Type: ERROR

Impact: Process

B2B-51147: Missing recipient information

Cause: Missed recipient information.

Action: Ask the trading partner to check the recipient certificate added during encryption and request for a re-send.
Level: 1

Type: ERROR

Impact: Process

B2B-51150: Failed to verify certificate chain.

Cause: Unable to verify the certificate chain while processing the message.

Action: Verify the certificates used and request a re-send.
Level: 1

Type: ERROR

Impact: Process

B2B-51152: CRL verification failed

Cause: CRL verification failed.

Action: CRL received not matching with the certificates in the keystore. Request the trading partner to send the correct CRL.
Level: 1

Type: ERROR

Impact: Process

B2B-51153: Certificate revoked

Cause: Certificate revoked.

Action: Request a re-send with the valid certificate from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51154: Certificate signature verification failed.

Cause: Failed to verify the certificate signature.

Action: Request for the valid certificate from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51165: Digest algorithm missing.

Cause: Message received with incorrect digest algorithm.

Action: Request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51193: Failed to open keystore.

Cause: Keystore file was not in correct format, incorrect location or incorrect password.

Action: Make sure the keystore is generated properly or the location or password is correct.
Level: 1

Type: ERROR

Impact: Process

B2B-51195: Failed to get key pair from keystore

Cause: Unable to retrieve key pair from the keystore.

Action: Verify that the keystore has valid key pair.
Level: 1

Type: ERROR

Impact: Process

B2B-51197: LDAP error

Cause: LDAP error

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

B2B-51198: LDAP connect failed.

Cause: LDAP connect failed.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

B2B-51199: LDAP bind failed.

Cause: LDAP bind failed.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

B2B-51200: LDAP search failed.

Cause: LDAP search failed.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

B2B-51201: LDAP entry missing attribute.

Cause: LDAP entry missing attribute.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

B2B-51202: No certificate in the directory for this user

Cause: Unable to retrieve the certificate for this user from the directory.

Action: Make sure that the certificate is available in the directory.
Level: 1

Type: ERROR

Impact: Process

B2B-51203: Error compressing data.

Cause: An error has occurred while compressing data.

Action: Check the payload.
Level: 1

Type: ERROR

Impact: Process

B2B-51204: Error decompressing data.

Cause: An error has occurred while compressing data.

Action: Check the payload received or request for re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51205: The alias is not present or configured incorrectly in partner profile

Cause: The alias is not present or configured incorrectly in partner profile.

Action: Make sure that the alias is available in the partner profile.
Level: 1

Type: ERROR

Impact: Process

B2B-51206: Validation of signatures or checks on the authenticity or authority of the sender of the message have failed.

Cause: Alias is present but received message is unsigned

Action: Make sure received message is signed
Level: 1

Type: ERROR

Impact: Process

B2B-51207: Database Connection Failed.

Cause: Database Connection failed.

Action: Check the Datasource details.
Level: 1

Type: ERROR

Impact: Process

B2B-51208: SQL Exception occurred during JDBC processing

Cause: SQL Exception occurred during JDBC processing.

Action: Check the Datasource details.
Level: 1

Type: ERROR

Impact: Process

B2B-51300: Interface Sequencing failure - Inbound sequence row not present for correlation

Cause: Inbound sequence row not present for correlation.

Action: Check if the group count is configured incorrectly or if the sequence row was discarded.
Level: 1

Type: ERROR

Impact: Process

B2B-51500: Document exchange success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

B2B-51501: Document exchange initialization failure.

Cause: Failed to initialize the document specific guidelines.

Action: Verify the document specific initialization parameters.
Level: 1

Type: ERROR

Impact: Process

B2B-51503: General create message error.

Cause: Failed to create message components.

Action: Verify values for message creation components.
Level: 1

Type: ERROR

Impact: Process

B2B-51504: General decode error.

Cause: Failed to decode the message.

Action: Verify the incoming message contents.
Level: 1

Type: ERROR

Impact: Process

B2B-51505: General validation error.

Cause: An unexpected error occurred during validation.

Action: Verify the validity of the document against the document definition.
Level: 1

Type: ERROR

Impact: Process

B2B-51506: Message digest validation error.

Cause: Message digest obtained from the incoming message payload, did not match with the original message digest.

Action: Verify the digest algorithm.
Level: 1

Type: ERROR

Impact: Process

B2B-51507: Payload validation error.

Cause: An error occurred during message payload processing in document plug-in.

Action: Verify the message payload validity against the document definition.
Level: 1

Type: ERROR

Impact: Process

B2B-51508: Validation of Group parameters failed. Verify all the Group parameters in the B2B configuration match the Group parameters in the message. The following parameters do not match the configured parameters in system. {0}

Cause: Validation of Group parameters failed. Verify all the Group parameters in the B2B configuration match the Group parameters in the message. The following parameters do not match the configured parameters in system.{0}

Action: Verify the EDI group header parameters of the message validity against the document definition.
Level: 1

Type: ERROR

Impact: Process

B2B-51509: Create message error: component- {0}.

Cause: Failed to create message components.

Action: Verify all components of the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51510: Validation of Batch header parameters failed. Verify all the Batch header parameters in the B2B configuration match the Batch header parameters in the message. Following parameters are not matching with the configured parameters in system.

Cause: Validation of Batch header parameters failed. Verify all the Batch header parameters in the B2B configuration match the Batch header parameters in the message. Following parameters are not matching with the configured parameters in system.

Action: Verify the batch message payload validity against the document definition.
Level: 1

Type: ERROR

Impact: Process

B2B-51511: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Interchange parameters in the message. Following parameters are not matching with the configured parameters in system.{0}

Cause: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Interchange parameters in the message. Following parameters are not matching with the configured parameters in system.{0}

Action: Verify the EDI Interchange header parameters of the message validity against the document definition
Level: 1

Type: ERROR

Impact: Process

B2B-51512: Message payload parameter validation error.

Cause: Document parameters validation failed.

Action: Verify the parameters of the message against the document protocol parameters.
Level: 1

Type: ERROR

Impact: Process

B2B-51513: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid.

Cause: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid.

Action: Verify the EDI Interchange header parameters of the message validity against the document definition
Level: 1

Type: ERROR

Impact: Process

B2B-51514: Validation of Message header parameters failed. Verify all the Message header parameters in the configuration match the Message header parameters in the message. Following parameters are not matching with the configured parameters.

Cause: An error occurred in message header of document during message processing.

Action: Verify all the Message header parameters in the configuration match the Message header parameters in the message. Following parameters are not matching with the configured parameters.
Level: 1

Type: ERROR

Impact: Process

B2B-51515: Validation of parameters failed. Some or all of the following parameters do not match the configured parameters in B2B.

Cause: Document parameters validation failed.

Action: Verify the parameters of the message against the document protocol parameters.
Level: 1

Type: ERROR

Impact: Process

B2B-51516: Validation of File header parameters failed. Verify all the File header parameters in the B2B configuration match the File header parameters in the message. Following parameters are not matching with the configured parameters in system.

Cause: Validation of File header parameters failed. Verify all the File header parameters in the B2B configuration match the File header parameters in the message. Following parameters are not matching with the configured parameters in system.

Action: Verify all the File header parameters in the B2B configuration match the File header parameters in the message. Following parameters are not matching with the configured parameters in B2B.
Level: 1

Type: ERROR

Impact: Process

B2B-51517: Document protocol identification error.{0}

Cause: Failed to identify the document protocol for the message.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51518: Mandatory parameter {0} {1} is missing.

Cause: Mandatory parameter {0} {1} is missing.

Action: Verify mandatory parameter is the same in payload and configuration.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51519: Interchange Receiver Id is not present.

Cause: Interchange Receiver Id is not present.

Action: Verify the Interchange Receiver Id is the same in payload and configuration.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51520: Validation of Interchange parameters failed. Following parameters are not matching with the configured parameters in B2B. {0}

Cause: Validation of Interchange parameters failed. Following parameters are not matching with the configured parameters in B2B. {0}

Action: Verify the document Interchange parameters of the message validity against the document definition
Level: 1

Type: ERROR

Impact: Process

B2B-51521: Document Callout Translation error: {0}.

Cause: Error while using callout to translate document

Action: Check payload and read the parsing error
Level: 1

Type: ERROR

Impact: Process

B2B-51522: Translation is not enabled in the agreement. {0}

Cause: Translation is not enabled in the agreement. {0}

Action: Enable the translation in the associated agreement in the B2B console
Level: 1

Type: ERROR

Impact: Process

B2B-51550: Invalid usage code.

Cause: Specified usage code was neither production nor test.

Action: Verify that the usage code is either production or test.
Level: 1

Type: ERROR

Impact: Process

B2B-51551: Invalid timestamp.

Cause: Timestamp was not in the correct format.

Action: Correct timestamp format is CCYYMMDDThhmmss.sssZ.
Level: 1

Type: ERROR

Impact: Process

B2B-51552: Mismatch in the PIP binding ID.

Cause: PIP binding ID in the initiating message did not match the PIP binding ID in the response message.

Action: Ensure that the PIP binding ID in the initiating message matches the PIP binding ID in the response message.
Level: 1

Type: ERROR

Impact: Process

B2B-51553: Mismatch in PIP code.

Cause: PIP code in the initiating message did not match the PIP code in the response message.

Action: Ensure that PIP Code in the initiating message matches the PIP code in the response message.
Level: 1

Type: ERROR

Impact: Process

B2B-51554: Mismatch PIP in instance ID.

Cause: PIP instance ID in the initiating message did not match the PIP instance ID in the response message.

Action: Ensure that the PIP instance ID in the initiating message matches the PIP instance ID in the responding message.
Level: 1

Type: ERROR

Impact: Process

B2B-51555: Mismatch in PIP version.

Cause: PIP version in the initiating message did not match the PIP version in the response message.

Action: Ensure that PIP version in the initiating message matches the PIP version in the response message.
Level: 1

Type: ERROR

Impact: Process

B2B-51556: Invalid response message.

Cause: Message ID in the initiating message did not match the message ID in the RefTo field of the response message.

Action: Ensure that message ID in the initiating message matches the message ID in the RefTo field of the response message.
Level: 1

Type: ERROR

Impact: Process

B2B-51557: PIP binding ID exceeds 255 characters.

Cause: PIP binding ID cannot exceed 255 characters.

Action: Limit the total characters of PIP binding ID to 255.
Level: 1

Type: ERROR

Impact: Process

B2B-51558: Invalid value for secure transport required attribute.

Cause: Secure transport was neither Yes nor No.

Action: Ensure that the secure transport has values Yes or No.
Level: 1

Type: ERROR

Impact: Process

B2B-51559: Mismatch in manifest content-type.

Cause: Content-type in the manifest did not match the content-type associated with the attachment.

Action: Ensure that the content-type in the manifest and attachment are the same.
Level: 1

Type: ERROR

Impact: Process

B2B-51560: Mismatch in manifest content-ID.

Cause: Content-ID in the manifest did not match the content-ID associated with the attachment.

Action: Ensure that the content-ID in the manifest matches the content-ID associated with the attachment.
Level: 1

Type: ERROR

Impact: Process

B2B-51561: Mismatch in the service of the host and the trading partner.

Cause: FromService field in the initiating message did not match the ToService field in the response message.

Action: Verify the FromService field of the host matches with ToService field of the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51562: Mismatch in the service of the host and the trading partner.

Cause: ToService field in the initiating message did not match the FromService field in the response message.

Action: Verify the ToService field of the host matches with FromService of the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51563: Mismatch in the role of the host and the trading partner.

Cause: FromRole field in the initiating message did not match the ToRole field in the response message.

Action: Verify the FromRole field of the host matches with ToRole field of the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51564: Mismatch in the role of the host and the trading partner.

Cause: ToRole field in the initiating message did not match the FromRole field in the response message.

Action: Verify the ToRole field of the host matches with FromRole field of the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51565: An unexpected error occurred while initializing the XML parser.

Cause: Failed to initialize XML parser.

Action: Ensure that the XML parser initialized properly.
Level: 1

Type: ERROR

Impact: Process

B2B-51566: Parse stream error

Cause: An unexpected error occurred while parsing the input stream.

Action: Verify the message components of incoming message.
Level: 1

Type: ERROR

Impact: Process

B2B-51567: Invalid Content-Type

Cause: Sub-type of the Content-Type in the HTTP header was neither Multipart/related nor Multipart/signed.

Action: Check for the Content-Type in the HTTP header.
Level: 1

Type: ERROR

Impact: Process

B2B-51568: encoding error

Cause: An unexpected error occurred while encoding data.

Action: Verify encoded type is base64.
Level: 1

Type: ERROR

Impact: Process

B2B-51569: decoding error

Cause: An unexpected error occurred while decoding data.

Action: Verify the decode type is base64.
Level: 1

Type: ERROR

Impact: Process

B2B-51570: Attachment error

Cause: An unexpected error occurred while creating an attachment as component data.

Action: Verify the well-form of the XML content for attachment.
Level: 1

Type: ERROR

Impact: Process

B2B-51571: Attachment error

Cause: An unexpected error occurred while forming an attachment as XML data.

Action: Verify that the XML format of the data for the attachment is well-formed XML. Also verify the encoding and type attributes of attachment.
Level: 1

Type: ERROR

Impact: Process

B2B-51572: Error reading input stream.

Cause: An unexpected error occurred while reading the input stream.

Action: Ensure the input value is nonempty.
Level: 1

Type: ERROR

Impact: Process

B2B-51573: Unexpected payload file naming, default format is <FromPartyName>_<MessageID>.<Extension> e.g. Sun_1234235.dat

Cause: Payload file name was not as per expected naming convention.

Action: Expect default format is <FromPartyName>_<MessageID>.<Extension> e.g. Sun_1234235.dat.
Level: 1

Type: ERROR

Impact: Process

B2B-51574: Error loading XEngine libraries. XEngine is most likely not installed.

Cause: XEngine was not installed.

Action: Make sure XEngine is installed.
Level: 1

Type: ERROR

Impact: Process

B2B-51575: Incorrect document exchange version.

Cause: Document exchange version mismatch.

Action: Verify the document exchange header value.
Level: 1

Type: ERROR

Impact: Process

B2B-51576: Incorrect document exchange.

Cause: Document exchange mismatch.

Action: Verify the document exchange name.
Level: 1

Type: ERROR

Impact: Process

B2B-51577: Document exchange validation error

Cause: Document exchange validation failed.

Action: Verify the document exchange header values
Level: 1

Type: ERROR

Impact: Process

B2B-51578: Exception Reported: {0}

Cause: B2B is unable to continue processing due to Control Number sequence generation failure.

Action: Please refer to documentation for EM property : b2b.useSequenceControlNum for further information.
Level: 1

Type: ERROR

Impact: Process

B2B-51703: Failed to unpack the message.

Cause: An unexpected error occurred during the unpackaging of the RosettaNet business message.

Action: Verify the message headers.
Level: 1

Type: ERROR

Impact: Process

B2B-51705: Unable to read the preamble.

Cause: Failed to read preamble.

Action: Ensure the correctness of preamble content.
Level: 1

Type: ERROR

Impact: Process

B2B-51707: Unable to read the delivery header.

Cause: Failed to read delivery header.

Action: Ensure the correctness of the delivery header content.
Level: 1

Type: ERROR

Impact: Process

B2B-51709: Unable to read the service header.

Cause: Failed to read the service header.

Action: Ensure the correctness of the service header.
Level: 1

Type: ERROR

Impact: Process

B2B-51715: Failed to unpack the message - reading the service content.

Cause: Failed to read the service content.

Action: Ensure the correctness of the service content.
Level: 1

Type: ERROR

Impact: Process

B2B-51915: No type is specified in party ID.

Cause: No type was specified in party ID.

Action: Specify a party ID type.
Level: 1

Type: ERROR

Impact: Process

B2B-51916: Reference ID in the manifest does not match payload ID.

Cause: Reference ID in the manifest did not match payload ID.

Action: Make sure that reference ID in the manifest matches the payload ID.
Level: 1

Type: ERROR

Impact: Process

B2B-51917: Content-Type set for ebMS message is incorrect.

Cause: Content-Type set for ebMS message was incorrect.

Action: Set a valid Content-Type for the ebMS message.
Level: 1

Type: ERROR

Impact: Process

B2B-51918: This version of ebMS is not supported. Only version 2.0 is supported.

Cause: This version of ebMS was not supported. Only version 2.0 is supported.

Action: Make sure to exchange messages for the supported version.
Level: 1

Type: ERROR

Impact: Process

B2B-51919: Hub mode not supported.

Cause: As Hub mode was not supported, the actor value is incorrect.

Action: Specify the actor as urn:oasis:names:tc:ebXML-msg:actor:toPartyMSH
Level: 1

Type: ERROR

Impact: Process

B2B-51921: SOAP message has defective packaging.

Cause: Defect identified in packaging of the SOAP message.

Action: Make sure that the message is a valid SOAP message.
Level: 1

Type: ERROR

Impact: Process

B2B-51922: If the service type is not specified then the service must be a URI.

Cause: If the service type was not specified then the service must be a URI.

Action: Specify a service URI if the service type is not specified.
Level: 1

Type: ERROR

Impact: Process

B2B-51923: Value {0} for the element {1} is not recognized.

Cause: Failed to recognise value for the element.

Action: Specify a correct value for the element.
Level: 1

Type: ERROR

Impact: Process

B2B-51924: Message failed the security check.

Cause: Message failed the security check.

Action: Verify that the message has been encrypted and signed with the correct credentials.
Level: 1

Type: ERROR

Impact: Process

B2B-51925: Feature {0} is not supported.

Cause: Selected feature is not supported.

Action: Make sure the feature is currently supported.
Level: 1

Type: ERROR

Impact: Process

B2B-51926: SyncReply element must exist in the message.

Cause: SyncReply element must be present in the message.

Action: Add a SyncReply element in the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51927: Time to live has expired for the message.

Cause: Time to live has expired for the message.

Action: Make sure to send a message with a valid time to live value.
Level: 1

Type: ERROR

Impact: Process

B2B-51928: Message header validation failed. The received {0} does not match with the configured {1}.

Cause: Message header did not have the element.

Action: Make sure to add element to the message header.
Level: 1

Type: ERROR

Impact: Process

B2B-51929: No payload is found for the reference ID {0}.

Cause: No payload attached for the reference ID.

Action: Make sure to have a payload for the reference ID, or remove this reference ID from the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51930: Message with ID {0} is a duplicate message.

Cause: Duplicate message identified with same ID.

Action: Make sure to send a message with a unique message ID, a message which is not duplicated.
Level: 1

Type: ERROR

Impact: Process

B2B-51931: Error found in decrypting or verifying the message.

Cause: Error in decryption or on message verification.

Action: Make sure that the message is being decrypted and verified with the correct credentials.
Level: 1

Type: ERROR

Impact: Process

B2B-51932: Multiple parts with same Content-ID or Content-Location header.

Cause: Multiple parts with same Content-ID or Content-Location header.

Action: Use different Content-ID or Content-Location header values for different MIME parts of the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51933: Referenced Content-ID or Content-Location header not found.

Cause: Referenced Content-ID or Content-Location header not found.

Action: Make sure that the referenced Content-ID or Content-Location header values are valid.
Level: 1

Type: ERROR

Impact: Process

B2B-51934: Unhandled attachment object {0} found.

Cause: Unhandled attachment object found.

Action: Make use of correct attachment type for attaching objects.
Level: 1

Type: ERROR

Impact: Process

B2B-51935: Error in resolving the content ID reference.

Cause: Failed to resolve the content ID reference.

Action: Make sure that the content ID reference is valid.
Level: 1

Type: ERROR

Impact: Process

B2B-51936: Signed acknowledgement requested, but not configured in delivery channel.

Cause: Signed acknowledgement requested, but not configured in delivery channel.

Action: Make sure that the sign acknowledgement is configured in delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-52250: Error decoding incoming message at MLLP exchange.

Cause: Message received consists of more than one part or component.

Action: Check the payload to make sure it has only one part/component.
Level: 1

Type: ERROR

Impact: Process

B2B-52251: Error identifying remote trading partner at MLLP exchange with MLLP ID {0}.

Cause: MLLP ID received from in the message header did not exist.

Action: Make sure that the MLLP ID of the remote trading partner is configured as in the trading partner identification section or the anonymous trading partner is configured.
Level: 1

Type: ERROR

Impact: Process

B2B-52252: Only one trading partner in the system can have hosted=true.

Cause: More than one trading partner has hosted=true.

Action: Make sure only one trading partner in the system has hosted=true.
Level: 1

Type: ERROR

Impact: Process

B2B-52253: Trading partner {0} must have trading partner name as one of the identification.

Cause: Trading partner must have trading partner name as one of the identification.

Action: Make sure trading partner has an identification with value as name of trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52254: Delivery channel {0} must have exchange protocol, if listening=false.

Cause: Delivery channel did not have exchange protocol.

Action: Make sure delivery channel has exchange protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-52255: Certificate alias not specified in the secure delivery channel {0}.

Cause: Security was enabled in delivery channel, but no certificate alias specified.

Action: Make sure certificate alias specified in the delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-52256: In delivery channel {0}, Transport protocol {1} is not supported by exchange protocol {2}.

Cause: Specified transport protocol was not supported by exchange protocol.

Action: Choose transport protocol which is supported by exchange protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-52257: In delivery channel {0}, algorithm {1} is not supported for exchange protocol {2}.

Cause: Specified algorithm was not supported by exchange protocol.

Action: Choose algorithm which is supported by exchange protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-52258: In delivery channel {0}, exchange protocol parameter {1} is not supported for exchange protocol {2}.

Cause: Selected exchangeProtocolParameter was not part of the specified exchange protocol.

Action: Select specified exchangeProtocol and re-save again in UI.
Level: 1

Type: ERROR

Impact: Process

B2B-52259: In delivery channel {1}, exchange protocol {0} has to have acknowledge mode as ASYNC or NONE.

Cause: RNIF exchange protocol did not support SYNC acknowledge mode.

Action: Verify RNIF exchange protocol has acknowledge mode as ASYNC or NONE.
Level: 1

Type: ERROR

Impact: Process

B2B-52260: effectiveToDate {0} in agreement {1} must be a date in the future.

Cause: Date specified in effectiveToDate was not a future date.

Action: Ensure that the effectiveToDate in the agreement is a date in the future.
Level: 1

Type: ERROR

Impact: Process

B2B-52261: The effectiveFromDate {0} should be less than effectiveToDate {1} in agreement {2}.

Cause: The effectiveFromDate should be less than effectiveToDate.

Action: Make sure the effectiveFromDate is less than effectiveToDate.
Level: 1

Type: ERROR

Impact: Process

B2B-52262: Agreement {0} does not have a host and trading partner.

Cause: Agreement did not have a host and trading partner.

Action: Make sure agreement has a host and trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52263: One of the participants must be a host in an agreement {0}.

Cause: None of the participants was host in agreement.

Action: Make sure a participant in agreement is host.
Level: 1

Type: ERROR

Impact: Process

B2B-52264: Document type name {0} and document protocol version {1} used in agreement {2} are not in sync with the corresponding definition in trading partner {3}.

Cause: Document type name and document protocol version used in agreement were not in sync with the corresponding definition in trading partner.

Action: Make sure agreement has document type name and document type version as given in trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52265: DUNS identification value {0} must be 9 digit.

Cause: DUNS identification was not have value in 9 digit.

Action: Verify DUNS identification has value in 9 digit.
Level: 1

Type: ERROR

Impact: Process

B2B-52266: Identification type {0} and value {1} must be unique in the trading partner.

Cause: Identification type and value occurred more than once in the trading partner.

Action: Make sure type and value of identification unique in the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52267: Only one exchange protocol can have default=true.

Cause: More than one exchange protocol has default=true.

Action: Make sure only one exchange protocol has default=true.
Level: 1

Type: ERROR

Impact: Process

B2B-52268: Only one document protocol can have default=true.

Cause: More than one document protocol has default=true.

Action: Make sure only one document protocol has default=true.
Level: 1

Type: ERROR

Impact: Process

B2B-52269: Participant {0} cannot have more than one identification of the same type {1}.

Cause: Participant has more than one identification of the same type.

Action: Make sure participant is not referring to more than one identification of same type.
Level: 1

Type: ERROR

Impact: Process

B2B-52270: Participant {0} identification reference {1} is not part of same trading partner identification.

Cause: Participant refer to some other trading partner identification.

Action: Make sure identification referred in participant is part of same trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52271: Participant {0} delivery channel reference {1} is not part of same trading partner.

Cause: Participant delivery channel reference was not part of either same trading partner or host.

Action: Make sure delivery channel referred in participant is part of trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52272: Participant {0} document definition {1} is not part of same trading partner.

Cause: Participant document definition was not part of same trading partner.

Action: Make sure trading partner has specified document definition.
Level: 1

Type: ERROR

Impact: Process

B2B-52273: Participant {0} identification type {1} and value {2} are not synchronous with trading partner identification.

Cause: Participant identification type and value were not sync with trading partner identification.

Action: Make sure the value and type given in identification reference in participant is synchronous with trading partner identification.
Level: 1

Type: ERROR

Impact: Process

B2B-52274: Participant {0} can have only one exchange identifier.

Cause: Participant has more than one exchange identification.

Action: Make sure only one exchange identification found in participant.
Level: 1

Type: ERROR

Impact: Process

B2B-52275: Type of the parameter {0} must match with the default value {1}.

Cause: Parameter type and default value type mismatched.

Action: Check the type and value of parameter are same type.
Level: 1

Type: ERROR

Impact: Process

B2B-52276: Type of the parameter {0} must match with the value.

Cause: Parameter type and given value mismatched.

Action: Check the type and value of parameter are same type.
Level: 1

Type: ERROR

Impact: Process

B2B-52277: Only Custom document protocol can set custom attribute equal to true.

Cause: Other than custom document protocol has custom attribute set to true.

Action: Make sure only custom document protocol has this attribute set to true.
Level: 1

Type: ERROR

Impact: Process

B2B-52278: Document protocol {0} must have ID {1} starts with doc_

Cause: Document protocol has ID which did not start with doc_

Action: Make sure document protocol has ID starts with doc_
Level: 1

Type: ERROR

Impact: Process

B2B-52279: Document protocol {0} reference must be doc_id.xml

Cause: Document protocol reference was not in the form of doc_id.xml

Action: Make sure document protocol reference is in the form of doc_id.xml
Level: 1

Type: ERROR

Impact: Process

B2B-52280: Trading partner {0} must have at least one exchange identification.

Cause: None of the exchange identification found in trading partner.

Action: Add at least one exchange identification in trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52281: Trading partner {0} must have ID {1} starts with tp_

Cause: Trading partner has ID which did not start with tp_

Action: Make sure trading partner has ID which starts with tp_
Level: 1

Type: ERROR

Impact: Process

B2B-52282: Trading partner {0} reference must be tp_id.xml

Cause: Trading partner reference was not in the form of tp_id.xml

Action: Make sure trading partner has reference in the form of tp_id.xml
Level: 1

Type: ERROR

Impact: Process

B2B-52283: In delivery channel {0}, certificate alias {1} not found in the keystore.

Cause: Given certificate alias did not exist in the keystore.

Action: Verify certificate alias is present in the keystore.
Level: 1

Type: ERROR

Impact: Process

B2B-52284: Delivery channel {0} which has transport protocol {1} cannot be a listening channel.

Cause: Selected transport protocol was not capable of listening

Action: Select listening transport to create listening delivery channel
Level: 1

Type: ERROR

Impact: Process

B2B-52285: Internal delivery channel {0} must use generic exchange.

Cause: Internal delivery channel has other than generic exchange protocol.

Action: Make sure internal delivery channel uses generic exchange.
Level: 1

Type: ERROR

Impact: Process

B2B-52286: HTTP transport protocol must have a URL.

Cause: HTTP transport protocol did not have a URL.

Action: Make sure HTTP transport protocol has a URL.
Level: 1

Type: ERROR

Impact: Process

B2B-52287: Agreement {0} must have ID {1} starts with tpa_

Cause: Agreement has ID which did not start with tpa_

Action: Make sure agreement has ID which starts with tpa_
Level: 1

Type: ERROR

Impact: Process

B2B-52288: Agreement {0} reference must be tpa_id.xml

Cause: Agreement reference was not in the form of tpa_id.xml

Action: Make sure agreement has reference which is in the form of tpa_id.xml
Level: 1

Type: ERROR

Impact: Process

B2B-52289: Agreement {0} has document definition with mismatching initiator flag.

Cause: Agreement has document definition with mismatching initiator flag in trading partner.

Action: Make sure document definition is supported to send or receive by trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52290: Agreement {0} must have exactly one supported document type.

Cause: Agreement has not exactly one supported document type.

Action: Make sure agreement has only one supported document type.
Level: 1

Type: ERROR

Impact: Process

B2B-52291: Duplicate agreement {0} found with same combination of trading partners {1}, {2}, and document type {3} and document protocol version {4}.

Cause: More than one agreement has same combination of trading partners, document type and version.

Action: Make sure only one agreement has same combination of trading partners, document type and version.
Level: 1

Type: ERROR

Impact: Process

B2B-52292: In agreement {0}, trading partner {1} must have a delivery channel.

Cause: The trading partner did not have delivery channel to send out bound message.

Action: Make sure in a agreement, the trading partner has a delivery channel to send out bound message.
Level: 1

Type: ERROR

Impact: Process

B2B-52293: In agreement {0}, the host {1} can refer to only the internal delivery channel.

Cause: Host refers to other than internal delivery channel.

Action: Make sure host is not referring to other than internal delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-52294: In agreement {0}, participant {1} cannot have more than one delivery channel.

Cause: Participant has more than one delivery channel.

Action: Make sure only one delivery channel exist for participant.
Level: 1

Type: ERROR

Impact: Process

B2B-52295: At least one name identification type present in system.

Cause: Name identification type did not present in system.

Action: Check at least one name identification type present in system.
Level: 1

Type: ERROR

Impact: Process

B2B-52296: Exchange identification {0} must have a value.

Cause: Exchange identification did not have a value.

Action: Make sure all exchange identification has a value.
Level: 1

Type: ERROR

Impact: Process

B2B-52297: Packaging protocol reference {0} must point to packaging protocol element.

Cause: Packaging protocol reference refer to other than packaging protocol element.

Action: Verify packaging protocol reference refers to packaging protocol element.
Level: 1

Type: ERROR

Impact: Process

B2B-52298: Transport URL {0} already used in system.

Cause: More than once same endpoint used in system.

Action: Make sure same endpoint not attached with different delivery channel in system.
Level: 1

Type: ERROR

Impact: Process

B2B-52299: Participant {0} must have at least one exchange identification.

Cause: None of the exchange identification referred in participant.

Action: Make sure participant has at least one exchange identification.
Level: 1

Type: ERROR

Impact: Process

B2B-52300: Duplicate ID {0} found in node {1} and node {2}.

Cause: Duplicate unique ID found in two different nodes.

Action: Target system has element with the same , change ID of importing node.
Level: 1

Type: ERROR

Impact: Process

B2B-52301: MDSReference {0} is not referring to the trading partner.

Cause: MDSReference did not refer to the trading partner.

Action: Make sure given reference is pointing to the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52302: MDSReference {0} is not referring to an agreement.

Cause: MDSReference did not refer to an agreement.

Action: Make sure given reference is pointing to an agreement.
Level: 1

Type: ERROR

Impact: Process

B2B-52303: Compressed file expected to import.

Cause: Given file was not compressed using ZIP format.

Action: Verify given file is in compressed in ZIP format.
Level: 1

Type: ERROR

Impact: Process

B2B-52304: Agreement {0} cannot have listening channels.

Cause: Listening channels referred in agreement.

Action: Verify agreement is not referring to any listening channels.
Level: 1

Type: ERROR

Impact: Process

B2B-52305: In agreement {0}, trading partner {1} cannot have internal delivery channel.

Cause: Trading partner has internal delivery channel(s).

Action: Make sure none of the trading partners has internal delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-52306: Internal delivery channel {0} must not use HTTP transport.

Cause: Internal delivery channel has HTTP as transport.

Action: Make sure internal delivery channel is not using HTTP transport.
Level: 1

Type: ERROR

Impact: Process

B2B-52307: Listening delivery channel {0} must have a polling interval value.

Cause: Listening channel did not have value for polling interval.

Action: Make sure listening channel has polling interval value.
Level: 1

Type: ERROR

Impact: Process

B2B-52308: Listening delivery channel {0} with transport {1} does not have user name and password.

Cause: Listening delivery channel did not have user name and password in transport.

Action: Make sure listening delivery channel has user name and password in transport.
Level: 1

Type: ERROR

Impact: Process

B2B-52309: Validation error: see the diagnostic log for more details.

Cause: Unknown exception found in validation engine.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52310: The XML {0} is not well-formed.

Cause: Given XML content was not well-formed.

Action: Check XML content is well-formed and valid based on XSD/DTD constraints.
Level: 1

Type: ERROR

Impact: Process

B2B-52311: New document protocol {0} found in source reference {1}.

Cause: New document protocol name found in import source.

Action: Check name of the document protocol is correct.
Level: 1

Type: ERROR

Impact: Process

B2B-52312: Document protocol {0} must have ID {1} starts with doc_

Cause: Document protocol has ID which did not start with doc_

Action: Make sure document protocol has ID which starts with doc_
Level: 1

Type: ERROR

Impact: Process

B2B-52313: Document protocol {0} reference must be doc_id.xml

Cause: Document protocol reference was not in the form of doc_id.xml

Action: Make sure document protocol has reference in the form of doc_id.xml
Level: 1

Type: ERROR

Impact: Process

B2B-52314: Repository host name {0} and source Host name {1} are different.

Cause: Different host name found in repository and source.

Action: Make host name as unique in source and target system, while doing import.
Level: 1

Type: ERROR

Impact: Process

B2B-52315: Duplicate identification type {1} and value {2} found in source trading partner {0}.

Cause: More than one identification type found in source trading partner(s) for a same value and type.

Action: Make sure combination of identification type and value unique in the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52316: Pre-import transfer operation failed.

Cause: Pre-import validation(s) failed while importing.

Action: Check validation error messages found below this message and correct source files accordingly.
Level: 1

Type: ERROR

Impact: Process

B2B-52317: Duplicate identification type {1} and value {2} found in source agreement {0}.

Cause: More than one identification type found in source agreement(s) for a same value and type.

Action: Make sure combination of identification type and value unique in agreement.
Level: 1

Type: ERROR

Impact: Process

B2B-52318: MDSReference {0} does not exist in Repository.

Cause: Specified reference was not available in repository.

Action: Make sure specified reference is available in repository.
Level: 1

Type: WARNING

Impact: Process

B2B-52319: Transfer error: see log for more details.

Cause: Unknown exception identified in transfer.

Action: Check the diagnostic log. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52320: In agreement {0}, functional acknowledge can be enabled only when translate=true.

Cause: Agreement has functional acknowledge with translate flag set to inactive.

Action: Functional acknowledge can be active only when translate is active.
Level: 1

Type: ERROR

Impact: Process

B2B-52321: No metadata found to import.

Cause: No metadata identified in recommended package.

Action: Check given import file has metadata in correct package.
Level: 1

Type: ERROR

Impact: Process

B2B-52322: Mandatory field {0} is missing in {1}.

Cause: Metadata might be imported without all mandatory fields.

Action: Import metadata with all mandatory fields or save again the business object which has error, using UI.
Level: 1

Type: ERROR

Impact: Process

B2B-52323: Out-bound agreement {0} has to have only one exchange identifier type - {1}, in both participants

Cause: Out-bound agreement has more than one exchange identifier, or has different type of exchange identifier which is not suitable to exchange protocol.

Action: Make sure given exchange identifier is supported by chosen exchange protocol in delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-52324: Listening Delivery channel {0} has duplicate endpoint {1}

Cause: Already a delivery channel has same endpoint, hence new delivery channel cannot be activated with same endpoint.

Action: Make sure all listening channel endpoints are unique.
Level: 1

Type: ERROR

Impact: Backup and Recovery

B2B-52325: Error in the SOA Composite {0}

Cause: See the base error message in the SOA Composite.

Action: Correct the error in the Fabric Composite.
Level: 1

Type: ERROR

Impact: Process

B2B-52326: Transport protocol with HTTPs URL has to have valid keystore location and password in host

Cause: Valid keystore location and password was not specified in host.

Action: Check with administrator, whether valid keystore location specified in host.
Level: 1

Type: ERROR

Impact: Process

B2B-52327: Channel {0} with transport {1} should have Queue name along with either datasource or the combination of SID, port number, user name, host name and password.

Cause: AQ channel does not have required parameter values to connect to AQ queue.

Action: Provide AQ Queue name along with either datasource or the combination of SID, port number, user name, host name and password.
Level: 1

Type: ERROR

Impact: Process

B2B-52328: Channel {0} with transport {1} should have either password or the combination of private key file and pass phrase.

Cause: SFTP channel does not have required parameter values to connect to SFTP server.

Action: Provide either password or the combination of private key file and pass phrase.
Level: 1

Type: ERROR

Impact: Process

B2B-52329: Web Service outbound flow invocation error.

Cause: An abnormal condition occurred during outbound flow invocation.

Action: Review the SOAP Fault for the exact error and correct the same. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52330: Error invoking translation Web Service.

Cause: An abnormal condition occurred during translation Web Service invocation.

Action: Review the SOAP Fault for the exact error and correct the same. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52331: Translated content is not available

Cause: B2B metadata or XEngine configuration was invalid.

Action: Review the SOAP Fault for the exact error and correct the same. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52332: Message is discarded and moved to error state with message id {0}

Cause: Message is discarded and moved to a error state based on a user input.

Action: Resubmit the message
Level: 3

Type: ERROR

Impact: Process

B2B-52333: received data from trading partner is too long

Cause: received data from trading partner is too long.

Action: resend hllp message where payload length should be less than or equal to 99994 bytes.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52334: checksum validation failed

Cause: checksum validation failed for received data.

Action: resend hllp message with correct checksum value.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52335: payload length is incorrect in received hllp packed message.

Cause: payload length is incorrect in received hllp packed message.

Action: resend hllp message with correct payload length.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52336: validation of received hllp message failed

Cause: validation of received hllp message failed

Action: resend hllp message
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52337: payload length is too large(>99994 bytes) at client side

Cause: payload length is too large(>99994 bytes) at client side

Action: resend hllp message with payload length less than or equal to 99994 bytes.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52338: Negative Ack Received from trading partner.

Cause: received negative ack from trading partner

Action: resend hllp message
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52339: Large Payload directory is inaccessible

Cause: Specified directory for large payload is inaccessible

Action: Ensure specified directory for large payload exists and it is write enabled
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52340: Un-delivered Sequenced Message has been resubmitted. Moved to ERROR state

Cause: Un-delivered Sequenced Message has been resubmitted. Moved to error state

Action: Please monitor the diagnostic logs for any resultant issues
Level: 3

Type: ERROR

Impact: Process

B2B-52341: Interface Sequence Message discarded. Message id {0}. Dependent Outbound Rows discarded {1}

Cause: Interface Sequence Message discarded.

Action: Please monitor the diagnostic logs for any resultant issues
Level: 3

Type: ERROR

Impact: Process

B2B-52342: WebService API call content is not available

Cause: Abnormal condition occurs when calling webservice api

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-53001: Handler is null while registering a Webservice End point

Cause: The handler is null when registering an endpoint.

Action: Provide a valid handler implementation while registering an endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53002: Unable to find a registered handler for this end point.

Cause: Unable to process the message due to handler identification failure.

Action: Re-register a valid handler for the end point. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53003: Unable to register an endpoint.

Cause: Registration of the webservice end point failed.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53004: Unable to remove a registered end point

Cause: Removal of the webservice end point failed.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53005: Unable to package the payload to a SOAP message

Cause: Packing the payload into a message caused an exception.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53006: Unable to retrieve the payload from the SOAP message

Cause: Unpacking the soap message caused an exception.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53007: No payload component found in the message

Cause: No payload component found in the message

Action: Provide a payload component when enqueuing the message. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53008: Unable to create the SOAP Protocol components

Cause: Unable to create the SOAP Protocol components

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53009: Unable to decode the soap message

Cause: Unable to decode the soap message

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53010: An exception occurred while processing the received message.

Cause: Unable to process the SOAP message received in the transport layer.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53011: Duplicate message with same message id found in a batch. Changing original message id {0} to new message id {1} and rejecting the message.

Cause: Duplicate message with same message id found in a batch.

Action: Make sure that duplicate messages with same message id are not passed in the same batch.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53012: Invalid argument found. Name or identificationType is null.

Cause: Invalid argument found. Name or identificationType is null

Action: Make sure that name of trading partner and identificationType is passed correctly.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53013: Unable to evaluate Payload XPath Expression

Cause: Provided XPath Expression can not be evaluated.

Action: Make sure that configured XPath Expression to extract Payload is correct.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53014: No payload or XPath not able to retrieve the payload

Cause: No payload or wrong XPath.

Action: Check the Payload and XPath
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53015: Unable to find specified security provider

Cause: Security Provider was not found in the environment.

Action: Verify provider.
Level: 1

Type: ERROR

Impact: Process

B2B-53016: Specified algorithm is not available from the specified provider

Cause: Algorithm was not available from the provider.

Action: Verify algorithm and provider .
Level: 1

Type: ERROR

Impact: Process

B2B-53017: Private key can not be recovered

Cause: Private key could not be recovered.

Action: Check the keystore and private key password.
Level: 1

Type: ERROR

Impact: Process

B2B-53018: KeysStore usage failure

Cause: Problem found in Keystore resource usage.

Action: Check the keystore.
Level: 1

Type: ERROR

Impact: Process

B2B-53019: Transport layer security context initialization failure

Cause: SSLContext was not getting initialized.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists
Level: 1

Type: ERROR

Impact: Process

B2B-53100: Unable to create sequencing entry for message

Cause: An error occurred while creating a sequencing entry 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: ERROR

Impact: Process

B2B-53101: Unable to update sequencing state for message

Cause: An error occurred while updating the sequencing state 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: ERROR

Impact: Process

B2B-53102: Failure occurred while persisting messages asynchronously in {0} repository

Cause: An error occurred while persisting messages to the {0} repository asynchronously.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: ERROR

Impact: Process

B2B-53103: Unable to update Message state in the repository for message id {0}.

Cause: Unable to update Message state in the repository for message id {0}.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: ERROR

Impact: Process

B2B-53104: Unable to enqueue event to Event Manager.

Cause: Unable to enqueue event to Event Manager

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: ERROR

Impact: Process

6 BAM-00101 to BAM-04999

BAM-00101: An attempt was made to use a BAM coherence context that has not been started.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00102: An attempt was made to start a BAM coherence context that has already been started.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00103: An attempt was made to use a BAM JMS context that has not been started.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00104: An attempt was made to start a BAM JMS context that has already been started.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00105: An attempt was made to use a BAM persistence context that has not been started.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00106: An attempt was made to start a BAM persistence context that has already been started.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00107: Lookup for Data Source "{0}" failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00108: Cannot remove column "{0}.{1}" from derived Data Object "{2}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00109: Duplicate column specified for table {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00110: Column "{0}" does not exist in Data Object "{1}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00111: Connection associated with current transaction is null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00112: Data Object "{0}" already exists.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00113: The Data Object "{0}" was not found.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00114: Failed to drop dynamic type for Data Object "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00115: Failed to drop flex table for Data Object "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00116: Failed to drop view for Data Object "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00117: Duplicate column specified. Column "{1}" already exists in Data Object "{2}" as "{0}.{1}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00118: A duplicate index was encountered.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00119: Failed to establish the coherence cache for cache ID "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00120: Value specified for {0} is invalid.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00121: Failed to create unmarshaller for DataObject operations XML payloads.

Cause: An exception has occurred attempting to create an unmarshaller for DataObject operations XML payloads.

Action: Report this error to Oracle support.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00122: Invalid use of a CLOB was encountered.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00123: Unimplemented method was invoked: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00124: Unable to obtain database metadata for configured datasource.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00125: Default BAM storage engine has not been instantiated.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00126: Unable to construct dynamic class for Data Object "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00127: Unable to construct dynamic type for Data Object "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00128: Unable to obtain EclipseLink dynamic class loader.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00129: Unable to obtain EclipseLink dynamic helper.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00130: Unable to construct Flex Table for Data Object "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00131: Unable to construct View for Data Object "{0}".

Cause: The attempt to create the database View for the specified Data Object failed.

Action: Check log for further details as to the cause of the failure.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00132: A null value was specified for non-null column "{0}.{1}" in Data Object "{2}".

Cause: A null value was specified for a column which has been defined as not allowing null values.

Action: Either do not specify a null value for the column or redefine the column to allow null values.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00133: Unable to add column "{1}" of type "{2}" to Data Object "{0}". Maximum number of "{2}" columns ({3,number,#0}) exceeded.

Cause: Base DataObjects are created with a user configured maximum number of columns for each of the supported data types. This maximumn has been exceeded.

Action: Increase the maximum number of columns for the indicated data type. This configuration is found on the "General" tab of the DataObject editor.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00134: Data Object "{0}" already has a parent specified.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00135: Parent Data Object specified, "{0}", does not exist.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00136: The version of the targeted BAM schema is later than the schema version expected by the running BAM server. A newer product version is required.

Cause: The version of the targeted BAM schema is later than the schema version expected by the running BAM server.

Action: A newer product version is required.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00137: The version of the targeted BAM schema is earlier than the schema version expected by the running BAM server. A schema upgrade is required.

Cause: The version of the targeted BAM schema is earlier than the schema version expected by the running BAM server.

Action: A schema upgrade is required.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00138: Failed to start BAM Server due to an unresolved or incompatible schema version. Encountered BAM schema version "{0}" when schema version "{1}" is required.

Cause: Failed to start BAM Server due to an unresolved or incompatible schema version.

Action: Check log for further details as to the cause of the failure. Either a newer version of the product is required or a schema upgrade is required.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00139: The BAM storage engine has encountered an exception{0,choice,0#.|1# for table "{1}".} See exception cause for further details.

Cause: The BAM storage engine has encountered an exception performing an operation for the specified table.

Action: Check log for further details as to the cause of the failure.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00140: BAM storage engine failed to start.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00141: Unable to instantiate BAM storage engine for configured datasource.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00142: Specified transaction ID does not exist: {1,number,#0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00143: A Unique Constraint violation was encountered.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00144: BAM schema in use does not include version information. Schema version is unresolved. A schema upgrade is required.

Cause: BAM schema in use does not include version information.

Action: A schema upgrade is required.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00145: Column type specified, "{0}", is not supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00146: Configured database is unsupported: "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00147: Data type specified, "{0}", is not supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00148: Data type specified, "{0}({1})", is not supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00149: Mismatched or malformed version encountered for BAM schema. Unable to check BAM schema version compatibility.

Cause: Mismatched or malformed version encountered for BAM schema.

Action: Check log for further details as to what is wrong with version information encountered.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00150: Failed to dispatch Data Object change notifications.

Cause: An attempt to dispatch Data Object change notifications failed.

Action: Check log for further details as to the cause of the failure.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00151: The specified Data Object name, "{0}", is invalid because it contains embedded blanks.

Cause: A Data Object name was specified that contains embedded blanks.

Action: Embedded blanks are not allowed in Data Object names. Remove the blanks or replace them with another character such as underscores.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00152: The specified Data Object column name, "{0}", is invalid because it contains embedded blanks.

Cause: A Data Object column name was specified that contains embedded blanks.

Action: Embedded blanks are not allowed in Data Object column names. Remove the blanks or replace them with another character such as underscores.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00153: The Data Object name specified is invalid because it cannot be null or an empty string.

Cause: A Data Object name was specified that was null or an empty string.

Action: The Data Object name cannot be null or an empty string. A valid Data Object name must be specified.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00154: A column name specified in Data Object, "{0}", is invalid because it is null or an empty string.

Cause: A Data Object column name was specified that was null or an empty string.

Action: The Data Object column name cannot be null or an empty string. A valid Data Object column name must be specified.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00155: The Data Object with ID "{0}" was not found.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00156: An attempt was made to modify non-existent Data Object "{0}". A Data Object must be created before it can be modified.

Cause: A Data Object must be created (exist) before it can be modified.

Action: If a Data Object has not yet been created (does not exist) then create it before attempting to modified it.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00157: Execution failed for statement: "{0}".

Cause: The specified SQL statement failed to execute successfully.

Action: Check log for further details as to the cause of the failure.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00158: Unable to modify View for Data Object "{0}".

Cause: An attempt to modify the database View associated with the specified Data Object failed.

Action: Check log for further details as to the cause of the failure.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00159: Date string specified, "{0}", does not conform to default pattern "{1}".

Cause: An invalid Date string was specified that does not conform to the specified Date pattern.

Action: Correct Date string to conform to the specified Date pattern.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00160: The mapped name cannot be null or an empty string.

Cause: A name-mapping name was specified that was null or an empty string.

Action: The name for a name-mapping cannot be null or an empty string. A valid name must be specified.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00161: The specified Data Object "{0}" is already mapped to database view "{1}".

Cause: An attempt was made to map a Logical or External Data Object to a database view when that Data Object is already mapped to a database view.

Action: A Logical or External Data Object can only be mapped to a single database view. In order to change this mapping the existing mapping must be deleted and then the new mapping created.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00162: The specified Data Object "{0}" is not currently mapped to a database view.

Cause: An attempt was made to delete the database view mapping for a Logical or External Data Object when no such mapping exists.

Action: Report this error to Oracle support.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00163: The BAM Server is unavailable. The server state is "{0}".

Cause: The BAM Server is not in an available state.

Action: Check log for further details as to the cause of the failure.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00164: The BAM {0} Service is invalid. No such service exists.

Cause: An attempt was made to access an invalid BAM Server service.

Action: Report this error to Oracle support.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00165: The BAM {0} Service is unavailable. The service state is "{1}".

Cause: The specified BAM Server service is not in an available state.

Action: Check log for further details as to the cause of the failure.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00166: A null value was specified for column "{0}.{1}" in Data Object "{2}" with update action "{3}". A null value can only be specified for update action "replace".

Cause: A null value was specified for a column with update action other than "replace". A null value can only be specified for update action "replace".

Action: Either do not specify a null value for the column or specify the "replace" update action.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00167: The specified update action, "{0}", is not valid for column type "{1}".

Cause: The specified update action is not valid for the specified column type.

Action: Update action "replace" is valid for all column types. Update actions INCREMENT and DECREMENT are only valid for column types IntegerColumn, FloatColumn and DecimalColumn.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00168: An access violation has occurred. The current execution context does not have the required "{0}" permission to {1} "{2}".

Cause: An attempt was made to perform an operation on a BAM resource without the required permission.

Action: Insure that the required permission is granted to the appropriate user, group or application role attempting to perform the operation on the targeted BAM resource.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00169: Operation of type "{0}" is illegal for Data Object "{1}" of type "{2}".

Cause: An attempt was made to perform an operation of a type not compatible with the type of the target DataObject.

Action: Only operations of type INSERT can be applied to DataObjects of type STREAM and ARCHIVED_STREAM, whereas DataObjects of type ARCHIVED_RELATION are compatible with all operation types.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00170: Incompatible Data Object types detected. Data Object "{0}" of type "{1} cannot be derived from Data Object "{2}" of type "{3}".

Cause: An attempt was made to derive a DataObject from another DataObject with an incompatible Data Object type.

Action: DataObjects can only be derived from other DataObjects of the same DataObject type. The Data Object types are ARCHIVED_RELATION, STREAM and ARCHIVED_STREAM.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00171: The specified Data Object column name, "{0}", is invalid because it is a reserved keyword.

Cause: An attempt was made to use reserved keyword as column name.

Action: Column name should be string that except from reserved keyword.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00172: Attempt to specify the "unique" attribute for column "{0}" of derived DataObject "{1}". The "unique" attribute is only valid for base DataObject columns.

Cause: The "unique" attribute was specified for a derived DataObject column. The "unique" attribute is only valid for base DataObject columns.

Action: Remove the "unique" attribute from the specified derived DataObject column or, if possible, move this column down into the associated base DataObject.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00173: Attempt to specify the "unique" attribute for newly added column "{0}" of DataObject "{1}". The "unique" attribute cannot be specified for columns added to an exisiting DataObject.

Cause: The "unique" attribute was specified for a column being added to an existing DataObject. The "unique" attribute can only be specified for columns on initial creation of base DataObjects.

Action: Drop the specified DataObject and recreate it with the new column configured with the "unique" attribute.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00174: Invalid attempt to add column "{0}" to DataObject "{1}" where this column does not allow null values and does not specify a non-null default value.

Cause: Added columns that do not allow null values must supply a non-null default value. BAM must set the value for this newly added column in any existing DataObject instances to this default value.

Action: Provide a non-null default value for the newly added column if it does not allow null values or change the newly added column to allow null values.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00175: The column "{0}" in Data Object "{1}" is not valid for use in a Data Object {2,choice,0#insert operation|1#update operation|2#operation filter|3#index}.

Cause: An attempt was made to use a Data Object column for a purpose for which it is invalid.

Action: Do not use the specified column for the specified purpose.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00176: A BAM security exception has occurred. See exception cause for further details.

Cause: An exception has occurred in the BAM security subsystem.

Action: See exception cause for details on the specific problem.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00177: An exception has occurred in BAM query processing. See exception cause for further details.

Cause: An exception has occurred in BAM query processing.

Action: See exception cause for details on the specific problem.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00178: An exception has occurred attempting to establish the BAM metadata storage facility. See exception cause for further details.

Cause: An exception has occurred attempting to establish the BAM metadata storage facility.

Action: See exception cause for details on the specific problem.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00179: An exception has occurred attempting to determine if Timer Service is operating in single server or clustered environment. See exception cause for further details.

Cause: An exception has occurred attempting to determine if Timer Service is operating in single server or clustered environment.

Action: See exception cause for details on the specific problem.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00180: An exception has occurred attempting to lookup the TimerService at "{0}". See exception cause for further details.

Cause: An exception has occurred attempting to lookup the TimerService.

Action: See exception cause for details on the specific problem.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00181: The specified metadata type, "{0}", is unsupported in this context.

Cause: The metadata type specified is unsupported in this context.

Action: Refer to product documentation for explanation of different BAM metadata types.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00182: An exception has occurred attempting to fire rule id "{0}". See exception cause for further details.

Cause: An exception has occurred attempting to fire a rule.

Action: See exception cause for details on the specific problem.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00183: No BAM Service function specified.

Cause: A BAM Service function HTTP request was made that did not specify a BAM Service function.

Action: A BAM Service function HTTP request requires a valid BAM Service name and function.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00184: No BAM Service name specified for BAM Service function.

Cause: A BAM Service function HTTP request was made that did not specify a BAM Service name.

Action: A BAM Service function HTTP request requires a valid BAM Service name and function.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00185: BAM Service function specified, "{0}", is invalid.

Cause: A BAM Service function HTTP request was made that did not specify a valid BAM Service function.

Action: A BAM Service function HTTP request requires a valid BAM Service name and function.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00186: BAM Service name specified, "{0}", is invalid for BAM Service function.

Cause: A BAM Service function HTTP request was made that did not specify a valid BAM Service name.

Action: A BAM Service function HTTP request requires a valid BAM Service name and name.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00187: The BAM Server is unavailable. The server state is "{0}".

Cause: The BAM Server is not in an available state.

Action: Check log for further details as to the cause of the failure.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00188: Credential with name, "{0}", can not be found.

Cause: Credential with specified name can not be found.

Action: Create the credential in Enterprise Manager or other ways.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00189: Credential with name, "{0}", already exists.

Cause: Credential with specified name can not be found.

Action: Create the credential in Enterprise Manager or other ways.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00190: The specified Data Object name, "{0}", is invalid because it contains invalid characters.

Cause: A Data Object name was specified that contains invalid characters.

Action: Data Object names can only contain the special character underscore. All other special characters are invalid.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00191: The specified Data Object column name, "{0}", is invalid because it contains invalid characters.

Cause: A Data Object column name was specified that contains invalid characters.

Action: Data Object column names can only contain the special character underscore. All other special characters are invalid.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00192: The length specified ({0,number,#0}) for Data Object string column, "{1}", is invalid. Length must be between 1 and {2,number,#0}, inclusive.

Cause: A Data Object string column was specified with a invalid length.

Action: Change the Data Object string column length so that it is in the specified valid range.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00193: The precision specified ({0,number,#0}) for Data Object decimal column, "{1}", is invalid. Precision must be between {2,number,#0} and {3,number,#0}, inclusive.

Cause: A Data Object decimal column was specified with a invalid precision.

Action: Change the Data Object decimal column precision so that it is in the specified valid range.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00194: The scale specified ({0,number,#0}) for Data Object decimal column, "{1}", is invalid. Scale must be between {2,number,#0} and {3,number,#0}, inclusive.

Cause: A Data Object decimal column was specified with a invalid scale.

Action: Change the Data Object decimal column scale so that it is in the specified valid range.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00195: Invalid attempt to add column "{0}" to DataObject "{1}" where this column does not allow null values, does not specify a non-null default value and the DataObject contains existing data.

Cause: Added columns that do not allow null values must supply a non-null default value or the DataObject must not contain any existing data. BAM must set the value for this newly added column in any existing DataObject rows to this default value so we need a default value or we need the DataObject to contain no existing rows.

Action: To make this addition provide a non-null default value for the newly added column or delete all the existing data from the DataObject or change the newly added column to allow null values.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00196: Invalid attempt to modify column "{0}" in DataObject "{1}" to not allow null values when the DataObject already contains null values for this column.

Cause: Columns cannot be modified to not allow null values if the DataObject already contains null values for that column.

Action: To make this modification you would need to remove existing null values from the DataObject for the modified column.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00197: An operation specifies the data type of column "{0}.{1}" in DataObject "{2}" as "{3}" when it is defined as "{4}".

Cause: An operation was specified with the incorrect data type for the specified column.

Action: Modify your operation to specify the correct data type.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00198: An exception has occurred attempting to assign the specified value "{0}" to column "{1}.{2}" in DataObject "{3}".{4}

Cause: An exception has occurred attempting to assign the specified value to the indicated column.

Action: Make sure the value being specified is valid for the indicated column. The text of the exception should indicate the problem.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00199: {0} occurred parsing a DataObject operations XML payload. Line({1}) Column({2}) Offset({3}) Node({4}) Object({5}) Exception: {6}

Cause: An exception has occurred attempting to parse a DataObject operations XML payload.

Action: Correct the problem and retry the DataObject operation. The text of the exception should indicate the problem.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00200: An aggregate expression is not allowed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00201: Argument {1} in function {0} must be a Boolean value.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00202: Argument {1} in function {0} must be a datetime type value.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00203: Argument {1} in function {0} must be an integer.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00204: Argument {1} in function {0} must be numeric.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00205: Argument {1} in function {0} must be a string.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00206: The function {0} requires argument values of same data type.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00207: Cannot be divided by zero.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00208: The MOD operator can only be used with integers.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00209: Invalid expression.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00210: invalid aggregate operand

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00211: The function {0} requires {1} arguments.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00212: invalid filter expression

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00213: Math expression contains a non-numeric operand.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00214: Return values differ in type.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00215: unknown expression type

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00216: Invalid arguments.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00217: Calculated field does not have a name.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00218: BAM Server has encountered an exception. See exception cause for further details.

Cause: The BAM server has encountered an exception.

Action: See exception cause in log file for further details.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00219: Unknown or unsupported data type encountered: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00220: 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-00221: 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-00250: A JMS message was received by BAM Persistence with no associated credentials. This message cannot be processed.

Cause: A JMS message was received by BAM Persistence with no associated credentials.

Action: All JMS messages sent to BAM Persistence must have attached credentials.
Level: 1

Type: ERROR

Impact: Configuration

BAM-00251: An unsupported JMS message type was received by BAM Persistence. This message cannot be processed.

Cause: A JMS message was received by BAM Persistence in an unsupported message type.

Action: BAM Persistence supports DataObjectOperations(java) instances sent as a serialized object in a JMS ObjectMessage or in XML or JSON formats as a JMS TextMessage.
Level: 1

Type: ERROR

Impact: Configuration

BAM-00252: A JMS text message was received by BAM Persistence with no text specified. This message cannot be processed.

Cause: A JMS text message was received by BAM Persistence with no text specified (i.e. No message body).

Action: The BAM Persistence API expects JMS text messages to contain a DataObjectOperations(java) instance as a string in XML or JSON formats.
Level: 1

Type: ERROR

Impact: Configuration

BAM-00253: The specified BAM payload format, "{0}", is invalid for JMS text messages. This message cannot be processed.

Cause: The supported BAM payload formats for JMS text messages are XML or JSON.

Action: Change the BAM payload format to one of the supported formats for JMS text messages.
Level: 1

Type: ERROR

Impact: BamServer

BAM-00255: A JMS object message was received by BAM Persistence with no object specified. This message cannot be processed.

Cause: A JMS object message was received by BAM Persistence with no object specified (i.e. No message body).

Action: BAM Persistence expects JMS object messages to contain a serialized instance of DataObjectOperations(java).
Level: 1

Type: ERROR

Impact: Configuration

BAM-00256: A JMS object message was received by BAM Persistence which contained an object other than DataObjectOperations(java). This message cannot be processed.

Cause: A JMS object message was received by BAM Persistence which contained an object other than DataObjectOperations(java).

Action: BAM Persistence expects JMS object messages to contain a serialized instance of DataObjectOperations(java).
Level: 1

Type: ERROR

Impact: Configuration

BAM-00257: The specified BAM payload format, "{0}", is invalid for this BAM Persistence API method.

Cause: The supported BAM payload formats for Persistence API methods that take a string payload are XML or JSON.

Action: Change the BAM payload format to one of the supported formats for Persistence API methods that take a string payload.
Level: 1

Type: ERROR

Impact: BamServer

BAM-00258: The specified BAM payload format, "{0}", is not yet implemented.

Cause: A BAM payload format was specified that is not yet implemented.

Action: Switch to one of the implemented BAM payload formats: POJO, XML or JSON.
Level: 1

Type: ERROR

Impact: BamServer

BAM-00259: JMS message receiver "{0}" failed to start. See exception causes for details.

Cause: A JMS message receiver failed to start.

Action: See exception causes for details on the cause of the failure.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00260: Exception encountered attempting to start message processing thread "{1}" of JMS message receiver "{0}". See exception causes for details.

Cause: An exception occurred attempting to start the message processing thread of a JMS message receiver.

Action: See exception causes for details on the cause of the failure.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00261: Message processing thread "{1}" of JMS message receiver "{0}" cannot be started because its current state is "{2}".

Cause: The message processing thread of a JMS message receiver cannot be started because its current state is illegal for a start request.

Action: The current state of the message processing thread is incompatible for a start request. For example, it may already be running or already failed to start.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00262: Exception encountered attempting to stop message processing thread "{1}" of JMS message receiver "{0}". See exception causes for details.

Cause: An exception ocurred attempting to stop the message processing thread of a JMS message receiver."

Action: See exception causes for details on the cause of the failure.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00263: Message processing thread "{1}" of JMS message receiver "{0}" cannot be stopped because its current state is "{2}".

Cause: The message processing thread of a JMS message receiver cannot be stopped because its current state is illegal for a stop request.

Action: The current state of the message processing thread is incompatible for a stop request. For example, it may already be stopped or failed to start.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00264: Exception encountered attempting to set the mode of message processing thread "{1}" of JMS message receiver "{0}" to "{2}". See exception causes for details.

Cause: An attempt to set the mode of the message processing thread of a JMS message receiver failed.

Action: See exception causes for details on the cause of the failure.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00265: A Rest API call was received by BAM Persistence with no associated credentials. This call cannot be processed.

Cause: A Rest API call was received by BAM Persistence with no associated credentials.

Action: All Rest API call made to BAM Persistence must have attached credentials.
Level: 1

Type: ERROR

Impact: Configuration

BAM-00300: Modifier XML contains an invalid <Group> element.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00301: Modifier XML contains an invalid <RecordField> element.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00302: Modifier XML contains an invalid <Sort> element.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00303: Modifier XML is invalid.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00304: Modifier XML does not contain any <Modifier> elements.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00305: Modifier XML does not contain a <Modifiers> element.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00306: Modifier XML does not contain a Dataset name.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00307: Modifier XML contains an unknown operator.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00400: Modifier XML contains prompts or parameters.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00500: Column value overflow: {0} value {1} is not between {2} and {3}

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00501: Invalid xsd:datetime: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00600: A negative or zero grouped time bucket cannot be created.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00601: Time buckets with a non-time-based function cannot be created.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00602: {0} is not divisible by {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00700: Report Cache initialization failed. Reason: "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00701: Report Cache open view set exception. See exception cause for further details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00702: Viewset not found. "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00703: Coherence could not be initialized. See Exception cause for details..

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00704: No Business QueryID passed in modifier while opening the view.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00705: Not a valid view set id. Empty view set id passed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00706: No Business Project name passed in modifier while opening the view.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00707: View Set Builder is not provided while opening the view.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00801: Unsupported operation was invoked: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00802: Initialize External DO Query Service providing JNDI/JDBC information before invoking this operation: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00803: AGO calculated function is not supported in BI mode.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00804: Calculated function: {0} is not supported in CQL.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00900: Unable to identify changes of Continuous Query to notify Dependent Objects

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00901: Object exists already, type: {0}, name: {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00902: Can't found Object, id: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00903: Project {0} does not exist.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00904: Validation failed, Can not find object {0} when handling {1} {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00905: Creation failed, type: {0}, name: {1}, message: {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00906: Failed to unserialize object {0} due to {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00907: Error happened for {0} name {1} due to error: {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00908: BeamMDSException, type: {0}, name: {1}, message: {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00909: Connection to BAM Server "{0}" failed .Please verify Username and Password.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00910: Connection to BAM Server failed :{0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00911: Validation failed, Can not find dependent objects for {0} {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00912: Can not find application role, group or user {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00913: Can not export data for logical data object.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00914: Connection to BAM Server "{0}" failed.Please verify the server URL.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00915: Unable to import zip file because the zip file version, "{0}", is higher than the version of the target Bam Server, "{1}".

Cause: Import is not allowed due to the mismatched version.

Action: Find the artifacts which versions are either equivalent or lower than the target Bam server to be imported.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00916: A Error happened when handling the zip file. See exception cause for further details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00917: Object with type: {0}, name: {1}, is invalid.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00918: Config API Exception occurred. Please check the log trace for more details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-00920: Principal {0} of type {1} does not exist.

Cause: The principal, user, group or application role does not exis

Action: Create it the system.
Level: 1

Type: ERROR

Impact: OTHER

BAM-00921: The format of the version in zip file, "{0}", is invalid. Please correct it in the zip file.

Cause: The format of the version doesn't follow the convention of BAM server.

Action: Correct it in the zip file.
Level: 1

Type: ERROR

Impact: OTHER

BAM-01001: Unable to get Config session

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01002: Unable to get Persistence session

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01003: Invalid payload XML, can not parse it

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01004: Invalid column data type

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01005: Unable to find the data object by the given display name

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01006: Could not create the Data Object

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01007: Could not update the Data Object

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01008: Could not delete the Data Object

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01009: Could not insert into Data Object

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01010: Could not update into Data Object

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01011: Could not delete from Data Object

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01012: Could not upsert into Data Object

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01013: Could not perform batch operation into Data Object

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01014: Unable to complete Get operation

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01015: Unable to fetch the specified rows from Data Object

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01016: Invalid Column name in the payload

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01017: Invalid CSV/payload. Please check if they match

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01018: Invalid Date Time specified

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01019: Invalid operation type

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01020: Could not get info for such a Data Object

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01021: Could not delete the data object

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01022: Could not create the data object

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01023: Could not update the data object

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

BAM-01024: Could not update the data object due to invalid payload

Cause: Payload has data for different Data Objects

Action: Provide data for only Data Object
Level: 1

Type: ERROR

Impact: OTHER

BAM-01025: Invalid keysCSV. Data Object does not contain specified key column {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: OTHER

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: Unable to load external class "{0}" from provided jar "{1}".

Cause: The Alerts Engine was unable to load the specified external action class from the specified jar file.

Action: Confirm that the specified external action class name and jar file name are correct and available.
Level: 1

Type: ERROR

Impact: Data

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 is null or empty string.

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-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: Data control is not available for the selected query {0}. Edit and Save the query again.

Cause: Data control is not available for the selected query.

Action: Edit and save the query again
Level: 1

Type: ERROR

Impact: Composer

BAM-02320: Alerts Engine encountered invalid rule XML for Alert {0}. The alert could not be initialized.

Cause: Failed to initialize rule from invalid rule XML.

Action: Configure Event, Condition and Action and save.
Level: 1

Type: ERROR

Impact: Data

BAM-02321: Alerts Engine encountered invalid event XML for Alert {0}. The alert could not be initialized.

Cause: Failed to initialize event from invalid event XML.

Action: Configure Event and save.
Level: 1

Type: ERROR

Impact: Data

BAM-02322: Alerts Engine encountered invalid action XML for Alert {0}. The alert could not be initialized.

Cause: Failed to initialize rule from invalid action XML.

Action: Configure Action and save.
Level: 1

Type: ERROR

Impact: Data

BAM-02323: Alerts Engine failed to initialize Alert {0} from rule XML.

Cause: Failed to initialize Alert from rule XML.

Action: Configure Event, Condition and Action and save.
Level: 1

Type: ERROR

Impact: Data

BAM-02324: Alerts Engine encountered an exception.

Cause: Alerts Engine encountered an exception. See exception cause for further details.

Action: See exception cause for details on the specific problem.
Level: 1

Type: ERROR

Impact: OTHER

BAM-02325: Unable to find CQService after several attempts.

Cause: Alerts Engine encountered an exception.

Action: Try the operation again or else restart the server.
Level: 1

Type: ERROR

Impact: Data

BAM-02326: Error parsing wsdl. Unable to display operations using given URL.

Cause: Error parsing wsdl. Unable to display operations using given URL.

Action: Provide valid URL for WSDL
Level: 1

Type: ERROR

Impact: Composer

BAM-02327: Error parsing wsdl. Unable to display parameters for selected operation

Cause: Error parsing wsdl. Unable to display parameters for selected operation

Action: Provide valid URL for WSDL
Level: 1

Type: ERROR

Impact: Composer

BAM-02328: Horizontal Bar does not support queries with time series as dimension.

Cause: Horizontal Bar does not support time series enabled query.

Action: Select any other business view type compatible to queries with time series as dimension.
Level: 1

Type: ERROR

Impact: Composer

BAM-02329: Unable to load external class "{0}" from provided jar "{1}".

Cause: The Custom Action Executor was unable to load the specified external action class from the specified jar file.

Action: Confirm that the specified external action class name and jar file name are correct and available.
Level: 1

Type: ERROR

Impact: Composer

BAM-02330: "Any" i.e a wildcard, can only be used with a query having "Like" operator associated with it.Can not proceed with this value : "{0}" for parameter : "{1}"

Cause: One or more queries are using the same parameter with other operators too.

Action: Create new parameter, if One or more queries are using the same parameter with different operators
Level: 1

Type: ERROR

Impact: Composer

BAM-02331: One or more selected filter field values are empty.

Cause: One or more selected filter field values are empty.

Action: Ensure that all the selected filter field values are provided
Level: 1

Type: ERROR

Impact: Composer

BAM-02332: Exception occured while loading the runtime makeactive configuration from pagedef.

Cause: PageDef file may corrupted.

Action: Create a new bsinessview and replace the existing one in dashboard
Level: 1

Type: ERROR

Impact: Composer

BAM-02333: Exception occured while saving the selected Dimensions to pagedef/jsff.

Cause: PageDef/JSFF file may corrupted.

Action: Create a new bsinessview and replace the existing one in dashboard
Level: 1

Type: ERROR

Impact: Composer

BAM-02334: Min value is more then the Max value for filter field: "{0}".

Cause: From value is more then the To value.

Action: Ensure that correct values are provided
Level: 1

Type: ERROR

Impact: Composer

BAM-02335: Cannot remove query legend "{0}" from selected dimension list

Cause: User trying to remove the query legend from selected dimension list.

Action: Ensure that query legend is not removed
Level: 1

Type: ERROR

Impact: Composer

BAM-03110: Variance function is applicable only for Flat Query.

Cause: STDDEVFROMMEAN and VARIANCEFROMMEAN are applicable only for flat query.

Action: Use flat query for variance analysis
Level: 1

Type: ERROR

Impact: Common Query

BAM-03111: Variance function should be part of select list in order to use in Filter Expression.

Cause: Variance function should be part of select list in order to use in Filter Expression.

Action: Include variance function in select list
Level: 1

Type: ERROR

Impact: Common Query

BAM-03112: An exception occurred attempting to load the external security plugin configuration file "ExternalSecurity.properties". See exception cause for further details.

Cause: An exception occurred attempting to load the external security plugin configuration file "ExternalSecurity.properties".

Action: See the exception cause for further details.
Level: 1

Type: ERROR

Impact: Common Query

BAM-03113: An exception occurred attempting to load the "{0}" external security plugin "{1}". See exception cause for further details.

Cause: An exception occurred attempting to load the specified external security plugin class.

Action: See the exception cause for further details.
Level: 1

Type: ERROR

Impact: Common Query

BAM-03114: An exception occurred attempting to get a filter expression for DataObject "{0}" from the "{1}" external security plugin "{2}". See exception cause for further details.

Cause: An exception occurred attempting to get a filter expression for the specified DataObject from the specified external security plugin class.

Action: See the exception cause for further details.
Level: 1

Type: ERROR

Impact: Common Query

BAM-03115: DisplayName conflicts: {0}.

Cause: An exception occurred attempting to add a DataObject with a duplicate display name.

Action: Change the display name of new DataObject.
Level: 1

Type: ERROR

Impact: Composer

BAM-03116: Name conflicts: {0}.

Cause: An exception occurred attempting to add a DataObject with a duplicate display name.

Action: Change the name of new DataObject.
Level: 1

Type: ERROR

Impact: Composer

BAM-03117: ID conflicts: {0}.

Cause: An exception occurred attempting to add a DataObject with a duplicate ID.

Action: Change the id of new DataObject.
Level: 1

Type: ERROR

Impact: Composer

BAM-03118: Field cannot be null: {0}.

Cause: The field is necessary but we do not set it.

Action: Set value for the field.
Level: 1

Type: ERROR

Impact: Composer

BAM-03119: Input parameter cannot be null: {0}.

Cause: The parameter is necessary but we do not assign a value to it.

Action: Set value for the input parameter.
Level: 1

Type: ERROR

Impact: Composer

BAM-03120: Object is not found with ID: {0}.

Cause: Caller specify a wrong ID, or the object has been removed.

Action: Change the ID.
Level: 1

Type: ERROR

Impact: Composer

BAM-03121: Data Object {0} is being used by these BAM Objects: {1}.

Cause: The object is being used by some other objects, we cannot delete it.

Action: Delete the objects those dependent on this object before delete this object.
Level: 1

Type: ERROR

Impact: Composer

BAM-03122: Beam Project does not exist: {0}.

Cause: The project has not been created or has been removed, but user tries to create something under it.

Action: Check the project first.
Level: 1

Type: ERROR

Impact: Composer

BAM-03123: Flex table already exits: {0}.

Cause: BAM tries to publish a flex table to persistence, but the flex table has been there.

Action: Remove the old flex table or change the name of new Data Object.
Level: 1

Type: ERROR

Impact: Composer

BAM-03124: Beam Project does not exist: {0}.

Cause: The project has not been created or has been removed, but user tries to create something under it.

Action: Check the project first.
Level: 1

Type: ERROR

Impact: Composer

BAM-03125: Data Object {0} doesn't have any joins.

Cause: Data Object does not join with others.

Action: Check the Logical Data Object.
Level: 1

Type: ERROR

Impact: Composer

BAM-03126: Find more than one Data Objects {0} work as the center of star schema.

Cause: Find more than one Data Objects work as the center of star schema.

Action: Check the Logical Data Object.
Level: 1

Type: ERROR

Impact: Composer

BAM-03127: Self join is not supported: {0}.

Cause: The Data Object is joinning to itself.

Action: Check the Logical Data Object.
Level: 1

Type: ERROR

Impact: Composer

BAM-03128: Data Object has not been added to Logical Data Object: {0}.

Cause: We find the join relation on one Data Object, but it is not added to Logical Data Object.

Action: Add the Data Object to Logical Data Object.
Level: 1

Type: ERROR

Impact: Composer

BAM-03129: Column {0} is being used by Logical Column {1} and can not be deleted.

Cause: Column is being used by some objects.

Action: Clear the dependency before we remove it.
Level: 1

Type: ERROR

Impact: Composer

BAM-03130: Column {0} is being used by Index {1} and can not be deleted.

Cause: Column is being used by some objects.

Action: Clear the dependency before we remove it.
Level: 1

Type: ERROR

Impact: Composer

BAM-03131: Column {0} is being used by Hierarchy {1} and can not be deleted.

Cause: Column is being used by some objects.

Action: Clear the dependency before we remove it.
Level: 1

Type: ERROR

Impact: Composer

BAM-03132: Multple facts is not allowed in star schema: {0}.

Cause: Multple facts is not allowed.

Action: Check the Logical Data Object.
Level: 1

Type: ERROR

Impact: Composer

BAM-03133: Data Object {0} is internal or system managed, can not be removed.

Cause: The object is internal or system managed, we cannot delete it.

Action: Don't try to delete this type data object
Level: 1

Type: ERROR

Impact: Composer

BAM-04001: Unable to find metadata: {0}.

Cause: Unable to find metadata "{0}"

Action: See the exception cause for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04002: Table not found: {0}.

Cause: An exception occurred attempting to find table for data object "{0}". "{1}"

Action: See the exception cause for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04003: Semantic analysis error : "{0}"

Cause: An exception occurred attempting to parse query: "{0}"

Action: See the exception cause for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04004: Destination error : "{0}"

Cause: Can't push data to destination "{0}".

Action: See the exception cause for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04005: Query execution error:"{0}".

Cause: Unable to execute query "{0}", "{1}".

Action: See the exception cause for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04006: EJB "{0}" is unavailable.

Cause: EJB "{0}" is unavailable.

Action: See the stack trace for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04007: Invalid event endpoint is used "{0}".

Cause: Invalid event endpoint is used "{0}".

Action: See the stack trace for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04008: Unable to send tuple "{0}".

Cause: An exception occurred attempting to send tuple "{0}".

Action: See the stack trace for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04009: Filter column is not set.

Cause: An exception occurred attempting to update data in the Data Object "{0}".

Action: See the stack trace for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04010: CQService coherence cache is not initialized correctly.

Cause: CQService coherence cache is not initialized correctly.

Action: See the stack trace for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04011: Unable to execute DDL to CQLEngine.

Cause: Unable to execute DDL to CQLEngine.

Action: See the stack trace for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04012: Unable to execute DML to CQLEngine.

Cause: Unable to execute DML to CQLEngine.

Action: See the stack trace for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04013: MessageSelectorIsNull

Cause: The message select is null for data object "{0}".

Action: See the stack trace for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04014: UnableToStartJMSSource

Cause: Unable to start jms recevier on destination "{0}". "{1}"

Action: See the stack trace for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04015: UnableToCloseJMSSource

Cause: Unable to close jms recevier on destination "{0}". "{1}"

Action: See the stack trace for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04016: UnableToGetEventConverter

Cause: Unable to get event converter "{0}", "{1}".

Action: See the stack trace for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04017: ParseDDLError

Cause: Parse fails "{0}", "{1}".

Action: See the stack trace for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04018: IncorrectScheduledQuerySyntax

Cause: Scheduled query syntax is incorrect: "{0}".

Action: See the stack trace for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04019: IncorrectTimeFormat

Cause: The time format in scheduled query syntax is incorrect: "{0}".

Action: See the stack trace for further details.
Level: 1

Type: ERROR

Impact: CQService

BAM-04999: Query execution error:"{0}".

Cause: Unable to execute query "{0}".

Action: See the exception cause for further details.
Level: 1

Type: ERROR

Impact: CQService

7 BEA-000001 to BEA-2194839

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-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} with ID:{2} from cluster:{1} view due to timeout.

Cause: Removing {0} from cluster as it failed to send heartbeats 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 {1} from a server listening on {0}.

Cause: This is an informational message.

Action: If this message continues to appear, ensure that the network is stable. Contact My Oracle Support for further assistance.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000144: Managed Server {0} has been suspended or shut down.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000145: Managed Server {0} is tagged as a migratable server. A cluster that has migratable servers should configure a JDBC data source to ensure that the migratable server is highly available.

Cause: The cluster is misconfigured.

Action: Configure the DataSourceForAutomaticMigration property.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000147: Server "{0}" failed to renew lease in the {1}.

Cause: The server failed to renew the lease on time.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000148: Migratable server "{0}" is misconfigured. For automatic migration, a pool of machines should be assigned to the cluster or each migratable server in the cluster should have at least a couple of machines assigned to it for automatic migration.

Cause: The migratable server is misconfigured.

Action: Ensure that the server is targeted to a machine and restart the migratable server.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000149: Server failed to get a connection to the {1} during {0}.

Cause: The database or the consensus leasing basis appears to be down.

Action: Ensure that the database is accessible to the cluster. In the case of consensus leasing basis the server is in the minority partition and the leasing basis is in some other partition that is not reachable.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000150: Server failed to get a connection to the {1} in the past {0} seconds for lease renewal. Or, Server could get a connection but failed to renew the lease. Server will shut itself down.

Cause: The database or consensus leasing basis appears to be down.

Action: Ensure that the database is accessible to the cluster. In the case of consensus leasing basis, the server is in the minority partition and the leasing basis is in some other partition that is not reachable. If this message continues to appear even when the database is accessible, something may be wrong in the database. Contact My Oracle Support for further assistance.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000151: Server "{0}" has taken over the role of Cluster Master.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000152: Server "{0}" lost the privileges to be the Cluster Master.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000153: Cluster is misconfigured. For automatic migration, a pool of machines should be assigned to the cluster or each migratable server in the cluster should at least have a couple of machines assigned to it for automatic migration.

Cause: The cluster is misconfigured.

Action: Assign a pool of machines for automatic migration and refer to WebLogic Server documentation for more details.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000154: Cluster is misconfigured. The remote cluster address {0} is not a valid URL.

Cause: The server is misconfigured.

Action: Set the correct remote cluster address and restart the servers. If it is not clear on how to set remote ClusterAddress, refer to WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000155: Configured cluster address is invalid : {0}. Constructing cluster address dynamically.

Cause: The cluster configuration is invalid.

Action: Ensure that the cluster address contains either a DNS name or a comma-separated host list (or IP list) or a comma-separated host:port list (or IP:port list).
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000156: Could not send out new attributes for cluster member {0}: {1}.

Cause: There was a problem sending out changed member attributes.

Action: Examine the server logs.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000158: Server has stopped sending cluster heartbeats and announcements. It is still receiving heartbeats and announcements from other cluster members.

Cause: The server is going out of the cluster as a result of the suspend or shutdown operation.

Action: No action is required
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000159: The clocks of the machines hosting local server and remote server "{0}" are off by {1} seconds

Cause: The clocks of the machines hosting servers in the cluster are not synchronized.

Action: Ensure that all the machines are synchronized to the same time.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000160: A request to synchronize the JNDI tree has been made over an insecure channel. Configure a secure HTTP channel for all of the servers in the cluster.

Cause: The cluster was configured to encrypt multicast data but the request to synchronize the JNDI tree was done on a non-secure channel (HTTP). To secure the cluster completely, configure a secure HTTP channel for all of the servers in the cluster.

Action: Configure a secure HTTP channel on all of the servers in the cluster.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000161: Multicast message from server {0} appears to have been tampered with.

Cause: The authenticity of the message could not be verified.

Action: Ensure that the network is not being hijacked.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000162: Starting "{0}" replication service with remote cluster address "{1}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000163: Stopping "{0}" replication service

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000164: Synchronized cluster JNDI tree from server {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000165: Some other domain has a cluster that is configured to use the same multicast address and port as a cluster in {0}. Two domains in the same LAN should not use the same multicast address.

Cause: Two clusters on the local area network are using the same multicast address.

Action: Change the multicast address of either domain.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000166: Some other cluster in this domain is configured to use the same multicast address as {0}. Clusters cannot use the same multicast address.

Cause: Multiple clusters in the same domain are using the same multicast address.

Action: For efficiency purposes, use two different multicast addresses.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000167: Some services failed to roll back successfully when trying to abort the migration: {0}.

Cause: An exception caused the rollback to fail: {0}.

Action: It would be safest to shut down this server so that any lingering services will stop. They will not be automatically restarted upon reboot. Once the cause of the rollback has been fixed, attempts to migrate to this server should be successful.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000168: Failed to restart/migrate server "{0}" because of {1}

Cause: There was an error while restarting migratable server: {1}

Action: Examine the server logs.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000170: The server {0} did not receive the multicast packets that it sent.

Cause: Each WebLogic Server instanec is expected to receive the messages it multicast to its multicast group. Since the server does not receive its own messages, the multicast address configuration in the cluster configuration or the interface address specification may be wrong.

Action: Ensure that the cluster configuration and server interface configuration are valid
Level: 1

Type: ERROR

Impact: Cluster

BEA-000171: Failed to load the custom Singleton Services SQL Query Helper: {0}, because of {1}.

Cause: The most likely cause for failing to load the named class is either a typo in the name of the class or that the class is missing from the server classpath.

Action: Ensure that the provided classname is valid and that the class exists in the classpath of the server.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000172: TCP/IP socket failure occurred while fetching state dump over HTTP from {0}. Error message received: {2}. The request was generated by {3}. {1}

Cause: An IOException occurred in the operating system.

Action: Ensure that no problems exist in the network. If the problem persists, contact My Oracle Support with the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000176: {0} does not specify a machine.

Cause: {0}'s configuration does not specify the machine on which it is running. Machines must be specified if scripts are to be executed when migrations happen.

Action: Specify the machine on which {0} is running in the server's console page.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000178: Failed to execute {0} because of {1}.

Cause: While trying to run {0}, an exception occurred: {1}.

Action: Check that the script, {0}, is fully debugged. It may help to run the script by hand to see if any errors are raised.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000179: {0} failed while altering its lease.

Cause: An exception occurred: {1}.

Action: Ensure that, if a database is being used for leasing, it is available.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000180: Unable to retrieve Job {0} from the database. The retrieval failed with {1}

Cause: An error occurred while reading a job from the database.

Action: ENsure that the classes corresponding to the job are present in the server classpath and are of the correct version.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000182: Job Scheduler created a job with ID {0} for TimerListener with description {1}

Cause: Job Scheduler created an entry in the database for a submitted job.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000183: Successfully cancelled job with ID {0}

Cause: Job Scheduler removed a job entry from the database based on application request

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000184: This server did not attempt to renew its lease for {0} seconds. The server may need to be restarted or migrated.

Cause: The thread that is supposed to regularly renew the lease has become blocked for some reason.

Action: Ensure that the server is not overloaded with work and that there are enough system resources available on the machine.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000185: Despite the delay in the lease-renewing thread, the server has successfully renewed its lease. It is no longer in imminent risk of being migrated or restarted.

Cause: The thread that is supposed to regularly renew the lease became blocked, but is running properly again and has successfully renewed the lease.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000186: An error was encountered while migrating {0}: {1}

Cause: See the error in the message body.

Action: Ensure that there are enough candidate servers running in the cluster.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000187: The Singleton Service {0} is now registered on this server. This server may be chosen to host this service.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000188: The Singleton Service {0} is no longer registered on this server.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000189: The Singleton Service {0} is now active on this server.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000190: The Singleton Service {0} has been deactivated on this server.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000191: Now monitoring the Migratable Server {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000192: A running server was not found to host {0}. The server will retry in a few seconds.

Cause: All running servers failed when asked to activate {0}.

Action: Ensure that there is at least one active candidate server for this service and that there is no bug in the activate() method. The service will be tried on all running servers in another few seconds.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000193: The JTA service for {0} has failed, but {0} is still running. JTA cannot be migrated from a running server.

Cause: The JTA service failed.

Action: Check the logs of {0}; {0} should be restarted once the cause of the error has been determined and fixed. Upon restart, the JTA service will be migrated and running transactions recovered.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000194: An error was encountered while trying to report a migration event: {0}.

Cause: The most likely cause is the Administration Server being unavailable. If this is intended, this message can be ignored.

Action: If monitoring information is desired, the Administration Server should be running and reachable.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000195: An error was encountered while trying to save a migration event. The error was: {0}.

Cause: An internal WebLogic Server 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,2016, 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-000401: Socket queue full, dropping socket {0}.

Cause: The internal queue for socket read requests is full. Additional read requests for sockets will be dropped.

Action: Check for other log messages that give more information about the failure.
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: A ThreadDeath error occurred while processing sockets.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: INTERNAL_ERROR

Impact: Socket

BEA-000405: Uncaught Throwable in processSockets {0}.

Cause: A Throwable was caught while processing sockets.

Action: Check for other log messages that give more information about the failure.
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: A Throwable was caught while processing sockets.

Action: Check for other log messages that give more information about the failure.
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: The maximum allowed number of pending I/O requests ({0}) has been exceeded. Further read requests for the socket cannot be initiated.

Action: Check for other log messages that give more information about the failure.
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: Creation of the Java socket muxer failed.

Action: Ensure that the classpath is set properly.
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.

Action: Correct any conditions as suggested by the error message, if applicable.
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: The internal data record for the socket could not be found while completing an I/O operation.

Action: Check for other log messages that give more information about the failure.
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: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000502: Peergone send failed - target already gone.

Cause: This is an informational message.

Action: No action is required.
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: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000513: Failure in heartbeat trigger for RJVM: {0}. {1}

Cause: This error indicates a temporary failure in the heartbeat trigger mechanism.

Action: No action is required. This is usually a temporary failure.
Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000514: openConnection() failed. {0}

Cause: Possible causes are an invalid target address or the target not being active or reachable.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000515: execute failed {0}

Cause: A failure was encountered when handling the incoming HTTP message.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000519: Unable to connect to a remote server on address {1} and port {2,number,0} with protocol {0}. The exception is {3}

Cause: The target is either not reachable or is not active.

Action: Ensure that the target is active.
Level: 1

Type: WARNING

Impact: RJVM

BEA-000570: Network Configuration for Channel "{0}" Listen Address {1} Public Address {2} Http Enabled {3} Tunneling Enabled {4} Outbound Enabled {5} Admin Traffic Enabled {6} ResolveDNSName Enabled {7}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000572: The server rejected a connection attempt {0} probably due to an incorrect firewall configuration or administrative command.

Cause: The incoming connection attempt was probably made through an address translating firewall. WebLogic Server needs to be correctly configured for this to work. This message can also occur if an administration connection attempt, requiring administrator level security, is made on a non-administrative port.

Action: Configure the public and private addresses for this WebLogic Server instance to reflect the configuration of the firewall. The private address is the actual address the server is running. The public address is the address that external clients use to connect.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000573: RequestTimeout for message id {0} with message: {1}.

Cause: The server timed out while waiting for a response to a request. The configured timeout may not be sufficient enough for the runtime environment.

Action: Consider raising the value of the "weblogic.jndi.responseReadTimeout" property.
Level: 1

Type: WARNING

Impact: RJVM

BEA-000574: Bootstrap to {0} failed. The remote side declared peer may be gone on this JVM.

Cause: Bootstrapping to the remote address has failed likely due to a PeerGone on this JVM.

Action: Check whether the remote server is up and running
Level: 1

Type: ERROR

Impact: RJVM

BEA-000577: Unable to get weblogic.rjvm.WebRjvmSupport.webRjvmSupport from HK2 services. exception: {0}

Cause: weblogic.rjvm.WebRjvmSupport is not registered as an HK2 service.

Action: Contact My Oracle Support with the server logs and configuration.
Level: 1

Type: WARNING

Impact: RJVM

BEA-000578: Unable to load weblogic.rjvm.WebRjvmSupport.webRjvmSupport. exception: {0}

Cause: Class weblogic.servlet.internal.utils.WebRjvmSupportImpl can be loaded.

Action: Contact My Oracle Support with the server logs and configuration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000579: Failed to get client certificate. exception: {0}

Cause: Failed to get client certificate. exception: {0}

Action: Check the custom class which is specified by the system property weblogic.security.SSL.ClientCertPlugin.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000580: Failed to send {0}. {1}

Cause: While sending a message an error was encountered.

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-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: The indicated error has occurred while the server was shutting down.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Common

BEA-000610: 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-000611: No resources in the pool {0} will be tested, as specified MaxUnavailable {1} has been reached.

Cause: The application MaxUnavailable attribute for this pool has been configured. Since the number of unavailable resources in the pool has reached or exceeded the configured limit, no more resources will be tested (as resources become unavailable to the application during the testing).

Action: If necessary, tune the value for the MaxUnavailable attribute for the pool.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000612: All {1} resource instances currently available in the pool {0} are being tested.

Cause: This is a warning indicating that all currently available resources in the pool are being tested. Therefore, some or all of them may become unavailable to the application for a short time.

Action: Reduce the current setting of the MaxUnavailable attribute for the pool.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000613: Testing of resources upon creation has been dynamically enabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000614: Testing of resources upon creation has been dynamically disabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000615: Testing of resources when being reserved has been dynamically disabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000616: Testing of resources when being reserved has been dynamically enabled for pool "{0}".

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000617: Testing of resources when being released has been dynamically enabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000618: Testing of resources when being released has been dynamically disabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000619: Unable to forcibly release resource "{1}" back into the pool "{0}". Received exception: {2}.

Cause: As part of the InactiveResourceTimeout feature, resources that are found to be inactive for the configured period of time are forcibly released back into the pool. The operation could not be performed for the indicated reason.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Common

BEA-000620: Forcibly releasing inactive resource "{1}" back into the pool "{0}".

Cause: The resource was found to be unused by the application for the specified duration, and hence is being forcibly released back into the pool.

Action: Check application code for leakages of resource objects, or tune the configured value of the relevant pool attribute.
Level: 1

Type: WARNING

Impact: Common

BEA-000621: Expected RemoteException, RuntimeException, or Error {0}

Cause: An unexpected low-level message was sent to the server.

Action: This is likely to be due to an internal server/client error that should be reported to My Oracle Support.
Level: 1

Type: ERROR

Impact: Common

BEA-000622: Ignoring attempt to release resource "{1}" to pool "{0}" after the pool has been shut down.

Cause: Application is trying to release a resource to a pool after the pool has been shutdown.

Action: Check application behaviour. All resources should be closed before the application is shutdown.
Level: 1

Type: WARNING

Impact: Common

BEA-000623: Setting CapacityIncrement for pool "{0}" to 1. The specified value of "{1}" is not valid.

Cause: The application had specified an invalid value for CapacityIncrement.

Action: Check and correct the specified value for CapacityIncrement for the indicated pool.
Level: 1

Type: WARNING

Impact: Common

BEA-000624: Setting frequency of testing of free resources in pool "{0}" to 5 seconds, since the specified value of "{1}" is not valid.

Cause: The application had specified an invalid value for the test frequency.

Action: Check and correct the specified value for TestFrequencySeconds for the indicated pool.
Level: 1

Type: WARNING

Impact: Common

BEA-000625: The application has disabled periodic testing of free resources in pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000626: Free resources in pool "{0}" will be tested every "{1}" seconds.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000627: Reached maximum capacity of pool "{0}", making "{2}" new resource instances instead of "{1}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000628: Created "{1}" resources for pool "{0}", out of which "{2}" are available and "{3}" are unavailable.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000629: Recreated "{2}" out of "{1}" resources for pool "{0}".

Cause: As part of forcibly suspending a pool, all resources currently in use are destroyed and recreated. This message indicates that not all required resources were recreated.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Common

BEA-000630: Unable to create "{1}" resources for pool "{0}".

Cause: As part of the ConnectionCreationRetry feature, pools periodically attempt to create unavailable resources. This message indicates that in the current attempt, the indicated number of resources could not be created.

Action: Check whether the failure condition that prevents the resources from being created (for example, the database server or downed network connectivity to it) is still persisting.
Level: 1

Type: WARNING

Impact: Common

BEA-000631: Unknown resource "{1}" being released to pool "{0}": {2}

Cause: Application is trying to release a resource to a pool that is no longer part of the pool. This could happen if the pool was forcibly suspended (which results in all borrowed resources being closed and replaced with new ones) while the resource was borrowed by the application.

Action: Check application behavior.
Level: 1

Type: WARNING

Impact: Common

BEA-000632: Resource Pool "{0}" shutting down, ignoring {1} resources still in use by applications..

Cause: The administrator is shutting down the pool while applications are still using resources that they have obtained from the pool. It is possible that these resources may have been leaked by the applications.

Action: Check application behavior.
Level: 1

Type: WARNING

Impact: Common

BEA-000633: Resource Pool "{0}" suspending due to consecutive number of resource creation failures exceeding threshold of {1}

Cause: Resource creation or resource tests have repeatedly failed.

Action: Determine the cause of resource failures and take corrective action.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000634: Resource hang detected for pool "{0}", group "{1}". Waited {2} milliseconds where a typical test has been taking {3}.

Cause: Resource tests have been taking longer than expected.

Action: Correct the condition that causes the resource tests to block for extended periods of time.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000635: Resource Pool "{0}", group "{1}" disabled due to number of resource creation or test failures exceeding threshold of {2}.

Cause: Resource creation or resource tests have repeatedly failed.

Action: Determine the cause of resource failures and correct.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000636: Resource Pool "{0}", group "{1}" enabled.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000637: Resource Pool "{0}" resuming due to successful resource creation or test.

Cause: This is an informmational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000638: Resource Pool "{0}" is being suspended by an external command (multi data source or console or other).

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000639: Resource Pool "{0}" is being force-suspended by an external command (multi data source or console or other).

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000640: Resource Pool "{0}" resuming by external command (multi data source or console or other).

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000701: Unable to mount the fileSystem named {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000702: Unable to unmount the fileSystem named {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000703: Unable to get fileSystem context from Root {0}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000704: Cannot create file system at {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000705: Created file system at {0}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: NOTIFICATION

Impact: T3Misc

BEA-000706: Unable to find remote file {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000707: Unable to open remote file {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000708: T3RemoteOutputStreamProxy: write timed out or interrupted - {0}, {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000709: T3RemoteOutputStreamProxy: flush timed out or interrupted - {0}, {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000710: TimeRepeat trigger scheduled to run at a date in the past : {0}, trigger will not repeat

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000711: Uncaught throwable in run {0}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000712: Exception invoking {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000713: Exception closing stream {0}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000800: {0} stopped.

Cause: A ThreadDeath exception caused a shutdown.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: Kernel

BEA-000801: ExecuteRequest: {0} cancelled.

Cause: This only happens when WebLogic Server is used in conjunction with an IDE, which uses JVMDI to cancel in-flight requests. If this occurs in normal operation, contact My Oracle Support.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Kernel

BEA-000802: ExecuteRequest failed {0}.

Cause: An execute request generated an exception that was not handled.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Kernel

BEA-000803: The Class {0} has a setter {1} for attribute {2} which does not have a constructor that could be initialized from a String value of {3}.

Cause: No constructor that takes a String argument was found for the declared attribute type.

Action: Provide a constructor with a String argument.
Level: 1

Type: ERROR

Impact: Kernel

BEA-000804: The Class {0} attribute {1} could not be initialized with value {2}. The exception message is {3}.

Cause: See the exception stack trace for details.

Action: Take the appropriate action based on the error message.
Level: 1

Type: ERROR

Impact: Kernel

BEA-000805: The self-tuning thread pool is disabled. An execute queue will be created for each Work Manager definition.

Cause: The server is starting.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Kernel

BEA-000807: Work Manager {0} has reached its capacity. It is rejecting from thread {1}. The message is {2}. Throwable is {3}.

Cause: This is a Work Manager bug.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Kernel

BEA-000808: The executing thread is a non-WebLogic Server thread. Modify the application to use the Commonj Work Manager API.

Cause: The use of an application spawned a Java thread instead of the Commonj Work Manager API.

Action: Modify the application to use the Commonj Work Manager APIs.
Level: 1

Type: WARNING

Impact: Kernel

BEA-000810: The memory pressure field has changed from {0} to {1}.

Cause: The memory pressure in the system has gone either up or down.

Action: The system should be responding to the memory pressure level. No further action should be taken.
Level: 1

Type: NOTIFICATION

Impact: Kernel

BEA-000902: A duplicate expression was found in the system property {0}.nonProxyHosts: {1}.

Cause: The system property {0}.nonProxyHosts contains a pipe character delimited list of hosts, which should be connected to directly and not through the proxy server.

Action: Check the system property {0}.nonProxyHosts. The value can be a list of hosts, each separated by a |. In addition, a wildcard character (*) can be used for matching. For example: -D{0}.nonProxyHosts="*.foo.com|localhost".
Level: 1

Type: ERROR

Impact: Net

BEA-000903: Failed to communicate with proxy: {0}/{1}. Will try connection {2}/{3} now.

Cause: An IOException was received while communicating with the proxy server.

Action: Check the exception for more information. Check if the proxy is running by pinging the proxy: {0}/{1} from the same machine.
Level: 1

Type: ERROR

Impact: Net

BEA-000904: {0} initializing the URL stream handler with custom factory: {1}.

Cause: The factory class that was specified against the system property weblogic.net.http.URLStreamHandlerFactory failed to load or invoke.

Action: Check the system property weblogic.net.http.URLStreamHandlerFactory. This property is used to set a custom URLStreamHandlerFactory.
Level: 1

Type: ERROR

Impact: Net

BEA-000905: Could not open connection with host: {0} and port: {1}.

Cause: The connection attempt failed.

Action: Ensure that the server is running on the specified host and port.
Level: 1

Type: WARNING

Impact: Net

BEA-000906: Failed to communicate with proxy: {0}/{1}.

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-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-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 data sources.

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 data source must have a Global scope.

Action: Correct the configuration for the specified data source.
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 cannot be verified.

Cause: test-on-reserve is disabled in the data source configuration.

Action: Enable test-on-reserve in the data source configuration. If all member data sources are marked as unhealthy and the WLS Administration Server fails to boot, use WLST to change the configuration.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001588: Shrinking connection pools due to memory pressure level of {0} exceeding shrink threshold of {1}.

Cause: There is increased memory consumption in the server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001589: Setting all data source statement cache sizes to {0}% of configured sizes due to memory pressure level of {1}.

Cause: There is increased memory consumption in the server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001590: Setting {0} statement cache size to {1} ({2}% of configured size {3}).

Cause: There is increased memory consumption in the server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001591: Configuring data source {0} for partition {1}: {2}.

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001592: Forcibly releasing inactive connection "{1}" back into the data source connection pool "{0}".

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 the pool.

Action: Check the application code for leakages of connection objects, or tune the configured value of the specified connection pool attribute.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001593: Forcibly releasing harvested connection "{1}" back into the data source connection pool "{0}".

Cause: The connection was harvested and the application callback did not close the connection. This occurs only when Connection Leak Profiling is enabled.

Action: Close the connection in the ConnectionHarvestingCallback.cleanup() method.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001594: Forcibly releasing an already closed connection "{1}" back into the data source connection pool "{0}".

Cause: When isClosed() is called on the connection, either directly by the application or when accessing a connection, the driver indicates that the connection is already closed. The connection is closed in the WLS data source and returned to the pool. The connection will be replaced in the pool with a new connection.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001595: Forcibly releasing connection "{1}" back into the data source connection pool "{0}" because of an initialization failure.

Cause: A failure occurred on the connection during initialization. The connection will be removed from the pool if it continues to have problems.

Action: This may indicate a problem with the database. Review other errors in the WLS data source or the database logs.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001596: Data source connection pool "{0}" Connection Local Transaction Leak Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001597: Data source connection pool "{0}" Closed JDBC Object Usage Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001598: Oracle Notification Service (ONS) initialization failed for data source {0}. ONS events will not be processed.

Cause: The ONS host and pair list is invalid or was unavailable for connection.

Action: Check the ONS configuration to make sure that it is correct and available.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001599: When creating Active GridLink (AGL) data source named {0}, the URL should be the long format with a SERVICE_NAME.

Cause: An incorrect URL is specified for an AGL data source.

Action: Correct the URL specified for the AGL data source.
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. Remote Server contacting us is {1}

Cause: Clients tried to connect to the server before it was in the RUNNING state.

Action: Connect to the server after it has started.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002624: The administration protocol is "{0}" and is now configured.

Cause: The server has loaded the administration protocol making it available for outbound traffic and configurable for inbound traffic.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002625: An attempt to configure channel "{0}" failed because of {1}.

Cause: The cause is detailed in the accompanying exception.

Action: Review the exception.
Level: 1

Type: ERROR

Impact: Server

BEA-002626: The protocol "{0}" could not be loaded: {1}

Cause: Consult the exception for why the protocol could not be loaded.

Action: Consult the exception for why the protocol could not be loaded.
Level: 1

Type: WARNING

Impact: Server

BEA-002627: The domain configuration must have at least one administration channel on every server or no administration channels at all.

Cause: The server was contacted by a server that did not reflect the same administration state as itself.

Action: Modify the domain configuration so that all servers have administration channels, or enable the domain-wide administration port.
Level: 1

Type: ERROR

Impact: Server

BEA-002628: Unable to export RemoteLifeCycleOperations RMI object due to {0}.

Cause: The RMI export failed.

Action: Contact My Oracle Support and provide the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002630: Accepting connections again.

Cause: The server is accepting client connections again after refusing connections as part of server throttling.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002631: Max threshold reached for open sockets [total open sockets: {0}, allowed max: {1}]. No more connections allowed.

Cause: The MaxOpenSocketCount attribute of the server configuration defines the upper bound of the number of open sockets.

Action: Increase the MaxOpenSocketCount attribute of the server configuration. Use the server tuning tab in the Administration Console.
Level: 1

Type: WARNING

Impact: Server

BEA-002632: Found jrmp.jar in {0} directory. JRMP service is now enabled.

Cause: JRMP is enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002633: A port conflict was detected in the server "{4}" configuration. The server "{4}" is configured to listen on two ports that have the same port number and IP address. Channel "{0}" address "{1}" conflicts with channel "{2}" address "{3}".

Cause: The server is configured to listen on two ports that have the same port number and IP address.

Action: Ensure that the address identities [ListenAddress and ListenPort combinations] are distinct and unique.
Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002634: The server "{0}" disconnected from this server.

Cause: The remote server may have crashed, been shut down normally or been partitioned from the network.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002635: The server "{0}" connected to this server.

Cause: The remote server may have been booted or a network partition may have been resolved.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002636: Unable to update server "{0}" with local channel information.

Cause: The remote server may have crashed, been shut down normally or been partitioned from the network.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Server

BEA-002637: Failed to register a disconnect listener because of {0}

Cause: This can happen during server startup when the incoming network connection is not suitable for callbacks and the booting server does not yet have a listen port open.

Action: No action is required. The server should eventually be connected properly.
Level: 1

Type: WARNING

Impact: Server

BEA-002638: {0} was issued remotely from {1}.

Cause: Log the host address of the machine that issued the SLC operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002639: ServerRuntime:{0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002640: A request has been received to force a shutdown of the server.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002641: -DserverType is set to an unrecognized value: {0}. The server will start with all services enabled.

Cause: An undefined server type was specified or a typographical error was made.

Action: See the WebLogic Server documentation for valid values for -DserverType.
Level: 1

Type: WARNING

Impact: Server

BEA-002642: {0} not found. The server will start with all services enabled.

Cause: The file was deleted or moved.

Action: Replace the file from the WebLogic Server installation.
Level: 1

Type: WARNING

Impact: Server

BEA-002643: Attempt to read {0}, failed: {1}

Cause: The file has been corrupted or had its permissions changed.

Action: Replace the file with one from the WebLogic Server installation.
Level: 1

Type: WARNING

Impact: Server

BEA-002644: The JAR file {0} being processed as a potential service plug-in could not be read: {1}

Cause: The file may be damaged.

Action: Check the file, replace & and try again.
Level: 1

Type: ERROR

Impact: Server

BEA-002645: The manifest of the JAR file {0} being processed as a potential service plug-in, could not be read: {1}

Cause: The manifest may be corrupted.

Action: Replace the file and retry.
Level: 1

Type: ERROR

Impact: Server

BEA-002646: Unable to load the service plug-in activator class from {0}: {1}

Cause: The plug-in JAR file does not meet the service plug-in requirements.

Action: Check the contents of the JAR file and retry.
Level: 1

Type: ERROR

Impact: Server

BEA-002647: The service plug-in, {1}, was added from {0}.

Cause: The plugin was placed in the domain lib directory.

Action: No action is required. To remove the plug-in, remove it from the domain lib directory.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002648: Could not obtain the relevant ServerRuntimeMBean for server {0}.

Cause: The remote server runtime object for server {0} could not be obtained. This can happen if the server has already been shut down or is otherwise unavailable.

Action: If the server is active when this error occurs, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Server

BEA-002649: A port conflict was detected in the server "{3}" configuration. Both TCP and SDP channels are configured to listen on the same port number and IP address. Channels "{0}" and "{1}" on address "{2}".

Cause: Both TCP and SDP channels are configured to listen on the same port number and IP address.

Action: Ensure that the channels with the same [ListenAddress and ListenPort combinations] either all support SDP or do not support SDP.
Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002650: Unable to schedule reconnection to a disconnected server.

Cause: The default timer manager has stopped. This is normal during server shutdown.

Action: None required if the server is in the process of shutting down.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002651: The process for the server {0} has not completely shut down. This problem should be reported and you may have to kill the process manually.

Cause: The process for the server {0} has not completely shut down.

Action: Kill the process manually.
Level: 1

Type: ERROR

Impact: Server

BEA-002652: The server has no configured channels.

Cause: The server has no configured channels.

Action: Create or define a correct channel configuration.
Level: 1

Type: ERROR

Impact: Server

BEA-002653: The server's administration channel conflicts with the Administration Server's channel.

Cause: The server's administration channel conflicts with the Administration Server's channel.

Action: Check the server channel configuration and fix the conflicts.
Level: 1

Type: ERROR

Impact: Server

BEA-002654: Initialization Failed: {0}

Cause: Initialization Failed: {0}

Action: Review the returned error and take appropriate action to fix it.
Level: 1

Type: ERROR

Impact: Server

BEA-002655: Cannot dynamically create new channel with admin protocol on Managed server {0} while it is running.

Cause: An attempt was made to create a new channel with admin protocol on Managed server {0} while the server is running.

Action: Shut down the Managed Server and then try creating the channel again.
Level: 1

Type: ERROR

Impact: Server

BEA-002656: Cannot dynamically enable or disable adminstration port on Managed Server {0} while it is running.

Cause: An attempt was made to dynamically enable or disable the adminstration port on Managed Server {0} while the server is running.

Action: Shut down the Managed Server and then try enabling or disabling the port again.
Level: 1

Type: ERROR

Impact: Server

BEA-002657: Cannot change MaxOpenSockCount enablement dynamically on Managed Server {0} while it is running.

Cause: An attempt was made to dynamically change MaxOpenSockCount enablement on Managed Server {0} while the server is running.

Action: Shut down the Managed Server and then try to change MaxOpenSockCount enablement again.
Level: 1

Type: ERROR

Impact: Server

BEA-002658: No configured outbound channel for {0}.

Cause: No configured outbound channel for {0}.

Action: Review the returned error and take appropriate action to fix it.
Level: 1

Type: ERROR

Impact: Server

BEA-002659: Only local HostID is supported {0}.

Cause: Only the local HostID is supported {0}

Action: Check and fix the error.
Level: 1

Type: ERROR

Impact: Server

BEA-002660: Failed to parse replication ports for server {0} port range: {1}.

Cause: Parsing replication ports for server {0} port range: {1} failed.

Action: Check and fix the error.
Level: 1

Type: ERROR

Impact: Server

BEA-002661: Server failed to bind to any usable port.

Cause: The server failed to bind to any usable port.

Action: See the preceding log message for details.
Level: 1

Type: ERROR

Impact: Server

BEA-002662: Server was unable to verify whether {0} maps to multiple addresses due to {1}.

Cause: Review the contents of the included error message for the cause.

Action: Review the contents of the included error message to determine the appropriate action to take.
Level: 1

Type: WARNING

Impact: Server

BEA-002663: Uncaught Throwable in processSockets {0}.

Cause: An unhandled Throwable error occurred while processing sockets.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Server

BEA-002664: Failed to start Admin Channel {0}.

Cause: There was an error binding to the Admin Channel port. The port may already be in use.

Action: Check for a port conflict.
Level: 1

Type: ERROR

Impact: Server

BEA-002665: A partition "{0}" appears to use a server resource; channel: {1}.

Cause: The server channel is a shared resource and cannot belong to a partition.

Action: Check whether this is not a Coherence partition. Otherwise configure either port-offset or explicit-port or uri-prefix.
Level: 1

Type: WARNING

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}" with configured minimum threads constraint "{3}" and maximum threads constraint "{4}" 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 WebLogic Server 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: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002921: The name of the Work Manager

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002922: The number of waiting requests in the queue

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002923: The number of requests that have been processed

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002924: An instance of the MinThreadsConstraint for a particular Work Manager

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002925: Completed request count

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002926: Pending requests that are waiting for an available thread

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002927: Number of requests that are currently executing

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002928: Number of requests executed out of turn to satisfy this constraint

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002929: Number of requests that must be executed to satisfy the constraint

Cause: This is an informational message.

Action: No action is required.
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: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002931: Number of requests that must be executed to satisfy the constraint

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002932: An instance of the MaxThreadsConstraint for a particular Work Manager

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002933: Number of requests that are currently executing

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002934: Number of requests that are denied a thread for execution because the constraint is exceeded

Cause: This is an informational message.

Action: No action is required.
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: The request class specified in the context case is not defined.

Action: Ensure that a request class with the same name as was specified in the context case request-class-name is configured.
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002936: maximum thread constraint {0} is reached

Cause: The number of threads assigned to this work manager has reached the configured value in the maximum threads constraint

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002937: The maximum thread constraint {0} is no longer reached.

Cause: The number of threads assigned to this Work Manager has dropped below the configured value in the maximum threads constraint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002938: Global work manager "{0}" created with customized configuration

Cause: The default configuration for a global work manager has been overriden and the work manager is created with a customized configuration

Action: no action needed
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002939: The maximum thread constraint {0} has been reached {1} times for the last {2} seconds.

Cause: The number of threads assigned to this work manager has reached the configured value for the maximum threads constraint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002940: Shutting down work manager "{0}" according to the configured work manager shutdown trigger.

Cause: A work manager is being shut down because the number of stuck threads has reached the configured value in a work manager shutdown trigger.

Action: Monitor the stuck threads to determine the reason why the requests have been taking a long time to process. If resumeWhenUnstuck is true, the work manager will be resumed when there are no more stuck threads for the work manager.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002941: Removed {0} threads from the standby thread pool.

Cause: The server is reducing the number of threads in the standby thread pool either because they are not needed or to reduce overall resource usages of the server.

Action: No action is required as the server auto tunes.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002942: CMM memory level becomes {0}. Setting standby thread pool size to {1}.

Cause: CMM memory level has changed. Standby thread pool size may be adjusted accordingly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002943: Maximum Threads Constraint "{0}" queue for work manager "{1}" reached maximum capacity of {2} elements. Consider setting a larger queue size for the maximum threads constraint.

Cause: The max threads constraint queue is full.

Action: Consider setting a larger queue size for the max threads constraint.
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002944: Maximum Threads Constraint "{0}" queue for work manager "{1}" reached maximum capacity of {2} elements {3} times for the last {4} seconds. Consider setting a larger queue size for the maximum threads constraint.

Cause: The max threads constraint queue is full.

Action: Consider setting a larger queue size for the max threads constraint.
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002945: Unable to perform ThreadLocal cleanup for self-tuning thread pool threads due to error: {0}

Cause: Please see the error in the message for additional information.

Action: Check the error in the message for details of the error and take approriate action if possible. It is also possible that ThreadLocal cleanup is not supported on your platform.
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002946: Partition configuration for partition {0} is not available while loading work manager components for the partition.

Cause: This message can be ignored if partition configuration is available at a later time. This could happen if the partition has just been created or if it has just been migrated from another server.

Action: Check whether there is a log message WLS-002947 in the log file for the same partition. If not, verify if the partition is being created properly.
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002947: Partition configuration for partition {0} is available. Work manager components for the partition have been loaded successfully.

Cause: Partition configuration was not available earlier when trying to load work manager components for the partition. This message indicates that the partition configuration is now available and the work manager components have been loaded successfully.

Action: No action is required. Earlier warning messages WLS-002946 and WLS-002948 for the same partition can now be disregarded.
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002948: Error occurred while loading work manager components for partition {0}: {1}

Cause: Please see the error in the message for additional information.

Action: Check the error in the message for details of the error and take approriate action if possible.
Level: 1

Type: ERROR

Impact: WorkManager

BEA-002949: Work manager components configured for partition {0} is being accessed, but the partition is not deployed to this server.

Cause: This can occur when there are possible inconsistencies in partition or resource group target configuration.

Action: Check the partition or resource group targets configuration.
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002950: Partition "{0}" is configured with a minimum threads constraint cap of {1}, which is less than the sum of all configured minimum threads constraints in the partition.

Cause: The WebLogic administrator has set a cap on the number of threads that will be allocated to this partition for satifying its minimum threads constraints. The configured value is less than the sum of all configured minimum threads constraints configured in this partition.

Action: Request a higher partition minimum threads constraint cap setting from the WebLogic administrator.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002951: An error occurred while trying to create a thread under the global context due to error: {0}. A thread wass created under the context of partition &quot;{1}&quot; instead.

Cause: Check the error in the message for additional information about what might have caused the error.

Action: Resource Consumption Management may not work properly with this error. Contact My Oracle Support and provide them with the logs.
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002952: Partition maximum threads constraint for partition {0} has been reached.

Cause: The number of threads assigned to this partition has reached the configured partition maximum threads constraint value.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002953: The partition maximum threads constraint for partition {0} has been reached {1} times in the last {2} seconds.

Cause: The number of threads assigned to this partition has reached the configured partition maximum threads constraint value.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002954: The Partition Maximum Threads Constraint "{0}" queue reached maximum capacity of {2} elements when trying to add a work entry for work manager "{1}" to the queue. Consider setting a larger queue size for the partition maximum threads constraint.

Cause: The partition maximum threads constraint queue is full.

Action: Consider setting a larger queue size for the partition max threads constraint.
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002955: The Partition Maximum Threads Constraint "{0}" reached maximum capacity of {2} elements {3} times in the last {4} seconds when trying to add work entries for work managers including "{1}". Consider setting a larger queue size for the partition maximum threads constraint.

Cause: The partition maximum threads constraint queue is full.

Action: Consider setting a larger queue size for the partition maximum threads constraint.
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002956: The thread count tuning feature in the self-tuning thread pool has stopped due to {0}.

Cause: The self-tuning timer task has to stop due to an unrecoverable error.

Action: The self-tuning thread pool would continue to process work request, althought without further adjustment of the thread pool size. Consider restarting the server if the thread pool size can no longer handle the work load of the server.
Level: 1

Type: ERROR

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 of the 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 and provide them 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 exists and is 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 restart).
Level: 1

Type: ERROR

Impact: Cluster

BEA-003116: Starting Member Death Detector.

Cause: This is an informational message.

Action: No action is required.
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} failed to resolve during cluster initialization.

Cause: A name service such as DNS is unavailable or unstable.

Action: Check the 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 was 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 an 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 not configured correctly.

Action: Check the leasing table in the database and connection configuration.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003123: Singleton Monitor has detected that the singleton service {0} is in a failed state.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003124: Singleton Monitor has detected that the singleton service {0} has an expired status.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003125: Singleton Monitor has detected that the singleton service {0} has no lease.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003126: {0} will attempt to auto-migrate.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003127: {0} will attempt to restart in place on server {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003128: {0} has been completed to restart in place.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003129: {0} will attempt to auto-migrate from {1} to {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003130: {0} successfully activated on server {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003131: The singleton service {0} has failed with failure state : {1}. Summary of reason Code : {2}

Cause: A critical service has failed, most likely due to an exception.

Action: Depending on the cause, corrective action must be taken to resolve the failure. If the problem still persists, contact My Oracle Support for further analysis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003132: An 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 an EJB, the EJB container determined that 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: Cluster

BEA-003133: An EJB is configured to use the clustered EJB timer implementation but the data-source-for-job-scheduler attribute is not configured in partition "{0}".

Cause: While deploying this EJB, the EJB container determined that the data-source-for-job-scheduler partition 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 partition.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003134: An EJB is configured to use the clustered EJB Timer implementation but this server is not part of a cluster.

Cause: You cannot 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: Cluster

BEA-003135: Job Scheduler service was not started for this partition because the data source for the job scheduler is not configured for this partition.

Cause: This is an informational message.

Action: No action is required unless the job scheduler service is needed in this partition, in which case you can configure a data source for the job scheduler for this partition and restart the partition.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003136: Job scheduler service was not started for this partition because this server does not belong to a cluster.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003137: Server in cluster {0} was unable to bind MulticastSocket to address {0}. Will bind to IP_ANY instead.

Cause: This was caused by an invalid multicast IP address.

Action: Configure the cluster to use a valid multicast IPv4 or IPv6 address.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003138: Synchronized {1} from server {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003139: AssertionError is raised on installing ServiceOffer from remote node : {0}

Cause: Internal data structure is corrupted.

Action: If there is no other problems, no action is required. Corrupted offer will be simply ignored.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003140: Partition {0} from server {1} {2} for cluster view {3}

Cause: The partition has been started/stopped on a particular server in the cluster

Action: No action is required
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003141: Thread {0} attempted a re-entrant call to the WLS Replication Service while actively replicating session state to a secondary server.

Cause: During replication of the application''s session state, an attempt was made by the same thread to access the same session instance that is actively being serialized..

Action: None
Level: 1

Type: WARNING

Impact: Cluster

BEA-003142: An exception occurred while ensuring replica {0} replicated: {1}

Cause: An exception occurred while ensuring replica {0} replicated: {1}

Action: Please check the exception for the exact error message.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003143: An exception occurred while locally cleaning up replica {0} for replication key {1}: {2}

Cause: An exception occurred while locally cleaning up replica {0} for replication key {1}: {2}

Action: Please check the exception for the exact error message.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003145: An exception occurred while starting TimerMaster for {0}: {1}

Cause: An exception occurred while starting TimerMaster service for job scheduler for {0}. The exception is {1}

Action: Please check the exception for the cause and take appropriate action.
Level: 1

Type: WARNING

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-003800: Could not parse the user random seed property whose value is {0}. Using seed {1}

Cause: The seed used to randomize startup services was not parseable. The seed is given to the server with the com.oracle.weblogic.debug.RandomizeServerServices.seed system property.

Action: Check the value of the com.oracle.weblogic.debug.RandomizeServerServices.seed property given to the server, and make sure it can be parsed into a valid long value
Level: 1

Type: WARNING

Impact: WebLogicServer

BEA-003801: Could not read server service randomizer file {0}. The seed used in this run is randomSeed

Cause: The seed file used to randomize startup services was not parseable. The name of the seed file is given to the server with the com.oracle.weblogic.debug.RandomizeServerServices.filename system property.

Action: Check the value of the com.oracle.weblogic.debug.RandomizeServerServices.filename property given to the server, and make sure it points to a file that contains one line that can be parsed into a long which should be used for the random seed
Level: 1

Type: WARNING

Impact: WebLogicServer

BEA-003802: The order in which the server services are started has been randomized with seed {0}{1}

Cause: The server service randomizer was used to randomize server services with the given seed

Action: No action necessary
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-003803: Could not write server service randomizer file {0}. The seed used in this run is {1}

Cause: When using the service randomizer the system attempted to write the seed used to a file for later use, but the system could not write the file

Action: Ensure that the randomizer file is in a directory where the system can write and that there is enough disk space in that file system
Level: 1

Type: WARNING

Impact: WebLogicServer

BEA-003804: The randomizer file with location {0} is not readable. The seed used in this run is {1}

Cause: The randomizer file at the given location is not readable

Action: Ensure that the randomizer file is readable by the system
Level: 1

Type: WARNING

Impact: WebLogicServer

BEA-003805: The data found in randomizer file with location {0} is not parseable into a long. The seed used in this run is {1}

Cause: The randomizer file at the given location has bad data in it

Action: Ensure that the randomizer file has one line that can be parsed into a long value
Level: 1

Type: WARNING

Impact: WebLogicServer

BEA-004501: Bootstrap request was rejected from server {0} of cluster {1}.

Cause: Server configuration parameters, such as listen-address and port, are duplicated between servers in different clusters.

Action: Change server configuration parameters of the servers in the domain.
Level: 1

Type: WARNING

Impact: ConsensusLeasing

BEA-004502: Exception occurred during unicast connection bootstrapping: {0}

Cause: See displayed exception.

Action: Report this error to My Oracle Support.
Level: 1

Type: WARNING

Impact: ConsensusLeasing

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: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010008: EJB Deploying file: {0}.

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010009: EJB deployed EJB with JNDI name {0}.

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010011: Exception looking up current transaction: {0}

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010012: Exception looking up current transaction: {0}

Cause: See the message body.

Action: No action required.
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: See the message body.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010032: Exception during ejbActivate(): {0}

Cause: See the message body.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010033: Exception from ejbLoad: {0}

Cause: See the message body.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010034: Exception from ejbStore: {0}.

Cause: See the message body.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010036: Exception from ejbStore: {0}.

Cause: See the message body.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010038: Exception from __WL_superEjbLoad: {0}.

Cause: See the message body.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010039: Exception in ejbStore: {0}.

Cause: See the message body.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010040: Exception in ejbStore: {0}.

Cause: See the message body.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010043: Exception in ejbActivate: {0}.

Cause: See the message body.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010044: Exception trying to resume transaction: {0}.

Cause: See the message body.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010045: Exception in afterBegin: {0}.

Cause: See the message body.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010046: Exception in beforeCompletion: {0}.

Cause: See the message body.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010047: Exception during setRollbackOnly: {0}.

Cause: See the message body.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010048: Exception in afterCompletion: {0}.

Cause: See the message body.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010049: EJB exception in method: {0}: {1}.

Cause: See the message body.

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: See the message body.

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: See the message body.

Action: No action required.
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: See the message body.

Action: No action required.
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: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010067: Exception during ejbRemove: {0}

Cause: See the message body.

Action: No action required.
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: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010076: Client-jar {0} created.

Cause: See the message body.

Action: No action required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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 connection 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: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010208: ddl-file {0} created.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010209: ddl-file {0} could not be deleted.

Cause: See the message body.

Action: Check the file permissions.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010210: Unable to write to ddl-file {0}.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010211: Unable to alter the table, as the primary key has changed.

Cause: See the message body.

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, because {1}. The transaction details are: {2}.

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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: No action is required.
Level: 1

Type: WARNING

Impact: EJB

BEA-010234: Failed to unbind {0} from JNDI tree due to {1}.

Cause: See the message body.

Action: If the application is redeployed, restart the target cluster/server on which the application has been deployed. Please report the issue to My Oracle Support with relevant details.
Level: 1

Type: WARNING

Impact: EJB

BEA-010235: The Message-Driven EJB {0} has connected or reconnected to the JCA resource adapter {1}.

Cause: The Message-Driven EJB has been re-associated with the JCA resource adapter.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010236: The Message-Driven EJB {0} (status: {1}) has not been associated with the JCA resource adapter, so trying suspending it actually did nothing.

Cause: The Message-Driven EJB has not been associated with the JCA resource adapter, so trying suspending it actually did nothing.

Action: No action is required.
Level: 1

Type: WARNING

Impact: EJB

BEA-010237: The Message-Driven Bean {0} was configured to use a JMS Topic, does not require transactions, and uses a non-WebLogic JMS provider. Only one thread will be used to receive and process all messages.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

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: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011079: An exception occurred while stopping the freepool idle timeout timer for ejb: {0}, {1}.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011080: An exception occurred while starting the Cache idle timeout timer for cache: {0}, {1}.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011081: An exception occurred while stopping the Cache idle timeout timer for cache: {0}, {1}.

Cause: See the message body.

Action: No action is required.
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-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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

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-011151: Unable to determine the {3} to use for Message Driven Bean {0}. Activation Configuration of Message Driven Bean {0} includes conflicting values specified using {1} and {2}. Consider dropping {2} and specifying the intended {3} using property {1}.

Cause: See the error message body.

Action: See the error message body.
Level: 1

Type: ERROR

Impact: EJB

BEA-011152: ConnectionFactoryResourceLink and DestinationResourceLink configuration attributes cannot be mixed with any of the following settings: DestinationJNDIName, InitialContextFactory, ProviderUrl, ConnectionFactoryJNDIName. Ensure that they are mutually exclusive for ejb {0}.

Cause: Conflicting configuration attributes were specified.

Action: Ensure that these configuration attributes are mutually exclusive.
Level: 1

Type: ERROR

Impact: EJB

BEA-011153: EJB {0} has a redundant Activation configuration, property {1} will be used, property {2} can be dropped.

Cause: There is a redundant configuration property.

Action: See the message body.
Level: 1

Type: WARNING

Impact: EJB

BEA-011154: The EJB {0} contains an illegal value for the activation config property TopicMessagePartitionMode. The specified value is {1} but the legal values are Isolated or Shared.

Cause: See the error message body.

Action: Correct the activation config property.
Level: 1

Type: ERROR

Impact: EJB

BEA-011155: Access is denied on a nonexistent method.

Cause: The specified method is not existing.

Action: Make sure the method is existing.
Level: 1

Type: ERROR

Impact: EJB

BEA-011156: Non numeric value was configured for activation config property {0}.

Cause: Non numeric value was configured for activation config property {0}.

Action: Correct activation config property setting.
Level: 1

Type: ERROR

Impact: EJB

BEA-011223: Cannot invoke stateful callback on {0}.

Cause: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011226: Error during {0}. Could not get connection: {1} {2}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011227: Error during finder {0}. Exception while preparing query: {1} {2} {3}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011232: Error during finder {0}. Exception while setting parameters for query {1} {2} {3}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011233: Error during finder {0}. Exception while executing query {1} {2}

Cause: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011237: A stored procedure or function is used by {0}, but no SqlShape is specified.

Cause: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011239: Query-caching is not supported for read-write beans.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011240: Error obtaining nativeQuery: {0}, {1}

Cause: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011242: Internal Error: Extended Persistence Context has been closed!

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011243: attempt at illegal state transaction from {0} to {1}

Cause: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011245: The EJB {0} is not an EJB3.0 bean.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011246: The EJB {0} does not declare a {1} home interface.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011247: The EJB {0} does not implement the business interface {1}.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011248: The bean has not been invoked through a business interface.

Cause: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011256: Single expiration timers cannot be cancelled from within ejbTimeout.

Cause: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011258: It is illegal to invoke Timer methods in ejbActivate or a PostActivate method.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011259: It is illegal to invoke Timer methods in ejbPassivate or a PrePassivate method.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011260: It is illegal to invoke Timer methods during a dependency injection.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011261: Invocation timed out. Timer is busy.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011262: Error cancelling timer

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011263: EjbJarBean is not set yet.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011264: Method {0} is marked TX_NEVER, but was called within a transaction.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011265: Unexpected exception in afterDelivery(): {0}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011266: An attempt was made to execute getDatabaseProductName using a non-WebLogic EntityManager.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011267: Error calling getDatabaseProductName: {0}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011268: An attempt was made to execute nativeQuery on query {0}, using a non-WebLogic EntityManager.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011269: Error obtaining nativeQuery: {0}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011270: Error preparing query: {0}

Cause: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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.
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: Check for other log messages that give more information about the failure.
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: See the message body.

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: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-014022: {0} is bound with JNDI name {1}.

Cause: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015002: Unable to load class {0} in Jar {1} : {2}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015003: Unable to create virual Jar {0} : {1}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015004: The super class {0} of session bean class {1} is also a session bean class.

Cause: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015007: No ejbCreate method was found for init method {0} in bean {1}.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015008: No matching create method for @Init method {0} in bean {1}.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015009: Could not load interceptor class {0}: {1}.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015010: In bean {0}, there are multiple method permission annotations for method {1}, which is illegal.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015011: There are multiple method permission annotations for class {0}, which is illegal.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015012: Unable to load interface class {0}: {1}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015013: Bean class {0} does not implement interface method {1}.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015014: ServiceEndpoint class {0} was specified but cannot be found.

Cause: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message body.

Action: No action is required.
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: See the message detail.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015044: @JNDIName is specified on multiple classes for the same business interface {0} but the value is different. Class: {1}; Class: {2}.

Cause: @JNDIName is specified on multiple classes for the same business interface {0} but the value is different. Class: {1}; Class: {2}.

Action: Remove @JNDIName from either {1} or {2}.
Level: 1

Type: ERROR

Impact: EJB

BEA-015045: @JNDIName on the bean implementation class does not provide the class of the client view, but more than one client view exists. Class: {0}.

Cause: @JNDIName on the bean implementation class does not provide the class of the client view, but more than one client view exists. Class: {0}.

Action: Remove @JNDIName from {0} or provide the class name of each client view.
Level: 1

Type: ERROR

Impact: EJB

BEA-015046: Illegal operation, context data is not supported for the Entity Bean.

Cause: An illegal operation has occurred, context data is not supported for the Entity Bean.

Action: Remove the retrieval operation for the Entity Bean's context data.
Level: 1

Type: ERROR

Impact: EJB

BEA-015047: Unable to bind portable JNDI name {0}.

Cause: The portable JNDI name could not be bound. See the exception for the cause.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-015048: This EJB class does not have a timeout method. To use TimerService, the bean class must implement javax.ejb.TimedObject or have a method that is annotated with @Timeout.

Cause: You are trying to create a timer but the corresponding EJB does not have a timeout method.

Action: Correct the EJB class and add a timeout method.
Level: 1

Type: ERROR

Impact: EJB

BEA-015049: Interface {0} implemented by EJB class {1} will be treated as a local business interface, because all implemented interfaces by the bean class should be local business interfaces by default. Note that this interface extends java.rmi.Remote exceptionally.

Cause: Interface {0} defaults to be a local business interface but it extends java.rmi.Remote.

Action: No action is required if the default works for you. If, however, you do want to use {0} as a remote business interface, specify it explicitly using @Remote annoation or deployment descriptor.
Level: 1

Type: WARNING

Impact: EJB

BEA-015050: {2} beans with bean-managed transactions must commit or roll back their transactions before completing a lifecycle callback interceptor method. The method {0} of EJB {1} either returned or generated an exception without properly completing a transaction.

Cause: A transaction started by the {2} bean lifecycle callback 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-015051: The following exception occured in {1} processing for stateful session bean {0}: {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015052: Cannot find proper lifecycle callback method {0} in bean class {1} of EJB {2}.

Cause: A lifecycle callback method in bean class must have the signature: "void <METHOD>()"

Action: Check the bean code to have the correct signature of the lifecycle callback method.
Level: 1

Type: ERROR

Impact: EJB

BEA-015054: Error deploying EJB {0}. The JMS connection factory referenced by the JNDI name {0} is a PooledConnectionFactory.

Cause: The JMS connection factory referenced by the JNDI name {0} is a PooledConnectionFactory. For example, the specified JNDI name may be the JNDI name of a resource reference.

Action: Specify a JMS connection factory JNDI name that, when looked up, does not return a PooledConnectionFactory. For example, specify a JMS connection factory JNDI name that is not the JNDI name of a resource reference.
Level: 1

Type: ERROR

Impact: EJB

BEA-015055: Error occurred during full state replication for replica {1} of stateful session bean {0} of resource group {2}: {3}

Cause: The exception was: {3}

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-015056: Unregistered replicas for stateful session bean {0}

Cause: Unregistered replicas for stateful session bean {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015057: An error occurred while attempting to process a message inside a Message-Driven Bean: {0} Exception is : {1}. {2} such exceptions were suppressed in logging.

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-015060: Activation exception for stateful session ben {0}: {1}.

Cause: An exception occurred while reading or processing the state of the bean.

Action: Please check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-015061: Exception reading the replicated state of stateful session bean {0}: {1}.

Cause: An exception occurred on reading the replicated state of stateful session bean, for example an application upgrade may have introduced a Java serialization incompatibility on the bean state between old and new versions.

Action: Please check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-015062: Exception on creating replicated stateful session bean {0}: {1}.

Cause: An exception occurred on creating replicated stateful session bean

Action: Please check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-015063: {0} following exceptions were suppressed in logging during a message processing inside Message-Driven Bean. The last occurrence of this exception has a timestamp {1}: {2} Exception is : {3}.

Cause: This can happen if the onMessage method of the MDB consecutively throws exceptions.

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

Impact: EJB

BEA-015064: An exception occurred in replication for stateful EJB {0} on {1} partition shutting down: {2}

Cause: An exception occurred in replication for stateful EJB {0} on {1} partition shutting down: {2}

Action: Please check the exception for the exact error message.
Level: 1

Type: WARNING

Impact: EJB

BEA-015065: An error occurred on check server or partition state during deactivation of stateful EJB {0}: {1}

Cause: An error occurred on check server or partition state during deactivation of stateful EJB {0}: {1}

Action: Please check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-015066: An exception occurred while cleaning up replicas states locally for stateful EJB {0} on {1} partition shutting down: {2}

Cause: An exception occurred while cleaning up replicas states locally for stateful EJB {0} on {1} partition shutting down: {2}

Action: Please check the exception for the exact error message.
Level: 1

Type: WARNING

Impact: EJB

BEA-015067: Ensure bean states are replicated for stateful EJB {0} on {1} partition shutting down

Cause: see message detail

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015068: Local replicas clean up for stateful EJB {0} on {1} partition shutting down

Cause: see message detail

Action: No action required
Level: 1

Type: NOTIFICATION

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 Java EE application (an EAR file), then you must add the sub-deployment stanza to the subdeployment that represents this JMS module in the Java EE application. You do not necessarily have to target the subdeployment yet. Simply adding the subdeployment with no targets will remove this warning. However, if you wish for this entity to exist somewhere in your domain you must target the sub-deployment.
Level: 1

Type: WARNING

Impact: JMS

BEA-040457: The Template named "{1}" element of Distributed Destination "{0}" is not supported and hence ignored. Please consider using a Uniform Distributed Destination.

Cause: An unsupported attribute JMSTemplate is used in a Distributed Destination.

Action: Use a Uniform Distributed Destination instead.
Level: 1

Type: WARNING

Impact: JMS

BEA-040458: Unable to unprepare {0} in module {1} due to {2}.

Cause: The prepared entity could not unprepare itself in a failure case.

Action: Refer to the available exception for more information.
Level: 1

Type: WARNING

Impact: JMS

BEA-040459: Unable to deactivate {0} in module {1} due to {2}.

Cause: The activated entity could not deactivate itself in a failure case.

Action: Refer to the available exception for more information.
Level: 1

Type: WARNING

Impact: JMS

BEA-040460: Unable to close the JMS component of module {0} due to {1}.

Cause: The JMS component could not close itself.

Action: Refer to the available exception for more information.
Level: 1

Type: WARNING

Impact: JMS

BEA-040461: Unable to deactivate {0} in module {1} due to {2}.

Cause: The activated entity could not deactivate itself in a failure case.

Action: Refer to the available exception for more information.
Level: 1

Type: WARNING

Impact: JMS

BEA-040464: Unable to destroy {0} in module {1} due to {2}.

Cause: The initialized entity could not destroy itself in a failure case.

Action: More information may be available from the exception.
Level: 1

Type: WARNING

Impact: JMS

BEA-040467: Unable to deactivate {0} in module {1} due to {2}.

Cause: The activated entity could not deactivate itself in a failure case.

Action: More information may be available from the exception.
Level: 1

Type: WARNING

Impact: JMS

BEA-040470: Unable to deactivate {0} in module {1} due to {2}.

Cause: The activated entity could not deactivate itself during dynamic deletion.

Action: More information may be available from the exception.
Level: 1

Type: WARNING

Impact: JMS

BEA-040475: The destination {0} does not have an associated quota object. The setting of bytesMaximum to {1} will have no effect.

Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases, a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.

Action: Please consider removing this destination from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1

Type: WARNING

Impact: JMS

BEA-040476: The destination {0} does not have an associated quota object. The setting of messagesMaximum to {1} will have no effect.

Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.

Action: Please consider removing this destination from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1

Type: WARNING

Impact: JMS

BEA-040477: An error occurred while unbinding a remote JNDI object from local JNDI name "{0}". The exception encountered was {1}.

Cause: There may be an error in the JNDI subsystem. See the exception for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: JMS

BEA-040478: The JMS subsystem could not deploy or undeploy the default JMS connection factories due to {0}.

Cause: There may be an error in the JNDI subsystem. See the exception for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: JMS

BEA-040479: The system failed to roll back an added connection consumer of name {0}. The exception received was {1}.

Cause: See the exception for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: JMS

BEA-040480: The system failed to remove a connection consumer of name {0}. The exception received was {1}.

Cause: See the exception for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: JMS

BEA-040490: {0} {1} has a conflicting name attribute value, which is now changed to have a unique name with its JMSServer name. The new destination-name attribute now holds the original name value.

Cause: A name conflict has been detected during upgrade for JMS destinations, maybe because in WebLogic Server versions prior to 9.2, more than one destination was allowed to have the same name, as long as the destinations belonged to different JMS servers.

Action: Ensure that destinations are created with their name decorated with the target JMS server name to avoid conflict.
Level: 1

Type: WARNING

Impact: JMS

BEA-040491: A {0} {1} with multiple targets has been split into multiple deployments one for each unique target.

Cause: A JMS Deployment found with multiple unique targets configured.

Action: In WebLogic Server versions prior to 9.2, both JMSConnectionFactory and ForeignJMSServer were allowed to be targeted to more than one server, cluster, or both. During upgrade of this configuration to WebLogic Server 9.2, these configuration entities are split into more than one entity, one for each unique target.
Level: 1

Type: WARNING

Impact: JMS

BEA-040494: An error occurred while shutting down the JMS server {0}: {1}.

Cause: See the detail message.

Action: The server should still shut down normally. No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040496: The template {0} does not have an associated quota object. The setting of bytesMaximum to {1} will have no effect.

Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.

Action: Please consider removing this template from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1

Type: WARNING

Impact: JMS

BEA-040497: The template {0} does not have an associated quota object. The setting of MessagesMaximum to {1} will have no effect.

Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.

Action: Consider removing this template from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1

Type: WARNING

Impact: JMS

BEA-040498: An error occurred while forwarding a message for distributed destination member {0}: {1}

Cause: There may be a temporary network problem, or one of the members of the cluster may be unavailable.

Action: See the detail message.
Level: 1

Type: WARNING

Impact: JMS

BEA-040499: An error occurred while pushing messages to a JMS client: {0}

Cause: There may be a network failure.

Action: The JMS protocol will recover automatically from such a problem eventually. Check for networking issues or crashed clients.
Level: 1

Type: WARNING

Impact: JMS

BEA-040500: Unable to deactivate entity "{0}" in module "{1}" due to {2}.

Cause: The activated entity could not rollback the proposed targeting change.

Action: More information may be available from the exception.
Level: 1

Type: WARNING

Impact: JMS

BEA-040501: Unable to roll back targeting change of the entity "{0}" in module "{1}" due to {2}.

Cause: The changed entity could not roll back in a failure case.

Action: More information may be available from the exception.
Level: 1

Type: WARNING

Impact: JMS

BEA-040502: While attempting to change the targeting of JMS module "{0}", an error occurred while activating the change. The exception returned is: {1}

Cause: The JMS module failed to activate a prepared change during a targeting update.

Action: More information may be available from the exception.
Level: 1

Type: ERROR

Impact: JMS

BEA-040503: The delivery mode override value of destination "{0}" hosted on JMS server "{1}" has been changed from {2} to {3}.

Cause: During the upgrade process, a configuration was detected that would force all messages through the given destination to be non-persistent. Therefore, the upgrade process made that override explicit.

Action: Review your application code and configuration. If you need a behavior other than the one that the upgrade process chose, you can modify the resulting configuration using the DeliveryMode parameter of the OverridesParams of the destination, or with the HasStore or AllowsPersistentDowngrade parameters of the JMS server on which the destination is targeted.
Level: 1

Type: WARNING

Impact: JMS

BEA-040504: While attempting to add an entity with name "{0}", an error occurred while trying to convert the old style entity to the new style entity. The error was "{1}".

Cause: See the description of the exception that occurred for more information on the cause of this failure.

Action: Take appropriate action based on the determined cause.
Level: 1

Type: WARNING

Impact: JMS

BEA-040505: The JMS module named "{0}" inside application "{1}" does not have a sub-deployment stanza named "{0}". Without such a stanza, no entities inside the module will be deployed, since the subdeployments inside of the sub-deployment stanza named "{0}" control where JMS entities inside this module are targeted.

Cause: When a JMS module is inside an EAR file, the targeting information for entities inside that module are nested within a sub-deployment named after the name of the JMS module found in the weblogic-application.xml file of the EAR file. If no sub-deployment exists with the name of the JMS module, then no targeted entities inside the module will become available. This is usually an oversight on the part of the administrator.

Action: Add a sub-deployment stanza with the name of the JMS module as specified in the weblogic-application.xml file to the app-deployment stanza. Nested inside that sub-deployment, you can target the entities in the module as you normally would.
Level: 1

Type: WARNING

Impact: JMS

BEA-040506: The JMS store-and-forward (SAF) forwarder has successfully connected to the remote destination "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040507: The JMS store-and-forward (SAF) forwarder failed to connect to the remote destination "{0}", because of {1}.

Cause: This is either due to a configuration error, a network failure, or the remote destination being temporarily unavailable.

Action: Check the configuration, network connection, or remote destination.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040508: BridgeDestinationMBean has been deprecated. The BridgeDestination "{0}" has been replaced in the configuration with a JMSBridgeDestination with the same name.

Cause: A deprecated MBean is being replaced in the configuration.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040509: Failed to ${1} JMS Server "{0}" because the earlier attempt to ${2} was failed.

Cause: This error occurred during deployment of the JMS server.

Action: Fix any deployment errors related to this JMS server.
Level: 1

Type: ERROR

Impact: JMS

BEA-040510: While attempting to rename a connection factory named "{0}", an error occurred while attempting to establish a JNDI listener. The cause was {1}.

Cause: There was an error while attempting to establish a JNDI listener. The description of the cause may provide more information about the true cause of the error.

Action: The cause of this problem may give an indication of the source of this problem. If this problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMS

BEA-040511: The system is waiting to unbind connection factory "{0}". An attempt is being made to change the JNDI name of this connection factory from "{1}" to "{2}".

Cause: An attempt is being made to unbind a connection factory from a JNDI name in order to dynamically change the JNDI from one name to another. This message will repeat every twenty seconds for five minutes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040512: An attempt is being made to change the JNDI name of connection factory "{0}" from "{1}" to "{2}". The system has waited to unbind "{1}" for five minutes. The new JNDI name "{2}" may or may not be bound properly.

Cause: The connection factory was not fully unbound after five minutes. Some error may have occurred while attempting to unbind this connection factory.

Action: In order to maintain the integrity of the connection factory it is recommended you untarget and retarget the connection factory that failed. Otherwise, the connection factory is in an indeterminate state.
Level: 1

Type: ERROR

Impact: JMS

BEA-040513: While attempting to rename a connection factory named "{0}", an error occurred while attempting to remove a JNDI listener. The cause was {1}.

Cause: There was an error while attempting to remove a JNDI listener. The description of the cause may provide more information about the true cause of the error.

Action: The cause of this problem may give an indication of the source of this problem and the action to take. If this problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JMS

BEA-040514: While attempting to rename a connection factory named "{0}" an error occurred in the JNDI listener. The error was {1}

Cause: While attempting to dynamically change the JNDI name of a connection factory, a JNDI error occurred. The error itself will tell more about the cause of this failure.

Action: The cause of this problem may give an indication of the source of this problem and the action to take. If this problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JMS

BEA-040515: A failured occured while attempting to unregister an InterceptionPoint, {0}.

Cause: An exceptoin coccurred while attempting to unregister an InterceptionPoint. The error will provide more details about the cause of this failure.

Action: The cause of this problem may give an indication of the source of this problem. If this problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JMS

BEA-040520: One or more Weighted Distributed Destination (WDD) resources were detected in JMS configuration module "{1}": {0}. This resource type was deprecated as of WebLogic Server 10.3.4.0. Consider using a Uniform Distributed Destination (UDD) instead. If you want to suppress this warning, set system property "weblogic.jms.WDD.SuppressDeprecationWarnings" to true when starting each WebLogic Server instance.

Cause: Deprecated resource was used.

Action: Use the Uniform Distributed Destination instead.
Level: 1

Type: WARNING

Impact: JMS

BEA-040521: The JMS resource "{0}" that you are trying to create in module "{1}" is a Weighted Distributed Destination (WDD). This resource type was deprecated as of WebLogic Server 10.3.4.0. Consider using a Uniform Distributed Destination (UDD) instead. If you want to suppress this warning, set system property "weblogic.jms.WDD.SuppressDeprecationWarnings" to true when starting each WebLogic Server instance.

Cause: A deprecated resource is trying to create.

Action: Use the Uniform Distributed Destination instead.
Level: 1

Type: WARNING

Impact: JMS

BEA-040522: Failed to update distributed destination membership in a multi-domain environment: {0}.

Cause: Cross domain security configuration is not properly set up.

Action: Check the security configuration, especially the cross-domain security configuration if the cross domain security feature is enabled. Contact My Oracle support if the problem persists.
Level: 1

Type: WARNING

Impact: JMS

BEA-040523: One or more properties - "{4}", specified by {3} with JNDI name {1} defined in the application {0} deployed to {2} are not recognized by WebLogic Server and are ignored. To change the log level of this message, see the {5} property of {3}.

Cause: One or more properties set for a {3} are not recognized by WebLogic Server.

Action: If the intent of the application is to specify properties recognized by WebLogic Server, check for a misspelling of the property name(s).
Level: 1

Type: WARNING

Impact: JMS

BEA-040524: The subdeployment "{0}" used by an entity of type {1} with name "{2}" in JMS module "{3}" defined in {4}, has no target specified in the configuration repository (config.xml). A subdeployment without a valid target will not be deployed.

Cause: The subdeployment "{0}" is not targeted, so the entity was ignored by the JMS module defined in {4}.

Action: Specifiy a valid target for the subdeployment "{0}".
Level: 1

Type: WARNING

Impact: JMS

BEA-040525: Shut down JMS connections for resource group {0}.

Cause: JMS connections for a resource group were shut down because the resource group has been shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040526: JMS Module "{3}" deployed to {4} defines an entity of type {1} with name "{2}" with default targeting enabled. There is no JMS server having a persistent store with distribution policy "{0}" available in {4} to host the entity. The destination "{2}" will be hosted when a JMS server having a persistent store with distribution policy "{0}" is configured in {4}.

Cause: For hosting the entity of type "{1}" with name "{2}" , with default targeting enabled defined in the JMS module "{3}" deployed to {4}, there should be exactly one JMS server with persistent store having distribution policy "{0}" defined in {4}. However, no candidate JMS server was found to host that entity.

Action: Create a JMS server in {4} with a persistent store having the distribution policy set to "{0}".
Level: 1

Type: WARNING

Impact: JMS

BEA-040527: JMS Module "{2}" deployed to {3} defines an entity of type {0} with name "{1}" with default targeting enabled. There is no SAF agent having a persistent store with distribution policy "Distributed" available in {3} to host the entity. The destination "{1}" will be hosted when a SAF agent having a persistent store with distribution policy "Distributed" is configured in {3}.

Cause: For hosting the entity of type "{0}" with name "{1}" , with default targeting enabled defined in the JMS module "{2}" deployed to {3}, there should be exactly one SAF agent with persistent store having distribution policy "Distributed" defined in {3}. However, no candidate SAF agent was found to host that entity.

Action: Create an SAF agent in {3} with a persistent store having the distribution policy set to "Distributed".
Level: 1

Type: WARNING

Impact: JMS

BEA-040528: Start JMS service for partition [{0}]

Cause: The partition is starting up.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040529: Shut down JMS service for partition [{0}].

Cause: The partition is shutting down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040530: JMS Destination Definition with JNDI name "{0}" defined in the application "{1}" deployed to {2} will not be hosted as there is no JMS Server having a persistent store with distribution policy "Distributed" available.

Cause: For hosting the JMS destination definition with JNDI name "{0}" defined in the application "{1}" there must be at least one JMS server having a persistent store with distribution policy "Distributed" However, no JMS server is available in {2} to host the JMS destination definition.

Action: Create a JMS server in {2} with a persistent store having a distribution policy set to "Distributed".
Level: 1

Type: WARNING

Impact: JMS

BEA-040531: One or more JMS Servers - "{0}" were not considered to host the entity {3} deployed to "{2} " as they do not have a persistence store with distribution policy set to "{1}".

Cause: The JMS Servers do not have a persistent store with a persistent store set to the indicated value.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040532: One or more JMS Servers - "{0}" were not considered to host the destination defined by JMS Destination Definition with JNDI name "{2}" defined in the application "{3}" deployed to {4} as they do not have a persistence store with distribution policy set to "{1}".

Cause: The JMS servers do not have a persistent store with the distribution policy set to the indicated value.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040533: The application "{0}" uses a JMS Destination Definition to create a WebLogic JMS {4} with JNDI name "{1}", its generated configuration name is "{3}" and its generated JMS module name is "{2}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

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} contains a standalone queue, topic or quota that can only be targeted to a single non-clustered JMS Server or to a clustered JMS Server with Singleton distribution-policy.

Cause: The SubDeploymentMBean of the given name cannot be targeted to anything but a single non-clustered JMS Server or to a clustered JMS Server with Singleton distribution-policy.

Action: Modify the target of the subdeployment so that it contains only a single non-clustered JMS Server or a clustered JMS Server with Singleton distribution-policy.
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-045119: The current JMS message is a Unit-of-Order (UOO) or Unit-of-Work (UOW) message that cannot be sent to the distributed destination (DD) "{0}". This DD has its UnitOfOrderRouting attribute configured to "Hash", which does not support UOO/UOW messages when either a DD is configured in a Resource Group scope, or a DD is hosted on a JMS server that is targeted to a cluster. To fix this issue: change the UnitOfOrderRouting attribute to "PathService" and ensure a Path Service is configured and running in the current scope.

Cause: A Unit-of-Order (UOO) or Unit-of-Work (UOW) JMS message cannot be sent to distributed destinations that have at least one member hosted by a cluster-targeted JMS Server, but the specified Distributed destination has one or more of its members hosted by a cluster-targeted JMS server. The current JMS message is a Unit-of-Order (UOO) or Unit-of-Work (UOW) message that cannot be sent to the distributed destination (DD). This DD has its UnitOfOrderRouting attribute configured to "Hash", which does not support UOO/UOW messages when either a DD is configured in a Resource Group scope, or a DD is hosted on a JMS server that is targeted to a cluster.

Action: To fix this issue: change the UnitOfOrderRouting attribute to "PathService" and ensure a Path Service is configured and running in the current scope.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045120: An injected JMSContext cannot be used when there is neither a transaction nor a valid request scope.

Cause: An injected JMSContext was used when there is neither a transaction or a valid request scope.

Action: Change your application so that it only uses an injected JMSContext when there is either a transaction or a valid request scope.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045121: Exception encountered whilst injecting a JMSContext: unable to create InitialContext: {0}

Cause: An exception was encountered whilst injecting a JMSContext: unable to create InitialContext: {0}

Action: Review the cause of the exception, fix the problem and try again.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045122: Error injecting JMSContext: unable to lookup connection factory with lookup name {0}. The exception was {1}.

Cause: An error was encountered whilst injecting a JMSContext: unable to lookup connection factory with lookup name {0}. The exception was {1}.

Action: Review the cause of the exception, fix the problem and try again.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045123: The method {0} is not permitted on a container-managed (injected) JMSContext.

Cause: An attempt was made to call the method {0} on a container-managed (injected) JMSContext. The use of this method is not permitted.

Action: Amend the application so that it does not call methods that are not permitted on a container-managed (injected) JMSContext. Then try again.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045124: A session mode of SESSION_TRANSACTED is not permitted on a container-managed (injected) JMSContext.

Cause: An attempt was made to use a container-managed (injected) JMSContext which specified a session mode of SESSION_TRANSACTED. This session mode is not permitted because the JMS specification forbids the use of the commit method on a container-managed (injected) JMSContext.

Action: Amend the code which declares the injected JMSContext to use a different value of JMSSessionMode, or omit the JMSSessionMode annotation.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045125: WebLogic JMS extension methods are only available on injected JMSContext objects if the JMS provider being used is WebLogic JMS

Cause: The application injected a JMSContext for a foreign JMS provider, cast it to weblogic.jms.client.JMSContextInternal and called a method defined on that interface.

Action: Amend the code to remove the cast to weblogic.jms.client.JMSContextInternal and the call to any methods on that interface.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045126: WebLogic JMS extension methods are only available on injected JMSContext objects if the JMS provider being used is WebLogic JMS

Cause: The application injected a JMSContext for a foreign JMS provider, cast it to weblogic.jms.extensions.WLJMSContext and called a method defined on that interface.

Action: Amend the code to remove the cast to weblogic.jms.extensions.WLJMSContext and the call to any methods on that interface.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045127: The application "{1}" has defined a resource using {2} Definition with JNDI name "{0}". There is, however, an object already bound to JNDI using that name.

Cause: The JNDI name used by {1} Definition is already bound to JNDI.

Action: Define the resource with a different JNDI name.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045128: The application "{1}" has defined duplicate resources using {2} Definition with JNDI name "{0}", but the duplicate resources defined by the application are not compatible.

Cause: The application has defined duplicate resources that are not compatible.

Action: Fix the duplicate resources defined by {2} Definition and redeploy the application.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045129: {0} in an application.xml and classes outside of a module, is allowed to define a resource only in java:global and java:app namespaces. the application "{1}" has, however, defined a {0} with the name "{2}", which is not valid.

Cause: An environment entry declared in the application.xml descriptor and classes outside of a module must specify a JNDI name in the namespace java:app or java:global.

Action: Define the {0} resource in one of the allowed JNDI namespaces.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045130: The application "{1}" has defined a {0} resource with name "{2}" in a namespace that is not a well-defined namespace by the Java EE specification. The {0} resource is allowed only in one of the JNDI namespaces - java:global, java:app, java:module and java:comp.

Cause: An invalid JNDI namespace was used to define a {0} resource.

Action: Define the {0} resource in one of the allowed JNDI namespaces.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045131: The application "{0}" has specified one or more properties to define a {1} resource. The value set for a property specified by {2} does not, however, match the value expected by WebLogic.

Cause: The value set for a property does not match the value expected by WebLogic,

Action: Find the nested exception for more details and correct the configuration.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045132: The application "{0}" has defined a {1} resource using {2} and specified a property "{3}" with value "{4}", which is not the expected type for that property.

Cause: An unexpected type was used for the property.

Action: Check all properties in the defined resource.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045133: The Uniform Distributed Queue/Topic cannot be hosted by a cluster targeted JMSServer that does not have its distribution-policy set to Distributed. The UDQ/UDT named {0} in JMS Module {2} has its subdeployment {1} targeted to the Clustered JMSServer {3}.

Cause: The Uniform Distributed Queue/Topic cannot be hosted by a cluster targeted JMSServer that does not have its distribution-policy set to Distributed. The UDQ/UDT named {0} in JMS Module {2} has its subdeployment {1} targeted to the Clustered JMSServer {3}.

Action: Modify the target of the UDQ/UDT subdeployment so that it is targeted cluster targeted JMSServer with distribution-policy set to Distributed.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045134: JMS Module "{3}" deployed to {4} defines an entity of type {1} with name "{2}" and with default targeting option enabled. There are more than one JMS servers "{5}", having a persistent store with distribution policy "{0}" available in {4} to host the entity, which is not allowed.

Cause: For hosting the entity of type {1} with name "{2}" , and with default targeting option enabled defined in the JMS module "{3}" deployed to {4}, there must be exactly one JMS server with persistent store having distribution policy "{0}" defined in "{4}", but more than one candidate JMS servers were found to host that entity.

Action: Ensure that there is exactly one JMS server with store distribution policy "{0}" defined in scope {4} or use subdeployment to target the entity to the required JMS server.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045135: JMS Module "{2}" deployed to {3} defines an entity of type {0} with name "{1}" and with default targeting option enabled. There are more than one SAF agents "{4}", having a persistent store with distribution policy "Distributed" available in {3} to host the entity, which is not allowed.

Cause: For hosting the entity of type "{0}" with name "{1}" , with default targeting enabled defined in the JMS module "{2}" deployed to "{3}", there should be exactly one SAF agent with persistent store having distribution policy "Distributed" defined in "{3}", but more than one candidate SAF agents were found to host that entity.

Action: Ensure that there is exactly one SAF agent with persistent store having distribution policy "Distributed" defined in scope {3} or use subdeployment to target the entity to the required SAF agent.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045136: The JMS Server with name "{0}" specified by the property jms-server-name of {1} with JNDI name "{2}" in application {3} is not available in the {4}.

Cause: The client application has specified a JMS Server with name {0}, which is not available in the {4}.

Action: If the intent of the application is to target the {5} to a particular JMS Server, specify a valid JMS Server using property jms-server-name.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045137: Weighted (Non-Uniform) Distributed Destination/Destinations configured under a JMS module "{0}" are not supported because JMS module "{0}" exists under "{1}". Weighted (Non-Uniform) Distributed Destination are not supported in the Resource Group or Resource Group Template scopes.

Cause: Weighted (Non-Uniform) Distributed Destination/Destinations are not supported under a Resource Group or Resource Group Template scope.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045138: A Uniform Distributed Topic "{0}" in JMS module "{1}" is configured with a forwarding policy "Replicated". This policy is unsupported in a Resource Group or Resource Group Template scope and the JMS module "{1}" is configured under "{2}"

Cause: A Uniform Distributed Topic with forwarding policy "replicated" was used under a Resource Group or Resource Group Template deployment scope.

Action: Configure the topic to use a "Partitioned" policy or configure a non-distributed topic instead.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045139: The JMS Server with name "{0}" specified by the property jms-server-name of JMS Destination Definition with JNDI name "{1}" in application {2} has a persistent store with distribution policy "{3}". A JMS Server with a store having distribution policy "Distributed" is only allowed to host the destination defined by JMS Destination Definition.

Cause: The client application has specified JMS Server with name {0}, having a store with distribution policy {3}, which is not allowed to host a destination defined by a JMS Destination Definition.

Action: Specify a JMS werver that has distribution policy "Distributed" for property jms-server-name of a JMS Destination Definition.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045140: Error using a JMSContext object that was injected using @Inject. The JNDI name {0} specified in the @JMSConnectionFactory annotation does not refer to a javax.jms.ConnectionFactory or javax.jms.XAConnectionFactory, it refers to a {1}.

Cause: An error was encountered while using a JMSContext object that was injected using @Inject. The lookup name {0} specified in the @JMSConnectionFactory annotation does not refer to a javax.jms.ConnectionFactory or javax.jms.XAConnectionFactory, it refers to a {1}.

Action: Correct the lookup name specified using @JMSConnectionFactory and try again.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045141: Error using a JMSContext object that was injected using @Inject. Unable to look up the connection factory using the JNDI name {0} that was specified in the @JMSConnectionFactory annotation.

Cause: An error was encountered while using a JMSContext object that was injected using @Inject. The @JMSConnectionFactory annotation specified that the connection factory to be used could be obtained using the JNDI name (0), but an error occurred while looking up the connection factory.

Action: Correct the lookup name that was specified using @JMSConnectionFactory and try again.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045142: WebLogic Server has detected a deprecated JMS Interop Module in your configuration. This feature will be removed in a future release. Oracle recommends that you take appropriate measures to remove dependencies on JMS Interop Modules.

Cause: A deprecated JMS Interop Module was used in the configuration.

Action: Remove JMS Interop Modules from the configuration.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045143: The Subdeployment "{0}" in JMS Module "{1}" contains a standalone Queue or standalone Topic that can only be targeted to the JMS Server/JMS Servers that references a store configured with "Singleton" distribution-policy.

Cause: A SubDeployment is being referenced by a singleton style resource such as a standalone Queue or standalone Topic, so it must target to the JMS Server/JMS Servers that references a Store configured with "Singleton" distribution-policy. Note that a asubdeployment under a Resource Group or Resource Group Template scope must be targeted to a single JMS Server or to a single SAF Agent.

Action: Modify the target of the subdeployment so that it contains only JMS server/JMS servers that reference a Store configured with "Singleton" distribution-policy. Note the you must target a subdeployment to single JMS Server or single SAF Agent under a Resource Group or Resource Group Template scope.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045144: The SubDeployment "{0}" in JMS Module "{1}" contains a Distributed Queue or Distributed Topic that can only be targeted to the JMS Server/JMS Servers that references a Store configured with "Distributed" distribution-policy.

Cause: The SubDeployment of the given name cannot be targeted to anything but the JMS Server/JMSServers that references a Store that is configured with "Distributed" distribution-policy.

Action: Modify the target of the subdeployment so that it contains only JMS server/JMS servers that references a Store with "Distributed" distribution-policy. Note the you must target a subdeployment to a single JMS Server or single SAF Agent under a Resource Group or Resource Group Template scope.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045145: The URL "{0};" references a WebLogic MT partition, but WebLogic JMS Client for Microsoft .NET does not support partitions.

Cause: WebLogic MT partitions are not supported by WebLogic JMS Client for Microsoft .NET.

Action: Do not use a partition-scoped url. Use a domain-level provider url instead.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045146: Destination "{0};" with JNDI name "{1};" is scoped to a WebLogic MT partition, but WebLogic JMS Client for Microsoft .NET do not support partitons.

Cause: WebLogic MT partitions are not supported by WebLogic JMS Client for Microsoft .NET.

Action: Do not use a partition-scoped destination. Use a domain-level destination instead.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045147: ConnectionFactory "{0};" is scoped to a WebLogic MT partition, but WebLogic JMS Client for Microsoft .NET does not support partitons.

Cause: WebLogic MT partitions are not supported by WebLogic JMS Client for Microsoft .NET.

Action: Do not use a partition-scoped connection factory. Use a domain-level connection factory instead.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045148: JMS Destination Definition with JNDI name "{0}" defined in the application "{1}" which is deployed to {2} will not be hosted as there are more than one JMS Servers having a persistent store with distribution policy "Distributed" available.

Cause: For hosting the JMS Destination Definition with JNDI name "{0}" defined in the application "{1}" there must be at least one JMS server with a persistent store with distribution policy "Distributed" available in {2} to host the JMS destination. More than one JMS servers are available, however, as candidates in {2} to host the destination defined by the JMS Destination Definition.

Action: Ensure that there is exactly one JMS server available to host the JMS Destination Definition or specify a JMS Server having distribution policy "Distributed" using the property "jms-server-name" to host the destination defined by the JMS Destination Definition on the specified JMS server.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045149: The application "{0}" has defined a {1} resource with name "{3}" using {2} in an application client module "{4}" and specified a resource adapter "{5}".

Cause: A {2} in an application client module specifying a resource adapter is not allowed.

Action: Update the application client module to be compliant.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045150: The target named "{1}" of an SAF imported destination named "{3}" inside a deployment named "{0}" must be an SAF agent, WebLogic Server instance, or a cluster. Instead, it is of type {2}.

Cause: An attempt was made to target an SAF imported destination to an invalid type of target.

Action: Do not attempt to target an SAF imported destination to anything other than JMS servers, ServerMBean or ClusterMBean. Any other type of target is not understood.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045151: The target named "{1}" of an SAF imported destination named "{3}" inside a deployment named "{0}" must be an SAF agent. Instead, it is of type {2}.

Cause: An attempt was made to target an SAF imported destination to an invalid type of target.

Action: Do not attempt to target an SAF imported destination to anything other than JMS servers. Any other type of target is not understood.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045152: The JMS Module "{1}" deployed to {2} defines a Foreign Server with name "{0}" and is targeted to subdeployment {3}. The subdeployment {3} is, however, targeted to a JMS Server with distribution policy "Singleton", which is not allowed to be used as a target for a Foreign Server.

Cause: A Foreign Server is not allowed to be targeted to a subdeployment that has a JMS Server with distribution policy "Singleton".

Action: Change the target of the subdeployment to have a JMS Server with distribution policy "Distributed" used by the Foreign Server or use default targeting.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045153: The JMS resource with JNDI name "{2}" defined using {0} by the application "{1}" does not have proper hierarchy of targets. "{3}" specified by property jms-server-name is not a subtarget of "{4}".

Cause: The JMS resource with JNDI name "{2}" defined using {0} by the application "{1}" does not have proper hierarchy of targets. "{3}" specified by property jms-server-name is not a subtarget of "{4}".

Action: Specify a JMS Server for property jms-server-name which is available in the same hierarchy as that of the application deployment.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045154: A Uniform Distributed Destination can only be targeted to a JMS Server that is in the same Resource Group or Resource Group Template scope as the uniform distributed destination. JMS Server "{0}" is not in the same scope as the destination.

Cause: A Uniform Distributed Destination can only be targeted to a JMS Server that is in the same Resource Group or Resource Group Template scope as the uniform distributed destination. JMS Server "{0}" is not in the same scope as the destination.

Action: Target the Uniform Distributed Destination to JMS Server defined in the same Resource Group/Resource Group Template scope as the uniform distributed destination.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045155: There is scope conflict. Either a naming context is attached to a pre-12.2.1 WebLogic Server but the scope type is Resource Group or Resource Group Template (the Domain scope type is the only valid type in this case), or a naming context is attached to a partition but the scope type is Domain or a Resource Group Template (the Resource Group scope type is the only supported type in this case).

Cause: There is scope conflict. Either a naming context is attached to a pre-12.2.1 WebLogic Server but the scope type is Resource Group or Resource Group Template (the Domain scope type is the only valid type in this case), or a naming context is attached to a partition but the scope type is Domain or a Resource Group Template (the Resource Group scope type is the only supported type in this case).

Action: When accessing resource group template or domain level configuration ensure that the specified naming context is attached to a domain level scope.Also, when accessing either resource group or resource group template configuration, ensure that the naming context is attached to WebLogic 12.2.1 or greater server.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045156: Could not find partition name in the given "Context" Object.

Cause: Could not find partition name in the given "Context" Object.

Action: Verify valid partition name is attached to the "Context" Object.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045157: {0} named "{1} " does not exist in the {2} scope.

Cause: {0} named "{1} " does not exist in the {2} scope.

Action: Specify a {0} which exists for deleting the same.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045158: A {0} named "{1} " does not exist in the Resource Group or Resource Group Template {2}.

Cause: A {0} named "{1} " does not exist in the Resource Group or Resource Group Template {2}.

Action: Specify a {0} which exists.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045159: A {0} "{1}" does not exist under {2}.

Cause: A {0} "{1}" does not exist under {2}.

Action: Specify a correct scope name, partition name and scope type.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045160: The Target name "{0}" is not allowed in {1} scope. Target name must be null in Resource Group/Resource Group Template scope and It should not be null for Domain scope.

Cause: The Target name "{0}" is not allowed in {1} scope. Target name must be null in Resource Group/Resource Group Template scope and It should not be null for Domain scope.

Action: Specify a valid target.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045161: Parameter {0} can't be null or empty.

Cause: Parameter {0} can't be null or empty.

Action: Specify a valid {0}.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045162: Operation "{0}" cannot be invoked in Resource Group or Resource Group Template scope.

Cause: Operation "{0}" cannot be invoked in Resource Group or Resource Group Template scope.

Action: Operation "{0}" is not allowed in current scope. Please verify your configuration.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045163: Targets of Uniform Distributed Destination deployment overlap. JMS Server named: " {0} " is been identified twice as potential JMSServer for hosting the Uniform Distributed Destionation's members under the Uniform Distributed.

Cause: Weblogic Internal Error.

Action: An Uniform Destionation can be targeted to single JMS Server.Please verify the configuration.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045164: Invalid partition name: the given partition Name {0} does not exist under {1}.

Cause: Invalid partition name: the given partition Name {0} does not exist under {1}.

Action: Verify whether partition name exist in given scope {1}.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045165: Object-based security is enabled on the JMS connection factory with JNDI name "{0}", therefore it can only be used by a 12.2.2.1.0 or later client.

Cause: Object-based security is enabled on the JMS connection factory with JNDI name "{0}", therefore it can only be used by a 12.2.2.1.0 or later client.

Action: Use another JMS connection factory whose Security Policy is ThreadBased.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045166: The InitialContextFactory {0} is not supported by Foreign Server.

Cause: The InitialContextFactory {0} is not supported by Foreign Server.

Action: Do not use this InitialContextFactory {0} because it is not supported by Foreign Server.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045167: The proposed JNDI name {0} for destination {1} is already bound by another object of type {2}. {3}

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045168: Connection is closed because {0} is shutting down.

Cause: The associated ResourceGroup or Partition is coming down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

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-050008: Illegal cross partition JNDI lookup detected for "{0}" from source context "{1}" to destination context "{2}".

Cause: An attempt was made to access the "{0}", the current partition is "{1}" but the target partition is "{2}". This cross partition should be taken care of by visibility control.

Action: Either configure "{0}" to allow cross partition access or modify the application to avoid cross partition lookup. For example, you can use a remote (host:port) url to target the destination.
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: The given method identification number does not exist.

Action: Check for other log messages that give more information about the failure.
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: The given method number could not be found in the given class.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055043: No such method {0} for class {1}.

Cause: The given method number could not be found in the given class.

Action: Check for other log messages that give more information about the failure.
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: The given method identification number does not exist.

Action: Check for other log messages that give more information about the failure.
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: An error occurred. See {0}.

Cause: See the message body.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055050: An error occurred {0}

Cause: See the message body.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055051: An error occurred {0}

Cause: See the message body.

Action: Check for other log messages that give more information about the failure.
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: See the message body.

Action: Check for other log messages that give more information about the failure.
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 {0} on a queue session.

Cause: A call to {0} was made on a QueueSession.

Action: Avoid calling {0} 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 integer 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: Check for other log messages that give more information about the failure.
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-055177: An invalid value ({0}) for session mode was specified.

Cause: An invalid value of the sessionMode parameter was specified when creating a JMSContext. The only valid values are JMSContext.AUTO_ACKNOWLEDGE, JMSContext.CLIENT_ACKNOWLEDGE, JMSContext.DUPS_OK_ACKNOWLEDGE and JMSContext.SESSION_TRANSACTED

Action: Change the code so that it passes in a valid session mode. See the JMS API for more information.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055178: This method may not be called in a Java EE web or EJB container

Cause: The code calls a JMS method which the JMS, EJB or Java EE specification states must not be called in a Java EE web or EJB container. See section EE.6.7 "Java Message Service (JMS) 2.0 Requirements" in the Java EE 7 platform specification" and section 16.3.5 "JMS API Requirements" in the EJB 3.2 specification.

Action: Change the code so that it uses methods that are valid a Java EE web or EJB container.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055179: JMSContext is closed

Cause: The code called the close methods on a JMSContext which had been previously closed.

Action: Change the code so that it uses a JMSContext that has not been closed.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055180: Cannot set the setClientID method on a JMSContext because the JMSContext is in an invalid state

Cause: The setClientID method was called on a JMSContext when the JMSContext is in an invalid state. It only valid to call the setClientID method on a JMSContext immediately after the JMSContext has been created and before any other action on the JMSContext is taken. It is also only valid to call the setClientID method on a JMSContext if the client ID has not already been administratively configured.

Action: Change the code to endure that the setClientID method on a JMSContext is only called immediately after the JMSContext has been created and before any other action on the JMSContext is taken, and only if the client ID has not already been administratively configured.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055181: Invalid client ID. Client ID may not be null.

Cause: The setClientID method was called on a JMSContext but the specified client ID was null.

Action: Change the code so that the specified client ID is neither null nor an empty string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055182: Invalid client ID. Client ID may not be an empty string.

Cause: The setClientID method was called on a JMSContext but the specified client ID was an empty string.

Action: Change the code so that the specified client ID is neither null nor an empty string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055183: JMSConsumer is closed

Cause: The code called the close method on a JMSConsumer which had been previously closed.

Action: Change the code so that it uses a JMSConsumer that has not been closed.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055184: Message is null

Cause: The code called the send method on a JMSProducer with a null value for the message parameter.

Action: Change the code so that the message parameter passed to the JMSProducer send method is not null
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055185: An invalid value ({0}) for delivery mode was specified

Cause: The setDeliveryMode method on JMSProducer was called with an invalid value of the deliveryMode parameter. The only valid values are DeliveryMode.NON_PERSISTENT, DeliveryMode.PERSISTENT.

Action: Change the code so that it passes in a valid delivery mode. See the JMS API for more information.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055186: An invalid value ({0}) for message priority was specified

Cause: The setPriority method on JMSProducer was called with an invalid value of the setPriority parameter. Priority must be a valie between 0 and 9.

Action: Change the code so that it passes in a valid priority value. See the JMS API for more information.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055187: Message property name must not be null.

Cause: The message property name parameter was null. This is not valid.

Action: Change the code to pass a message property name which is not null.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055188: Message property name must not be an empty string

Cause: The message property name parameter was an empty string. This is not valid.

Action: Change the code to pass a message property name which is not an empty string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055189: Message property value must not be of type ({0})

Cause: The message property name was of an invalid type. A message property value must be of type Boolean, Byte, Short, Integer, Long, Float or Double.

Action: Change the code to pass a message property value of a valid type. Valid types are Boolean, Byte, Short, Integer, Long, Float and Double.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055190: Message property name ({0}) must not be a reserved word

Cause: The message property name is a reserved word. This is not valid. A message property name cannot be NOT, AND, OR, BETWEEN, LIKE, IN, IS, or ESCAPE.

Action: Change the code to pass a message property name which is not a reserved word.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055191: Message property name ({0}) contains an invalid character.

Cause: Message property name contains an invalid character. The first character must be a letter and subsequent characters must be either a letter or a digit. A letter is any character for which the method Character.isJavaLetter returns true. This includes '_' and '$'. A letter or digit is any character for which the method Character.isJavaLetterOrDigit returns true.

Action: Change the code to pass a message property name which contains valid characters.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055192: Message property name ({0}) contains an invalid first character.

Cause: Message property name contains an invalid start character. The first character must be a letter and subsequent characters must be either a letter or a digit. A letter is any character for which the method Character.isJavaLetter returns true. This includes '_' and '$'. A letter or digit is any character for which the method Character.isJavaLetterOrDigit returns true

Action: Change the code to pass a message property name which contains valid characters.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055193: Message body is a {0} and cannot be assigned to the specified class {1}

Cause: Message body is a {0} and cannot be assigned to the specified class {1}. The application called the getBody method on a Message object. This method returns the message body as an object of the specified type. The message body must be capable of being assigned to the specified type. This means that the specified class or interface must be either the same as, or a superclass or superinterface of, the class of the message body.

Action: Specify a class which is suitable for the actual body type
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055194: Message body is a StreamMessage and the getBody method cannot be used

Cause: The application called the getBody method on a Message object. Message body is a StreamMessage and the getBody method cannot be used with this type of message.

Action: Use the methods specific to StreamMessage to obtain the message body. Do not use the getBody method.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055195: Shared durable connection consumers are not supported.

Cause: The system does not support shared durable connection consumers.

Action: Do not attempt to create a shared durable connection consumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055196: Shared connection consumers are not supported.

Cause: The system does not support shared connection consumers.

Action: Do not attempt to create a shared connection consumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055197: Invalid deliveryDelay , must be >= 0.

Cause: The deliveryDelay parameter passed to setDeliveryDelay was invalid.

Action: Change the code to pass a deliveryDelay parameter that is >= 0 .
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055198: The JMS specification does not permit a message listener to call {0} on its own {1}.

Cause: A message listener attempted to call {0} on its own {1}. This is not permitted by the JMS specification.

Action: To conform to the JMS specification, change the message listener code so that it does not call {0} on its own {1}. Alternatively enable the connection factory setting AllowCloseInOnMessage to specify that this non-JMS behavior is permitted.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055199: An injected JMSContext cannot be used when there is neither a transaction nor a valid request scope.

Cause: The application attempted to use an injected JMSContext when there was neither a Java EE transaction nor a CDI request scope.

Action: Change the code to ensure that methods on the injected JMSContext are only called when there is a Java EE transaction or a valid CDI request scope. Alternatively, use an application-managed JMSContext (one created explicitly from a Connectionfactory) instead of an injected JMSContext.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055200: Asynchronous message forward is not currently supported.

Cause: The application called the JMSProducer method setAsync before calling the JMSProducer method forward on the same JMSProducer object.

Action: Remove the call to the JMSProducer method setAsync and try again. This will perform a synchronmous forward instead.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055201: An invalid value ({0}) for message priority was specified

Cause: The send method on MessageProducer was called with an invalid priority value. Priority must be a value between 0 and 9.

Action: Pass a valid priority value. See the JMS API for more information.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055202: An invalid value ({0}) for delivery mode was specified.

Cause: The send method on MessageProducer was called with invalid delivery mode value. The only valid values are DeliveryMode.NON_PERSISTENT, DeliveryMode.PERSISTENT.

Action: Pass a valid delivery mode value. See the JMS API for more information.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055203: The same Message object ({0}) was previously sent asynchronously but is not complete yet.

Cause: A send method is called for a Message object that was asynchronously sent but is not complete yet.

Action: Create a new Message object to send or wait for the asynchronous send to complete.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055204: JMS asynchronous send is not supported in an XA transaction.

Cause: A JMS asynchronous send was used in an XA transaction.

Action: Do not attempt to use asynchronous send in an XA transaction.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055205: There is no message body.

Cause: There is no message body in the message.

Action: Do not attempt to get the message body from a message that has no message body.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055206: CompletionListener is null.

Cause: A null CompletionListener was passed to the asynchronous send method.

Action: Do not pass a null CompletionListener to the JMS asynchronous send method.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055207: The Security Policy setting for JMS Connection Factory ({0}) is ({1}) which is not compatible with a Thread Based InitialContext.

Cause: The Security Policy setting for JMS Connection Factory ({0}) is ({1}) which is not compatible with a Thread Based InitialContext.

Action: Use an Object Based InitialContext to lookup the connection factory instead of a Thread Based InitialContext, or set a different Security Policy.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055208: Object based InitialContext does not support to lookup type "{0}".

Cause: Object based InitialContext only support to lookup three types: jndi context, WLJMS CF and WLJMS destinaton.

Action: Use a WL standard InitialContext to lookup other types.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055209: Foreign Server is not supported by Object Based InitialContext.

Cause: Foreign Server is not supported by Object Based InitialContext. Looking up the local JNDI name of the Foreign Server is not supported by Object Based InitialContext.

Action: Do not use Object Based InitialContext to look up the local JNDI name of the Foreign Server.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055210: Object based InitialContext does not support the "{0}" method.

Cause: Object based InitialContext does not support the "{0}" method.

Action: Do not call this method with Object Based InitialContext or use a WL standard InitialContext instead.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055211: Object based InitialContext only support the "{0}" method on server side and install client.

Cause: Object based InitialContext only support the "{0}" method on server side and install client, does not support it on other client.

Action: Call this method on server side or install clientï¼Œdo not call it on other client.
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-080028: Failover attempt failed: {0} after {1} retries

Cause: The cause was {0}

Action: Please check the trace message.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-090058: A Security Provider Exception occurred in a non-default AuditProvider {0}

Cause: A Security exception occurred during an audit write event.

Action: Check errors or access permissions for the Auditing provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090059: The "{0}" AccessDecision class encountered an invalid Principal while attempting to check access to a WebLogic resource. Error: {1}

Cause: It is possible for this error to occur if a user has been deleted from a security realm while that user is still active.

Action: If the user was mistakenly removed from the security realm, define them in the security realm again. Otherwise, no action is needed.
Level: 1

Type: WARNING

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-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 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 attempting to load LDIF for provider {0} from file {1}.

Cause: An exception occurred 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-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 provider {0} has been bootstrapped but has not been initialized with any LDIF data.

Cause: A WebLogic 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-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: Shutdown 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. Reboot 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: Shutdown the server. Attempt to restore the file from a backup. If no backup is available,reboot the server. Note that the default WebLogic 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 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. Reboot the server. 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-090161: A failure occurred attempting to save LDIF for security provider {0} using file {1}.

Cause: An exception occurred 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 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-090234: The Auditing Provider is not initialized.

Cause: The WebLogic Auditing provider was not initialized before the writeEvent method was called.

Action: Ensure that the WebLogic Auditing provider has been initialized before events are written.
Level: 1

Type: ERROR

Impact: Security

BEA-090235: Invalid Audit Severity

Cause: The Audit severity value is invalid or not supported.

Action: Verify the Audit severity value passed to the setAuditSeverity method.
Level: 1

Type: ERROR

Impact: Security

BEA-090236: DefaultAuthenticatorImpl constructor failed: {0}

Cause: An exception was thrown in the constructor of the WebLogic Authentication provider.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090237: Validation of old password failed

Cause: The old password was not valid.

Action: Pass in the correct old password to the changeUserPassword method.
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 BEA 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 BEA 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-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: LDAP exception during 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-090254: name cannot be null

Cause: The name cannot be null in the setUserDescription, setGroupDescription, getUserDescription, or getGroupDescription methods.

Action: Pass in a non-null name to the method.
Level: 1

Type: ERROR

Impact: Security

BEA-090255: User or Group {0}

Cause: The user or group cannot be found.

Action: Pass in a user or group that exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090256: Error setting description for {0}

Cause: an exception occurred while calling to modify the description in the server.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090257: group cannot be null

Cause: The group name cannot be null.

Action: Pass in a non-null group name to the method.
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} can not be found.

Cause: Group {0} does not exist in the server.

Action: Pass in a group that exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090260: Error listing group members for {0}

Cause: an exception was thrown while searching for the group members in the store.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090261: wildcard cannot be null

Cause: 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 exception was thrown while searching for the groups in the store.

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: 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: 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: 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: Group name cannot be null.

Action: Pass a non-null group name to the method.
Level: 1

Type: ERROR

Impact: Security

BEA-090267: Group {0}

Cause: Group {0} already exists in the LDAP server. Users and groups must have unique names.

Action: Pass in a unique group name.
Level: 1

Type: ERROR

Impact: Security

BEA-090268: Group {0}

Cause: User {0} already exists in the LDAP server. Users and groups must have unique names.

Action: Pass in a unique user name.
Level: 1

Type: ERROR

Impact: Security

BEA-090269: Error adding group {0}

Cause: an exception was thrown while adding the group in the store.

Action: Users and groups must have unique names.
Level: 1

Type: ERROR

Impact: Security

BEA-090270: group cannot be same as member

Cause: Member and group names must be unique.

Action: Pass in a group and member name that are unique.
Level: 1

Type: ERROR

Impact: Security

BEA-090271: Member {0} can not be found.

Cause: Member does not exist.

Action: Pass in a member name that exists in the store.
Level: 1

Type: ERROR

Impact: Security

BEA-090272: Error adding member {0} to {1}

Cause: an exception was thrown while adding the member to the group in the store.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090273: member cannot be group

Cause: Member and group names must be unique.

Action: Pass in a group and member name that are unique.
Level: 1

Type: ERROR

Impact: Security

BEA-090274: Error removing member {0} from {1}

Cause: an exception was thrown when removing the member from the group in the store.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090275: Error removing group {0}

Cause: an exception was thrown while removing the group from the store.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090276: Error removing group {0} invalid cursor

Cause: An InvalidCursorException exception was thrown while removing the group from the store.

Action: This exception indicates an internal coding error in the server. Contact BEA support.
Level: 1

Type: ERROR

Impact: Security

BEA-090277: Error destroying provider:

Cause: an LDAP exception was thrown while removing all the users and groups from the LDAP server.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090278: Error listing member groups {0}

Cause: an LDAP exception was thrown 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 was thrown 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-090280: user cannot be null

Cause: User name cannot be null.

Action: Pass a non-null user name to the method.
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-090282: password cannot be null

Cause: The password cannot be null.

Action: Pass a non-null password 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-090284: Group {0}

Cause: Group {0} already exists in the LDAP server. Groups and users must have unique names.

Action: Pass in an user name that is not already an existing group.
Level: 1

Type: ERROR

Impact: Security

BEA-090285: password must be at least {0} characters long

Cause: Password is not long enough.

Action: Enter a password that meets the specified minimum length requirement.
Level: 1

Type: ERROR

Impact: Security

BEA-090286: Error adding user {0}

Cause: an LDAP exception was thrown while adding the user to the LDAP server.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090287: User {0} can not be found.

Cause: User {0} does not exist in the server.

Action: Pass a user name that exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090288: Invalid password for user {0}

Cause: The bind to the LDAP server using this user name and password failed.

Action: Pass a valid password or use the resetPassword method which does not require the old password.
Level: 1

Type: ERROR

Impact: Security

BEA-090289: Error changing password for {0}

Cause: an LDAP exception was thrown while modifying the password in the LDAP server.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090290: Error removing user {0}

Cause: an LDAP exception was thrown while removing the user from the server.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090291: {0} search scope ({1}) not recognized

Cause: Search scope {1} is not a valid value.

Action: Change the User Search Scope attribute for the LDAP Authentication provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090293: Error creating provider

Cause: An LDAP exception was thrown when checking the LDAP hierarchy in the initialization of the provider.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090294: could not get connection

Cause: an LDAP exception was thrown 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-090295: caught unexpected exception

Cause: An unexpected LDAP exception was thrown when calling LDAP methods.

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 was thrown 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 BEA 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 BEA 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 BEA support.
Level: 1

Type: ERROR

Impact: Security

BEA-090300: Identity Assertion Failed: User {0} does not exist

Cause: 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: Password cannot be null.

Action: This exception indicates an internal coding error in the server. Contact BEA 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-090303: Authentication Failed: User {0} {1}

Cause: an LDAP exception caused the authentication of the user to fail.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090304: Authentication Failed: User {0} {1}

Cause: An unexpected exception caused the authentication of the user to fail.

Action: Read the exception text for more information on diagnosing the problem.
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-090306: Authentication Failed Getting Groups for User {0} {1}

Cause: A Invalid Cursor, Invalid Parameter, or LDAP exception was thrown when looking up the groups of which the user is a member.

Action: Read the exception text in {1} for more information on diagnosing the problem.
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-090308: Validation of old password failed

Cause: The old password was not valid.

Action: Verify the old password. Optionally, use the resetPassword method to change the user password.
Level: 1

Type: ERROR

Impact: Security

BEA-090310: Failed to create resource

Cause: An EnCreateException was thrown 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 was thrown 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 was thrown 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 was thrown 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 was thrown 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 BEA support.
Level: 1

Type: ERROR

Impact: Security

BEA-090317: bug in PredicateArgument

Cause: The arguments for the predicate are invalid.

Action: Verify the definition of the condition expression of the security policy.
Level: 1

Type: ERROR

Impact: Security

BEA-090318: DefaultRoleMapperImpl init failed: {0}

Cause: An exception was thrown 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 BEA support.
Level: 1

Type: ERROR

Impact: Security

BEA-090320: Failed to create role

Cause: An exception was thrown 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 was thrown during the delete operation.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090324: DefaultCredentialMapperImpl init failed: {0}

Cause: An exception was thrown during the initialization of the WebLogic Credential Mapping provider.

Action: Read the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090326: DefaultCredentialMapperImpl.listCredentials got LDAP exception

Cause: An LDAP exception was thrown while accessing the LDAP server to get the list of credentials for this WebLogic resource.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090327: DefaultCredentialMapperImpl.getCurrentCredentialRemoteUsername failed: No such credentials list cursor available

Cause: Cursor is invalid.

Action: Verify that the cursor was returned from the listCredentials method.
Level: 1

Type: ERROR

Impact: Security

BEA-090329: DefaultCredentialMapperImpl.listMappings got LDAP exception

Cause: An LDAP exception was thrown while accessing the LDAP server to get the list of credential mappings for this WebLogic resource.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090330: DefaultCredentialMapperImpl.getCurrentMappingWLSUsername failed: No such resource maps list cursor available

Cause: Cursor is invalid.

Action: Verify that the cursor was returned from the listMappings method.
Level: 1

Type: ERROR

Impact: Security

BEA-090331: DefaultCredentialMapperImpl.getCurrentMappingRemoteUsername failed: No such resource maps list cursor available

Cause: Cursor is invalid.

Action: Verify that the cursor was returned from the listMappings method.
Level: 1

Type: ERROR

Impact: Security

BEA-090332: DefaultCredentialMapperImpl.getRemoteUserName got LDAP exception

Cause: An LDAP exception was thrown while accessing the LDAP server to get the credential map or the credential map principal.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090333: DefaultCredentialMapperImpl.getRemotePassword got LDAP exception

Cause: An LDAP exception was thrown while accessing the LDAP server to get the password for the credential map.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090334: DefaultCredentialMapperImpl.setUserPasswordCredential got LDAP exception

Cause: An LDAP exception was thrown while accessing the LDAP server to set the password for the credential map.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090335: DefaultCredentialMapperImpl.setUserPasswordCredentialMapping got LDAP exception

Cause: An LDAP exception was thrown while accessing the LDAP server to set the credential resource map.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090336: DefaultCredentialMapperImpl.removeUserPasswordCredential got LDAP exception

Cause: An LDAP exception was thrown while accessing the LDAP server to remove the user password credential.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090337: DefaultCredentialMapperImpl.removeUserPasswordCredentialMapping got LDAP exception

Cause: An LDAP exception was thrown while accessing the LDAP server to remove the user password credential mapping.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090339: Could not create file output stream {0}

Cause: An IO exception was thrown during the create of either the temporary file or the real file for the Audit log.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090367: This method not yet implemented

Cause: Method is not implemented and should not be used.

Action: This exception indicates an internal coding error in the server. Contact BEA 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 BEA support.
Level: 1

Type: ERROR

Impact: Security

BEA-090377: Identity Assertion Failed, {0}

Cause: An IdentityAssertion exception was thrown in the assertIdentity or assertChallengeIdentity method of the Identity Assertion provider

Action: Read the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090380: Identity Assertion Failed, Unsupported Token Type: {0}

Cause: Token type is not configured as an active type.

Action: Define the token type {0} in the Active Types attribute of the configured Identity Assertion provider.
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 BEA support.
Level: 1

Type: ERROR

Impact: Security

BEA-090442: location null or empty

Cause: A keystore filename must not 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-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 is 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: Import file cannot be read.

Action: Verify the import filename.
Level: 1

Type: ERROR

Impact: Security

BEA-090453: Import File Error

Cause: An IO exception was thrown 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-090455: Export File Error

Cause: An IO exception was thrown 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-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 a LDIF template file produced by an export operation.
Level: 1

Type: ERROR

Impact: Security

BEA-090473: DefaultAuthorizerImpl search failed: {0}

Cause: An exception was thrown 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-090511: The following exception has occurred:

Cause: An error condition has occurred.

Action: Read the associated exception in the log or in application to determine the problem. In general, a stack trace can be used to debug an existing problem.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090512: The WebLogic Auditing provider failed to register to listen for AuditorMBean attribute change notifications

Cause: The installation of WebLogic Server is corrupt.

Action: In order for a change in the auditing severity to take effect, the server needs to be rebooted.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090516: The {0} provider has preexisting LDAP data.

Cause: The provider was initialized during a previous boot of the WebLogic Server

Action: No action necessary.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090517: Group {0} cannot be added to group {1} since group {0} is already ancestor of group {1}.

Cause: Group membership can not be circular..

Action: Ensure that group membership is not circular. Add this group to a different group.
Level: 1

Type: ERROR

Impact: Security

BEA-090545: DefaultRoleMapperImpl search failed: {0}

Cause: An exception was thrown 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-090553: Invalid system property value: {0}={1}

Cause: Invalid system property value was passed on the command line.

Action: Make sure the property value is valid and restart the server.
Level: 1

Type: WARNING

Impact: Security

BEA-090555: The DefaultCredentialMapper could not get credentials. The requestor is {0}. The initiator is {1}. The resource is {2}. The exception is {3}.

Cause: An unexpected exception occurred when trying to get credentials.

Action: Read the exception text from the log message for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090583: The EndCertificateSelector constructor was passed an illegal X509Certificate.

Cause: The X509Certificate must not be null.

Action: Pass a valid X509Certificate to the EndCertificateSelector constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-090584: The IssuerDNSerialNumberSelector constructor was passed an illegal issuer DN.

Cause: The issuer DN must not be null or empty.

Action: Pass a valid issuer DN to the IssuerDNSerialNumberSelector constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-090585: The IssuerDNSerialNumberSelector constructor was passed an illegal serial number.

Cause: The serial number must not be null.

Action: Pass a valid serial number to the IssuerDNSerialNumberSelector constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-090586: The SubjectDNSelector constructor was passed an illegal subject DN.

Cause: The subject DN must not be null or empty.

Action: Pass a valid subject DN to the SubjectDNSelector constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-090587: The SubjectKeyIdentifierSelector constructor was passed an illegal subject key identifier.

Cause: The subject key identifier must not be null or empty.

Action: Pass a valid subject key identifier to the SubjectKeyIdentifierSelector constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-090588: The WLSCertPathBuilderResult constructor was passed an illegal Certpath.

Cause: The CertPath must not be null or empty.

Action: Pass a valid CertPath to the WLSCertPathBuilderResult constructor. It must at least contain the end certificate of the cert chain."
Level: 1

Type: ERROR

Impact: Security

BEA-090593: The realm {0} has an illegal cert path builder configured. To correct the problem, select one of the realm"s cert path providers as the realm"s cert path builder.

Cause: The realm {0} has an illegal cert path builder configured.

Action: To correct the problem, select one of the realm"s cert path providers as the realm"s cert path builder.
Level: 1

Type: WARNING

Impact: Security

BEA-090594: The {0} cert path security provider was passed an illegal CertPathParameters.

Cause: The CertPathParameters must be a weblogic.security.spi.CertPathBuilderParametersSpi.

Action: The {0} cert path security provider must not be called directly by application code.
Level: 1

Type: ERROR

Impact: Security

BEA-090595: The {0} cert path security provider was passed an illegal CertPathParameters.

Cause: The CertPathParameters must be a weblogic.security.spi.CertPathValidatorParametersSpi.

Action: The {0} cert path security provider must not be called directly by application code.
Level: 1

Type: ERROR

Impact: Security

BEA-090596: The WebLogicCertPathProvider was passed an unsupported CertPathSelector.

Cause: The CertPathSelector must be an EndCertificateSelector.

Action: Pass an EndCertificateSelector to the WebLogicCertPathProvider.
Level: 1

Type: ERROR

Impact: Security

BEA-090597: The CertificateRegistry was passed an unsupported CertPathSelector.

Cause: The CertPathSelector must be an EndCertificateSelector, IssuerDNSerialNumberSelector, SubjectDNSelector or SubjectKeyIdentifierSelector.

Action: Pass an EndCertificateSelector, IssuerDNSerialNumberSelector, SubjectDNSelector or SubjectKeyIdentifierSelector to the CertificateRegistry.
Level: 1

Type: ERROR

Impact: Security

BEA-090603: The certificate chain is invalid because it could not be completed. The trusted CAs did not include {0}.

Cause: The trusted CAs did not include {0}.

Action: Add {0} to the chain or to the list of the trusted CAs if you want this chain to be validated.
Level: 1

Type: ERROR

Impact: Security

BEA-090604: The certificate chain is invalid because none of its certificates is a trusted CA.

Cause: None of its certificates is a trusted CA.

Action: Add one of the certificates in the chain to the list of of trusted CAs if you want this chain to be validated.
Level: 1

Type: ERROR

Impact: Security

BEA-090605: The certificate chain is invalid because it contains the certificate {0} is either expired or is not currently valid.

Cause: The invalid certificate is {0}.

Action: If this certificate is a trusted CA, and the certificate authority has issued a replacement certificate with the same subject DN and private key, and you want the certificate chain to be validated, then replace the trusted CA with the updated one. Otherwise, you must obtain a new certificate chain if you want the chain to be validated.
Level: 1

Type: ERROR

Impact: Security

BEA-090606: The certificate chain is invalid because a certificate"s issuer DN "{0}" does not match it"s CA"s subject DN "{1}".

Cause: The certificate"s issuer DN is "{0}". The CA"s subject DN is "{1}".

Action: You must obtain a new certificate chain if you want the chain to be validated.
Level: 1

Type: ERROR

Impact: Security

BEA-090607: The certificate chain is invalid because of an encoding error for certificate {0}.

Cause: The invalid certificate is {0}.

Action: Ensure that the certificate chain only contains certificates using RSA keys and that the JDK is configured to support RSA keys.
Level: 1

Type: ERROR

Impact: Security

BEA-090608: The certificate chain is invalid because a certificate"s signature could not be validated by it"s CA"s public key. The invalid certificate is {0}. The CA is {1}.

Cause: Most likely, the wrong CA is in the chain for the certificate. The invalid certificate is {0}. The CA is {1}.

Action: You must obtain a new certificate chain if you want the chain to be validated.
Level: 1

Type: ERROR

Impact: Security

BEA-090609: The certificate chain is invalid because there is no JDK provider for certificate {0}.

Cause: The invalid certificate is {0}.

Action: Ensure that the certificate chain only contains certificates using RSA keys and that the JDK is configured to support RSA keys.
Level: 1

Type: ERROR

Impact: Security

BEA-090610: The certificate chain is invalid because there is no default JDK provider for certificate {0}.

Cause: The invalid certificate is {0}.

Action: Ensure that the certificate chain only contains certificates using RSA keys and that the JDK is configured to support RSA keys.
Level: 1

Type: ERROR

Impact: Security

BEA-090611: The certificate chain is invalid because a certificate"s signature could not be validated. The invalid certificate is {0}.

Cause: Most likely, the certificate has been tampered with. The invalid certificate is {0}.

Action: You must obtain a new certificate chain if you want the chain to be validated.
Level: 1

Type: ERROR

Impact: Security

BEA-090612: The certificate chain is invalid because it contains a certificate with an unsupported critical extension. The invalid certificate is {0}. The unsupported critical extension"s oid is {1}.

Cause: The invalid certificate is {0}. The unsupported critical extension"s oid is {1}.

Action: You must obtain a new certificate chain if you want the chain to be validated.
Level: 1

Type: ERROR

Impact: Security

BEA-090613: The certificate chain is invalid because it is longer than one of it"s CA"s allows. The CA is {0}. The chain length to that CA is {1}. The maximum chain length to that CA is {2}.

Cause: The CA is {0}. The chain length to that CA is {1}. The maximum chain length to that CA is {2}.

Action: You must obtain a new certificate chain if you want the chain to be validated.
Level: 1

Type: ERROR

Impact: Security

BEA-090614: The certificate chain is invalid because it contains a CA without basic constraints. The CA is {0}.

Cause: The CA is {0}.

Action: You must obtain a new certificate chain if you want the chain to be validated.
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-090616: The configured CertPathBuilder provider returned an empty cert path.

Cause: The configured CertPathBuilder provider has a bug. It should never return an empty cert path.

Action: Fix the bug in the configured CertPathBuilder.
Level: 1

Type: ERROR

Impact: Security

BEA-090618: The WLS CertPathValidator was passed a null or empty cert path.

Cause: The WLS CertPathValidator was passed a null or empty cert path.

Action: Pass a cert path containing at least one certificate to the WLS CertPathValidator.
Level: 1

Type: ERROR

Impact: Security

BEA-090620: There is no JDK CertPathBuilder for algorithm {0}.

Cause: There is no JDK CertPathBuilder for algorithm {0}.

Action: This is an internal WebLogic Server error in either the JDK or a WLS CertPathProvider.
Level: 1

Type: ERROR

Impact: Security

BEA-090621: There is no JDK CertPathValidator for algorithm {0}.

Cause: There is no JDK CertPathValidator for algorithm {0}.

Action: This is an internal WebLogic Server error in either the JDK or a WLS CertPathProvider.
Level: 1

Type: ERROR

Impact: Security

BEA-090623: Failed to get the default trusted CAs for this server.

Cause: This exception is thrown 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-090624: Failed to create an X509 CertPath from an array of X509Certificates.

Cause: Failed to create an X509 CertPath from an array of X509Certificates.

Action: Look at the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090635: No Results

Cause: There are no policies that match the search criteria.

Action: No action necessary.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090636: No Results

Cause: There are no roles that match the search criteria.

Action: No action necessary.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090637: No role name 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 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 a valid resource type was supplied and contact BEA 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 component type parameter specified is not valid.

Action: Specify a valid component type of EJB, WebApp, Connector or WebService.
Level: 1

Type: ERROR

Impact: Security

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-090656: Empty {0} resource {1} string

Cause: An empty string was supplied for an element of the resource.

Action: Specify a valid string.
Level: 1

Type: ERROR

Impact: Security

BEA-090657: Empty {0} resource {1} array string

Cause: An empty string was supplied for an array element of the resource.

Action: Specify a valid string.
Level: 1

Type: ERROR

Impact: Security

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 necessary. 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 necessary. However, the security provider should be updated.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090666: Deploy handle not supplied

Cause: The deployment handle is null.

Action: This exception is an internal WebLogic Server error. Contact BEA support.
Level: 1

Type: ERROR

Impact: Security

BEA-090667: Application information not supplied

Cause: The application information is null.

Action: This exception is an internal WebLogic Server error. Contact BEA support.
Level: 1

Type: ERROR

Impact: Security

BEA-090671: Unable to get password digest for user name {0}

Cause: The user does not exist in the WebLogic authentication provider Embedded LDAP server or there is no password information available to calculate a digest.

Action: Verify that the user exists in the WebLogic authentication provider, the authentication provider has the PasswordDigestEnabled attribute set to true, and the user entry has set the password since the attribute was set to true.
Level: 1

Type: ERROR

Impact: Security

BEA-090683: The CertificateRegistry could not build a certificate path for end certificate {0}. This indicates that either someone is trying to access the server with an untrusted certificate or that the administrator has forgotten to register the certificate in the CertificateRegistry.

Cause: The CertificateRegistry does not contain the certificate {0}.

Action: If you want to trust the end certificate {0}, then register it in the CertificateRegistry.
Level: 1

Type: ERROR

Impact: Security

BEA-090684: The CertificateRegistry could not build a certificate path for the subject DN {0}. This indicates that either someone is trying to access the server with an untrusted subject DN or that the administrator has forgotten to register a certificate with this subject DN in the CertificateRegistry.

Cause: The CertificateRegistry does not contain a certificate whose subject DN is {0}.

Action: If you want to trust the subject DN {0}, then register a certificate with this subject DN in the CertificateRegistry.
Level: 1

Type: ERROR

Impact: Security

BEA-090685: The CertificateRegistry could not build a certificate path for the issuer DN {0} and serial number {1}. This indicates that either someone is trying to access the server with an untrusted issuer DN and serial number or that the administrator has forgotten to register a certificate with this issuer DN and serial number in the CertificateRegistry.

Cause: The CertificateRegistry does not contain a certificate whose issuer DN is {0} and whose serial number is {1}.

Action: If you want to trust the issuer DN {0} and serial number {1}, then register a certificate with this issuer DN and serial number in the CertificateRegistry.
Level: 1

Type: ERROR

Impact: Security

BEA-090686: The CertificateRegistry could not build a certificate path for the subject key identifier {0}. This indicates that either someone is trying to access the server with an untrusted subject key identifier or that the administrator has forgotten to register a certificate with this subject key identifier in the CertificateRegistry.

Cause: The CertificateRegistry does not contain a certificate whose subject key identifier is {0}.

Action: If you want to trust the subject key identifier {0}, then register a certificate with this subject key identifier in the CertificateRegistry.
Level: 1

Type: ERROR

Impact: Security

BEA-090687: The CertificateRegistry could not validate a certificate path whose end certificate is {0}. This indicates that either someone is trying to access the server with an untrusted certificate or that the administrator has forgotten to register the certificate in the CertificateRegistry.

Cause: The CertificateRegistry does not contain the certificate {0}.

Action: If you want to trust the end certificate {0}, then register it in the CertificateRegistry.
Level: 1

Type: ERROR

Impact: Security

BEA-090688: The maximum number of concurrent lists has been exceeded. The maximum is {0}. These lists are allocated by listing functions listAliases for the CertificateRegistry. Wait for some of the existing lists to either expire or be closed. Lists automatically expire if they have not been used for {1} milliseconds.

Cause: Either the server is under very heavy load, or someone is launching a denial service attack against the server or some application code (e.g. a client) is not closing lists after it finishes using them.

Action: Wait for some of the existing lists to either time out or be closed.
Level: 1

Type: ERROR

Impact: Security

BEA-090689: The certificate alias is null or empty.

Cause: An empty or null certificate alias is not supported.

Action: Modify the code to pass a non-null and non-empty certificate alias.
Level: 1

Type: ERROR

Impact: Security

BEA-090690: The file name is null or empty.

Cause: An empty or null file name is not supported.

Action: Modify the code to pass a non-null and non-empty file name.
Level: 1

Type: ERROR

Impact: Security

BEA-090691: The certificate alias wildcard is null or empty.

Cause: An empty or null certificate alias wildcard is not supported.

Action: Modify the code to pass a non-null and non-empty certificate alias wildcard.
Level: 1

Type: ERROR

Impact: Security

BEA-090692: 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-090693: Certificate alias {0} not found.

Cause: The alias cannot be found.

Action: Pass in a certificate alias that exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090694: The security provider already has a certificate registered under the alias {0}.

Cause: Certificate alias {0} already exists in the security provider.

Action: Pass in another certificate alias.
Level: 1

Type: ERROR

Impact: Security

BEA-090695: Subject DN {0} already registered under the alias {1}

Cause: A certificate with subject DN {0} already exists in the security provider under the alias {1}.

Action: Either remove the previous certificate from the security provider or register a different certificate.
Level: 1

Type: ERROR

Impact: Security

BEA-090696: Issuer DN {0} and serial number {1} already registered under the alias {2}

Cause: A certificate with issuer DN {0} and serial number {1} already exists in the security provider under the alias {2}.

Action: Either remove the previous certificate from the security provider or register a different certificate.
Level: 1

Type: ERROR

Impact: Security

BEA-090697: Subject key identifier {0} already registered under the alias {1}

Cause: A certificate with subject key identifier {0} already exists in the security provider under the alias {1}.

Action: Either remove the previous certificate from the security provider or register a different certificate.
Level: 1

Type: ERROR

Impact: Security

BEA-090698: Errors occurred while importing data into this security provider.

Cause: Some of the data could not be imported into this security provider.

Action: The getExceptions method on the ErrorCollectionException thrown by this method may be used to get a list of the errors that occurred.
Level: 1

Type: ERROR

Impact: Security

BEA-090699: Errors occurred while exporting data from this security provider.

Cause: Some of the data could not be exported from this security provider.

Action: The getExceptions method on the ErrorCollectionException thrown by this method may be used to get a list of the errors that occurred.
Level: 1

Type: ERROR

Impact: Security

BEA-090710: Unable to write the file {0}.

Cause: Examine the nested exception for more information in diagnosing the problem.

Action: Verify that the file is not a directory or a read-only file.
Level: 1

Type: ERROR

Impact: Security

BEA-090711: Unable to read the file {0}.

Cause: Examine the nested exception for more information in diagnosing the problem.

Action: Verify that the file exists and is not a directory.
Level: 1

Type: ERROR

Impact: Security

BEA-090712: Unable to read the JKS keystore {0}.

Cause: Examine the nested exception for more information in diagnosing the problem.

Action: Verify that the file is a JKS keystore.
Level: 1

Type: ERROR

Impact: Security

BEA-090713: Unable to read the certificate in the PEM or DER file {0}.

Cause: Examine the nested exception for more information in diagnosing the problem.

Action: Verify that the file is a PEM or DER file containing a single certificate.
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 has completed.

Action: Call the hasChallengeIdentityCompleted method before calling the method to get the subject.
Level: 1

Type: ERROR

Impact: Security

BEA-090726: Unexpected exception while reading credential attribute: {0}

Cause: LDAP connection failure, corrupted LDAP database, or invalid cursor.

Action: Verify that LDAP is up and running.
Level: 1

Type: ERROR

Impact: Security

BEA-090728: Failed to read credential of type {0} stored under alias {1}

Cause: LDAP connection failure, or the database is corrupted.

Action: Verify that LDAP is up and running.
Level: 1

Type: ERROR

Impact: Security

BEA-090731: Unable to retrieve query

Cause: The internal query structure was not able to be retrieved from the connection. This could potentially be caused by a misconfigured DBMS ATN provider, but is more likely caused by an internal coding error in the DBMS ATN provider.

Action: Review JDBC connection pool configuration, and provider level SQL Query settings. If these appear valid, this exception may indicate an internal coding error in the DBMS ATN provider. Contact BEA support.
Level: 1

Type: ERROR

Impact: Security

BEA-090732: Invalid data source name specified: {0}

Cause: The DBMS ATN provider was most likely configured with an invalid data source name

Action: Review and correct the data source name in the DBMS ATN provider configuration
Level: 1

Type: ERROR

Impact: Security

BEA-090734: The connection pool was not usable

Cause: The DBMS ATN provider or the connection pool it is configured to use may be misconfigured or unavailable.

Action: Review the JDBC related configuration in the server and the DBMS ATN provider configuration, and test the JDBC connection pool.
Level: 1

Type: ERROR

Impact: Security

BEA-090735: The DBMS connection was not usable

Cause: The DBMS ATN provider or the connection pool it is configured to use may be misconfigured or unavailable.

Action: Review the JDBC related configuration in the server and the DBMS ATN provider configuration, and test the JDBC connection pool.
Level: 1

Type: ERROR

Impact: Security

BEA-090736: An exception occurred while validating the {0} configuration settings

Cause: An unexpected exception was thrown while validating configuration settings. This may indicate a configuration problem, or it may be an internal coding error

Action: Review the exception trace for details on the cause, if the cause and solution are not apparent, contact BEA support.
Level: 1

Type: ERROR

Impact: Security

BEA-090737: An exception occurred while getting connection to validate the configuration settings

Cause: An exception was thrown while validating configuration settings. This may indicate a configuration problem, or it may be an internal coding error

Action: Review the exception trace for details on the cause, if the cause and solution are not apparent, contact BEA support.
Level: 1

Type: ERROR

Impact: Security

BEA-090738: The {0} password hash algorithm is not usable

Cause: The password algorithm name was not found to be supported by the JCE crypto configuration

Action: Verify the password algorithm is specified correctly, and that the JCE configuration supports the algorithm.
Level: 1

Type: ERROR

Impact: Security

BEA-090739: The SQL statement for {0} does not appear to be correct

Cause: The DBMS SQL providers attempt to validate the configured SQL statements are correct. The validation code detected something was wrong with the configured SQL.

Action: Review and correct the SQL statement.
Level: 1

Type: ERROR

Impact: Security

BEA-090740: An unexpected exception occurred while calling the {0} method of the user defined DBMS sub plugin

Cause: The DBMS pluggable runtime providers caught an unexpected exception while calling the user defined sub plugin. The cause likely resides in the user defined sub plugin.

Action: Review the exception details and the user defined sub plugin code to determine the cause and action.
Level: 1

Type: ERROR

Impact: Security

BEA-090741: A SQLException occurred while calling the {0} method of the user defined DBMS sub plugin

Cause: The DBMS pluggable runtime providers caught a SQLException while calling the user defined sub plugin. The cause could be a database connectivity issue, or it could reside in the user defined sub plugin.

Action: Review the exception details and the user defined sub plugin code to determine the cause and action.
Level: 1

Type: ERROR

Impact: Security

BEA-090742: The DBMS pluggable runtime sub plugin failed to load

Cause: The DBMS pluggable runtime provider was not able to load the user defined sub plugin.

Action: Review the DBMS pluggable runtime provider configuration. Verify the name of the user defined sub plugin class is correct, and that it is present in the server classpath.
Level: 1

Type: ERROR

Impact: Security

BEA-090743: An unexpected exception occurred while loading the {0} sub plugin class

Cause: The DBMS pluggable runtime provider was not able to load the user defined sub plugin class and the exception thrown was not expected.

Action: Review the exception details and the sub plugin configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-090744: The DBMS sub plugin class {0} was not found

Cause: The user defined sub plugin class was not found

Action: Verify the name of the user defined sub plugin class is correct, and that it is present in the server classpath.
Level: 1

Type: ERROR

Impact: Security

BEA-090745: The DBMS sub plugin class {0} was not the correct type

Cause: The user defined sub plugin class was not the correct type. Either the wrong class was specified, or the sub plugin was not coded correctly

Action: Verify the user defined sub plugin class name is correct and that it implements the correct interface.
Level: 1

Type: ERROR

Impact: Security

BEA-090746: The DBMS sub plugin class {0} was not able to be accessed

Cause: The user defined sub plugin class was not able to be accessed. Either the wrong class was specified, or the sub plugin was not coded correctly

Action: Verify the user defined sub plugin class name is correct, that it implements the correct interface, and that the class is publicly accessible.
Level: 1

Type: ERROR

Impact: Security

BEA-090747: The DBMS sub plugin class {0} was not able to be instantiated

Cause: The user defined sub plugin class was not able to be instantiated. Either the wrong class was specified, or the sub plugin was not coded correctly

Action: Verify the user defined sub plugin class name is correct, that it implements the correct interface, it is defined as a class, and it is not an abstract class.
Level: 1

Type: ERROR

Impact: Security

BEA-090748: There was a failure closing the DBMS connection

Cause: The exception information should be reviewed to determine the cause.

Action: Review the exception details to determine if action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090751: Failed to retrieve the prepared statement for {0}

Cause: Failed to retrieve the prepared statement for {0}, this is potentially an internal coding error

Action: Review the JDBC configuration, contact BEA support if the cause is not apparent
Level: 1

Type: ERROR

Impact: Security

BEA-090752: The password type in the DBMS was not a supported type

Cause: It is most likely caused by the password field in the DBMS stored as an unexpected type, binary or char data is expected.

Action: Review the type for the password field in the database to ensure it is either binary or char data
Level: 1

Type: ERROR

Impact: Security

BEA-090753: Hash algorithm {0} was not found

Cause: The JCE configuration is most likely not setup to support the algorithm

Action: Review the JCE configuration to ensure the hash algorithm is available for use.
Level: 1

Type: ERROR

Impact: Security

BEA-090754: The DBMS authenticator provider login module was not properly initialized

Cause: The DBMS authentication provider configuration may be incorrect, or there could be an internal coding error.

Action: Review the DBMS authentication provider configuration. If no cause is found, contact BEA support.
Level: 1

Type: ERROR

Impact: Security

BEA-090755: A database connection was not available from pool. Try increasing Connection Pool Size or Timeout

Cause: The connection pool size or timeout settings may need to be increased

Action: Review the JDBC connection pool related configuration in the server, and consider increasing the connection pool size or timeout
Level: 1

Type: ERROR

Impact: Security

BEA-090756: The DBMS provider was unable to form a query to access the {0} information

Cause: For SQL based DBMS providers configuration is most likely incorrect. For sub pluggable DBMS providers the user defined sub-plugin code could also be the cause.

Action: Review and correct the DBMS provider configuration. If a sub pluggable provider is being used, also review the user defined sub plugin code.
Level: 1

Type: ERROR

Impact: Security

BEA-090757: The DBMS provider got an exception when formatting the user

Cause: If a user defined sub-plugin for formatting the user was supplied, it may have a coding error

Action: Review and correct the user defined sub-plugin user format code.
Level: 1

Type: ERROR

Impact: Security

BEA-090758: The DBMS provider got an exception when formatting the groups

Cause: If a user defined sub-plugin for formatting the groups was supplied, it may have a coding error

Action: Review and correct the user defined sub-plugin group format code.
Level: 1

Type: ERROR

Impact: Security

BEA-090759: A SQLException occurred while retrieving {0} information

Cause: A SQLException occurred while retrieving {0} information

Action: Review the exception details to determine the cause and action.
Level: 1

Type: ERROR

Impact: Security

BEA-090760: The user {0} was not unique in the DBMS

Cause: This is caused by multiple records for the username existing in the DBMS

Action: Review the DBMS records for the username.
Level: 1

Type: ERROR

Impact: Security

BEA-090761: Authentication failed for user {0}

Cause: The exception details need to be reviewed to determine the cause

Action: Review the exception details to determine the cause and action to take.
Level: 1

Type: ERROR

Impact: Security

BEA-090762: Exception occurred in login module

Cause: The exception details need to be reviewed to determine the cause

Action: Review the exception details to determine the cause and action to take.
Level: 1

Type: ERROR

Impact: Security

BEA-090765: Failed to create policies for application version {0}

Cause: An exception was thrown 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 was thrown 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-090767: Failed to create credential mappings for application version {0}

Cause: An exception was thrown 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-090768: credential mapping removal error

Cause: An unexpected exception occurred when trying to remove the credentials for a deleted application.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090769: The Active Directory ATN provider could not access the tokenGroups attribute for userDN {0} with principal {1} to perform group membership lookup.

Cause: The tokenGroups attribute was not accessible in the user entry. This is most likely the a problem with the Active Directory schema, or an Active Directory permission problem with the principal that is configured to access Active Directory.

Action: Have the Active Directory administrator verify that the tokenGroup attribute is present in the Active Directory schema, and that the {1} principal has permission to read the tokenGroups attribute in Active Directory
Level: 1

Type: ERROR

Impact: Security

BEA-090771: The Negotiate Identity Asserter was not configured with enough active types to perform negotiation.

Cause: The Negotiate Identity Asserter needs to be configured with all of its supported types specified as active types in order to perform negotiation.

Action: Update the Negotiate Identity Asserter configuration to add all supported types listed for the provider to be active types.
Level: 1

Type: ERROR

Impact: Security

BEA-090776: Exception when trying to generate a SAML assertion: {0}

Cause: An exception during the generation 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-090777: Exception when trying to sign a SAML assertion: {0}

Cause: An exception 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-090781: The SAMLLoginModule expected to receive a SAMLNameCallback and instead received a {0}.

Cause: This likely a configuration problem, if a SAMLIALoginModule is configured without a corresponding SAMLIdentityAsserter being configured.

Action: Check the configuration of Identity Asserters and Login Modules.
Level: 1

Type: ERROR

Impact: Security

BEA-090784: While Trying to find the groups that {0} belongs to,A Duplicate member {1} was detected.

Cause: A duplicate Membership in the groups was detected.

Action: It might be possible that a cycle exists in the group entries.
Level: 1

Type: WARNING

Impact: Security

BEA-090785: The Negotiate Identity Asserter found no identity to assert and no continuation was indicated.

Cause: This likely a configuration problem.

Action: Check the configuration for the negotiate identity asserter and kerberos.
Level: 1

Type: ERROR

Impact: Security

BEA-090786: The Negotiate Identity Asserter encountered an unexpected error processing a token.

Cause: This should not happen. This could be due to an invalid or corrupt SPNEGO token, or possibly some unknown token format similar to SPNEGO.

Action: This exception indicates an internal coding error in the server. Contact BEA support.
Level: 1

Type: ERROR

Impact: Security

BEA-090787: A Null DataSource name specified

Cause: A configuration setting that required a DataSource name was null.

Action: Check configuration settings that require DataSource names to verify they are correctly specified.
Level: 1

Type: ERROR

Impact: Security

BEA-090788: "Problem with DataSource/ConnectionPool configuration, verify DataSource name {0} is correct and Pool configurations are correct"

Cause: A configuration setting that required a DataSource name was likely incorrect, or the pool settings associated with it are incorrect.

Action: Check configuration settings to ensure the DataSource name is correct and the associated pool configuration settings are correct
Level: 1

Type: ERROR

Impact: Security

BEA-090789: The DBMS authentication provider encountered an unexpected exception during authentication.

Cause: An unexpected exception occurred during authentication.

Action: Review the exception stack trace. If the cause is not obvious, contact BEA support
Level: 1

Type: ERROR

Impact: Security

BEA-090790: BINARY or VARBINARY Result type is not allowed for this SQL statement {0}

Cause: The SQL statement result was a type that is not allowed for that statement

Action: Review the SQL statement in the configuration to ensure it returns an appropriate type
Level: 1

Type: ERROR

Impact: Security

BEA-090791: Result type is not {0} for SQL statement {1}

Cause: The SQL statement requires a result type of {0}

Action: Review the SQL statement in the configuration to ensure it returns an appropriate type
Level: 1

Type: ERROR

Impact: Security

BEA-090792: Parameter {0} type is not CHAR or VARCHAR for SQL statement {1}

Cause: The SQL statement parameter {0} requires a type of CHAR or VARCHAR

Action: Review the SQL statement in the configuration to ensure the parameter types are correct
Level: 1

Type: ERROR

Impact: Security

BEA-090793: Unexpected exception caught accepting the kerberos context, verify the JCE configuration is correct in java.security and the sun.security.jgss.SunProvider is configured

Cause: The exception stack should be reviewed, but this could be due to the JCE configuration in java.security not having the sun.security.jgss.SunProvider configured

Action: Verify the JCE configuration is correct. If it is correct, review the exception to determine the cause.
Level: 1

Type: ERROR

Impact: Security

BEA-090794: Password hash algorithm was not specified

Cause: The configuration is most likely set with an empty password hash algorithm

Action: Review the configuration to ensure the hash algorithm is specified correctly.
Level: 1

Type: ERROR

Impact: Security

BEA-090795: No columns in SQL results, need 1 column for SQL statement {0}

Cause: The SQL statement requires a result

Action: Review the SQL statement in the configuration to ensure it returns an appropriate number and type of result
Level: 1

Type: ERROR

Impact: Security

BEA-090796: Number of parameters was expected to be {0} but was {1} for SQL statement {2}

Cause: The SQL statement requires a specific number of parameters, and the statement specified had a different number of parameters

Action: Review the SQL statement in the configuration to ensure it has the expected number of parameters specified
Level: 1

Type: ERROR

Impact: Security

BEA-090798: Invalid characters found in input {0}

Cause: Input was specified that had invalid characters in it

Action: Review the rejected input to determine what invalid characters were specified and enter the input without them
Level: 1

Type: ERROR

Impact: Security

BEA-090799: PKICredentialMapperImpl init failed: {0}

Cause: An exception was thrown during the initialization of the WebLogic PKI Credential Mapping provider.

Action: Read the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090800: Value for argument {0} for the credential type {1} not found.

Cause: Value for {0} for credential type {1} does not exist in the LDAP server.

Action: Pass a value that exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090801: Value for resource {0}, initiator name {1} representing user name {2} with credential action {3} for the credential type {4} not found.

Cause: Value for resource {0}, initiator name {1} representing user name {2} with credential action {3} for the credential type {4} does not exist in the LDAP server.

Action: Pass the values that exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090802: PKI Credential Mapper has got an LDAP exception.

Cause: An LDAP exception was thrown while accessing the LDAP server to set the Key Pair mapping.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090803: PKI Credential Mapper has got an LDAP exception.

Cause: An LDAP exception was thrown while accessing the LDAP server to set the Public Certificate Mapping.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090804: Credential of the type {0} could not be removed.

Cause: An LDAP exception was thrown while accessing the LDAP server.

Action: Check if the LDAP serer is up and running.
Level: 1

Type: WARNING

Impact: Security

BEA-090805: Failed to read credential for Resource {0}, initiator name {1} representing user name {2} with credential action {3} for the credential type {4}.

Cause: LDAP connection failure, or the database is corrupted.

Action: Verify that LDAP is up and running.
Level: 1

Type: ERROR

Impact: Security

BEA-090806: PKI Keystore at location {0} not found .

Cause: Keystore configured at location {0} for the PKI Credential Provider not found.

Action: Please create the keystore that is configured for the PKI Credential Mapper.
Level: 1

Type: ERROR

Impact: Security

BEA-090807: PKI Keystore at location {0} of the type {1} and of type {2} and could not be loaded with the password provided.

Cause: Either the keystore password provided was not correct or the keystore type and provider not correctly entered.

Action: Configure the keystore properly.
Level: 1

Type: ERROR

Impact: Security

BEA-090808: The keystore alias {0} provided does not exist in the keystore configured for the provider.

Cause: The alias provided does not exist in the keystore configured for the provider.

Action: Configure the keystore with the alias provided.
Level: 1

Type: ERROR

Impact: Security

BEA-090809: The key pair could not be retrieved from the keystore with the supplied alias {0} and its password.

Cause: Either the alias supplied does not represent a key pair or the password provided is incorrect.

Action: Please configure the keystore with the key pair properly.
Level: 1

Type: ERROR

Impact: Security

BEA-090810: The keystore alias {0} provided does not represent a certificate entry in the keystore.

Cause: The alias provided does not represent a certificate entry in the keystore.

Action: Configure the keystore with the appropriate certificate entry.
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-090813: DefaultCredentialMapperImpl.getCurrentMappingResourceID failed: No such resource maps list cursor available

Cause: Cursor is invalid.

Action: Verify that the cursor was returned from the listMappings method.
Level: 1

Type: ERROR

Impact: Security

BEA-090815: The password provided for the keystore configured for the PKICredential Mapper was null.

Cause: The keystore password provided for the PKI Credential Mapper cannot be null.

Action: Enter a valid password for the keystore configured for the PKI Credential Mapper.
Level: 1

Type: ERROR

Impact: Security

BEA-090816: Error creating security configuration runtime: {0}

Cause: During initialization, the security runtime registers with the management infrastructure. If this process fails, a management exception is thrown.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090817: These configuration changes cannot be activated since the domain does not have a default realm configured.

Cause: The "DefaultRealm" is not set for the domain's SecurityConfiguration.

Action: To correct the problem, set the "DefaultRealm" for the domain's SecurityConfiguration to one of its realms. If it does not have any realms, create and configure one.
Level: 1

Type: ERROR

Impact: Security

BEA-090820: The internal variable {0} is null and it should not be.

Cause: Unknown.

Action: This exception is an internal WebLogic Server error. Contact BEA support.
Level: 1

Type: ERROR

Impact: Security

BEA-090821: The configured CertPathBuilder provider returned an unordered CertPath. {0} The CertPath is {1}

Cause: The configured CertPathBuilder provider has a bug. It should never return an unordered CertPath.

Action: Fix the bug in the configured CertPathBuilder.
Level: 1

Type: ERROR

Impact: Security

BEA-090824: Unable to generate SAML Assertion: {0}

Cause: The SAML assertion could not be generated due to incorrect SAML configuration or missing/incorrect parameters supplied to the assertion generator.

Action: Check the SAML configuration.
Level: 1

Type: 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-090828: Identity Assertion type cannot be null

Cause: The token type was null.

Action: Null should not be passed as the token type.
Level: 1

Type: ERROR

Impact: Security

BEA-090829: Identity Assertion token cannot be null

Cause: The identity assertion token was null.

Action: Null should not be passed as the token.
Level: 1

Type: ERROR

Impact: Security

BEA-090830: Identity Assertion type of {0} is not a valid token type for the LDAP X509 Identity Assertion provider.

Cause: The token type passed in did not match the LDAP X509 Identity Assertion token type.

Action: Pass in the correct token type for the LDAP X509 Identity Assertion provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090831: 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-090832: No matching certificate found in the LDAP directory.

Cause: No matching certificate were found in the LDAP directory.

Action: Verify that the appropriate certificates are present in the configured LDAP directory.
Level: 1

Type: ERROR

Impact: Security

BEA-090833: No certificates found in the LDAP directory.

Cause: No certificates were found in the LDAP directory.

Action: Verify that the appropriate certificates are present in the configured LDAP directory.
Level: 1

Type: ERROR

Impact: Security

BEA-090834: No LDAP connection could be established.

Cause: The connection parameters provided were either not correct or the LDAP was offline.

Action: Verify that the connection parameters provided are correct and the LDAP server is running.
Level: 1

Type: ERROR

Impact: Security

BEA-090835: Required parameter not supplied when performing the management operation on the PKI Credential Provider.

Cause: A required parameter was null.

Action: Please call the management operations with the appropriate parameters.
Level: 1

Type: ERROR

Impact: Security

BEA-090836: The Keystore provider configured for PKICredential Mapper does not exist at location {0}.

Cause: The file {0} does not exist.

Action: To use the PKICredentialProvider please point to an existing keystore. Reboot the server.
Level: 1

Type: ERROR

Impact: Security

BEA-090837: The configured keystore location for the PKI Credential Mapper is either null or empty.

Cause: The PKI Credential provider location value was either set to null or empty.

Action: Set the PKI Credential provider keystore location to a valid keystore location.
Level: 1

Type: ERROR

Impact: Security

BEA-090841: SAMLServlet: Unexpected exception while handling {0} request.

Cause: SAML providers not configured correctly, internal server error, or malformed request.

Action: Check SAML configuration and server status. If configuration is OK and server is operating normally, enable SAML debug logging for more information.
Level: 1

Type: ERROR

Impact: Security

BEA-090842: SAMLServletAuthenticationFilter: Unexpected exception.

Cause: SAML providers not configured correctly, internal server error, or malformed request.

Action: Check SAML configuration and server operation. If problem persists, enable SAML debug logging for more information.
Level: 1

Type: ERROR

Impact: Security

BEA-090843: {0} provider initialization failed: {1} parameter is null.

Cause: Internal server error.

Action: Try restarting server.
Level: 1

Type: ERROR

Impact: Security

BEA-090844: {0} provider initialization failed: Invalid {1} property ''{2}'' for ''{3}''.

Cause: Incorrect provider configuration.

Action: Check and update the indicated provider property.
Level: 1

Type: ERROR

Impact: Security

BEA-090845: {0} provider initialization failed: Missing {1} property for "{2}".

Cause: Invalid provider configuration.

Action: Check and update the indicated provider property.
Level: 1

Type: ERROR

Impact: Security

BEA-090846: {0} provider initialization failed: Invalid {1} attribute ''{2}''.

Cause: 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: Invalid provider configuration.

Action: Check and update the indicated provider attribute.
Level: 1

Type: ERROR

Impact: Security

BEA-090848: {0} provider initialization failed: Unexpected exception.

Cause: Internal server error.

Action: Check server status.
Level: 1

Type: ERROR

Impact: Security

BEA-090849: {0} provider initialization failed: Exception while initializing XML parsers.

Cause: Internal server error.

Action: Check server.
Level: 1

Type: ERROR

Impact: Security

BEA-090851: The {0} provider is initialized.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090853: SAMLIdentityAsserter initialization failed: Could not instantiate/initialize the used assertion cache class: {0}.

Cause: Invalid class name configured, class is not visible to the class loader, or initialization parameters are incorrect..

Action: Check configuration of class name and initialization parameters. Check that class is installed in a valid location.
Level: 1

Type: ERROR

Impact: Security

BEA-090854: {0} provider initialization failed: Could not retrieve credentials for {1}.

Cause: SSL identity not configured for server.

Action: Check SSL configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-090856: {0} configuration update failed: Provider settings updated while not initialized.

Cause: Internal server error.

Action: Check server.
Level: 1

Type: ERROR

Impact: Security

BEA-090857: {0} provider initialization failed: Could not register MBean update listener.

Cause: Internal server error.

Action: Check server.
Level: 1

Type: ERROR

Impact: Security

BEA-090863: There was an error in the SAML CredentialMapper Cache subsystem. The exception is {0}.

Cause: The SAML Cache could have been misconfigured.

Action: Please check the SAML Cache parameters and restart the server.
Level: 1

Type: ERROR

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-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 doing a service lookup

Action: Check the configuration to see that the missing service was actually configured.
Level: 1

Type: ERROR

Impact: Security

BEA-090873: Expected a {0} object but did not get one.

Cause: Possible configuration problem.

Action: Check 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: This is most likely a configuration error.
Level: 1

Type: ERROR

Impact: Security

BEA-090878: Unknown token type: {0}

Cause: Likely caused by the token type not being properly configured.

Action: This is most likely a configuration error.
Level: 1

Type: ERROR

Impact: Security

BEA-090879: The certificate for the imported alias {0} is already in registry, certificate not imported

Cause: None

Action: No action required.
Level: 1

Type: WARNING

Impact: Security

BEA-090881: Management operation could not be performed

Cause: The administration server is not reachable.

Action: Check that the administration server is running and available on the network.
Level: 1

Type: ERROR

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: List number should not be negative.

Action: Check that the list number is not negative.
Level: 1

Type: ERROR

Impact: Security

BEA-090887: Can not find member {0} from group {1}.

Cause: Member {0} not exit in group {1}.

Action: Check the group members.
Level: 1

Type: ERROR

Impact: Security

BEA-090897: A failure occurred attempting to update XACML global policies for security provider {0}.

Cause: An exception occurred attempting to update XACML global policies.

Action: Examine the exception and correct the cause.
Level: 1

Type: ERROR

Impact: Security

BEA-090899: User attribute name cannot be null.

Cause: User attribute name is null for the request.

Action: Please pass in user attribute name which is not null.
Level: 1

Type: ERROR

Impact: Security

BEA-090900: User attribute name is not supported for specified operation.

Cause: User attribute name is not supported.

Action: Please pass in user attribute name which is supported. Please refer to documentation for details.
Level: 1

Type: ERROR

Impact: Security

BEA-090901: Invalid group name: {0}. Can not contain {1}.

Cause: 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 is 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, 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-090905: Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -D{0}=true

Cause: CryptoJ JCE Provider self-integrity check incurs some performance penalty at server startup.

Action: No action needed.
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 slower.

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090907: Invalid user name: {0}. Can not contain {1}.

Cause: 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: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090909: Using the configured custom SSL Hostname Verifier implementation: {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090910: Grant statement has invalid syntax: {0}

Cause: There is an error in the syntax of the grant statement.

Action: Verify that the grant statement syntax is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-090911: Permission found in grant statement has invalid syntax: {0}

Cause: There is an error in the syntax of the permission within the grant statement.

Action: Verify that the grant statement permission syntax is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-090912: Attempting to check revocation status for certificate with subject: {0}

Cause: X.509 certificate revocation checking is enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090913: Unknown revocation status not causing failure for certificate with subject: {0}

Cause: X.509 certificate revocation checking is enabled, however, certificate revocation status cannot be determined, and is configured not to fail on an unknown status.

Action: If validation failure is required, configure certificate revocation status to fail on an unknown status. To determine why the status is unknown, enable debug logging.
Level: 1

Type: WARNING

Impact: Security

BEA-090914: Certificate revocation status: {0}

Cause: X.509 certificate revocation checking is enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090915: Nonce was ignored by the OCSP responder, forcing certificate revocation status to be ignored and considered unknown: {0}.

Cause: X.509 certificate revocation checking is enabled, and OCSP is configured with nonces enabled.

Action: To enable use of the ignored status, configure to disable OCSP nonces.
Level: 1

Type: WARNING

Impact: Security

BEA-090916: Unknown revocation status causing failure for certificate with subject: {0}.

Cause: X.509 certificate revocation checking is enabled, certificate revocation status cannot be determined, and is configured to fail on an unknown status.

Action: If validation failure is not required, configure certificate revocation status to not fail on an unknown status. To determine why the status is unknown, enable debug logging.
Level: 1

Type: WARNING

Impact: Security

BEA-090917: Revoked certificate causing validation failure, certificate with subject: {0}.

Cause: X.509 certificate revocation checking is enabled, and the checked certificate was reported revoked.

Action: Contact the certificate presenter (for example, SSL peer) and request that the revoked certificate be updated.
Level: 1

Type: WARNING

Impact: Security

BEA-090918: Non-revoked certificate with subject: {0}.

Cause: X.509 certificate revocation checking is enabled, and the checked certificate was reported NOT revoked.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090919: The configured SSL minimum protocol version {0} is invalid or not supported. The minimum has been changed to {1}.

Cause: The current SSL implementation does not support the configured SSL minimum protocol version.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Security

BEA-090920: Certicom SSL is available, however JSSE is being used for SSL, since JSSE has been selected by system property {0}, either explicitly or by default.

Cause: The system property {0} is selecting JSSE either explicitly or by default.

Action: To use Certicom for SSL, set the system property {0} to false.
Level: 1

Type: WARNING

Impact: Security

BEA-090921: JSSE has not been selected by system property {0}, however Certicom SSL is not available, so JSSE is being used for SSL.

Cause: Certicom SSL is not available, so JSSE is being used for SSL, even though JSSE was not selected.

Action: To use Certicom for SSL, install Certicom.
Level: 1

Type: WARNING

Impact: Security

BEA-090922: Certicom SSL is available, however JSSE is being used for SSL, since JSSE has been selected by the SSLMBean.JSSEEnabled attribute, either explicitly or by default.

Cause: The attribute SSLMBean.JSSEEnabled is selecting JSSE either explicitly or by default.

Action: To use Certicom for SSL, set the attribute SSLMBean.JSSEEnabled to false.
Level: 1

Type: WARNING

Impact: Security

BEA-090923: JSSE has not been selected by the SSLMBean.JSSEEnabled attribute, however Certicom SSL is not available, so JSSE is being used for SSL.

Cause: Certicom SSL is not available, so JSSE is being used for SSL, even though JSSE was not selected.

Action: To use Certicom for SSL, install Certicom.
Level: 1

Type: WARNING

Impact: Security

BEA-090924: JSSE has been selected by default, since the SSLMBean is not available.

Cause: This usually occurs early in server startup, before Management Service runtime access is available.

Action: No action is required. Eventually the Management Service will start and normal operation will commence.
Level: 1

Type: WARNING

Impact: Security

BEA-090925: JSSE has been selected by default, since the system property {0} has the invalid value "{1}".

Cause: The system property {0} was not set to "true" or "false".

Action: Change the system property {0} value to be either "true" or "false".
Level: 1

Type: WARNING

Impact: Security

BEA-090926: Illegal key store source value [keyStoreType="{0}", source="{1}", exception="{2}", message="{3}"]

Cause: The configured key store source value is not valid for the key store type.

Action: Correct the key store source value, ensuring that the source is appropriate for the key store type. For example, the "jks" key store type requires that the source be a file path to an existing key store file.
Level: 1

Type: ERROR

Impact: Security

BEA-090927: Illegal or unknown key store type value [keyStoreType="{0}", source="{1}"]

Cause: The configured key store type value is not recognized.

Action: Correct the key store type value. For example, the "jks" key store type requires the type value to be "jks".
Level: 1

Type: ERROR

Impact: Security

BEA-090928: Unable to instantiate key store [keyStoreType="{0}", provider="{1}", exception="{2}", message="{3}"]

Cause: Key store instantiation failure usually occurs because no appropriate specified or default provider is available. See the exception for details.

Action: Verify that key store type is correct, and that a supporting Java Cryptography Architecture (JCA) provider is available in the Java Runtime Environment. A "jks" key store provider is usually available by default. An Oracle Key Store Service (type "kss") provider is only available if Oracle Java Required Files (JRF) is installed.
Level: 1

Type: ERROR

Impact: Security

BEA-090929: Unable to load key store [keyStoreType="{0}", source="{1}", exception="{2}", message="{3}"]

Cause: A key store could fail to load due to an invalid source or password. Since key store instantiation succeeded, the key store type is valid. See the exception for details.

Action: Check the configured key store source and password values.
Level: 1

Type: ERROR

Impact: Security

BEA-090930: One of the Custom Identity Key Store attributes is not set on the channel override (NetworkAccessPointMBean). If any of the following attributes are set, then all of these attributes must be set: CustomIdentityKeyStoreFileName, CustomIdentityKeyStoreType, and either CustomIdentityKeyStorePassPhrase or CustomIdentityKeyStorePassPhraseEncrypted.

Cause: One of the following Custom Identity Key Store attributes are not set: CustomIdentityKeyStoreFileName, CustomIdentityKeyStoreType, and either CustomIdentityKeyStorePassPhrase or CustomIdentityKeyStorePassPhraseEncrypted.

Action: Ensure all of the following attributes are set: CustomIdentityKeyStoreFileName, CustomIdentityKeyStoreType, and either CustomIdentityKeyStorePassPhrase or CustomIdentityKeyStorePassPhraseEncrypted.
Level: 1

Type: ERROR

Impact: Security

BEA-090931: When overriding Custom Identity Key Store attributes, ChannelIdentityCustomized must be enabled.

Cause: ChannelIdentityCustomized is not enabled, and must be when the following Custom Identity Key Store attributes are set: CustomIdentityKeyStoreFileName, CustomIdentityKeyStoreType, and either CustomIdentityKeyStorePassPhrase or CustomIdentityKeyStorePassPhraseEncrypted.

Action: Enable ChannelIdentityCustomized.
Level: 1

Type: ERROR

Impact: Security

BEA-090932: When overriding Custom Identity Key Store attributes, CustomPrivateKeyAlias must be set on the channel override (NetworkAccessPointMBean).

Cause: CustomPrivateKeyAlias is not set on the NetworkAccessPointMBean, and must be when the following Custom Identity Key Store attributes are set: CustomIdentityKeyStoreFileName, CustomIdentityKeyStoreType, and either CustomIdentityKeyStorePassPhrase or CustomIdentityKeyStorePassPhraseEncrypted.

Action: Set the CustomPrivateKeyAlias attribute on the NetworkAccessPointMBean.
Level: 1

Type: ERROR

Impact: Security

BEA-090933: Unable to obtain private key with alias {2} from {1} keystore file : {0}

Cause: Either KeyStoreFileName or KeyStorePassPhrase or KeyStoreAlias or KeyStore private key password is incorrect.

Action: Verify that the path to the keystore, the keystore type, the password for the keystore, the alias for the keystore, and the password for the private key were specified correctly.
Level: 1

Type: ERROR

Impact: Security

BEA-090934: Loading certificates and private key from {1} keystore file {0} caused an Exception :{2}

Cause: Either KeyStoreFileName or KeyStorePassPhrase or KeyStoreAlias or KeyStore private key password is incorrect.

Action: Verify that the path to the keystore, the keystore type, the password for the keystore, the alias for the keystore, and the password for the private key were specified correctly.
Level: 1

Type: ERROR

Impact: Security

BEA-090935: Could not load a {1} keystore from the file {0}. Exception: {2}

Cause: There is an I/O or format problem with the keystore data.

Action: Verify that the path to the keystore, the keystore type, and the password for the keystore were specified correctly. Note that some keystore types (for example, JKS) do not require a password for read-only access. Read the exception text for more help on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090936: Security restarting security realm: {0}

Cause: This message is for informational purposes.

Action: Verify that the correct security realm is being restarted.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090937: Security completed restarting security realm: {0}

Cause: This message is for informational purposes.

Action: Verify that the correct security realm is restarted.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090938: Authentication failure: The specified user failed to log in.

Cause: The specified username, password, or both are incorrect.

Action: Verify the username and password.
Level: 1

Type: ERROR

Impact: Security

BEA-090939: The JWTToken is invalid.

Cause: JWT token could not satisfy the rule.

Action: See the log for detailed information and take appropriate action.
Level: 1

Type: ERROR

Impact: Security

BEA-090940: JWTIdentityAsserter received unknown token data, data should by byte[].

Cause: An invalid JWT token was supplied.

Action: Supply a valid JWT token.
Level: 1

Type: ERROR

Impact: Security

BEA-090941: The JWT token cannot pass the sign validation.

Cause: An invalid JWT token was supplied.

Action: Supply a valid JWT token.
Level: 1

Type: ERROR

Impact: Security

BEA-090942: Partitions require a realm with updated default role mapper and authorizations policies. The realm {0} does not contain the correct default policies. Create a new realm and reapply any custom policies.

Cause: Partition support requires updated default role mapping and authorization policies.

Action: Create a new realm with the same providers as the existing realm. Transfer the custom security policies from the old realm to the new realm and set the partition realm attribute to point to the new realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090943: The provider {1} in realm {0} does not support identity domains via the IdentityDomainAwareProviderMBean interface. If identity domains are configured in the domain, then all role mapper, authorization, credential mapper, and audit providers must support this interface.

Cause: The configured providers do not support identity domains.

Action: Ensure that all configured role mapper, authorization, credential mapper, and audit providers support identity domains. Remove any providers that do not support identity domains.
Level: 1

Type: WARNING

Impact: Security

BEA-090944: Inconsistent security configuration, the provider {1} in security realm {0} does not support identity domains via the IdentityDomainAwareProviderMBean interface. If identity domains are configured in the domain, then all role mapper, authorization, credential mapper, and audit providers must support this interface.

Cause: The configured providers do not support identity domains.

Action: Ensure that all configured role mapper, authorization, credential mapper, and audit providers support identity domains. Remove any providers that do not support identity domains.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090945: Security shutting down retired instance of security realm: {0}

Cause: This message is for informational purposes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090946: Security pre-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-090947: Security post-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-090948: Security starting security realm: {0}

Cause: This message is for informational purposes.

Action: Verify that the correct security realm is being restarted.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090949: Security completed starting security realm: {0}

Cause: This message is for informational purposes.

Action: Verify that the correct security realm is started.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090950: The realm "{0}" failed during shut down: {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-090951: Failed operation using security realm: {0}

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-090952: Provider configured for identity domain(s) "{0}" but login was supplied identity domain {1}

Cause: The partition or security configuration may be configured with a different identity domain than the provider.

Action: None required if the realm handles multiple identity domains. Otherwise, the security configuration may have inconsistent identity domains.
Level: 1

Type: WARNING

Impact: Security

BEA-090953: These configuration changes cannot be activated because the Administrative Identity Domain must be set on the Security Configuration when Identity Domains are in use.

Cause: The "Administrative Identity Domain" attribute is not set for the domain's SecurityConfiguration.

Action: To correct the problem, set the "AdministrativeIdentityDomain" for the domain's SecurityConfiguration.
Level: 1

Type: ERROR

Impact: Security

BEA-090954: These configuration changes cannot be activated because the Primary Identity Domain must be set on Partition {0} when Identity Domains are in use.

Cause: The "Primary Identity Domain" attribute is not set for the specified Partition.

Action: To correct the problem, set the "PrimaryIdentityDomain" for the specified Partition.
Level: 1

Type: ERROR

Impact: Security

BEA-090955: These configuration changes cannot be activated because there is no authenticator configured to support the "{0}" Identity Domain value.

Cause: No authenticator in this realm is configured to support the specified Identity Domain value.

Action: To correct the problem, configure one of the authenticator providers to support the specified identity domain. This can either be a WebLogic Server provider or a custom provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090956: Both permissions.xml and a deployment descriptor grant were found.

Cause: Both permissions.xml and a deployment descriptor grant were used to declare permissions.

Action: Use either permissions.xml or a deployment descriptor grant to declare permissions for the application. Use only one and remove the other before redeployment.
Level: 1

Type: ERROR

Impact: Security

BEA-090957: One or more of the declared permissions in permissions.xml are not allowed.

Cause: The application's permissions.xml file contains one or more permissions which are not allowed.

Action: Remove the prohibited permissions from the permissions.xml file before redeploying the application.
Level: 1

Type: ERROR

Impact: Security

BEA-090958: Security permissions declared in the "{0}" deployment descriptor are not allowed due to the server's configuration.

Cause: The server is configured to not allow Java security permissions to be declared in the Weblogic deployment descriptors.

Action: Remove Java security permissions from the deployment descriptor or change the server's security configuration before redeployment.
Level: 1

Type: ERROR

Impact: Security

BEA-090959: Java EE packaged permissions are not allowed due to the server's configuration.

Cause: The server is configured to not allow Java EE packaged permissions in the application.

Action: Remove permissions.xml or change the server's security configuration before redeployment.
Level: 1

Type: ERROR

Impact: Security

BEA-090960: The serverr's SSL configuration is not available. There will potentially be SSL handshake failures.

Cause: The server has not been able to load its SSL configuration. This usually occurs early in server startup, before Management Service runtime access is available.

Action: Verify that the Administration Server is running. If the Administration Server non-secure port is disabled, verify that the Managed Server default SSL configuration is sufficient to handshake with the Administration Server over the SSL port.
Level: 1

Type: WARNING

Impact: Security

BEA-090961: These configuration changes cannot be activated because the realm "{0}" already exists.

Cause: There is more than one realm named "{0}" configured for the domain's SecurityConfiguration.

Action: To correct the problem, change the name of each realm configured for the domain's SecurityConfiguration to be a unique name.
Level: 1

Type: ERROR

Impact: Security

BEA-090962: These configuration changes cannot be activated because the realm "{0}" is not valid.

Cause: The realm "{0}" 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-090963: The {0} provider imports a modified entry: {1}

Cause: The security provider needs to be modified because of the overwrite flag is open.

Action: Modified the imported data from the existing one.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090964: The connection to the datasource using "{0}" could not be established due to the following error: {1}.

Cause: There are multiple possible causes.

Action: Read the returned exception to determine if any action is required.
Level: 1

Type: WARNING

Impact: Security

BEA-090965: Unable to create policy with type {0}. Got exception {1}.

Cause: An internal WebLogic server error occurred when creating policy type {0}.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-090966: A failure has occurred checking for WebLogic Kernel Permission: {0}

Cause: An attempt to perform an action that requires privileges has failed.

Action: Read the returned exception to determine what action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090967: LDAP test connection failed: {0} not configured.

Cause: The connection parameters provided were incomplete.

Action: Verify that the connection parameters provided are complete.
Level: 1

Type: ERROR

Impact: Security

BEA-090968: Error processing test connection parameters {0}: {1}

Cause: The connection parameters provided were incorrect.

Action: Verify that the connection parameters provided are correct.
Level: 1

Type: ERROR

Impact: Security

BEA-090969: Identity Assertion type cannot be null

Cause: The token type was null.

Action: Null should not be passed as the token type.
Level: 1

Type: ERROR

Impact: Security

BEA-090970: Identity Assertion token cannot be null

Cause: The identity assertion token was null.

Action: Null should not be passed as the token.
Level: 1

Type: ERROR

Impact: Security

BEA-090971: Identity Assertion type of {0} is not a valid token type for the OpenID Connect Identity Assertion provider.

Cause: The token type passed in did not match the OpenID Connect Identity Assertion token type.

Action: Pass in the correct token type for the OpenID Connect Identity Assertion provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090972: Resource type already registered: "{0}"

Cause: The supplied resource type has already been registered.

Action: Specify a valid resource type.
Level: 1

Type: ERROR

Impact: Security

BEA-096500: Artifact of type SAML2 artifact-04 is not successfully constructed.

Cause: The passing parameter {0} was null or its length was not {1}.

Action: Check the parameters being passed to the SAMLArtifact constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-096501: SAML message returned in samlp:ArtifactResponse is not the right type. It should be of {0} type.

Cause: The SAML message that was returned in samlp:ArtifactResponse was not the one that samlp:ArtifactRequest requested.

Action: Check the remote ARS storage to see if there is a {0} corresponding to the artifact.
Level: 1

Type: ERROR

Impact: Security

BEA-096502: There is no SAML message in returned samlp:ArtifactResponse.

Cause: The SAML message may have been deleted because of expiration, or the client has no authority to access it.

Action: Check the remote ARS storage to see if there is an item corresponding to the artifact.
Level: 1

Type: ERROR

Impact: Security

BEA-096503: The artifact in the HTTP request is null. It should be {0} parameter in the HTTP request.

Cause: The artifact in the HTTP request was null. It should be {0} parameter in the HTTP request.

Action: Check the HTTP request to see if there is a {0} parameter with a non-null value.
Level: 1

Type: ERROR

Impact: Security

BEA-096504: Could not get binding handler of {0} type.

Cause: An internal WebLogic Server error occurred while getting the binding handler.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-096505: Could not get SAML response, it should be of {0} type.

Cause: The remote service may be down or the message exchange timed out.

Action: Check the remote service status.
Level: 1

Type: ERROR

Impact: Security

BEA-096506: The SAML response is invalid in the field {0}, expected value is {1}, actual value is {2}.

Cause: The SAML response was not the one that the SAML request expected.

Action: Check the remote service configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-096507: Could not get end point, the entityID is {0}, service type is {1}, end point index is {2}.

Cause: The end point was not registered.

Action: Check the register storage to see if there is such an endpoint.
Level: 1

Type: ERROR

Impact: Security

BEA-096508: Cannot get the key to sign {0}.

Cause: There may not be a key to sign {0}.

Action: Check the local configuration to see if there is a key for signing {0}.
Level: 1

Type: ERROR

Impact: Security

BEA-096509: Cannot get the key to verify the signature of {0}.

Cause: There may not be a key to verify the signature of {0}.

Action: Check the partner registration information to see if there is key for verifying {0}.
Level: 1

Type: ERROR

Impact: Security

BEA-096510: There is no SAML message in the HTTP request, it should be a value of {0} parameter.

Cause: There was no message in the HTTP request with a value of {0}.

Action: Check the HTTP request to confirm that there is a parameter with a non-null value.
Level: 1

Type: ERROR

Impact: Security

BEA-096511: The certificate chain sent by the SSL server is null or empty.

Cause: The remote partner acting as an SSL server did not send a certificate to authenticate itself.

Action: Check the remote partner to see if it has an SSL certificate to authenticate itself.
Level: 1

Type: ERROR

Impact: Security

BEA-096512: The SSL server cannot be trusted for {0}.

Cause: The remote partner acting as an SSL server cannot be trusted.

Action: Check the SSL certificate that the remote partner uses to authenticate itself.
Level: 1

Type: ERROR

Impact: Security

BEA-096513: Could not get partner, the entityID(or SHA-1 hash value) is {0}.

Cause: The partner is not registered.

Action: Check the register storage to see if there is such a partner.
Level: 1

Type: ERROR

Impact: Security

BEA-096514: Could not get Transport Layer Certificate from partner whose entityId is {0}.

Cause: The partner did not register its Transport Layer Certificate information.

Action: Check the register storage to see if this partner has a Transport Layer Certificate.
Level: 1

Type: ERROR

Impact: Security

BEA-096515: The SSL client is expected to authenticate, but cannot get the key and certificate.

Cause: The SSL key and certificate could not be retrieved.

Action: Check the metadata to see if there is a Transport Layer Certificate and key.
Level: 1

Type: ERROR

Impact: Security

BEA-096516: Could not get SAML signature from the HTTP request, it should be a {0} parameter.

Cause: If there is no SAML signature in the HTTP request, there should also be no signature algorithm in the HTTP request.

Action: Check the HTTP request. The signature and signature algorithm should appear at the same time.
Level: 1

Type: ERROR

Impact: Security

BEA-096517: The SAML message was signed but could not get a signature from it.

Cause: The SAML message was signed but there was no signature to retrieve.

Action: Check the SAML message for the signature.
Level: 1

Type: ERROR

Impact: Security

BEA-096518: The signature is invalid.

Cause: The signature was verified but was not valid.

Action: Provide a valid signature.
Level: 1

Type: ERROR

Impact: Security

BEA-096519: Could not get artifact when storing the SAML message, have no idea whether the SAML message was stored successfully.

Cause: There may have been an error when generating the artifact.

Action: Check the log files for an error.
Level: 1

Type: ERROR

Impact: Security

BEA-096520: Could not receive a valid SAML request of type "{0}" from HTTP request.

Cause: A valid SAML request of type "{0}" was not received from the HTTP request.

Action: Check whether the configuration of the corresponding partner is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-096521: Could not receive a valid SAML response of type "{0}" from HTTP request.

Cause: A valid SAML response of type "{0}" was not retrieved from the HTTP request.

Action: Check whether the configuration of the corresponding partner is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-096522: Error occurs when signing {0}.

Cause: Error occurs when signing {0}.

Action: Error occurs when signing {0}.
Level: 1

Type: ERROR

Impact: Security

BEA-096523: Authentication failed.

Cause: Authentication failed due to an invalid certificate or an invalid username or password.

Action: Ensure that your certificate or your username and password are correct.
Level: 1

Type: ERROR

Impact: Security

BEA-096524: Invalid Identity Assertion token object for specified token type.

Cause: An internal WebLogic server error occurred while determining the token type.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-096525: Signature required but assertion is not signed.

Cause: An unsigned SAML assertion was received where the SAML configuration required a signed assertion.

Action: Check the SAML partner configuration or contact the SAML Identity Provider.
Level: 1

Type: ERROR

Impact: Security

BEA-096526: There must be a subject in assertion.

Cause: A SAML assertion was received in which the SAML Subject was not provided.

Action: Contact the SAML Identity Provider for information on how to correct the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-096527: No SubjectConfirmation in assertion.

Cause: A SAML assertion was received in which the SAML Subject Confirmation was not provided.

Action: Contact the SAML Identity Provider for information on how to correct the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-096528: Unsupported assertion type: {0}.

Cause: A SAML assertion was received in which the SAML Subject Confirmation is not supported.

Action: Contact the SAML Identity Provider for information on how to correct the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-096529: Signature required but no valid certificate in the specified partner configuration.

Cause: A signature was required but the certificate has expired, is not yet valid or is undefined in the specified partner configuration.

Action: Provide a valid certificate for the partner.
Level: 1

Type: ERROR

Impact: Security

BEA-096530: Cannot get the key to verify the signature.

Cause: An improper key was provided.

Action: Provide a proper key to verify the signature.
Level: 1

Type: ERROR

Impact: Security

BEA-096531: The signature is invalid.

Cause: The signature was verified but was not valid.

Action: Provide a valid signature.
Level: 1

Type: ERROR

Impact: Security

BEA-096532: Invalid version found in the {0} document: {1}.

Cause: The sender sent a document that is not version 2.0.

Action: Fix the SAML sender.
Level: 1

Type: ERROR

Impact: Security

BEA-096533: Certificate in assertion's keyinfo does not match configured signing certificate.

Cause: A SAML assertion was received where the SAML KeyInfo does not match the SAML partner entry.

Action: Check the SAML partner configuration or contact the SAML Identity Provider.
Level: 1

Type: ERROR

Impact: Security

BEA-096534: No issuer in the assertion.

Cause: A SAML assertion was received where the SAML Issuer is not supplied or the SAML Issuer is empty.

Action: Contact the SAML Identity Provider for information on how to correct the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-096535: The Issuer in {0} is invalid: {1}.

Cause: The sender sent an invalid SAML document that contains an invalid Issuer URI.

Action: Ask the SAML requester to fix this problem.
Level: 1

Type: ERROR

Impact: Security

BEA-096536: Invalid issuer format: {0}.

Cause: The sender sent a document that contains an invalid issuer format attribute.

Action: Ask the SAML requester to send a correct document.
Level: 1

Type: ERROR

Impact: Security

BEA-096537: Assertion is not yet valid ({0} condition).

Cause: The received SAML assertion is not yet valid.

Action: Check the SAML configuration, the system clock or contact the SAML Identity Provider.
Level: 1

Type: ERROR

Impact: Security

BEA-096538: Assertion has expired ({0} condition).

Cause: The received SAML assertion has expired.

Action: Check the SAML configuration, the system clock or contact the SAML Identity Provider.
Level: 1

Type: ERROR

Impact: Security

BEA-096539: AudienceRestriction condition not satisfied (no matching audience).

Cause: The received SAML assertion audience restrictions where not satisfied.

Action: Check the SAML partner configuration or contact the SAML Identity Provider.
Level: 1

Type: ERROR

Impact: Security

BEA-096540: The assertion: {0} cannot be used again.

Cause: The received SAML assertion has already been consumed and cannot be used again.

Action: Contact the SAML Identity Provider for information on how to correct the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-096541: Web SSO profile must be bearer confirmation method.

Cause: A SAML assertion was received where the SAML Subject Confirmation must be of Bearer type.

Action: Contact the SAML Identity Provider for information on how to correct the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-096542: No NameID in assertion.

Cause: A SAML assertion was received in which the SAML Issuer is not supplied or the SAML Issuer is empty.

Action: Contact the SAML Identity Provider for information on how to correct the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-096543: The partner: {0} does not exist or is disabled.

Cause: The partner: {0} does not exist or is disabled.

Action: Register or enable the specified partner.
Level: 1

Type: ERROR

Impact: Security

BEA-096544: Cannot find identity provider partner, partnerName: {0}, request URI: {1}.

Cause: Cannot find identity provider partner, partnerName: {0}, request URI: {1}.

Action: Check the identity provider partner setting.
Level: 1

Type: ERROR

Impact: Security

BEA-096545: Cannot find single sign-on services for partner: {0}.

Cause: No single sign-on services are defined for partner: {0}.

Action: Define single sign-on services for partner: {0}.
Level: 1

Type: ERROR

Impact: Security

BEA-096546: Cannot get the single sign-on sign key to sign the {0} in the key store.

Cause: Either no single sign-on sign key is defined in the local configuration or the key/keystore is invalid.

Action: Correct the key configuration for SAML services.
Level: 1

Type: ERROR

Impact: Security

BEA-096547: The status code of SAML2 response indicates that the request failed: {0}.

Cause: The SAML2 response from the identity provider partner indicates that the request failed.

Action: Contact the identity provider partner to get the reason.
Level: 1

Type: ERROR

Impact: Security

BEA-096548: Cannot find identity provider partner for issuer URI: {0}.

Cause: The identity provider partner for issuer URI: {0} is not defined.

Action: Define the identity provider partner for issuer URI: {0}.
Level: 1

Type: ERROR

Impact: Security

BEA-096549: Cannot get a valid certificate in partner registry to verify {0} for partner {1}.

Cause: The certificate has expired, is not yet valid or is undefined for the specified partner.

Action: Provide a valid certificate for the partner.
Level: 1

Type: ERROR

Impact: Security

BEA-096550: Failed to create session for identity: {0}.

Cause: This usually is caused by one of the LoginSessionListeners failing to create a session.

Action: Ensure that all the listeners work properly or try to re-install.
Level: 1

Type: ERROR

Impact: Security

BEA-096551: {0} binding of local configuration is not enabled.

Cause: The binding: {0} of the local configuration is not enabled.

Action: Enable the binding: {0} for the local configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-096552: Illegal destination: {0} of assertion response.

Cause: The SAML2 response received from the identity provider partner is illegal.

Action: Contact the identity provider partner to ensure that the generated response is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-096554: Cannot find request for InResponseTo: {0} in response.

Cause: The SAML2 response received from the identity provider partner is illegal.

Action: Contact the identity provider partner to ensure that the generated response is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-096555: Attribute: {0} should not be empty.

Cause: The SAML2 response received from the identity provider partner is illegal.

Action: Contact the identity provider partner to ensure that the generated response is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-096556: Attribute: {0} should be omitted.

Cause: The SAML2 response received from the identity provider partner is illegal.

Action: Contact the identity provider partner to ensure that the generated response is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-096557: Illegal confirmation method: {0}.

Cause: The SAML2 response received from the identity provider partner is illegal.

Action: Contact the identity provider partner to ensure that the generated response is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-096558: Illegal Recipient: {0} for the subject confirmation data.

Cause: The SAML2 response received from the identity provider partner is illegal.

Action: Contact the identity provider partner to ensure that the generated response is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-096559: Illegal InResponseTo: {0} for the subject confirmation.

Cause: The SAML2 response received from the identity provider partner is illegal.

Action: Contact the identity provider partner to ensure that the generated response is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-096560: The Issuer element cannot have NameQualifier, SPNameQualifer and SPProviderID.

Cause: The SAML requester sent a document that contains an invalid <Issuer>.

Action: Ask the SAML Requester to fix this.
Level: 1

Type: ERROR

Impact: Security

BEA-096561: Identity provider partner: {0} is not enabled.

Cause: The specified identity provider partner is not enabled.

Action: Enable the identity provider partner.
Level: 1

Type: ERROR

Impact: Security

BEA-096562: Errors occurred when sending {0}.

Cause: An internal WebLogic server error occurred when sending A SAML assertion.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-096563: Errors occurred when receiving {0}.

Cause: An internal WebLogic Server error occurred when A SAML assertion was requested.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-096565: Artifact requester authentication failed.

Cause: There was an invalid basic auth/certificate.

Action: Check the log for more details and take appropriate action.
Level: 1

Type: ERROR

Impact: Security

BEA-096566: The SAML2 identity provider service is disabled.

Cause: The SAML2 identity provider service is disabled in the local configuration, but a request was sent to this service.

Action: Enable the identity provider in the local configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-096567: Cannot find service provider partner with the specified URI {0}.

Cause: The partner may be misconfigured in the partner registry, or this issuer is not enabled/configured in the registry.

Action: Configure the partner correctly in the partner registry, or just ignore it if this issuer should not be served. It could also be errors in the service provider that issues this request.
Level: 1

Type: ERROR

Impact: Security

BEA-096568: The service provider partner {0} is disabled.

Cause: The specified service provider partner is disabled in the partner registry.

Action: Enable the partner in the partner registry.
Level: 1

Type: ERROR

Impact: Security

BEA-096569: Cannot authenticate user in passive mode.

Cause: The AuthnRequest wants the user to be authenticated in passive mode, but the Identity Provider is not able to do this.

Action: Ensure that the service provider does not send passive requests, or just ignore this error.
Level: 1

Type: ERROR

Impact: Security

BEA-096570: The user is accessing the login return URL of SAML2 service, however, this user is not authenticated.

Cause: A user accidentally accessed this page or bookmarked it, or the login application is behaving incorrectly.

Action: Fix the login application.
Level: 1

Type: ERROR

Impact: Security

BEA-096571: There is no <AuthnRequest> object in user's session.

Cause: The user's session may have expired. The user must do the single sign-on process from the very beginning. This could also be caused by an incorrect login application.

Action: Start the single sign-on process from the beginning, or fix the login application.
Level: 1

Type: ERROR

Impact: Security

BEA-096572: The user is accessing the Identity Provider initiator service, but is not authenticated yet.

Cause: The user accidentally accessed this page or bookmarked it, or the login application is behaving incorrectly.

Action: Fix the login application or the page links to this URL.
Level: 1

Type: ERROR

Impact: Security

BEA-096573: The Identity provider-initiated single sign-on requires a parameter {0}, but the request does not have one.

Cause: The user or the link did not append the parameter.

Action: Append the parameter in the request.
Level: 1

Type: ERROR

Impact: Security

BEA-096574: Cannot find partner with name: {0}

Cause: The partner with name {0} does not exist in the partner registry.

Action: Add a partner with the indicated name, or rename a partner to this name.
Level: 1

Type: ERROR

Impact: Security

BEA-096575: The URL for relay state is too long.

Cause: The service provider-initiated single sign-on requester sent a request URL longer than 80 bytes.

Action: If the URL for the service provider is too long, do not send it.
Level: 1

Type: ERROR

Impact: Security

BEA-096576: Received a SAML document that is not a AuthnRequest document, but {0}.

Cause: The SAML requester sent an invalid document to the identity provider single sign-on service.

Action: Ask the requester to send a valid document.
Level: 1

Type: ERROR

Impact: Security

BEA-096577: Failed to receive {0} document from the requester.

Cause: Review other messages in the log for the cause.

Action: Fix the error in the document or network.
Level: 1

Type: ERROR

Impact: Security

BEA-096578: Cannot generate assertion for the user.

Cause: There may be an error in the credential mapper, or the SAML2 credential mapper is not configured correctly.

Action: Configure the SAML2 credential mapper correctly.
Level: 1

Type: ERROR

Impact: Security

BEA-096579: Failed to unmarshal the assertion from the credential mapper.

Cause: An internal WebLogic Server error occurred during unmarshaling.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-096580: No assertion consumer services configured in the {0} partner.

Cause: No assertion consumer services are configured in the partner.

Action: Configure the ACS service for this partner.
Level: 1

Type: ERROR

Impact: Security

BEA-096581: The destination attribute of <AuthnRequest> does not match local configuration.

Cause: Either the request was sent to the wrong place, or the request document is wrong.

Action: Fix the SAML requester to match the destination attribute.
Level: 1

Type: ERROR

Impact: Security

BEA-096582: <SubjectConfirmation> cannot exist in the <Subject> element of <AuthnRequest>

Cause: The SAML requester sent an <AuthnRequest>, its <subject> contains a <SubjectConfirmation>, which is not allowed by the SAML specification.

Action: Fix the SAML requester.
Level: 1

Type: ERROR

Impact: Security

BEA-096583: Requested NameId format not supported, only urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified is supported.

Cause: The SAML requester sent a request that is not supported yet.

Action: Fix the SAML requester to send a request without the name id format, or set the format to "unspecified".
Level: 1

Type: ERROR

Impact: Security

BEA-096584: <RequestedAuthnContext> is not currently supported.

Cause: The SAML requester sent an invalid <AuthnRequest> document.

Action: Fix the SAML requester to send a request without <RequestedAuthnContext>.
Level: 1

Type: ERROR

Impact: Security

BEA-096585: The SPNameQualifier is not supported in <AuthnRequest>.

Cause: The SAML requester sent a request that is not supported yet.

Action: Fix the SAML requester to not send such a document.
Level: 1

Type: ERROR

Impact: Security

BEA-096586: Find service provider partner by issuer URI {0} error.

Cause: The exception was caused while searching for the service provider partner from the store by the issuer uri.

Action: Check the store service.
Level: 1

Type: ERROR

Impact: Security

BEA-096587: Find service provider partner by name {0} error.

Cause: This exception was caused while searching for the service provider partner from the store by name.

Action: Check the store service.
Level: 1

Type: ERROR

Impact: Security

BEA-096588: Find identity provider partner by name {0} error.

Cause: This exception was caused while searching for the identity provider partner from the store by name.

Action: Check the store service.
Level: 1

Type: ERROR

Impact: Security

BEA-096589: Find partner by name {0} error.

Cause: This exception was caused while searching for the partner from the store by name.

Action: Check the store service.
Level: 1

Type: ERROR

Impact: Security

BEA-096590: Could not get local entity ID for checking audience in assertion.

Cause: The service provider has no entity ID.

Action: Check the service provider local configuration to see whether it has an entity ID.
Level: 1

Type: ERROR

Impact: Security

BEA-096591: Could not get partner from partner registry by name.

Cause: There is no such partner in the partner registry.

Action: Check the partner registry to see whether this partner exists.
Level: 1

Type: ERROR

Impact: Security

BEA-096592: Partner is not enabled in partner registry.

Cause: This partner is in the partner registry, but the partner is not enabled.

Action: Check the partner registry to see whether the partner is enabled.
Level: 1

Type: ERROR

Impact: Security

BEA-096593: Audience cannot be empty.

Cause: The assertion contains an empty audience.

Action: Check the CredentialMapper.
Level: 1

Type: ERROR

Impact: Security

BEA-096594: Web single sign-on service provider partner entity ID is empty, could not create assertion.

Cause: The SAML partner entry does not have an Entity ID or the Entity ID is empty.

Action: Check and import the SAML service provider metadata file or contact the SAML service provider to obtain the Entity ID.
Level: 1

Type: ERROR

Impact: Security

BEA-096595: Confirmation method should not be empty.

Cause: The provider partner has no confirmation method.

Action: Check the partner information to make sure it has a confirmation method.
Level: 1

Type: ERROR

Impact: Security

BEA-096596: Assertion signing certificate should not be empty while wantAssertionSigned is TRUE.

Cause: The provider partner has no assertion signing certificate while wantAssertionSigned is TRUE.

Action: Check the partner information to make sure it has an assertion signing certificate.
Level: 1

Type: ERROR

Impact: Security

BEA-096597: Artifact POST form should not be empty while isArtifactUsePost is TRUE.

Cause: The provider partner has no artifact POST form while isArtifactUsePost is TRUE.

Action: Check the partner information to make sure it has an artifact POST form.
Level: 1

Type: ERROR

Impact: Security

BEA-096598: Single sign-on signing certificate should not be empty while assertion/artifact request/authn request wants to be signed.

Cause: The provider partner has no single sign-on signing certificate while the assertion/artifact request/authn request wants to be signed.

Action: Check the partner information to make sure it has a single sign-on signing certificate.
Level: 1

Type: ERROR

Impact: Security

BEA-096599: Issuer URI should not be empty.

Cause: The provider partner has no issuer URI.

Action: Check the partner information to make sure it has an issuer URI.
Level: 1

Type: ERROR

Impact: Security

BEA-096600: No SAML2 service entity ID configured.

Cause: The SAML2 service entity ID is not configured.

Action: Configure the SAML2 service entity ID.
Level: 1

Type: ERROR

Impact: Security

BEA-096601: No SAML2 service published site URL configured.

Cause: The SAML2 service published site URL is not configured.

Action: Configure the SAML2 service published site URL.
Level: 1

Type: ERROR

Impact: Security

BEA-096602: No SAML2 service single sign-on signing key alias configured.

Cause: The SAML2 service single sign-on signing key alias is not configured.

Action: Configure a SAML2 service single sign-on signing key alias.
Level: 1

Type: ERROR

Impact: Security

BEA-096603: No SAML2 service single sign-on signing key pass phrase configured.

Cause: The SAML2 service single sign-on signing key pass phrase is not configured.

Action: Configure the SAML2 service single sign-on signing key pass phrase.
Level: 1

Type: ERROR

Impact: Security

BEA-096604: No SAML2 service login return query parameter are configured.

Cause: The SAML2 service login return query parameter is not configured.

Action: Configure the SAML2 service login return query parameter.
Level: 1

Type: ERROR

Impact: Security

BEA-096605: Entity ID should not be empty.

Cause: The provider partner has no entity ID.

Action: Check the partner information to make sure it has an entity ID.
Level: 1

Type: ERROR

Impact: Security

BEA-096606: Name should not be empty.

Cause: The provider partner has no name.

Action: Check the partner information to make sure it has a name.
Level: 1

Type: ERROR

Impact: Security

BEA-096607: Single sign-on services should not be empty.

Cause: Provider partner has no single sign-on services.

Action: Check the partner information to make sure it has single sign-on services.
Level: 1

Type: ERROR

Impact: Security

BEA-096608: Assertion consumer services should not be empty.

Cause: The provider partner has no assertion consumer services.

Action: Check the partner information to make sure it has assertion consumer services.
Level: 1

Type: ERROR

Impact: Security

BEA-096609: Illegal published site url: {0}.

Cause: The published site url is illegal.

Action: Check the partner information to make sure it has a legal published site url.
Level: 1

Type: ERROR

Impact: Security

BEA-096610: Cannot resolve IssuerURI for SAML Assertion.

Cause: The system could not resolve the IssuerURI for the SAML Assertion from the context and credential mapper MBean.

Action: Check the context and credential mapper MBean to make sure that the issuerURI is not empty.
Level: 1

Type: ERROR

Impact: Security

BEA-096611: Cannot get key info for key {0} from key service.

Cause: The key info got from key service for key {0} is empty.

Action: Check the key store service for key {0}.
Level: 1

Type: WARNING

Impact: Security

BEA-096612: Decrypt password {0} error.

Cause: The password {0} could not be decrypted, causing an exception.

Action: Check the key and the password.
Level: 1

Type: WARNING

Impact: Security

BEA-096613: Clearing cache {0}.

Cause: The SAML cache is being cleared.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-096614: Cache {0} cleared.

Cause: The SAML cache has been cleared.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-096615: The SAML credential cache item's ttl value {0} is smaller than the minimum viable ttl {1} in milliseconds and will not be cached.

Cause: The SAML credential cache is unable to retain the item due to the length of the timeout.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-096616: The value of max to return is negative.

Cause: The value of max to return cannot be negative.

Action: Check the value of max to return and make sure that the value is not negative.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-096617: The value for contact person type is illegal.

Cause: The value for the contact person type is not legal. The legal value must be in one of "technical", "support", "administrative", "billing" or "other".

Action: Choose one of the legal values and try again.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-096618: Invalid keystore configuration.

Cause: The keystore configuration is not correct.

Action: Configure a valid value and try again.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-096619: Key name is null or empty.

Cause: The key name is null or empty when updating/retrieving key information.

Action: Choose a valid key name and try again.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-096620: Invalid key information.

Cause: At least one of key name, alias or passphrase is not correct.

Action: Choose a valid value and try again.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-096621: SAML2 Service cannot be initialized:{0}

Cause: Errors occurred while initializing the SAML2 service.

Action: Check and change the SAML2 configuration and try again.
Level: 1

Type: ERROR

Impact: Security

BEA-096622: ForceAuthn and IsPassive cannot both be true.

Cause: ForceAuthn wants to authenticate the user freshly, but IsPassive requests that the identity provider not do this.

Action: Change one of the values to false.
Level: 1

Type: ERROR

Impact: Security

BEA-096623: Item has already expired on {0}, it will not be cached.

Cause: The configured timeout may be too short.

Action: Check the timeout configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-096624: The "{1}" parameter passed to "{0}" must not be null.

Cause: A null "{1}" parameter was passed to "{0}".

Action: Ensure that a valid reference is passed.
Level: 1

Type: ERROR

Impact: Security

BEA-096625: The parameter MaxCacheSize or timeout must not be a negative number.

Cause: The parameter MaxCacheSize or timeout cannot be a negative number.

Action: Change the MaxCacheSize parameter or timeout to zero or a positive number.
Level: 1

Type: ERROR

Impact: Security

BEA-096626: The partner name cannot be changed at partner update operation.

Cause: The user tried to change the read-only partner name.

Action: Set the partner name back to the original name.
Level: 1

Type: ERROR

Impact: Security

BEA-096627: There is no login URL configured in Identity Provider Site.

Cause: No login URL was configured in the Identity Provider Site.

Action: Configure a valid login URL in SingleSignOnServicesMBean.
Level: 1

Type: ERROR

Impact: Security

BEA-096628: The value configured for NameMapper attribute: {0} is not valid.

Cause: The name mapper class {0} is not in the classpath or it does not implement a name mapper interface.

Action: Ensure that the name mapper class {0} is in the classpath and implements a name mapper interface.
Level: 1

Type: ERROR

Impact: Security

BEA-096629: The confirmation method passed through Context handler: {0} is not valid.

Cause: An invalid confirmation method was passed through the Context handler.

Action: Make sure the confirmation method passed through Context handler {0} has a valid value.
Level: 1

Type: ERROR

Impact: Security

BEA-096630: Using expired certificate at alias {0} for signing.

Cause: An attempt was made to use an expired certificate at alias {0} for signing, but allow expired cert is false.

Action: Use a valid certificate for signing.
Level: 1

Type: ERROR

Impact: Security

BEA-096631: Using not yet valid certificate at alias {0} for signing.

Cause: A not yet valid certificate was used at alias {0} for signing, but allow expired cert is false.

Action: Use a valid certificate for signing.
Level: 1

Type: ERROR

Impact: Security

BEA-096632: Binding type {0} is unsupported, endpoint with this binding is filtered out from partner.

Cause: The binding type that was used is not supported.

Action: Use a binding type that is supported.
Level: 1

Type: WARNING

Impact: Security

BEA-096633: The partner metadata file does not contain an XML root element of <EntityDescriptor>.

Cause: The partner metadata file content is not supported.

Action: Update the partner metadata content or obtain a new partner metadata file.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-097000: Service info was not found for service to shut it down, {0}

Cause: Service info was not found when shutting down a service.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097001: Configuration problems detected.

Cause: A bad configuration was supplied.

Action: Check and fix the configuration.
Level: 1

Type: ERROR

Impact: Engine

BEA-097002: Configuration canno be modified after the engine has been started.

Cause: This is an internal WebLogic Server error indicating that the service engine configuration was modified after the engine was started.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097004: Engine has already been started.

Cause: An attempt was made to start the engine after it had been started.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097005: Unable to find ServiceConfig.

Cause: This is an internal WebLogic Server error indicating that the service engine cannot be configured.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097006: Duplicate service name {0}.

Cause: The service engine was configured with a duplicate service name.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097007: Logger not found.

Cause: The service engine could not find the logger.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097008: An attempt was made to access the ServiceEngine after it had already been shut down.

Cause: This is an internal WebLogic Server error indicating that the service engine was accessed after being shut down.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097009: Engine already shut down.

Cause: This is an internal WebLogic Server error indicating that the service engine has already been shut down.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097010: Service {0} not found.

Cause: This is an internal WebLogic Server error indicating that the service engine cannot find the service.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097011: Service {0} not exposed.

Cause: This is an internal WebLogic Server error indicating that the service engine looked up a service that it cannot expose.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097012: Service {0} does not implement ServiceLifecycleSpi.

Cause: This is an internal WebLogic Server error indicating that the service engine was configured with a service that it cannot use.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097013: Null service {0} loaded.

Cause: This is an internal WebLogic Server error indicating that the service engine was configured with a null service.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097014: Classloader not found for service {0}.

Cause: This is an internal WebLogic Server error indicating that the service engine was configured with a service but the service's classloader could not be found.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097015: Failure loading service {0} using class {1}.

Cause: This is an internal WebLogic Server error indicating that the service engine could not load a service.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097016: Service {0} is dependent upon {1} which does not exist.

Cause: This is an internal WebLogic Server error indicating that the service engine could not find a dependent service.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097017: Service name not specified.

Cause: This is an internal WebLogic Server error indicating that the service engine could not find a service.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097018: Attempt to remove lifecycle impl for {0} when {1} dependencies still exist.

Cause: This is an internal WebLogic Server error indicating that the service engine attempted to remove a service that still has dependencies.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097019: Attempt to remove dependencies for {0} when no dependencies still exist.

Cause: This is an internal WebLogic Server error indicating that the service engine attempted to remove dependencies for a service when no dependencies exist.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097020: Internal consistency failure in {0}

Cause: This is an internal WebLogic Server error.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097021: Manageable Service {0} not found.

Cause: This is an internal WebLogic Server error. An attempt was made to look up a manageable service but it was not found.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097022: Service {0} is not manageable.

Cause: This is an internal WebLogic Server Error. An attempt was made to look up a manageable service and a service with the requested name was found, but it was not a manageable service.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Engine

BEA-097500: {0} requires a {1} to be supplied for configuration but it was not supplied.

Cause: The configuration supplied to {0} was incorrect.

Action: Ensure that the configuration supplied for {0} is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-097501: {1} supplied to {0} is missing {2}

Cause: The configuration supplied to {0} was incorrect.

Action: Ensure that the configuration supplied for {0} is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-097502: MaxIdentitiesInCache value for the IdentityCacheService is invalid {0}

Cause: The value supplied for MaxIdentitiesInCache for the IdentityCacheService was invalid.

Action: Change MaxIdentitiesInCache to a valid value.
Level: 1

Type: ERROR

Impact: Security

BEA-097503: The configured CertPathBuilder service returned a non X.509 certificate path.

Cause: The CertPathBuilder was configured with an incorrect certificate path for an X.509 certificate.

Action: Correct the configured CertPathBuilder service.
Level: 1

Type: ERROR

Impact: Security

BEA-097504: AdjudicationService does not have an AdjudicatorV2Name but has multiple AccessDecision providers.

Cause: The AdjudicationService has multiple AccessDecision providers, but there are no providers that implement the AdjudicatorV2 interface.

Action: Configure an adjudicator that implements the AdjudicatorV2 interface.
Level: 1

Type: ERROR

Impact: Security

BEA-097505: None of the configured {0} support JAAS login.

Cause: There are no authentication providers configured to support JAAS login.

Action: Configure at least one authentication provider that supports JAAS login.
Level: 1

Type: ERROR

Impact: Security

BEA-097506: An AuthorizationProvider returned a null AccessDecision.

Cause: An AuthorizatonProvider was not able to return an AccessDecision.

Action: Examine the AuthorizationProvider.
Level: 1

Type: ERROR

Impact: Security

BEA-097507: {0} may only be called if hasChallengeIdentityCompleted returns false.

Cause: This is an internal WebLogic Server error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-097508: {0} may only be called if hasChallengeIdentityCompleted returns true.

Cause: This is an internal WebLogic Server error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-097509: {0} returned a null {1}.

Cause: There is a configuration problem because a null object was returned.

Action: Examine the specific objects referenced in the error message to see what may be the cause.
Level: 1

Type: ERROR

Impact: Security

BEA-097510: Got back a null {0} object.

Cause: There is a configuration problem because a null object was returned.

Action: Examine the specific object referenced in the error message to see what may be the cause.
Level: 1

Type: ERROR

Impact: Security

BEA-097511: Expected a {0} object but did not get one.

Cause: There is a configuration problem because an object was expected and a different object was returned.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-097512: Multiple challenges not supported.

Cause: An attempt has made to handle multiple challenges with a provider that does not support it.

Action: Correct the code or configure a ChallengeIdentityAsserter that supports multiple challenges.
Level: 1

Type: ERROR

Impact: Security

BEA-097513: Incorrect Cert Path type, expecting a {0} type.

Cause: The wrong type of Cert Path was passed due to incorrect configuration.

Action: Correct the configured CertPathBuilder service.
Level: 1

Type: ERROR

Impact: Security

BEA-097514: Multiple {0} support the token type {1}.

Cause: The configuration is not correct.

Action: Remove one of the objects supporting this token token type from the configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-097515: Unsupported token type {0}

Cause: No objects are configured to support the specified token type.

Action: Configure an object that supports this token type.
Level: 1

Type: ERROR

Impact: Security

BEA-097516: Unable to validate a non X.509 certificate path.

Cause: Not all certificate paths are of type X.509.

Action: Correct the configured CertPathBuilder service to ensure that all certificate paths are of type X.509.
Level: 1

Type: ERROR

Impact: Security

BEA-097517: A certificate is self signed but it is not the last certificate in the chain, see {0}

Cause: There is a certificate chain but one of the certificates is self signed.

Action: Ensure that the certificate chain is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-097518: Issue DN mismatch error. Issued: {0} does not match issuer: {1}.

Cause: There is an inconsistent certificate chain. The issuer DN of a certificate did not match the subject DN of the next certificate in the chain.

Action: Ensure that the the certificates in the chain correctly refer to each other.
Level: 1

Type: ERROR

Impact: Security

BEA-097519: Certificate not signed by issuer. Certificate: {0} not signed by issuer: {1}.

Cause: There is an inconsistent certificate chain. A certificate was not signed by the next certificate in the chain.

Action: Ensure that the the certificates in the chain correctly refer to each other.
Level: 1

Type: ERROR

Impact: Security

BEA-097520: Capacity {0} greater than maximum {1}

Cause: The specified queue capacity is too large.

Action: Reduce the specified queue capacity.
Level: 1

Type: ERROR

Impact: Security

BEA-097521: Maximum capacity {0} is greater than the allowed {1}

Cause: The specified maximum queue capacity is larger than allowed.

Action: Reduce the specified maximum capacity.
Level: 1

Type: ERROR

Impact: Security

BEA-097522: Initial specified capacity of {0} is illegal.

Cause: The specified capacity is illegal.

Action: Specify a correct capacity.
Level: 1

Type: ERROR

Impact: Security

BEA-097523: Illegal load factor.

Cause: An illegal load factor was specified.

Action: Specify a load factor greater than 0 and less than 1.
Level: 1

Type: ERROR

Impact: Security

BEA-097524: No appropriate registered configuration to handle the AppConfigurationEntry named: {0}

Cause: No appropriate JAASConfiguration has been registered.

Action: Register the appropriate JAASConfiguration
Level: 1

Type: ERROR

Impact: Security

BEA-097525: Null JAASConfiguration.

Cause: An attempt was made to register a null JAASConfiguration.

Action: Register a non-null JAASConfiguration.
Level: 1

Type: ERROR

Impact: Security

BEA-097526: Duplicate JAASConfiguration.

Cause: An attempt was made to register a JAASConfiguration twice.

Action: Do not attempt to register the JAASConfiguration twice.
Level: 1

Type: ERROR

Impact: Security

BEA-097527: JAASConfiguration not registered.

Cause: An attempt was made to unregister a JAASConfiguration that is not registered.

Action: Do not attempt to unregister an unregistered JAASConfiguration.
Level: 1

Type: ERROR

Impact: Security

BEA-097528: A null {0} was specified.

Cause: This method cannot accept a null argument.

Action: Do not pass in a null argument.
Level: 1

Type: ERROR

Impact: Security

BEA-097529: The principal validators {0} and {1} both validate the same principal types.

Cause: There can only be one principal validator for each principal type.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-097530: No {1} found in method {0}

Cause: Objects should have been configured but were not.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-097531: Method {0} was unable to sign a principal.

Cause: Something was wrong with the principal or the principal validator was incorrect.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-097532: Null parameter supplied to method {0}.

Cause: A parameter was not correctly specified. This is most likely a coding error.

Action: Check the code for an incorrectly specified parameter.
Level: 1

Type: ERROR

Impact: Security

BEA-097533: SecurityProvider service class name for {0} is not specified.

Cause: The SecurityProviderConfig does not contain a SecurityProvider service class name.

Action: Examine the specific objects referenced in the error message to see what may be the cause, and take appropriate action.
Level: 1

Type: ERROR

Impact: Security

BEA-097534: Failed to obtain an instance of class {0}.

Cause: There is a possible configuration problem. A {0} class name is invalid, or is not in the class path. It does not have a public no argument constructor, or has the constructor which failed to execute.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-097535: The configuration does not define a store, but providers that require a store are in use.

Cause: There is no store servoce defined in the configuration.

Action: Configure a store service.
Level: 1

Type: ERROR

Impact: Security

BEA-097536: The {0} service can not be found for {1}.

Cause: A null was returned when doing a service lookup.

Action: Check the configuration to see if the missing service was actually configured.
Level: 1

Type: ERROR

Impact: Security

BEA-097537: The {2} setting supplied in the {1} configuration to {0} is invalid.

Cause: The configuration setting {2} supplied in {1} to {0} is incorrect.

Action: Ensure that the configuration supplied for {0} is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-097538: The keystore {0} of type {1} could not be accessed.

Cause: The keystore {0} of type {1} could not be accessed and the configuration may be incorrect.

Action: Ensure that the keystore {0} of type {1} can be accessed.
Level: 1

Type: ERROR

Impact: Security

BEA-097539: Connection to the database is currently unavailable.

Cause: The database configuration may be incorrect or the database was not available.

Action: Ensure that the database configuration is correct and that the database is available.
Level: 1

Type: ERROR

Impact: Security

BEA-097540: Property could not be parsed and will be skipped. Format must be name=value. Format found: {0}

Cause: The properties configured for the database pool could not be parsed and will be skipped.

Action: Check the format of the properties supplied to the configuration
Level: 1

Type: WARNING

Impact: Security

BEA-097541: {0} requires a {1}, this was not available.

Cause: This may be a coding error or a configuration error.

Action: Check for configuration errors. If the configuration appears valid, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Security

BEA-097542: Connection was not found by name {0}.

Cause: The named SQL connection was not found.

Action: Check the log to see whether there is a connection pool checkout failure and determine the cause.
Level: 1

Type: ERROR

Impact: Security

BEA-097543: Store service properties must not be null.

Cause: This may be a store service configuration error.

Action: Check the store service configuration.
Level: 1

Type: WARNING

Impact: Security

BEA-097544: Get a null {0} value in store service properties.

Cause: A data store connection was not specified in the store service properties.

Action: Check the store service configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-097545: The internal state of the token is not consistent, possibly due to a failure during encoding/decoding the token.

Cause: This is an internal WebLogic Server error.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-097546: Timestamp is not of the correct length: {0}.

Cause: The timestamp format was not correct.

Action: Fix the timestamp format.
Level: 1

Type: ERROR

Impact: Security

BEA-097547: Timestamp contains illegal non-digit characters: {0}.

Cause: The timestamp format is not correct.

Action: Fix the timestamp format.
Level: 1

Type: ERROR

Impact: Security

BEA-097548: Timestamp has invalid timezone designator: {0}.

Cause: The timestamp format is not correct.

Action: Fix the timestamp format.
Level: 1

Type: ERROR

Impact: Security

BEA-097549: Timestamp is missing timezone designator: {0}.

Cause: The timestamp format is not correct.

Action: Fix the timestamp format.
Level: 1

Type: ERROR

Impact: Security

BEA-097550: Month value is out-of-range for given year: {0}.

Cause: The timestamp format is not correct.

Action: Fix the timestamp format.
Level: 1

Type: ERROR

Impact: Security

BEA-097551: Day of month value is out-of-range for given month and year: {0}.

Cause: The timestamp format is not correct.

Action: Fix the timestamp format.
Level: 1

Type: ERROR

Impact: Security

BEA-097552: SPNEGO token trying to be constructed with invalid parsed information.

Cause: The parsed information is invalid.

Action: This is likely an internal WebLogic Server error. If this occurs again, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-097553: SAMLSourceSite: Error while generating {0}: {1}.

Cause: {0} Could not be generated.

Action: This is likely an internal WebLogic Server error. If this occurs again, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-097554: Queries that test at least one scope primary key must test all primary keys with a lower index.

Cause: Not all primary keys with a lower index were tested.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-097555: This store does not support nested containers (that is, collections of collections).

Cause: You are using nested containers for a store that does not support them.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-097556: Primary key field must not be null: {0}.

Cause: There was no value found for the primary key.

Action: Check the query to see if the primary key is not null or empty.
Level: 1

Type: ERROR

Impact: Security

BEA-097558: FederationServicesMBean configuration Protocol Signing Key {0} is invalid.

Cause: The FederationServicesMBean Protocol Signing Key was configured with an invalid value.

Action: Check the key information to see if it is valid.
Level: 1

Type: ERROR

Impact: Security

BEA-097559: FederationServicesMBean configuration SSL Client Key {0} is invalid.

Cause: The FederationServicesMBean SSL Client Key was configured with an invalid value.

Action: Check the key information to see if it is valid.
Level: 1

Type: ERROR

Impact: Security

BEA-097560: Invalid Source Site configuration, {0} must not be null or empty.

Cause: The Source Site configuration is missing.

Action: Check the configuration to see if there is a null or empty field.
Level: 1

Type: ERROR

Impact: Security

BEA-097561: Store service is not initialized properly.

Cause: The store service was configured incorrectly.

Action: Check the Store service configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-097562: Cannot forward to custom post form, please check if the post form configuration is valid.

Cause: The post form configuration was invalid.

Action: Fix the post form configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-097563: Connection was not found by name {0}.

Cause: There was a configuration error or an internal WebLogic Server error.

Action: Ensure that the specified data source is configured. In addition, check the log to see whether there is a connection pool checkout failure and find the cause.
Level: 1

Type: ERROR

Impact: Security

BEA-097564: The JDBC Connection Service initialization failed.

Cause: The configuration is incorrect.

Action: Check that the SQL configuration has been specified properly.
Level: 1

Type: ERROR

Impact: Security

BEA-098500: Decimal is too short.

Cause: The value length is less than or equal to 0.

Action: Pass in a correct value.
Level: 1

Type: ERROR

Impact: Security

BEA-098501: Decimal contains incorrect characters.

Cause: The specified decimal value contains incorrect characters.

Action: Pass in a correct value.
Level: 1

Type: ERROR

Impact: Security

BEA-098502: Hex binary data bad length.

Cause: The length of hex binary data is uneven.

Action: Pass in a correct value.
Level: 1

Type: ERROR

Impact: Security

BEA-098503: Invalid hex digit.

Cause: An invalid hexadecimal digit was encountered.

Action: Pass in a correct value.
Level: 1

Type: ERROR

Impact: Security

BEA-098504: Invalid RFC822 name: {0}

Cause: An invalid RFC822 name attribute value was passed.

Action: Pass in a valid RFC822 name attribute value.
Level: 1

Type: ERROR

Impact: Security

BEA-098505: Illegal X500 value: {0}

Cause: An illegal X500 value was passed.

Action: Pass in a valid X500 name attribute value.
Level: 1

Type: ERROR

Impact: Security

BEA-098506: Not enough BASE64 bytes

Cause: The atom cannot be decoded because not enough bytes were available.

Action: Correct the BASE64 value.
Level: 1

Type: ERROR

Impact: Security

BEA-098507: Incorrect XPathVersion

Cause: An unsupported XPathVersion was specified.

Action: Use a supported XPathVersion
Level: 1

Type: ERROR

Impact: Security

BEA-098508: Negative month with non-zero year

Cause: The month cannot be negative if the year is a non-zero value.

Action: Correct the month or year value.
Level: 1

Type: ERROR

Impact: Security

BEA-098509: Month and year are zero.

Cause: Both the month and the year are zero. At least one of the month and year must be non-zero.

Action: Correct the month or year value.
Level: 1

Type: ERROR

Impact: Security

BEA-098510: Method {0} had an internal WebLogic Server error.

Cause: This is an internal WebLogic Server error

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-098511: Illegal explicit to non-explicit time zone comparison

Cause: It is illegal to compare time values when one has an explicit time zone and the other does not.

Action: Correct the time-zone specification mismatch.
Level: 1

Type: ERROR

Impact: Security

BEA-098512: Could not schedule Audit log rotate trigger

Cause: There is an issue with the parameters configured on the Audit provider.

Action: Correct the parameters configured on the Audit provider.
Level: 1

Type: ERROR

Impact: Security

BEA-098513: Service Initialization when getting service with {0} service name.

Cause: The service with {0} service name was not correctly initialized in the service engine.

Action: Correctly initialize the service in the service engine.
Level: 1

Type: ERROR

Impact: Security

BEA-098514: Failed to generate a certificate thumbprint: {0}.

Cause: The thumbprint algorithm cannot be found or a certificate encoding error occurred.

Action: Examine the error message to determine the exact cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Security

BEA-098515: {1} cannot be {2}.

Cause: This is most likely a coding error.

Action: Pass a valid {1} to the method {0}.
Level: 1

Type: ERROR

Impact: Security

BEA-098516: The CertificateRegistry could not build a certificate path for the thumbprint {0}. This indicates that either someone is trying to access the server with an untrusted thumbprint or that the administrator has forgotten to register a certificate with this thumbprint in the CertificateRegistry.

Cause: The CertificateRegistry does not contain a certificate whose thumbprint is {0}.

Action: If you want to trust the thumbprint {0}, then register a certificate with this thumbprint in the CertificateRegistry.
Level: 1

Type: ERROR

Impact: Security

BEA-098517: Failed to get SAML assertion info: {0}.

Cause: A SAML assertion document parsing error occurred.

Action: Examine the error message to determine the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Security

BEA-098518: The environment does not support anonymous, please log in.

Cause: The method getAnonymousIdentity of IdentityService returned null.

Action: Check the environment configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-098519: Invalid file store password or the file has been invalidly changed.

Cause: The password for the file store is illegal or the file is modified.

Action: Ensure that the store password is not changed and the file is not modified either.
Level: 1

Type: ERROR

Impact: Security

BEA-098520: Unable to instantiate the CSSDelegate implementation.

Cause: The CSS Delegate implementation is not in the classpath.

Action: Check the CSS classpath.
Level: 1

Type: ERROR

Impact: Security

BEA-098521: Invalid principal class name {0} is entered to the PrincipalFactory create() API.

Cause: An invalid principal class name was entered to the PrincipalFactory create() API.

Action: Ensure that the principal class derives from WLSPrincipal.
Level: 1

Type: ERROR

Impact: Security

BEA-098522: Unable to instantiate the principal instance for principal class {0}.

Cause: The principal class {0} is not in the classpath.

Action: Ensure that the class {0} is in the classpath.
Level: 1

Type: ERROR

Impact: Security

BEA-098523: Unable to instantiate the PrincipalConfigurationDelegate instance.

Cause: The related class, either WLSPrincipalConfigurationDelegateImpl or OPPrincipalConfigurationDelegateImpl, is not in the classpath.

Action: Ensure that WLSPrincipalConfigurationDelegateImpl and OPPrincipalConfigurationDelegateImpl are in the classpath.
Level: 1

Type: ERROR

Impact: Security

BEA-099000: Null {0} parameter supplied to method {1}.

Cause: A parameter was not correctly specified. This is most likely a coding error.

Action: Check for a coding error.
Level: 1

Type: ERROR

Impact: Security

BEA-099001: Invalid ContextHandler value for {0} type: expect to {1} type.

Cause: This most likely was caused by an environment error.

Action: Check and update the indicated context element.
Level: 1

Type: ERROR

Impact: Security

BEA-099002: Null or empty certificate chain

Cause: This was most likely caused by an environment error.

Action: Check and update the indicated context element.
Level: 1

Type: ERROR

Impact: Security

BEA-099003: SAMLBeanUpdateListener {0}: {1} failed with exception: {2}

Cause: This was most likely caused by an environment error.

Action: Check and update the environment.
Level: 1

Type: ERROR

Impact: Security

BEA-099004: SAMLCreateAssertion: Exception while creating authentication statement.: {0}

Cause: This was most likely caused by an environment error.

Action: Check and update the environment.
Level: 1

Type: ERROR

Impact: Security

BEA-099005: SAMLCreateAssertion: can't map confirmation method

Cause: This was most likely caused by an environment error.

Action: Check and update the environment.
Level: 1

Type: ERROR

Impact: Security

BEA-099006: provider {0}: SAML Key Manage failed to validate key (Assertions signing) configuration in the FederationServicesMBean, key alias: {1}

Cause: This was most likely caused by an environment error.

Action: Check and update the environment.
Level: 1

Type: ERROR

Impact: Security

BEA-099007: Provider {0} not initialized: method {1} could not be called.

Cause: An internal WebLogic Server error occurred when the SAML provider was initialized.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-099008: Store service properties must not be null.

Cause: This was most likely caused by a configuration error.

Action: Check the Store service configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-099009: Get a null {0} value in store service properties.

Cause: This was most likely caused by a configuration error.

Action: Check the Store service configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-099010: Unable to derive key.

Cause: The input {0} is null or empty.

Action: Verify that the input parameter {0} is not null or empty.
Level: 1

Type: ERROR

Impact: Security

BEA-099011: Unable to get digest value for a password.

Cause: The input {0} is null or empty.

Action: Verify that the input parameter {0} is not null or empty.
Level: 1

Type: ERROR

Impact: Security

BEA-099012: Unable to create password digest - UTF-8 encoding required but unavailable:{0}.

Cause: An internal WebLogic Server error occurred while performing a message digest.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-099013: Invalid token type {0} received by the LDAP X509 certificate identity asserter.

Cause: This was likely caused by the provider not being properly configured.

Action: Check the provider configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-099014: {0}: {1} is null

Cause: A parameter was not correctly specified.

Action: Check for a coding error.
Level: 1

Type: ERROR

Impact: Security

BEA-099015: The format for import or export is invalid.

Cause: The format for import or export was invalid.

Action: Check the string used for import or export.
Level: 1

Type: ERROR

Impact: Security

BEA-099016: Could not get partner by partner id: {0}.

Cause: The partner could not be retrieved using the partner id: {0}.

Action: Check the registry to see if the partner exists.
Level: 1

Type: ERROR

Impact: Security

BEA-099017: Could not add partner with null partner id.

Cause: The partner id is null.

Action: Check the partner information.
Level: 1

Type: ERROR

Impact: Security

BEA-099018: Update business object failed, could not determine the object to update.

Cause: The object for updating could not be found.

Action: Check the registry to find the correct partner for updating.
Level: 1

Type: ERROR

Impact: Security

BEA-099019: Could not parse assertion: {0}.

Cause: An assertion was received that could not be properly parsed.

Action: Check the SAML assertion or contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-099020: Assertion validity check failed: {0}.

Cause: An assertion was received that did not pass validation.

Action: Check the SAML assertion or contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-099021: Signature required but assertion is not signed.

Cause: The assertion is not signed.

Action: Check the SAML assertion.
Level: 1

Type: ERROR

Impact: Security

BEA-099022: Signature is required but no signing certificate alias configured.

Cause: No signing certificate alias is configured.

Action: Check the SAML configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-099023: Unable to find trusted certificate for alias: {0}.

Cause: The trusted certificate was not available from the certificate registry.

Action: Check the SAML configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-099024: Signature verified but no certificate found to check trust.

Cause: No certificate was found to check the trust.

Action: Check the signature for the certificate.
Level: 1

Type: ERROR

Impact: Security

BEA-099025: Certificate in signature does not match configured signing cert.

Cause: The certificate in the signature does not match the configured signing cert.

Action: Check the certificate information in the partner registry.
Level: 1

Type: ERROR

Impact: Security

BEA-099026: Certificate is not trusted.

Cause: An assertion was received for which the signing certificate is not trusted.

Action: Check the SAML configuration and add the certificate to the registry.
Level: 1

Type: ERROR

Impact: Security

BEA-099027: Could not create name mapper: {0}.

Cause: An error occurred while creating an instance of the configured SAML name mapper.

Action: Check the details of the error message to determine the proper handling.
Level: 1

Type: ERROR

Impact: Security

BEA-099028: Mapping name error: {0}.

Cause: An error occurred while invoking an instance of the configured SAML name mapper.

Action: Check the details of the error message to determine the proper handling.
Level: 1

Type: ERROR

Impact: Security

BEA-099029: Mapping group error: {0}.

Cause: An error occurred while invoking an instance of the configured SAML name mapper.

Action: Check the details of the error message to determine the proper handling.
Level: 1

Type: ERROR

Impact: Security

BEA-099030: NameMapper returned no username mapping.

Cause: An instance of the configured SAML name mapper returned no user or group information.

Action: Check the SAML assertion or contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-099031: Assertion is invalid before {0}.

Cause: The received SAML assertion is not yet valid.

Action: Check the SAML configuration, the system clock or contact the SAML Identity Provider.
Level: 1

Type: ERROR

Impact: Security

BEA-099032: Assertion is invalid on or after {0}.

Cause: The received SAML assertion has expired.

Action: Check the SAML configuration, the system clock or contact the SAML Identity Provider.
Level: 1

Type: ERROR

Impact: Security

BEA-099033: No matching audience.

Cause: The received SAML assertion audience conditions was not satisfied.

Action: Check the SAML configuration or contact the SAML Identity Provider.
Level: 1

Type: ERROR

Impact: Security

BEA-099034: Unrecognized assertion condition (schema extension).

Cause: The received SAML assertion contained an unknown condition.

Action: Contact the SAML Identity Provider for information on how to correct the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-099035: No target in context handler.

Cause: An internal WebLogic Server error occurred while determining the SAML target.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-099036: Could not map Confirmation Method URN: {0}.

Cause: The received SAML assertion contained an unknown confirmation method.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-099037: Could not find asserting party matching assertion and context.

Cause: The SAML partner could not be determined from the received SAML assertion.

Action: Check the SAML assertion or contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-099038: Could not verify signature: {0}.

Cause: The signature from the received SAML assertion could not be verified.

Action: Check the SAML assertion or contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-099039: No issuer URI configured for asserting party.

Cause: The SAML asserting party was not configured with an issuer URI.

Action: Check the SAML configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-099040: Assertion issuer does not match issuer configured for asserting party.

Cause: The issuer from the received SAML assertion could not be verified.

Action: Check the SAML assertion against the SAML configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-099041: Assertion subject confirmation method does not match asserting party configuration.

Cause: The subject confirmation from the received SAML assertion could not be verified.

Action: Check the SAML assertion against the SAML configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-099046: Illegal value for {0}: {1}.

Cause: This error has multiple possible causes. When using the PasswordHashUtility, an invalid command line argument was passed. For SAML, it means that there is an invalid SAML provider configuration.

Action: Check the command line argument for the parameter specified in the message or check the SAML provider configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-099047: Missing parameter {0}.

Cause: The SAML provider configuration is invalid.

Action: Check the SAML provider configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-099048: Invalid {0} value {1} for {2}.

Cause: An invalid configuration was supplied for the SAML provider.

Action: Check the SAML provider configuration based on the configuration parameter from the error message.
Level: 1

Type: ERROR

Impact: Security

BEA-099049: Could not load SAML partner registry schema file {0}.

Cause: An internal WebLogic Server error occurred while loading the SAML partner registry.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-099050: Could not generate XML Schema from SAML partner registry schema file: {0}.

Cause: An internal WebLogic Server error occurred while loading the SAML partner registry.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-099051: ImportMode = fail, partnerID {0} exists, import operation terminated.

Cause: The SAML partner could not be imported because the partner entry already exists.

Action: Check the SAML configuration or select a different SAML partner import mode.
Level: 1

Type: ERROR

Impact: Security

BEA-099052: Could not locate {0} {1} in the import XML document, import operation abort.

Cause: The SAML partner could not be imported because the partner or certificate could not be found.

Action: Check the SAML partner registry file based on the information from the error message.
Level: 1

Type: ERROR

Impact: Security

BEA-099053: {0} {1} already exists, Import operation fail.

Cause: The SAML partner could not be imported because the partner or certificate already exists.

Action: Check the SAML configuration based on the information from the error message.
Level: 1

Type: ERROR

Impact: Security

BEA-099054: Error getting {0} {1} from registry, Import operation fail.

Cause: The SAML partner could not be imported because the partner or certificate could not be located.

Action: Check the SAML configuration based on the information from the error message.
Level: 1

Type: ERROR

Impact: Security

BEA-099055: Could locate {0} {1} from registry.

Cause: The SAML partner could not be imported because the partner or certificate could not be located.

Action: Check the SAML configuration based on the information from the error message.
Level: 1

Type: ERROR

Impact: Security

BEA-099056: Could not export partner registry data ldift: {0}.

Cause: An internal WebLogic Server error occurred while exporting a SAML partner.

Action: Contact My Oracle Support and provide them with the log files.
Level: 1

Type: ERROR

Impact: Security

BEA-099057: Could not decrypt password: {0}.

Cause: The supplied password could not be read.

Action: Check that the password value is correct or contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-099058: No sender certificate is provided for checking trust.

Cause: The received SAML assertion could not be trusted because no certificate was provided.

Action: Check the SAML configuration, the SSL configuration or contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-099059: There is no {0} in {1}.

Cause: The received SAML assertion could not be validated.

Action: Check the details of the error message to determine the proper handling.
Level: 1

Type: ERROR

Impact: Security

BEA-099060: The URL specified for the data store connection is invalid: {0},please check all host configuration parameters.

Cause: This was most likely caused by a configuration error.

Action: Check all host configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-099061: Hash algorithm {0} was not found

Cause: The JCE configuration is most likely not set up to support the algorithm.

Action: Review the JCE configuration to ensure the hash algorithm is available for use.
Level: 1

Type: ERROR

Impact: Security

BEA-099062: The {0} password hash algorithm is not usable.

Cause: The password algorithm name was not found to be supported by the JCE crypto configuration.

Action: Verify that the password algorithm is specified correctly, and that the JCE configuration supports the algorithm.
Level: 1

Type: ERROR

Impact: Security

BEA-099063: Plaintext password usage was rejected.

Cause: Plaintext passwords are configured to not be allowed, but a Plaintext password was either found or was attempted to be saved.

Action: If the failure occurred during authentication, review the plaintext passwords and correct them. If the failure occurred while changing a password, review the password style settings to ensure that they specify a non-plaintext style.
Level: 1

Type: ERROR

Impact: Security

BEA-099064: Plaintext password is not allowed and unable to parse the stored hashed password.

Cause: Plaintext passwords are configured to not be allowed, but the hashed password could not be parsed.

Action: If the failure occurred during authentication, review the plaintext passwords and correct them. If the failure occurred while changing a password, review the password style settings to ensure that they specify a non-plaintext style.
Level: 1

Type: ERROR

Impact: Security

BEA-099065: Password ("quit" to end)

Cause: The password hash utility internally uses this prompt for a password.

Action: This is the prompt that will be used by the password hash utility.
Level: 1

Type: ERROR

Impact: Security

BEA-099066: Usage: Java com.bea.security.utils.authentication.PasswordHashUtility [-a algorithm] [-s size] password* "algorithm" is the name of the hash algorithm "size" is the length of the salt characters "passwords" are the plain text passwords to be hashed. None for interactive mode.

Cause: The is the text the password hash utility displays for usage of the utility.

Action: This is the usage text that will be used by the password hash utility.
Level: 1

Type: ERROR

Impact: Security

BEA-099067: The minimum length of password must not be greater than the maximum length of password.

Cause: System password validation was configured with an invalid password length.

Action: Change the value for minimum or maximum length of a password.
Level: 1

Type: ERROR

Impact: Security

BEA-099068: The user name cannot be empty.

Cause: The user name is null.

Action: Input correct user name information.
Level: 1

Type: ERROR

Impact: Security

BEA-099069: The password length cannot be less than {0}.

Cause: The current password length is less than {0}.

Action: Change your password, and try again.
Level: 1

Type: ERROR

Impact: Security

BEA-099070: The password length cannot be greater than {0}.

Cause: The current password length is greater than {0}.

Action: Change your password, and try again.
Level: 1

Type: ERROR

Impact: Security

BEA-099071: The password cannot contain or be equal to your username.

Cause: The password contains or is the same as your username.

Action: Change your password, and try again.
Level: 1

Type: ERROR

Impact: Security

BEA-099072: The password cannot contain or be equal to the reverse of your username.

Cause: The password contains or is equal to the reverse of your username.

Action: Change your password, and try again.
Level: 1

Type: ERROR

Impact: Security

BEA-099073: The maximum instances of a character in a password cannot be greater than {0}.

Cause: The maximum occurrences of a character in the password is greater than what is allowed by the configuration of system password validation.

Action: Change your password, and try again.
Level: 1

Type: ERROR

Impact: Security

BEA-099074: The maximum repeating consecutive characters in a password cannot be greater than {0}.

Cause: The repetition of a character in the password is greater than what is allowed by the configuration of system password validation.

Action: Reduce the repeating consecutive characters in your password, and try again.
Level: 1

Type: ERROR

Impact: Security

BEA-099075: The number of alphabetic characters in a password cannot be less than {0}.

Cause: The number of alphabetic characters in the password is less than what is required by the configuration of system password validation.

Action: Add more alphabetic characters in your password.
Level: 1

Type: ERROR

Impact: Security

BEA-099076: The number of numeric characters in a password cannot be less than {0}.

Cause: The number of numeric characters in the password is less than {0}.

Action: Add more numeric characters in your password.
Level: 1

Type: ERROR

Impact: Security

BEA-099077: The number of lowercase characters in a password cannot be less than {0}.

Cause: The number of lowercase characters in the password is less than {0}.

Action: Add more lowercase characters in your password.
Level: 1

Type: ERROR

Impact: Security

BEA-099078: The number of uppercase characters in a password cannot be less than {0}.

Cause: The number of uppercase characters in the password is less than {0}.

Action: Add more uppercase characters in your password.
Level: 1

Type: ERROR

Impact: Security

BEA-099079: The number of non-alphanumeric characters in a password cannot be less than {0}.

Cause: The number of non-alphanumeric characters in the password is less than {0}.

Action: Add more non-alphanumeric characters in your password.
Level: 1

Type: ERROR

Impact: Security

BEA-099080: The user password cannot be null.

Cause: The user password is null.

Action: Input your password, and try again.
Level: 1

Type: ERROR

Impact: Security

BEA-099081: Illegal command line.

Cause: Command line syntax is not correct.

Action: Retype the command line and try again.
Level: 1

Type: ERROR

Impact: Security

BEA-099082: Could not configure attribute {0} in MBean {1}.

Cause: The method to configure this attribute could not be found or the parameter for this method could not be created.

Action: Refer to the MBean javadoc to verify whether the MBean attribute name is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-099083: The key {0} in property file is in the wrong format.

Cause: The key {0} in property file is in the wrong format.

Action: Modify the property file and use a valid format for the key.
Level: 1

Type: ERROR

Impact: Security

BEA-099084: Could not create MBean.

Cause: The MBean type or MBean class in property file may not be correct.

Action: Check the MBean type or MBean class in the property file.
Level: 1

Type: ERROR

Impact: Security

BEA-099085: Unknown MBeanResource ActionType {0}.

Cause: The MBean resource method that a caller is attempting to access is unknown.

Action: Modify your entitlement policy and try again.
Level: 1

Type: ERROR

Impact: Security

BEA-099086: Get null or empty encrypted value. An encrypted value must not be null or empty.

Cause: The encrypted value is null or empty.

Action: Check the encrypted value.
Level: 1

Type: ERROR

Impact: Security

BEA-099087: The MaxPasswordLength must not be less than MinAlphabeticCharacters+MinNumericCharacters+MinNonAlphanumericCharacters.

Cause: System password validation was configured with an invalid password length.

Action: Change the system password validation configuration lengths.
Level: 1

Type: ERROR

Impact: Security

BEA-099088: The MaxPasswordLength must not be less than MinLowercaseCharacters+MinUppercaseCharacters+MinNumericCharacters+MinNonAlphanumericCharacters.

Cause: System password validation was configured with an invalid password length.

Action: Change the system password validation configuration lengths.
Level: 1

Type: ERROR

Impact: Security

BEA-099089: The NegotiateCredentialMapper could not get credentials. The requestor is {0}. The initiator is {1}. The resource is {2}. The exception is {3}.

Cause: An unexpected exception occurred when trying to get the credentials.

Action: Read the exception text from the log message for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-099090: The NegotiateCredentialMapper could not get credentials for initiator with String type. The requestor is {0}. The initiator is {1}. The resource is {2}.

Cause: The initiator should not be a String while acquiring credentials with NegotiateCredentialMapperProvider.

Action: Try the getCredentials() method with a Subject as the initiator.
Level: 1

Type: ERROR

Impact: Security

BEA-099091: Illegal parameter type.

Cause: An initiator with String type is not supported by NegotaiteCredentialMapper for method getCredential().

Action: Try the method getCredentials() with Subject as the initiator type.
Level: 1

Type: ERROR

Impact: Security

BEA-099092: Trust group {0} not found.

Cause: The group could not be found as the group parameter that was passed to the method is not registered in the security provider.

Action: Pass in a trust group that exists.
Level: 1

Type: ERROR

Impact: Security

BEA-099093: The security provider already has a trust group registered with {0}.

Cause: The trust group {0} already exists in the security provider.

Action: Pass in another trust group name.
Level: 1

Type: ERROR

Impact: Security

BEA-099094: The trust group is null or empty.

Cause: An empty or null trust group was passed but this is not supported.

Action: Modify the code to pass a non-null and non-empty trust group.
Level: 1

Type: ERROR

Impact: Security

BEA-099095: The trust group wildcard is null or empty.

Cause: An empty or null trust group wildcard was passed, but this is not supported.

Action: Modify the code to pass a non-null and non-empty trust group wildcard.
Level: 1

Type: ERROR

Impact: Security

BEA-099096: An invalid entry {1} found in the group JKS keystore {0}.

Cause: Examine the nested exception for more information in diagnosing the problem.

Action: Verify that the file is a group JKS keystore.
Level: 1

Type: ERROR

Impact: Security

BEA-099097: The group {0} is not in the specified file {1}.

Cause: The group is not contained in a group JKS keystore.

Action: Verify that the group is contained in a group JKS keystore.
Level: 1

Type: ERROR

Impact: Security

BEA-099098: The security provider already has a certificate registered for trust group {0} under the alias {1}.

Cause: The certificate alias {0} already exists in the trust group {0}.

Action: Pass in another certificate alias.
Level: 1

Type: ERROR

Impact: Security

BEA-099099: Errors occurred when register certificate into groups {0}, please see nested message for details.

Cause: Errors occurred when trying to register certificates into trust groups.

Action: Remove the trust group from the passed in trust group list.
Level: 1

Type: ERROR

Impact: Security

BEA-099100: The trust group is null or empty.

Cause: An empty or null trust group was used, but this is not supported.

Action: Modify the code to pass a non-null and non-empty trust group.
Level: 1

Type: ERROR

Impact: Security

BEA-099101: The trust group name {0} is reserved for internal use, please choose another trust group name.

Cause: The trust group name is reserved.

Action: Modify the code to pass another trust group name.
Level: 1

Type: ERROR

Impact: Security

BEA-099102: Subject DN {1} already registered under the alias {2} trust group {0}.

Cause: A certificate with subject DN {1} already exists in the trust group {0} under the alias {2}.

Action: Either remove the previous certificate from the trust group {0} or register a different certificate.
Level: 1

Type: ERROR

Impact: Security

BEA-099103: Issuer DN {1} and serial number {2} already registered under the alias {3} in the trust group {0}

Cause: A certificate with issuer DN {1} and serial number {2} already exists in the trust group {0} under the alias {3}.

Action: Either remove the previous certificate from the trust group {0} or register a different certificate.
Level: 1

Type: ERROR

Impact: Security

BEA-099104: Subject key identifier {1} already registered under the alias {2} in the trust group {0}.

Cause: A certificate with subject key identifier {1} already exists in the trust group {0} under the alias {2}.

Action: Either remove the previous certificate from the security provider or register a different certificate.
Level: 1

Type: ERROR

Impact: Security

BEA-099105: The file path {0} does not exist.

Cause: The specified file path does not exist.

Action: Create the file path {0} or use another existing file path.
Level: 1

Type: ERROR

Impact: Security

BEA-099106: The password is a null or empty string.

Cause: The password is a null or empty string.

Action: Supply a new password which is neither null nor empty.
Level: 1

Type: ERROR

Impact: Security

BEA-099107: The algorithm {0} used to encrypt the file is invalid.

Cause: The algorithm {0} used to encrypt the file is invalid.

Action: Supply a new algorithm.
Level: 1

Type: ERROR

Impact: Security

BEA-099108: Invalid Property file: property "{0}" is required but is not configured.

Cause: Invalid Property file: property "{0}" is required but is not configured.

Action: Add configuration of property "{0}" to your property file.
Level: 1

Type: ERROR

Impact: Security

BEA-099109: Had problem attempting to get CallbackHandler for debugging in {0}: {1}

Cause: The system property weblogic.security.DumpContextHandler was set to true, but no CallbackHandler is available to handle the callback.

Action: If using programmatic authentication, check if the passed CallbackHandler supports handling weblogic.security.auth.callback.ContextHandlerCallback. Otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-099110: The value configured for NameMapper attribute: {0} is not valid.

Cause: The name mapper class {0} is not in the classpath or it does not implement thename mapper interface.

Action: Ensure that the name mapper class {0} is in the classpath and implements the name mapper interface.
Level: 1

Type: ERROR

Impact: Security

BEA-099111: The KerberosCredentialMapper could not get credentials. The requestor is {0}. The initiator is {1}. The resource is {2}. The exception is {3}.

Cause: An unexpected exception occurred when trying to get the credentials.

Action: Read the exception text from the log message for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-099112: The KerberosCredentialMapper could not get credentials for initiator with String type. The requestor is {0}. The initiator is {1}. The resource is {2}.

Cause: The initiator should not be a String while acquiring credentials with KerberosCredentialMapperProvider.

Action: Try the getCredentials() method with a Subject as the initiator.
Level: 1

Type: ERROR

Impact: Security

BEA-099113: Illegal parameter type.

Cause: An initiator with String type is not supported by NegotaiteCredentialMapper for method getCredential().

Action: Try the method getCredentials() with Subject as the initiator type.
Level: 1

Type: ERROR

Impact: Security

BEA-099114: The MaxPasswordLength must not be less than MinAlphaCharacters+MinNumericOrSpecialCharacters.

Cause: The MaxPasswordLength is less than MinAlphaCharacters+MinNumericOrSpecialCharacters.

Action: Change the value and try again.
Level: 1

Type: ERROR

Impact: Security

BEA-099115: The MaxPasswordLength must not be less than MinLowercaseCharacters+MinUppercaseCharacters+MinNumericOrSpecialCharacters.

Cause: The MaxPasswordLength is less than MinLowercaseCharacters+MinUppercaseCharacters+MinNumericOrSpecialCharacters.

Action: Change the value and try again.
Level: 1

Type: ERROR

Impact: Security

BEA-099116: The number of numeric or special characters in a password cannot be less than {0}.

Cause: The number of numeric or special characters in the password is less than {0}.

Action: Add more numeric or special characters into your password.
Level: 1

Type: ERROR

Impact: Security

BEA-099117: The LDAP authentication provider named "{0}" failed to make a connection to LDAO server at {1}://{2}:{3}, the error cause is: {4}.

Cause: Exception in making connection to LDAP server by the LDAP authentication provider.

Action: Check the configured host name and port of the LDAP server for the failed LDAP authentication provider; also check SSL configuration details if SSL is enabled. If the failed provider is not used anymore in the domain, remove it to avoid the warning message. To change the default log interval (600 seconds), use the system property "weblogic.security.providers.authentication.connWarningLogIntervalSeconds". Note: If multiple LDAP providers are configured, the failover mechanism may tolerate failures for some providers.
Level: 1

Type: WARNING

Impact: Security

BEA-099500: 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-099501: 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-099502: 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-099503: 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-099504: Evaluation of policy associated with resource {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-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.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100057: This server does not have deployment for the Web application with context path: {0}. The callback: {1} failed while replicating the session. Check the configuration; only uniform configurations in a cluster are supported.

Cause: WebLogic Server clustering relies on uniform Web application deployment across the cluster. It seems the Web application was not deployed on all the servers.

Action: Redeploy the Web application, and ensure that it targets the cluster and all members in the cluster.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100058: The PersistentStoreType for the Web application with context path: {0} is not replicated. The callback: {1} failed while replicating the session. Check the configuration; only uniform configurations in a cluster are supported.

Cause: WebLogic Server clustering relies on uniform Web application deployment across the cluster. It seems the Web application was not deployed on all the servers with uniform configuration.

Action: Redeploy the Web application, and ensure that it targets the cluster and all members in the cluster. Also, the PersistentStoreType should be set to "replicated" for all cluster members.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100059: An unexpected error occurred while cleaning up sessions during undeployment of Web application: {0}.

Cause: The trigger failed to clean up the expired session.

Action: Check the exception text for the exact error message. When using JDBC-based HTTP session persistence, ensure that the database is set up properly. For file-based persistence, ensure that the permissions on the storage directory are appropriately set.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100060: An unexpected error occurred while retrieving the session for Web application: {0}.

Cause: The session from persistent store could not be retrieved.

Action: Check the configuration, and check the exception text for the exact error message. Also, check the WebLogic Server documentation for more details about how to configure session persistence for Web applications.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100061: Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. This attribute will be lost upon redeployment. This message is logged only once per session.

Cause: The session.setAttribute(name, value) was invoked with a non-serializable value for memory-based sessions.

Action: If the session data should survive redeployment, ensure that all attributes are serializable. Otherwise, the non-serializable data will be lost upon redeployment.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100062: Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be replicated to the secondary server. This message is logged only once per session.

Cause: The session.setAttribute(name, value) was invoked with a non-serializable value for a replicated session.

Action: If the session data should survive redeployment and session failovers, ensure that all attributes are serializable. Otherwise, the non-serializable data will be lost upon failover and redeployment.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100063: Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the disk. This message is logged only once per session.

Cause: The session.setAttribute(name, value) was invoked with a non-serializable value for a file-based persistent session.

Action: If the session data should survive redeployment and session failovers, ensure that all the attributes are serializable. Otherwise, the non-serializable data will be lost upon failover and redeployment.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100064: Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. The attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the database. This message is logged only once per session.

Cause: The session.setAttribute(name, value) attribute was invoked with a non-serializable value for a JDBC-based persistent session.

Action: If the session data should survive redeployment and session failovers, ensure that all the attributes are serializable. Otherwise, the non-serializable data will be lost upon failover and redeployment.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100065: {0}. Failed to remove attributes for HTTP session ID: {1}.

Cause: An unexpected error occurred during HTTP session invalidation.

Action: Check the error message for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100066: Failed to look up the replicated session object for Web application: {0}, session ID: {1}.

Cause: The ReplicationManager returned the NotFoundException.

Action: This happens if the object has been cleaned up underneath or the version number does not match with the secondary object. This should not happen normally. Unwanted failovers at the front end can cause unnecessary session failovers in the back end, which could result in this error in certain situations. Check the error message for more information.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100067: Failed to look up the secondary information for Web application: {0} session ID: {1}.

Cause: The ReplicationManager returned the NotFoundException. This happens if the object has been cleaned up underneath or the version number does not match with the secondary object. This should not happen normally. Unwanted failovers at the front end can cause unnecessary session failovers in the back end, which could result in this error in certain situations.

Action: Check the error message for more information.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100068: Failed to look up the secondary information for Web application: {0} session ID: {1}.

Cause: The ReplicationManager failed to look up the secondary information for a valid session.

Action: This is an unexpected error. Check the error message for details.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100069: The getAttribute(): {0} was a HomeHandle, reconstructing the EJBHome.

Cause: This is an informational message indicating that the container is storing only the handle for the EJBHome placed into the session.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100070: Error reconstructing the EJBHome put into session for name: {0}

Cause: The container found an EJBHome handle stored in the session. However, it failed to reconstruct the EJBHome using that EJBHome handle.

Action: Ensure that the HomeHandle is still valid. Check the exception text for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100071: The setAttribute(): {0} was an EJBHome, storing the HomeHandle into the session.

Cause: The container found an EJBHome handle stored in the session. It will reconstruct the EJBHome object before returning.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100072: Error in finding the HomeHandle for the EJBHome: {0}.

Cause: The container stores only the handle for an EJBHome put into the session. However, in this case, it failed to find the HomeHandle.

Action: Check the RemoteException for the exact error message details.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100073: Exception while serializing session object: {0}.

Cause: The session object failed to serialize.

Action: Check the exception text for the exact error message details.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100079: WAN failover configuration missing.

Cause: The JDBCTxDataSource or the backup cluster address was not properly configured.

Action: Set the JDBCTxDataSource or the backup cluster address to store session state.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100081: Persistent store settings cannot be changed between versions. The persistent store settings for application {0} is different from the settings for previous versions.

Cause: The persistent store settings of the new version were different from previous versions.

Action: Ensure that the persistent store settings are not changed when deploying a new version of an application.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100082: Failed to deploy {0} because the JDBC data source was missing. Target a JDBC data source to the cluster.

Cause: The configuration was incomplete.

Action: Target a JDBC data source to the cluster. Refer to the cluster documentation for more information.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100083: The Web application: {0} in application: {1} has its PersistenceStoreType set to: {2} for HTTP sessions. However, the target list does not contain all members of cluster: {3}. Non-homogeneous deployment for replicated sessions is not allowed.

Cause: Non-homogeneous deployment for replicated sessions is not allowed. The target list must be a cluster or a virtual host which is targeted to a cluster.

Action: Fix the targets for this Web application. Specify a cluster or virtual host as the target.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100084: The Web application: {0} in application: {1} has its PersistenceStoreType set to: {2} for HTTP sessions. However, the target list contains virtual host: {3}, for which the target list does not contain all members of cluster: {4}. Non-homogeneous deployment for replicated sessions is not allowed.

Cause: Non-homogeneous deployment for replicated sessions is not allowed. The target list must be a cluster or a virtual host which is targeted to a cluster.

Action: Fix the targets for this Web application.Specify a cluster or virtual host as the target.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100087: The JDBC session data for session ID: {0} has been modified by another server in the cluster.

Cause: The front-end Web server failed to maintain server affinity.

Action: Ensure that the front-end Web server or load balancer has been properly configured.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100089: The session ID: {0} has been accessed from {1}, a server that is neither the primary ({2}) nor the secondary ({3}). The request URL was: {4}

Cause: The most likely cause is a configuration error on a front end hardware loadbalancer or webserver plugin. They should be configured to respect the values of primary/secondary in the cookie (i.e., stickiness), when possible.

Action: Please ensure that the front end webserver or load-balancer has been properly configured.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100090: An unexpected error occurred during a batched update of the last accessed time attribute of the updated sessions in application {0}.

Cause: Check the exception message for details.

Action: Check the exception message for details.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100094: The session ID: {0} has been accessed from {1}, a server that is not the primary ({2}). The request URL was: {3}.

Cause: The most likely cause is a configuration error on a front-end hardware load balancer or Web server plug-in. These should be configured to respect the values of the primary or secondary in the cookie (for example, stickiness), when possible.

Action: Ensure that the front-end Web server or load balancer has been properly configured.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100095: persistent-data-source-jndi-name is required for an async-jdbc session.

Cause: persistent-data-source-jndi-name was not used to specify the data source JNDI name for the JDBC connection, but persistent-store-type is async-jdbc.

Action: Use persistent-data-source-jndi-name to specify the data source JNDI name for the JDBC connection.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100096: persistent-data-source-jndi-name will take effect and persistent-store-pool will be ignored for async-jdbc session in application {0}.

Cause: This is debug information.

Action: No action is required.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100097: The IDLength {0} is too short. It is not secure. WebLogic Server will increase the length to {1}.

Cause: The IDLength of Session Descriptor is smaller than {1}.

Action: Mofify the Weblgoic deployment descriptor. Ensure that the IDLength of Session Descriptor is equal to or greater than {1}.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100098: persistent-data-source-jndi-name or persistent-store-pool is required when persistent-store-type is jdbc.

Cause: persistent-data-source-jndi-name or persistent-store-pool was not used to configure the database connection, but persistent-store-type is jdbc.

Action: Use persistent-data-source-jndi-name or persistent-store-pool to configure the database connection.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-101002: [{0}] Could not deserialize the context attribute.

Cause: The classloader changed. When this happens, the old attributes are deserialized using the new classloader.

Action: Ensure that the attribute class is available to the Web application scope and is serializable.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101003: [{0}] {1} called with a null document root.

Cause: The Web application did not initialize correctly.

Action: Check the log file for error messages about this Web application.
Level: 1

Type: INTERNAL_ERROR

Impact: HTTP

BEA-101005: [{0}] {1} called with unsafe path: "{2}".

Cause: The virtual path that was passed in points to a resource outside of the Web application scope.

Action: Check the virtual path being passed to the method and rectify the problem accordingly.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101008: [{0}] Cannot get InputStream of resource "{1}".

Cause: The getResourceAsStream() method failed to get an InputSteam for the resource.

Action: Ensure that the resource exists.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101017: [{0}] Root cause of ServletException.

Cause: The Web application container caught an unexpected exception.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101019: [{0}] Servlet failed with an IOException.

Cause: An unexpected IOException was caught while processing the request.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101020: [{0}] Servlet failed with an Exception

Cause: An unexpected error occurred.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101024: [{0}] Unsupported error status code for the error-page element in web.xml.

Cause: The format of the error status code was invalid.

Action: Check the web.xml and fix the error-page element error status code.
Level: 1

Type: INTERNAL_ERROR

Impact: HTTP

BEA-101025: [{0}] Document root is null.

Cause: This should never happen. The initialization failed.

Action: Check the log file for error messages during the Web application initialization phase.
Level: 1

Type: INTERNAL_ERROR

Impact: HTTP

BEA-101027: [{0}] Document root: "{1}" does not exist.

Cause: This is an unexpected error message.

Action: Ensure that the directory exists.
Level: 1

Type: INTERNAL_ERROR

Impact: HTTP

BEA-101029: [{0}] cannot make temporary directory "{1}". Will not be able to compile JSPs.

Cause: The creation of the temporary directory failed.

Action: Check the write permissions.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101040: [{0}] Error occurred while trying to set "{1}{2}".

Cause: A NumberFormatException occurred while parsing the value assigned to the reloadCheckSecs parameter in web.xml.

Action: Ensure that the value was entered correctly.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101045: [{0}] {1}

Cause: This is a general purpose error message.

Action: Check the message for the exact cause and take proper action.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101046: [{0}] {1}

Cause: This is a general purpose error message.

Action: Check the exception for exact cause and take proper action.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101047: [{0}] {1}

Cause: This is a general purpose informational message for debug purposes only.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101051: [{0}] started

Cause: This is an informational message indicating that the Web server has been started.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101052: [{0}] Initialized

Cause: This is an informational message indicating that the Web server has been initialized.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101053: [{0}] Loading Web application: {1}

Cause: The Web application is being deployed.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101054: [{0}] {1} is the default Web application for {2}.

Cause: The given Web application is being registered as a default Web application.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101060: [{0}] Loading "{1}" from directory: "{2}"

Cause: The Web application was deployed using an exploded directory structure.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101061: [{0}] Could not find Web application "{1}".

Cause: The descriptor for the Web application with the name given could not be loaded.

Action: Check the error message for details and ensure that the Web application was configured properly.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101062: [{0}] Error reading Web application "{1}".

Cause: An IOException occurred while reading the descriptors for the Web application.

Action: Ensure that the web.xml and weblogic.xml descriptors exist in the right place.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101064: [{0}] Error parsing descriptor in Web appplication "{1}"

Cause: An unexpected error occurred while reading the descriptors for the Web application.

Action: Ensure that web.xml and weblogic.xml exist in the right place
Level: 1

Type: ERROR

Impact: HTTP

BEA-101066: [{0}] Cannot initialize HTTP URL resources. Could not get JNDI context: {1}.

Cause: The URL contexts could not be registered because the JNDI context was not found.

Action: Ensure that the JNDI resources were properly configured.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101067: [{0}] Disregarding null URL resource value for property {1}

Cause: The URL for the JNDI resource specified in URLResource was null.

Action: Correct the configuration (WebServerMBean). The URLs cannot be null.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101068: [{0}] Could not parse URL resource value {1}.

Cause: The URL for the JNDI resource specified in the URL resource was malformed.

Action: Correct the configuration (WebServerMBean). Specify a valid URL.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101069: [{0}] Could not bind URL {1} to JNDI name {2} error message: {3}.

Cause: The URL failed to bind with the JNDI name.

Action: Correct the configuration (WebServerMBean).
Level: 1

Type: ERROR

Impact: HTTP

BEA-101070: [{0}] Bound URL resource "{1}" to JNDI name "{2}".

Cause: This is an informational message only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101075: [{0}] HttpServer is shutting down.

Cause: The Web server is shutting down.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101083: Connection failure.

Cause: The connection failed while writing data into the stream.

Action: Check the exception for the exact cause and take appropriate action.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101086: No host in HTTP header. Dispatching to default HTTP server.

Cause: Host header missing.

Action: Ensure that the requests are accompanied with a host header in order for virtual hosting to work. Also, proper HTTP redirects must have a host header.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101087: {0} is not a virtual host. Dispatching to default HTTP server.

Cause: The host header is missing from the HTTP request.

Action: Make sure the requests are accompanied with a host header in order for Virtual Hosting to work. Also, proper HTTP redirects must have a host header.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101088: Dispatching request to {0}.

Cause: Dispatching the request to the Web server (Virtual Host) defined by the host header.

Action: Check the configuration.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101093: A problem occurred while dispatching the servlet request.

Cause: The request could not be dispatched into the execute queue.

Action: The request could be malformed. Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101095: POST time exceeded the configured MaxPostTimeSecs of {0,number}.

Cause: The parameter makes sure that a malicious user does not send slow POSTs to cause a denial of service attack.

Action: If you think the time was too short, try increasing the value of MaxPostTimeSecs using the Administration Console.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101096: POST size exceeded the MaxPostSize={0,number}.

Cause: The parameter makes sure that a malicious user does not send huge POSTs to cause a denial of service attack.

Action: If you think the post size is unreasonable, try increasing MaxPostSize using the Administration Console.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101100: [{0}] Got bad cookie header: {1} from User-Agent: {2}

Cause: A cookie was malformed.

Action: Refer to the cookie specifications for the correct format: http://www.ietf.org/rfc/rfc2965.txt (Oct 2000; Obsoletes: 2109) http://www.ietf.org/rfc/rfc2109.txt (Feb 1997) http://www.ietf.org/rfc/rfc2616.txt (Jun 1999; Obsoletes: 2068) http://www.ietf.org/rfc/rfc2068.txt (Jan 1997)
Level: 1

Type: ERROR

Impact: HTTP

BEA-101101: [{0}] Unable to create new session.

Cause: A new session could not be created.

Action: Ensure that the persistent store has been properly configured.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101104: Servlet execution in servlet context "{0}" failed, {1}.

Cause: An unexpected error occurred while serving the request. This is not a simple client connection reset error.

Action: Check the error message for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101105: [{0}] error-page location: "{1}" for the error-code: "{2,number}" does not exist. Serving the default error page.

Cause: The error-page you configured in web.xml does not exist. A configuration error has occurred.

Action: Correct the web.xml descriptor, or make the resource available.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101106: [{0}] Could not serve custom error page: "{1}" for the error code: "{2,number}"

Cause: The error-page configured in web.xml does not exist. A configuration error has occurred.

Action: Correct the web.xml descriptor or make the resource available.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101107: [{0}] Problem occurred while serving the error page.

Cause: The error-page configured in web.xml could not be served.

Action: Check the configuration in web.xml.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101108: [{0}] Unsupported encoding: "{1}" specified.

Cause: The specified encoding is not supported by the underlying virtual machine(VM).

Action: Ensure that the specified encoding is valid or install the additional encoding classes.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101122: [{0}] Servlet: "{1}" is permanently unavailable.

Cause: The Web application is not currently available.

Action: Ensure that the Web application has been deactivated. Check to see if redeployment is in progress.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101123: [{0}] Servlet: "{1}" will be unavailable for the next: "{2,number}" seconds.

Cause: The servlet has been marked as unavailable.

Action: Make the request again after the specified time.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101125: [{0}] Error occurred while instantiating servlet: "{1}".

Cause: The servlet failed to instantiate.

Action: Ensure that the servlet has been configured properly in web.xml. Also, check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101126: [{0}] Error casting servlet: "{1}" to javax.servlet.Servlet

Cause: The servlet class that has been configured does not implement javax.servlet.Servlet.

Action: Fix the definition of the class.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101128: Initializing HTTP services.

Cause: This is an informational message.

Action: Ensure that the resources are available now.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101129: Initializing the Web application container.

Cause: This is an informational message.

Action: This is an informational message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101133: Initializing Web server {0}.

Cause: The Web server was just initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101135: {0} is the default Web server.

Cause: The default Web server name is being logged.

Action: This is an informational message for debug purposes only. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101136: Registering virtual host: {0}.

Cause: A Virtual Host (non-default Web server) has been registered.

Action: This is an informational message for debug purposes only. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101138: {0} One of the getParameter family of methods was called after reading from the ServletInputStream. Not merging post parameters.

Cause: If the servlet reads the data from the input stream directly, then the request data will not be available for the getParameter family of methods.

Action: If the code relies on post parameters being available through the getParameter method, fix the code.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101140: An error occurred while creating servlet {1} (class: {2}, initArgs: {3}) for Web application {0}.

Cause: The servlet instance failed to initialize.

Action: Check the configuration and the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101142: There was an error unregistering servlet runtime {0}.

Cause: The servlet runtime MBean that is used for monitoring could not be destroyed.

Action: Report this problem to My Oracle Support.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101143: An error occurred while unregistering Web application component runtime {0}.

Cause: The Web application runtime MBean that is used for monitoring could not be destroyed.

Action: Report this problem to My Oracle Support.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101159: [{0}] Received IllegalAccessException while instantiating servlet: "{1}". Ensure that the servlet implementation is a public class.

Cause: This occurs if WebLogic Server attempts to instantiate a servlet class that is not declared public.

Action: Ensure that the servlet implementation is a public class.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101160: Deployment descriptor is malformed; check against the DTD: {0}.

Cause: The web.xml file is not in strict conformance to the DTD. There may be deployment problems if this is not corrected.

Action: Check the web.xml file against the DTD to ensure conformance. Remember that the ordering of elements is important.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101162: User defined listener {0} failed: {1}.

Cause: The listener failed while processing the event fired by the container.

Action: Check the exception for the exact error message and fix the listener code.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101163: Could not load user defined listener: {0}

Cause: The listener class could not be loaded or instantiated.

Action: Check the exception for the exact error message and fix the listener code.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101164: User defined class {0} is not a listener, as it does not implement the correct interface(s).

Cause: The class is invalid.

Action: Fix the listener code to implement the appropriate interfaces.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101165: Could not load user defined filter in web.xml: {0}.

Cause: The filter class could not be loaded.

Action: Check the configuration and ensure that the class is available to the context classloader.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101168: The security-role-assignment references an invalid security-role: {0}.

Cause: The security-role-assignment specified in weblogic.xml is not valid.

Action: Ensure that the role-name defined in web.xml is valid. Also, check the DTD and examples for the correct syntax.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101169: The servlet {0} is referenced but not defined in web.xml.

Cause: The servlet-mapping element in web.xml refers to a servlet name that was not defined.

Action: Ensure that the servlet-name that is used for the mapping is defined. Check the DTD for the correct syntax.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101170: The servlet {0} is referenced in servlet-mapping {1} but not defined in web.xml.

Cause: The servlet-mapping element in web.xml refers to a servlet name that was not defined.

Action: Ensure that the servlet-name that is used for the mapping is defined. Check the DTD for the correct syntax.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101171: The web.xml descriptor has no resource-ref entries for the reference-descriptor defined in weblogic.xml.

Cause: The resource-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding resource-ref-name defined in web.xml.

Action: Ensure that the resource-ref-name matches a resource-ref-name defined in web.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101172: The web.xml descriptor has no ejb-ref entries.

Cause: The ejb-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding ejb-ref-name defined in web.xml.

Action: Ensure that the ejb-ref-name matches a ejb-ref-name defined in web.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101173: Did not find resource-ref in web.xml matching {0}.

Cause: The resource-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding resource-ref-name defined in web.xml.

Action: Ensure that the resource-ref-name matches a resource-ref-name defined in web.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101174: Did not find ejb-ref in web.xml matching {0}.

Cause: The ejb-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding ejb-ref-name defined in web.xml.

Action: Ensure that the ejb-ref-name matches a ejb-ref-name defined in web.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101175: [{0}] Exception occurred while closing zip file {1}.

Cause: A zip file failed to close while undeploying a Web application.

Action: Report this problem to My Oracle Support.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101180: The auth-constraint references security-role: {0}, which is not defined in web.xml.

Cause: The auth-constraint should refer to roles that have been defined in web.xml.

Action: Add the definition of this role in the security-role element of web.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101188: A bad exception-type exists in web.xml: {0}.

Cause: An invalid class can cause this exception while registering the Web application.

Action: Check the classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101189: Could not load the url-match-map class defined in weblogic.xml: {0}.

Cause: An invalid classname will cause this exception while registering the Web application.

Action: Check the classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101194: The preprocessor {0} is referenced but not defined in weblogic.xml.

Cause: The preprocessor element is not defined in weblogic.xml.

Action: Check the weblogic.xml descriptor.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101196: [{0}]: Error while parsing the Tag Library Descriptor at "{1}".

Cause: A TLD parsing exception occurred.

Action: Check the exception for the exact cause.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101198: Could not deploy role: {0} for Web application: {1} application: {2}.

Cause: The Web application could not deploy the role defined in web.xml.

Action: Ensure that security is configured properly in the server. Also, check the stack trace for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101199: Could not deploy policy for resource: {0}.

Cause: The Web application failed to deploy the policy for the security-constraint defined in web.xml.

Action: Ensure that security is configured properly in the server. Also, check the stack trace for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101200: CacheFilter not caching the response for URI: {0} reason: {1}

Cause: The CacheFilter does not cache responses unless the status is 200.

Action: Check the message for information on how to fix the problem.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101212: {0}:{1} Failure while precompiling JSPs: {2}.

Cause: The JSPs failed to precompile at startup.

Action: Check the exception for the exact cause.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101214: Included resource or file "{0}" not found from requested resource "{1}".

Cause: The included resource or file is missing.

Action: Add the missing resource or file.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101215: Malformed request "{0}". Request parsing failed, Code: {1}

Cause: The request does not follow the pattern specified by the HTTP 1.0/1.1 specification(s).

Action: Fix the client that sent the invalid request.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101216: Servlet: "{0}" failed to preload on startup in Web application: "{1}".

Cause: The servlet that was marked as load-on-startup failed to preload on startup.

Action: Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101217: Cannot deploy {0} from {1} on {2}, because there is already a Web application named {3} loaded from {4}, using the context path {5}.

Cause: The Web application that is being deployed has been assigned a context path that is already in use.

Action: Choose a different context path.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101218: An error exists in web.xml for servlet "{0}". Neither servlet-class nor jsp-file is defined.

Cause: The servlet element should contain either servlet-class or jsp-file. Both are missing.

Action: Update the web.xml descriptor.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101220: An error occurred while setting the document root for "{0}" to "{1}".

Cause: Setting the document root for the Web application failed. The Web application will not be deployed.

Action: Check the IOException message for exact cause of the problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101221: The url-pattern is empty or null for url-pattern {0} in {1}.

Cause: Not a valid url-pattern for the servlet.

Action: If the servlet is intended to be a default servlet, then specify / or /*.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101223: {0}: The server {1} is temporarily suspended.

Cause: The server has been suspended by the administrator.

Action: Wait until it comes back up again.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101226: AuthFilter: {0} invocation failed in: {1} phase for URI: {2}

Cause: The authentication filter that acts before and after the authentication phase failed to execute.

Action: Check the exception for the exact cause of the problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101228: Failed to undeploy security policy for resource: {0} while undeploying Web application.

Cause: The security policy defined in web.xml failed to undeploy upon Web application undeployment.

Action: Check the exception for the exact cause of the problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101229: Failed to undeploy security policy for resource: {0} while undeploying the Web application.

Cause: The security role defined in web.xml failed to undeploy upon Web application undeployment.

Action: Check the exception for the exact cause of the problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101231: The HTTP log file does not use version 1.0 of the Extended Log File format.

Cause: The ELF headers in the existing log file specify a version other than 1.0.

Action: Only version 1.0 is supported. Delete the existing log file and start over again.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101232: An exception occurred while reading headers of HTTP log file.

Cause: An IOException was received while reading the headers.

Action: Check the exception for the exact cause of the problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101234: Attempting to initialize ExtendedLogFormat application specific header: {0}. However, initialization failed due to an exception.

Cause: An unexpected error occurred while initializing the log file format.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101235: Attempting to initialize ExtendedLogFormat application specific header: {0}. However, initialization failed because class: {1} is not an instance of weblogic.servlet.logging.CustomELFLogger.

Cause: An unexpected error occurred while initializing the ExtendedLogFormat.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101236: The format of log field {0} is incorrect.

Cause: The format of the log field is invalid.

Action: Check the log field and fix the format.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101237: HTTP logging has been disabled for the Web server: {0}.

Cause: This is a debug message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101242: Failed to roll the HTTP log file for the Web server: {0}.

Cause: An unexpected error occurred.

Action: Check the exception message for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101247: {0}: Public ID references the old version of the Servlet DTD. Change the public ID in web.xml file to "{1}".

Cause: The public ID in WEB-INF/web.xml references the old version of servlet DTD.

Action: Generally, this will not cause any problems with the application unless the DTD has changed in a way such that the web.xml cannot be parsed. To avoid the message, change the public ID in the web.xml file to the current version of the servlet DTD.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101248: [{0}]: Deployment descriptor "{1}" is malformed. Check against the DTD: {4} (line {2}, column {3}).

Cause: The descriptor file is not in strict conformance to its DTD. There may be deployment problems if this is not corrected.

Action: Check the descriptor file against the DTD to ensure conformance. Remember that the ordering of elements is important.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101249: [{0}]: Servlet class {2} for servlet {1} could not be loaded because the requested class was not found in the classpath {3}. {4}.

Cause: The servlet class was not recognized by the Web application classloader.

Action: Ensure that the servlet class is available either in WEB-INF/classes or WEB-INF/lib or the system classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101250: [{0}]: Servlet class {2} for servlet {1} could not be loaded because a class on which it depends was not found in the classpath {3}. {4}.

Cause: One of the classes the servlet class uses was not recognized by the Web application classloader.

Action: Make sure the class is available either in WEB-INF/classes or WEB-INF/lib or system classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101251: [{0}]: Could not load servlet class {2} for servlet {1} because a resource on which it depends was not found in the classpath {3}. {4}.

Cause: This exception occurs if the Java Virtual Machine (JVM) cannot find an appropriate native-language definition of a method that is declared native.

Action: This could be due to a problem with path/LD_LIBRARY_PATH. Check if the resource it complains about exists.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101252: [{0}]: Servlet class {2} for servlet {1} could not be verified. {3}.

Cause: This exception occurs when the "verifier" detects that a class file, though well formed, contains some sort of internal inconsistency or security problem.

Action: Verify the servlet class.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101253: [{0}]: Servlet class {2} for servlet {1} could not be defined. The class file could be corrupt. {3}.

Cause: This exception occurs when the Java Virtual Machine (JVM) attempts to read a class file and determines that the file is malformed or otherwise cannot be interpreted as a class file.

Action: Check to see if the class file is corrupt.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101254: [{0}]: Servlet class {2} for servlet {1} could not be handled by the classloader with classpath {3}. {4}.

Cause: Subclasses of LinkageError indicate that a class has some dependency on another class; however, the latter class has incompatibly changed after the compilation of the former class.

Action: Check the class and its dependencies.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101256: The run-as user: {0} for the servlet: {1} for Web application: {2} could not be resolved to a valid user in the system. Verify that the user exists.

Cause: The run-as element in weblogic.xml refers to an invalid user.

Action: Check to see if the user exists.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101257: Failed to parse the client certificate in header: {0}. Ignoring this certificate.

Cause: The format of the client certificate was invalid.

Action: Check the exception for more details.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101258: Invalid JSP parameter in weblogic.xml with name: {0}.

Cause: The JSP parameter was not recognized.

Action: Check the weblogic.xml descriptor and refer to the DTD for the correct syntax and element information.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101260: The JSP parameter name in weblogic.xml is empty.

Cause: One of the mandatory elements in weblogic.xml was found to be empty.

Action: Check the weblogic.xml descriptor.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101261: Invalid session parameter name in weblogic.xml: {0}.

Cause: One of the session parameters configured in weblogic.xml was invalid.

Action: Check the weblogic.xml and correct the session parameter.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101262: The session parameter name "{0}" in weblogic.xml is deprecated.

Cause: This parameter has been deprecated.

Action: See the WebLogic Server documentation for an alternative. This parameter might be removed from future releases.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101263: The session parameter name in weblogic.xml is empty.

Cause: The param-name element is a mandatory element.

Action: Check the weblogic.xml descriptor.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101264: {0}: CLIENT-CERT-based authentication failed.

Cause: Authentication failed.

Action: Either the certificate was missing or the user the certificate resolves to is not a valid user in the system.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101267: Failed while destroying filter: {0}.

Cause: Destroying the filter on the Web application undeploy failed.

Action: There might be a problem in the implementation of the destroy method. Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101268: {0}: Failed while destroying servlet: {1}.

Cause: Destroying a servlet on the Web application undeploy failed.

Action: There might be a problem in the implementation of the destroy method. Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101271: The url-pattern element is not specified for the web-resource-collection/web-resource-name: {0} in the web.xml descriptor.

Cause: The url-pattern element is a mandatory element.

Action: If you want the security constraint to apply for all requests, specify url-pattern=/*.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101275: Server has detected non-replicated sessions while SUSPENDING. Server will wait for non-replicated sessions to either become invalidated or timed out or will wait until a secondary is chosen using the lazy process (meaning if a session does not have a secondary, the server waits until the next request to create the secondary). The current timeout value is {0} seconds. To terminate non-replicated sessions immediately, use the FORCESHUTDOWN option.

Cause: During graceful shutdown, the server waits for inflight work to complete. This includes non-replicated sessions.

Action: No action is required. Use FORCESHUTDOWN to ignore inflight work and force shutdown of the server.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101276: Web application(s) {1} still have non-replicated sessions after {0} minutes of initiating SUSPEND. Waiting for non-replicated sessions to finish.

Cause: The server is waiting for sessions to finish before gracefully shutting down.

Action: No action is required. Use FORCESHUTDOWN to ignore inflight work and shutdown the server.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101277: Web application(s) {0} has {1} non-replicated session(s) respectively.

Cause: The server has detected non-replicated sessions while gracefully shutting down.

Action: No action is required. Use FORCESHUTDOWN to ignore inflight work and shut down the server.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101278: There are no active sessions. The Web service is ready to suspend.

Cause: All active sessions have completed. The Web service is ready to gracefully shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101280: Failed to create WebServerRuntimeMBean for the Web server: {0}.

Cause: The Web server creates a runtime MBean during the initialization phase for monitoring.

Action: Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101282: {0}: jspServlet "{1}" defined in weblogic.xml could not be registered. It should be a subclass of javax.servlet.http.HttpServlet.

Cause: The user-defined class should be a subclass of javax.servlet.http.HttpServlet.

Action: The jspServlet class must be a subclass of javax.servlet.http.HttpServlet.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101283: {0}: jspServlet "{1}" defined in weblogic.xml could not be loaded.

Cause: The user-defined class was unable to load.

Action: Ensure that the class appears in the webapp-classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101287: {0}. The servlet: {1} received an exception during servlet destroy. Ensure that the super.init(config) is called in the init() method.

Cause: This is due to a bug in javax.servlet.GenericServlet.

Action: Ensure that the super.init(config) is called in the init() method for the servlet.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101288: Application:{0} WebAppModule: {1} failed to set contextPath: {2}.

Cause: The set context path call failed for the MBean.

Action: Check that the context path assigned to this Web application module is valid.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101291: The webAppModule: {1} in application: {0} is unable to reload classes because it shares a classloader with other modules.

Cause: An attempt to reload a class was made when the classloader was shared by other modules.

Action: Ensure that the module has its own classloader or reload all modules that share the classloader at once.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101292: Validation failed for the descriptor: {0} param: {1}.

Cause: The container found an illegal value assigned to this parameter.

Action: Check the error message for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101295: Recompiling JSP [{0}], resource [{1}], because it is stale. It was previously compiled using a different version of WebLogic Server. JSP build version: {2} WebLogic Server build version: {3}.

Cause: A JSP was compiled using a different version of WebLogic Server or JSPC.

Action: To precompile JSPs, ensure that you precompile them using the same version, service pack, rolling patches, and temporary-patches in your classpath for WebLogic Server or JSPC. This will ensure the same version string and compatibility at runtime.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101296: Unable to load the default compiler class "{0}". Using the default javac compiler to compile JSPs.

Cause: The compiler class was not found and hence could not be loaded.

Action: Ensure that the class exists in the classpath.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101297: The value assigned to the container-descriptor parameter: index-directory-sort-by in weblogic.xml is invalid: {0}. The valid values are "NAME", "LAST_MODIFIED", or "SIZE".

Cause: An invalid value is specified in weblogic.xml for the container-descriptor parameter: index-directory-sort-by.

Action: Fix the values in the weblogic.xml descriptor. Valid values are "NAME", "LAST_MODIFIED", or "SIZE".
Level: 1

Type: ERROR

Impact: HTTP

BEA-101299: The servlet-mapping for servlet-name "{0}" will override the default mapping for *.jsp. This can lead to a show code vulnerability.

Cause: The url-pattern *.jsp is being overriden in the web.xml by a user-defined servlet.

Action: Since the default JSP servlet will be overriden, care must be taken to ensure that JSP source code does not appear directly on the browser.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101302: Web application: {0}, the {1} role: {2} defined in the descriptor: {3} has not been mapped to a principal name in weblogic.xml. Will use the first principal-name: {4} specified in security-role-assignment as the run-as-identity. The run-as role can be mapped to a principal name in weblogic.xml using either run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.

Cause: No mapping was found for the run-as role in weblogic.xml.

Action: Since the server has decided to use the implicit map, ensure that this is the principal-name you intended to use. The run-as role can be mapped to a principal name in weblogic.xml using either the run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101303: Web application: {0}, the {1} role: {2} defined in the descriptor: {3} has not been mapped to a principal name in weblogic.xml. Also there is no security-role-assignment defined for this role. Will use the rolename itself as a principal-name for {1} for the servlet. The run-as role can be mapped to a principal name in weblogic.xml using either the run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.

Cause: No mapping was found for the run-as role in weblogic.xml.

Action: Since the server has decided to use the implicit map, ensure that this is the principal-name you intended to use. The run-as role can be mapped to a principal name in weblogic.xml using either the run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101304: Web application: {0}, the {1}: {3} defined in web.xml {2} not been mapped to principals in security-role-assignment in weblogic.xml. Will use the rolename itself as the principal-name.

Cause: Did not find a mapping for the roles which were supposed to be mapped to a principal in security-role-assignment in weblogic.xml.

Action: Since the server has decided to use the implicit map, ensure that this is the principal-name you intended to use.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101305: [{0}] Error-page location: "{1}" for the error code: "{2,number}" causes an infinite loop condition as it throws the same code for which it has been mapped.

Cause: The servlet for the error-page, which maps to the given error code, throws the same error code. This causes an infinite loop condition.

Action: Fix the error page.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101306: Could not resolve entity "{0}" for the webapp at: "{1}". Check the DTD reference in the corresponding descriptor (web.xml/weblogic.xml).

Cause: The descriptor validation failed.

Action: Check the DTD and ensure that the descriptors comply with that. Check the exception message for more details. Also, ensure that there are no typos in the DOCTYPE header.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101307: Got an error while resolving entity "{0}" for the Web application at: "{1}". Check the DTD reference in the corresponding descriptor (web.xml/weblogic.xml).

Cause: The descriptor validation failed.

Action: Check the DTD and ensure that the descriptors comply with that. Check the exception message for more details. Also, ensure that there are no typos in the DOCTYPE header.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101310: Web server: {0}, failed to perform batched update for replicated sessions against jndiname: {1} on the secondary server: {2} http-port: {3} https-port: {4}

Cause: The Remote Management Interface (RMI) call from the trigger, which was intended to periodically update the read-only replicated sessions on the secondary server, failed.

Action: Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101317: The Web application: {0} has specified DIGEST as the auth-method in web.xml, which is not implemented. Will default to BASIC.

Cause: DIGEST authentication is not yet implemented. The Web application will fallback to BASIC authentication.

Action: Choose either BASIC, FORM, or CLIENT-CERT.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101318: The Web application: {0} has specified: {1} as the auth-method in web.xml, which is not valid. Valid values are BASIC (default), FORM, and CLIENT-CERT.

Cause: An invalid authentication method was specified in web.xml.

Action: The valid values are BASIC, FORM, and CLIENT-CERT. Fix the web.xml file for the Web application.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101319: The Web application: {0} has "FORM" based authentication specified but the mandatory element: {1} is left blank.

Cause: The form-login-page and form-error-page are mandatory elements when auth-method is "FORM."

Action: Fix the web.xml for the specified Web application.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101325: The local-path: {1} specified for the virtual-directory-mapping specified in weblogic.xml for the Web application: {0} (docroot={2}), is not valid.

Cause: A relative path was possibly assigned to the local-path. If so, the container makes the path relative to the document root.

Action: Ensure that the relative path exists with respect to the document root.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101326: The element: {1} contains an undefined security-role: {0}

Cause: The security-role definition is mandatory.

Action: Ensure that the security role-name is defined in web.xml. Also check the DTD and examples for the correct syntax.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101327: The element: {0} is not allowed to appear more than once in the descriptor: {1}

Cause: The parser found more than one occurrence for the element.

Action: Ensure that than the element appears only once (check the schema).
Level: 1

Type: ERROR

Impact: HTTP

BEA-101328: {0}: invalid dispatcher: {2} for filter-mapping: {1}

Cause: An invalid value was found for the filter mapping dispatcher.

Action: Valid values are: "REQUEST," "FORWARD," "INCLUDE," or "ERROR."
Level: 1

Type: ERROR

Impact: HTTP

BEA-101331: Cannot deploy {0} from {1} on {2}, because there is already a non-versioned Web application named {3} loaded from {4}, using the context path {5}.

Cause: The Web application version that is being deployed has been assigned a context path that is already in use by a non-versioned Web application.

Action: Choose a different context path or undeploy the conflicting Web application.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101332: Failed to register JACC policy context handlers for the Web application container.

Cause: This is an unexpected error.

Action: See the error message for more information.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101337: Received a SecurityException during: {0}, for : {1}, Web application: {2}

Cause: The user does not have enough privileges.

Action: See the error message for more information.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101338: The context parameter "weblogic.httpd.defaultServlet" has been deprecated. Instead, use the servletMapping = "/" to define the default servlet.

Cause: A deprecated context parameter was used.

Action: The servlet weblogic.servlet.FileServlet is the default servlet. If you want to override the default, define a new servlet-mapping in web.xml with url-pattern = "/".
Level: 1

Type: WARNING

Impact: HTTP

BEA-101339: The context parameter: {0} has been deprecated. Instead, use the element: {1} in weblogic.xml.

Cause: A deprecated context parameter was used.

Action: Replace it with the suggested alternative in weblogic.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101340: The context parameter "weblogic.httpd.servlet.classpath" has been deprecated. Instead use manifest classpath or WEB-INF/lib or WEB-INF/classes or virtual-directories in weblogic.xml

Cause: A deprecated context parameter was used.

Action: There are better ways to extend the classpath exposed to the Web application classloader, including virtual-directories and a manifest classpath.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101341: {0}: Class file up-to-date for JSP: {1}

Cause: This message indicates that the class file associated with the JSP is up-to-date.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101342: {0}: Error(s) encountered while precompiling JSP {1} {2}

Cause: The JSP file shown by the error message had errors and could not be precompiled.

Action: Correct the errors shown by the message so that it gets precompiled without errors.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101343: {0}: Attempting to precompile {1}, since the class file associated with it was found to be out-of-date.

Cause: This message indicates that the class file associated with the given JSP was out of date and needs recompilation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101344: {0}: Attempting to precompile {1}, since the class file associated with it was not found in the Web application classpath.

Cause: This message indicates that the class file associated with the given JSP was not found in the Web application classpath and thus needs to be compiled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101345: A change in value was detected for the "Fields" directive in access.log for webserver: {0}. Rotating the access.log. The value defined for the WebServerMBean will take precedence. Default being "time cs-method cs-uri sc-status". Old value: "{1}" and new value: "{2}".

Cause: This message indicates that the value from WebServerMBean.getELFFields() was different that the value in the "Fields" directive on the top of access.log.

Action: Changing the ELF fields by hand editing access.log is no longer supported. Change the access.log "Fields" using the Administration Console.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101346: The virtual host name: {0} being used by the Virtual Host: {1} is already in use by: {2}

Cause: There is duplicate name usage for VirtualHostNames.

Action: Fix the VirtualHostNames fields for the Virtual Host and choose a unique name.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101347: The server channel name (NetworkAccessPoint): {0} being used by the Virtual Host: {1} is already in use by: {2}

Cause: There is uplicate name usage for ServerChannelName for Virtual Hosts.

Action: Fix the ServerChannelName field for the Virtual Host and choose a unique name.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101348: The server channel name (NetworkAccessPoint): {0} being used by the Virtual Host: {1} is not defined. This virtual host will not be deployed.

Cause: The NetworkAccessPoint is not yet defined.

Action: Choose a different NetworkAccessPoint name or define a new one using the Administration Console.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101349: Failed to save the WorkContexts into the session or cache for the request: {0}

Cause: An unexpected exception occurred.

Action: At the end of the request, the Web application container saves the WorkContexts into the session and the local cache in order to propagate them between successive HTTP requests. Contact My Oracle Support and report this problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101350: Web application(s) {2} of module {1} of application {0} has {3} pending session(s) respectively.

Cause: The server has detected pending sessions for the Web application module while the application is gracefully transitioning from running to administration mode.

Action: No action is required. Use the -force option to ignore inflight work and bring the application to administration mode.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101351: Server has detected pending sessions while gracefully transitioning webapp module {1} of application {0} from running to administration mode. Server will wait for pending sessions to either become invalidated or timed out. The current timeout value is {2} seconds. To terminate sessions immediately, use the -force option.

Cause: During graceful transition of the application from running to administration mode, the server waits for inflight work to complete. This includes pending sessions.

Action: No action is required. Use the -force to ignore inflight work and force transition of the application from running to administration mode.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101352: There are no active sessions. The Web application module {1} of application {0} is ready to go into administration mode.

Cause: All active sessions have completed. The Web service is ready to gracefully transition to administration mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101354: Web application(s) {3} of module {1} of application {0} still have pending sessions after {2} minutes of initiating transition from running to administration mode. Waiting for pending sessions to finish.

Cause: The server is waiting for the application sessions to finish before gracefully shutting down.

Action: No action is required. Use the -force option to ignore inflight work and force transition of the application into administration mode.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101355: [{0}] Version {2} is specified for Web Services {1}, but versioning of Web Services is not supported.

Cause: An attempt was made to deploy Web Services with versioning.

Action: Deploy the Web Services (or the application containing the Web Services) without versioning.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101356: Web application: {0} failed to load the shared library (fastfile) for using native I/O in the FileServlet, falling back to the standard I/O.

Cause: An unexpected error occurred while attempting to load the native library (fastfile) for using native I/O in the FileServlet.

Action: Ensure that the shared library (fastfile) exists in a directory that is in the LD_LIBRARY_PATH or PATH. Also, note that native I/O is supported on Windows, Linux, and Solaris. If problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101357: A force graceful production to administration mode transition was initiated. The Web application module {1} of application {0} is ready to go into administration mode.

Cause: A force graceful production to administration mode transition was initiated. The Web service is ready to transition to administration mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101359: The servlet {0} initilization method failed while it was run in the background. The exception was: {1}.

Cause: The servlet initilization method caused an exception.

Action: The cause of the exception must be corrected and then the application should be redeployed.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101360: Recompiling JSP [{0}], resource [{1}], because it is stale.

Cause: The JSP was changed from the last time it was compiled.

Action: The JSP will be always recompiled if it is different from the last compiled version.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101361: [{0}] A library reference in weblogic.xml has an illegal Specification-Version: {1}. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1.

Cause: The Specification-Version of a library reference in weblogic.xml cannot be parsed.

Action: Fix the library's Specification-Version in weblogic.xml to conform to the required version string syntax.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101362: [{0}] could not deserialize the {1} scoped attribute with name: "{2}"

Cause: Classloader changed. When this happens, the old attributes will be deserialized using the new classloader. The classloader can change either as the result of a dynamic reload of classes (controlled by weblogic.xml parameter "reload-check-secs" or upon across webapp dispatch (include or forward).

Action: Ensure that the attribute class is available to the Web application scope and that the attribute class and all the references it holds are serializable.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101363: Application: {0}, Web application: {1} has context-root specified in application.xml: "{2}". The context-root specified in weblogic.xml: "{3}" will be ignored.

Cause: The context-root specified in application.xml takes higher precedence than the one in weblogic.xml.

Action: This is an informational message. Ensure that this is what you intended to do.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101364: {0}:{1} Failure while precompiling JSP: {2}.

Cause: The JSP failed to precompile on a partial update.

Action: Check the exception for the exact cause.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101366: The server could not send the HTTP message during the configured timeout value. The socket has been closed.

Cause: This is an informational message.

Action: Bump up the value of CompleteMessageTimeout. The default is 60 seconds. If you have slow clients that cannot complete the messsage transfer and are getting timed out, raise the value.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101367: An error occurred while extracting archived file for "{0}", located at "{1}".

Cause: An error occurred while extracting the archived WAR file, due to path length limitations on some OS's.

Action: Some OS's only allow a certain number of characters in the file name. This limitation can be noticed when extracting an archive in a deeply nested directory. Since the default temporary directory for extracting all archives is relative to the server root directory, it is recommended that one use the system property weblogic.j2ee.application.tmpDir and set it to a shorter file path, or one could ensure that the server is started in a directory with a shorted file path.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101369: {0}: The encoding jsp-descriptor parameter has been deprecated. Consider declaring the encoding in the jsp-config element (web.xml) or as a page directive (pageEncoding) instead.

Cause: {0}: The encoding jsp-descriptor parameter has been deprecated.

Action: Consider declaring the encoding in the jsp-config element (web.xml) or as a page directive (pageEncoding) instead.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101370: There was a failure when merging library descriptors into the application descriptors for application {0}. Ensure that the descriptors are valid. The error is {1}

Cause: The library or the application descriptors are invalid.

Action: Fix the descriptors in the application or the library.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101371: There was a failure when processing annotations for application {0}. Ensure that the annotations are valid. The error is {1}

Cause: The descriptor has an invalid servlet-class, filter-class, or listener-class.

Action: Fix the descriptors in the application or the library.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101372: There was a failure in application {0} when attempting to inject dependencies into {1}. Dependencies will not be injected into this class.

Cause: The annotations defined in the class may be invalid or the descriptor may have conflicting entries.

Action: Check the annotations defined in this class. Also, verify that the descriptor has valid entries.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101373: Reloading classes in application {0} failed due to change of annotations on a refreshed class. Modified or new annotations will not be processed during servlet reload as they involve a non-dynamic change. Redeploy the application for these annotations to be processed.

Cause: New or modified annotations will not be processed in application {0} due to a servlet refresh.

Action: Redeploy the application for reloading classes when annotations are modified.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101374: The Web container failed to look up the transaction associated with the current thread for Web application: ${0}.

Cause: After the response is sent, the container needs to check if there is any active transaction associated with the thread so that it can abort the transaction. See the exception message for more details.

Action: See the exception message for more details.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101375: [{0}]: Error while parsing the JSF Configuration Descriptor at "{1}".

Cause: A JSF Configuration Descriptor parsing exception occurred.

Action: Check the exception for the exact cause.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101376: Unable to purge cache of Bean classes from BeanELResolver, error occurs at "{0}".

Cause: Unable to get the cache property of BeanELResolver.

Action: Contact My Oracle Support and report this problem.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101377: Filtering class loader configuration ignored for web module {1} of application {0}.

Cause: Filtering class loader configuration is only supported in descriptors at the main level of the deployment (for example, in enterprise applications or standalone web applications). This configuration is not supported in Web modules of an enteprise application.

Action: Remove the filtering class loader configuration from the deployment descriptor of web module {1} of application {0}.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101378: The version of OpenJPA shipped with WebLogic Server does not support JPA 2.0. Recompile the application with the JPA 1.0 API JAR available at http://www.jcp.org/en/jsr/summary?id=220.

Cause: The Kodo-OpenJPA persistence provider that ships with WebLogic Server does not support JPA 2.0.

Action: Recompile the application with the JPA 1.0 API jar available at http://www.jcp.org/en/jsr/summary?id=220 or use TopLink if you wish to use a JPA 2.0 persistence provider.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101379: Starting with WebLogic Server 10.3.4.0, some methods changed in the OpenJPA interfaces that ship with WebLogic Server. Recompile the application with the OpenJPA JAR in your WebLogic Server installation.

Cause: Some methods in the OpenJPA interfaces that ship with WebLogic Server have changed.

Action: Recompile the application with the OpenJPA JAR in your WebLogic Server installation.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101380: There is more than one Web fragment with the same name: "{0}".

Cause: There is more than one Web fragment with the same name.

Action: Change the duplicate Web fragment names to avoid the conflict.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101381: Both before others and after others found in Web fragment: "{0}".

Cause: Both before others and after others was found in the Web fragment.

Action: Ensure that the Others element appears only in before or after.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101382: WLServlet annotation cannot be used with WebServlet together.

Cause: WLServlet annotation cannot be used with WebServlet together.

Action: Oracle recommends that you use only servlet 3.0 annotations.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101383: WLFilter annotation can't be used with WebFilter together

Cause: WLFilter annotation can't be used with WebFilter together.

Action: Suggest to use servlet 3.0 annotations only
Level: 1

Type: ERROR

Impact: HTTP

BEA-101384: {0} annotation is deprecated, please use servlet 3.0 annotation instead. App:{1}, Class:{2}

Cause: The older WL annotations are deprecated, and replaced by servlet 3.0 annotations, for example WLServlet is replaced by WebServlet, WLFilter is replaced by WebFilter.

Action: Suggest to use servlet 3.0 annotations instead if WL annotations
Level: 1

Type: WARNING

Impact: HTTP

BEA-101385: WebListener annotation is used illegally, the class annotated by WebListener must implement listener interface

Cause: WebListener annotation is used illegally, the class annotated by WebListener must implement listener interface, for example: javax.servlet.ServletContextListener and so on, please check the servlet 3.0 specification.

Action: The class annotated by WebListener must implement listener interface, for example: javax.servlet.ServletContextListener and so on, suggest to check the servlet 3.0 specification.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101386: The ServletSecurity Annotation is illegal, the root is {0}

Cause: The ServletSecurity Annotation is illegal, the root is {0}.

Action: Suggest not to correct ServletSecurity Annotation accroding to the Servlet 3.0 Specification.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101387: ServletContext has already been initialized, cannot call method {0} any longer.

Cause: ServletContext has already been initialized, cannot call method {0} any longer.

Action: Check Servlet 3.0 Specification and the corresponding javadoc.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101388: The ServletContext was passed to the ServletContextListener.contextInitialized method of a ServletContextListener that was neither declared in web.xml or web-fragment.xml, nor annotated with javax.servlet.annotation.WebListener.

Cause: The ServletContext was passed to the ServletContextListener.contextInitialized method of a ServletContextListener that was neither declared in web.xml or web-fragment.xml, nor annotated with javax.servlet.annotation.WebListener.

Action: Check Servlet 3.0 Specification and the corresponding javadoc.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101389: Cannot add this ServletContextListener

Cause: Because this ServletContext was passed to the ServletContextListener's contextInitialized() method of a ServletContextListener that was neither declared in web.xml or web-fragment.xml, nor annotated with javax.servlet.annotation.WebListener.

Action: Check Servlet 3.0 Specification and the corresponding javadoc.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101390: It is illegal to use both value and urlPatterns attributes together in the same WebServlet/WebFilter annotation: {0}.

Cause: As per the Servlet 3.0 specification, section 8.1, both the value attribute and urlPatterns attribute were detected in the identical WebServlet/WebFilter annotation.

Action: Use either the value attribute or urlPatterns attribute, but not both at the same time in the same annotation.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101391: Circular references found in web fragments relative ordering.

Cause: Circular references found in web fragments relative ordering.

Action: Use absolute ordering to overwrite relative ordering or change relative ordering config.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101392: Glassfish Descriptor element <{0}> was successfully parsed and applied.

Cause: This is an information message.

Action: No action is required if the element parsing was successful.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101393: Glassfish Descriptor element <{0}> is not supported by WebLogic.

Cause: This is an informational message.

Action: No action is required. Note that the element is ignored by the descriptor parser.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101394: The exception "{0}" occurred when processing getParameter or getParameterValues from a multipart value of a ServletRequest.

Cause: The exception "{0}" occurred when processing getPart or getParts from a ServletRequest.

Action: Check whether the size of the uploaded file exceeds the size limit. Check that the content of the post-multipart form data is correct.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101395: Application or module {0} is deployed as a web application.

Cause: The spplication or module {0} was deployed as a web application because there was no hint (descriptors or classes annotated by component annotations) detected. WebLogic Server deploys applications without deployment descriptors or classes annotated by component annotations as web application.

Action: No action is required if the application is a web application or a web module. Otherwise, add the corresponding deployment descriptors so that WebLogic Server can detect the application type correctly.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101396: Either the urlPatterns or the value attribute in the WebServlet annotation MUST be present: {0}.

Cause: As per the Servlet 3.0 specification, section 8.1.1, neither the value attribute nor the urlPatterns attribute was detected in the WebServlet annotation.

Action: Use either the value attribute or urlPatterns attribute, but not both at a same time in the same annotation.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101397: The urlPatterns attribute, servletNames attribute, or value attribute of the WebFilter annotation MUST be specified: {0}.

Cause: As per the Servlet 3.0 specification, section 8.1.2, neither the urlPatterns attribute, servletNames attribute, nor value attribute was detected in the WebFilter annotation.

Action: Use either the urlPatterns, servletNames, or value attribute in the annotation. Do not use both the urlPatterns and value attributes at a same time in the same annotation.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101398: Exception : [{0}][{1}] during request upgrade.

Cause: An error occurred while creating an instance of HttpUpgradeHandler. [{0}][{1}]

Action: Check whether the Implement of HttpUpgradeHandler exists or the class has been put under the correct classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101399: The Web application: {0} has specified DIGEST as the auth-method in web.xml, which is not implemented.

Cause: DIGEST authentication is not yet implemented.

Action: Choose either BASIC, FORM, or CLIENT-CERT.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101400: The value of {0} attribute {1} can not be serialized and will be removed when reloading the application, the class of the value object is {2}.

Cause: An exception occurred when serializing the attribute value.

Action: Either correct the serialization issue of the attribute value class or ignore this warning if it is harmless for application reloading.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101401: The url-pattern {0} in web application {1} is mapped to multiple Servlets.

Cause: The effective web.xml, after merging information from fragments and annotations, contains url-patterns that are mapped to multiple servlets.

Action: Check the web.xml, fragment.xml, and annotations to remove the multiple url-patterns mapping issue of the servlets.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101402: Cannot get Request or Response when the current state is completed or dispatched.

Cause: Try to get Request or Response from a completed or dispatched AsyncContext.

Action: Try to call AsyncContext.getRequest and AsyncContext.getResponse after the asynchronous request is completed or dispatched.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101403: For security constraint with url-pattern {0} in web application {1}, only the http methods "{2}" are covered.

Cause: During application deployment, the container must inform the deployer of any uncovered http methods that are present in the application security constraint configuration resulting from the combination of the constraints defined for the application.

Action: Check the security constraint in the web application. Remove the uncovered http methods.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101404: For security constraint with url-pattern {0} in web application {1}, the http methods "{2}" are uncovered.

Cause: During application deployment, the container must inform the deployer of any uncovered HTTP methods that are present in the application security constraint configuration resulting from the combination of the constraints defined for the application.

Action: Check the security constraint in the web application. Remove the uncovered http omitted methods.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101405: The preliminary servlet {0} defined in web.xml or web-fragment.xml has not been completed through the ServletContext.addServlet() API by any ServletContextListener or ServletContainerInitializer.

Cause: The servlet does not have any servlet-class or jsp-file configured in web.xml or web-fragment.xml. Therefore it does not get completed by by ServletContextListener or ServletContainerInitializer with the programmatically servlet adding API of ServletContext.

Action: Ensure that the servlet is completed in web.xml or web-fragment.xml, or can be completed by ServletContextListener or ServletContainerInitializer with the programmatically servlet adding API of ServletContext.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101406: Filter Name cannot be a Null or Empty string.

Cause: The filter name is a Null or Empty string when calling ServletContext.addFilter().

Action: Check the application. Add a 'not null' string type name for ServletContext.addFilter().
Level: 1

Type: ERROR

Impact: HTTP

BEA-101407: Servlet Name cannot be a Null or Empty string.

Cause: The Servlet name is a Null or Empty string when calling ServletContext.addServlet().

Action: Check the application. Add a 'not null' string type name for ServletContext.addServlet().
Level: 1

Type: ERROR

Impact: HTTP

BEA-101408: [{0}] An error occurred while removing WLDFDataAccessRuntimeMBean.

Cause: The WLDFDataAccessRuntimeMBean associated with Web application {0} could not be removed.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101409: The referenced shared library {0} {1} will be ignored and the {0} library in system class path will be used.

Cause: Since WebLogic Server 12c, application is unnecessary to reference shared library to use JSF/JSTL feature. Since WebLogic Server 12.2.1, the referenced JSTL 1.2 and JSF 2.x shared library in application will be ignored. The JSF/JSTL shared library in system classpath will be used.

Action: The JSF 2.x/JSTL 1.2 library-ref in deployment descriptor should be removed.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-110000: Transaction log record class name encoding error [{0}]: {1}

Cause: An error occurred while writing a record to the transaction log.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: WARNING

Impact: JTA

BEA-110001: Transaction log record encoding error [{0}]: {1}

Cause: An error occurred while writing a record to the transaction log. See the reported exception for more details.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: WARNING

Impact: JTA

BEA-110003: onError() callback exception: {0}

Cause: An error occurred while writing a record to the transaction log.

Action: Check for other log messages that give more information about the failure.
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 error occurred while reading a record from the transaction log. 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: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: JTA

BEA-110008: Log record class readExternal problem [{0}]: {1}

Cause: An error occurred while reading externalized state information for a record from the transaction log. 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: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: JTA

BEA-110011: onRecovery() callback exception: {0}.

Cause: See the message detail.

Action: Check for other log messages that give more information about the failure.
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: An attempt to unregister the Transaction Recovery Service for server [{0}] from the migratable service framework failed.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: WARNING

Impact: JTA

BEA-110209: Registration of Transaction Recovery Service for server [{0}] failed.

Cause: An attempt to register the Transaction Recovery Service for server [{0}] from the migratable service framework failed.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: WARNING

Impact: JTA

BEA-110210: Failback of Transaction Recovery Service for server [{0}] failed.

Cause: Transaction recovery actions are performed for the Transaction Recovery Service for server [{0}]. An attempt to failback the Transaction Recovery Service failed.

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: Transaction recovery actions are performed for the Transaction Recovery Service for server [{0}]. Both the first and second attempt to failback the Transaction Recovery Service failed. JTA is going to give up implicitly failing back the Transaction Recovery Service for server [{0}].

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: The activation of Transaction Recovery Service for server [{0}] failed.

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: The Transaction.getStatus() method was called and the transaction status is not a valid value.

Action: Check for other log messages that give more information about the failure.
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: The heuristic completion status of a transaction is calculated based on the expected and actual completion states of all participants. The logic to determine the heuristic outcome did not account for the combination of the actual and expected completion states.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: WARNING

Impact: JTA

BEA-110407: Unknown state in getStatus(): {0}

Cause: The Transaction.getStatus() method did not recognize the transaction state as a valid state.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: WARNING

Impact: JTA

BEA-110408: An attempt to add a duplicate transaction to the transaction manager list was ignored.

Cause: The internal transaction table of the server already contains the transaction instance being added. This event is innocuous.

Action: Check for other log messages that give more information about the failure.
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: During server initialization, information about the local server could not be obtained from the local JNDI context.

Action: Check for other log messages that give more information about the failure.
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: While attempting to retry the commit phase of a transaction, it was detected that the state of the transaction is not valid. To be in the commit phase, a transaction can only be in the prepared or committing states.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: JTA

BEA-110415: Illegal state. Proceeding with rollback anyway. {0}

Cause: While attempting to retry the rollback of a prepared transaction, it was detected that the state of the transaction is not valid.

Action: Check for other log messages that give more information about the failure.
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: Timer method was called on committed transaction {0}.

Cause: The transaction manager invoked a timer method on a transaction that has already completed. The transaction manager periodically checks for transactions that should be aborted due to timeout. This transaction should have been removed from the internal transaction table.

Action: Check for other log messages that give more information about the failure. No action required.
Level: 1

Type: ERROR

Impact: JTA

BEA-110422: Forcibly aborting a transaction found in an unexpected internal state. Details={0}

Cause: While processing a transaction, the transaction manager detected that the transaction is in an illegal state. The only course of action for the coordinator is to attempt to force a rollback of all participants.

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: The Transaction Manager is in distributed mode and can participate in distributed transactions.

Action: No action is required.
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 for the cause.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-111004: Transaction could not set CoordinatorURL to use AdminChannel downgrading {0}.

Cause: An error occurred while trying to set CoordinatorURL to use AdminChannel.

Action: Check for other log messages that give more information about the failure.
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 is accessible.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-111006: Transaction could not set CoordinatorURL to use SSL URL downgrading {0}

Cause: An error occurred while trying to set CoordinatorURL to use the SSL port.

Action: Check for other log messages that give more information about the failure.
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: The transaction log may contain transaction records for committed two-phase transactions that have not completed committing all resources involved in the transaction..

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111009: activateDeployments failed during initialization. Failing reason: {0}

Cause: During WLS start up, an exception was caught at activateDeployemts.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111010: SetPrimaryStore failed. Failing reason: {0}

Cause: An exception was caught at setPrimaryStore.

Action: Check for other log messages that give more information about the failure.
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: The Transaction Log Primary Store may contain transaction records for committed two-phase transactions that have not completed committing all resources involved in the transaction.

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 exception was caught at close store in retrying setPrimaryStore .

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111013: Recover JDBCStore init store exception: {0}

Cause: An exception occurred when init store.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111014: There is a naming conflict for resource = [{0}]. This resource is being registered by this server and has already been registered in: [{1}].

Cause: This resource is trying to be registered as a NonXAResource but was already registered as an XAResource.

Action: Correct the configuration either by making the resource name unique or by making the resource consistently either an XAResource or a NonXAResource.
Level: 1

Type: ERROR

Impact: JTA

BEA-111015: The commit operation for transaction {0} timed out after {1} seconds.

Cause: The application may take longer than the time that is specified in timeout-seconds in the JTA parameter before issuing the commit.

Action: Increase the transaction timeout-seconds in the JTA parameter or tuning application.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-111016: Recovery is not possible as determiner resource can not be obtained {0}.

Cause: Determiner resource may have been removed or is otherwise unobtainable.

Action: Insure determiner resource can be obtained and has not been removed.
Level: 1

Type: ERROR

Impact: JTA

BEA-111017: Encountered an exception while attempting to acquire a transaction manager for transactional annotation interceptors {0}.

Cause: Examine the root exception to determine the cause of the problem.

Action: Take appropriate action based on the cause.
Level: 1

Type: ERROR

Impact: JTA

BEA-111018: No ComponentInvocation is present for @Transactional annotation processing. The restriction on use of UserTransaction will not be enforced.

Cause: No ComponentInvocation is present for @Transactional annotation processing.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JTA

BEA-111019: The server has detected pending transactions after graceful shutdown in ClientInitiatexTxShutdownService.stop. Continue to work.

Cause: The server has detected pending transactions after graceful shutdown in ClientInitiatexTxShutdownService.stop. Continue to work.

Action: No action is required. Use a forced shutdown command to ignore inflight work and shut down the server immediately.
Level: 1

Type: WARNING

Impact: JTA

BEA-111020: An issue occurred during cross-site recovery processing: {0}.

Cause: A lease store connection or other failures has occurred.

Action: Refer to logs for information on the cause of failure.
Level: 1

Type: WARNING

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: See the message detail.

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: This is an information message.

Action: No action is required.
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: This is an information message.

Action: No action is required.
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: This is an information message.

Action: No action is required.
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: This is an information message.

Action: No action is required.
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: This is an information message.

Action: No action is required.
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: This is an information message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130014: XML cache event: statistics checkpointed.

Cause: This is an information message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130015: XML cache event: cache created. current memory usage (bytes): {0}, current disk usage (bytes): {1}

Cause: This is an information message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130016: XML cache event: cache loaded. Current memory usage (bytes): {0}, current disk usage (bytes): {1}

Cause: This is an information message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130017: XML cache event: cache closed. current disk usage (bytes): {0}

Cause: This is an information message.

Action: No action is required.
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: This is an information message.

Action: No action is required.
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 WebLogic Server 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 WebLogic Server 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: See the message detail.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: WARNING

Impact: Management

BEA-141227: Making a backup copy of the configuration at {0}.

Cause: This happens during certain server lifecycle transitions and during configuration changes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141228: An attempt to back up the configuration to {0} failed with {1}.

Cause: See the message text for the exception message.

Action: Check the exception information included in the message text.
Level: 1

Type: ERROR

Impact: Management

BEA-141229: The upgrade process has been canceled by the user. The server process will not be started.

Cause: The server startup cannot proceed without upgrading the domain.

Action: Upgrade the domain, and then start the server.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141230: Could not locate the descriptor file for System Resource: {0}.

Cause: The descriptor file could not be located in the specified path.

Action: Ensure that the descriptor file is in the appropriate location.
Level: 1

Type: WARNING

Impact: Management

BEA-141231: Could not register the JSR object: {0}.

Cause: There are many possible causes for this warning.

Action: Look at the stack trace and take appropriate action.
Level: 1

Type: WARNING

Impact: Management

BEA-141232: Could not decrypt the {1} attribute value of {2} from the file {0}. The edit session has been canceled. The decryption failed with the exception {3}.

Cause: An invalid encrypted value was found in the edit lock file.

Action: Start a new edit session.
Level: 1

Type: ERROR

Impact: Management

BEA-141233: Could not decrypt the edit lock file {0}. The edit session has been canceled. The decryption failed with the exception {1}.

Cause: An exception occurred when decrypting the edit lock file.

Action: Start a new edit session.
Level: 1

Type: ERROR

Impact: Management

BEA-141234: A rollback of a dynamic change failed. The message for the failure is "{0}". The cause of the exception is "{1}".

Cause: See the message body for the cause.

Action: Look at the possible causes of this error. The cause may give some indication of the possible actions to take.
Level: 1

Type: WARNING

Impact: Management

BEA-141237: Extraneous text found in the config.xml file: {0}.

Cause: This is generally caused by mistakes in hand-edited config.xml files. The config.xml file is a valid XML document, however, the extraneous text is not related to any MBean attributes.

Action: Review the config.xml file for mistakes, such as extra delimeters near the text listed in the error message.
Level: 1

Type: WARNING

Impact: Management

BEA-141238: A non-dynamic change has been made which affects the server {0}. This server must be rebooted in order to consume this change.

Cause: This happens when one or more of the changes made to the configuration affect non-dynamic settings. When this occurs, the affected Managed Servers are determined, and those servers are not updated when the change is activated. In order to consume the change, these servers must be rebooted.

Action: Reboot the named server.
Level: 1

Type: WARNING

Impact: Management

BEA-141239: The non-dynamic attribute {1} on {0} has been changed. This may require redeploying or rebooting configured entities.

Cause: This happens when one or more of the changes made to the configuration affect non-dynamic settings.

Action: The required action, if any, will be indicated in a later log message.
Level: 1

Type: WARNING

Impact: Management

BEA-141240: Found a version {0} config.cml file, but expected a version 9 or higher config.xml file. This could happen if an attempt to boot was made from the config directory rather than the domain root.

Cause: This could happen if an attempt was made to boot from the config directory rather than the domain root. Otherwise, the configuration could be corrupted.

Action: Ensure that the config.xml file is not corrupted and that the boot is attempted from the domain root.
Level: 1

Type: ERROR

Impact: Management

BEA-141241: Found a version {0} config.xml file, but expected a pre-version 9 config.xml file. This could happen if an attempt was made to boot from the config directory rather than the domain root.

Cause: This could happen if a 9.x config.xml file was put in the top level, rather than in the config directory.

Action: Ensure that the config.xml file is in the correct location in the domain.
Level: 1

Type: ERROR

Impact: Management

BEA-141242: Invalid configuration version found at {1} version = {0}.

Cause: WebLogic Server found a config.xml file with a version that does not match any known version of the product.

Action: Ensure that the version string in the config.xml file is valid.
Level: 1

Type: ERROR

Impact: Management

BEA-141243: The property {0} in element {1} has been deprecated in version {2} - {3}.

Cause: The config.xml file contained elements that have been deprecated.

Action: Replace or remove the deprecated configuration artifacts.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141244: Schema validation errors while parsing {0} - {1}.

Cause: The WebLogic Server configuration files are defined by a schema. When parsing these files, they are validated against the schema. This warning indicates that there were problems found during validation. The problems may or may not be fatal, depending on the setting of the system property weblogic.configuration.schemaValidationEnabled.

Action: See the error details for more information on the validation problem.
Level: 1

Type: ERROR

Impact: Management

BEA-141245: Schema validation error in {0}. See the log for details. Schema validation can be disabled by starting the server with the command line option: {1}.

Cause: The WebLogic Server configuration files are defined by a schema. When parsing these files, they are validated against the schema. This warning indicates that there were problems found during validation. The problems may or may not be fatal, depending on the setting of the system property weblogic.configuration.schemaValidationEnabled.

Action: See the error details for more information on the validation problem.
Level: 1

Type: ERROR

Impact: Management

BEA-141246: The configuration directory {0} does not exist.

Cause: The server was booted from a directory that does not contain a configuration directory.

Action: Ensure that the server is booted from a valid domain directory.
Level: 1

Type: ERROR

Impact: Management

BEA-141247: The configuration directory {0} does not exist, and the Administration Server is not available.

Cause: The configuration directory is missing and the Administration Server is not available to download a copy. In this case, the Managed Server cannot boot.

Action: Ensure that either the server is booted from a valid domain directory or that the Administration Server is available.
Level: 1

Type: ERROR

Impact: Management

BEA-141248: The configuration directory {0} is missing the file {1}.

Cause: The server was booted from a directory that does not contain a valid domain configuration.

Action: Ensure that the server is booted from a valid domain directory.
Level: 1

Type: ERROR

Impact: Management

BEA-141249: The configuration directory {0} is missing the file {1}, and the Administration Server is not available to download it.

Cause: The server was booted from a directory that does not contain a valid configuration, and the Administration Server is unavailable to download the current configuration files.

Action: Ensure that either the server is booted from a valid domain directory or that the Administration Server is available.
Level: 1

Type: ERROR

Impact: Management

BEA-141251: The attribute {1} from the element {0} was introduced in version 9.0.0.0 or later and is not valid in a pre-9.0 config.xml file.

Cause: An attribute that was introduced in release 9.0 or later was found in a pre-9.0 config.xml file.

Action: Verify that the upgrade process correctly handles the named elements by reviewing the upgraded configuration files.
Level: 1

Type: WARNING

Impact: Management

BEA-141252: The domain version {0} is greater than the release version {1} of this server.

Cause: The DomainVersion in the configuration used by the Administration Server is not compatible with the release version of this Managed Server.

Action: Update the WebLogic Server installation for this server.
Level: 1

Type: ERROR

Impact: Management

BEA-141253: An error occurred while loading the configuration translator {0} : {1}.

Cause: The message includes the specific cause.

Action: Repair or remove the configuration translator.
Level: 1

Type: WARNING

Impact: Management

BEA-141254: Generating new domain directory in {0}.

Cause: There was no domain directory at the specified location. Either a command line option or user input specified creation of the domain, so generation of the domain is commencing.

Action: No action is required. The domain directory will be generated, and the server will continue to boot normally.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141255: Domain generation completed in {0} milliseconds.

Cause: A new domain has been generated.

Action: No action is required. The server will continue to boot normally.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141256: A RuntimeException occurred while adding or removing a configuration element: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141257: An exception occurred while translating a configuration file: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141258: An exception occurred while constructing an ObjectName: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141259: An exception occurred while sending a Notification: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141260: An exception occurred while removing a Notification: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141261: An exception occurred while unregistering a Notification: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141262: An exception occurred while adding a Filter: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141263: An exception occurred in an MBean customizer: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141264: An exception occurred in an MBeanProxy: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141265: Could not get the configuration lock used to serialize access to the configuration files.

Cause: The lock could not be obtained before the specified timeout period had elasped.

Action: Verify the configuration files and ensure that no server has hung, thereby not releasing the lock.
Level: 1

Type: ERROR

Impact: Management

BEA-141266: Parsing failure in {0}: {1}.

Cause: This error occurs when the configuration file has invalid XML syntax or other errors.

Action: Validate the contents of the configuration file.
Level: 1

Type: ERROR

Impact: Management

BEA-141267: Parsing failure in {0} on line {1}: {2}.

Cause: This error occurs when the configuration file has invalid XML syntax or other errors.

Action: Validate the contents of the configuration file.
Level: 1

Type: ERROR

Impact: Management

BEA-141268: Parsing failure in {0} on line {1}, column {2}: {3}.

Cause: This error occurs when the configuration file has invalid XML syntax or other errors.

Action: Validate the contents of the configuration file.
Level: 1

Type: ERROR

Impact: Management

BEA-141269: The temporary bean tree {0} was allocated for an undo, get, or activate operation, but has not been garbage collected.

Cause: The temporary bean tree has not been garbage collected.

Action: Repeat the specified operation and determine if memory usage in the server is increasing.
Level: 1

Type: WARNING

Impact: Management

BEA-141270: Could not get the configuration lock used to serialize access to configuration files. Retrying for another {0} seconds.

Cause: Another server was reading or writing to the configuration files, and the lock could not be obtained before the specified timeout period had elasped.

Action: No action is required. If the configuration subsystem fails to get the lock, and the number of retries is exhausted, a different message with error severity will be displayed.
Level: 1

Type: WARNING

Impact: Management

BEA-141271: An IOException occurred while recording setAttribute {1} on MBean {0}. Exception: {2}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Take action based upon the provided exception details.
Level: 1

Type: ERROR

Impact: Management

BEA-141272: An IOException occurred while recording invoke {1} on MBean {0}. Exception: {2}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Take action based upon the provided exception details.
Level: 1

Type: ERROR

Impact: Management

BEA-141273: An upgrade framework class was not found. Exception: {0}. The configuration and upgrade framework component may not have been installed.

Cause: The configuration and upgrade framwork component may not have been installed.

Action: Install the Configuration Wizard and pgrade framework component by running the installer again.
Level: 1

Type: ERROR

Impact: Management

BEA-141274: Production mode has been specified at the command line using the the weblogic.ProductionModeEnabled system property. This system property overrides the development mode setting contained in the config.xml file. However, the Administration Console and WLST show the attribute values and defaults that correspond to the development mode specified in the config.xml file.

Cause: The command line overrides are not persisted to the config.xml file.

Action: If the Administration Console or WLST should display production mode defaults for attributes, then enable production mode in the Administration Console or WLST and activate the changes.
Level: 1

Type: WARNING

Impact: Management

BEA-141275: Development mode has been specified at the command line by setting the weblogic.ProductionModeEnabled system property to false. This system property overrides the production mode setting contained in the config.xml file. However, the Administration Console and WLST show the attribute values and defaults that correspond to the production mode specified in the config.xml file.

Cause: The command line overrides are not persisted to the config.xml file.

Action: If the Administration Console or WLST should display development mode defaults for attributes, then enable development mode in the Administration Console or WLST and activate the changes.
Level: 1

Type: WARNING

Impact: Management

BEA-141276: An exception occurred while obtaining the class for interface {0}. The exception is: {1}

Cause: A resource or classloader issue caused the class lookup to fail.

Action: See the underlying exception to troubleshoot further.
Level: 1

Type: WARNING

Impact: Management

BEA-141277: The JMX MBean PlatformMBeanServerUsed attribute is true, but the Platform MBeanServer was created without the hooks for the WebLogic Server security infrastructure. The Platform MBeanServer will not be used and Platform MBeans will not be available using the WebLogic Server Runtime or Domain Runtime MBeanServers. This can occur if Platform MBeanServer system properties or JVM options (-Dcom.sun.management.jmxremote or JRockit -XManagement) were defined. To allow the Platform MBeanServer to be used, either remove the system properties and JVM options or start WebLogic Server with the following system property: -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder To eliminate this log error if Platform MBeans do not need to be available when using WebLogic Server, set the PlatformMBeanUsed attribute in the JMXMBean to false.

Cause: A system property was specified that caused the Platform MBeanServer to be created before the WebLogic Server Runtime MBeanServer.

Action: Remove the system properties or start WebLogic Server with the following system property: -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder.
Level: 1

Type: WARNING

Impact: Management

BEA-141278: Java entropy configuration is: {0}.

Cause: This message is informational and is printed every time WebLogic Server starts.

Action: Change your jave entropy configuration, if needed.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141279: Detected BLOCKING java entropy configuration. This is the most secure setting, but may cause performance issues on machines with few sources of entropy.

Cause: This message is informational and is printed every time WebLogic Server starts.

Action: Change your jave entropy configuration, if needed.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141280: Detected NON-BLOCKING java entropy configuration. This setting will provide the best performance on machines with few sources of entropy, but is less secure than a blocking entropy configuration.

Cause: This message is informational and is printed every time WebLogic Server starts.

Action: Change your jave entropy configuration, if needed.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141281: A ForeignJNDIProvider named {0} has two child ForeignJNDILinks named {1} and {2}, which both have the same LocalJNDIName {3}. This duplication of LocalJNDIName is invalid.

Cause: Two links cannot share the same LocalJNDIName because it would be unclear as to which remote JNDI name to link to.

Action: Change the LocalJNDIName of one of the ForeignJNDILinks.
Level: 1

Type: ERROR

Impact: Management

BEA-141282: Server name {0} not found in domain {1}.

Cause: A managed server is started with -Dweblogic.Name with a value that is not configured in the domain.

Action: Specify the correct value of the param -Dweblogic.Name.
Level: 1

Type: ERROR

Impact: Management

BEA-141283: Server name could not be determined.

Cause: Either the name is not specified or the specified name does not exist in the config.xml file.

Action: Specify the correct value of the -Dweblogic.Name parameter.
Level: 1

Type: ERROR

Impact: Management

BEA-141284: A deprecated MBean for {0} has been removed from the current version of WebLogic Server but still exists in an application configuration file.

Cause: A deprecated MBean for {0} has been removed from the current version of WebLogic Server but still exists in an application configuration file.

Action: Update the configuration file to remove the deprecated MBean.
Level: 1

Type: INTERNAL_ERROR

Impact: Management

BEA-141285: The network access point property {0} was ignored because the specified network access point name was not found.

Cause: The specified network access point does not exist in the configuration.

Action: Modify the system property, and specify a valid network access point name.
Level: 1

Type: WARNING

Impact: Management

BEA-141286: The creation of the dynamic server failed with an exception.

Cause: An exception occurred during the creation of the dynamic server.

Action: Take action based upon the provided exception details, make any required changes, and retry the operation.
Level: 1

Type: WARNING

Impact: Management

BEA-141287: No matching machines were found based on the MachineNameMatchPrefix property. No machine has been calculated for servers from dynamic servers {0}.

Cause: The MachineNameMatchPrefix did not match any of the existing machines in the domain.

Action: Set the MachineNameMatchPrefix property so it matches the machine names in the domain.
Level: 1

Type: WARNING

Impact: Management

BEA-141288: Unable to obtain file lock but will retry.

Cause: This is an informational message only.

Action: If WebLogic Server fails to start because it was unable to obtain the file lock, then the lock files need to be removed manually before restarting WebLogic Server.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141289: Upgrade of 8.1 or prior domains is no longer supported. Convert the {1} from version {0} to 10.x format using weblogic.Upgrade.

Cause: WebLogic Server found a config.xml file with a version that is no longer supported.

Action: Upgrade the config.xml file to a newer version using weblogic.Upgrade from a 10.3 or lower version of the product.
Level: 1

Type: ERROR

Impact: Management

BEA-141290: Configuration plug-in not found for component type "{0}" in location "{1}"

Cause: The plug-in JAR file was not found.

Action: Verify the installation to ensure that the plug-in was installed correctly.
Level: 1

Type: ERROR

Impact: Management

BEA-141291: A system component for component type "{0}" was not defined in config.xml. The file "{1}" will not be distributed to the external server.

Cause: The system component is not defined in config.xml

Action: Define the corresponding system component in config.xml.
Level: 1

Type: WARNING

Impact: Management

BEA-141292: A machine was not specified in the system component "{0}" in config.xml. The file "{1}" will not be distributed to the external server.

Cause: The machine for the system component is not defined in config.xml

Action: Define the corresponding machine in the system component in config.xml.
Level: 1

Type: WARNING

Impact: Management

BEA-141293: Bad CAM replication exclusive file {0} : {1}.

Cause: See the error message for details.

Action: Correct the error in the CAM replication exclusive file.
Level: 1

Type: WARNING

Impact: Management

BEA-141294: Found invalid entries in CAM replication exclusive file {0}: {1}.

Cause: There are invalid entries in the file.

Action: Correct the invalid entries in the file.
Level: 1

Type: WARNING

Impact: Management

BEA-141295: Unable to contact Node Manager on "{1}". Activation for system component "{0}" is deferred until "{1}" becomes available.

Cause: Contact with Node Manager on "{1}" could not be made.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Management

BEA-141296: Unable to contact Node Manager on "{1}". Activation for system component "{0}" is deferred until "{1}" becomes available.

Cause: Contact with Node Manager on "{1}" could not be made.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Management

BEA-141297: Could not get the server file lock. Ensure that another server is not running in the same directory. Retrying for another {0} seconds.

Cause: Another server is running and still has the server lock.

Action: Check to see if another server is running.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141298: Could not register with the Administration Server: {0}

Cause: A network connection failed or an I/O exception occurred.

Action: Check the underlying exception and determine why the Managed Server could not connect to the Administration Server.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141299: An exception occurred during the registration of MBeans in the MBeanServer : {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review the message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141300: The activate changes operation for request "{0}" could not be completed because the activate timed out. Detailed state info is: {1}

Cause: The activate changes operation timed out.

Action: Try increasing the activate changes timeout value. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Management

BEA-141301: Access not allowed for ObjectName: {0}, on action: {1}, target {2} in partition {3}.

Cause: The user does not have enough access to the MBean in the partition.

Action: Check WebLogic Server JMX policies to determine which role is required to access MBeans.
Level: 1

Type: ERROR

Impact: Management

BEA-141302: Access not allowed for Subject: {0}, on resource {1}, action: {2}, target {3}.

Cause: The Subject role for the user does not have enough access to the MBean.

Action: Check WebLogic Server JMX policies to determine which role is required to access MBeans.
Level: 1

Type: ERROR

Impact: Management

BEA-141303: The internal method that you have invoked is not available unless you are running as Kernel. You are running as: {0}

Cause: The Subject role for the user does not have enough access to the MBean.

Action: Check WebLogic Server JMX policies to determine which role is required to access MBeans.
Level: 1

Type: ERROR

Impact: Management

BEA-141304: Access not allowed for Subject roles: {0} on ObjectName {1}: Resource Type: {2}, Action: {3}, Target: {4} in partition {5}

Cause: The person with the specified Subject role does not have enough access to the MBean.

Action: Check WebLogic Server JMX policies to determine which role is required to access MBeans.
Level: 1

Type: ERROR

Impact: Management

BEA-141305: An error occurred while firing an edit DomainMBean reload event: {0}

Cause: EditAccess fires an event when the edit DomainMBean is reloaded but one listener throws an exception.

Action: Check the JMX client.
Level: 1

Type: ERROR

Impact: Management

BEA-141306: JMS configuration error --- {0} ---.If you need to delay fixing this problem, you can force a log message to occur instead of a configuration exception by configuring the "{1}" system property to false. This system property will be removed in a future 12.2.1 stage.

Cause: JMS resource MBean validations failed.

Action: Check the cross MBean relationships of JMS resources.
Level: 1

Type: ERROR

Impact: Management

BEA-141307: Unable to connect to the Administration Server. Waiting {1} second(s) to retry (attempt number {0} of {2}).

Cause: The Administration Server is not available.

Action: Start the Administration Server.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141308: New

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Management

BEA-141309: Initialized

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Management

BEA-141310: Prepared

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Management

BEA-141311: Activated

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Management

BEA-141312: Suspended

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Management

BEA-141313: Automatic resolve operation during startEdit fails. {0}

Cause: {0}

Action: It is recommended to call resolve() manually.
Level: 1

Type: WARNING

Impact: Management

BEA-141314: Use of the GlobalMBeansVisibleToPartitions system property is temporary. It serves only as a transitional aid to the new MBean visibility model. This warning is generated when it is detected that the old MBean visibility model is in use. Switch to the new model by eliminating the use of the -DGlobalMBeansVisibleToPartitions property. This property will be removed prior to August 2015.

Cause: The system property -DGlobalMBeansVisibleToPartitions=true was included in the server startup command.

Action: Remove the system property -DGlobalMBeansVisibleToPartitions=true or use -DGlobalMBeansVisibleToPartitions=false when starting the server.
Level: 1

Type: WARNING

Impact: Management

BEA-141315: Canceling the configuration update failed with an exception. {0}

Cause: An exception occurred during an attempt to cancel an update. {0}

Action: Ensure that the config is valid. Take action based upon the provided exception details, make any required changes, and retry the activate.
Level: 1

Type: WARNING

Impact: Management

BEA-141316: An exception was received during the prepare phase of configuration, the system is attempting to recover. {0}

Cause: An exception occurred during an attempt to prepare an update. {0}

Action: If the system is unable to automatically recover, ensure that the config is valid. Take action based upon the provided exception details, make any required changes, and retry the activate.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141317: Auto-halting partition "{0}" due to config change; no active targeted admin resource groups

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141318: Auto-booting partition "{0}" due to config change; active targeted admin resource groups

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141319: The file distribution servlet failed to initialize JMX default security policies 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: No action is required if REST management support is not required. Otherwise, configure an authorization security provider in the security configuration that implements weblogic.security.spi.PolicyConsumer such as the XACML Authorization provider.
Level: 1

Type: WARNING

Impact: Management

BEA-149000: Unable to create DeployerRuntimeMBean.

Cause: This may occur if an error at the JMX level exists.

Action: Report this problem to My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Deployer

BEA-149001: No application named "{0}" exists for operation "{1}".

Cause: The application name was likely misspelled.

Action: Verify that the application is correctly named.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149002: The source file was not provided for activation of application: "{0}".

Cause: Source files do not exist for the application to be deployed.

Action: Make source files available for the application to be deployed in the said path.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149003: Unable to access application source information in "{0}" for application "{1}". The specific error is: {2}.

Cause: Source files for the application to be deployed are not accessible.

Action: Ensure that no other process is using the source file(s).
Level: 1

Type: WARNING

Impact: Deployer

BEA-149004: Failures were detected while initiating {1} task for application "{0}".

Cause: Task creation can fail for many reasons.

Action: Check the error message and take appropriate action.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149011: Some of the targets in the deployment request are not configured in this domain. The named targets are: "{0}".

Cause: This error occurs when a deployment request is made to a target that is not configured.

Action: Ensure that the target list in the request is correct.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149013: Application "{0}" does not define the module, "{1}". {2} are the known valid module(s) for this application.

Cause: Incorrect deployment information was provided in the activate request.

Action: Ensure that the module information in the request is accurate. If adding modules, ensure that the source file is specified again so that it is reloaded and any new modules are deployed.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149014: Target "{0}" is not defined.

Cause: Incorrect deployment information was provided in the activate request.

Action: Ensure that the target information in the request is accurate.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149015: Unable to add "{0}" to component "{1}".

Cause: The component is already targeted to the server, cluster, or virtual host.

Action: Check the target list.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149021: Rejecting {2} request for application "{1}". The specified ID, {0}, is already being used.

Cause: A {1} request included an ID provided by a user that is already assigned to another task.

Action: Choose a different ID or allow the system to allocate an ID for the request.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149025: An invalid attempt was made to target a non-Web application component, "{1}", in application "{0}" to a virtual host, "{2}".

Cause: An invalid attempt was made to target a non-Web application to virtual hosts.

Action: Correct the target list.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149026: {2} application {0} on {1}.

Cause: This is an informational message about the task description.

Action: This is an informational message about the task description.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149027: Unable to activate the application "{1}" from source "{0}". Reason: {2}

Cause: The application was improperly defined.

Action: Define the application properly.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149028: An invalid path, "{1}", was specified for the application "{0}".

Cause: The configured path for this application does not exist.

Action: Provide the application files in the specified location.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149031: The staging mode of "{0}" is invalid. The legal values are "stage" or "nostage".

Cause: An invalid staging mode has been specified.

Action: Specify a valid staging mode for the deployment request.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149032: An attempt to restart a task has been rejected. The task has already been started.

Cause: This error results if start is called on a task that has already been started.

Action: Do not call start on a task that has already been started.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149033: {2} application {0} on {1}.

Cause: An application-level deployment notification has been reported.

Action: No action is required. This is an informational log message.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149034: An exception occurred for task {0}: {1}.

Cause: An error occurred while reporting the application status.

Action: The error may be due to server instability. Check the health of the server.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149035: Module {0} reported error: {1}.

Cause: The deployment request failed.

Action: Check the exception log and take appropriate action.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149038: Initiating task for {1} : {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149040: An attempt to change the staging mode for the application "{0}" has been rejected.

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

Action: The staging mode cannot be changed once it is set. Try deploying again without changing the staging mode.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149045: An attempt to add cluster target "{0}" was rejected, since cluster member "{1}" is also targeted by module "{2}". Targeting to a cluster member results in different behaviors than targeting to the entire cluster.

Cause: A cluster member is already in the target list of the module.

Action: Remove the cluster member from the target list, or re-target the cluster member rather than the cluster itself.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149048: An attempt to add server target "{1}" to module "{2}" has been rejected. This is because its parent cluster, "{0}", is also targeted by the module.

Cause: The module is already targeted to a cluster that contains the server.

Action: Remove the cluster from the target list or remove the cluster member from the target list.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149054: An attempt to add a virtual host target "{0}" to a non-Web application module "{1}" has been rejected.

Cause: An EJB or connector was attempting to target a virtual host.

Action: Remove the host from target list.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149055: Adding server {1} of cluster {0} as a target for module {3}. This module also includes server {2} that belongs to this cluster as one of its additional targets. Having multiple individual servers of a cluster as targets instead of having the entire cluster as the target can result in non-optimal load balancing and scalability. Therefore, this is not usually recommended.

Cause: The module is already targeted to a different cluster member.

Action: Target the entire cluster to the module.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149058: Distribute can only have stage as its staging mode. Application "{0}" has {1} as its staging mode.

Cause: This is an unexpected error.

Action: Specify a valid staging name.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149059: Module {1} of application {0} is transitioning from {2} to {3} on server {4}.

Cause: A module is being deployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149060: Module {1} of application {0} successfully transitioned from {2} to {3} on server {4}.

Cause: A module is being deployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149061: Module {1} of application {0} failed to transition from {2} to {3} on server {4}.

Cause: An error was encountered during a module deployment.

Action: Details of the specific failure are documented in the associated log entries. Take appropriate action.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149062: The task containing ID {0} cannot be canceled, since it has already completed execution.

Cause: An attempt has been made to cancel a deployment task that has completed execution.

Action: Do not attempt this operation on a completed task.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149066: Unable to deploy application "{0}", because module "{1}" does not provide a valid URI.

Cause: The application is incorrectly configured.

Action: Provide a URI for the module, or remove the application from the configuration.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149068: This is an unexpected exception.

Cause: An unexpected exception occurred.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149069: Deploying {0} using a deprecated protocol.

Cause: The application is configured with TwoPhase=false or is not a recognized type of application. For example, an application that is not an EAR file (no application.xml) but has multiple modules will not be deployed with the two-phase protocol.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149073: The application "{0}" has no configured modules.

Cause: The application is improperly configured.

Action: The application will be marked as undeployable. After resolving configuration issues with the application, the administrator can retry the deployment.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149074: Successfully completed deployment task: {0}.

Cause: A deployment operation was requested.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149078: Stack trace for message {0}

Cause: A deployment failure occurred.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149080: A partial update of an archived application is not allowed. Application "{0}" cannot be redeployed.

Cause: There was an attempt to partially redeploy an archived application.

Action: Try deploying the entire application.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149081: Cannot {2} application, "{0}", with version "{1}". The application was previously deployed without a version.

Cause: An attempt was made to {2} a versioned application when it was previously deployed without a version.

Action: Try {2} without a version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149082: Cannot {2} application "{0}" without a version. The application was previously deployed with version "{1}".

Cause: An attempt was made to {2} an application without a version when it was previously deployed with a version.

Action: Try {2} with a version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149083: An attempt was made to activate the application "{0}" when stop was in progress.

Cause: An attempt was made to activate the application "{0}" when stop was in progress.

Action: Try to activate the application "{0}" again after the stop is done. If it is a graceful stop, stop the application forcefully to end the graceful stop immediately.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149085: No application version was specified for application "{0}". The {2} operation will be performed against the currently active version "{1}".

Cause: No application version was specified for the operation.

Action: Verify that the currently active version is the desired version for the operation. If not, perform the operation again with the -app_version operation to specify a particular version.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149086: The application {0} is being retired gracefully.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149087: The application {0} will be retired after {1} seconds.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149088: The retirement for application {0}, which was scheduled to happen after {1} seconds, is canceled.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149089: An attempt was made to activate the application "{0}" when retirement was in progress.

Cause: An attempt was made to activate the application "{0}" when retirement was in progress.

Action: Try to activate the application "{0}" again after the retirement is done. If it is a graceful retirement, undeploy the application to end the graceful retirement immediately.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149091: An attempt was made to deploy application "{0}" with specified archive version "{1}". However, the application archive, as specified in the source, has version "{2}".

Cause: This error occurs when an attempt is made to specify a version that is different from the manifest version of the application archive in the source location.

Action: Perform the deployment again without specifying the version, or specify version "{2}" instead of "{1}".
Level: 1

Type: ERROR

Impact: Deployer

BEA-149092: The source is not specified for the deployment operation of application "{0}", and the expected version is "{1}". However, the application archive at the source location for a previous deployment of version "{1}" now has version "{2}".

Cause: The source is not specified for the deployment operation of application "{0}", and the expected version is either explicitly specified or the currently active version. However, the application archive at the previously configured source location of the expected version has a different manifest version.

Action: Perform deployment again specifying either the source location or version "{2}".
Level: 1

Type: ERROR

Impact: Deployer

BEA-149093: No version specified for the versioned application named "{0}" for operation {1}, and no active version is available.

Cause: The version was not specified for the operation when no currently active version was available.

Action: Specify the version of the application for the operation.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149095: The application {0} is being retired now.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149096: Operation {1} is deprecated and cannot be applied to versioned application "{0}". Use operation {2} instead.

Cause: An attempt was made to perform the deprecated operation {1} on a versioned application. Use operation {2} instead.

Action: Use operation {2} instead.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149097: The retirement for application "{0}" failed.

Cause: This may have happened due to a problem with accessing the persistent store.

Action: Check for other log messages that give more information about the failure.
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: The deployment subsystem was unable to complete the persistence of the active application version state.

Action: Check for other log messages that give more information about the failure.
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: The deployment configuration could not be obtained.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149117: {2} library {0} on {1}.

Cause: This is an informational message about the task description.

Action: This is an informational message about the task description.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149118: "{1}" is not targeted to "{0}".

Cause: An attempt was made to undeploy the application from a target where it is not deployed.

Action: Correct the target list for the operation.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149119: Different targets cannot be specified when deploying a new version "{1}" of application "{0}". The targets specified, "{3}", are different from those of the previous version, "{2}".

Cause: An attempt was made to deploy a new application version with targets that are different from that of the previous version.

Action: Try deploying again without specifying targets, or specify the exact same target as the previous version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149120: The plan version "{1}" cannot be specified when deploying a non-versioned application "{0}".

Cause: An attempt was made to deploy a non-versioned application with a plan version.

Action: Try deploying again with an application version or without the plan version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149121: Rejecting {1} request for application {0} because the deployment service is not started.

Cause: A deployment operation was attempted when the server was starting or shutting down.

Action: Perform the deployment operation again after the server has started or before the server has shut down.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149122: Deployment perations on internal application "{0}" are not permitted;.

Cause: Deployment operations are not permitted on internal applications.

Action: Do not attempt any deployment operations on internal applications.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149123: The application "{0}" currently has security model "{1}", and an attempt was made to redeploy the application again with a different security model "{2}". The specified security model will be ignored for the current deployment operation. To change the security model, undeploy the application and deploy it again with the new security model.

Cause: An attempt was made to redeploy the same application with a different security model.

Action: Undeploy the application and deploy it again with the new security model.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149124: Failures were detected while initiating {1} task for application "{0}". Error is: "{2}"

Cause: Task creation can fail for many reasons.

Action: Check the error message and take appropriate action.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149125: No application version was specified for the {0} operation of application "{1}". The {0} operation will be performed against the retired application version "{2}".

Cause: This is an informational message only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149126: No application version was specified for the {0} operation of application "{1}". The application version "{2}" will not be removed as its retirement is still in progress. Oracle recommends that the application version "{2}" be undeployed explicitly after the retirement is done. An explicit undeploy of the application version can also be performed before retirement is done; however, exercise caution as this may interrupt inflight work.

Cause: No application version was specified for the {0} operation of application "{1}".

Action: No action is required.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149127: Failures were detected while initiating "{0}" task. Error is: "{1}"

Cause: Task creation can fail for many reasons.

Action: Check the error message and take appropriate actions.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149128: The "{1}" option was specified for the {0} operation of application "{2}". The {0} operation will be performed against the retired application version "{3}".

Cause: This is an informational message only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149129: The "{1}" option was specified for the {0} operation of application "{2}". The {0} operation will be performed against the retiring application version "{3}". Note that retirement is still in progress for version "{3}" and any inflight work will be interrupted.

Cause: This is an informational message only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149130: The "{1}" option was specified for the {0} operation of application "{2}". The {0} operation will be performed against the currently active version "{3}".

Cause: This is an informational message only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149131: Cannot perform operation {2} because application "{0}" is in state {1}

Cause: The application is no longer active.

Action: Ensure that the application is active. Deploy again if needed.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149132: Split directory application {0} can only be deployed on the Administration Server.

Cause: An attempt was made to perform the deployment operation on the split directory application on a server other than the Administration Server.

Action: For split directory application {0}, perform deployment operations on the Administration Server alone.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149133: Auto-deployed application {0} can only be deployed on the Administration Server.

Cause: An attempt was made to perform the deployment operation on the auto-deployed application on a server other than the Administration Server.

Action: For auto-deployed application {0}, perform deployment operations on the Administration Server alone.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149134: A redeploy was performed without specifying -source for the archived versioned application "{0}". Partial update of an archived application is not allowed. To perform production redeployment of versioned applications, specify -source with the redeploy operation.

Cause: An attempt was made to partially redeploy an archived application.

Action: Specify -source for production redeployment, or redeploy the entire application.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149135: Operation {2} cannot be performed since application "{0}" is not deployed on the target "{1}".

Cause: Operation {2} could not be performed because the application was not deployed on the provided target.

Action: Rery with a valid target.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149137: {0} is an invalid path for partial redeployment. The URI of the file or directory to be redeployed should be relative to {1}, the root of the enterprise application, or to the standalone module being redeployed.

Cause: The file could not be located in the application.

Action: Use a valid specification for the file.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149138: A subset of the originally configured targets for the application "{0}" was specified. This can potentially lead to out-of-sync applications between the different server targets. The targets specified, "{2}", are different from those of the previous version, "{1}".

Cause: A deployment operation was performed on an existing application with a subset of the originally configured targets.

Action: If the application content has changed since the last operation, Ensure that all configured targets are updated. To do so, repeat the operation without specifying targets in order to automatically use the configured targets.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149139: Application "{0}" is targeted to cluster "{1}", and provided the target for {3} operation is "{2}". The {3} operation on a subset of the targeted clustered servers is not supported.

Cause: The {3} operation was attempted on one or more servers in the targeted cluster.

Action: Retry with the targeted cluster, or undeploy from the cluster and deploy to the desired individual servers.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149140: The task cannot be processed further until the current edit session is activated. When this occurs, task processing will continue. The user can exit the deployer tool without affecting the task.

Cause: The user is the current owner of the domain configuration edit lock.

Action: Activate (or cancel) the edit session. The user can exit the deployer tool without affecting the task.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149141: The AppDeploymentMBean already exists for application "{0}".

Cause: The AppDeploymentMBean already exists for application "{0}".

Action: Ensure that different applications do not have the same name.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149142: Cluster target "{0}" is configured with no servers, and therefore configuration is updated.

Cause: A deployment to a cluster target was attempted, but the cluster contains no servers.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149143: Submodule targets in an application must be specified with the correct module name.

Cause: A submodule target was specified incorrectly.

Action: Ensure that the submodule target was specified with the correct syntax and with the correct module name.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149145: Unable to contact "{0}". Deployment is deferred until "{0}" becomes available.

Cause: Contact with "{0}" could not be made. Deployment is deferred until "{0}" becomes available.

Action: No action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149146: Attempt to reach the Administration Server with alternate URL: "{0}" failed.

Cause: The attempt to reach the Administration Server with the alternate URL: "{0}" failed.

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149147: Could not reach the Administration Server through any of its URLs: "{0}".

Cause: The Administration Server could not be reached through any of its URLs: "{0}".

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149148: Exception occurred while receiving a message on loopback.

Cause: An exception occurred while receiving a message on loopback.

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149149: Malformed URL: "{0}".

Cause: The URL: "{0}" was malformed.

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149150: An IOException occurred while reading the input.

Cause: An IOException occurred while reading the input.

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149151: Could not find a registered DeploymentReceiver to handle requests for "{0}".

Cause: A registered DeploymentReceiver could not be found to handle requests for "{0}".

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149152: No deployment request for which to set up the context.

Cause: No deployment request for which to set up the context.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149153: A "prepare" message was received for ID "{0}" that has already been completed or canceled.

Cause: A "prepare" message was received for ID "{0}" that has already been completed or canceled.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149154: A "get deployments response" message was received for ID "{0}" that has no request. It may have already been completed or may have been canceled.

Cause: A "get deployments response" message was received for ID "{0}" that has no request. It may have already been completed or may have been canceled.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149155: Received "get deployments response" message "{0}" while already handling one. Ignoring the second request.

Cause: A "get deployments response" message "{0}" was received while another was being handled. The second request was ignored.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149156: Illegal state for operation start: "{0}".

Cause: The start operation was called on an application that either had an update pending or was used with the administration mode flag.

Action: To move the application from active to administration mode, use the stop operation.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149157: There is nothing to do for task "{0}".

Cause: There is nothing to do for task "{0}".

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149158: No application files exist at "{0}".

Cause: No application files exist at "{0}".

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149159: There was an attempt to create a staging directory that is null.

Cause: There was an attempt to create a staging directory that is null.

Action: Ensure that the staging directory is properly configured. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149160: There was an attempt to create a staging directory for a null application name.

Cause: There was an attempt to create a staging directory for a null application name.

Action: Ensure that the application name is properly configured. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149161: This operation requires that a target be specified.

Cause: This operation requires that a target be specified.

Action: Ensure that the deployment request is complete and contains the required targeting information.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149162: This operation requires that a deployment plan be specified.

Cause: This operation requires that a deployment plan be specified.

Action: Ensure that the deployment request is complete and contains the required deployment plan information.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149163: The domain edit lock is owned by another session in non-exclusive mode. This deployment operation requires exclusive access to the edit lock and therefore cannot proceed. If using "Automatically Aquire Lock and Activate Changes" in the Administration Console, then the lock will expire shortly, so retry this operation.

Cause: The domain edit lock is owned by another session in non-exclusive mode. This deployment operation requires exclusive access to the edit lock and therefore cannot proceed.

Action: Ensure that the domain edit lock is available, and try again. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149164: The domain edit lock is owned by another session in exclusive mode. Therefore, this deployment operation cannot proceed.

Cause: The domain edit lock is owned by another session in exclusive mode. Therefore, this deployment operation cannot proceed.

Action: Ensure that the domain edit lock is available, and try again. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149165: Invalid target specified.

Cause: An invalid target was specified.

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149166: Deployments cannot be triggered through configuration updates and through the Deployment APIs simultaneously.

Cause: Deployments cannot be triggered through configuration updates and through the Deployment APIs simultaneously.

Action: Ensure that the domain edit lock is available, and try again. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149167: No action was needed to commit the request for "{0}" on "{1}".

Cause: No action was needed to commit the request for "{0}" on "{1}".

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149168: Request "{0}" has already been completed or was canceled.

Cause: The request "{0}" has already been completed or was canceled.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149169: Requires server restart for completion.

Cause: In order to complete the action, the server must be restarted.

Action: Restart the required servers.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149170: Invalid targeting was specified for this operation. Module and submodule targets cannot both be specified for this type of request.

Cause: The operation specified both module and submodule targeting, which is invalid for this operation.

Action: Perform the operation separately for both module and submodule targets.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149171: Deferred deployment task: {0}

Cause: A deployment operation was requested with targets that were unreachable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149172: Deployment request {0} is affecting the system resource {1}, which involves a non-dynamic property {2} in {3}. Therefore, a restart of the resource or the appropriate server targets is required for the changes to be active.

Cause: This is an informational message indicating that deployment involves a non-dynamic property.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149178: Application "{0}" is targeted to cluster "{1}", and the provided target for {3} operation is "{2}". This can potentially lead to client request problems on the cluster.

Cause: An operation was performed on a subset of a cluster for an application targeted to the cluster.

Action: Ensure that the cluster properly serves requests by performing operations on the cluster rather then on individual servers within the cluster.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149181: Deployment service encountered an error while aborting the edit session before start. Initiator for this edit session is "{0}". Error is "{1}".

Cause: See the reported error.

Action: Take appropriate action based on the reported error.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149182: An invalid alternate descriptor was specified for the redeploy operation. Alternate descriptors cannot be changed during a redeploy operation.

Cause: An invalid alternate descriptor was specified for the redeploy operation. Alternate descriptors cannot be changed during a redeploy operation.

Action: Repeat the redeploy operation without the alternate descriptor.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149183: An invalid retiretimeout option was specified for the deploy operation. The retiretimeout option was specified as "{2}" for the initial deployment of application "{0}". Retirement policies must be set during the deploy or redeploy of the next version in order to apply to version "{1}" of "{0}".

Cause: An invalid retiretimeout option was specified for the deploy operation.

Action: Specify the retiretimeout option during the deploy or redeploy of subsequent versions in order for the retirement to occur correctly at that time.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149184: The application "{0}" was autodeployed and may only be redeployed by touching the REDEPLOY file in the domain autodeploy directory for the respected application.

Cause: Autodeployed applications cannot be redeployed through tools.

Action: See the WebLogic Server documentation on autodeployed applications for more information.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149185: The application "{0}" was autodeployed and may only be deleted by removing the files from the domain autodeploy directory.

Cause: Autodeployed application cannot be undeployed through tools.

Action: See the WebLogic Server documentation on autodeployed applications for more information.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149186: The application "{0}" was autodeployed and cannot be redistributed.

Cause: Autodeployed application cannot be redistributed.

Action: See the WebLogic Server documentation on autodeployed applications for more information.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149187: An unexpected error occurred when specifying configuration information for the application "{0}" due to {1}.

Cause: Application configuration upgrade requires targeting information.

Action: Inspect the problematic application parts and deploy the application.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149188: No application named "{0}" exists for operation {1}. Operation cannot be performed until the server is restarted.

Cause: The application was created after non-dynamic changes were activated. The server needed to be restarted.

Action: Restart the server and then start the application. In the future, start the application before making non-dynamic changes to the configuration.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149189: An attempt was made to execute the "{0}" operation on an application named "{1}" that is not currently available. The application may have been created after non-dynamic configuration changes were activated. If so, the operation cannot be performed until the server is restarted so that the application will be available.

Cause: The application may have been created after non-dynamic changes were activated. The server needed to be restarted.

Action: Restart the server and then perform the operation on the application.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149190: Changes are pending from another session whose lock has expired. This deployment operation will not activate changes from another edit session and therefore cannot proceed. Either cancel the edit lock or activate the pending changes using the Administration Console or WLST.

Cause: Changes were made with an edit session that has now expired.

Action: Cancel the edit lock or activate the pending changes using the Administration Console or WebLogic Scripting Tool (WLST).
Level: 1

Type: WARNING

Impact: Deployer

BEA-149191: Operation "{0}" on application "{1}" is initializing on "{2}".

Cause: This is an informational message indicating deployment status change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149192: Operation "{0}" on application "{1}" is in progress on "{2}".

Cause: This is an informational message indicating deployment status change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149193: Operation "{0}" on application "{1}" has failed on "{2}".

Cause: This is an informational message indicating deployment status change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149194: Operation "{0}" on application "{1}" has succeeded on "{2}".

Cause: This is an informational message indicating deployment status change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149195: Operation "{0}" on application "{1}" has been deferred since "{2}" is unavailable.

Cause: This is an informational message indicating deployment status change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149196: Rejecting {1} request for application {0} because {2} request is running for the application.

Cause: A second operation for an application was requested when an operation for the application was runnning.

Action: Perform the operation again when the operation that is running is completed.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149197: Cannot perform operation {3} because application "{0}" is in state {1} and "{2}" is running.

Cause: The application is in the wrong state for the operation.

Action: Ensure that the application is in the correct state before attempting the operation.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149198: Cannot rename directory "{0}" to {1}.

Cause: The rename operation failed since the source directory is not present or there is a privilege issue.

Action: Check that the source directory is present and has the required permissions.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149199: Security permissions declared in the "{0}" deployment descriptor are not allowed due to the server's configuration.

Cause: The server is configured not to allow Java security permissions to be declared in the Weblogic deployment descriptors.

Action: Remove Java security permissions from the deployment descriptor before re-deployment.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149202: Encountered an exception while attempting to commit the {0} task for the application "{1}" on [partition-name: {2}].

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 or shared library "{0}" while the application is running (in state {1}). This operation is not permitted while the application is running or has pending updates.

Cause: The application or shared library was not stopped or had pending updates.

Action: Verify that the application or shared library is stopped or has no pending updates before attempting to distribute it. You may also consider redeploying 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}" on [partition-name: {2}]. Error is: "{3}"

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-149319: {0}: List of servers being worked upon are {1}.

Cause: {0}

Action: None
Level: 1

Type: NOTIFICATION

Impact: Management

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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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: WARNING

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

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

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

Impact: JMX

BEA-149512: JMX Connector Server started at {0}.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMX

BEA-149513: JMX Connector Server stopped at {0}.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: WARNING

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 WebLogic Server 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 WebLogic Server 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: WARNING

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 WebLogic Server 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-149526: Cannot access the attribute "{0}"{ from a partition "{{1}"{ on MBean "{{2}"{ because it is annotated with @ExcludeFromPartition or its interface is annotated with @ExcludeFromPartition.

Cause: An MBean or its attribute is annotated with @ExcludeFromPartition.

Action: Either do not access the attribute, or remove the @ExcludeFromPartition annotation from the MBean interface or attribute.
Level: 1

Type: ERROR

Impact: JMX

BEA-149527: Cannot access the operation "{{0}"{ from a partition "{{1}" on MBean "{2}" because it is annotated with @ExcludeFromPartition or the MBean interface is annotated with @ExcludeFromPartition.

Cause: An attempt was made to access an operation annotated with @ExcludeFromPartition.

Action: Either do not access the operation, or remove the @ExcludeFromPartition annotation from the operation or MBean interface.
Level: 1

Type: ERROR

Impact: JMX

BEA-149528: Cannot get the attribute "{0}" on MBean "{2}" from the partition "{1}". Either the attribute does not exist or the attribute is not visible to the partition.

Cause: The attribute does not exist or the attribute is not visible to the partition.

Action: If the attribute does not exist in the MBean, either change the MBean interface and its implementation to add the attribute or change to get other existing attributes. If the attribute exists but is not visible to the partition, annotate the attribute with @VisibleToPartitions ALWAYS.
Level: 1

Type: ERROR

Impact: JMX

BEA-149529: Cannot set the attribute "{0}" on MBean "{2}" from the partition "{1}". Either the MBean does not contain the attribute or the MBean attribute is not visible to the partition.

Cause: The attribute does not exist or the attribute is not visible to the partition.

Action: If the attribute does not exist in the MBean, either change the MBean interface and its implementation to add the attribute or change to set other existing attributes. If the attribute exists but is not visible to the partition, annotate the attribute with @VisibleToPartitions ALWAYS.
Level: 1

Type: ERROR

Impact: JMX

BEA-149530: Cannot invoke the operation "{0}" on MBean "{2}" from partition "{1}". Either the MBean does not contain the operation or the operation is not visible to the partition.

Cause: The MBean does not contain the operation or the operation is not visible to the partition.

Action: If the operation does not exist in the MBean, either change the MBean interface and its implementation to add the operation or invoke other existing operations. If the operation exists but is not visible to the partition, annotate the operation with @VisibleToPartitions ALWAYS.
Level: 1

Type: ERROR

Impact: JMX

BEA-149531: Cannot find the MBean "{0}" in partition "{1}".

Cause: The MBean is not visible to partitions.

Action: The MBean is not registered correctly or the MBean needs to be annotated with @VisibleToPartitions ALWAYS.
Level: 1

Type: ERROR

Impact: JMX

BEA-149532: The MBean "{0}" contains a different Partition key property value in the ObjectName: found "{1}", should be "{2}".

Cause: The MBean ObjectName is not correct.

Action: Provide an MBean ObjectName that is owned by the current partition.
Level: 1

Type: ERROR

Impact: JMX

BEA-149533: Cannot invoke the operation "{0}" on MBean "{2}" from partition "{1}" because one or more of the MBean operation parameters is not visible to partitions: {3}

Cause: The MBean passed in as an operation parameter is not visible to partitions.

Action: Annotate the MBean passed in as an operation paramter with @VisibleToPartitions ALWAYS.
Level: 1

Type: ERROR

Impact: JMX

BEA-149534: An exception occurred while calling queryNames for all mBeans from Managed Server: {0}.

Cause: The size of the result of call queryNames for all mBeans exceeds the configured Maximum Message Size for the Administration Server.

Action: Increase the Maximum Message Size configured for the Administration Server, or disable the indicated Managed Server notifications by using the property weblogic.management.disableManagedServerNotifications=true.
Level: 1

Type: ERROR

Impact: JMX

BEA-149535: JMX Resiliency Activity Server={0} : {1}

Cause: Refer to the embedded info fore more details.

Action: Refer to the embedded info for more details.
Level: 1

Type: WARNING

Impact: JMX

BEA-149601: The deployment framework was unable to resume accepting requests.

Cause: See the message detail.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149603: The deployment framework was unable to cleanly shut down.

Cause: See the message detail.

Action: Check for other log messages that give more information about the failure.
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-150044: The protection domain of class {1} does not have permission to inject a service from descriptor {0}. The protection domain is {2} and the permission is {3}.

Cause: A service does not have permission to inject a service that was found for it. The creation of the service will fail if no other appropriate service can be found to satisfy the injection point.

Action: Ensure that the protection domain of the class has rights to the specified permission.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150045: Edit session name {0} contains illegal character(s) and cannot be used. Choose a different name.

Cause: The specified edit session name does not meet the criteria for this component. It contains illegal character(s).

Action: Choose a different name.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150046: An edit session named {0} already exists. Choose a different name.

Cause: You attempted to create two edit sessions with the same name.

Action: Choose a different name.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150048: Cannot destroy default edit session.

Cause: You attempted to destroy the default edit session.

Action: Use a named edit session.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150049: 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: Configuration Management

BEA-150050: Cannot destroy DOMAIN partition.

Cause: You attempted to destroy DOMAIN partition. This is not a valid operation.

Action: Use a named edit session.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150051: Cannot remove edit session. This edit session belongs to a different partition.

Cause: Entities from other partitions cannot be operated on in an edit session for a given partition.

Action: Review the management request.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150052: Edit session {0} is locked by user {1} and cannot be deleted. Administrator permissions required.

Cause: The edit session is currently being edited.

Action: Review the management request or use force=true while logged in as an administrator.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150053: Edit session {0} is locked by user {1} and cannot be deleted. Use destroyEditSession("{0}", force = true) to override.

Cause: The edit session is currently being edited.

Action: Review management request or use force=true.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150054: Edit session {0} contains changes pending activation. Destroy edit session command has been aborted. Use destroyEditSession("{0}", force = true) to force the destroy operation.

Cause: The edit session contains changes that are pending activation.

Action: Review the management request or use force=true.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150055: Edit session {0} was created by user {1}. Administrator permissions required.

Cause: The caller is not the creator of the edit session.

Action: Review the management request or use force=true while logged in as an administrator.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150056: Edit session {0} was created by user {1}. Destroy edit session command has been aborted. Use destroyEditSession("{0}", force = true) to force the destroy operation.

Cause: The caller is not the creator of the edit session.

Action: Review the management request or use force=true.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150057: A failure has occurred during service lookup, bind or unbind from descriptor {0} using permission {1} with: {2}

Cause: The operation being performed does not have permission to lookup, bind or unbind the service descriptor.

Action: Carefully read the returned error to determine what action is required.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-159900: USER {0} CREATED {1}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159901: USER {0} CREATE {1} FAILED {2}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159902: USER {0} REMOVED {1}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159903: USER {0} REMOVE {1} FAILED {2}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159904: USER {0} MODIFIED {1} ATTRIBUTE {2} FROM {3} TO {4}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159905: USER {0} MODIFY {1} ATTRIBUTE {2} FROM {3} TO {4} FAILED {5}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159907: USER {0} INVOKED ON {1} METHOD {2} PARAMS {3}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159908: USER {0} INVOKED ON {1} METHOD {2} PARAMS {3} FAILED {4}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159909: USER {0}, configuration auditing is enabled.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159910: USER {0}, configuration auditing is disabled.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159911: Invalid number {0} was found while encrypting clear text passwords.

Cause: See the message body.

Action: No action is required.
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: This is an information message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160041: Undeployed MailSession named {0}.

Cause: This is an information message.

Action: No action is required.
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: See the message detail.

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: This is an information message.

Action: No action is required.
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.
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: See the message detail.

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: See the message detail.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160214: Output location exists {0}

Cause: The file pointed to by the output location already exists,

Action: No action is required.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160215: ERROR: The moduleUri, "{0}", is not Web module.

Cause: The moduleUri is not valid Web module.

Action: Ensure that the specified moduleUri is a valid Web module and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160216: Unexpected errors occurred while sending deployment event {1} on behalf of application ''{0}''.

Cause: The deployment event listener(s) registered to receive deployment event caused unexpected exceptions when processing deployment event {1} on behalf of application ''{0}''.

Action: Report this problem to My Oracle Support.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160217: Unexpected errors occurred while sending a vetoable deployment event on behalf of application ''{0}''.

Cause: The deployment event listener(s) registered to receive vetoable deployment events caused unexpected exception(s) when processing deployment event {1} on behalf of application ''{0}''.

Action: Report this problem to My Oracle Support.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160218: Filtering classloader configuration ignored for module {1} of application {0}

Cause: Filtering classloader configuration is only supported in descriptors at the main level of the deployment (for example, in enterprise applications or standalone Web applications). Such configuration is not supported in modules of an enterprise application.

Action: Remove the filtering classloader configuration from the deployment descriptor of module {1} of application {0}.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160219: The JPA persistence unit {0} will use the following configured default persistence provider: {1}

Cause: No provider element was specified in the associated persistence.xml file.

Action: No action is required unless you want a different JPA provider to be used for the given persistence unit, in which case you can specify the provider in the persistence.xml file or change the default provider for the domain.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160220: Compilation completed successfully.

Cause: The compilation task has completed successfully.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160221: env-entry for type java.lang.Character had length = 0.

Cause: See the error message body.

Action: See the error message body.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160222: Could not create a new JMS ConnectionFactory for the application: {0}.

Cause: See the error message body.

Action: See the error message body.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160223: The resource-env-ref ''{0}'' declared in the standard descriptor or annotation has no JNDI name mapped to it. The resource-env-ref must be mapped to a JNDI name using the resource-env-description element of the weblogic proprietary descriptor or corresponding annotation.

Cause: See the error message body.

Action: See the error message body.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160224: Encountered an error cleaning up references for application: ${0} - ${1}

Cause: See the error message body.

Action: See the error message body.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160225: A new JPA API method is being invoked against an older version of the persistence provider, in which the method is not supported yet. Update the application to use a compliant provider, or ensure that the application does not attempt to invoke unsupported methods that are not supported by the current provider.

Cause: A new JPA API method is being invoked against an older version of the persistence provider, in which the method is not supported yet.

Action: Update the application to use a compliant provider, or ensure that the application does not attempt to invoke unsupported methods that are not supported by the current provider.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160226: Ignoring the configuration file [{0}: {1}]. Only applications that use Kodo as the JPA provider can be configured with this file.

Cause: This file can configure only persistence units that use Kodo.

Action: Remove the configuration file or specify the information in persistence.xml; otherwise, one or more persistence units in this application use Kodo.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160227: The persistence unit "{0}" in "{1}" does not use Kodo as a JPA provider. Ignoring the configuration for this persistence unit found in persistence-configuration.xml.

Cause: The persistence-configuration.xml file cannot configure persistence units that do not use Kodo.

Action: Remove the persistence unit from the persistence-configuration.xml file or specify in persistence.xml, or otherwise, that the persistence unit uses Kodo.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160228: AppMerge failed to merge your application. If you are running AppMerge on the command-line, merge again with the -verbose option for more details. See the error message(s) below.

Cause: AppMerge can fail for many reasons. See the specific error message for details.

Action: Use the provided error message to track down and fix the problem.
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.
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.
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.
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.
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: Multiple entries have the same environment entry name, but have different values.

Action: Ensure that each environment entry has a different environment name, or that entries with the same have 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 for details.

Action: See the error message for details.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160241: Error: There are validation errors for environment entries in module {0}. {1}

Cause: There are validation errors in the environment entries. With an EJB in WAR files, it is possible that names for environment entries 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. An environment entry that is declared in the application.xml descriptor must specify a JNDI name in the java:app or java:global namespace.

Action: Correct the validation errors.
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: The EJB component may have overwritten data source definitions in its interceptors. In this case, data source definitions in interceptors will be ignored.

Action: Please verify the cause above is not an issue for the application.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160243: A creating StoredProcedureQuery API method is being invoked on a container-managed and transaction-scoped EntityManager outside of a transaction, but the method is not supported yet. Update the application to start a transaction before creating the StoredProcedureQuery objects.

Cause: A creating StoredProcedureQuery API method is being invoked on a container-managed and transaction-scoped EntityManager outside of a transaction, but the method is not supported yet.

Action: Update the application to start a transaction before creating the StoredProcedureQuery objects.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160244: An environment entry {0} declared in the application.xml descriptor does not specify a JNDI name in the java:app or java:global namespace.

Cause: An environment entry declared in the application.xml descriptor must specify a JNDI name in the java:app or java:global namespace.

Action: Specify a JNDI name in the java:app or java:global namespace.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160245: It is an error for both the env-entry-value and lookup-name elements to be specified for a given env-entry element {0}.

Cause: An environment entry declared in the application.xml descriptor specified both the env-entry-value and lookup-name elements.

Action: Specify either the env-entry-value or lookup-name, but not both.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160246: Warning: It is an error to request injection of two resources into the same target class {0} and target name {1}.

Cause: Injection of two resources into the same target was requested.

Action: Remove one of the targets from the application.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160247: Warning: Ignore the realm name: {0} in deployment descriptor.

Cause: The realm name was ingored in the deployment descriptor.

Action: No action is required.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160248: Unable to parse class file: {0}. {1}

Cause: This is generally due to a corrupted class file in the application.

Action: Use an external tool such as JAD to ascertain the validity of the class. It is important to fix any invalid class in order to avoid potentially severe errors later in deployment or at runtime.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160249: Skipping schema-generation actions for persistence unit {0} by overriding relevant properties because this is only a server startup instead of an application deployment.

Cause: This is an information message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160250: No ComponentMBeanFactory with the class name {0} was found among the registered DeploymentFactory instances. Creating an instance using reflection.

Cause: There was no registered DeploymentFactory instance that had the same name as {0}.

Action: No action is required.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160251: Failed to create an instance of ComponentMBeanFactory with the class name {0} because of an exception {1}

Cause: The ComponentMBeanFactory instance could not be located among registered DeploymentFactory instances.

Action: No action is required.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160252: The following application inconsistencies must be corrected {0}. Code path: {1}

Cause: WebLogic Server detected multiple declarations of the same env-entry.

Action: Search the application, including any shared library, for the listed env-entry declarations in both the descriptors and code annotations. Make sure that all the declarations are consistent. It is better to declare each env-entry only once to avoid this issue.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160253: {0}

Cause: See the message ddetails.

Action: Consider eliminating redundant declarations of entries to avoid potential conflicts.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160254: Unable to read from application cache file {0} because of exception {2} with message: {1}

Cause: The cause of this exception is an underlying Java exception.

Action: No action is needed, since WebLogic can recover from this failure by constructing these objects again.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160255: Unable to write to application cache file {0} because of exception message: {1}

Cause: The cause of this exception is an underlying Java IOException.

Action: No action is needed, since WebLogic can recover from this failure by constructing these objects again when it need to read from this location.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160256: Unable to close {1} object stream to application cache file {0} because of exception message: {2}

Cause: The cause of this exception is an underlying Java IOException.

Action: No action is needed, since WebLogic can recover from this failure.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160257: Application with name "{0}" cannot be deployed because the name is already in use in {1} named "{2}".

Cause: The deployment failed due to another application or library that already exists with the same name in the current deployment scope.

Action: Retry the deployment with a different application name.
Level: 1

Type: ERROR

Impact: J2EE

BEA-169800: A PooledConnectionFactory object with an invalid external version of {0} was found.

Cause: The version of WebLogic Server that stored the PooledConnectionFactory object is not compatible with the version that is retrieving it.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169801: The JMS method {0} may not be called inside an EJB or servlet.

Cause: The application code has violated the Java EE 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 Java EE 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 exception 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: NOTIFICATION

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 Java EE 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: A JMS session pool was either created directly by the user or by internal container code that did not properly specify a property.

Action: Check for other log messages that give more information about the failure.
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-169825: Cannot create a wrapped JMSContext using a username and password when the res-auth element is set to Container.

Cause: The application code is not using the Java EE APIs properly.

Action: Either remove the username and password, or set the res-auth element to Application.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169826: The JMSContext 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 JMSContext pool.

Action: Either change the JNDI name of the JMSContext pool property or change the JNDI name of the object that is currently bound into JNDI.
Level: 1

Type: WARNING

Impact: JMSPool

BEA-169827: The resource reference "{0}" of type JMS Connection Factory in application "{1}" does not specify a JNDI name. As of Java EE 7 and WebLogic version 12.2.1, such references return a "java:comp/DefaultJMSConnectionFactory" by default when no Connection Factory with a JNDI name that matches the resource name is found.

Cause: See the error message from the JMS provider.

Action: If the application intends to use a specific JMS Connection Factory, Oracle recommends (a) checking for a misspelling of the resource reference name either in the @Resource annotation or, if there is a deployment descriptor file, in the <resource-ref-name> of the deployment descriptor, and (b) if there is no misspelling, explicitly setting the desired JNDI name using a lookup or mappedName attribute in the descriptor or annotation.
Level: 1

Type: NOTIFICATION

Impact: JMSPool

BEA-169828: An invalid value ({0}) for session mode was specified.

Cause: An invalid value of the sessionMode parameter was specified when creating a JMSContext. The only valid values are JMSContext.AUTO_ACKNOWLEDGE, JMSContext.CLIENT_ACKNOWLEDGE, JMSContext.DUPS_OK_ACKNOWLEDGE and JMSContext.SESSION_TRANSACTED

Action: Change the code so that it passes in a valid session mode. See the JMS API for more information.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169829: JMS 2.0 method "{0}", called on the interface "{1}", is not implemented by this JMS Provider.

Cause: JMS 2.0 method "{0}", called on the interface "{1}", is not implemented by this JMS Provider.

Action: Either use a JMS 1.1 method instead or use a JMS provider that supports JMS 2.0.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169830: JMS Connection Factory unmapped resource reference mode : {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMSPool

BEA-169831: System property weblogic.jms.JMSConnectionFactoryUnmappedResRefMode has 2 legal values "{0}" and "{1}". The value "{2}" is invalid and will be ignored.

Cause: There are two legal values for the weblogic.jms.JMSConnectionFactoryUnmappedResRefMode property.

Action: No action is required.
Level: 1

Type: WARNING

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-170026: The servlet context logger could not be initialized for servlet context {0} to write to its own log file.

Cause: There was an I/O error when opening the file for the servlet context log.

Action: Ensure that the logging configuration for the web application is valid.
Level: 1

Type: ERROR

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 Server Logging bridge has initialized successfully.

Cause: This message is logged for informational purpose only.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170032: The Server has detected ODL configuration for java.util.logging. The PlatformLoggerLevels attribute configuration on the LogMBean will be ignored.

Cause: This message is logged for informational purpose only.

Action: Users should specify the java.util.logging Logger Level configuration with ODL.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170033: The Server logging bridge could not be registered.

Cause: See the stack trace for the exact cause of this error, it could be due to misconfiguration or incorrect CLASSPATH being set for the logging APIs.

Action: Take appropriate action based on the error message.
Level: 1

Type: ERROR

Impact: Log Management

BEA-170034: LogMonitoring Service counted {0} log messages in the last {1} seconds. This exceeds the throttle threshold value of {2}, certain repetitive messages will now be throttled.

Cause: This message is logged for informational purpose only.

Action: No action is needed.
Level: 1

Type: WARNING

Impact: Log Management

BEA-170035: LogMonitoring Service counted {0} log messages in the last {1} seconds which is below the threshold value of {2}. Log messages are not being throttled.

Cause: This message is logged for informational purpose only.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170036: The Logging monitoring service timer has started to check for logged message counts every {0} seconds.

Cause: This message is logged for informational purpose only.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170037: The log monitoring service timer has been stopped.

Cause: This message is logged for informational purpose only.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170038: The log monitoring service is throttling messages with the following Message ID/LoggerName/Message signature and the total count of logged messages over the throttle period is: {0}

Cause: This message is logged for informational purpose only.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170039: The log monitoring service encountered an error when it was trying to reopen the server log file.

Cause: The cause of the error is included in the error stack trace of the message.

Action: Please take corrective action based on the error stack trace reported in the log message to resolve the issue.
Level: 1

Type: ERROR

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: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: WTC

BEA-180003: Naming exception error: {0}

Cause: The specified name could not be resolved.

Action: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: WTC

BEA-180006: Naming exception error: {0}

Cause: The specified name could not be resolved.

Action: Check for other log messages that give more information about the failure.
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: See the message detail.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: WTC

BEA-180054: Failure occurred while reading the received domain security token: {0}.

Cause: See the message detail.

Action: Check for other log messages that give more information about the failure.
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.

Action: Try to force garbage collection, and remove some services to reduce memory usage.
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.

Action: Try to force garbage collection, and remove some services to reduce memory usage.
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: See the message detail.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: WTC

BEA-180089: Error occurred while decoding {0} message.

Cause: See the message detail.

Action: Check for other log messages that give more information about the failure.
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 Java EE Connector Service.

Cause: The Java EE Connectoor Services is currently initializing.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190001: Java EE Connector Service initialized successfully.

Cause: The Java EE Connector Service has initialized successfully.

Action: No action required.
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 occurred 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 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: No ConnectionRequestInfo was provided for Application Managed Security Context.

Action: No action required.
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: The component with the indicated JNDI name has the indicated managed security type.

Action: No action required.
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: The indicated resource adapter is currently being tested for viability connection proxies.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190082: Proxy test passed. WebLogic Server will use connection proxies for resource adapter "{0}".

Cause: The proxy test passed for the incidated resource adapter.

Action: No action required.
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: See the message detail.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Connector

BEA-190103: Failed to register the Diagnostic Image for the Connector Service.

Cause: See the message detail.

Action: Check for other log messages that give more information about the failure.
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: See the message detail.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Connector

BEA-190106: Failed to find the RuntimeMBean for the module: {0}

Cause: See the message detail.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Connector

BEA-190107: Failed to unregister the RuntimeMBean for the module: {0}

Cause: See the message detail.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Connector

BEA-190108: Failed to initialize the Jndi Subcontexts for the adapter: appId = {0}, {1}

Cause: See the message detail.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Connector

BEA-190109: Extracting file {0} to {1}.

Cause: The indicated file is being extracted to the indicated native Lib directory.

Action: No action required.
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: See the message detail.

Action: Check for other log messages that give more information about the failure.
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: See the message detail.

Action: Check for other log messages that give more information about the failure.
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 stack trace for details about the cause of this error.

Action: Take appropriate action based on the information in the stack trace.
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: The outbound adapter with the indicated JNDI name is using the indicated sharing scope.

Action: No action required.
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: An internal consistency check failed, assertion failed: {0}

Cause: An internal consistency check failed, indicating a software defect.

Action: Check for other log messages that give more information about the failure.
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: No compliance or validation errors were found in the indicated resource adapter.

Action: No action required.
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: This message is logged to incidate the number of errors and warnings that were found for the indicated resource adapter.

Action: No action required.
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: The indicated connection pool was reset.

Action: No action required.
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: See the message body.

Action: No action required.
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: No old version adapter instance is currently deployed.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199180: This application EAR is not deployed in a side-by-side versioning style.

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199181: Waiting for complete callback from Side-by-side versioning adapter {0}.

Cause: See the message body.

Action: No action required.
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: The indicated resource adapter is safe to undeploy.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199183: HintsContext: Ignore unknown hint name [{0}] and its value [{1}].

Cause: An unknown hint was used.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: WARNING

Impact: Connector

BEA-199184: ManagedConnectionFactory of connection pool [{0}] implements javax.resource.spi.TransactionSupport interface. Will use runtime TransactionSupport value [{2}] and igore the value [{1}] configured in DD or annotation.

Cause: A new feature was used, see Section 7.13 of the Connector 1.6 specification.

Action: No action is required if this behavior is expected.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199185: There is no META-INF/validation.xml file in the adapter archive {0}. The default Bean Validation configuration will be used.

Cause: No META-INF/validation.xml file was found in the RAR archive.

Action: No action is required if this behavior is expected.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199186: Found META-INF/validation.xml in adapter archive {0}.

Cause: A META-INF/validation.xml file was found in the RAR archive.

Action: No action is required if this behavior is expected.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199187: Found {2} constraint violation error(s) for {0} on instance [{1}]: {3}

Cause: Bean Validation failed and got constraint violation errors.

Action: Check the adapter configuration.
Level: 1

Type: WARNING

Impact: Connector

BEA-199188: Bean validation failed when validating for {0} on bean instance [{1}]. Exception: {2}

Cause: Bean validation failed.

Action: Check the adapter configuration and exception details.
Level: 1

Type: WARNING

Impact: Connector

BEA-199189: A long-running work submission has been rejected because the count of current active long-running work requests has reached the MaxConcurrentLongRunningRequests limit {0}.

Cause: A long-running work submission was rejected because the count of current active long-running work requests has reached the MaxConcurrentLongRunningRequests limit {0}.

Action: Check the adapter configuration and increase MaxConcurrentLongRunningRequests if necessary.
Level: 1

Type: WARNING

Impact: Connector

BEA-199190: The max-concurrent-long-running-requests limit was changed from {0} to {1}.

Cause: The configuration was changed or initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199191: Warning: Caller application {2} defines a shareable resource reference {1} to outbound connection pool {0}, but the pool does not support share by its design either because its transaction support level is NOTransaction or the ManagedConnectionFactory class has the @Unshareable annotation. Will treat as unshareable.

Cause: An invalid resource reference definition was made to an unshareable ConnectionFactory.

Action: Change the SharingScope of the resource reference definition to Unshareable.
Level: 1

Type: WARNING

Impact: Connector

BEA-199192: Warning: Caller application {2} defines a resource reference {1} to outbound connection pool {0} without defining SharingScope explicitly. The pool does not support share by its design either because its transaction support level is NOTransaction or the ManagedConnectionFactory class has the @Unshareable annotation. Will treat as unshareable.

Cause: An invalid resource reference definition was made to an unshareable ConnectionFactory.

Action: Change the SharingScope of the resource reference definition to Unshareable.
Level: 1

Type: WARNING

Impact: Connector

BEA-199193: ManagedConnection {0} of connectionInfo {1} in Connection Pool {2} has been destroyed already. Previous destroy stacktrace: {3} New destroy stacktrace: {4}

Cause: The ManagedConnection was destroyed again.

Action: Check the server log.
Level: 1

Type: WARNING

Impact: Connector

BEA-199194: Resource adapter generated unexpected exception during work event notification for event {0}. Ignored. Exception: {1}

Cause: The resource adapter generated an unexpected exception during work event notification.

Action: Check the work event processing codes of the resource adapter.
Level: 1

Type: WARNING

Impact: Connector

BEA-199195: Connector annotation scan: Ignored unexpected error [{2}] when processing annotations on {0} while {1}.

Cause: Check the error message and stacktrace to determine the cause.

Action: Check error message and stacktrace to determine the appropriate action to take.
Level: 1

Type: WARNING

Impact: Connector

BEA-199196: Ignore @javax.resource.Connector annotation on class {0} since ResourceAdapter Bean {1} is already specifed in ra.xml.

Cause: ra.xml already specifies the ResourceAdapter bean to use.

Action: No action is required if this behavior is expected.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199197: An exception occurred when removing admin object {0}. Exception is: {1}

Cause: This exception occurs as the result of an attempt to unbind the admin object from JNDI.

Action: Examine the log for the exact exception. Report the error to My Oracle Support.
Level: 1

Type: WARNING

Impact: Connector

BEA-199198: An exception occurred when invoking preDestroy on {0}: {1}. Exception is: {1}

Cause: This exception occurs as the result of the CDI container calling the preDestroy method.

Action: Examine the log for the exact exception. You may need to report the error the resource adapter vendor.
Level: 1

Type: WARNING

Impact: Connector

BEA-199199: The work was rejected because it has expired before WorkManager executed it.

Cause: The time value for the startTimeout argument is too short. The WorkManager cannot start the work within the specified time period.

Action: Increase the time value for the startTimeout argument and ensure that it is big enough for WarkManager to start the work.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199200: Annotation scan/process of the resource adapter {0} resulted in the following {1} warnings: {2}

Cause: The specified resource adapter failed to pass the annotation scan/process as indicated by the listed warnings.

Action: Check warning messages and fix the annotations that are involved.
Level: 1

Type: WARNING

Impact: Connector

BEA-199201: Failed to merge resource adapter {0} when processing annotations due to {1} error(s) found.

Cause: Failed to merge resource adapter {0} when processing annotations due to {1} error(s) found.

Action: Check the errors and fix them.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199202: Ignored unexpected exception [{1}] when unregistering runtime mbean {0}.

Cause: Check error message and stack trace to figure out the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: WARNING

Impact: Connector

BEA-199211: Compliance checking and validation of the resource adapter {0} resulted in the following non-critical errors: {1}

Cause: The specified resource adapter failed to pass compliance and validity checking as indicated by the listed warnings and errors.

Action: Correct the ra.xml or weblogic-ra.xml files, or check the resource adapter archive.
Level: 1

Type: WARNING

Impact: Connector

BEA-199212: Failed to create connection pool [{0}] due to error: {1}

Cause: Check the reported error message and stack trace to determine the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: ERROR

Impact: Connector

BEA-199213: A new error occurred when trying to destroy a connection pool [{0}] that was previously in a failed state : the following new error will be ignored: {1}

Cause: Check the error message and stack trace to determine the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: WARNING

Impact: Connector

BEA-199214: The connection pool [{0}] was in a HEALTH_CRITICL state already, therefore this method call is not allowed.

Cause: Check the error message and stack trace to determine the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199215: The connection pool [{0}] will move to a HEALTH_CRITICAL state because the adapter is not in deploy-as-a-whole mode. This pool failed due to errors: {1}

Cause: Check the error message and stack trace to determine the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: WARNING

Impact: Connector

BEA-199216: An error occurred when performing action {2} on connection pool [{0}]. The following error will be ignored: {1}

Cause: Check the error message and stack trace to determine the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: WARNING

Impact: Connector

BEA-199217: Connection pool [{0}] has validation errors and cannot be reset. Try to fix all validation errors and then do a dynamic update or redeploy this adapter.

Cause: Check the error message and stack trace to determine the cause.

Action: Try to fix all validation errors and then do a dynamic update or redeploy this adapter.
Level: 1

Type: WARNING

Impact: Connector

BEA-199218: Unable to determine whether properties were changed for Connection pool [{0}]. If there are changed properties, they may be ignored during a dynamic update: {1}

Cause: Check the error message and stack trace to determine the cause.

Action: Try to fix all validation errors and then do a dynamic update or redeploy this adapter.
Level: 1

Type: WARNING

Impact: Connector

BEA-199219: Invalid shrink threshold value {0} specified for the system property weblogic.connector.cmm.shrinkThreshold. Value must be between 0 and 10 (inclusive).

Cause: The value of the system property weblogic.connector.cmm.shrinkThreshold is invalid.

Action: Check the value of the system property weblogic.connector.cmm.shrinkThreshold. Ensure that it is between 0 and 10 (inclusive). A value of 0 indicates that the connector will not take any action on any memory pressure level.
Level: 1

Type: ERROR

Impact: Connector

BEA-199220: Failed to parse the string for UniversalResourceKey: {0}.

Cause: The UniversalResourceKey string representation is incorrect.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: ERROR

Impact: Connector

BEA-199221: Failed to parse the defining application information for UniversalResourceKey: {0}.

Cause: The UniversalResourceKey string representation is incorrect.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: ERROR

Impact: Connector

BEA-199222: The UniversalResourceKey is defined by application information: {1}#{2}#{3}, but its JNDI name {0} has the wrong name space.

Cause: An application-defined resource has an invalid JNDI name.

Action: Check the name field of @ConnectionFactoryDefinition/@AdministeredObjectDefinition or the equivalent deployment descriptor element. Ensure that it has a valid JNDI name space.
Level: 1

Type: ERROR

Impact: Connector

BEA-199223: The name space of a JNDI name {0} does not match its application information: {1}#{2}#{3}

Cause: An application-defined resource has an invalid JNDI name.

Action: Check the name field of @ConnectionFactoryDefinition/@AdministeredObjectDefinition or the equivalent deployment descriptor element. Ensure that it has a valid JNDI name space.
Level: 1

Type: ERROR

Impact: Connector

BEA-199224: JNDI name {0} has prefix of 'java:', but has no defining application information.

Cause: An invalid JNDI name was specified for a resource.

Action: Check the jndi-name field of the resource and ensure that it has a valid JNDI name.
Level: 1

Type: ERROR

Impact: Connector

BEA-199300: Cannot find Connection Definition via interfaceName:{0} from Resource Adapter:{1}. The application information: {2}#{3}#{4} The JNDI name:{5}

Cause: The interfaceName field may be filled incorrectly for the ConnectionFactoryDefinition annotiation or the equivalent deployment descriptor.

Action: Use the correct interfaceName for the ConnectionFactoryDefinition annotation or the equivalent deployment descriptor.
Level: 1

Type: ERROR

Impact: Connector

BEA-199301: Cannot find AdminObject definition in Resource Adapter {0} with className: {1} and interfaceName: {2} The application information: {3}#{4}#{5} The JNDI name:{6}

Cause: Either the className field or the interfaceName field contains an incorrect value.

Action: Fill the className or interfaceName field or both with the correct value.
Level: 1

Type: ERROR

Impact: Connector

BEA-199302: Cannot determine the AdminObject interface from class:{0} from Resource Adapter:{1} The application information: {2}#{3}#{4} The JNDI name:{5}

Cause: 1. The interfaceName field has no entry. 2. An incorrect className field was used for AdminObject.

Action: 1. Fill the interfaceName field with a valid value. 2. Fill the className field with the correct value.
Level: 1

Type: ERROR

Impact: Connector

BEA-199303: The connector resource {4} is defined in application: {1}#{2}#{3}. The corresponding resource adapter {0} is not globally accessible and is not in the same application with {1}.

Cause: The resource adapter's deployment descriptor is not accessible from the component that defines the connector resource.

Action: 1. Use another resource adapter for the connector resource. 2. Update the resource adapter's deployment descriptor, and ensure that it is accessible from the component that defines the connector resource.
Level: 1

Type: ERROR

Impact: Connector

BEA-199304: Failed to export object of class:{0} from Resource Adapter:{1} The application information: {2}#{3}#{4} The JNDI name:{5}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199305: Duplicated resource definition for Resource Adapter:{0} The application information: {1}#{2}#{3} The JNDI name:{4}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199306: At least one application-defined resource is found for Resource Adapter:{0} The application information: {1}#{2}#{3} The JNDI name:{4}

Cause: The resource adapter cannot be undeployed when an application-defined resource exists.

Action: Undeploy the application first.
Level: 1

Type: ERROR

Impact: Connector

BEA-199307: Failed to unexport object: {0} which JNDI name is {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-199308: Failed to find PartitionRuntimeMBean for the partition {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-199309: Unable to register runtime MBean for connector: {0}.

Cause: The runtime MBean cannot be registered. 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-199310: Failed to lookup JNDI name: {3}. This resource is defined in application: {0}#{1}#{2}.

Cause: The corresponding resource adapter may not be activated.

Action: Check the status of the corresponding resource adapter and activate it or take other appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199311: Failed to find Resource Adapter:{0} The application information: {1}#{2}#{3} The JNDI name:{4}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199312: At least one of the permissions declared in permissions.xml is not allowed.

Cause: Check the permissions.xml configuration for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199313: Application classloader is used for loading resource adaptor {1}'s classes in application {0}.

Cause: <enable-ee-compliant-classloading-for-embedded-adapters> is set to true.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199314: Resource adaptor's classloader is used for loading resource adaptor {1}'s classes in application {0}. This classloader is the child classloader of the application classloader.

Cause: <enable-ee-compliant-classloading-for-embedded-adapters> is set to false.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199315: The <classloader-structure> configuration in application {0}'s weblogic-application.xml is ignored by resource adapter {1} because resource adapter {1}'s <enable-global-access-to-classes> is set to true.

Cause: <enable-global-access-to-classes> is set to true.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Connector

BEA-199316: Failed to destroy 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-199317: Failed to create admin object [{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-199318: It is not supported to access connector resource outside server {0} which defines the resource, current server is {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-199319: It is not supported to access resource adapter outside partition {0} which defines the resource, current partition is {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-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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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-200048: {1} destination "{2}" of bridge "{0}" has a configured adapter JNDI name "{3}", so it will find the internal automatically deployed adapter with JNDI name "{4}". The bridge will ignore an explicitly configured and deployed adapter with adapter JNDI name "{3}". The deployed adapter will be ignored, the bridge does not need to deploy a separate adapter.

Cause: This is due to a configuration upgrade.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200049: {1} destination "{2}" of bridge "{0}" uses a custom adapter JNDI name "{3}" instead of the expected names of eis.jms.WLSConnectionFactoryJNDIXA or eis.jms.WLSConnectionFactoryJNDINOXA.

Cause: The bridge destination uses a configured adapter JNDI name.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200050: The bridge has a configured adapter JNDI name "{1}", so it will find the internal automatically deployed adapter with JNDI name "{2}". The bridge will ignore an explicitly configured and deployed adapter "{0}". The deployed adapter will be ignored.

Cause: The bridge destination uses a configured adapter.

Action: No action is required.
Level: 1

Type: WARNING

Impact: MessagingBridge

BEA-210000: {0}

Cause: See the message body.

Action: Correct the error.
Level: 1

Type: ERROR

Impact: COM

BEA-210001: {0}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: COM

BEA-210003: No network channel is available to handle COM requests.

Cause: The server is not configured with at least one non-SSL port.

Action: Configure a plain text listener port if COM is enabled.
Level: 1

Type: ERROR

Impact: COM

BEA-213500: Partition {0} has ResourceDeploymentPlanPath set to {1} but the zip file from which it is being imported does not have an entry for it.

Cause: While importing the paritition, an attempt was made to import a partition without proper configuration. The element resource-deployment-plan-path points to a plan which is to be used for overwriting resource attributes. As part of exporting a partition, this plan should have been archived as part of the overall partition archive created, but the exported archive is missing the plan.

Action: Export the partition once again and verify that the exported archive ZIP file contains the file referred to by <resource-deployment-plan-path > in config.xml before importing the partition.
Level: 1

Type: ERROR

Impact: Partition Portability

BEA-213501: Could not find partition by name {0} to export in the current domain.

Cause: The partition name that was provided for export does not exist in the domain.

Action: Check the name of the partition and then run exportPartition again.
Level: 1

Type: ERROR

Impact: Partition Portability

BEA-213502: A ResourceGroupTemplate with name {0} already exists.

Cause: This error occurs if importPartition is called with the createNew parameter set to null, and the partition being imported references a ResourceGroupTemplate that has the same name as one of the ResourceGroupTemplates in the domain.

Action: If you want to use the existing ResourceGroupTemplate, run importPartition again with createNew set to false. If you want to clone the ResourceGroupTemplate with a new name, run importPartition again with createNew set to true.
Level: 1

Type: ERROR

Impact: Partition Portability

BEA-213503: Could not delete temporary pending file {0}.

Cause: During import, if the option createNew is set to false, then it is imperative that the files corresponding to the ResourceGroupTemplate copied into the pending directory as part of import be deleted before activate is called.

Action: Delete the file {0} and run importPartition again.
Level: 1

Type: ERROR

Impact: Partition Portability

BEA-213504: The destination for writing imported app {0} already exists at {1}.

Cause: While importing a partition with the application binaries/plan, the destination for writing the binary/plan file in an imported domain file system already has a file with the same name.

Action: Delete the file in the domain at {1} and run importPartition again.
Level: 1

Type: ERROR

Impact: Partition Portability

BEA-213505: Application {0} with staging mode set to {1} does not exist at the specified sourcepath {2}.

Cause: The imported partition references an application that is neither in the exported ZIP file nor at the specified location as specified by the source-path attribute of the app-deployment bean.

Action: Check that source-path is correct and run importPartition again after placing the application binary at the specified source-path.
Level: 1

Type: ERROR

Impact: Partition Portability

BEA-213506: The application {0} has the stagingMode set to {1} but the exported ZIP file does not have application binaries to import.

Cause: The imported partition references an application that is in {1} staged mode. The exported ZIP file does not, however, contain the application binary.

Action: Either change the staging mode in the attributes.json file to external_stage/nostage or export again with the application binaries included.
Level: 1

Type: ERROR

Impact: Partition Portability

BEA-213507: attributes.json has a reference attribute {0} with its value set to {1}, but this attribute was not found in the imported domain's configuration.

Cause: A wrong attributes value was specified in the attributes.json file during importPartition.

Action: Look at config.xml before importing and use the proper attribute values for updating attributes.json before importing the partition.
Level: 1

Type: ERROR

Impact: Partition Portability

BEA-213508: The name of the object {0} in partition-config.xml is {1} whereas {2} has the name changed to something else. Therefore it could not be found. Changing names of attributes in {2} is not supported.

Cause: The name of an attribute was changed in {2}.

Action: Revert the name change in {2} and importPartition again.
Level: 1

Type: ERROR

Impact: Partition Portability

BEA-213509: Partition {0} is in an unknown state because of a non-dynamic change that was made which affects {1}. The server must be rebooted in order for the partition to become stable and export Partition to work.

Cause: The partition being exported is in an unknown state. A common cause of this is that a non-dynamic configuration change was made to the domain that has deferred the initialization of the partition until the Administration Server is restarted.

Action: Restart the Administration Server.
Level: 1

Type: ERROR

Impact: Partition Portability

BEA-213510: {0} for partition {1} failed.

Cause: TBD

Action: Look at the stack trace and fix appropriate error.
Level: 1

Type: ERROR

Impact: Partition Portability

BEA-213511: {0} for partition {1} succeeded.

Cause: TBD

Action: TBD
Level: 1

Type: NOTIFICATION

Impact: Partition Portability

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: See the message body.

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: See the message body.

Action: Check for other log messages that give more information about the failure.
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: See the message detail.

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

Cause: See the message detail.

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-260143: "{0}" and "{1}" cannot both be specified.

Cause: The combination of the two parameters is inconsistent.

Action: Use only one of the parameters.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260144: The specified partition "{0}" does not exist in the domain.

Cause: A partition needs to exist in the domain before deploying to it.

Action: Create the specified partition before deploying to it.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260145: The specified resource group "{0}" does not exist in the specified partition "{1}".

Cause: A resource group needs to exist before deploying to it.

Action: Create the specified resource group before deploying to it.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260146: The specified resource group template "{0}" does not exist in the domain.

Cause: A resource group template needs to exist before deploying to it.

Action: Create the specified resource group template before deploying to it.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260147: The resource group name cannot be derived in this case. Specify the resource group option along with the partition option.

Cause: A resource group option need to be specified with the partition option for the cases where it cannot be derived.

Action: Specify the resource group option with partition option.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260148: A resource group template option cannot be specified with a resource group option.

Cause: Cannot specify a resource group template option and a resource group option together.

Action: Either specify a resource group template option or specify a resource group option.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260149: The specified resource group "{0}" does not exist in the domain.

Cause: A resource group needs to exist before deploying to it.

Action: Create the specified resource group before deploying to it.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260150: A partition administrator cannot perform deployment operations to a resource group template.

Cause: A partition administrator cannot operate on a resource group template.

Action: Operate on the resource group template as a system administrator.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260151: Partition administrator from partition {0} cannot perform deployment operations to partition {1}.

Cause: A partition administrator is trying to operate someone else' partition.

Action: A partition administrator should only operate on their own partition.
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 store record is longer than the maximum length of {0} bytes.

Cause: This was caused by a programming error.

Action: Either change the code or increase the size of the record.
Level: 1

Type: ERROR

Impact: Store

BEA-280019: There was an error while writing to a storage.

Cause: See the detail message for the cause.

Action: Ensure that the hardware and operating system are functioning properly and that there is enough space available for the storage area.
Level: 1

Type: ERROR

Impact: Store

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

Cause: See the detail message for the cause.

Action: Ensure that the hardware and operating system are functioning properly and that all the storage spaces are available online.
Level: 1

Type: ERROR

Impact: Store

BEA-280021: There was an error while opening the file store file "{0}".

Cause: Either the specified file does not exist, the server does not have permissions to open the file, or there is a hardware or operating system problem.

Action: Ensure that the file exists and that the directory name was specified correctly.
Level: 1

Type: ERROR

Impact: Store

BEA-280024: There was an error while creating a new file named "{0}" for the file store.

Cause: See the detail message. The disk may be full, or there may be a hardware or operating system problem.

Action: Ensure that there is enough disk space and that the hardware and operating system are working properly.
Level: 1

Type: ERROR

Impact: Store

BEA-280026: The primary or cache file "{0}" is not both readable and writeable.

Cause: The file permissions are incorrect, or the server is running under the wrong user ID.

Action: Fix the file permissions or run the server under the correct user ID.
Level: 1

Type: ERROR

Impact: Store

BEA-280029: The store record {0} could not be found.

Cause: This is caused by a programming error.

Action: Ensure that the correct record ID was specified.
Level: 1

Type: ERROR

Impact: Store

BEA-280031: The store named "{0}" has not yet been opened.

Cause: This is a programming error.

Action: Fix the code and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280032: The store suffered a fatal error and it must be reopened.

Cause: A fatal error occurred previously.

Action: Restart the server.
Level: 1

Type: ERROR

Impact: Store

BEA-280035: Unable to access the store directory "{0}".

Cause: See the detail message.

Action: Check that the specified path name is correct, that it exists, and that the directory is readable and writeable by the server's user ID.
Level: 1

Type: ERROR

Impact: Store

BEA-280036: Missing the file store file "{0}" in the directory "{1}".

Cause: The file has been accidentially deleted or moved, or the wrong directory name was specified, or the server process does not have permissions to read and write the file.

Action: Ensure that the directory name is correct and that the server process has permissions to read and write the files. If necessary, create an empty file with the same name.
Level: 1

Type: ERROR

Impact: Store

BEA-280037: The file store has reached the maximum number of {0} files and no more files can be created.

Cause: There are too many records in the store.

Action: Delete data from the store and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280038: An error occurred while flushing the contents of a file store file.

Cause: See the detail message.

Action: See the detail message.
Level: 1

Type: ERROR

Impact: Store

BEA-280039: The store handle {0} is not valid.

Cause: This is caused by a programming error.

Action: Fix the code and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280040: An invalid record was found in the store: Code={0}.

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

Action: For File store, Change the DirectIOMode or restore from backup if the problem persists.
Level: 1

Type: ERROR

Impact: Store

BEA-280041: A record was found in the store with an invalid version of {0}

Cause: The store may have been used with an incompatible version of WebLogic Server.

Action: Restore from backup.
Level: 1

Type: ERROR

Impact: Store

BEA-280042: The file store primary or cache file "{0}" cannot be opened because it is actually a directory.

Cause: A directory was accidentially created in the file store's own main or cache directory, or the specified path is incorrect.

Action: Check that the file store path is correct.
Level: 1

Type: ERROR

Impact: Store

BEA-280044: The file store directory "{0}" does not exist.

Cause: The directory has not yet been created, or its filesystem is not available.

Action: Check that the directory path has been correctly specified, and create the directory if necessary.
Level: 1

Type: ERROR

Impact: Store

BEA-280045: The file store primary or cache directory "{0}" is not a directory.

Cause: The directory has not yet been created, or its filesystem is not available.

Action: Check that the directory path has been correctly specified, remove any file or directory that already exists in its place, and create the directory if necessary.
Level: 1

Type: ERROR

Impact: Store

BEA-280046: The directory "{0}" is not both readable and writeable.

Cause: The file permissions are incorrect, or the server is running under the wrong user ID.

Action: Fix the file permissions or run the server under the correct user ID.
Level: 1

Type: ERROR

Impact: Store

BEA-280051: The store was not able to create a new record.

Cause: See the message detail.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Store

BEA-280052: The store was not able to read a record.

Cause: See the message detail.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Store

BEA-280055: Invalid name for store write policy: "{0}".

Cause: See the message detail.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Store

BEA-280056: A store error occurred: {0}

Cause: See the description of the underlying exception.

Action: See the description of the underlying exception
Level: 1

Type: ERROR

Impact: Store

BEA-280057: The store named "{0}" is already open.

Cause: This is a programming error.

Action: Fix the code and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280059: "{0}" is not a valid store connection name.

Cause: This is a programming error.

Action: Fix the code and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280060: The store "{0}" encountered a fatal error, and it must be shut down: {1}

Cause: There was a serious I/O error, either with file I/O, replicated store IO or the JDBC connection to the database.

Action: Restart the server.
Level: 1

Type: INTERNAL_ERROR

Impact: Store

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

Cause: See he detail message.

Action: See the detail message.
Level: 1

Type: ERROR

Impact: Store

BEA-280062: The store "{0}" could not be shut down: {1}

Cause: See the detail message.

Action: See the detail message.
Level: 1

Type: WARNING

Impact: Store

BEA-280063: The "{0}" field value "{1}" in table reference "{2}" (format [[[catalog.]schema.]table) is too long. The database supports a maximum length of "{3}" for this field.

Cause: This is a configuration error.

Action: When configuring a table name, choose a shorter name for the indicated field. Note that JDBC stores automatically append "WLStore" to the table name.
Level: 1

Type: ERROR

Impact: Store

BEA-280064: {0} (server="{1}" store="{2}" table="{3}")

Cause: See the exception text, and 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 store "{0}" encountered an unresolvable failure while processing transaction "{1}". Shut down and restart to resolve this transaction. {2}

Cause: There was a serious I/O error, either with file I/O, replicated I/O or the JDBC connection to the database, or an unexpected exception occurred while processing a transaction.

Action: Restart the server.
Level: 1

Type: ERROR

Impact: Store

BEA-280075: JDBC store "{0}" failed to retain ownership of database table "{1}", either due to database access problems or due to concurrent accessors of the table. See the linked exception for more information.

Cause: Some other WebLogic server process or JDBC store has taken over ownership of the database table, or some database access error prevented this JDBC store from renewing ownership of the database table.

Action: The error message has information to identify potential owners in conflict.
Level: 1

Type: ERROR

Impact: Store

BEA-280076: Database table "{1}" for store "{0}" is currently owned by "{2}". Trying to wait for ownership.

Cause: Some other WebLogic Server process or JDBC store has ownership of the database table.

Action: The warning message has information to identify the current owner of the database table. If the current owner does not yield ownership within some time, this server will not be able to open the JDBC store and will log an error.
Level: 1

Type: WARNING

Impact: Store

BEA-280077: JDBC store "{0}" in this server is not the owner of database table "{1}". Unexpected current owner is "{2}", expected current owner is "{3}".

Cause: Some other WebLogic Server process or JDBC store has ownership of the database table.

Action: The error message has information to identify and resolve the owners in conflict.
Level: 1

Type: ERROR

Impact: Store

BEA-280078: The handle that was passed was created from a different store connection.

Cause: This is a programming error.

Action: Ensure that the correct connection was used.
Level: 1

Type: ERROR

Impact: Store

BEA-280079: An instance of the mSA PersistentStore

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280080: Number of create requests issued by this store.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280081: Number of read requests issued by this store.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280082: Number of update requests issued by this store

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280083: Number of delete requests issued by this store

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280084: Number of objects contained in the store

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280085: Number of times the store flushed its data to durable storage

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280086: An instance of an mSA PersistentStoreConnection

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280087: Number of create requests issued by this store connection

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280088: Number of read requests issued by this store connection

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280089: Number of update requests issued by this store connection

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280090: Number of delete requests issued by this store connection

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280091: Number of objects contained in the store connection

Cause: See the message body.

Action: No action is required.
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: See the message body.

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: See the message body.

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: See the message body.

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: See the message body.

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 store "{2}". The direct IO mode "{1}" specified by the property "{0}" is invalid and will be ignored. Using the default value "{3}"

Cause: See the message body.

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: See the message body.

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 "{2}" for the persistent store file "{1}" could not be verified, or the cache file is missing. Ignore this Warning if this is the first time the store has ever booted. Possible causes include: first boot of store (potentially after using a write policy different from Direct-Write-With-Cache), store migration, unclean shutdown, off-line store compression, and manual removal of cache files.

Cause: The cache file is missing, or the signature stored in the cache file does not match the signature of the primary file.

Action: Make sure that the configuration is correct, do not delete cache files, and ensure a clean shutdown.
Level: 1

Type: WARNING

Impact: Store

BEA-280103: The persistent file store "{0}" will cache in {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280104: The persistent file store "{0}" will use buffered writes instead of direct IO because the configured block size "{2}" is not a multiple of the environment's direct IO alignment "{1}". When there are high request loads, this may reduce file store performance. The store is still operating in a transactionally safe synchronous mode.

Cause: Direct I/O requires the block size to be a multiple of directIO granularity.

Action: Reconfigure the store with a block size that is a multiple of the direct I/O alignment for your environment. If the store is not empty and contains useful data, use the store admin compact utility to change block size, otherwise make sure that all storage areas are removed before starting WebLogic Server again.
Level: 1

Type: WARNING

Impact: Store

BEA-280105: The persistent file store "{0}" cannot open file {1}.

Cause: An IOException occurred.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Store

BEA-280106: The persistent file store "{0}" cannot memory-map the locked file "{1}" and has to downgrade to explicit buffered IO. For example, in some NFS environments memory-mapping and locking are not compatible. Consider configuring a local cache directory.

Cause: See the message body.

Action: Consult your storage vendor and operating system documentation.
Level: 1

Type: ERROR

Impact: Store

BEA-280107: The store record {0}, connection "{1}", in the store named "{2}" does not exist because it has been deleted.

Cause: This was caused by a programming error.

Action: Ensure that the correct record ID was specified.
Level: 1

Type: ERROR

Impact: Store

BEA-280108: The store record {0}, connection "{1}" already exists in the store named "{2}".

Cause: This was caused by a programming error.

Action: Ensure that the correct record ID was specified.
Level: 1

Type: ERROR

Impact: Store

BEA-280109: The JVM was unable to load the native wlfileio library for the store "{0}". File and paging stores will continue to function correctly. Specifically, file stores that are configured with a transactionally safe synchronous write policy will continue to operate safely and transactionally but may open with a different write-policy. Other store types may not be able to open.

Cause: See message body.

Action: See file store open log messages for the requested and final file store write policies. See the documentation for file store synchronous write policy configuration.
Level: 1

Type: WARNING

Impact: Store

BEA-280110: The "{1}" attribute of Store "{0}" has been changed from "{2}" to "{3}".

Cause: This is due to a configuration change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280111: The "{1}" attribute of Store "{0}" has been changed from "{2}" to "{3}".

Cause: This is due to a configuration change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280112: [StoreBootOnError] "{0}" Ignoring AssertionError on bootHandle: record type: {1}, handle:{2}, row: {3}

Cause: There is some corruption of the JDBC store.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Store

BEA-280113: The JDBC store "{0}" is initially pointing to RAC instance "{1}".

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280114: The JDBC store "{0}" is configured with worker count as "{1}" but only started "{2}" workers as it is not able to acquire enough JDBC connections for the configured worker count.

Cause: The JDBC store was not able to acquire enough JDBC connections for the configured worker count.

Action: Modify the data source configuration.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280115: Replicated store "{0}": the daemon is approaching its shared memory limit and the store itself has used up to "{1}%" of its shared memory.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280116: Replicated store "{0}": the daemon is approaching its shared memory limit and the store itself has used up to "{1}%" of its shared memory. It will reject new JMS persistent messages.

Cause: See the message body.

Action: Check if there are things that need to be cleaned up, for example abandoned durable subscriptions. Consider restart the daemon with a bigger limit.
Level: 1

Type: WARNING

Impact: Store

BEA-280117: Replicated store "{0}" the daemon has used up to "{1}%" of its shared memory limit.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280118: Replicated store "{0}": the daemon has used up to "{1}%" of its shared memory limit. It may take actions, including rejecting new JMS persistent messages or failing on creating any new stores or opening any recovered stores.

Cause: The amount of shared memory used by the replicated store daemon has met or exceeded the configured warning threshold.

Action: Check if there are things that need to be cleaned up, for example abandoned durable subscriptions. Consider restart the daemon with a bigger limit.
Level: 1

Type: WARNING

Impact: Store

BEA-280119: Replicated store "{0}": the daemon used up to "{1}%" of its shared memory limit. It will fail on creating new stores or opening any recovered store.

Cause: The amount of shared memory used by the replicated store daemon has met or exceeded the configured error threshold.

Action: Check if there are things that need to be cleaned up, for example abandoned durable subscriptions. Consider restart the daemon with a bigger limit.
Level: 1

Type: ERROR

Impact: Store

BEA-280120: Opening the Replicated store "{0}(Region Name={1})" for recovery: directory={2} driver="{3}".

Cause: Informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280121: The Replicated store "{0}(Region Name={1})" ({2}) has been opened: blockSize={3} records={4}.

Cause: Informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280122: Missing the region "{1}" from this replicated store(name="{0}").

Cause: The region has been accidentially deleted or moved, or the wrong name was specified, or the server process does not have permissions to read and write to the region.

Action: Ensure that the replicated Store name is correct and that the server process has permissions to read and write to the regions in replicated store. If necessary, create an empty region with the same name.
Level: 1

Type: ERROR

Impact: Store

BEA-280123: The replicated store has reached the maximum number of {0} regions and no more region can be created.

Cause: There are too many records in the store.

Action: Delete data from the store and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280124: An error occurred while flushing the contents of a replicated store region.

Cause: See the detail message.

Action: See the detail message.
Level: 1

Type: ERROR

Impact: Store

BEA-280125: The replicated store "{0}(Region Name={1})" could not be opened because it contained a region with an invalid version {2}. A region of version {3} was expected.

Cause: The replicated store has not been properly upgraded from a previous version of WebLogic Server, or the region has been corrupted on the memory store.

Action: Ensure that the file store was upgraded using the weblogic.Upgrade tool.
Level: 1

Type: ERROR

Impact: Store

BEA-280126: Opening existing replicated store "{1}(Region Name={2})". The block size value specified by the property {0} is ignored because the block size of preexisting regions cannot change.

Cause: See the message body.

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-280127: The replicated store "{0}" cannot open region {1}.

Cause: An IOException occurred.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Store

BEA-280128: The store can't be initialized.

Cause: See the message body.

Action: Please check that the cryptographic services of the execution environment and the host operating system are properly configured and operating correctly.
Level: 1

Type: ERROR

Impact: Store

BEA-280129: JDBC store "{0}" will be opened with connection caching policy "{1}" and will keep {2,choice,1#1 database connection|2#{2} database connections} open.

Cause: Informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280130: The configuration property "{2}" with value "{3}" on JDBC store "{0}" is incompatible with connection policy "{1}".

Cause: Conflicting configuration options.

Action: Either the connection caching policy must be changed or the property value must be changed.
Level: 1

Type: ERROR

Impact: Store

BEA-280131: The use of piggy-back commit is incompatible connection policy "{1}" and has been disabled for JDBC store "{0}".

Cause: Conflicting configuration options.

Action: Either the connection caching policy must be changed or the property value must be changed.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280132: JDBC store "{0}" will be opened with connection caching policy "{1}" and will get one connection from its data source as needed.

Cause: Informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280133: The version record is missing from the table "{1}" for the JDBC store "{0}". Make sure that only Weblogic processes are accessing and modifying the table.

Cause: The version record is missing from the non-empty table backing the JDBC store.

Action: Contact My Oracle Support regarding restoring the version record in the JDBC store.
Level: 1

Type: ERROR

Impact: Store

BEA-280134: The version record is missing from the table "{1}" for the JDBC store "{0}" and will be restored.

Cause: Informational message.

Action: No action is required.
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.

Action: Check the agent's configuration.
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.

Action: Check the agent's configuration.
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.

Action: Check the agent's configuration.
Level: 1

Type: ERROR

Impact: SAFService

BEA-281025: SAFAgent "{0}" has been paused for incoming messages.

Cause: An Incoming Message Pause request was issued for the specified SAFAgent.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281026: SAFAgent "{0}" has been resumed for new incoming messages.

Cause: An Incoming Message Resume request was issued for the specified SAFAgent.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281027: SAFAgent "{0}" has been paused for forwarding

Cause: A Forwarding Pause request was issued for the specified SAFAgent.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281028: SAFAgent "{0}" has been resumed for forwarding.

Cause: A Forwarding Resume request was issued for the specified SAFAgent.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281029: RemoteEndpoint "{0}" has been paused for new incoming messages.

Cause: An Incoming Pause Request was issued for the specified remote endpoint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281030: RemoteEndpoint "{0}" has been resumed for new incoming messages.

Cause: An Incoming Resume Request was issued for the specified remote endpoint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281031: RemoteEndpoint "{0}" has been paused for forwarding.

Cause: A Forwarding Pause Request was issued for the specified remote endpoint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281032: RemoteEndpoint "{0}" has been resumed for forwarding.

Cause: A Forwarding Resume request was issued for the specified remote endpoint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-282000: Unsupported class version {0}. Expected a value between {1} and {2} inclusive.

Cause: While attempting to interoperate between different releases or service packs, an error occurred while attempting to serialize or deserialize an object. The version number of the object was not in the expected range. If {0} is larger than {2}, then it is possible an attempt was made to access a newer version than the current version. Otherwise, a possible attempt has been made to interoperate with an unsupported older version.

Action: Ensure that the versions of Oracle products that are interoperating are supported. If the versions need to be supported, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282001: The messaging kernel {0} is beginning recovery of its persistent state.

Cause: This is normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Messaging

BEA-282002: The messaging kernel {0} has recovered {1} persistent messages.

Cause: This is normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Messaging

BEA-282003: The messaging kernel {0} will use up to {1} bytes of memory before paging begins.

Cause: This is normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Messaging

BEA-282004: Message redirection has failed in a non-recoverable way for the messaging kernel {0}. Restart the server in order to restart message redirection.

Cause: See the previous error messages, which should explain the cause.

Action: Restart the WebLogic Server.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282005: An error occurred while redirecting a message for the messaging kernel {0}: {1}.

Cause: See the attached detail message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282006: An error occurred while deleting an expired message for the messaging kernel {0}: {1}.

Cause: See the attached detail message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282007: An error occurred in the transaction prepare phase of a message send operation for the messaging kernel {0}.

Cause: See the attached stack trace.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282008: A message send transaction for the messaging kernel {0} could not be committed because the kernel has been shut down.

Cause: A server was shut down or a destination was removed while a transaction was in progress.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282009: A message receive transaction for the messaging kernel {0} could not be committed because the kernel has been shut down.

Cause: A server was shut down or a destination was removed while a transaction was in progress.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282010: A sequence number update transaction for the messaging kernel {0} could not be committed because the kernel has been shut down.

Cause: A server was shut down or a destination was removed while a transaction was in progress.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282011: There was an error making a message visible after a delivery delay: {0}.

Cause: Most likely, a transient I/O error occurred.

Action: Consider restarting the server if the error persists. The message will not be lost.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282012: There was a failure while performing paging I/O.

Cause: Either a transient I/O error occurred, or the server did not have enough memory to complete the paging I/O request.

Action: Consider restarting the server if the error persists.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282013: Skipping unexpected null message encountered on store boot, {0}.

Cause: Message data corruption has occurred. The corrupted message will be skipped to allow data recovery on other non-corrupted messages.

Action: Report this issue to My Oracle Support.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282014: [StoreBootOnError] "{0}" Ignoring 2PC record for sequence={1}, queue={2}, type={3}, id={4}, xid={5}; message reference element cannot be found.

Cause: Potential message data corruption has occurred. A 2PC record was found in the store without an associated message reference element. The 2PC record will be ignored.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282015: "{0}" An error occurred while writing a message to store: info={1}; null message body detected.

Cause: An error was detected while attempting to write a message to the persistent store.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Messaging

BEA-283002: Path Service has been started on server {0} with jndiName {1} with store {2}

Cause: See the message body.

Action: No action required.
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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 WebLogic Server 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 admin server failed in {0} phase. This server needs to be restarted to enable it to synchronize with the domain configuration.

Cause: The server configuration is out of date with the domain configuration and an attempt to synchronize with the admin server failed in {0} phase. This server needs to be restarted to enable it to synchronize with the domain configuration.

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 WebLogic Server 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 WebLogic Server 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 WebLogic Server error. No action is required.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290071: Deployment service servlet failed when parsing the request or uploading the file.

Cause: The request is not an RFC 1867-compliant multipart/form-data stream.

Action: The request should comply with RFC 1867. Verify that the Administration Server and Managed Servers are running versions that interoperate.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290073: Deployment service servlet received a request of type "{0}" with an invalid application name: "{1}".

Cause: An invalid deployment service servlet request was made.

Action: Correct the application name and retry the request.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290074: Deployment service servlet received file download request for file "{0}". The file may exist, but download of this file is not allowed.

Cause: The file to download is a security file or is outside of the domain root directory.

Action: Enter a valid file name for download.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290075: Target Server encountered an error in sending "{0}" of id "{1}" with "{2}".

Cause: The deployment message cannot be delivered to the Administration Server.

Action: This is an internal WebLogic Server error. No action is required.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290079: Deployment service servlet received a request of type "{0}" with an invalid upload path: "{1}".

Cause: An invalid deployment service servlet request was made.

Action: Correct the upload path and retry the request.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290080: Deployment service servlet received a request of type "{0}" with no upload path.

Cause: An invalid deployment service servlet request was made.

Action: This is an internal WebLogic Server error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290081: Deployment service servlet received a request of type "{0}" with an invalid partition name: "{1}".

Cause: An invalid deployment service servlet request was made.

Action: Correct the partition name and retry the request.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290082: Deployment service servlet received a request of type "{0}" unable to overwrite existing file: "{1}".

Cause: An invalid deployment service servlet request was made.

Action: Remove existing user file and retry the request.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290083: Deployment service servlet received a request of type "{0}" file already exists: "{1}".

Cause: An invalid deployment service servlet request was made.

Action: Remove existing user file or set overwrite flag and retry the request.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-300037: The NodeManager at host {0} and port {1} seems to be down. Start the NodeManager and rerun the command.

Cause: The NodeManager is not running.

Action: Start the NodeManager and rerun the command.
Level: 1

Type: WARNING

Impact: NodeManager

BEA-300040: An I/O error occurred while writing a NodeManager status change message.

Cause: Possible causes are that the standard output stream has been closed or the NodeManager stopped monitoring.

Action: If this server requires monitoring, restart the server.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300043: NodeManager native library not found - server process ID not saved.

Cause: The NodeManager native library is not in the library search path or is unavailable on this platform.

Action: Ensure that the NodeManager native library is available and in the library search path.
Level: 1

Type: WARNING

Impact: NodeManager

BEA-300044: An I/O error occurred while writing the server PID file: "{0}".

Cause: The server PID file might be write-protected.

Action: Ensure that the server PID file is not write-protected. In addition, check to see if the parent directory exists (should have been created by the NodeManager server before starting the server).
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300048: Unable to start the server {0} : {1}

Cause: The most likely cause is a configuration error in the Shell/SSH/RSH NodeManager configuration.

Action: Ensure that you can access the remote NodeManager. This may require setting up SSH permissions for the SSH-based NodeManager. In addition, ensure that the default PATH settings for the remote NodeManager are correct. See the NodeManager documentation for more information.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300049: An I/O error occurred while writing the server URL file: "{0}".

Cause: The server URL file might be write-protected.

Action: Ensure that the server URL file is not write-protected. In addition, check to see if the parent directory exists (it should have been created by the NodeManager server before starting the server).
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300051: An I/O error occurred while updating the startup properties for "{0}". This probably occurred because the NodeManager is unreachable. This could mean that the servers boot.properties or startup.properties file is out of date, and the next time NodeManager attempts to automatically restart the server on a failure, it will use out of date properties. To resolve this issue, either ensure that the NodeManager is able to receive the updates and reset the properties, or restart the server.

Cause: An I/O error occurred while updating the startup properties for "{0}". This probably occured because the NodeManager is unreachable.

Action: Either ensure that the NodeManager is able to receive the updates and reset the properties, or restart the server.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300053: A migratable server was not found to contain any specified IP address in the ServerMBean or custom network channels for migration. No IPs will be passed to NodeManager and no IPs will be migrated. The server may not start without an available address, or may not be accessible throughout migration without a consistent IP. Configure an appropriate floating listen address for the server.

Cause: A migratable server was not found to contain any specified IP address in the ServerMBean or custom network channels for migration. No IPs will be passed to NodeManager and no IPs will be migrated. The server may not start without an available address, or may not be accessible throughout migration without a consistent IP.

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

Type: ERROR

Impact: NodeManager

BEA-300054: Could not find appropriate IP for ListenAddress "{0}" specified for a migratable server. Reason: "{1}". The NodeManager may not be able to bind the specified address and the server may not start without the available address. Configure an appropriate floating listen address for the server.

Cause: No appropriate IP was found for a migratable server's listen address. The NodeManager may not be able to bind the 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-300055: The NodeManagerMonitor add requires a non-null MachineMBean to monitor the active status of a NodeManager.

Cause: See the message body.

Action: Provide a non-null MachineMBean.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300056: Could not execute the native output file rotation logic due to "{0}".

Cause: Could not execute the native output file rotation logic due to "{0}".

Action: Could not execute the native output file rotation logic due to "{0}".
Level: 1

Type: ERROR

Impact: NodeManager

BEA-310001: Subsystem {0} in partition {1} 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. 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} in partition {1} has failed. Setting server state to FAILED. Reason: {2}

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} in partition {1} has failed because of: {2} 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} in partition {1} has failed. Reason: {2}

Cause: One of the non-critical subsystems of the server has failed.

Action: Check the server log to determine the cause of the subsystem failure.
Level: 1

Type: INTERNAL_ERROR

Impact: Health

BEA-320000: The Diagnostics subsystem is initializing on Server {0}.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320001: The ServerDebug service initialized successfully.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320002: The Diagnostics subsystem is stopping on Server {0}.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320004: The following unexpected exception was thrown: {0}

Cause: An exception was thrown unexpectedly.

Action: Take appropriate action based on the unexpected exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320005: Diagnostic monitor of unknown type {1} used in instrumentation scope {0}.

Cause: The Diagnostic Monitor library is probably out of date.

Action: Update the Diagnostic Monitor library.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320008: Error occurred while collecting diagnostic metrics:

Cause: An error occurred while constructing a Harvester instance.

Action: Ensure that all harvester configuration parameters are set appropriately.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320009: The elapsed time of the last snapshot of diagnostic metrics exceeded the configured sample period by the following number of milliseconds: {0}.

Cause: Harvested MBeans and/or DataSources are taking too long to return sampled attribute values.

Action: Increase the sample period window.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320010: An error occurred while generating a diagnostic image: {0}

Cause: Permissions were abruptly changed on the zip/directory. The file system does not have sufficient disk space to continue writing the image.

Action: Allocate sufficient disk space and provide the proper permissions to create the image zip file.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320011: The following diagnostic image destination directory could not be created: {0}

Cause: You have not given write permissions to the absolute path for the default directory, or you have not allocated sufficient disk space for the directory to be created.

Action: You must give write permissions to the absolute path for the default directory if no configured destination directory is specified. You must also allocate sufficient disk space for the default directory to be created if no destination directory is specified.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320012: The following destination directory for diagnostic images could not be read or written to: {0} or there is not enough free space available to create the diagnostic image.

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

Action: Create the destination directory with the appropriate read and write permissions.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320013: Diagnostic image capture was attempted during a lockout period.

Cause: The ImageManager has locked image captures for a specified number of minutes.

Action: The lockout period must expire before a new image capture request is accepted.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320014: Lockout of {0} above allowed maximum lockout minutes for image captures.

Cause: The specified a number of minutes exceeds the maximum allowed lockout minutes.

Action: Specify a lockout period between the minimum and maximum.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320015: Lockout of {0} below allowed minimum lockout minutes for image captures.

Cause: The specified a number of minutes falls below the minimum allowed lockout minutes.

Action: Specify a lockout period between the minimum and maximum.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320016: Creating diagnostic image in {0} with a lockout minute period of {1}.

Cause: A FirstFailure has occurred, a diagnostic image notification handler was configured, or a capture image method was explicitly invoked on ImageManager.

Action: No action is required. The diagnostic image capture request will be scheduled and executed.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320018: Instrumentation engine configuration {0} could not be parsed due to: {1}

Cause: The instrumentation engine configuration is possibly malformed.

Action: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320022: An error was encountered while creating SerialVersionUID for class {0}.

Cause: SerialVersionUID for a class could not be created.

Action: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320035: Instrumentation configuration {0} could not be read.

Cause: The instrumentation configuration is missing or invalid.

Action: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320039: Invalid class inclusion pattern(s) for instrumentation engine/scope {0}. Disabling instrumentation in scope {0}.

Cause: Inclusion patterns are malformed.

Action: Specify inclusion patterns in the correct format.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320040: Invalid class exclusion pattern(s) for instrumentation engine/scope {0}. Disabling instrumentation in scope {0}.

Cause: One or more exclusion patterns are malformed.

Action: Specify exclusion patterns in the correct format.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320041: Invalid lockout minutes {0} specified in image notification. Image capture was not performed.

Cause: The value is invalid.

Action: Recreate the notification with a valid lockout minutes value.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320042: Invalid diagnostic image location {0} specified in notification, exception message is {1}. Image capture was not performed.

Cause: The value is not a valid directory or file name.

Action: Recreate the notification with a valid image location. Take appropriate action based on the exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320043: Image notification was not performed because the image capture was attempted before the lockout time expired. The exception message is {0}

Cause: An image capture was attempted before the lockout period expired.

Action: Recreate the image notification with a smaller value for lockout minutes. Optionally, use the watch alarm feature to ensure that the notification does not occur again before the lockout period has expired.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320044: Error occurred while performing a watch notification:

Cause: An error occurred while performing the operations required for the notification.

Action: Take appropriate action based on the unexpected exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320047: Mail notification has not been sent due to an error that occurred while creating or sending a mail message:

Cause: An error occurred while performing the mail operations required for the notification.

Action: Verify the MailSession properties and email destination. Take appropriate action based on the Messaging exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320048: JMS notification message has not been sent due to an error that occurred while creating a JMS map message:

Cause: An error occurred while performing the JMS operation.

Action: Verify the JMS queue and connection factory configuration settings in the JMS notification. Take appropriate action based on the JMS exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320049: An exception occurred sending JMS notification message. Reinitializing JMS objects and retrying.

Cause: An error occurred while sending the JMS message.

Action: Look for additional error messages in the log from the reinitialization or resend of the message.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320052: An error occurred while initializing a SMTP notification:

Cause: The mail session is incorrectly configured or not available.

Action: Ensure that the mail session JNDI name is correct. Ensure that the mail session MBean properties are valid. Take appropriate action based on the exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320053: The SNMP Agent is not configured. The trap for the SNMP Watch notification cannot be sent.

Cause: The SNMP Agent is not enabled.

Action: Enable the SNMP Agent using the console.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320054: An error occurred while sending an SNMP notification:

Cause: An exception occurred in the SNMP Agent when sending the SNMP trap to the configured trap destinations.

Action: Ensure that the trap destinations are configured correctly. Take appropriate action based on the exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320055: Could not read or create index on log file {0}.

Cause: The drive may be full or the directory is not writable.

Action: Check whether the drive is full or the directory is not writable.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320056: Log index file {0} has an invalid magic number.

Cause: The index file is corrupt or invalid.

Action: Delete the corrupt index file.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320057: Log index file {0} contents are inconsistent with its header.

Cause: The index file is corrupt or truncated.

Action: Delete the index file.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320058: Could not parse log record: {0}

Cause: The log record is malformed.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320063: An attempt to add watch {0} failed because the watch has already been defined.

Cause: Two different watch definitions have the same name.

Action: Remove one of the watch entries that has the same name.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320064: Watch {0} could not be created due to the following unexpected exception: {1}

Cause: An exception occurred unexpectedly.

Action: Take appropriate action based on the unexpected exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320066: An attempt to add notification {0} failed because the notification has already been defined.

Cause: Two different notification definitions have the same name.

Action: Remove one of the notification entries with the same name.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320068: Watch "{0}" in module "{1}" with severity "{2}" on server "{3}" has triggered at {4}. Notification details: {5}

Cause: A configured watch has evaluated to true and has triggered.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320069: Watch {0} contains an invalid notification {1} that is not defined.

Cause: The notification does not exist.

Action: Define the notification or remove the notification from the watch.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320070: Error occurred while performing notification {1} for watch {0}. Notification may not have completed.

Cause: An exception occurred while performing the notification.

Action: Validate the definition for the specified watch and notification. Take appropriate action based on the error message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320071: Error occurred while creating watch notification {0}. Notifications may not have completed for this watch.

Cause: An exception occurred while creating the watch notification.

Action: Validate the definition for the specified watch and notification. Take appropriate action based on the error message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320073: Error while locating a record for timestamp {0} in the archive

Cause: There is a misconfigured or missing data archive for harvested data.

Action: Check that the harvested data archive exists.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320074: Error while executing query.

Cause: A runtime error occurred while executing a query.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320075: Error while reading a record from the archive

Cause: The harvested data archive may be corrupt.

Action: Reconfigure the harvested data archive.
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.

Action: Reconfigure the harvested data archive.
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.
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: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
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: In most cases, you should be able 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.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320134: An 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: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
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: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320155: Inconsistent instrumentation handling information was specified in the same pointcut definition for {0} : {1} : {2}.

Cause: The instrumentation configuration contains a pointcut definition that specifies conflicting information for the method.

Action: Review the pointcuts that specify the method listed in the error, and verify that there are not multiple definitions for the methods with which they conflict. For example, one indicating an argument is not-sensitive while another indicates it is.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320156: The renderer class {0} could not be loaded due to {1}, the following renderer will be used instead: {2}.

Cause: The instrumentation configuration specified a renderer class that either was not found, is not accessible, or is not a renderer.

Action: Verify that the renderer class is correctly specified in the instrumentation configuration and that it is available to the server classloader.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320157: An error occurred when registering the log4j for data gathering operations.

Cause: The log4j libraries may not be in the CLASSPATH.

Action: Ensure that the log4j libraries are available when using Log watch rules with Log4j enabled.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320158: An error was detected while capturing the flight recorder image.

Cause: The specified exception provides details on the error that was encountered.

Action: Review the provided exception information to determine the cause and action to take.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320159: An error was detected while initializing the flight recording.

Cause: The specified exception provides details on the error that was encountered.

Action: Review the provided exception information to determine the cause and action to take.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320160: The type-based renderer class {0} for type {1} could not be loaded due to {1}, that type-based renderer will not be used.

Cause: The instrumentation configuration specified a type-based renderer class that either was not found, is not accessible, or is not a renderer. It may also be that the type itself was not found or loadable.

Action: Verify that the type-based renderer class and type class are correctly specified in the instrumentation configuration and that they are available to the server classloader.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320161: A legacy Spring instrumentation API was called for an unknown method {0}.

Cause: A legacy Spring instrumentation API was called for an unknown method {0}.

Action: Instrument Spring using the tools in the current release.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320162: A legacy Spring instrumentation API was called.

Cause: A legacy Spring instrumentation API was called.

Action: Legacy Spring features should function normally, but you should instrument Spring using the tools in the current release.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320163: Wildcarded types are not allowed to be marked as being insensitive with %.

Cause: A % character was specified for a wildcarded type, such as an asterisk or ellipses. This is not allowed, as it could lead to inadvertantly exposing a type that should be treated as being sensitive.

Action: Review the pointcuts that specify the % character to ensure that it is not supplied for any types that are wildcarded using an asterisk or ellipses.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320164: Circular class load detected during stackmap frame computation for {0}.

Cause: An attempt was made to class load the class currently being instrumented. This is not supported.

Action: Do not instrument the class that encountered the cycle.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320165: Received an unexpected error dispatching an Instrumentation event for Watch rule processing: {0}

Cause: An exception occurred while dispatching a WLDF Instrumentation event for Watch rule processing.

Action: Check the server log for details on the error.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320166: Received an unexpected error dispatching an logging event for Watch rule processing: {0}

Cause: An exception occurred while dispatching a WLDF log event for Watch rule processing.

Action: Check the server log for details on the error.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320167: Expected monitors were not instrumented : {0}

Cause: Monitors which were specified as being expected to be instrumented were not instrumented.

Action: Review the instrumentation configuration and the code being instrumented, and then verify that all dependencies are available in the classpath to allow the instrumentor to walk the class hierarchy for inheritance matches.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320168: Disabling instrumentation on application "{0}" in partition "{1}" since it may contain shareable classloaders.

Cause: The deployment descriptor of this application may have indicated that its classloaders may be shared with applications in other partitions.

Action: If application instrumentation for this application is needed, remove shareable classloader definitions from the weblogic-application.xml deployment descriptor.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320169: Activating dynamic debug patch "{0}" at system level.

Cause: Dynamic debug patch is being activated at the system level.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320170: Activating dynamic debug patch "{0}" at application "{1}"

Cause: Dynamic debug patch is being activated at the application level.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320171: Activating dynamic debug patch "{0}" at module "{2}" in application "{1}"

Cause: Dynamic debug patch is being activated at the indicated module in the indicated application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320172: Activating dynamic debug patch "{0}" at application "{1}" in partition "{2}"

Cause: Dynamic debug patch is being activated at the indicated application in the indicated partition.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320173: Activating dynamic debug patch "{0}" at module "{2}" in application "{1}" in partition "{3}"

Cause: Dynamic debug patch is being activated at the indicated module in the indicated application in the indicated partition.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320174: Successfully activated debug patch "{0}".

Cause: Debug patch was successfully activated.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320175: Failed to activate dynamic debug patch "{0}".

Cause: Classes in the dynamic debug patch may be structurally different than the original classes.

Action: Check whether the class(es) in the dynamic debug patch are structurally different than the original classes.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320176: Deactivating dynamic debug patch "{0}" at system level.

Cause: Dynamic debug patch is being deactivated at the system level.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320177: Deactivating dynamic debug patch "{0}" at application "{1}"

Cause: Dynamic debug patch is being deactivated at the application level.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320178: Deactivating dynamic debug patch "{0}" at module "{2}" in application "{1}"

Cause: Dynamic debug patch is being deactivated at the indicated module in the indicated application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320179: Deactivating dynamic debug patch "{0}" at application "{1}" in partition "{2}"

Cause: Dynamic debug patch is being disabled at the indicated application in the indicated partition.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320180: Deactivating dynamic debug patch "{0}" at module "{2}" in application "{1}" in partition "{3}"

Cause: Dynamic debug patch is being deactivated.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320181: Successfully deactivated debug patch "{0}".

Cause: Debug patch was successfully deactivated.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320182: Failed to deactivate dynamic debug patch "{0}".

Cause: The indicated dynamic debug patch was not deactivated.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320183: Debug patch "{0}" contains unknown classes: "{1}

Cause: Debug patch contains unknown classes that cannot be found on the classpath.

Action: Contact the patch producers and have them address this issue.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320184: Failed to open diagnostic store file {0} due to reason: {1}. Re-trying to open..

Cause: This usually happens when the file is locked at the system level.

Action: Identify the entity holding the lock and release the lock. This may be a system-dependent operation.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320185: Failed to open diagnostic store file {0} after {1} attempts. Some diagnostics features will be unavailable.

Cause: This usually happens when the file is locked at the system level.

Action: Identify the entity holding the lock and release the lock. This may be a system dependent operation.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320186: Unable to find canonical path to diagnostic store directory {0}

Cause: The specified store directory path is not correct.

Action: Specify the correct store directory path.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320187: ClassInfo for {0} is not available.

Cause: The ClassInfo for the class was not able to be retrieved or computed.

Action: Enable instrumentation debug logging to determine the root cause.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320188: Long RID value with {0} components was created.

Cause: RID values grow during DiagnosticContext propagation, which are outbound calls to other JVMs or when Work is scheduled. Extremely long RID values may be expected but if they are growing rapidly, this may indicate a problem if they are growing unbounded. Note that the first occurrence of this message is reported immediately. After that it is throttled and only reported periodically if further growth is being seen. A corresponding log event is also produced to the FlightRecorder.

Action: Enable DiagnosticContext debug and review the FlightRecorder data to look for JFRDebugEvents which indicate extreme RID growth and where it is seen. Pay particular attention to the scheduling of work from daemon threads. These can cause RID growth and may require that the daemon thread call DiagnosticContextHelper.handleLocalContextAsNonInheritable() to prevent propagating the Context.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320189: Log file or rotation directory for accessor {0} changed, but the accessor failed to adapt to the change.

Cause: There may have been an error while refreshing the accessor due to an internal WebLogic error.

Action: Enable DebugDiagnosticAccessor and DebugDiagnosticArchive and review logs to get more information on the possible cause of the internal WebLogic error leading to this error.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320190: Failed to close diagnostic store.

Cause: Failed to close diagnostic store, likely to be due to an internal error.

Action: Review logs to get more information on the possible cause of the internal WebLogic error leading to this error.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320200: Action {0} of type {1} not valid for current WLDF deployment, ignoring.

Cause: The action type requested may not be valid for the WLDF deployment; for example, this can happen if the action is deployed on a managed server, but is only valid deployed within the administration server.

Action: Check the action documentation, and revise the Watch and/or action configuration accordingly.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320201: An unexpected error occurred while instantiating action {1} for action type {0}: {2}

Cause: An unexpected error occurred while instantiating the specified action instance.

Action: Check the error in the server logs and make any necessary configuration changes.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320202: Map entry string {0} is not valid.

Cause: A Map object entry in the WLDFActionBean did not have the proper form.

Action: Fix the entry in the WLDF System Resource descriptor.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320203: The timeout period of {1} seconds expired for action {0}, canceling the action execution.

Cause: The action did not complete withing the specified timeout interval.

Action: Consider increasing the timeout for the action, or see if an error occurred during processing that needs to be addressed.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320204: Executing action {0} with timeout period {1} seconds.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320205: An IOException occurred while communicating with server {0}, unable to query it for instances matching "{1}"

Cause: A network error occurred while attempting to communicate with server {0}. If the error persists, check the server logs and Node Manager logs.

Action: Determine the source of the communication error and correct it if possible.
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320206: An error occurred while executing the script action {0}: {1}

Cause: The configured script was not executed successfully. This may be due to an error in the action configuration or an error that was encountered within the script itself.

Action: Check the action configuration, and ensure that the script is available and has executable permissions.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320207: The script action {0} was interrupted during execution, exception: {1}

Cause: The script action may have timed out, or was abruptly terminated.

Action: Check the error message for details about what may have caused execution to be interrupted.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320208: An invalid action configuration type {0} was passed into the ScriptAction service, expected a configuration of type {1}.

Cause: The ScriptAction service is not receiving the expected configuration type. This is likely a product defect and should be reported to My Oracle Support.

Action: Contact My Oracle Support and provide them with the log file for further analysis.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320209: The executable path {1} for script action {0} is not valid.

Cause: The executable path indicated in the script action config is either missing or empty, or the path does not exist.

Action: Check the action configuration and correct the executable path.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320210: Script action {0} execution of {1} completed with exit code {2}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320211: Script action {0} starting, stdout redirected to {1}, stderr redirected to {2}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320212: Cancel was requested for script action {0}, destroying the process.

Cause: The currently executing script action was cancelled externally, either by user request or by the action exceeding the configured timeout.

Action: No action is required.
Level: 1

Type: WARNING

Impact: DiagnosticsWatch

BEA-320213: REST notification {0} could not be delivered successfully to end point {1}. The response code is {2} and the detailed reason is {3}.

Cause: The REST end point may not be available or the REST notification is not configured correctly.

Action: Take appropriate action based on the status code and detailed reason reported in the error.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320214: No action config present in action context.

Cause: There is likely a misconfiguration in the WLDFSystemResourceMBean associated with the action.

Action: Check the configuration and resolve any issues.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320215: Scale down action {0} invoked for cluster {1} with scaling size {2} and timeout period of {3} seconds.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320216: Scale down task {0} for cluster {1} complete, status: {2}

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320217: Invalid configuration {0} of type {1} passed to scale down action, expected an object of type {2}.

Cause: This was caused by an invalid configuration or a software defect.

Action: Verify the action and policy configuration.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320218: No scale-up action config present in action context

Cause: There is likely a misconfiguration in the WLDFSystemResourceMBean associated with the action.

Action: Check the configuration and resolve any issues.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320219: Invalid configuration {0} of type {1} passed to scale down action, expected an object of type {2}.

Cause: This was caused by an invalid configuration or a software defect.

Action: Verify the action and policy configuration.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320220: Scale up action {0} invoked for cluster {1} with scaling size {2} and timeout period of {3} seconds.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320221: Scale up task {0} for cluster {1} complete, status: {2}

Cause: The scale up task for the cluster is complete.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320222: Skipping actions processing for policy {0} since processing for a previous invocation is still in progress.

Cause: A previous invocation of the actions processing was found to be in progress. The new invocation was skipped.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320223: Another ThreadDumpAction is already in progress, so skipping execution of action {0}.

Cause: Another ThreadDumpAction is already in progress.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320224: Thread dump created at {0} by thread dump action {1} for policy {2} in diagnostics module {3}.

Cause: Thread dump is created due to execution of ThreadDumpAction.

Action: Analyze generated thread dumps.
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320225: Failed to write thread dump file {0}. {1}

Cause: Failed to write thread dump file due to permission or other file system problem.

Action: Ensure appropriate permissions and sufficient disk space.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320226: Waiting for {0} seconds before capturing next thread dump.

Cause: Wait for configured time between successive thread dump captures.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320227: An attempt to capture a heap was made while another capture was already in progress.

Cause: An attempt to capture a new heap dump was made while another capture was already in progress; only one capture is allowed at a time.

Action: No action is required.
Level: 1

Type: WARNING

Impact: DiagnosticsWatch

BEA-320228: Capturing heap heap dump to file {0}, liveSetOnly={1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320229: An unexpected exception occurred checking for the availability of the heap dump operation, heap dump action is not available: {0}

Cause: The HotSpot Diagnostic MBean is not available in the local JVM, therefore the heap dump action will not be available.

Action: If the heap dump action is required, consider using a version of the Java Virtual Machine that supports the HotSpot Diagnostic MBean.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320230: Heap dump capture by action {1} for policy {2} in module {3} complete, located at {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320231: HeapDumpAction {0} was deployed on a JVM platform that does not suport it, the action will be disabled

Cause: HeapDumpAction {0} was deployed on a JVM platform that does not suport it.

Action: If the action is required, consider using a JVM that supports the HotSpot Diagnostic MBean.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320232: The JMX Platform MBeanServer can not be found, heap dump actions are not available.

Cause: The Platform MBeanServer could not be found, check that the JVM supports the HotSpot Diagnostic MXBean.

Action: If the heap dump action is required, consider using a JVM that supports the HotSpot Diagnostic MXBean.
Level: 1

Type: WARNING

Impact: DiagnosticsWatch

BEA-320233: The dumpHeap() method could not be found, heap dump actions will not be available for this JVM.

Cause: The dumpHeap() method could not be found on the Hotspot Diagnostic MBean.

Action: If the heap dump action is required, consider using a JVM that supports the HotSpot Diagnostic MXBean.
Level: 1

Type: WARNING

Impact: DiagnosticsWatch

BEA-320234: The Hotspot Diagnostic MBean with ObjectName {0} could not be found, heap dump actions will not be available for this JVM

Cause: The JVM may not support heap dump operations.

Action: If the heap dump action is required, consider using a JVM that supports the HotSpot Diagnostic MXBean.
Level: 1

Type: WARNING

Impact: DiagnosticsWatch

BEA-320235: Caught unexpected error capturing heap dump: {0}

Cause: An unexpected error occurred while capturing a heap dump.

Action: Check the exception message in the server logs, contact Oracle Support if the issue can not be corrected.
Level: 1

Type: ERROR

Impact: DiagnosticsWatch

BEA-320236: Thread dump action {0} canceled

Cause: Thread dump action was cancelled.

Action: No action necessary.
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320237: Older dump file {0} removed to make space for new dump file.

Cause: Limit for number of heap or thread dump files is already reached. Removing older dump files to make space for new dump file.

Action: No action necessary.
Level: 1

Type: NOTIFICATION

Impact: DiagnosticsWatch

BEA-320238: Unable to execute scale down action {0}, cluster {1} is already at the minimum number of required running servers: {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: DiagnosticsWatch

BEA-320239: Unable to execute scale up action {0}, cluster {1} is already at the maximum allowed number of running servers: {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: DiagnosticsWatch

BEA-320300: The WLS ServerRuntime MBeanServer was not available for harvesting; custom MBean harvesting will not be available.

Cause: This could be the result of a serious error in the OA&M infrastructure. Check for other error messages in the log in that area.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsHarvester

BEA-320301: The WLDF Harvester could not activate the Watch and Notifications framework due to an exception: {0}

Cause: During server startup, the Watch and Notifications activation is deferred until the WLDF Harvester is fully activated. The deferred activation encountered an unexpected exception, potentially impairing the Watch and Notifications functionality.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsHarvester

BEA-320303: The namespace {1} for the harvested type specification {0} can not be serviced by a Managed Server instance; it is valid only when targed to an Administration Server.

Cause: A harvested type specifying the DomainRuntime namespace was targeted to a Managed Server. A Managed Server can only service the ServerRuntime namespace.

Action: Correct the namespace declaration of the harvested type, or retarget the WLDF configuration to an Administration Server in order to service this type.
Level: 1

Type: WARNING

Impact: DiagnosticsHarvester

BEA-320304: The following errors were reported during the validation of the metrics for watched values {0}: {1}

Cause: Some of the configured harvested types may have errors, resulting in the harvester being unable to process them for collection.

Action: Correct any issues with the harvested type configuration.
Level: 1

Type: WARNING

Impact: DiagnosticsHarvester

BEA-320305: The instance name {0} is not a valid ObjectName or instance name pattern.

Cause: The instance name must be a valid JMX ObjectName, or a pattern conforming to the syntax supported by the WebLogic Diagnostics Framework.

Action: Correct the instance name in the harvested type.
Level: 1

Type: ERROR

Impact: DiagnosticsHarvester

BEA-320400: The log file {0} will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms, such as Windows.

Cause: This event happens whenever the log file is about to be rotated based on either size or time rotation criterion.

Action: On certain platforms, if some application is tailing the log, the rotation fails. Stop the application tailing and reopen the tail after the rotation is complete.
Level: 1

Type: NOTIFICATION

Impact: LoggingService

BEA-320401: The log file has been rotated to {1}. Log messages will continue to be logged in {0}.

Cause: This event happens after the log file is rotated based on either size or time rotation criterion.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: LoggingService

BEA-320450: The DebugScope name {0} is not valid.

Cause: The DebugScope with the given name is not defined in the ServerDebugMBean interface.

Action: Configure the debug scope with a valid name.
Level: 1

Type: ERROR

Impact: DebugModule

BEA-320451: An error occurred while applying the DebugScopes configuration.

Cause: This may be due to an I/O error while reading the DebugScopes from the disk.

Action: Take action based on the error stack trace.
Level: 1

Type: ERROR

Impact: DebugModule

BEA-320452: An error occurred while adding PropertyChangeListener to bean {0}.

Cause: The debug configuration bean does not support PropertyChangeListeners.

Action: Take action based on the error stack trace.
Level: 1

Type: ERROR

Impact: DebugModule

BEA-320453: An error occurred while removing PropertyChangeListener from bean {0}.

Cause: The debug configuration bean does not support PropertyChangeListeners.

Action: Take action based on the error stack trace.
Level: 1

Type: ERROR

Impact: DebugModule

BEA-320454: An error occurred while initializing Server Debug from older DebugCategory mappings.

Cause: The error details are included in the stack trace of the Exception reported.

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 WebLogic Server 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: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400201: Migrating old security provider JARS from {0}

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400204: No security provider JARs have been upgraded.

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400205: Copying the upgraded security provider JAR to {0}

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400206: Completed upgrading of {0} old security provider JARs.

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400207: Skipped converting {0} since it is a security provider JAR built with 9.0.

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400208: No MDFs (.xmls) found in the old security provider JAR with name {0}

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400209: Created new security provider JAR {0} from {1}

Cause: See the message body.

Action: No action required.
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: See the message body.

Action: No action required.
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: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400212: Now processing {0}

Cause: See the message body.

Action: No action required.
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: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400214: Running the first phase of Security Provider Upgrade process on {0}

Cause: See the message body.

Action: No action required.
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: See the message body.

Action: No action required.
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-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: See the message body.

Action: No action required.
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: The MBeanTypeUtil has failed while trying to access a registered MBean.

Action: Check for other log messages that give more information about the failure.
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: The MBeanTypeUtil has failed to access a registered MBean in two tries.

Action: Check for other log messages that give more information about the failure.
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: The MBeanTypeUtil has failed to access two consecutive different MBeans.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: MBeanTypingUtil

BEA-2012306: {1} Unable to process the {2} of MBean: {0} . 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} . 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-2145000: Unable to fire asynchronous listeners. Associated stack trace follows:

Cause: An error condition was reported.

Action: Check the Work Manager configuration for work scheduling problems.
Level: 1

Type: WARNING

Impact: BEA Cache

BEA-2145001: Could not configure cache with write policy of {0} because no store has been configured for the cache.

Cause: The configuration is invalid.

Action: Either remove the write policy configuration or specify a custom store along with it.
Level: 1

Type: ERROR

Impact: BEA Cache

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-2154000: Enabling FastSwap on application "{0}".

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: FastSwap

BEA-2154001: Starting FastSwap operation on application "{0}".

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: FastSwap

BEA-2154002: Finished FastSwap operation on application "{0}" with status {1}.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: FastSwap

BEA-2154003: FastSwap operation on application "{0}" failed: {1}.

Cause: One or more classes could not be redefined.

Action: Redeploy the application for updates to classes to take effect.
Level: 1

Type: ERROR

Impact: FastSwap

BEA-2156001: "config-root" {0} is not a directory.

Cause: The "config-root" may not have been set properly.

Action: Verify that the "config-root" is correct.
Level: 1

Type: WARNING

Impact: WebLogicDescriptorWL

BEA-2156002: Attribute "{0}": duration value "{1}" is not valid: {2}

Cause: The provided duration value was not a valid duration lexical representation.

Action: See the lexical rules for a javax.datatype.Duration, and ensure that the provided duration value is valid according to these rules.
Level: 1

Type: ERROR

Impact: WebLogicDescriptorWL

BEA-2156003: Attribute "{0}": logical store name value "{1}" is not valid.

Cause: The provided logical store name value was not a valid name. Logical store names must be valid Java identifiers.

Action: See the lexical rules for a Java identifier, and ensure that the logical store name follows these rules.
Level: 1

Type: ERROR

Impact: WebLogicDescriptorWL

BEA-2156004: Attribute "{0}": JNDI name value "{1}" is not valid.

Cause: The provided JNDI name value was not a valid name. JNDI names must be non-null and non-empty and meet the rules of the J2EE platform's JNDI implementation.

Action: See the lexical rules for a JNDI name, and ensure that the JNDI name follows these rules.
Level: 1

Type: ERROR

Impact: WebLogicDescriptorWL

BEA-2156200: Unable to load descriptor {1} of module {0}. The error is {2}.

Cause: The descriptor is not valid.

Action: Correct the descriptor.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156201: An error occurred while parsing descriptors: {0}.

Cause: Check the stack trace.

Action: Check the stack trace.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156202: References were found in the deployment plan for module "{0}" with URI, "{1}". The plan was merged.

Cause: The plan contained variable overrides.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156203: A version attribute was not found in element "{0}" in the deployment descriptor {1}. A version attribute is required, but this version of the WebLogic Server will assume that the latest version is used. Future versions of WebLogic Server will reject descriptors that do not specify the Java EE version. To eliminate this warning, add an appropriate "version=" to element "{0}" in the deployment descriptor.

Cause: The required version attribute was missing.

Action: Add the version attribute with the appropriate JEE version value.
Level: 1

Type: WARNING

Impact: Munger

BEA-2156204: The root element {0} is missing in the descriptor file {1}.

Cause: The required root element was missing in the descriptor file.

Action: Add the root element to the descriptor file.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156205: Updating the configuration with the deployment plan overrides for module "{0}" with URI, "{1}".

Cause: A deployment plan was specified for the application.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156206: No module overrides were found in the deployment plan for module "{0}" with URI, "{1}". If overrides were expected for this module, verify the deployment plan.

Cause: The plan contained no matching variable overrides.

Action: No action is required. This is an informational message. It may be an expected action.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156207: The variable assignment from the deployment plan with variable name "{0}" and XPath "{1}" will be included when overriding the deployment configuration.

Cause: The plan contained matching variable overrides.

Action: No action is required. This is an informational message used to troubleshoot deployment plan overrides.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156208: The variable assignment from the deployment plan with variable name "{0}" and XPath "{1}" will be included when overriding the deployment configuration.

Cause: The plan contained matching variable overrides.

Action: No action is required. This is an informational message used to troubleshoot deployment plan overrides.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156209: Applying the overrides from the deployment plan for module "{0}" with URI, "{1}".

Cause: A deployment plan was specified for the application.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156210: Applying the override for variable "{0}" with XPath "{1}" and operation "{2}".

Cause: A deployment plan was specified for the application.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156211: After applying the overrides from the deployment plan, the descriptor "{0}" is: "{1}".

Cause: A deployment plan was specified for the application. The descriptor was updated.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156212: An error occurred while parsing the specifed XPath "{0}" : {1}.

Cause: The specified XPath value was invalid.

Action: Check the associated exception to determine the cause, and correct the XPath value.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156213: An error occurred while parsing the specifed XPath "{0}" : {1}.

Cause: The specified XPath value was invalid.

Action: Check the associated exception to determine the cause, and correct the XPath value.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156214: The XPath "{0}" specifies a key selection but the bean "{1}" does not have any keys defined.

Cause: The specified XPath value was invalid because no keys were defined for this element.

Action: Check the associated schema, and ensure that the element has the corresponding key.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156215: Removed the value matched by the deployment plan variable "{0}" with element name "{1}".

Cause: A deployment plan was specified for the application, and an element has been removed.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156216: The deployment plan operation failed because there was no method named "{0}" on the bean "{1}" corresponding to the element "{2}".

Cause: A deployment plan operation requires a corresponding destroy, remove, or set method. This method was not present.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156217: An error occurred while performing the plan operation for variable "{0}" with element name "{1}" : {2}.

Cause: An unexpected exception occurred during the deployment plan operation.

Action: Check the associated exception to determine the cause, and correct the issue.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156218: Updated the element matched by the deployment plan variable "{0}" with element name "{1}" to have value "{2}".

Cause: A deployment plan was specified for the application, and a matching element has been updated.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156219: Created the element matched by the deployment plan variable "{0}" with element name "{1}".

Cause: A deployment plan was specified for the application, and a matching element has been created.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156220: Created the element matched by the deployment plan variable "{0}" with element name "{1}" to have name "{2}".

Cause: A deployment plan was specified for the application, and a matching element has been created.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156221: The remove operation for the deployment plan variable "{0}" with element name "{1}" specified an array index of "{2}" but the array was smaller, so no elements were removed.

Cause: The specified array index was larger than the size of the array.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156222: The variable "{0}" specifies a property "{1}" that is a primitive array but no index is specified in the XPath.

Cause: The specified XPath value was invalid since no array index was defined for this element.

Action: Check the XPath, and specify an index.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156223: The variable "{0}" for the add operation does not specify a property in the XPath "{1}". This variable assignment has been ignored.

Cause: The specified XPath value was invalid since no property was specified for the add operation.

Action: Check the XPath, and specify a property.
Level: 1

Type: WARNING

Impact: Munger

BEA-2156224: Added the element matched by the deployment plan variable "{0}" with element name "{1}" with value "{2}".

Cause: A deployment plan was specified for the application, and a matching element has been added.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156225: The XPath "{0}" contains a trailing invalid "/". It has been ignored. Remove it from the XPath expression.

Cause: The specified XPath value was invalid because it contained a trailing slash.

Action: Remove the trailing slash.
Level: 1

Type: WARNING

Impact: Munger

BEA-2156226: Skipping the override for the deployment plan variable "{0}" and XPath "{1}" since the value is not set in the deployment plan.

Cause: A deployment plan did not contain a value for the variable.

Action: Add a variable value if one is desired, or remove the variable assignment if it is not needed.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156227: The "{0}" deployment descriptor for the "{1}" module is in DTD format. Overrides from the deployment plan will NOT be applied since only deployment descriptors in XML Schema format are supported.

Cause: A deployment descriptor in DTD format exists in the application archive.

Action: Convert the deployment descriptor to an XML Schema format.
Level: 1

Type: WARNING

Impact: Munger

BEA-2156228: Updating the configuration with the resource deployment plan overrides for resource "{0}".

Cause: A resource deployment plan was specified for the application.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156229: References were found in the resource deployment plan for resource "{0}". 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-2156230: No resource overrides were found in the resource deployment plan for resource "{0}". If overrides were expected for this resource, verify the resource 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-2156231: Applying the overrides from the resource deployment plan for resource "{0}".

Cause: A resource deployment plan was specified for the application.

Action: No action is required. This is an informational message.
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 is more than one instance of CoherenceClusterSystemResourceMBean defined using {0}

Cause: Multiple instances of CoherenceClusterSystemResourceMBean were targeted.

Action: When the Coherence JAR is in the system classpath, only one CoherenceClusterSystemResourceMBean should be targeted to the server.
Level: 1

Type: NOTIFICATION

Impact: CacheProvider

BEA-2156301: Failed to shut down application {0} due to {1}

Cause: Failed to shut down application {0} due to {1}

Action: Examine the exception details and take corrective actions.
Level: 1

Type: ERROR

Impact: CacheProvider

BEA-2156302: Only one server can be a management proxy in a Coherence cluster. {0} has {1} and {2} set as management proxies

Cause: Only one server can be a management proxy in a Coherence cluster. {0} has {1} and {2} set as management proxies.

Action: Examine the CoherenceMemberConfig management proxy setting for each server.
Level: 1

Type: ERROR

Impact: CacheProvider

BEA-2156303: Invoking {0} on node {1} resulted in {2}.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: WARNING

Impact: CacheProvider

BEA-2156304: MBeanServerConnector not available at: {0}

Cause: See the message body.

Action: No action is required.
Level: 1

Type: WARNING

Impact: CacheProvider

BEA-2156400: The validation.xml file, located at {0}, does not conform to the JSR 303 specifications.

Cause: The file does not conform to the JSR 303 specification. This 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: See the message detail.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: ERROR

Impact: Weblogic-Validation

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

Cause: See the message detail.

Action: Check for other log messages that give more information about the failure.
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: See the message body.

Action: Check for other log messages that give more information about the failure.
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 WebLogic Server 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-2159700: {0}

Cause: REST logs informational messages about REST usage.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: REST

BEA-2159701: {0}

Cause: REST has encountered an error that is potentially harmful.

Action: Review the warning message text to determine the appropriate action.
Level: 1

Type: ERROR

Impact: REST

BEA-2159702: REST encountered the following error: {0}

Cause: REST has encountered an error, but may continue to run.

Action: Review the error message text to determine the appropriate action.
Level: 1

Type: ERROR

Impact: REST

BEA-2159703: REST encountered the following error: {0}

Cause: REST has encountered a critical error.

Action: Review the message text to determine the appropriate action.
Level: 1

Type: INTERNAL_ERROR

Impact: REST

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: See the message detail.

Action: Check for other log messages that give more information about the failure.
Level: 1

Type: WARNING

Impact: WeblogicSpring

BEA-2160002: "{0}" is not a registered scope name.

Cause: The scope name supplied to a runtime mbean operation is not registered.

Action: Supply a registered scope name to the runtime mbean operation.
Level: 1

Type: WARNING

Impact: WeblogicSpring

BEA-2162200: No Main-Class defined in the manifest file of Java Module: {0}. This module will be treated as a utility JAR and subsequent initialization steps will be skipped.

Cause: See the message body.

Action: No action is required unless you believe that this should be a Java client module. In this case, you should specify Main_Class for this module in MANIFEST.MF.
Level: 1

Type: NOTIFICATION

Impact: Application Client

BEA-2162206: Warning: Could not find an entry for javax.transaction.UserTransaction in the root context.

Cause: There is no entry for javax.transaction.UserTransaction in the root context.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Application Client

BEA-2162210: No persistence unit named '{0}' is available in scope.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Application Client

BEA-2162224: No {0} was specified in your client-jar file: {1}.

Cause: This is a retired message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Application Client

BEA-2162231: Warning: Could not bind java:comp/DefaultJMSConnectionFactory due to the following exception - {0}.

Cause: Binding java:comp/DefaultJMSConnectionFactory to the application client container failed.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Application Client

BEA-2162500: Class, {0}, was compiled with an incompatible version of Java. Ensure that all the classes needed by the application have been compiled with a compatible java version. {1}

Cause: This error occurred while attempting to use a class that was compiled with a java compiler version that is not compatible with the JVM used by the application server.

Action: Ensure 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 could not define class, {0} due to the following error: {1}

Cause: The cause of this is unknown.

Action: Contact My Oracle Support for assistance.
Level: 1

Type: ERROR

Impact: Class Loaders

BEA-2162502: Ignoring manifest file for classpath entry {0}.

Cause: An error occurred while reading the manifest file for the classpath entry.

Action: Inspect the exception stack trace and correct the problem.
Level: 1

Type: WARNING

Impact: Class Loaders

BEA-2162503: Not adding pre-processor class {0}.

Cause: The pre-processor class was not found.

Action: Inspect the exception stack trace and correct the problem.
Level: 1

Type: WARNING

Impact: Class Loaders

BEA-2162504: Not adding pre-processor class {0}.

Cause: The pre-processor class could not be intialized.

Action: Inspect the exception stack trace and correct the problem.
Level: 1

Type: WARNING

Impact: Class Loaders

BEA-2162505: Skipping pre-processing using pre-processor {0} with description: {1}

Cause: An error was encountered while pre-processing.

Action: Inspect the exception stack trace and correct the problem.
Level: 1

Type: WARNING

Impact: Class Loaders

BEA-2162506: Ignoring manifest during definition of class {0}.

Cause: An error occurred while reading the manifest for the jar file. The manifest declaration will be ignored during class definition.

Action: To fix this problem, inspect the exception stack trace, and correct the problem
Level: 1

Type: WARNING

Impact: Class Loaders

BEA-2162507: Aborting annotation processing due to a symlink cycle. The following directory has been visited already. Path: {0} Cannonical Path: {1}.

Cause: Symlink cycles in a classes directory tree are causing the directory traversal to repeat the traversal of part of the directory tree indefinitely.

Action: Inspect the classes directory that is related to the reported path for symlink. Ensure that the symlinks do not cause cycling. Differences between the Path and Cannonical Path may suggest where the troublesome symlink lies.
Level: 1

Type: ERROR

Impact: Class Loaders

BEA-2162508: corrupted jar found. file:{0} ,md5sum:{1}, lastModified:{2}.

Cause: An error occurred while reading jar file. This means archive corruption.

Action: To fix this problem, inspect the exception stack trace, and correct the problem
Level: 1

Type: WARNING

Impact: Class Loaders

BEA-2162600: Creating ManagedThreadFactory "{2}" (partition="{3}", module="{0}", application="{1}")

Cause: The application is being initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162601: Creating ContextService "{2}" (partition="{3}", module="{0}", application="{1}")

Cause: The application is being initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162602: {0} is still running, create another timer {1}.

Cause: A timer with the same name in ManagedScheduledExecutorService has already been created.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162603: The value {1} of parameter {0} is illegal.

Cause: The provided parameter value is illegal.

Action: Provide a valid value.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162604: Unable to create runtime MBean for concurrent managed object {0}. {1}

Cause: A fatal error occurred while creating the runtime MBeans.

Action: Contact My Oracle Support and provide them with the server logs.
Level: 1

Type: INTERNAL_ERROR

Impact: CONCURRENCY

BEA-2162605: ManagedThreadFactory {0} rejected newThread request as current length reached max capacity {1}, limit type {2}.

Cause: A newThread request was rejected as the capacity was reached.

Action: Configure the MaxConcurrentNewThreads attribute to limit running threads created by ManagedThreadFactory.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162606: Managed(Scheduled)ExecutorService {0} rejected newThread request as current length reached max capacity {1}, limit type {2}.

Cause: A newThread request was rejected as the capacity was reached.

Action: Configure the MaxConcurrentLongRunningThreads attribute to limit running threads created by Managed(Scheduled)ExecutorService.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162607: Out-of-date thread {1} is still running when ManagedThreadFactory {0} is restarted.

Cause: A thread was shut down and interrupted when the ManagedThreadFactory was stopped but it was still running when the ManagedThreadFactory was restarted.

Action: No action is required. The thread will be still running in a shutdown and interrupted state.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162608: ManagedTaskListener registered for task {0} throws exception in method {1}: {2}

Cause: A user-provided ManagedTaskListener implementation may have a defect.

Action: Check your ManagedTaskListener implementation.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162609: An attempt to process user a transaction failed:{0}

Cause: Transaction processing failed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162610: Creating ManagedExecutorService "{4}" (partition="{0}", module="{2}", application="{1}", workmanager="{3}")

Cause: The application is being initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162611: Creating ManagedScheduledExecutorService "{4}" (partition="{0}", module="{2}", application="{1}", workmanager="{3}")

Cause: The application is being initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162612: ManagedThreadFactory {0} rejected newThread request as it is in an illegal state such as stopped.

Cause: A newThread request was rejected with an IllegalStateException as the ManagedThreadFactory was in an illegal state such as stopped.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162613: The invocation of method {0} of a proxy object failed because of the exception: {1}.

Cause: The invocation of method {0} of proxy object failed because of the exception: {1}.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162614: Workmanager {0} in application {1} could not be found, using default.

Cause: The dispatch-policy attribute is not correct.

Action: Correct the dispatch-policy attribute.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162615: Concurrent object {2} in application {0} module {1} could not be found, using default.

Cause: The resource-link or mappedName attribute of the resource reference is not correct.

Action: Correct the resource-link or mappedName attribute of the resource reference.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162616: Proxy is created by a different ContextService object.

Cause: This occurred while trying to get the execution properties on a contextual object proxy that was created by a different ContextService.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162617: ContextObject is not a valid contextual object proxy created with the createContextualProxy method.

Cause: This occurred while trying to get the execution properties on an invalid contextual object proxy by calling the getExecutionProperties() method of ContextService.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162618: The instance parameter of createContextualProxy method cannot be null.

Cause: This occurred while trying to create a new contextual object proxy by calling the createContextualProxy method of ContextService but the input object instance was null.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162619: The interfaces parameter of createContextualProxy method cannot be null.

Cause: This occurred while trying to create a new contextual object proxy by calling the createContextualProxy method of ContextService but no interface was specified.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162620: Class does not implement at least one of the provided interfaces.

Cause: This occurred while trying to create a new contextual object proxy by calling the createContextualProxy method of ContextService, but the instance does not implement at least one of the provided interfaces.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162621: Lifecycle related method is not supported.

Cause: An attempt was made to invoke an unsupported lifecycle related method.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162622: Task list is empty.

Cause: An empty task list was passed to invokeAll/invokeAny.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162623: Task submission was rejected because executor {0} has been stopped.

Cause: A task was submitted to a stopped executor.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162624: Task was canceled because concurrent managed object {0} is stopped.

Cause: A task was submitted to a stopped concurrent managed object.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162625: ManagedExecutorService {0} rejected a newThread request as it is in an illegal state such as stopped.

Cause: A newThread request was rejected with an IllegalStateException as the ManagedExecutorService was in an illegal state such as stopped.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162626: Task {0} was canceled by user.

Cause: A task was canceled by a user.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162627: Contextual object proxy deserialization error: {0} is expected but current object is {1}.

Cause: An attempt was made to deserialize a contextual object proxy but the context was not as expected.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162628: Save contexts failed: {0}.

Cause: An exception occurred while saving the current contexts. The context's setup in the executing thread will be ignored.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162629: Setup contexts failed: {0}.

Cause: An exception occurred while setting up contexts in the executing thread. The contexts will be rolled back.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162630: Reset contexts failed: {0}.

Cause: An exception occurred while resetting the current contexts in the executing thread.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162631: Concurrent managed objects are used before the concurrent service is started. {0}

Cause: Concurrent managed objects were used before the concurrent service was started.

Action: No action is required.
Level: 1

Type: WARNING

Impact: CONCURRENCY

BEA-2162632: New thread request was rejected by ManagedThreadFactory {0} because {1}.

Cause: A new thread request was rejected by the limit of maximum new threads or the serialize-deserialize check.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162633: Contextual object proxy deserialization error: cannot get the expected {0} from cache with key {1}.

Cause: An attempt was made to deserialize a contextual object proxy but no related context can be found in cache. Check the status of the corresponding application to see if the context was released.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162634: Override {0} is not allowed.

Cause: A task is canceled by a user

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162635: Override is is not allowed.

Cause: The JNDI name was not correct.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162636: Task {1} submitted to {0} skip partition class loader check.

Cause: This is an information message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162637: Unable to create ConcurrentManagedObjectsRuntimeMBean for partition {0}. {1}

Cause: An exception occurred while creating the ConcurrentManagedObjectsRuntimeMBean.

Action: Contact My Oracle Support and provide them with the server logs.
Level: 1

Type: WARNING

Impact: CONCURRENCY

BEA-2162638: Unable to destroy ConcurrentManagedObjectsRuntimeMBean for partition {0}. {1}

Cause: An exception occurred while destroying the ConcurrentManagedObjectsRuntimeMBean.

Action: Contact My Oracle Support and provide them with the server logs.
Level: 1

Type: WARNING

Impact: CONCURRENCY

BEA-2162639: Context setup failed because {0} is not started.

Cause: Context setup failed because {0} is not started.

Action: Check the state of the corresponding partition, application or module.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162640: Unable to create the partition level concurrent manangement object.

Cause: The partition level concurrent manangement object could not be created.

Action: Contact My Oracle Support and provide them with the server logs.
Level: 1

Type: WARNING

Impact: CONCURRENCY

BEA-2162641: Trying to unbind a non-existent {0} factory named {1}: {2}

Cause: An attempt was made to unbind a non-existent factory.

Action: Contact My Oracle Support and provide them with the server logs.
Level: 1

Type: WARNING

Impact: CONCURRENCY

BEA-2162642: Roll back transaction {0} because it was begun but has not been committed by task {1}.

Cause: The transaction was not committed by the task after it had begun.

Action: Contact My Oracle Support and provide them with the server logs.
Level: 1

Type: WARNING

Impact: CONCURRENCY

BEA-2162643: Trigger used for task {0} throws exception in method {1}: {2}

Cause: A Trigger implementation may have a defect.

Action: Check the Trigger implementation.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162644: {0} belonging to ManagedExecutorService {1}, application {2} was released as the ManagedExecutorService was shutting down.

Cause: This is an information message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162645: {0} belonging to ManagedExecutorService {1}, WorkManager {2}, application {3} was released as the WorkManager was shutdown and the task was not submitted by an administrator.

Cause: This is an information message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162646: {0} cannot be used outside of its partition in {1}: {2}

Cause: A concurrent managed object was used outside of its partition.

Action: Check all code that is submitting tasks to the concurrent managed object.
Level: 1

Type: WARNING

Impact: CONCURRENCY

BEA-2162647: Application Level {0} cannot be used outside of its application in {1}: {2}

Cause: An application-level concurrent managed object was used outside of its application.

Action: Check all code that is submitting tasks to the concurrent managed object.
Level: 1

Type: WARNING

Impact: CONCURRENCY

BEA-2162648: {0} rejected the task because the submitting component {1} was not started: {2}

Cause: A concurrent managed object was used by another component and that component was not started.

Action: Check the state of the submitting component.
Level: 1

Type: WARNING

Impact: CONCURRENCY

BEA-2162649: {0} rejected createContextualProxy because it was not started.

Cause: createContextualProxy was rejected with an IllegalArgument exception as the ContextService was not started.

Action: Check the state of the ContextService.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162650: Context setup failed because the submitting component {0} is not started.

Cause: Context setup failed because the submitting component {0} is not started.

Action: Check the state of the submitting component.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162651: {0} belonging to ManagedExecutorService {1}, application {2} was released as the submitting application {3} was shutting down.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162652: Long running task was canceled because the submitting application {0} is stopped.

Cause: A long running task was canceled because the submitting application {0} is stopped.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CONCURRENCY

BEA-2162700: {0}: Cluster {1} contains {2} running Managed Servers which meets or exceeds the maximum number of allowed servers ({3}). The cluster will not be scaled up.

Cause: The cluster size has already reached the configured Maximum Elastic Cluster Size.

Action: If possible, for example, if additional capacity exists, increase the Maximum Elastic Cluster Size.
Level: 1

Type: WARNING

Impact: Elasticity

BEA-2162701: {0}: Cluster {1} contains a sufficient number of available Managed Servers. Cluster will be scaled by {2} servers.

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162702: {0}: Proposed size ({2}) for cluster {1} will exceed the configured maximum size. Limiting cluster size to {3}.

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162703: {0}: Cluster {1} will be expanded by {2} servers.

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162704: {0}: Cluster {1} contains only {2} running Managed Servers which is less or equal to the minimum number of servers ({3}). The cluster will not be scaled down.

Cause: Cluster size has already reached the configured Minimum Elastic Cluster Size.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Elasticity

BEA-2162705: {0}: Cluster {1} will be scaled down by {2} servers.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162706: {0}: Cluster {1} has only {2} running servers. The cluster will be scaled down by {3} servers instead of the requested scaling size {4} since the minimum size of the cluster is {5}.

Cause: There are fewer running servers than what may be necessary to satisfy the request to shut down the specified number of servers.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162707: A suitable Lifecycle Management end point was not found while performing a scaling operation on cluster {0}. The scaling operation will be attempted without Lifecycle Management capabilities.

Cause: A suitable Lifecycle Management end point was not found while performing a scaling operation on the cluster.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162708: {0}: Unable to scale cluster {1} by the requested amount of {2}, adjusting scaling request to {3} instances.

Cause: The requested capacity likely exceeded the MaxDynamicClusterSize setting for the cluster.

Action: If necessary, increase the MaxDynamicClusterSize on the DynamicServersMBean for the cluster. This may, however, also require that you provision additional hardware capacity.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162709: {0}: Scaling operation failed to start server {2} for cluster {1}.

Cause: Server startup failed. Check the server log to determine why the startup failed.

Action: Determine what caused the startup to fail, and take corrective action.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162710: {0}: Cluster {1} scale up, server {2} successfully started.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162711: {0}: Scale up work for cluster {1} completed, started {2} new instances.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162712: {0}: The workflow operation status for the scale-up work was null.

Cause: The scale-up work may not be configured correctly, or this could be a product defect.

Action: Check the server log and contact My Oracle Support if necessary.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162713: Current size of dynamic cluster {0} is already at maximum: {1}

Cause: The dynamic cluster size maximum was reached.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Elasticity

BEA-2162714: Updating max servers count for {0} by {1} to {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162715: Failed to perform forced shutdown on server {0} during scaledown operation on cluster {1}. {2}

Cause: There may be an environmental problem.

Action: Check other log messages in the log for details.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162716: Unable to locate ServerLifecycleRuntimeMBean instance for {0}.

Cause: This can result when the cluster size was not successfully adjusted to meet the requested capacity, but the scale-up was attempted.

Action: Check the scaling action and DynamicServersMBean configuration for problems. If a defect is suspected, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162717: {0}: Scale down of server {1} completed successfully for cluster {2}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162718: An unexpected exception occurred trying to start server {0} in cluster {1}. {2}

Cause: An unexpected exception occurred.

Action: Check the server log for other messages for more details.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162719: Adjusting maximum servers count by requested amount {1} for cluster {0}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162720: {0}: Scaling operation failed to stop server {2} for cluster {1}.

Cause: Server shutdown failed, check the server log to determine why the startup failed.

Action: Determine what caused the shutdown to fail, and take corrective action.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162721: {0}: Scale down work for cluster {1} completed, stopped {2} instances.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162722: {0}: The workflow operation status for the scale-down work was null.

Cause: The scale down work may be misconfigured, or this could be a product defect.

Action: Check the server log and contact My Oracle Support if necessary.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162723: {0}: Graceful shutdown of server {1} in cluster {2} failed. Performing a forceful shutdown on the server.

Cause: Graceful shutdown may not finish due to reasons such as sessions that may not have migrated within the specified timeout period.

Action: If more time will be needed for quiescing the server before shutdown, increase the value of the DynamicClusterShutdownTimeoutSeconds attribute in the DynamicServersMBean for the cluster.
Level: 1

Type: WARNING

Impact: Elasticity

BEA-2162724: {0}: ScriptExecutorCommand executing pre-processor script {1} as configured in script MBean {2} while performing scale up operation for cluster {3}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162725: {0}: ScriptExecutorCommand executing pre-processor script {1} as configured in script MBean {2} while performing scale down operation for cluster {3}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162726: {0}: ScriptExecutorCommand executing post-processor script {1} as configured in script MBean {2} while performing scale up operation for cluster {3}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162727: {0}: ScriptExecutorCommand executing post-processor script {1} as configured in script MBean {2} while performing scale down operation for cluster {3}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162728: {0}: Pre-processor script {1} as configured in script MBean {2} completed with exit code {4} while performing scale up operation for cluster {3}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162729: {0}: Pre-processor script {1} as configured in script MBean {2} completed with exit code {4} while performing scale down operation for cluster {3}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162730: {0}: Post-processor script {1} as configured in script MBean {2} completed with exit code {4} while performing scale up operation for cluster {3}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162731: {0}: Post-processor script {1} as configured in script MBean {2} completed with exit code {4} while performing scale-down operation for cluster {3}.

Cause: This is an informational message..

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162732: ScriptInterceptor adding workflow item for pre-processor script {0} as configured in script MBean {1} for performing scale-up operation for cluster {2}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162733: ScriptInterceptor adding workflow item for pre-processor script {0} as configured in script MBean {1} for performing scale-down operation for cluster {2}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162734: ScriptInterceptor adding workflow item for post-processor script {0} as configured in script MBean {1} for performing scale-up operation for cluster {2}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162735: ScriptInterceptor adding workflow item for post-processor script {0} as configured in script MBean {1} for performing scale-down operation for cluster {2}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162736: {0}: Script interceptor {2} timed out after {4} seconds while executing script {1} for cluster {3}.

Cause: The script did not complete within the specified timeout. The script may be hung or executing slower than expected.

Action: Investigate if the script is hung or depending on resources that may not be responding. Adjust the timeout settings if necessary.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162737: {0}: Script interceptor {2} failed with exit status {4} while executing script {1} for cluster {3}.

Cause: One or more commands executed by the script failed. In addition, the script may have errors or the interceptor may not be configured correctly.

Action: Check the configuration of the script interceptor and check for errors in the script or its configuration.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162738: {0}: An unexpected exception occurred while trying to cancel the scale-up operation for server {2} in cluster {1}: {3}

Cause: An unexpected exception occurred.

Action: Check the server log.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162739: {0}: An unexpected exception occurred while trying to cancel the scale-down operation for server {2} in cluster {1}: {3}

Cause: An unexpected exception occurred.

Action: Check the server log.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162740: {0}: Server {1} cannot participate in scaling operation because its NodeManager is either not configured correctly or not reachable.

Cause: NodeManager for the server is either not configured correctly or is unreachable.

Action: Check the Machine and NodeManager configuration for the server and ensure that the NodeManager is running properly.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162741: {0}: Aborting execution of script {1} due to cancel or timeout.

Cause: The script executed by a ScriptInterceptor was aborted due to a cancel operation or timeout.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162742: Scaling operation with Lifecycle Management endpoint {0} failed. Please check endpoint configuration and ensure that the lifecycle runtime service is running.

Cause: The lifecycle management endpoint may be misconfigured, or the lifecycle runtime service may not be running or is accessible.

Action: Ensure that the url and credential information of the lifecycle management endpoint is correct. Ensure also that the lifecycle runtime service is running and accessible from the Administration Server.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162743: An unexpected exception occurred trying to shut down server {0} in cluster {1}. {2}

Cause: An unexpected exception occurred.

Action: Check the server log for other messages for more details.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162744: An error occurred while trying to update size for cluster {0}. {2}

Cause: The configuration update failed. It may be due to several factors such as locked down configuration, timeouts, or another issue.

Action: Check the server log for other messages for more details.
Level: 1

Type: WARNING

Impact: Elasticity

BEA-2162745: {0}: An error occurred trying to scale cluster {1}. Scaling operation failed because there is another scaling activity occurring on cluster {1} .

Cause: The scaling operation failed because there is another scaling activity occurring on the same cluster.

Action: Initiate the scaling activity after the current activity finishes.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162746: {0}: An error occurred while trying to scale cluster {1}. Scaling operation failed because the cluster {1} is in cool-off period and cannot be scaled for another {2} seconds.

Cause: The scaling operation failed because the cluster cannot be scaled during the cool-off period.

Action: Initiate the scaling activity after the specified cool-off period.
Level: 1

Type: ERROR

Impact: Elasticity

BEA-2162747: {0}: Scale-up operation on cluster {1} started.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

BEA-2162748: {0}: Scale-down operation on cluster {1} started.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Elasticity

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

BEA-2164000: The specified partition "{0}" does not exist in the domain.

Cause: A partition needs to exist in the domain before deploying to it.

Action: Create the specified partition before deploying to it.
Level: 1

Type: WARNING

Impact: Deployer

BEA-2164001: Start and stop operations are not supported for resources at the resource group template level.

Cause: Start and stop operations are not supported for resources at the resource group template level.

Action: Start and stop resources at the referencing resource group level.
Level: 1

Type: WARNING

Impact: Deployer

BEA-2164002: The specified resource group "{0}" does not exist in the specified partition "{1}".

Cause: A resource group needs to exist before deploying to it.

Action: Create the specified resource group before deploying to it.
Level: 1

Type: WARNING

Impact: Deployer

BEA-2164003: The specified resource group template "{0}" does not exist in the domain.

Cause: A resource group template needs to exist before deploying to it.

Action: Create the specified resource group template before deploying to it.
Level: 1

Type: WARNING

Impact: Deployer

BEA-2164004: The resource group name cannot be derived in this case. Specify the resource group option along with the partition option.

Cause: A resource group option must be specified with the partition option in cases where it cannot be derived.

Action: Specify the resource group option with the partition option.
Level: 1

Type: WARNING

Impact: Deployer

BEA-2164005: A resource group template option cannot be specified with a resource group option.

Cause: A resource group template option and resource group option were specified together.

Action: Either specify the resource group template option or specify the resource group option.
Level: 1

Type: WARNING

Impact: Deployer

BEA-2164007: The specified resource group "{0}" does not exist in the domain.

Cause: A resource group needs to exist before you can deploy to it.

Action: Create the specified resource group before deploying to it.
Level: 1

Type: WARNING

Impact: Deployer

BEA-2164008: The override of the deployment plan was already removed.

Cause: The override of the plan cannot be removed because it was already removed.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Deployer

BEA-2164009: A resource group template option cannot be specified in a partition context.

Cause: A partition administrator cannot operate on a resource group template.

Action: Operate on a resource group template outside of the partition context.
Level: 1

Type: WARNING

Impact: Deployer

BEA-2164011: A resource group option cannot be specified in this operation.

Cause: A resource group option was specified but is not supported in this operation.

Action: Retry the operation without the resource group option.
Level: 1

Type: WARNING

Impact: Deployer

BEA-2164012: Unable to perform the {1} request for application "{0}". Either the application does not exist, or it is deployed to a resource group template referenced by resource group "{2}".

Cause: The application name was likely misspelled, or it is deployed to a resource group template but no resourceGroupTemplate option value was provided.

Action: Verify that the application is correctly named, or provide a resource group template name using the resourceGroupTemplate option if application is deployed to a resource group template, or remove the reference to the resource group template from the resource group.
Level: 1

Type: WARNING

Impact: Deployer

BEA-2164013: Unable to perform the {1} request for application "{0}". Operation cannot be performed until the server is restarted. Either the application does not exist, or it is deployed to a resource group template referenced by resource group "{2}".

Cause: The application name was either misspelled, was created after non-dynamic changes were activated, or it is deployed to a resource group template but no resourceGroupTemplate option value is provided. The server needed to be restarted.

Action: Verify that the application is correctly named, or provide a resource group template name using the resourceGroupTemplate option if the application is deployed to a resource group template, or remove the reference to the resource group template from the resource group. Then restart the server and start the application. In the future, start the application before making non-dynamic changes to the configuration.
Level: 1

Type: WARNING

Impact: Deployer

BEA-2164014: The deployment task "{0}" for application "{1}" was canceled.

Cause: The deployment task was canceled by the adminstrator or due to an error.

Action: No action is required if the the task was explicitly canceled.
Level: 1

Type: WARNING

Impact: Deployer

BEA-2164015: Application or library version must be specified during undeployments from a resource group template if more than one version exists.

Cause: It is not possible to find our the active version given a resource group template because the state of an application is defined in the context of a partition, not by a resource group template alone.

Action: If the intent it to undeploy the application or library from all partitions that refer to this resource group template, provide version information for this application or library.
Level: 1

Type: ERROR

Impact: Deployer

BEA-2164016: Cannot start an application which is in a shutdown partition {0} or resource group {1}.

Cause: An administrator is trying to start an application which is in a shutdown partition or resource group.

Action: An application will be started when the partition or resource group is started.
Level: 1

Type: WARNING

Impact: Deployer

BEA-2164017: Implicitly retiring {0} during managed server startup

Cause: A newer version of the application could have been deployed since this server was last booted

Action: No action needs to be taken
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-2164018: More than one non-retiring app ids found on server startup: {0}

Cause: The older version might not have been retired yet

Action: No action needs to be taken
Level: 1

Type: WARNING

Impact: Deployer

BEA-2164019: More than one retiring app ids found on server startup: {0}

Cause: A newer version of the application could have been deployed since this server was last booted

Action: More than one production redeploy might have been performed
Level: 1

Type: WARNING

Impact: Deployer

BEA-2164021: Application {0} is marked for retirement at {1} in future. This app will not be implicitly retired at this time {2}

Cause: The reiterment time is valid but set to some time in the future

Action: No action needs to be taken
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-2165000: Resource Consumption Management service initialization started.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165001: Resource Consumption Management service initialization completed.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165002: Resource Consumption Management resource class was not found. An error occurred during initialization: {0}

Cause: A resource class name was not found.

Action: Check the "config.xml" file. Verify the resource class name or the configuration.
Level: 1

Type: ERROR

Impact: RCM

BEA-2165003: Resource Consumption Management resource runtime MBean is not registered. An error occurred during initialization of runtime MBeans: {0}

Cause: There was an error while registering runtime MBeans.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: RCM

BEA-2165004: Trigger value is updated for an Resource Consumption Management resource.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165005: New trigger is added to an Resource Consumption Management resource.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165006: Trigger is removed for an Resource Consumption Management resource.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165007: Resource Consumption Management resource is added to Resource Manager.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165008: Resource Consumption Management Resource is removed from Resource Manager.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165009: Resource Consumption Management resource manager is added to Resource Management.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165010: Resource Consumption Management resource manager is removed from Resource Management.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165011: Resource Consumption Management resource manager is added to the partition.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165012: Resource Consumption Management resource manager is removed from the partition.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165013: Updating resource manager reference at the partition.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165014: Updating resource manager reference at the partition, moving current usage to the new resource manager.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165015: Trying to update a resource manager reference at the partition but can not proceed as Current Usage is more than the new value specified at the Trigger level.

Cause: Current Usage was more than the new value specified at the Trigger level.

Action: Increase the Trigger value for a shutdown or fail action.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165016: FairShare is removed for the Resource Consumption Management resource.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165017: New FairShare is added to the Resource Consumption Management resource.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165018: Resource Consumption Management Notification Withdraw Message: Notification action has been withdrawn because the quota has been reached below the given trigger value.

Cause: This is an informational message for a withdrawal notification action under Resource Consumption Management.

Action: This is a log message based on a "notify" trigger specified for the resource under Resource Consumption Management. If you want, you can â€¨use the WebLogic Diagnostic Framework(WLDF) to define different rules for this notification.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165019: "ResourceManagement" is not supported in this JDK. Use Oracle JDK 8u40 or later which supports "ResourceManagement", to use the WebLogic Server "Resource Consumption Management" feature.

Cause: "ResourceManagement" is not supported in the JDK used to start the WebLogic Server.

Action: Use Oracle JDK 8u40 or later.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165020: FairShare was updated to the Resource Consumption Management resource.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165021: "ResourceManagement" is not enabled in this JVM. Enable "ResourceManagement" to use the WebLogic Server "Resource Consumption Management" feature. To enable "ResourceManagement", you must specify the following JVM options in the WebLogic Server instance in which the JVM runs: -XX:+UnlockCommercialFeatures -XX:+ResourceManagement.

Cause: "ResourceManagement" is not enabled in this JVM.

Action: Enable "ResourceManagement" to use the WebLogic Server "Resource Consumption Management" feature.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165022: The process of creating the Resource Consumption Management Diagnostic Image has been timed out by the Diagnostic Framework. The resulting image may be incomplete.

Cause: The process of creating the Resource Consumption Management Diagnostic Image has been timed out by the Diagnostic Framework.

Action: Investigate the contents of the log and Diagnostic Images for more information.
Level: 1

Type: WARNING

Impact: RCM

BEA-2165023: Resource Consumption Management Fail Withdraw Message: Fail action has been withdrawn because the quota dropped below the given trigger value.

Cause: This is an informational message for a withdrawal fail action under Resource Consumption Management.

Action: This is a log message based on a fail trigger specified for the resource under Resource Consumption Management. If you want, you can use WebLogic Diagnostic Framework(WLDF) to define different rules for this notification.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165024: "ResourceManagement" is not supported in this JDK, but found a "Resource Consumption Management" policy configuration in the WebLogic Server for partition "{0}". Use Oracle JDK 8u40 or later which supports "ResourceManagement", to use the WebLogic Server "Resource Consumption Management" feature.

Cause: "ResourceManagement" is not supported in the JDK used to start the WebLogic Server.

Action: Use Oracle JDK 8u40 or later.
Level: 1

Type: INTERNAL_ERROR

Impact: RCM

BEA-2165025: "ResourceManagement" is not enabled in this JVM, but found a "Resource Consumption Management" policy configuration in the WebLogic Server for partition "{0}". Enable "ResourceManagement" to use the WebLogic Server "Resource Consumption Management" feature. To enable "ResourceManagement", you must specify the following JVM options in the WebLogic Server instance in which the JVM runs: -XX:+UnlockCommercialFeatures -XX:+ResourceManagement.

Cause: "ResourceManagement" is not enabled in this JVM.

Action: Enable "ResourceManagement" to use the WebLogic Server "Resource Consumption Management" feature.
Level: 1

Type: INTERNAL_ERROR

Impact: RCM

BEA-2165026: System Accounting flag is turned on. All resources consumed for performing System work by a Partition are tracked separately and not included in the Partition's resource consumption values. If there are any Resource Consumption Management Policies(Triggers) configured, they will not be accounting system context based resource consumption. Similarly, Partition Resource Metrics will not include system context based resource consumption.

Cause: This is an informational message.

Action: When "System Accounting" feature is enabled, Resource Consumption Management policies established for a Partition would not include the resources consumed for a Partition to execute System work. If the Resource Consumption Management policies established for a Partition must track all resources used for a Partition, disable the "System Accounting" feature.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165027: "Resource Consumption Management" policy for "Heap Retained" resource is defined in the WebLogic Server for partition "{0}". However "Heap Retained Metric" is not available in WebLogic Server.Resource Consumption Management" policy for "Heap Retained" resource can not be activated if "Heap Retained Metric" is not available. "Heap Retained Metric" is unavailable if "G1 Garbage Collector" is not enabled in the WebLogic Server JVM. Please enable "G1 Garbage Collector" to use "Heap Retained Metric" in WebLogic Server. To enable "G1 Garbage Collector", you must specify the following JVM options in the WebLogic Server instance in which the JVM runs: -XX:+UseG1GC.

Cause: "Heap Retained Metric" is not available in WebLogic Server but found a "Resource Consumption Management" policy configuration for "Heap Retained" resource in the WebLogic Server for partition "{0}"

Action: Enable "G1 Garbage Collector", Please specify the following JVM options in the WebLogic Server instance in which the JVM runs: -XX:+UseG1GC.
Level: 1

Type: INTERNAL_ERROR

Impact: RCM

BEA-2165028: "Heap Retained Metric" is not available in WebLogic Server."Resource Consumption Management" support for "Heap Retained" resource is not available. "Heap Retained" resource is available only with "G1 Garbage Collector".

Cause: "Heap Retained Metric" is not available in WebLogic Server.

Action: If "Resource Consumption Management" support for "Heap Retained" resource is needed , please enable "G1 Garbage Collector" by specifying the following JVM options in the WebLogic Server instance in which the JVM runs:-XX:+UseG1GC.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165029: Resource Consumption Management Restart Message: Given quota has been reached for the partition and a "restart" action has been executed.

Cause: Given quota for the resource under Resource Consumption Management was reached for the partition and a "restart" action was executed. The partition was restarted due to this action.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165030: Resource Consumption Management Restart Message: Partition has been restarted the maximum number of times as a result of resource consumption management "restart" action, in the duration, as specified in the partition config. Partition can not be restarted anymore, and is being shutdown.Partition would have to be started manually.

Cause: There are many attempts to "restart" the partition in configured duration.In order to prevent restart action going in a loop ,a "shutdown" action is executed.

Action: There are many attempts to "restart" the partition in configured duration. You can reconfigure max-restart-allowed and max-restart-allowed-interval with higher value if this is expected behaviour .
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165031: Resource Consumption Management : Partition restart is unsuccessful. It failed with an error : {0}

Cause: There was an error while restarting the partition.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: RCM

BEA-2165032: Restart Loop Protection updated for a Resource Consumption Management Resource Manager.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165799: Resource Consumption Management Notification Message: Given quota has been reached for the partition and a "notify" action has been executed.

Cause: Given quota for the resource under Resource Consumption Management was reached for the partition and a "notify" action was executed.

Action: This is a log message based on a "notify" trigger specified for the resource under Resource Consumption Management. If you want, you can use the WebLogic Diagnostic Framework(WLDF) to define different rules for this notification.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165800: Resource Consumption Management Slow Message: Given quota has been reached for the partition and a "slow" action has been executed.

Cause: Given quota for the resource under Resource Consumption Management was reached for the partition and a "slow" action was executed.The partition was slowed down due to this action.Once the resource consumption drops below the specified quota, partition would be un-slowed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165801: Resource Consumption Management Shutdown Message: Given quota has been reached for the partition and a "shutdown" action has been executed.

Cause: Given quota for the resource under Resource Consumption Management was reached for the partition and a "shutdown" action was executed. The partition was stopped due to this action.

Action: The partition has been stopped. Restart the partition manually. Use the Administration Console or WebLogic Diagnostic Framework(WLST) to start the partition.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165802: Resource Consumption Management Fail Message: Given quota has been reached for the partition and a "fail" action has been executed.

Cause: Given quota for the resource under Resource Consumption Management was reached for the partition and a "fail" action was executed. The resource consumption request failed due to this action.

Action: Reissue the request.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165803: Resource Consumption Management Un-slow Message: Slow action is "withdraw" as quota has been reached below the given trigger value.

Cause: Slow action was withdrew as quota reached below the given trigger value for the resource under Resource Consumption Management .

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RCM

BEA-2165804: Resource Consumption Management : Unable to successfully execute action {0}. It failed with an error : {1}

Cause: There was an error while executing the indicated action.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: RCM

BEA-2165805: Resource Consumption Management : Unable to successfully withdraw action {0}. It failed with an error : {1}

Cause: There was an error while withdrawing the indicated action.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: RCM

BEA-2166001: Message "{0}" Exception: {1}

Cause: This message displays output from the script.

Action: No action is required.
Level: 1

Type: ERROR

Impact: LCM

BEA-2166002: Exception Loading Plugins during LCM bootstrap: {0}

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

Action: Ensure LCM Plugins are in Plugin directory.
Level: 1

Type: ERROR

Impact: LCM

BEA-2166003: Exception getting the LCM Configuration File: {0}

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

Action: Ensure LCM Configuration file is present in Domain Config Directory.
Level: 1

Type: ERROR

Impact: LCM

BEA-2166004: Exception Setting up File Watcher for LCM Configuration File: {0}

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

Action: Ensure LCM Configuration file is present in Domain Config Directory.
Level: 1

Type: ERROR

Impact: LCM

BEA-2166005: Exception reloading LCM Configuration File: {0}

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

Action: Ensure LCM Configuration file is present in Domain Config Directory.
Level: 1

Type: ERROR

Impact: LCM

BEA-2166201: Could not shutdown server {0}

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

Action: Take appropriate action based on the details provided in the exception.
Level: 1

Type: ERROR

Impact: LCM_WLS_Plugin

BEA-2166202: Could not shutdown server {0}

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

Action: Take appropriate action based on the details provided in the exception.
Level: 1

Type: ERROR

Impact: LCM_WLS_Plugin

BEA-2166203: Could not get server mbean details for {0}

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

Action: Take appropriate action based on the details provided in the exception.
Level: 1

Type: ERROR

Impact: LCM_WLS_Plugin

BEA-2190000: {0} ERROR DATA recv on CLOSED messageId {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5}

Cause: Data was received after the message was closed.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190001: {0} ERROR DATA recv on zero messageId {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5}

Cause: Data was received with an illegal messageId.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190002: {0} ERROR INIT recv after INIT, releasing endpoint {1} peer: {2}/{3} local: {4}/{5}

Cause: An INIT was received after a previous INIT.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190003: {0} ERROR INIT recv frame too short {1}

Cause: An INIT frame was received that is not long enough.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190004: {0} ERROR INIT recv version mismatch {1} peer: {2}/{3} local: {4}/{5}

Cause: An INIT frame was received with version information that cannot be matched.

Action: Verify that the correct versions of all software are installed. If the problem persists, contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190005: {0} ERROR message received before connection initialized {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5}

Cause: A message was received before the connection was initialized.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190006: {0} ERROR recv message too short {1} bytes: {2}

Cause: A received message was too short.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190007: {0} START recv for existing messageId {1} flags: {2} subprotocol: {3} messageId: {4}

Cause: A START frame was received for an existing messageId.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190008: {0} ERROR ignoring START message received on endpoint in GRACEFUL_SHUTDOWN state {1} flags: {2} subprotocol: {3} messageId: {4} connectionState: {5}

Cause: A START frame was received but the endpoint is shutting down.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190009: {0} ERROR START recv on messageId zero {1} flags: {2} subprotocol: {3}

Cause: A START was received with an illegal messageId.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190010: {0} ERROR recv subprotocol mismatch {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5} subprotocol of previous message {6}

Cause: A message was received with a subprotocol that does not match the previous subprotocol for the same messageId.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190011: {0} ERROR recv unknown error code {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5} errorCode: {6}

Cause: A message was received with an unknown error code.

Action: Verify that the correct versions of all software are installed. If the problem persists, contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190012: {0} ERROR recv unknown frame type {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5}

Cause: A message was received with an unknown frame type.

Action: Verify that the correct versions of all software are installed. If the problem persists, contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190013: {0} ERROR INTERNAL open or close admin receiver threw exception (ignored) {1} adminReceiver: {2}

Cause: A BuzzAdminReceiver threw an exception in its #close or #open method (ignored).

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190014: {0} ERROR INTERNAL graceful shutdown ack received admin receiver threw exception (ignored) {1} adminReceiver: {2}

Cause: A BuzzAdminReceiver threw an exception in its #gracefulShutdown method (ignored).

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190015: {0} ERROR INTERNAL graceful shutdown ack admin receiver threw exception (ignored) {1} adminReceiver: {2}

Cause: A BuzzAdminReceiver threw an exception in its #gracefulShutdown method (ignored).

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190016: {0} ERROR INTERNAL connect or release receiver threw exception (ignored) {1} subprotocol: {2} subprotocolReceiver: {3} eventType: {4}

Cause: A BuzzSubprotocolReceiver threw an exception in its #connect or #release method (ignored).

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190017: {0} ERROR INTERNAL receipt receiver threw exception (ignored) {1} subprotocol: {2} subprotocolReceiver: {3} receiptCookie: {4}

Cause: A BuzzSubprotocolReceiver threw an exception in its #receipt method (ignored).

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190018: {0} ERROR INTERNAL backlog receiver threw exception (ignored) {1} subprotocol: {2} subprotocolReceiver: {3} isExcessive: {4}

Cause: A BuzzSubprotocolReceiver threw an exception in its #backlog method (ignored).

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190019: {0} ERROR INTERNAL graceful shutdown ack sent done receiver threw exception (ignored) {1} subprotocol: {2} subprotocolReceiver: {3}

Cause: A BuzzSubprotocolReceiver threw an exception in its #gracefulShutdown method (ignored).

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190020: {0} ERROR INTERNAL subprotocol receiver threw exception (ignored) {1} frameType: {2} flags: {3} subprotocol: {4} messageId {5} subprotocolReceiver: {6}

Cause: A BuzzSubprotocolReceiver threw an exception in its #receive method (ignored).

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190021: {0} ERROR INTERNAL graceful shutdown receiver threw exception (ignored) subprotocol: {1} subprotocolReceiver: {2} gracefulShutdownState: {3}

Cause: A BuzzSubprotocolReceiver threw an exception in its #gracefulShutdown method (ignored).

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190022: {0} ERROR INTERNAL subprotocol internal receiver threw exception (ignored) {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5} subprotocolReceiver: {6}

Cause: A BuzzSubprotocolReceiverInternalApi threw an exception in its #receiveRstInternal method (ignored).

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190023: {0} ERROR INTERNAL graceful shutdown internal receiver threw exception (ignored) {1} subprotocol: {2} errorCode: {3} subprotocolReceiver: {4}

Cause: A BuzzSubprotocolReceiverInternalApi threw an exception in its #receiveGsdInternal method (ignored).

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190024: {0} ERROR INTERNAL EventCollector exception (ignored) {1}

Cause: Collector.add threw an exception which will be ignored.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190025: {0} ERROR exception in tryRelase (ignored) {1} extra: msg

Cause: An exception occurred in TryRelease (ignored).

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190026: {0} ERROR INTERNAL POTENTIAL RDMA MEMORY LEAK no subprotocol receiver for receipt cookie {1} receiptCookie: {2}

Cause: There is no subprotocol receiver for the receipt cookie. This may be due to an RDMA memory leak.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190027: {0} ERROR INTERNAL incorrect event type in connect release receiver {1} eventType: {2}

Cause: There is an INTERNAL incorrect event type in the connect release receiver.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190028: {0} ERROR INTERNAL POTENTIAL RDMA MEMORY LEAK unknown receipt type {1} receiptCookie: {2}

Cause: An unknown receipt type was encountered. This may be due to an RDMA memory leak.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190029: {0} ERROR INTERNAL recv exception reading BufferSequenceInputStream {1} bytes: {2}

Cause: An exception occurred while reading BufferSequenceInputStream.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190030: {0} ERROR INTERNAL POTENTIAL RDMA MEMORY LEAK forceCloseIdAux message info is null {1} messageId {2}

Cause: INTERNAL MessageInfo is null. This may be due to an RDMA memory leak.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190031: {0} ERROR INTERNAL no ConnectionInfo {1}

Cause: No connection info was provided for the endpoint.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190032: {0} ERROR INTERNAL no epToMessageMap entry {1}

Cause: The epToMessageMap entry for the endPoint was missing.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190033: {0} ERROR INTERNAL recv no subprotocol receiver {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5}

Cause: No subprotocol receiver was provided for the messageId.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190034: {0} ERROR INIT INTERNAL recv connection in wrong state, should be CONNECTED {1} peer: {2}/{3} local: {4}/{5} connectionState: {6}

Cause: An INIT frame was received but the endpoint is in the wrong state.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190035: {0} ERROR INTERNAL INIT recv error ConnectionInfo should not be null {1}

Cause: An INTERNAL INIT was received but ConnectionInfo is null.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190036: {0} ERROR INTERNAL POTENTIAL RDMA MEMORY LEAK recv unknown messageId scope for RST {1} flags: {2} subprotocol: {3} messageId: {4} errorCode: {5}

Cause: An RST frame was received with an unknown messageId scope. This may be due to an RDMA memory leak.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190037: {0} ERROR INTERNAL send incorrect message state - should be HALF_CLOSED {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5} messageState: {6}

Cause: An attempt was made to send a message but the message is in an incorrect state.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190038: {0} ERROR INTERNAL send incorrect message state - should be OPEN {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5} messageState: {6}

Cause: An INTERNAL attempt was made to send a message but the message is in an incorrect state.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190039: {0} ERROR INTERNAL send existing endPoint to ConnectionInfo during INIT {1}

Cause: An error of type INTERNAL occurred during initialization.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190040: {0} ERROR INTERNAL send exception when sending RST {1} subprotocol: {2} messageId: {3} errorCode: {4} extra: {5}

Cause: An exception of type INTERNAL occurred when sending RST.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190041: {0} ERROR INTERNAL flush receiver threw exception (ignored) subprotocol: {1} subprotocolReceiver: {2}: {3}

Cause: A BuzzSubprotocolReceiver threw an exception in its #flush method (ignored).

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190042: {0} ERROR close time out extra: waited for {1} {2}

Cause: An internal close timeout occurred.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBus

BEA-2190043: Unexpected DummyBuzzChannel usage by App Container with stack trace: {0}.

Cause: There was an unexpected usage of DummyBuzzChannel by the Application Container.

Action: Contact My Oracle Support and provide them with the logs.
Level: 1

Type: WARNING

Impact: BuzzMessageBus

BEA-2190044: Buzz Message Bus is initialized at {0}.

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: BuzzMessageBus

BEA-2191000: {0} Invalid HTTP header length in Buzz frame: {1}

Cause: The HTTP header length in the Buzz frame is invalid.

Action: Contact My Oracle Support and provide them the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBusHttp

BEA-2191001: {0} Incomplete HTTP header in Buzz frame

Cause: The HTTP header in the Buzz frame is incomplete.

Action: Contact My Oracle Support and provide them the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBusHttp

BEA-2191002: {0} Invalid message type for HTTP BuzzSubprotocolHandler: {1}

Cause: The message type received by the HTTP BuzzSubprotocolHandler is invalid.

Action: Contact My Oracle Support and provide them the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBusHttp

BEA-2191003: {0} The BuzzSubprotocolRecieverHttpWLSImpl#receipt method should not be invoked. There may be a memory leak: {1}

Cause: The Http BuzzSubprotocolHandler encountered an internal receipt error.

Action: Contact My Oracle Support and provide them the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBusHttp

BEA-2191004: {0} Internal receive error in Http BuzzSubprotocolHandler: {1}

Cause: The Http BuzzSubprotocolHandler encountered an internal receive error.

Action: Contact My Oracle Support and provide them the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBusHttp

BEA-2191005: {0} A complete message could not be read on socket: '{1}', in the configured timeout period of '{2}' secs.

Cause: A complete HTTP message could not be read on the socket within the configured timeout.

Action: Contact My Oracle Support and provide them the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBusHttp

BEA-2191006: {0} BuzzSubprotocolRecieverHttpWLSImpl#closeYourId({1}) should not be invoked because WLS/Buzz/HTTP does not initiate messages.

Cause: BuzzSubprotocolRecieverHttpWLSImpl#closeYourId was invoked.

Action: Contact My Oracle Support and provide them the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: BuzzMessageBusHttp

BEA-2192000: Workflow {0} failed in step <{1}> during {2} operation without a specified reason. Requested resolution is {3}

Cause: {0}

Action: Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192001: Workflow {0} failed in step <{1}> during {2} operation. Requested resolution is {3}. Reason: {4}

Cause: {0} - {2}

Action: Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192002: Workflow {0} - the saved workflow is corrupted, there are missing work units.

Cause: The workflow could not be loaded properly from persistent storage.

Action: Review the server configuration or create a new workflow.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192003: Workflow {0} - the saved workflow is corrupted, checksum errors were detected.

Cause: The workflow could not be loaded properly from persistent storage.

Action: Review the server configuration or create a new workflow.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192004: Workflow {0} Running: {1} / {2}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MgmtOrchestration

BEA-2192005: Workflow {0} finished successfully. {1} steps completed.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MgmtOrchestration

BEA-2192006: Workflow {0} failed and the revert process has been initiated.

Cause: See getError for details of the failure.

Action: Allow the workflow to revert automatically, then diagnose the failure with the information reported by getError before attempting the process again.
Level: 1

Type: NOTIFICATION

Impact: MgmtOrchestration

BEA-2192007: Workflow {0} failed and the revert process was not initiated. The failure was: {1}

Cause: See getError for details of the failure.

Action: Diagnose the failure with the information reported by getError and address it.
Level: 1

Type: NOTIFICATION

Impact: MgmtOrchestration

BEA-2192008: Workflow {0} failed, the revert process was initiated and completed successfully. The failure that triggered the revert process was: {1}

Cause: See getError for details of the failure.

Action: Diagnose the failure with the informatipn reported by getError and address it. Then try running the procedure again.
Level: 1

Type: NOTIFICATION

Impact: MgmtOrchestration

BEA-2192009: Workflow {0} failed, the revert process was initiated, but it failed as well. The failure that triggered the revert process was: {1}

Cause: See getError for details of the cause.

Action: Review the cause details from getError and address the reported issue. The partial completion of this operation may have left affected targets in an inconsistent state.
Level: 1

Type: NOTIFICATION

Impact: MgmtOrchestration

BEA-2192010: Workflow {0} was canceled.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MgmtOrchestration

BEA-2192011: Workflow {0} cannot create directory to store workflow: {0}

Cause: The requested directory could not be created.

Action: Ensure that the parent directory is writable and the hard drive has sufficient free space.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192012: Workflow {0} could not delete a file during the workflow storage cleaning process. {1}

Cause: {1}

Action: Unlock the file and check the user's privileges.
Level: 1

Type: WARNING

Impact: MgmtOrchestration

BEA-2192013: Workflow {0} - found unexpected or invalid structures in the storage directory:{1}

Cause: This is usually caused by external changes to the directory contents.

Action: Create a new workflow for this procedure.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192014: Workflow {0} could not move the temporary workflow file ({0}) to the permanent destination ({1}).

Cause: The cause is unknown.

Action: Ensure that the parent directory is writable and that the temporary workflow file is writable. You will likely need to start a new workflow for this procedure.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192015: Workflow {0} is starting the revert process.

Cause: There was a previously reported error with the workflow and the revert process is starting.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MgmtOrchestration

BEA-2192016: Workflow {0} is already completed and cannot be started again.

Cause: You attempted to start a completed workflow.

Action: To run the process again, start a new workflow.
Level: 1

Type: WARNING

Impact: MgmtOrchestration

BEA-2192017: Workflow {0} is already running.

Cause: You attempted to start a running workflow.

Action: No action is required.
Level: 1

Type: WARNING

Impact: MgmtOrchestration

BEA-2192018: Could not delete a file or directory: {0}

Cause: Either the file is locked or the user has insufficient privileges.

Action: Unlock the file and check the user's privileges.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192019: Workflow {0} is not running, so it cannot be canceled.

Cause: Only a running workflow can be canceled.

Action: No action is required.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192034: {0} {1} {2}-{3} (duration: {4})

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: MgmtOrchestration

BEA-2192035: {0} {1} {2}-{3} (duration: {4}) - ERROR {5}

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: MgmtOrchestration

BEA-2192036: {0} {1} {2}-{3} (duration: {4}) - ERROR Unknown error

Cause: See the message body.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: MgmtOrchestration

BEA-2192037: Failure performing {1} of {0}

Cause: See the cause of the exception.

Action: Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details.
Level: 1

Type: WARNING

Impact: MgmtOrchestration

BEA-2192038: Workflow {0} was never executed. Cannot revert.

Cause: You attempted to revert a new workflow.

Action: This operation is valid only for stopped workflows, not for completed but already executed workflows, for example, failed workflows.
Level: 1

Type: WARNING

Impact: MgmtOrchestration

BEA-2192039: Service is blocked. It was used too early or was not used on the Administration Server.

Cause: The server is not in a state where the orchestration framework can act.

Action: Check the status of the Administration Server.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192040: Workflow instance {0} is running. Cannot delete.

Cause: A running workflow instance cannot be deleted.

Action: Wait for the workflow to complete.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192041: It is not possible to execute the workflow instance in its current state.

Cause: The current state of the workflow is not compatible with this operation.

Action: Check the state of the workflow instance.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192042: It is not possible to revert the workflow instance in its current state.

Cause: The current state of the workflow is not compatible with this operation.

Action: Check the state of the workflow instance.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192043: Cannot execute the workflow instance. Not all required shared state objects are defined. ({0})

Cause: The workflow instance cannot be constructed because of missing shared state objects.

Action: Ensure that you have defined all necessary attributes.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192044: Failure performing {1} of {0}, caused by {2}

Cause: See the cause of the exception.

Action: Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details.
Level: 1

Type: WARNING

Impact: MgmtOrchestration

BEA-2192045: Debug Message: {0}

Cause: Used for capturing debug information during testing.

Action: No action is required.
Level: 1

Type: WARNING

Impact: MgmtOrchestration

BEA-2192046: Workflow {0} failed in step <{1}> during {2} operation. Requested resolution is {3}. Reason: {4}

Cause: {0} - {2}

Action: Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192047: Workflow {0} failed to store step <{1}> during {2} operation. Reason: {4}

Cause: {0} - {2}

Action: Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192048: Unable to load stored progress object of type: {0} from {1} due to {2}.

Cause: {0} - {2}

Action: Check that the file store is still valid and that the workflow information is not lost.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192049: Unable to initialize progress object from persistence: {0} due to {1}.

Cause: {0} - {1}

Action: Check that the file store is still valid and that the workflow information is not lost.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192050: Error initializing progress for workflow {0} from path {1}, due to {2}.

Cause: {2}

Action: Check that the file store is still valid and that the workflow information is not lost.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192051: Error starting workflow {0}, due to {1}.

Cause: {1}

Action: Check the exception that caused the failure for more information.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192052: Error setting type {1} on workflow {0}, {2}.

Cause: {2}

Action: Check the exception that caused the failure for more information.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192053: Error setting target type {1} on workflow {0}, {2}.

Cause: {2}

Action: Check the exception that caused the failure for more information.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192054: Error setting target {1} on workflow {0}, {2}.

Cause: {2}

Action: Check the exception that caused the failure for more information.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192055: Error cleaning up workflows on Partition {0} deletion.

Cause: {1}

Action: Check the exception that caused the failure for more information.
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192056: Unable to get workflow for Partition {0} and workflowid {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: MgmtOrchestration

BEA-2192057: Unable to delete workflowfiles for for Partition {0} and workflowid {1} as workflow was in state {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: MgmtOrchestration

BEA-2192058: Found a workflow with state = null for Partition {0} and workflowid {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: MgmtOrchestration

BEA-2192059: Error attempting to create workflow orchestration directory {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: MgmtOrchestration

BEA-2192100: Script "{0}" output: {1}

Cause: This message displays output from the script.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Patching

BEA-2192101: Timeout polling ready application URL for server: {0}.

Cause: The system failed to perform a ready check on applications within the stipulated time.

Action: Check the server log to determine which applications or applications failed to load. You may need to increase the readyCheckAppsTimeoutInMin value depending on how long the application or applications take to load.
Level: 1

Type: ERROR

Impact: Patching

BEA-2192102: Failed to construct URL for server: {0}.

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

Action: Take appropriate action based on the details provided in the exception.
Level: 1

Type: ERROR

Impact: Patching

BEA-2192103: Error opening URL.

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

Action: Take appropriate action based on the details provided in the exception.
Level: 1

Type: ERROR

Impact: Patching

BEA-2192104: Failed to get ServerLifeCycleRuntimeMBean for server {0}

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

Action: Take appropriate action based on the details provided in the exception.
Level: 1

Type: ERROR

Impact: Patching

BEA-2192105: Server lifecycle operation error for server {0}: {1}

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

Action: Take appropriate action based on the details provided in the exception.
Level: 1

Type: ERROR

Impact: Patching

BEA-2192106: Cannot unregister deleted MBean: {0}

Cause: A workflow was deleted but it was not possible to unregister the relevant MBean.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Patching

BEA-2192107: Workflow {0} is executing {1} on {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Patching

BEA-2192108: Workflow {0} is retyring {1} on {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Patching

BEA-2192109: Workflow {0} is reverting {1} on {2}.

Cause: This is an informational message.

Action: No action isrequired.
Level: 1

Type: NOTIFICATION

Impact: Patching

BEA-2192110: Workflow {0} successfully completed {1} on {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Patching

BEA-2192111: Workflow {0} successfully completed revert of {1} on {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Patching

BEA-2192112: Workflow {0} failed to complete {1} on {2}.

Cause: Use getError for details of the failure.

Action: Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details and take appropriate action.
Level: 1

Type: NOTIFICATION

Impact: Patching

BEA-2192113: Workflow {0} failed to complete {1} on {2} due to error {3}.

Cause: Use getError for details of the failure.

Action: Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details and take appropriate action.
Level: 1

Type: NOTIFICATION

Impact: Patching

BEA-2192114: Workflow {0} failed to revert {1} on {2}.

Cause: See the log for details of the failure.

Action: Review the cause details from getError and address the reported issue. The partial completion of this operation may have left affected targets in an inconsistent state.
Level: 1

Type: NOTIFICATION

Impact: Patching

BEA-2192115: Workflow {0} failed to revert {1} on {2} due to error {3}.

Cause: See the log for details of the failure.

Action: Review the cause details from getError and address the reported issue. The partial completion of this operation may have left affected targets in an inconsistent state.
Level: 1

Type: NOTIFICATION

Impact: Patching

BEA-2192116: Unable to enable session handling features on restarted server: {0}.

Cause: See the log for details of the failure.

Action: Review the cause and address the reported issue. The partial completion of this operation may have left affected targets in an inconsistent state.
Level: 1

Type: WARNING

Impact: Patching

BEA-2192117: Targeted application redeploy for "{0}" on server "{1}" during patching failed with an exception {2}.

Cause: See the log for details about the cause of the failure.

Action: Review the cause in the logs and address the reported issue. The partial completion of this operation may have left affected targets in an inconsistent state.
Level: 1

Type: ERROR

Impact: Patching

BEA-2192118: Workflow {0} skipped {1} on {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Patching

BEA-2192119: The user path input "{0}" was translated to "{1}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Patching

BEA-2192120: Error using the NodeManager to verify local paths on machine {0}. The last lines of script output (full script output in the log): {1}.

Cause: This is usually caused by a file not being found at the specified path.

Action: Confirm that the specified paths are correct.
Level: 1

Type: ERROR

Impact: Patching

BEA-2192121: Error from ZDT agent invocation on node manager: [{0}] Message: {1}

Cause: Operation failed while executing on node manager.

Action: Review the cause based on the error message.
Level: 1

Type: ERROR

Impact: Patching

BEA-2192122: Warning from ZDT agent invocation on node manager: [{0}] Message: {1}

Cause: Warning generated while executing on node manager.

Action: Review the warning message.
Level: 1

Type: WARNING

Impact: Patching

BEA-2192123: Info from ZDT agent invocation on node manager: [{0}] Message: {1}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Patching

BEA-2192124: Info message from ZDT agent local invocation: {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Patching

BEA-2192125: Warning message from ZDT agent local invocation: {0}

Cause: Warning generated while executing ZDT agent.

Action: Review the warning message.
Level: 1

Type: WARNING

Impact: Patching

BEA-2192126: Error message from ZDT agent local invocation: {0}

Cause: Operation failed while executing ZDT agent.

Action: Review the cause based on the error message.
Level: 1

Type: ERROR

Impact: Patching

BEA-2192127: Exception message from ZDT agent local invocation: {0}

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

Action: Take appropriate action based on the details provided in the exception.
Level: 1

Type: ERROR

Impact: Patching

BEA-2192128: Targeted application redeploy for "{0}" on partition "{1}"on server "{2}" during patching failed with an exception {3}.

Cause: See the log for details about the cause of the failure.

Action: Review the cause in the logs and address the reported issue. The partial completion of this operation may have left affected targets in an inconsistent state.
Level: 1

Type: ERROR

Impact: Patching

BEA-2192129: Rollout is being started on Coherence cluster "{0}" , but the cluster has only 2 managed servers or 2 machines. This can lead to probable data loss if during the rollout, the other server which is running fails.

Cause: There are only 2 managed server belonging to the Coherence cluster.

Action: The Coherence cluster must have atleast 3 managed servers, ideally belonging to 3 different machines, to prevent data loss during rollout.
Level: 1

Type: WARNING

Impact: Patching

BEA-2192130: ElasticitySyncCounter.loadCounterFromDisk caught an exception while trying to load persisted counter file from disk at [{0}]. Message: {1}

Cause: An exception occurred while trying to load persisted file from disk

Action: Review the cause in the logs and address the reported issue. The Elasticity service may remain enabled and affect the rollout operation.
Level: 1

Type: WARNING

Impact: Patching

BEA-2192300: The partition lifecycle operation "{0}" failed for partition "{1}".

Cause: The partition lifecycle operation "{0}" failed for partition "{1}" with exception "{2}".

Action: Try restarting the partition.
Level: 1

Type: ERROR

Impact: Partition Lifecycle

BEA-2192301: The resource group lifecycle operation "{0}" failed for resourceGroupName "{2}" of partition "{1}".

Cause: The resource group lifecycle operation "{0}" failed for resourceGroupName "{2}" of partition "{1}" with exception "{2}".

Action: Try restarting the resource group
Level: 1

Type: ERROR

Impact: Partition Lifecycle

BEA-2192302: The partition lifecycle operation "{0}" failed for partition "{1}".

Cause: The partition lifecycle operation "{0}" failed for partition "{1}" with exception "{2}".

Action: Check whether the targets for partition "{1}" are running.
Level: 1

Type: ERROR

Impact: Partition Lifecycle

BEA-2192303: The partition lifecycle operation "{0}" for partition "{1}" is initiated.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192304: The partition lifecycle operation "{0}" for partition "{1}" was successful.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192305: The partition lifecycle operation "{0}" for the untargeted partition "{1}" was successful.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192306: The resource group lifecycle operation "{0}" for resourceGroupName "{2}" of partition "{1}" was initiated.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192307: The resource group lifecycle operation "{0}" for resourceGroupName "{2}" of partition "{1}" was successful.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192308: The resource group lifecycle operation "{0}" for untargeted resourceGroupName "{2}" of partition "{1}" was successful.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192309: The partition "{0}" is already in the "{1}" state.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192310: The resource group "{0}" of partition "{1}" is already in the "{2}" state.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192311: The partition lifecycle operation "{1}" is in progress for partition "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Partition Lifecycle

BEA-2192312: The resource group lifecycle operation "{2}" for resource group "{0}" belonging to partition "{1}" is in progress.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Partition Lifecycle

BEA-2192313: The partition lifecycle operation "{1}" on partition "{0}" is incompatible with the current state "{2}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Partition Lifecycle

BEA-2192314: The resource group lifecycle operation "{2}" for resource group "{0}" belonging to partition "{1}" is incompatible with the current state "{3}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Partition Lifecycle

BEA-2192315: The partition operation "{1}" for partition "{0}" failed with exception "{2}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Partition Lifecycle

BEA-2192316: Performing an automatic HALT on partition "{1}" after operation "{0}" because there are no targeted active admin resource groups.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192317: Skipping BOOT for partition "{0}" because there are no targeted active admin resource groups.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192318: Graceful operation "{0}" on partition "{1}" timed out; converting to "{2}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192319: Partition lifecycle operation "{0}" initiated using partitionLifeCycleRuntimeMbean for partition "{1}" on servers "{2}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192320: The status of partition lifecycle sub task "{0}" for partition "{1}" is "{2}" on server "{3}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192321: The partition lifecycle sub task "{0}" for partition "{1}" failed on server "{2}" with exception "{3}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Partition Lifecycle

BEA-2192322: The status of partition lifecycle task "{0}" for partition "{1}" is "{2}" on servers "{3}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192323: The partition lifecycle task "{0}" for partition "{1}" failed with exception "{2}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Partition Lifecycle

BEA-2192324: The partition lifecycle operation "{0}" for the partition "{1}" is a no-op since the partition is already in expected state "{2}" in all the targeted servers

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192325: The resource group lifecycle operation "{0}" for the resource group "{1}" is a no-op since the resource group is already in expected state "{2}" in all the targeted servers

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192326: Resource group lifecycle operation "{0}" initiated using resourceGroupLifeCycleRuntimeMbean for resource group "{1}" on servers "{2}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192327: The status of resource group lifecycle sub task "{0}" for resource group "{1}" is "{2}" on server "{3}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192328: The resource group lifecycle sub task "{0}" for resource group "{1}" failed on server "{2}" with exception "{3}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Partition Lifecycle

BEA-2192329: The status of resource group lifecycle task "{0}" for resource group "{1}" is "{2}" on servers "{3}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192330: The resource group lifecycle task "{0}" for resource group "{1}" failed with exception "{2}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Partition Lifecycle

BEA-2192331: A partition forceRestart operation halted the partition "{0}" on this server but the corresponding runtime MBean remains.

Cause: This is a warning message.

Action: Monitor the system for unexpected behavior of the partition on this server.
Level: 1

Type: WARNING

Impact: Partition Lifecycle

BEA-2192332: Partition "{0}" is in state "{2}". The resource group "{1}" can not be transitioned to "{3}" state.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192333: Performing an automatic HALT on partition "{1}" after operation "{0}" because SHUTDOWN_TO_HALTED flag is True.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Partition Lifecycle

BEA-2192334: An inconsistent state "{0}" and substate "{1}" were found; continuing with substate "{2}".

Cause: The system uses separate remote messages to obtain the state and substate of a partition on a remote server. If between those two messages the state of the server or partition changes or the underlying network connection falters, the retrieved state and substate might be inconsistent with each other.

Action: Make sure that the system actions following the substate substitution are what was intended.
Level: 1

Type: WARNING

Impact: Partition Lifecycle

BEA-2192400: JAX-RS OWSM configuration may not work: {0}

Cause: This problem may be caused by an incorrect WebLogic class path.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JAXRSClient

BEA-2192500: Application MBean not initialized for application '{0}'.

Cause: The application was destroyed.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JAXRSIntegration

BEA-2192501: Cannot find URI for {0} resource class.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JAXRSIntegration

BEA-2192502: Do not call JaxRsApplicationRuntimeMBean.setApplicationEnabled(boolean).

Cause: This is an informational message. This is a deprecated API with no replacement.

Action: Enable 'DebugRestJersey2Integration' to get the caller stack trace.
Level: 1

Type: NOTIFICATION

Impact: JAXRSIntegration

BEA-2192503: InitialContext not found. JAX-RS EJB support is not available.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: ERROR

Impact: JAXRSIntegration

BEA-2192504: EJB component provider has not been initialized properly.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: ERROR

Impact: JAXRSIntegration

BEA-2192505: An instance of EJB class {0} could not be looked up using a simple form name. Attempting to look up using the fully-qualified form name.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JAXRSIntegration

BEA-2192506: Exception thrown when trying to look up actual handling method {0} for EJB type {1} using interface {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JAXRSIntegration

BEA-2192507: Class {0} has been bound by Jersey EJB component provider.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JAXRSIntegration

BEA-2192508: The failure was: {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: ERROR

Impact: JAXRSIntegration

BEA-2192509: Changing servlet class from {0} (web.xml) to {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JAXRSIntegration

BEA-2192510: Cannot add Jersey servlet for application class {0} because ApplicationPath annotation is not set on it.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JAXRSIntegration

BEA-2192511: The list of resource packages: {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JAXRSIntegration

BEA-2194500: Initializing a Coherence cluster scoped to classloader {0} using {1}

Cause: Initializing a Coherence cluster scoped to classloader {0} using {1}

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CoherenceIntegration

BEA-2194501: 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: CoherenceIntegration

BEA-2194502: 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: CoherenceIntegration

BEA-2194503: 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: CoherenceIntegration

BEA-2194504: Deployed a GAR ({0}) without a CoherenceClusterSystemResourceMBean definition on this server. In most of the scenarios, a Coherence cluster must be created for applications to work properly.

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. Only in some special cases, for example using Coherence Extend with TCMP disabled, a Coherence cluster may not be associated with a managed server.
Level: 1

Type: WARNING

Impact: CoherenceIntegration

BEA-2194505: Server {0} is configured with 'localhost' as the Unicast Listen Address. A generated Coherence WKA list will not operate correctly across multiple machines. This will result in an error if Coherence is run in Production mode.

Cause: Server {0} is configured with 'localhost' as the Unicast Listen Address. When using Coherence WKA and not explicitly defining a WKA list, the configuration may not operate correctly across multiple machines. This will result in an error if Coherence is run in Production mode.

Action: Explicitly define a Well Known Address (WKA) list for the Coherence cluster.
Level: 1

Type: WARNING

Impact: CoherenceIntegration

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

Cause: The JNDI resource [{0}] referenced by {1} could not be found.

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

Type: WARNING

Impact: CoherenceIntegration

BEA-2194507: The Coherence cluster service failed to start or failed to join cluster due to {0} using {1}.

Cause: The Coherence cluster service failed to start or failed to join cluster due to {0} using {1}.

Action: Review the Coherence configuration for the cause of the exception.
Level: 1

Type: ERROR

Impact: CoherenceIntegration

BEA-2194508: Coherence configuration failed due to {0} using {1}.

Cause: The Coherence configuration failed due to {0} using {1}.

Action: Review the Coherence configuration for the cause of the exception.
Level: 1

Type: WARNING

Impact: CoherenceIntegration

BEA-2194509: The WeblogicCoherenceBean and CoherenceClusterParamsBean are not defined for the CoherenceClusterSystemResourceMBean {0}.

Cause: The CohererenceClusterSystemResourceBean {0} needs to have an association with valid WeblogicCoherence and CoherenceCluster Beans.

Action: Create a CoherenceClusterSystemResource MBean with the required associations.
Level: 1

Type: WARNING

Impact: CoherenceIntegration

BEA-2194510: While configuring the Coherence Cluster Service, the Server MBean or Server CoherenceMemberConfig MBean or both were not defined.

Cause: The Server MBean or Server CoherenceMemberConfig MBean or both were not defined and thus will not be used when configuring the Coherence Cluster Service.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CoherenceIntegration

BEA-2194511: Server {0} is configured with 'localhost' as the Unicast Listen Address which is an error in Coherence Production mode. A generated Coherence WKA list will not operate correctly across multiple machines.

Cause: Server {0} is configured with 'localhost' as the Unicast Listen Address resulting in an error when Coherence is in Production mode. When using Coherence WKA and not explicitly defining a WKA list, the configuration may not operate correctly across multiple machines.

Action: Explicitly define a Well Known Address (WKA) list for the Coherence cluster.
Level: 1

Type: ERROR

Impact: CoherenceIntegration

BEA-2194512: While undeploying a GAR, the deployment module received an exception when closing files {0}.

Cause: While undeploying a GAR, one or more files could not be closed due to {0}.

Action: Review the exception and determine if there any file system issues for the referenced files.
Level: 1

Type: WARNING

Impact: CoherenceIntegration

BEA-2194513: Deployed an application ({0}) with Coherence*Web as session persistence type without a CoherenceClusterSystemResourceMBean definition on this server. Typically, a Coherence cluster must be created for this scenario to work properly.

Cause: Deployed an application ({0}) with Coherence*Web as session persistence type 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. Only in some special cases, for example using Coherence Extend with TCMP disabled, a Coherence cluster may not be associated with a managed server.
Level: 1

Type: NOTIFICATION

Impact: CoherenceIntegration

BEA-2194514: There was an error creating Timer Manager for the Managed Server Level Coherence*Web Session Reaping Manager.

Cause: TBD

Action: TBD
Level: 1

Type: NOTIFICATION

Impact: CoherenceIntegration

BEA-2194515: There was an error during the Session Reaping process of the Coherence*Web Session Reaping Manager.

Cause: TBD

Action: TBD
Level: 1

Type: NOTIFICATION

Impact: CoherenceIntegration

BEA-2194801: The archive file name {0} specified for importPartition is null

Cause: This is an internal WebLogic Server error.

Action: Specify a valid archive file for importPartition
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194802: Partition name cannot be null, please specify a partition name.

Cause: This is an internal WebLogic Server error.

Action: Specify a name for the partition
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194803: A Path Service targeted to a cluster requires High Availability Policies set on that Cluster, so MigrationBasis must be set in the Cluster "{0}". If database is chosen as MigrationBasis, then DataSourceForAutomaticMigration must be set. When consensus leasing is chosen as MigrationBasis, all servers that belong to the cluster must have a machine set and node manager configured for that machine.

Cause: This is an internal WebLogic Server error.

Action: Configure the High Availability Policies for the Cluster "{0}".
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194804: A domain partition with the name "{0}" already exists. Please specify a name for the partition which is not already configured in the given domain.

Cause: This is an internal WebLogic Server error.

Action: Specify a name for the domain partition which is not already configured.
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194805: The domain archive "{0}" is empty, specify a valid domain archive for import operation.

Cause: This is an internal WebLogic Server error.

Action: Specify a valid domain archive for import operation.
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194806: The domain archive "{0}" and/or the associated json file is not compatible with the current version of importPartition. Please generate the archive using the current Domain To Partition Conversion Tool. If the generated json file is modified to remove the resource-group entries please correct it.

Cause: This is an internal WebLogic Server error.

Action: Supply a compatible domain archive for import partition operation.
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194807: Cannot find realm "{0}" in the domain configuration.

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194808: The exiting virtual-target {0} is not for target {1}.

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194809: Cannot create a virtual target with the name "{0}" as the server "{1}" is a member of the cluster "{2}"!

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194810: Cannot add "{0}" to available targets of the domain partition as the server "{1}" is a member of the cluster "{2}".

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194811: The target "{0}" of virtual-target "{1}" does not exist in the target domain.

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194812: Cannot find Virtual Target "{0}" to add as an available target.

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194813: Cannot find Virtual Target "{0}" to add as the default target.

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194814: Virtual Target with the name "{0}" is not available, to set as target for the resource group "{1}"!

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194815: Virtual Target with the name "{0}" is not one of the available targets in the partition "{1}"!

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194816: Resource Group Template "{0}" already exists in the domain.

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194817: JMS Server "{0}" is referencing a persistence store "{1}" with distribution policy 'Singleton', as it is hosting one or more standalone destinations. However the same persistence store is referenced by SAF Agent "{2}", which requires the persistence store to have distribution policy 'Distributed'. This conflict is not allowed, so JMS Server and SAF Agent should not refer the same persistence store.

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194818: The "{0}" element in the json generated by the Domain TO Partition Conversion Tool is not an JSON Array. If the json file is modified before import, please correct the issue and try import again.

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194819: Cannot add the Virtual Target "{0}" to available targets of the domain partition as the server "{1}" is a member of the cluster "{2}".

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194820: The destination for writing the imported application "{0}" already exists at {1}.

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194821: The imported zip file does not contain the application plan at "{0}".

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194822: The imported zip file does not contain the application/library source at "{0}".

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194823: The destination for writing the imported plan for application "{0}" already exists at {1}.

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: DomainToPartition

BEA-2194824: Import of "{1}" of type "{0}" is excluded in the json file, an excluded resource won't be available in the partition.

Cause: The resource is excluded in the json file generated by Domain To Partition Conversion Tool, before importing to the partition.

Action: Manually configure the resource appropriately.
Level: 1

Type: NOTIFICATION

Impact: DomainToPartition

BEA-2194825: Partition "{0}" already contains a default target with the name "{1}".

Cause: TBD

Action: TBD
Level: 1

Type: NOTIFICATION

Impact: DomainToPartition

BEA-2194826: Cannot find/set JDBCStore "{0}" to JMS Server "{1}".

Cause: TBD

Action: TBD
Level: 1

Type: NOTIFICATION

Impact: DomainToPartition

BEA-2194827: Removing the target "{1}" from the subdeployment "{0}", to retain the first target for the subdeployment.

Cause: TBD

Action: TBD
Level: 1

Type: NOTIFICATION

Impact: DomainToPartition

BEA-2194828: Modifying the distribution policy to 'Singleton' and the migration policy to 'Always' of the persistent store "{0}" referenced by the Path Service "{1}".

Cause: TBD

Action: TBD
Level: 1

Type: NOTIFICATION

Impact: DomainToPartition

BEA-2194829: Path Service "{0}" in the source domain was pointing to default store. So creating a file store with the name "{1}" under Resource Group / Resource Group Template "{2}" as a path service without a valid store is not supported in a partitioned environment.

Cause: TBD

Action: TBD
Level: 1

Type: NOTIFICATION

Impact: DomainToPartition

BEA-2194830: The importPartition operation failed to create the report.

Cause: TBD

Action: TBD
Level: 1

Type: NOTIFICATION

Impact: DomainToPartition

BEA-2194831: The importPartition operation completed.

Cause: TBD

Action: TBD
Level: 1

Type: NOTIFICATION

Impact: DomainToPartition

BEA-2194832: The activation of importPartition failed with the error - {0}

Cause: TBD

Action: TBD
Level: 1

Type: NOTIFICATION

Impact: DomainToPartition

BEA-2194833: Error creating the JDBC Store "{0}", cannot find and set JDBC SystemResource "{1}"

Cause: TBD

Action: TBD
Level: 1

Type: WARNING

Impact: DomainToPartition

BEA-2194834: The JDBC Store "{0}" in the source domain does not have an associated JDBC System Resource. So this JDBC Store won't be created in the target domain partition. Any reference to this JDBC Store by a JMS Server or a SAF Agent or a Path Service will result in a validation exception due to unresolved reference in the configuration (config.xml).

Cause: TBD

Action: TBD
Level: 1

Type: WARNING

Impact: DomainToPartition

BEA-2194835: The Uniform Distributed Topic "{0}" in JMS Module "{1}" is configured to use the forwarding policy 'Replicated'(the default). This configuration is not supported when importing this domain to a partition, so the forwarding policy will be changed to 'Partitioned'.

Cause: TBD

Action: TBD
Level: 1

Type: WARNING

Impact: DomainToPartition

BEA-2194836: The subdeployment "{0}" in JMS Module "{1}" is targeted to "{2}" of type "{3}". This configuration is not supported. Subdeployments when not targeted to a JMS Server or a SAF Agent, will be left untargeted and any resources that reference that subdeployment will not be deployed.

Cause: TBD

Action: TBD
Level: 1

Type: WARNING

Impact: DomainToPartition

BEA-2194837: The subdeployment "{0}" in JMS Module "{1}" is targeted to "{2}" of type "{3}" and "{2}" is associated with a specific server in cluster "{4}" via a target of "{5}" of type "{6}". Partition scoped JMS destinations do not support targeting a particular Server or Migratable Target, so, after import, this subdeployment will be targeted to a JMS Server or a SAF Agent with an effective target of a Cluster, the destination runtime will therefore be hosted on a single random server in the cluster, or across all members of the cluster depending on its distribution policy and the server hosting the destination may change after failures or restarts.

Cause: TBD

Action: TBD
Level: 1

Type: WARNING

Impact: DomainToPartition

BEA-2194838: The subdeployment "{0}" in JMS module "{1}" does not have any valid target. After import, any JMS destination that refer this subdeployment will not be deployed.

Cause: TBD

Action: TBD
Level: 1

Type: WARNING

Impact: DomainToPartition

BEA-2194839: Unable to undo the changes which are not activated. Cause: {0}

Cause: TBD

Action: TBD
Level: 1

Type: WARNING

Impact: DomainToPartition

8 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

9 CAPTURE-10000 to CAPTURE-10151

CAPTURE-10000: Initializing Capture

Cause: The capture application is starting.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

CAPTURE-10001: Error creating Batch Item

Cause: The user tried adding an item to the batch.

Action: Make sure there is no problem accessing the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10002: Error committing documents

Cause: There was a problem updating the commited column of the document record.

Action: Make sure the database is accessible and that the user has proper permission to the database tables.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10003: Error creating workspace

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10004: Error updating workspace

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10005: Error deleting workspace

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10006: Error loading workspaces

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10007: Error creating index definition

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10008: Error loading index definitions

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10009: Error updating index definition

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10010: Error deleting index definition

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10011: Error locating capture object

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10012: Error locating capture object children

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10013: Error loading capture objects

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10014: Error creating batch

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10015: Error updating batch

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10016: The batch lock is no longer valid

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: NOTIFICATION

Impact: Other

CAPTURE-10017: Error deleting batch

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10018: Error finding batch by id

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10019: Error finding batch item by id

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10020: Error loading batches

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10021: Error loading batches by user and workstation

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10022: Error loading batches by user

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10023: Error loading locked batches by user

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10024: Error loading locked batches by workstation

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10025: Error loading locked batches by user and workstation

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10026: Error loading batch items

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10027: Error deleting batch item

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10028: The batch is already locked by ?1 on workstation ?2

Cause: The batch is locked by another user

Action: The batch must be unlocked before it can be locked by somone else
Level: 1

Type: NOTIFICATION

Impact: Other

CAPTURE-10029: Error locking batch

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10030: The specified batch has not been persisted or has been deleted by another user.

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: NOTIFICATION

Impact: Other

CAPTURE-10031: Error unlocking batch

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10032: Error creating batch name

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10033: Error creating document

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10034: Error creating db return field

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10035: Error creating db search field

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10036: Error creating db search profile

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10037: Error loading documents

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10038: Error deleting document

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10039: Error loading documents

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10040: Error linking item to document

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10041: Error unlinking item from document

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10042: Error locating datasource

Cause: The data source could not be found

Action: Ensure the database connection is configured properly and the database is accessible
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10043: Error generating batch id

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10044: Error creating log record

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10045: Error updating capture object

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10046: Error saving database search profile

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10047: Error deleting object child entities

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10048: Error deleting capture object entity

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10049: Error loading search profile

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10050: Error loading search profiles

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10051: Error deleting search profile

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10052: Error loading search fields

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10053: Error loading return fields

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10054: Error deleting return field

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10055: Error deleting search field

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10056: Error saving search field

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10057: Error saving return field

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10058: Error loading database schemas

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

Cause: Database permission issue

Action: Ensure the user has proper permissions to the requried database objects

CAPTURE-10059: Error loading database table fields

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

Cause: Database permission issue

Action: Ensure the user has proper permissions to the requried database objects

CAPTURE-10060: Error loading database tables

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

Cause: Database permission issue

Action: Ensure the user has proper permissions to the requried database objects

CAPTURE-10061: Error executing database lookup

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10062: Error saving document

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10063: Error testing lock

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10064: Error creating extension profile

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10065: Error loading extension profiles

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10066: Error updating extension profile

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10067: Error deleting extension profile

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10068: Error searching for extension profile

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10069: Error getting batch number

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10070: Error requesting session information

Cause: Application configuration error

Action: The application configuration is invalid or incomplete. Ensure the application is properly configured
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10071: Error moving document pages

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10072: Error splitting document

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10073: Error deleting document pages

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10074: Error creating documents

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10075: Error deleting documents

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10076: Error inserting into documents

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10077: Error searching database

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10078: Error creating bundle entity

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10079: Error loading installed bundles

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10080: Error loading installed bundles by name and version

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10081: Error deleting bundle

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10082: Error updating bundle

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10083: Error during bundle lookup

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10084: Error finding bundle by interface name

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10085: Error scanning for bundles

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10086: Error creating script

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10087: Error loading scripts for product

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10088: Error updating script

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10089: Error deleting script

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10090: Error loading script

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10091: Error loading picklist source

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10092: Error loading picklist link profiles

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10093: Error updating picklist source

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10094: Error creating picklist source

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10095: Error deleting picklist source

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10096: Error loading picklist drivers

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10097: Error finding picklist source

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10098: Error loading picklists

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10099: Error creating picklist

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10100: Error updating picklist

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10101: Error deleting picklist

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10102: Error creating picklist item

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10103: Error loading picklist items

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10104: Error updating picklist items

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10105: Error deleting picklist item

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10106: Error creating picklist link profile

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10107: Error loading picklist profile links

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10108: Error updating picklist link profile

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10109: Error deleting picklist link profile

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10110: Error deleting profile links

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10111: Error linking item to list

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10112: Error unlinking item from list

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10113: Error finding item link

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10114: Error creating Commit Profile

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10115: Error loading Commit Profiles

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10116: Error updating Commit Profile

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10117: Error deleting Commit Profile

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10118: Error deleting batch statuses for workspace

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10119: Error deleting index definitions for workspace

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10120: Error deleting batch status from workspace

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10121: A JMS Error has occurred

Cause: Diskspace capacity may have been reached.

Action: Check the disk space capacity and increase as needed.
Level: 1

Type: ERROR

Impact: Other

Cause: Network connectivity problem.

Action: Ensure the JMS server is accessible.

CAPTURE-10122: Error creating commit profile

Cause: The required batch processor could not be created.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10123: Failed to load document types

Cause: Database connectivity failure.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10124: The commit driver's configuration is invalid

Cause: The commit driver configuration has missing or invalid information

Action: Verify the configuration settings in the Workspace Management Console.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10126: Unknown commit error

Cause: An unexpected excption was encountered processing the document. This is usually caused by an unhandled exception in the commit driver or export driver.

Action: Verify the configuration settings in the Workspace Management Console.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10127: The import processor context must contain a valid DocumentEntity reference

Cause: The Import Job may not be properly configured.

Action: Verify the configuration settings in the Workspace Management Console.
Level: 1

Type: NOTIFICATION

Impact: Other

CAPTURE-10128: The import source file is null in the Import Context

Cause: The data being imported could not be found.

Action: Ensure that the Import Processor has privileges to the source file
Level: 1

Type: NOTIFICATION

Impact: Other

CAPTURE-10129: The HA token was not found in the import processor context

Cause: The Import Processor Context HA Token was missing.

Action: Ensure that the database server is running.
Level: 1

Type: NOTIFICATION

Impact: Other

CAPTURE-10130: The specified workspace could not be found

Cause: The Import Processor Context HA Token was missing.

Action: Ensure that the database server is running.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10131: Batch [{0}] was successfully locked by user [{1}] batch id is [{2}]

Cause: The batch was successfully locked by a user.

Action: No action required.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

CAPTURE-10132: Failed to deliver email

Cause: Unable to send email.

Action: Use the Enterprise Manager to ensure that the Email server settings are correct.
Level: 1

Type: ERROR

Impact: Other

Cause: (See message)

Action: Ensure that the Email server can be reached

CAPTURE-10133: Error copying workspace

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10134: Commit profile [{0}] does not specifiy a commit driver.

Cause: Commit profile configuration problem

Action: Ensure the specified commit profile has a commit driver specified.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10135: Commit profile [{0}] does not specifiy an export driver.

Cause: Commit profile configuration problem

Action: Ensure the specified commit profile has an export driver specified.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10136: Commit profile [{0}] specifies a commit driver that could not be found on the system.

Cause: The commit driver specified in the commit profile could not be found.

Action: Ensure the specified commit driver is properly installed or edit the commit profile and select a different commit driver.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10137: Commit profile [{0}] specifies an export driver that could not be found on the system

Cause: The export driver specified in the commit profile could not be found.

Action: Ensure the specified export driver is properly installed or edit the commit profile and select a different export driver.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10138: Unable to create the export directory.

Cause: The export driver specified in the commit profile could not be found.

Action: Ensure the specified export driver is properly installed or edit the commit profile and select a different export driver.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10139: The following required fields do not have values: [{0}]

Cause: Document is missing one or more required fields.

Action: Ensure all required fields are indexed.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10140: The batch was routed to a processing job that could not be found

Cause: The batch was routed to a job that was not found. The job may have been deleted.

Action: Ensure that the specified job exists.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10141: The batch was routed to a processing job that is currently offline

Cause: The batch was routed to a job that is in an offline state.

Action: The job needs to be put in an online state by someone with the required permissions
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10142: A workspace by the specified name already exists.

Cause: The user tried to create a workspace using a name that already exists.

Action: The user should try again using a unique name.
Level: 1

Type: NOTIFICATION

Impact: Other

CAPTURE-10143: Error loading locked batches for the specified workspace id

Cause: An invalid workspace id was specified or the specified workspace id does not exist.

Action: Ensure a valid workspace id was specified.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10144: Method access violation. User {0} attempted to invoke a method they are not authorized to access.

Cause: An invocation was made on a method to which the subject was not permitted access.

Action: Ensure the subject is a member of a secuirity role with permission to invoke the method.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10145: Unable to send a broadcast email. The SMTP Server connection information is incomplete.

Cause: The SMTP server connection information is incomplete

Action: Use Fusion Middleware Control to configure the SMTP Connection information.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10146: Document contains no pages.

Cause: The document contains no pages

Action: Review the batch in the capture client and check the system logs for more information.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10148: Generic commit error.

Cause: An error occurred during commit process.

Action: Check previous log entries for error detail.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10149: Error duplicating documents.

Cause: Database connectivity issue.

Action: Ensure the database is accessible and the specified user has the necessary permissions to the database..
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10150: Document Id does not exist.

Cause: A document ID was specified but was not found in the database. The document may have been deleted.

Action: Ensure that the specified document ID exists.
Level: 1

Type: ERROR

Impact: Other

CAPTURE-10151: Index Field [{0}] of Document [{1}] was assigned invalid value [{2}]

Cause: An attempt was made to save a document containing an invalid field value. The field may have contained an unprintable character.

Action: Ensure that only valid printable characters are assigned to document index fields.
Level: 1

Type: ERROR

Impact: Other

10 CFGFWK-20836 to CFGFWK-64276

CFGFWK-20836: Test Successful!

Cause: JDBC connection test was successful.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20839: Database Load Successful!

Cause: Database load was successful.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20840: PointBase Server Started...

Cause: PointBase server was started successfully.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20841: PointBase Server Stopped...

Cause: PointBase server stopped.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20842: PointBase Server start up message.

Cause: The PointBase Server instance has been started in the background on port {0}

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20843: Operations cause server stop.

Cause: Navigating from the panel will cause PointBase server to stop.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20844: Selected template names.

Cause: Currently selected templates are {0}

Action: Information message. No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20845: Applied templates.

Cause: Previously applied templates: {0}

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20846: Selected templates.

Cause: Currently selected templates: {0}

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20847: Template selected.

Cause: Selecting template {0}:{1} and all its prerequisites.

Action: Information message. No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20848: Template loaded.

Cause: Loading template {0}:{1}.

Action: Information message. No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20849: Available templates.

Cause: Currently available templates for loading: {0}

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20850: The domain is already at the current version.

Cause: {0}

Action: Click cancel to exit the wizard.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-40317: Invalid "Servers, Clusters and Machines" configuration.

Cause: The "Servers, Clusters and Machines" configuration in your domain is invalid.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40318: Invalid or missing JDBC datasource connection parameters.

Cause: The JDBC datasource required parameters are invalid or missing.

Action: Correct the datasource connection parameters.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40319: Invalid "JMS" configuration.

Cause: The "JMS" configuration in your domain is invalid.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40320: Invalid "Security" configuration.

Cause: The "Security" configuration in your domain is invalid.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40321: Configuration port conflict.

Cause: Duplicate Server listen ports exist in your domain configuration: {0}

Action: Change conflicting ports.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40322: External port conflict.

Cause: Server listen ports in your domain configuration conflict with ports in use by active processes on this host: {0}

Action: Change conflicting ports.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40323: Invalid configuration.

Cause: A section of configuration in your domain is invalid.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40324: Invalid "JMS" configuration.

Cause: JMSDestination's JNDI names are not unique in same target.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40325: Invalid "JDBC" configuration.

Cause: JDBC JNDI names are not unique in the same target.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40326: Invalid coherence server address.

Cause: At least one server in a Coherence cluster should have non localhost address.

Action: Enter a non localhost listen address for at least one Coherence server.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40327: Non supported configuration for restricted mode exists.

Cause: Non supported configuration for restricted mode like config mapping exists.

Action: Restricted templates should not include non supported configuration.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40865: The text in the file has changed.

Cause: This file has been modified in the editor, discard changes?

Action: Confirm to discard the changes.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40866: Discard previous changes.

Cause: Discard previously saved changes?

Action: Confirm to discard changes.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40867: Discard the changes.

Cause: Edited file has been modified, discard changes?

Action: Confirm to discard changes.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40868: No system component instance

Cause: You have not created any system component.

Action: Create a system component.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40891: A Custom directory doesn't contain valid JDK.

Cause: Unable to determine if the specified directory contains a valid JDK.

Action: Specify a directory with valid JDK.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40893: Invalid JDK Version.

Cause: The selected JDK version doesn't match the jdk version pattern.

Action: Select a different JDK.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40894: Invalid minimum JDK Version.

Cause: The recommended minimum JDK version doesn't match the JDK version pattern.

Action: Enter a valid JDK directory.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40895: Invalid JDK Version.

Cause: The selected JDK version is lower than recommended minimum version.

Action: Enter a valid JDK directory.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40905: Template exists.

Cause: A template already exists in that location. Do you want to overwrite it?

Action: Select the desired answer.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40906: Node Manager configuration will be skipped.

Cause: Oracle recommends using per domain Node Manager configuration. Current selection will cause the configuration of Node Manager for the domain to be skipped.

Action: Continue configuration to skip the current node manager configuration.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40915: JMS system resource selected for conversion to a UDD

Cause: At least one JMS system resource has been selected for conversion to a Uniform Distributed Destination (UDD). This conversion will take place only if the JMS system resource is assigned to a cluster.

Action: Warning message. No action required.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40930: Oracle Home not set

Cause: Oracle Home is not set for the current configuration.

Action: Set Oracle Home.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40931: No domain information.

Cause: Unable to obtain information pertaining to current domain.

Action: Provide domain information.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40950: Reconfiguration template was not available for custom template, and original not found; start scripts may be incomplete

Cause: The custom template at {0} had no corresponding reconfiguration template, and the original template could not be found.

Action: Check start scripts and manually edit to add contributions from the custom template.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40951: An application or library was not relocated to the new MW home.

Cause: Custom Applications were left in the original MW home and must be fixed manually: {0}

Action: Correct source path of the applications to refer to the new installation.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42001: Configuration conflicts detected.

Cause: Duplicate elements were found in configuration: {0}

Action: No action required. Elements from an incoming template will be discarded.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42057: No templates installed.

Cause: Installation contains no standard templates.

Action: Check installation or use custom template if available.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42061: Configuration component conflict detected.

Cause: The selected template contains a component already defined in the existing domain.

Action: Indicate how to resolve this conflict.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42062: Unable to select template.

Cause: The {0} template could not be selected because of the following: {1}.

Action: Fix the problems which prevented template selection, then try again.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42063: Unable to unselect template.

Cause: The {0} template could not be unselected because of the following: {1}.

Action: Fix the problems which prevented template unselected, then try again.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42064: Hidden selected templates.

Cause: One or more of the templates you selected are no longer visible in the list of Available Templates. To see all the templates you selected, select All Templates from the Template Categories menu.

Action: Select "All Templates" from the Template Categories menu.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42065: Missing driver classes.

Cause: The driver classes listed below were not found in the product installation: {0} A test will not be performed for any database connections using these drivers.

Action: Provide driver class.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42066: Missing driver class.

Cause: The driver class listed below was not found in the product installation: {0} A test will not be performed for any database connections using this driver.

Action: Provide driver class.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42067: The JDBC configuration test did not fully complete or completed with errors.

Cause: You can click "Next" to bypass the testing.

Action: Go back to the previous panels to fix the problems.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42068: The schema component data are not bound or the binding operation is unsuccessful with errors.

Cause: Error message: {0}.

Action: Enter the correct database connection parameters.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-60001: User name contains unsupported characters.

Cause: The user name contains commas, tabs, spaces, or any of the following characters: <>#|&?(){}

Action: Remove unsupported characters.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60005: Invalid password.

Cause: WebLogic domain requires the password to be minimum 8 characters

Action: Provide valid password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60052: Class name contains spaces.

Cause: Space characters are not allowed.

Action: Correct the class name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60055: Duplicated value.

Cause: The property "{0}" value is duplicated.

Action: Remove the duplicates.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60058: Invalid class name.

Cause: The class name must have the format "xxx.xxx.xxx.xxx".

Action: Correct the class name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60062: Additional address disallowed.

Cause: Invalid {0} of {1} "{2}". If "All Local Addresses" is selected, no additional address should be provided.

Action: Remove additional address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60063: No listen address is provided.

Cause: Invalid {0} of {1} "{2}". The list of address is empty.

Action: Provide at least one address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60064: Mismatched passwords.

Cause: The confirmation password does not match the entered password.

Action: Correct the password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60150: Servers port conflict.

Cause: The server "{0}" has the same combination of listen address and port as server "{1}".

Action: Select different port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60151: SSL port conflict.

Cause: The server "{0}" has the same combination of listen address and SSL port as server "{1}".

Action: Select different SSL port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60152: Admin port conflict.

Cause: The server "{0}" has the same combination of listen address and port as admin server.

Action: Select a different port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60153: Admin SSL port conflict.

Cause: The server "{0}" has the same combination of listen address and SSL port as admin server.

Action: Select a different port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60154: Server port conflict.

Cause: The server "{0}" has the same port and SSL port.

Action: Set one of the ports to a different value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60155: Empty Listen Port.

Cause: Server "{0}" Listen Port is empty.

Action: Set Listen Port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60156: IP v6 address in a wrong format.

Cause: The IP address must have the proper v6 format like "xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx" or "xxxx:xxxx:xxxx:xxx:xxx.xxx.xxx.xxx" or other supported format.

Action: Correct the IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60157: IP address in a wrong format.

Cause: The IP address must have the format "xxx.xxx.xxx.xxx".

Action: Correct the IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60158: Invalid IP address segment.

Cause: Each segment of the IP address must contain an integer in the range of 0 to 255.

Action: Correct the IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60159: Invalid IP address segment.

Cause: Each segment of the IP address must contain an integer in the range of 0 to 255.

Action: Correct the IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60160: Multicast IP address out of range.

Cause: The IP multicast address must be in the range of 224.0.0.1 to 239.255.255.255.

Action: Correct the IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60161: Invalid host name.

Cause: The host name does not allow leading or trailing dot (.).

Action: Correct the host name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60162: Invalid host name.

Cause: The host name does not allow multiple dots (.).

Action: Correct the host name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60163: Invalid host name.

Cause: No member of the hostname may begin or end with a dash (-).

Action: Correct the host name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60164: Invalid host name.

Cause: The entered value is not a valid hostname. Please use only alphanumeric characters and dot (.) and dash (-).

Action: Correct the host name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60165: Invalid Host Address.

Cause: Host address allows only digits.

Action: Correct the host address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60166: Invalid address format.

Cause: Each entry must be expressed as <hostname> or <hostname>:<port>.

Action: Correct the hostname and port format.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60167: Invalid port.

Cause: The port number must be an integer.

Action: Correct the port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60168: Invalid port.

Cause: The port number must be an integer in the range of 1 to 65535.

Action: Correct the port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60169: Conflicting multicast ports.

Cause: The cluster has the same combination of multicast address and port as other cluster.

Action: Change address or port for one of the clusters.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60170: Invalid multicast port.

Cause: Multicast port cannot be empty.

Action: Provide valid port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60171: Conflicting machine definitions.

Cause: The machine "{0}" has the same combination of listen address and port as other machine "{1}".

Action: Change one of machine definitions.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60172: Invalid listen port.

Cause: Listen port cannot be empty.

Action: Provide valid port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60173: Port conflict.

Cause: The admin server listen address "{0}" and port "{1,number,#}" conflicts with ports in use by existing processes on current host.

Action: Select a different port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60174: SSL port conflict.

Cause: The admin server SSL listen address "{0}" and port "{1,number,#}" conflicts with ports in use by existing processes on current host.

Action: Select a different port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60175: Empty SSL Listen Port.

Cause: Server "{0}" SSL Listen Port is empty.

Action: Set SSL Listen Port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60176: Invalid IP address segment.

Cause: Invalid {0} of {1} "{2}". Please enter a valid hostname or IP address. Note that if you are entering a IP address, Each segment of the IP address must contain an integer in the range of 0 to 255.

Action: Correct the IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60177: System component type is not specified.

Cause: System component type can not be empty.

Action: Enter a valid system component type.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60178: Only system component types "{0}" are supported.

Cause: Only system component types "{0}" are supported.

Action: Enter a valid system component type.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60179: Invalid OHS instance name "{0}".

Cause: The following OHS instance names are not valid, regardless of lower or upper case: "mbeans", "domain_bak", "instances", "AdminServer", "AdminServerTag".

Action: Enter a valid OHS instance name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60180: Invalid OHS instance name "{0}".

Cause: OHS instance names must begin with an alphabetic character, contain only alpha-numerics, underscores, and hyphens, and be no more than 30 characters long.

Action: Enter a valid OHS instance name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60181: Conflicting machine definition.

Cause: The machine "{0}" has the same combination of listen address and port as other server "{1}".

Action: Change machine definitions.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60182: Conflicting server definition.

Cause: The server "{0}" has the same combination of listen address and port as machine "{1}".

Action: Change server definition.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60200: Invalid targeting for distributed destination.

Cause: The targets of the distributed destination should cover all the servers that host the members.

Action: Include the missing servers.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60201: The distributed topic is not deployed.

Cause: The distributed topic "{0}" that distributed topic member "{1}" belongs to is not deployed.

Action: Deploy the distributed topic.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60202: The JMS server is not deployed.

Cause: The JMS Server "{0}" that topic "{1}" belongs to is not deployed.

Action: Deploy the JMS server.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60203: The distributed queue is not deployed.

Cause: The distributed queue "{0}" that distributed queue member "{1}" belongs to is not deployed.

Action: Deploy distributed queue.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60204: The JMS server is not deployed

Cause: The JMS Server "{0}" that queue "{1}" belongs to is not deployed.

Action: Deploy the JMS server.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60205: Empty group with Admin role.

Cause: Group(s) assigned to "Admin" role must contain at least one user.

Action: Add user to group.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60206: Unassigned Admin role.

Cause: Admin role must be assigned at least one group or one user.

Action: Assign Admin role to a group or a user.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60209: JDBCConnectionPool undeployment failure.

Cause: The JDBCConnectionPool "{0}" could not be undeployed from target "{1}", because it is used by the JMSJDBCStore "{2}", which is used by the deployed JMSServer "{3}".

Action: Switch JMSJDBCStore to use a different JDBCConnectionPool.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60250: Duplicate JNDI name.

Cause: The JNDI name is duplicated in JMS server "{0}"

Action: Choose a different JNDI name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60300: Domain name missing.

Cause: Domain name is not specified.

Action: Specify the domain name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60301: Domain name conflict.

Cause: The name of the WebLogic domain and the server and cluster names within it must be unique. A server or cluster already exists with the WebLogic domain name you specified.

Action: Change the name of the domain, conflicting server or cluster.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60302: Domain already exists.

Cause: A domain already exists at the specified location.

Action: Change the domain location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60303: Domain directory is not empty.

Cause: The domain directory "{0}" you specified contains files. You may only create a domain in an empty directory.

Action: Pick a different domain location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60304: Applications directory is not empty.

Cause: The applications directory "{0}" that you specified contains files. Applications may only be written to an empty directory.

Action: Pick a different directory.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60305: Invalid domain name.

Cause: The specified domain name is invalid. It must include only alphanumeric characters, hyphens ('-') or underscore characters ('_') and contain at least one letter but must not start with a number.

Action: Correct the domain name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60306: Domain location contains spaces.

Cause: The domain location contains spaces.

Action: Remove space characters.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60307: Domain location is missing.

Cause: The domain location is not be specified.

Action: Specify the domain location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60308: Domain location not writable.

Cause: The domain location does not have write permission.

Action: Correct permissions or select different domain location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60309: Applications location contains spaces.

Cause: The applications location contains spaces.

Action: Remove space characters.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60310: Applications location missing.

Cause: The applications location is not specified.

Action: Specify applications location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60311: Applications location not writable.

Cause: The applications location does not have write permission.

Action: Correct permissions or select different location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60312: Template name missing.

Cause: Template name is not specified.

Action: Specify the template name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60313: Invalid template name.

Cause: The specified template name is invalid. It must include only alphanumeric characters, hyphens ('-') or underscore characters ('_') and contain at least one letter or digit.

Action: Correct the template name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60314: Template location contains spaces.

Cause: The template location contains spaces.

Action: Remove space characters.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60315: Template location missing.

Cause: The template location is not specified.

Action: Specify template location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60316: Template location not writable.

Cause: The template location does not have write permission.

Action: Correct permissions or select different location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60317: The name of the domain, server or cluster names must be unique.

Cause: A domain or cluster already exists with the Server name.

Action: Change the name of the domain, conflicting server or cluster.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60324: Location is not a directory.

Cause: The given location is not a directory.

Action: Provide a valid location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60325: Invalid location.

Cause: The directory location is invalid.

Action: Provide a valid location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60326: Invalid directory location.

Cause: The specified directory location is invalid. It must include only alphanumeric characters, hyphens ('-') or underscore characters ('_') and contain at least one letter or digit.

Action: Correct the location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60327: Location is missing.

Cause: Location is not provided.

Action: Specify the location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60328: Invalid applications directory.

Cause: The applications location is not a directory.

Action: Provide a valid directory.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60329: Missing KeyStore password.

Cause: The following templates require entry of a KeyStore password:

Action: Set password for affected templates.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60330: KeyStore information missing.

Cause: Some of the added template require KeyStore information.

Action: Use the storeKeyStorePassword(template_location, password) command for each template listed above to enter required KeyStore passwords. The command must be entered after adding templates and before updating the domain.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60331: The domain location path is not absolute.

Cause: The path of the domain location field is not absolute.

Action: Correct path or select different location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60332: The application location path is not absolute.

Cause: The path of the application location field is not absolute.

Action: Correct path or select different location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60333: Node Manager location contains spaces.

Cause: The Node Manager location contains spaces.

Action: Remove space characters.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60334: Node Manager location is missing.

Cause: The Node Manager location is not be specified.

Action: Specify the Node Manager location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60335: The Node Manager location path is not absolute.

Cause: The path of the Node Manager location field is not absolute.

Action: Correct path or select different location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60336: Location is not a directory.

Cause: The given location is not a directory.

Action: Provide a valid location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60337: Node Manager location not writable.

Cause: The Node Manager location does not have write permission.

Action: Correct permissions or select different domain location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60338: Non supported distributed topic exists.

Cause: As part of JMS expansion JMS topics were converted to replicated distributed topics (RDTs) to preserve backward compatible behavior. The JMSServers targeted to dynamic clusters do not currently support RDT topics. The support is only available for partition distributed topics (PDT). Because PTD behavior is different from RTD an explicit property needs to be passed to the process to indicate that the conversion is intentional.Â Use system property "-Dcie.jms.internal.temp.expansion.use.pdt=true" to generate partitioned distributed topic.

Action: Use system property "-Dcie.jms.internal.temp.expansion.use.pdt=true" to generate partitioned distributed topic as default is replicated distributed topic.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60339: Machine and Node Manager is not configured.

Cause: An attempt was made to set the migration-policy of Persistent Store to "On-Failure" or "Alwyas". Before automatic migration of any kind can be used, the MigrationBasis must be set in the ClusterMBean. If database is chosen as MigrationBasis, then DataSourceForAutomaticMigration must be set as well.When consensus leasing is chosen as MigrationBasis, all servers that belong to the cluster must have a machine set and nodemanager configured for that machine.

Action: Set machine and configure nodemanager for that machine.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60340: A cluster member is being individually targeted via VirtualTarget.

Cause: A Managed server cannot be a member of cluster and individually targeted using VirtualTarget. The following VirtualTargets cannot be targeted individually {0}.

Action: The clustered Managed server VirtualTarget should not be used for targeting.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60341: Calculated Machine Names or Machine and Node Manager is not configured.

Cause: Some Oracle Fusion Middleware Products require calculated machine names to be selected and Machine and Node Manager to be configured unless Front-End Host is used.

Action: Set calculated machine names attribute, machines and configure nodemanager for that machine.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60450: Attempt to delete admin user.

Cause: The default admin user could not be deleted.

Action: Operation aborted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60451: Attempt to add restricted groups.

Cause: Cannot add built-in groups "everyone" or "users".

Action: Operation aborted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60452: Missing roles.

Cause: Built-in roles "Admin" and "Anonymous" must be provided.

Action: Provide required roles.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60453: Password too short.

Cause: The supplied user password for "{0}" is too short.

Action: Provide valid password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60454: Password too short.

Cause: The supplied user password for "{0}" is too short.

Action: Provide valid password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60455: Invalid password.

Cause: The password must be at least 8 alphanumeric characters with at least one number or special character.

Action: Correct the password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60456: Invalid or missing credentials configuration.

Cause: The credentials configuration in your domain is invalid.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60457: Invalid or missing keystore configuration.

Cause: The keystore configuration in your domain is invalid.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60458: Invalid private key password.

Cause: The password must be the same, used to create a private key.

Action: Correct the private key password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60550: Script execution aborted.

Cause: Encountered error: "{0}". Error is logged to "{1}".

Action: See log for details.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60600: Missing domain security.

Cause: Before booting this domain, it is necessary to run the SQL file located at {0} in order to initialize a domain security admin user in the database.

Action: Execute the SQL file.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60707: Template already selected.

Cause: The template "{0}" is already selected.

Action: No action required. The template is ignored.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60708: Template not found.

Cause: Found no templates with {0} name and {1} version

Action: Select a different template.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60709: Multiple matching templates.

Cause: Found {2} templates with {0} name and {1} version.

Action: Possibly corrupted installation. Check installation for correctness.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60710: Template not selected.

Cause: No templates were selected!

Action: Select templates to load.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60711: Template loading failed.

Cause: Unable to load template with {0} name and {1} version: {2}.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60712: Template loading failed.

Cause: Unable to load template from [{0}].

Action: Provide valid path.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60713: Command execution failed.

Cause: Attempt to execute command "{0}" in invalid state: {1}

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60714: Method not present.

Cause: The method "{0}" is not available.

Action: Provide valid method.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60716: The domain contains online pending unactivated changes, offline changes will be ignored on activation of pending changes.

Cause: The domain contains online pending unactivated changes.

Action: Activate or undo the pending changes before upgrading domain using WLST offline script.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60800: Bad Template

Cause: There is a problem with the template

Action: Correct the template
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60806: Error when generating log file

Cause: The Configuration Wizard was unable to generate the log file located at

Action: Check the log file.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60808: Unsupported Domain

Cause: Only domains associated with Oracle Home {0} are eligible for update..

Action: Select a domain from the currently active middleware home.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60816: Unsupported Template

Cause: The template {0} is not supported in the current environment as it was created without the presence of application server.

Action: Select a template created from the environment without the presence of an application server
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60817: Unsupported Template

Cause: The template {0} is not supported in the current environment which requires the presence of an application server.

Action: Select a template created from the environment containing an application server
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60818: Unsupported Domain

Cause: The domain {0} is not supported in the current environment as it was created without the presence of application server.

Action: Select a domain created without the presence of application server
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60819: Unsupported Domain

Cause: The domain {0} is not supported in the current environment which requires the presence of an application server.

Action: Select a domain created from the environment containing an application server
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60820: Unsupported Domain

Cause: This domain is a managed domain. It has been scaled out from the original domain.

Action: Select a domain which is a compatible with this environment.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60825: Error in HTTP proxy Application

Cause: Unable to create HTTP proxy application(s)

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60826: Existing Proxy

Cause: You have chosen a managed server {0} which is already a proxy for a cluster.

Action: It is recommended that a managed server only proxy a single cluster.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60827: Invalid Host name or IP address for managed Server

Cause: The managed server {0} chosen as a HTTP proxy for the cluster has an invalid Host name or IP address.

Action: The managed server should have a valid host name or an IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60828: Invalid Host name for Server

Cause: The server {0}, which is assigned to the cluster {1} has an invalid Host name or IP address.

Action: The Listen Address for all servers in a cluster with an HTTP proxy should be a valid host name or an IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60829: Invalid managed Server

Cause: The managed server with the server Name {0} chosen as a HTTP proxy for a cluster does not exist.

Action: The managed server should exist and be valid.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60830: No file to load.

Cause: There must be files to load.

Action: Provide file to load.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60831: No file selected.

Cause: You must select a file first.

Action: Select a file.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60834: Invalid URL.

Cause: The URL entered may not end with forward slash ("/").

Action: Modify the URL.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60835: Invalid URL.

Cause: The URL entered was malformed: {0}

Action: Modify the URL.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60837: Test failed.

Cause: Test Failed!

Action: Check the log.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60838: Error in connection.

Cause: Error getting connection information!

Action: Check the log.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60839: Failed to load database.

Cause: Database Load Failed!

Action: Check the log.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60840: Error in PointBase server startup.

Cause: Error encountered starting PointBase server or the server process was killed!

Action: Check the log.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60841: Log path.

Cause: For possible information regarding the error check the log located at:

Action: Check the log.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60842: Error in stopping PointBase server.

Cause: Error encountered stopping the PointBase server! Check log file:

Action: Check the log.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60843: Error in writing log file.

Cause: Error Writing Log File:

Action: Check the log.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60855: Invalid Template Name.

Cause: The Template Name is blank.

Action: Enter a valid Template Name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60856: Invalid Template Version.

Cause: The Template Version is blank.

Action: Enter a valid Template Version.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60857: Invalid Template Version Number.

Cause: The Template Version Number is invalid. It should be in the format N.N.N.N.N or N.N.N.N where N is a whole number.

Action: Enter a valid Template Version Number.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60865: Can not edit the file.

Cause: This file type is not editable

Action: Provide writable permission to file.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60870: Invalid start or end character for path.

Cause: Path cannot start or end with a path separator.

Action: Remove the path separator at the start or end
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60875: Invalid selection for removal

Cause: The selected directory is a representation of a location that will be selected by the user when using this configuration and cannot be removed.

Action: Select another file or directory to remove
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60876: Invalid selection for removal

Cause: You cannot remove the files in red or their parent directories because they comprise this configuration's applications.

Action: Select another file or directory to remove
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60877: No file selected to be removed

Cause: You must first select a file to remove.

Action: Select a file to be removed
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60878: Not selected Source file or directory

Cause: You must select a source file or directory on the left

Action: Select a valid source file or directory
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60879: Invalid destination location

Cause: You must select a destination location on the right

Action: Select a destination location
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60880: Invalid selection

Cause: The selected directory is a representation of a location that will be selected by the user when using this configuration and files cannot be added.

Action: Select another destination file or directory
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60881: Invalid selection

Cause: The selected file cannot be added to your domain directory because it is a reserved file. This usually means that the file will be auto-generated by the configuration wizard and does not need to be added.

Action: Select a different file or directory
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60882: Error reading template location.

Cause: The template location {0} cannot be read due to an unexpected I/O error.

Action: Verify template location is a valid one.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60885: Error preparing the template

Cause: Error encountered preparing template from jar

Action: Check the jar file.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60891: A Custom directory doesn't contain valid JDK.

Cause: Unable to determine if the specified directory contains a valid JDK. Do you want to proceed?

Action: Specify a directory with valid JDK.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60892: Invalid directory location

Cause: The specified directory does not exist.

Action: Enter a valid JDK directory.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60900: No file selected

Cause: No file was selected to be moved up

Action: Select a file to be moved up
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60901: No file selected

Cause: No file was selected to be moved down

Action: Select a file to be moved down
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60905: Password mismatch.

Cause: Password does not match.

Action: Correct the password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60906: Empty field.

Cause: The field {0} cannot be empty.

Action: Provide field value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60907: Invalid field value.

Cause: The field {0} must be an integer.

Action: Provide integer value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60908: Empty password field.

Cause: The password/confirm password field is empty.

Action: Provide value for password/confirm password field.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60909: Password does not match.

Cause: The password entered should match the confirm password field.

Action: Correct the password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60915: Invalid custom directory.

Cause: A Custom directory is not empty.

Action: Specify a valid directory.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60916: Invalid node manager home

Cause: The node manager home is not a directory.

Action: Specify a valid directory.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60918: Invalid user name

Cause: The user name can not be empty.

Action: Specify a valid user name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60919: Invalid SSL Listen Port.

Cause: SSL Listen Port of Server "{2}" is empty.

Action: Provide SSL Listen Port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60920: The name of the domain, server or cluster names must be unique.

Cause: A domain or server already exists with the Cluster name "{2}".

Action: Change the name of the domain, conflicting server or cluster.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60921: The name of the domain, server or cluster names must be unique.

Cause: A domain or cluster already exists with the Server name "{2}".

Action: Change the name of the domain, conflicting server or cluster.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60922: Invalid port value.

Cause: The listen port value {3,number,#} of {1} "{2}" is out of range. It must be between 1 and 65535.

Action: Enter a valid port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60923: Invalid port value.

Cause: The SSL listen port value {3,number,#} of Server "{2}" is out of range. It must be between 1 and 65535.

Action: Enter a valid port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60924: Invalid value of "{0}" property.

Cause: Property "{0}" of {1} "{2}" is invalid. The name must not be null or empty and may not contain any : , = * ? % / _cloned.

Action: Provide valid property value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60925: Invalid port value.

Cause: The Coherence listen port value {1,number,#} of cluster "{0}" is out of range. It must be between 0 and 65535.

Action: Enter a valid port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60926: Invalid port value.

Cause: The listen port value {3,number,#} of node manager for machine "{2}" is out of range. It must be between 1 and 65534.

Action: Enter a valid port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60927: Invalid port value.

Cause: The Coherence listen port value {1,number,#} of cluster "{0}" is invalid. It must be between 0 and 65535.

Action: Enter a valid port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60928: Invalid existing node manager home directory.

Cause: Existing node manager home directory does not exist or is not accessible.

Action: Specify a valid directory or check permissions if it is not accessible.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60930: Failed to select template. Please run with logging turned on.

Cause: There may be issues with the template(s) and/or with the template location(s).

Action: Fix template(s) and/or provide correct template location(s).
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60931: Failed to process database information.

Cause: Failed to process database information.

Action: Fix db info in the template(s).
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60932: Invalid listen port.

Cause: Port number must be between 1 and 65535, and different from SSL listen port and Coherence port.

Action: Fix the listen port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60933: Invalid ssl port.

Cause: Port number must be between 1 and 65535, and different from listen port and Coherence port.

Action: Fix the ssl port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60934: Invalid coherence port.

Cause: Port number must be between 1 and 65535, and different from listen port and SSL listen port.

Action: Fix the Coherence port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60935: Failed to select template.

Cause: Please see the log file {0} for details.

Action: Fix template(s) and/or its location in the configuration file. Also check the validity of the configuration xml file.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60950: Required template not found in new installation directory

Cause: A template that was required for the reconfiguration could not be found in the upgraded MiddleWare home: {0}

Action: Refer to upgrade documentation for information about installation and product migration.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60951: Failed to load reconfiguration template

Cause: The reconfiguration template {0} failed to load due to invalid meta-data

Action: Correct the template.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60952: Failed to load replacement template

Cause: Unable to load the template {0}

Action: Correct the template
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60953: An application or library was not relocated to the new MW home.

Cause: An error in the reconfiguration templates resulted in the following deployments being left in the original MW home: {0}

Action: Correct the reconfiguration templates
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60954: A reconfiguration template cannot be the replacement for another reconfiguration template

Cause: The reconfiguration template {0} specified another reconfiguration template {1} as its replacement. The replacement must be either an extension or domain template.

Action: Correct the reconfiguration template
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60955: Unable to locate the WebLogic Server component.

Cause: The domain did not contain component references corresponding to known WebLogic Server components

Action: None; the domain cannot be reconfigured
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60956: Unable to locate the certifiate.

Cause: The certificate does not exist at given location {0}.

Action: Browse or provide the proper certificate location
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60957: Unable to locate the private key file.

Cause: The private key file does not exist at given location {0}.

Action: Browse or provide the proper private key file location
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60958: The empty password is not allowed.

Cause: The password is not provided.

Action: Provide the valid password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60959: Unable to locate the certifiate.

Cause: The certificate does not exist at given location {0}.

Action: Browse or provide the proper certificate location
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60970: Reconfigured domain had template dependency conflicts

Cause: Invalid reconfiguration templates left the domain in an invalid state.

Action: Correct the reconfiguration templates
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60971: The domain is not reconfigurable.

Cause: The domain did not contain information necessary to determine how to reconfigure the domain.

Action: Refer to the upgrade documentation on how to proceed.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61000: Failed to create CAM instance.

Cause: An error occured while generating a CAM instance.

Action: Check the log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61001: Invalid system component schema with details

Cause: An error occurred while validating the schema for System Component. {0}

Action: Set all the required properties for system component.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61010: The entered Domain Frontend URL is invalid.

Cause: An error occured while validating the URL {0}

Action: Please enter a valid URL.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61011: The Domain Frontend URLs could not be set in ConfigMapping

Cause: The Frontend host were not set in Config Mapping.

Action: Please check log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61012: The Schema entered for Domain Frontend URL is invalid.

Cause: An error occured while validating the Schema for the URL {0}

Action: Please enter a valid URL.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61013: The entered Address for Domain Frontend URL is invalid.

Cause: An error occured while validating the Address for the URL {0}

Action: Please enter a valid URL.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61014: The entered Port for Domain Frontend URL is invalid.

Cause: An error occured while validating the Port for the URL {0}

Action: Please enter a valid URL.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61015: The url for the field cannot be null or empty

Cause: An error occured while validating the URL. The URL cannot be Null or empty.

Action: Please enter an URL.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61020: Frontend HTTP/HTTPS Port has been entered, but Frontend Host is missing.

Cause: Frontend Host is empty.

Action: Enter a valid Frontend Host address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61021: Frontend Host has been entered, but Frontend HTTP/HTTPS Port is missing.

Cause: Frontend HTTP/HTTPS Port is empty.

Action: Enter a valid Frontend HTTP/HTTPS Port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-62002: Invalid Oracle home location

Cause: Given Oracle home "{0}" doesn't exist.

Action: Provide valid Oracle home.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-62003: Oracle home location is missing

Cause: Oracle home location is not specified.

Action: Specify the Oracle home location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-62004: Location is not a directory

Cause: The given location ("{0}") is not a directory.

Action: Provide a valid location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-62005: No template found in the given Oracle home.

Cause: The given location ("{0}") is not a valid Oracle home.

Action: Provide a valid Oracle home.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-62006: Error occurred in templates retrieval

Cause: Error occurred: "{0}"

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

Type: ERROR

Impact: Configuration

CFGFWK-62007: No choice selected

Cause: No flow choice selected

Action: Select a valid choice
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-62008: Invalid value of "{0}" property.

Cause: Property "{0}" of {1} "{2}" is invalid. The name must not be null or empty and may not contain any : , ; = * ? % /.

Action: Provide valid property value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-62009: Invalid value of "{0}" property.

Cause: Property "{0}" of {1} is invalid. {0} must start with /

Action: Provide valid property value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-62010: Invalid value of "{0}" property.

Cause: Port values for "{2}" of {1} is invalid. Either Explicit Port or Port Offset must to be set to a non zero value.

Action: Provide valid property value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-62011: Invalid value of "{0}" property.

Cause: Port values for "{2}" of {1} is invalid. Cannot set both Explicit Port and Port Offset.

Action: Provide valid property value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64001: Property value is not part of enumerated values.

Cause: According to the XML schema, the value for property {0} of {1} must be one of the following: {3}.

Action: Use one of the valid values.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64002: Invalid property value.

Cause: The value "{3}" for property "{0}" of {1} {2} did not pass XML schema validation: {4}.

Action: Provide valid value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64009: The "{0}" property is missing.

Cause: "{0}" is empty. It must be set on the {1} objects. The name must not be null or empty.

Action: Provide a name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64010: Invalid property value.

Cause: Property "{0}" of {1} "{2}" is invalid.

Action: Provide valid property value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64012: Invalid property value.

Cause: Property "{0}" of {1} "{2}" is invalid. Space characters are not allowed.

Action: Provide valid property value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64013: Internal representation conversion error.

Cause: The string cannot be converted.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64014: The required property is missing.

Cause: Invalid property "{0}" of {1}: value "{2}" is invalid. The property value is required.

Action: Provide property value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64015: Duplicated property.

Cause: Invalid property "{0}" of {1}: value "{2}" is invalid. The property value is duplicated.

Action: Correct the property value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64016: Attempt to set disabled property.

Cause: The property "{0}" is disabled on type {1}.

Action: Internal error. No user actions available.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64017: Attempt to set unsupported property.

Cause: The property "{0}" is not supported on type {1}.

Action: Internal error. No user actions available.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64018: Mismatched password values.

Cause: The password value does not match the confirmation password.

Action: Correct password values.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64019: The "{0}" property is missing.

Cause: "{0}" is empty. It must be set on the {1} objects. The name must not be null or empty and should contain valid characters only.

Action: Provide a name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64020: The file "{0}" does not exist or is not a file.

Cause: "{0}" does not exist or is not a file.

Action: Provide a file name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64021: Fatal internal error.

Cause: An unexpected internal condition was detected: {0}. The wizard cannot continue.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64022: Unspecified error.

Cause: One of the subsystems generated an error: {0}

Action: Check error text for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64023: The file "{0}" does not have permission to read.

Cause: "{0}" does not have permission to read.

Action: Provide a read permission.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64024: The file "{0}" does not have permission to write.

Cause: "{0}" does not have permission to write.

Action: Provide a write permission.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64025: Maximum number of entries reached.

Cause: At most {0} entries can be created.

Action: Operation aborted; no further action required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64026: Maximum number of entries reached.

Cause: At most 1 entry can be created.

Action: Operation aborted; no further action required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64027: Minimum number of entries not reached.

Cause: At least {0} entries must be provided.

Action: Operation aborted; no further action required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64028: Minimum number of entries not reached.

Cause: At least 1 entry must be provided.

Action: Operation aborted; no further action required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64029: Can not remove entry.

Cause: Disabled entry may not be removed.

Action: Removal aborted. No user actions available.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64030: The target file must be specified.

Cause: The target file must be specified.

Action: Provide a target file.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64031: The service-id and service-type both are required for the service type "NEW".

Cause: The service-id and service-type both are required for the service type "NEW".

Action: Provide a service-id and service-type.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64032: The output-date-target element must be specified.

Cause: The output-date-target element must be specified.

Action: Provide a output-date-target element.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64033: The invalid input-data-src type specified.

Cause: The invalid input-data-src type specified.

Action: Provide a valid input-data-src type.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64034: The target xpath for a token bind or target-key for an xml bind is not applicable.

Cause: The target xpath for a token bind or target-key for an xml bind is not applicable.

Action: Provide a target-key for a token bind or target-xpath for an xml bind.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64035: Multiple assignment to target.

Cause: The {0} "{1}" could not be assigned to the target "{2}" since each target can have only one {0} assigned.

Action: Change the assignment.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64036: The invalid app-svc-name "{0}" is defined.

Cause: The invalid app-svc-name "{0}" is defined.

Action: Provide a valid app-svc-name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64037: The invalid FEHost Address type "{0}" is defined.

Cause: The invalid FEHost Address type "{0}" is defined.

Action: Provide a valid FEHost Address type.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64038: The app-svc-name "{0}" must have target.

Cause: The app-svc-name "{0}" must have target.

Action: Provide a valid target.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64040: Invalid template location.

Cause: Specified template does not exist or is not a file: "{0}".

Action: Provide a valid template location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64041: Invalid template.

Cause: Template "{0}" is not a valid jar file.

Action: Provide a valid template location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64042: Invalid template.

Cause: Template "{0}" does not contain template-info.xml.

Action: Provide a valid template location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64043: Invalid template.

Cause: template-info.xml could not be parsed: {0}

Action: Provide a valid template location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64044: Invalid template.

Cause: XML schema validation failed for template-info.xml: {0}

Action: Provide a valid template location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64045: Unable to save template-info.

Cause: Encountered error while saving template-info.xml: {0}

Action: Check generated exception for details.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64050: Invalid location

Cause: No template was selected

Action: Select a valid template
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64051: Invalid location.

Cause: The selected location does not contain WebLogic domain.

Action: Select a valid domain.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64052: Invalid configuration

Cause: This is not a valid configuration! Correct the following error in config.xml: {0}

Action: Correct config.xml
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64053: Domain loading error.

Cause: The Configuration Wizard encountered problems attempting to load the domain you selected: {0}.

Action: Select a different domain.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64054: Unsupported domain.

Cause: The domain in this directory is not a supported version.

Action: Select a different domain.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64055: Invalid template extension.

Cause: Template destination is not having a valid extension.

Action: Correct the template destination extension to .jar.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64056: Error adding templates.

Cause: The Configuration Wizard encountered problems attempting to add templates you selected: {0}.

Action: Verify template integrity or select different templates.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64058: Incompatible templates.

Cause: Some of the extension templates you have selected are incompatible with each other due to conflicting application and/or service names: {0}

Action: Modify template selection.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64059: Unsatisfied conditions.

Cause: The template you selected cannot be applied because the following conditions have not been satisfied: {0}

Action: Select "Yes" to override these conditions (Not Recommended).
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64062: Invalid template.

Cause: Domain template "{0}" could not be loaded: {1}

Action: Select a valid domain template
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64063: Missing config.xml in template

Cause: The config.xml is invalid or missing in the template selected

Action: Select a valid template
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64064: No domain template in selection.

Cause: Selection must contain at least one domain template. Currently selected templates are defined as extension templates and do not express a dependency on a domain template.

Action: Include domain template into your selection.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64065: No templates added.

Cause: At least one template needs to be added to configuration.

Action: Add a template.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64066: Template location is missing.

Cause: Template location is not provided.

Action: Specify template location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64067: Invalid template.

Cause: Only Oracle product templates from the Oracle Home already associated with this domain are eligible for selection.

Action: Select a template associated with the current Oracle Home.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64069: Missing template prerequisites.

Cause: The following prerequisites could not be satisfied: {0}

Action: Verify that prerequisite templates are present or change your selection.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64070: Template conflict.

Cause: The following templates are both prerequisites and conflicts for the current selection: {0}

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64071: Template conflict.

Cause: The selection conflicts with templates already present in the domain: {0}

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64072: Ambiguous prerequisite.

Cause: There are multiple matches for one of the prerequisites specified by a template. Resolve the ambiguity by preselecting one of the choices before attempting selection: {0}

Action: Select the desired prerequisite.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64073: Non-selectable template.

Cause: The template is not selectable in the current mode.

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64074: Missing template.

Cause: The template is not available.

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64075: Template is configured.

Cause: The template was previously configured.

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64076: Template already selected.

Cause: The template is already selected.

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64077: Template already unselected.

Cause: The template is already unselected.

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64078: Template selection error.

Cause: Encountered error during selection operation: {0}

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64079: Template conflict.

Cause: The selection requires templates which conflicts with the current domain: {0}

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64080: Invalid template config-groups.

Cause: The template "{0}" config-groups contains the app-svcs names {1} which are not present in configuration.

Action: remove invalid app-svcs names from config-groups.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64085: Directory not selected.

Cause: A directory was not set.

Action: Select a valid directory.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64086: 'Extension Template' as a source not allowed.

Cause: Selection of an 'Extension Template' as source for 'Domain Template' creation is not supported.

Action: Select a valid source.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64087: Invalid source type.

Cause: Selection of an Oracle product 'Extension Template' as a source is not allowed.

Action: Select a valid source.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64100: Invalid help topic.

Cause: No such help topic exists.

Action: Provide valid help topic.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64101: Help is not configured

Cause: No Help configuration found.

Action: Configure help.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64102: Invalid help type.

Cause: Help type not supported.

Action: Provide the valid help type.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64103: Failed to load help.

Cause: Errors occurred while loading Help.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64104: Low console width.

Cause: Value of console width is too low!

Action: Increase the console width.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64200: No common database driver.

Cause: The selected data sources do not share any common database drivers. The wizard will deselect data sources to allow selection of compatible drivers.

Action: No action required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64201: No common database driver.

Cause: The selected component schemas do not share any common database drivers. The wizard will deselect component schemas to allow selection of compatible drivers.

Action: No action required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64204: Validation errors.

Cause: Some more validation errors occurred.

Action: Correct validation errors.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64205: Unspecified property.

Cause: The {0} must be specified.

Action: Specify the property.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64206: Unspecified properties.

Cause: The following must be specified: {0}

Action: Provide missing properties.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64207: Mismatched passwords.

Cause: The {0} and {1} do not match.

Action: Correct the password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64208: Invalid value.

Cause: The {0} must be an integer.

Action: Provide integer value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64209: Test Canceled!

Cause: You have cancelled the connection test.

Action: No further action required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64210: Test Failed!

Cause: JDBC connection test failed.

Action: Check logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64211: Test Failed!

Cause: Error getting connection information!

Action: Provide connection details.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64212: No rows returned.

Cause: A connection was established to the database but no rows were returned from the test SQL statement.

Action: Check logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64213: Test Successful!

Cause: JDBC connection test was successful.

Action: No action required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64215: There are no data sources selected.

Cause: Detected that there are no data sources selected.

Action: Select the data sources that you want to test.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64216: Data source {0} connection test failed.

Cause: Error message: {0}

Action: Go to previous panels to fix the problem and test it again.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64217: JDBC data source validations failed.

Cause: Error message: {0}

Action: Go to previous panels to fix the problem and test it again.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64218: Server configuration validations failed.

Cause: For instance {0}, valid input value for {1} must be specified,

Action: Enter the required values.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64219: Failed to bind the schema component data

Cause: Error message: {0}.

Action: Enter the correct database connection parameters.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64220: CopyFileDefinition validations failed.

Cause: The duplicate copy file definition name across multiple templates : {0}.

Action: Each copy file definition must be defined with an unique name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64221: DeleteFileDefinition validations failed.

Cause: The duplicate delete file definition name across multiple templates : {0}.

Action: Each delete file definition must be defined with an unique name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64222: CopyFileDefinition source exists validations failed.

Cause: The source location does not exist for the copy definition.

Action: Correct the copy definition in the template to refer to a valid source location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64253: Error occurred in "{0}" phase initialization

Cause: Encountered error: {1}

Action: Check log for more detail.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64254: Error occurred in "{0}" phase execution

Cause: Encountered error: {1}

Action: Check log for more detail.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64255: Error occurred in parsing the configuration file: "{0}".

Cause: Encountered error: {1}

Action: Check log for more detail.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64256: Invalid Template location.

Cause: Template generation location is not set.

Action: Check log for more detail.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64257: Failed to delete old template.

Cause: Unable to delete existing template "{0}" file.

Action: Check log for more detail.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64258: Unable to create template directory.

Cause: Failed to create template "{0}" directory.

Action: Check log for more detail.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64261: Invalid Domain location.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64262: Unable to create domain directory:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64263: Invalid Applications location.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64264: Unable to create applications directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64265: Invalid Scratch location.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64266: Unable to create scratch directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64267: Error creating JarHelper

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64268: Failed to create backup file

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64272: Domain directory did not exist.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64273: Domain directory not set.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64276: Reconfiguration Failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

11 CLONE-20200 to CLONE-92302

CLONE-20200: The clone option or argument is invalid.

Cause: The option or argument "{0}" was not supported by movement scripts.

Action: Provide a valid option or argument. Use the "-help" option for more information about movement scripts 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 clone argument is invalid.

Cause: The argument "{0}" was not provided with "{1}" movement script.

Action: Make sure that the combination of arguments and script is correct.
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: Invalid value for "{0}" option.

Cause: The provided value was "{0}".

Action: Supported values are "{0}".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20206: Invalid value for "{0}" option.

Cause: The provided value was not a Boolean value.

Action: Supported Boolean values are "true" or "false".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20207: Unable to update following property "{0}" in nodemanager.properties file.

Cause: Encryption was unsuccessful.

Action: Update the nodemanager.properties file manually to provide the value of property "{0}" in clear text. Then start nodemanager to encrypt the value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20208: Log level is invalid

Cause: Bad log level "{0}". It was set via "{1}" for system property "{2}".

Action: Set valid log level. Supported log levels are "{0}" .
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20209: Cloning operation can not be performed.

Cause: Following files {0} were present inside Oracle Home.

Action: Delete above files and perform clone operation again.
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 copyBinary or copyConfig operation.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20218: Cloning is not successful.

Cause: An internal operation failed.

Action: Check the clone log and error file for detailed information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20219: Clone type is invalid.

Cause: Clone type was either empty or not supported.

Action: The clone type is either "{0}" or "{1}" or "{2}".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20220: Parameters are missing.

Cause: Either archiveLocation or cloneType was empty. The values provided were archiveLocation : "{0}" cloneType : "{1}".

Action: Make sure that the correct values are provided.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20221: Invalid clone type.

Cause: The clone type "{0}" did not match "{1}" or "{2}".

Action: The clone type should be either "{0}" or "{1}".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20222: Parameters validation has failed.

Cause: Primary parameters validation for "{0}" failed.

Action: Check the clone log and error file and provide correct value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20223: Invalid Oracle Home.

Cause: There are four possible causes for an invalid Oracle Home "{0}": 1. It did not exist. 2. It was an empty directory. 3. It had invalid inventory pointer file (if operating system is other than Windows). 4. It had no top component or invalid top component version.

Action: Provide a valid Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20225: Some configuration files have incorrect entry.

Cause: The following files were still referring to the source Oracle Home {0} {1}

Action: Update those files with target Oracle Home path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20227: Error in validating T2P binary..

Cause: T2P binary had been compromised.

Action: Make sure that the T2P binaries are valid. Check the T2P documentation for more information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20228: Error in validating archive file.

Cause: Unable to find internal version pertaining to T2P operation from the archive.

Action: Make sure that archive file is valid and correct T2P binaries are used during copy and paste operation.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20229: Error in validating archive file.

Cause: Archive file had been compromised.

Action: Make sure that the archive file is valid. Check the T2P documentation for more information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20230: Primary validation prior to clone operation has failed for {0}.

Cause: Parameter(s) were missing or some validation(s) failed.

Action: Check the clone log and error file for information about which parameter is missing or why validation failed.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20231: Error in validating archive file.

Cause: The version of archive file and T2P binary were "{0}" and "{1}" respectively. The possible causes were: 1. The major version was mismatched. 2. The minor version of archive file is higher than the minor version of T2P binary used for paste operation.

Action: Make sure that correct T2P binary is used during copy and paste operation.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20232: Oracle Home configuration has failed.

Cause: Exception occurred while configuring Oracle Home.

Action: Check the oraInstaller, cloneAction log and error file for more details. The location of these files can be found from the clone log file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20235: Adding "{0}" to the archive has failed.

Cause: An internal operation failed.

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

Type: ERROR

Impact: Cloning

CLONE-20236: Archive creation has failed.

Cause: An internal operation failed.

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

Type: ERROR

Impact: Cloning

CLONE-20237: Restoring the sourceid "{0}" has failed.

Cause: An internal operation failed.

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

Type: ERROR

Impact: Cloning

CLONE-20238: Restoring the sourceid "{0}" has not completed successfully.

Cause: An internal operation completed with warning.

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

Type: ERROR

Impact: Cloning

CLONE-20239: Invalid archive file.

Cause: Either archive did not have sourceid file, or a sourceid was a zero size file.

Action: Make sure the correct archive file is provided, and check the extracted sourceid file whose path is "{0}".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20240: Invalid archive file.

Cause: Either archive did not have "{0}" file, or archive was not created through copyConfig operation.

Action: Make sure that the correct archive file is provided.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20241: Permission of some of the files are not captured.

Cause: Permission of following files were not correct {0}.

Action: Correct permission either at source and run copyBinary again or at target after pasteBinary.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20242: Permission of some of the files are not captured.

Cause: Permission of following files were not captured because their names were not calculated properly {0}.

Action: Correct permission of the files under those directories at target after pasteBinary.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20243: Permission of some of the files are not captured.

Cause: Number of fields in permission details was not {0} for following permission details. {1}.

Action: Correct permission of the files under those directories at target after pasteBinary.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20245: Unable to include permission file to the archive.

Cause: Permission file creation failed.

Action: Check the clone log and error file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20247: Not all file permission operations are successful.

Cause: Either some files were missing from the Oracle Home {0} or some invalid entry in permission restore file {1}.

Action: Check the clone log file, permission restore log file {0} and permission file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20248: Execution of system prerequisites have failed.

Cause: The following system prerequisites failed : {0}.

Action: Check the nextgen log file {0} present under {1} and clone log file 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 the nextgen log file {0} present under {1} and clone log file 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 the nextgen log file {0} present under {1} and clone log file for more details on prerequisites output and result.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20251: Execution of system prerequisites failed for the Oracle Home.

Cause: Some of the system prerequisites were not completed successfully.

Action: Check the clone log 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: The operation could not be performed because the Oracle Home did not have supported binaries.

Cause: The root causes were :{1}.

Action: Make sure that the Oracle Home has correct binaries.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20255: The operation could not be performed because the Oracle Home name is already registered with the Oracle Inventory.

Cause: The Oracle Home name {0} provided in -ouiparam argument was already registered with the Oracle Inventory for Oracle home {1}.

Action: Either provide a different inventory location or provide a different Oracle Home name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20256: Unable to capture permission of all the files present under the Oracle Home.

Cause: Some of the files did not have proper permission.

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

Type: ERROR

Impact: Cloning

CLONE-20257: Unable to clone the Oracle Home.

Cause: The Oracle Home name "{0}" was already registered with the Oracle Inventory for Oracle Home "{1}".

Action: Either provide a different inventory location or provide a different Oracle Home name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20258: Unable to archive a file.

Cause: The file "{0}" did not have sufficient permission to access.

Action: Correct the permission of above file and run copyBinary again.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20261: Invalid Oracle Inventory.

Cause: There are six possible causes for an invalid inventory pointer file "{0}": 1. File did not exist. 2. File did not have read permission. 3. It was a zero size file. 4. File did not have any pointer to OraInventory. 5. Oracle Inventory found from file was not absolute. 6. Oracle Inventory specified in the inventory pointer file did not have write permission.

Action: Provide a valid inventory pointer file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20262: Unable to clone the Oracle Home.

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

Action: Either provide a different inventory location or provide a different location for the new Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20263: Invalid Oracle Inventory.

Cause: There are two possible causes for an invalid OraInventory "{0}". 1. Inventory was empty. 2. It did not have valid inventory.xml file.

Action: Provide a valid Oracle Inventory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20264: Default inventory pointer file is invalid.

Cause: There are six possible causes for the default inventory pointer file "{0}": 1. File did not exist. 2. File did not have read permission. 3. It was a zero size file. 4. File did not have any pointer to OraInventory. 5. Oracle Inventory found from file was not absolute. 6. Oracle Inventory specified in the inventory pointer file did not have write permission.

Action: Ensure that the default inventory pointer file is valid or provide a different, valid inventory Pointer file using the {0} argument.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20265: Invalid argument.

Cause: Either argument was an empty string or "null".

Action: Provide a valid argument.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20266: Loading of OUI and engine jar to system class loader was unsuccessful.

Cause: The possible causes are : {0}

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

Type: ERROR

Impact: Cloning

CLONE-20268: Extracting is unsuccessful.

Cause: Unable to move Oracle home binaries from its temporarily extracted location {0} to actual location {1}.

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

Type: ERROR

Impact: Cloning

CLONE-20269: Setting Java library path has failed.

Cause: There are four possible causes: 1. The OUI library path {0} was empty. 2. Unable to find OUI library directory name. 3. The oraInstaller library path {1} was empty. 4. The oraInstaller library path {1} was corrupted.

Action: Make sure that OUI and the oraInstaller library are available.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20271: Invalid characters.

Cause: Command-line input {0} had some unsupported characters.

Action: Supported characters are "{0}" but these three characters "_.-" are not allowed in the beginning of a string.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20272: Invalid path.

Cause: Path "{0}" was either not absolute or did not have valid characters.

Action: Supported characters are "{0}" but these three characters "_.-" are not allowed in the beginning of a string.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20275: Insufficient space to create {0}.

Cause: Minimum required space was at least "{0}" MB, but only "{1}" MB was available for use.

Action: Make sure that the minimum required space is available for use.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20276: Extracting is unsuccessful.

Cause: Either there was no space available or no write permission.

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

Type: ERROR

Impact: Cloning

CLONE-20277: Some files are missing.

Cause: After configuration, some files were removed.

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

Type: ERROR

Impact: Cloning

CLONE-20278: Oracle Home configuration is unsuccessful.

Cause: Some symbolic link(s) were either mismatching or were not present.

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

Type: ERROR

Impact: Cloning

CLONE-20279: Some of the files present under Oracle Home did not have proper permission.

Cause: Some of the files did not have proper permission.

Action: Find expected and actual permission from permission file {0}. Update the permission of those files to have the proper permissions.
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-20288: Unable to unregister all asinstances(which were present in source domain) from target domain.

Cause: An internal operation failed.

Action: Check the clone log and error file for more details and unregister following asinstances {0} from target domain through admin console.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20293: Oracle Home configuration is unsuccessful.

Cause: The OraInventory {0} from invPtrLoc file {1} did not match with OraInventory {2} from reference invPtrLoc file {3}.

Action: Check the clone log file and install CloneAction file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20294: Oracle Home configuration is unsuccessful.

Cause: Unable to find Oracle Home name from the inventory.xml file.

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

Type: ERROR

Impact: Cloning

CLONE-20295: Oracle Home configuration is unsuccessful.

Cause: Some "symbolic link" files were either not present or not properly linked where absolute path should be "{0}" and canonical path should be "{1}"

Action: Create those symbolic link.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20299: Oracle Home configuration is unsuccessful.

Cause: Some "no read permission" files were not present.

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

Type: ERROR

Impact: Cloning

CLONE-20305: Extracting is unsuccessful.

Cause: Some files were missing.

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

Type: ERROR

Impact: Cloning

CLONE-20318: Missing argument: {0}.

Cause: Required argument was not provided at command line or in the argument file.

Action: Provide a valid argument.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20324: Unsupported character sequence.

Cause: Input value "{0}" had some unsupported characters.

Action: Name must begin with an alphanumeric character; may only contain alphanumeric or underscore (_) or hyphen (-) characters; and must be 4 to 30 characters long.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20325: Invalid packed domain jar file.

Cause: There are four possible causes for an invalid packed domain jar file "{0}": 1. File did not exist. 2. File did not have read permission. 3. It was a zero size file. 4. File path is not absolute.

Action: Provide a valid packed domain jar file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20326: Invalid port number.

Cause: Port number "{0}" was not within the range : {1} - {2}.

Action: Make sure that port is within the range.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20327: Invalid password file.

Cause: The {0} password file {1} did not exist or first line did not contain password.

Action: Provide a valid password file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20328: Invalid domain port.

Cause: The domain port was invalid.

Action: Provide a valid port.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20329: Error in validating "SERVER_CONFIG".

Cause: Value of the config property "{0}" for server "{1}" was "{2}" and was invalid.

Action: Support values are {0}.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20330: Execution of wlst script is not successful.

Cause: An internal operation failed while executing {0} wlst script.

Action: Check the clone log and error file for detailed information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20331: Unable to set listen address of Managed Server to its actual value.

Cause: Execution of the internal script was not successful for Managed Server "{0}".

Action: Check the clone log and error file for detailed information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20333: Error in validating "SERVER_CONFIG".

Cause: All password files specified in config property {0} of server "{1}" were not valid.

Action: Make sure that valid password files are provided.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20334: Invalid domain home location.

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

Action: Provide valid absolute writable path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20335: Error in validating "SERVER_CONFIG".

Cause: All aliases specified in config property {0} of server "{1}" were not valid.

Action: Make sure that valid aliases are provided.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20336: The 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: Starting of Managed Server locally may not be successful.

Cause: Unable to reset listen address of Managed Server "{0}" properly.

Action: Check clone log and error file for detailed information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20340: Error in validating "SERVER_CONFIG".

Cause: There was a mismatch between number of aliases and their keypass files specified in config property {0} and {1} of server "{2}" respectively.

Action: Make sure that number of aliases and keypass files are same.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20341: Error in copyConfig.

Cause: The Administration Server is down.

Action: Make sure that the Administration Server 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: Value of the config property "{0}" for server "{1}" was not in "{2}" format.

Action: Make sure that you have provided correct value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20346: Error in validating port number in "{0}" config group.

Cause: Value of the {0} config proeprty was : {1} ; which was invalid. Possible causes were: 1. The value was either empty or not an positive integer. 2. The port number was not within the range.

Action: Make sure that valid port number is specified for this config property 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-20356: Error in validating "SERVER_CONFIG".

Cause: There was a mismatch in number of servers present under SERVER_CONFIG configGroup of target move plan and source move plan(present inside archive).

Action: Make sure that no server is added or removed in the move plan.
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: Error in starting Managed Server.

Cause: Managed Server({0}) start failed.

Action: Check Managed Server log file for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20359: Error in validating "FILESTORE_CONFIG".

Cause: Specified move plan did not have equal numbers of filestores as compared to the source move plan.

Action: Make sure that neither new filestores are added nor any filestore is removed from the move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20360: Error in validating "FILESTORE_CONFIG".

Cause: Specified filestore name {0} did not exist in the target move plan as compared to source move plan.

Action: Make sure that value of READ_ONLY config property "FileStore Name" is not modified in the move plan.
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 move plan are not correct or the end points are not configured correctly in adapter or application deployment plans.

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

Type: ERROR

Impact: Cloning

CLONE-20362: Connection to Administration Server failed.

Cause: Starting the Administration Server failed. Make sure that the Administration Server parameters specified in the move plan are correct.

Action: Check the Administration Server 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 clone log and error file 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 clone log and error file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20365: Error in executing WebLogic script while updating server, cluster , datasource , machine, and authenticator in packed domain template.

Cause: The possible causes were : 1. The values specified in the move plan were not correct.2. Some "READ_ONLY" properties in the move plan were modified.3. Target Middleware Home was not valid.4. Some internal operation failed.

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

Type: ERROR

Impact: Cloning

CLONE-20366: Domain unpack failed.

Cause: Make sure that values specified are correct.

Action: Check the clone log and error file 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 clone log and error file 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: A possible cause was that the ports of the following servers - {0} - were not available.

Action: Either provide valid free ports or if those servers are targeted to non admin host, then use temporary port range mechanism.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20373: The system temporary directory is inaccessible.

Cause: The system temporary directory "{0}" did not have write permission.

Action: Make sure that system temporary directory has write permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20374: Default domain application directory already exists and is not empty.

Cause: Domain application directory was not provided. The default location "{0}" used by unpack process was not empty.

Action: Possible actions are : 1. If domain application directory is not provided, then its default location "{0}" should not exist or shoould be an empty directory. 2. Provide different domain application directory using "-appDir" command line argument.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20375: Invalid Oracle Home.

Cause: Required files needed for cloning were not found in the Oracle Home {0}.

Action: Make sure that the Oracle Home has the required files for cloning.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20376: Error in validating move plan.

Cause: ConfigGroup "{0}" was either added or removed from the move plan as compared to source move plan.

Action: Make sure that no configGroup is added or removed from the move plan.
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: Unable to include packed domain jar file in the archive.

Cause: Unable to copy user provided packed domain jar file {0} to temporary location {1}. Possible causes were:1. Packed domain jar file was not accessible.2. There was not enough free space at temporary location.

Action: Make sure that the packed domain jar file is accessible and temporary location has enough space.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20379: Move plan validation failed for Network channel configuration.

Cause: Possible causes were: 1. Number of Network channels mismatch. 2. Name of Network channel is changed.

Action: Make sure that Network channels configuration is not added or removed from move plan and name of the Network channel is not altered.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20380: Incorrect domain home.

Cause: PasteConfig operation will fail as following file "{0}" exists.

Action: Rename the file and run T2P operation again.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20381: Error in validating move plan.

Cause: The possible causes were {0}

Action: Make sure that move plan is provided and all the values specified in it are correct.
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 {0} {1} was not valid.

Action: Make sure that valid port numbers are specified in the move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20392: The domain home validation failed.

Cause: The following file {0} did not exist under domain home.

Action: Provide a valid domain location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20393: Error in validating command-line parameter "{0}".

Cause: Path {0} was either not absolute or did not exist.

Action: Provide an absolute path for the command-line parameter "{0}"
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20394: Invalid domain home location.

Cause: Path "{0}" was not absolute or an empty directory.

Action: Provide a valid absolute path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20395: Invalid domain home location.

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

Action: Provide a valid absolute path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20396: The domain home validation failed.

Cause: An attempt was made to perform T2P of "{0}" domain. The specified domain home "{1}" was not a "{0}" domain.

Action: Provide a valid domain location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20397: Error in validating "RDBMS Security Store".

Cause: RDBMS Security Store was not enabled in source domain

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

Type: ERROR

Impact: Cloning

CLONE-20398: Error in validating "RDBMS Security Store".

Cause: {0} for RDBMS Security Store was not valid.

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

Type: ERROR

Impact: Cloning

CLONE-20399: Unable to determine Oracle Home used by the domain home.

Cause: Oracle Home information was missing in "{0}" file present under domain home.

Action: Make sure that the specified domain home is associated with a valid Oracle home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20400: Source Oracle Home location validation failed.

Cause: The source Oracle Home "{0}" did not match the Oracle Home "{1}" used by the domain home "{2}" .

Action: Provide the Oracle home specified in "{0}" file present under domain home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20401: The domain location is invalid.

Cause: The file {0} did not exist.

Action: Provide a valid domain location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20402: The move plan file is invalid.

Cause: The xml file was not a valid multi archive move plan.

Action: Provide a valid xml file for multi archive move plan.
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 clone log and error file 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 move plan file.

Action: Provide a valid xml move plan file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20412: Insufficient arguments.

Cause: An attempt was made to perform "{0}" operation. No argument was provided from the following supported arguments : "{1}".

Action: Provide valid arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20413: Unsupported command argument(s).

Cause: An attempt was made to perform "{0}" operation. Some of the arguments are not supported by this operation on this OS platform. The supported arguments are: "{1}".

Action: Provide valid arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20414: Unsupported command argument(s).

Cause: An attempt was made to perform "{0}" operation of "{1}". Some of the arguments are not supported by this operation. The supported arguments are :"{2}".

Action: Provide valid arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20415: Insufficient arguments.

Cause: An attempt was made to perform "{0}" operation of "{1}". The following required arguments were missing: "{2}".

Action: Provide required arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20416: Arguments combination is invalid.

Cause: An attempt was made to perform "{0}" operation by providing parameters for "{1}" .

Action: Provide valid arguments for a particular type.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20417: Insufficient arguments to decide exact operation.

Cause: An attempt was made to perform "{0}" operation. Unable to decide type of operation from provided arguments. The supported arguments for this operation are: "{1}".

Action: Provide valid arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20418: Invalid path.

Cause: The value provided for argument "{0}" was "{1}". There are five possible causes: 1. The path was not an absolute path. 2. The path did not exist. 3. The path did not represent a file. 4. The file did not have read permission. 5. The file size was zero.

Action: Provide a valid path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20419: Invalid path.

Cause: The value provided for argument "{0}" was "{1}". There are six possible causes: 1. The path was not an absolute path. 2. The path did not exist. 3. The path did not represent a directory. 4. It was an empty directory. 5. The directory represented by the path did not have read permission. 6. If environment is UNIX, the directory represented by the path did not have executable permission.

Action: Provide a valid path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20420: Invalid path.

Cause: The value provided for argument "{0}" was "{1}". There are four possible causes: 1. The path was not an absolute path. 2. The path was already existing. 3. The parent directory did not have write permission. 4. If environment is UNIX, there was no executable permission on the existing directory.

Action: Provide absolute path and make sure that it does not exist and its parent directory is writable.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20421: Invalid integer value.

Cause: The value provided for argument "{0}" was "{1}" and it was not a valid positive integer.

Action: Provide a valid positive integer.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20422: Invalid boolean value.

Cause: The value provided for argument "{0}" was "{1}" and it was not a boolean value.

Action: Provide either "true" or "false".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20423: Invalid password file.

Cause: The value provided for argument "{0}" was "{1}". There are six possible causes: 1. The path was not an absolute path. 2. The path did not exist. 3. The path did not represent a file. 4. The file did not have read permission. 5. The file size was zero. 6. The first line of the file did not contain the password.

Action: Provide a valid password file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20424: Invalid path.

Cause: The value provided for argument "{0}" was "{1}". There are five possible causes: 1. The path was not an absolute path. 2. The path was existing. It was not an empty directory. 3. The path was not existing. Unable to create all the non existing directories. 4. The path was existing. It did not have write permission. 5. If environment is UNIX, there was no executable permission on the existing directory.

Action: Provide absolute path of either a non existing or an existing empty directory and make sure that it is writable.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20425: Archive file is not provided.

Cause: An attempt was made to perform "{0}" operation. Archive file is a mandatory argument.

Action: Provide valid archive file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20426: Archive file is invalid.

Cause: This file was invalid for "{0}" operation. This archive was not created using T2P "{1}" operation.

Action: Provide valid archive file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20427: Oracle Home is invalid.

Cause: An attempt was made to run "{0}" operation of "{1}" domain. The following file {2} was not present under target Oracle Home.

Action: Provide a valid Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20428: 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 not existing. Unable to create all the non existing directories. 3. The path was existing. It did not have write permission. 4. 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 directory and make sure that it is writable.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20429: Oracle Home is invalid.

Cause: An attempt was made to run "{0}" operation of "{1}". The Oracle Home "{2}" was invalid.

Action: Provide a valid Oracle Home location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20430: Invalid string value.

Cause: The value provided for argument "{0}" was "{1}" and it was not a valid string value.

Action: Provide a non-empty value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20432: Invalid path.

Cause: The value provided for argument "{0}" was "{1}". There are five possible causes: 1. The path was not an absolute path. 2. The path was existing. It was not a directory. 3. The path was not existing. Unable to create all the directories. 4. The path was existing. It did not have write permission. 5. If environment is UNIX, there was no executable permission on the existing directory.

Action: Provide absolute path of a directory and make sure that it is writable.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20433: Invalid target Oracle home.

Cause: Target Oracle home was not empty directory.

Action: Provide absolute path of either a non existing or an existing empty directory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20434: Invalid target Oracle home name.

Cause: There are two possible causes for the target Oracle home name {0}:1. Length of the target Oracle home name was {1} and it was not within 2 to 128 characters long.2. target Oracle home name had contained unsupported characters.

Action: Target Oracle home name must begin with an alphanumeric character; may only contain alphanumeric or underscore (_) characters; and must be 2 to 128 characters long.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20435: Error in validating "MACHINE_CONFIG".

Cause: Specified machine name {0} was not unique.

Action: Make sure that unique machine names are specified in the move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20444: Mismatch between archive file and multi archive move plan.

Cause: The archive file used during this pasteConfig operation was not provided during execution of extractMovePlan command.

Action: Execute the 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-20458: Error in executing WebLogic script while adding users and groups to DefaultAuthenticator.

Cause: An internal operation failed.

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

Type: ERROR

Impact: Cloning

CLONE-20459: Unable to set listen port of Managed Servers to its actual value.

Cause: Execution of the internal script was not successful.

Action: Check the clone log and error file for detailed information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20460: Unable to get required free ports from the specified port range.

Cause: Port range "{0}" was not large enough to assign free ports to required Managed Servers from that range.

Action: Increase the port range and execute the pasteConfig operation again.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20461: Error while enabling Network channels.

Cause: Execution of the internal script was not successful.

Action: Check the clone log and error file for detailed information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20504: Invalid domain name in the move plan.

Cause: Domain name "{0}" from move plan was not matching with domain name "{1}" found using domain credentials.

Action: Provide valid domain name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20506: Invalid domain name in the move plan.

Cause: Domain name was empty in the move plan.

Action: Provide valid domain name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20507: Invalid domain location in the move plan.

Cause: Domain location was empty in the move plan.

Action: Provide valid domain location.
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 movement script again.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20511: Unable to retrieve Administration Server Password for domain {0}.

Cause: Either the password file {0} did not exist, or the Administration Server password was empty.

Action: Provide a valid password file for Administration Server Password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20512: Unable to determine Administration Server 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 move plan.

Action: Provide valid Administration Server credentials in the move plan and run the movement script again.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20513: Unable to determine Node Manager credentials for domain {0} from move plan.

Cause: Either one of Node Manager User Name or Node Manager Password for domain {0} was not provided in the move plan.

Action: Provide valid Node Manager credentials in the move plan and run the movement script again.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20514: Unable to retrieve Node Manager Password for domain {0}.

Cause: Either the password file {0} did not exist, or the Node Manager password was empty.

Action: Provide a valid password file for Node Manager Password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20515: Unable to connect to Administration Server for domain(s) {0}.

Cause: The Administration Server for domains(s) {0} was not running.

Action: Bring up the Administration Server for each domain before running the movement script.
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 exist.

Action: Provide an existing password file in which the first line is the password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20519: Error in retrieving password from file {0} .

Cause: The first line of file {0} does not contain a valid password.

Action: Provide an existing password file in which the first line is the password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20520: Error in validating "SERVER_CONFIG".

Cause: Value of the config property "{0}" for server "{1}" was empty.

Action: Provide correct value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20521: Error in validating "Node manager config".

Cause: Value of the config property "{0}" was not in "{1}" format.

Action: Make sure that you have provided correct value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20522: Error in validating "Node Manager Config".

Cause: Value of the config property {0} in Node Manager Config cannot be changed.

Action: Make sure that you have not changed its value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20523: Error in validating "SERVER_CONFIG".

Cause: The file {0} specified via config property {1} for server {2}, either did not exist or is of zero size or is non-readable.

Action: Provide a valid file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20524: Error in validating Node manager listen address and port.

Cause: Node manager listen address and port was invalid in MACHINE_CONFIG configGroup where machineid is "{0}".

Action: Make sure that you have provided correct value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20525: Error in importing metadata.

Cause: Applications for which MDS Metadata import would be perfromed were not in active state.

Action: Make sure that all those applications are in active state.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20526: T2P is not supported for multi tenancy enabled domain.

Cause: Provided source domain was configured with domain partitions.

Action: Remove the partitions from the source domain and re-run "copyConfig".
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 "DATASOURCE" config group.

Cause: In "{0}" datasource, value of the "{1}" config property was empty.

Action: Make sure that valid value is specified for this config property in the move plan.
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: Administration Server was down in the provided source environment. The "copyConfig" operation requires Administration Server to be up and running.

Action: Make sure that Administration Server is up and running.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20607: Error in 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 in 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 in 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 in validating source Node Manager Home.

Cause: Specified source Node Manager Home location is not valid. "nodemanager.properties" file is not present under Node Manager Home location.

Action: Make sure that source Node Manager Home location is correct and all required files are present.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20611: Error in validating source Node Manager Home.

Cause: Specified source Node Manager Home location is not valid. "nodemanager.domains" file is not present under Node Manager Home location.

Action: Make sure that source Node Manager Home location is correct and all required files are present.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20612: Error in executing wlst script.

Cause: {0} did not exist.

Action: Make sure that specified Oracle Home is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20613: Listen port validation failed.

Cause: Specified port, {0} is either not valid or not available.

Action: Provide valid free port.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20614: Node Manager 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 Node Manager should come up.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20616: Domain credentials validation failed.

Cause: Specified domain credentials were not of the source domain location.

Action: Make sure that specified source domain location and domain credentials are valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20617: Error reading MDM URL Resolver configuration.

Cause: MDM URL Resolver configuration file "{0}" could not be read.

Action: Make sure that the file exists and has read permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20618: Error updating MDM URL Resolver configuration.

Cause: MDM URL Resolver configuration file "{0}" could not be updated.

Action: Make sure that the file exists and has write permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20619: OPSS re-association failed.

Cause: Execution of reassociateSecurityStore to target environment failed.

Action: Check the clone log and error file for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20620: Administration Server restart failed.

Cause: Could not restart Administration Server.

Action: Check the clone log and error file and Administration Server logs for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20621: Data source creation failed.

Cause: Error in creating OPSS datasource.

Action: Check clone log and error file for details. Make sure values provided in move plan 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 the clone log file for error details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20624: Error in validating "Node Manager Config".

Cause: Config property name cannot be empty.

Action: Make sure config property names are not modified in move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20625: Unable to find Node Manager configuration.

Cause: Node Manager home location is empty.

Action: Make sure that the Node Manager configuration is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20626: Unable to find Node Manager configuration.

Cause: Node Manager type is empty.

Action: Make sure that the Node Manager configuration is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20627: Error in finding Node Manager configuration.

Cause: Node Manager is not configured correctly for the source domain.

Action: Make sure that the Node Manager configuration is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20628: Error in validating Custom Location Node Manager home.

Cause: Node Manager home location was not provided in the move plan.

Action: Provide valid location for Node Manager home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20629: Error in validating Custom Location Node Manager home.

Cause: Node Manager home location was not an empty directory.

Action: Provide valid location for Node Manager home. It should be either existing empty directory or non-existing.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20630: Error in validating "Node Manager Config".

Cause: Value of the config property {0} in Node Manager Config was not a valid file.

Action: Provide a valid file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20631: Error in starting node manager.

Cause: Node Manager start failed.

Action: Check node manager log file, {0} for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20632: Error in retrieving Node Manager configuration.

Cause: Internal error happened while validating Node Manager configuration.

Action: Make sure the archive provided is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20633: Error in validating "Node Manager Config".

Cause: {0} for Node Manager Config was not valid.

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

Type: ERROR

Impact: Cloning

CLONE-20634: Error in validating "Node Manager Config".

Cause: {0} was not valid config property for Node Manager.

Action: Make sure config property names are not modified in move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20635: OPSS data {0} failed.

Cause: Unable to find "{0} / {1} / {2}" at "{3}".

Action: Make sure these files exist and are accessible.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20636: OPSS data import failed.

Cause: Unable to seed the schema.

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

Type: ERROR

Impact: Cloning

CLONE-20637: OPSS data import failed.

Cause: Unable to add ldap container.

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

Type: ERROR

Impact: Cloning

CLONE-20638: OPSS data {0} failed.

Cause: Unable to update {0}.

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

Type: ERROR

Impact: Cloning

CLONE-20639: Connection to {0} failed.

Cause: There are four possible causes: 1. Server might be down. 2. Credentials provided might be wrong. 3. If only SSL mode is enabled, provide value of "-trustKeyStoreLoc" parameter. 4. Administration port was enabled and that port was not provided.

Action: Make sure server is running and credentials are valid. If SSL port is used, provide value of "trustKeyStoreLoc" and re-run "copyConfig".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20640: OPSS data {0} failed.

Cause: Unable to find "{0}" at "{1}".

Action: Make sure this file exists and is accessible.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20641: An internal operation failed.

Cause: Component registration xml, {0} is not a valid xml file.

Action: Make sure that {0} is a valid component registration xml file and is not corrupted.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20642: Move plan comparison failed.

Cause: The move plan xml passed in the argument does not contain the same metadata as the one present in archiveMetadata property "{0}" from argument move plan is "{1}" Metadata property "{0}" from archive move plan is "{2}"

Action: Make sure the move plan is actually generated from the archive passed in the argument.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20643: Additional parameter format not valid. The value provided for argument "{0}" was "{1}"

Cause: There are three possible causes: 1. Parameter value may be null. 2. Parameter value is not a key-value pair. 3. If more than one key-value pair is passed, they may have not been separated using a ,(comma).

Action: Make sure that the additional parameter uses the proper syntax. Syntax : -additionalParams property1=value1,property2=value2 Example: -additionalParams server=orclSv1,port=8888 Note:','(comma) and '='(equal) characters cannot be directly used within the key or value. They can be used by replacing them with the escape character as mentioned below ','(comma) -> %2C '='(equal) -> %3D Example: -additionalParams server=srv1%2CfailoverServer%3Dsrv2,ports=8888%2C8881
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20644: Invalid passphrase file.

Cause: The passphrase file {0} specified via config property {1} for server {2}, either did not exist or first line did not contain passphrase.

Action: Provide a valid passphrase file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20645: Mismatch between domain credentials and domain location.

Cause: The provided domain location "{0}" was different from the domain location "{1}" found from domain by using domain credentials.

Action: Make sure that specified source domain location and domain credentials are in sync.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20646: Target domain location validation failed.

Cause: Target domain directory name, {0} contains invalid characters.

Action: The specified domain directory name must include only alphanumeric characters, hyphens ('-') or underscore characters ('_'). The domain directory name must contain at least one letter or digit.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20647: {0} listen address validation failed.

Cause: Specified listen address, {0} is not a local machine address.

Action: "pasteConfig" is run on domain Administration Server machine. Specify valid local ip address for {0} listen address.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20648: Java vendor and version validation failed

Cause: The Java vendor and version of the target environment ({0}) is different from the source environment ({1})

Action: Make sure that the Java vendor and major version of the target environment is same as source environment. Example: Oracle Corporation 1.8
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20649: Invalid value.

Cause: The {0} value is empty.

Action: Provide a valid value for {0} property.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20650: Unable to identify the Node Manager home from move plan and hence skipping Node Manager configuration.

Cause: There are two possible causes: 1. The Node Manager home is empty. 2. The Node Manager home does not exist.

Action: There are two possible actions: 1. If the Node Manager home was left empty intentionally, then it is safe to ignore this warning message. 2. If the specified Node Manager home does not exist, it can be manually setup after the pasteConfig operation is completed.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20651: Node Manager configuration could not be retrieved and hence skipping Node Manager configuration.

Cause: There are two possible causes: 1. The Node Manager is not configured for this domain. 2. The Node Manager home could not be identified.

Action: There are two possible actions: 1. If the Node Manager is not configured for this domain, then it is safe to ignore this warning message. 2. If the Node Manager home could not be identified, it can still be configured for target domain by providing an existing Node Manager home in move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20652: Import keystores to kss is not successful.

Cause: Import operation failed.

Action: Check clone log file for exact cause.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20653: Move plan is invalid.

Cause: ConfigGroup of type {0} is missing from the move plan.

Action: Provide valid move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20654: Error in validating "DATASOURCE".

Cause: Unable to connect to datasource "{0}".

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

Type: ERROR

Impact: Cloning

CLONE-20655: Error in validating "DATASOURCE".

Cause: Invalid driver class "{0}" specified for datasource "{1}". Failed to load specified driver class.

Action: Make sure that correct driver class is provided in the move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20656: Error in validating server listen address.

Cause: The following servers: {0} did not have the same type of listen address as the other servers: {1}.

Action: All servers in the move plan should have same type of listen address. Example: Hostname, IPV4 IP address or IPV6 IP address. There cannot be a mix of these three address types. Make sure that valid values are provided in the move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20657: Error in validating "FILESTORE_CONFIG".

Cause: Specified directory "{0}" for filestore "{1}" was not valid. There are two possible causes: 1. It was empty. 2. Path was absolute but either not a directory or not writable.

Action: Provide valid filestore directory. It needs to be either a relative path to domain home or an absolute writable directory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20658: Admin user validation failed.

Cause: Admin user "{0}" was not a direct member of Administrators group.

Action: As Admin user is present in embedded ldap, user needs to be a direct member of Administrators group.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20659: Configure Wallet operation failed.

Cause: Make sure that values specified were correct.

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

Type: ERROR

Impact: Cloning

CLONE-20660: Oracle Home is invalid.

Cause: Unable to find T2P plugins for following system component types : {0} .

Action: Provide valid Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20904: Error happened while shutting down the Managed Servers. Check the clone log and error file for details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20905: OPSS store re-association from {0} to {1} is not supported. OPSS store will not be re-associated to {2}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20906: OPSS store re-association values are not provided. Source domain OPSS store will be used for unpacked domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20907: {0} Details provided for OPSS configuration is same as source domain. Re-association will not be executed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20908: Deployment plan ({0}) specified for {1} does not exist. {2} will not be added to the move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20909: Application deployment plan ({0}) specified for {1} does not exist. {2} will not be added to the move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20910: Default Authenticator data export failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20911: Default Authenticator data import failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20913: {0} is not a valid configProperty for {1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20914: Exception caught while creating move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20915: Exception occurred while trying to write FMWClonerBean to File.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20916: Exception occurred while trying to write CopyArgBean to File.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20917: Exception occurred while deserializing FMWClonerBean from File.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20918: Exception occurred while deserializing CopyArgumentBean from File.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20919: Error in enrolling Node Manager with domain {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20920: Node Manager default startup script {0} does not exist.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20921: Unable to start the Node Manager.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20923: Error in examining OWSM targets. Verify that OWSM targeting is fine post pasteConfig.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20924: Unable to establish a connection to the MBean server to verify an active edit session. Make sure that an edit session is not active in the domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20925: Error in validating RDBMS security store properties. Could not establish connection to the RDBMS security store.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20928: "pasteConfig" operation of standalone domain failed. Check the clone log and error files for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20929: "copyConfig" operation failed for {0} plugin. Check the clone log and error files for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20930: Found invalid "configProperty", {0} for {1} configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20931: Error occurred while adding default realm data to archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20932: Error occurred while extracting default realm data from archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20933: optimizationHints argument is required during extract move plan for multi archive mode. Use -optimizationHints (-opth) option to specify optimization hints.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20934: At least one valid optimization flag has to be specified. Flag(s) provided are : {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20935: "pasteConfig" operation of Node Manager failed. Correct the error before running the utility again. Also target Node Manager Home, {0} will be in an unusable state, so delete the directory before re-running "pasteConfig".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20936: "pasteConfig" operation failed for {0} plugin. Check the clone log and error files for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20937: "pasteConfig" operation of J2EE domain failed. Check the clone log and error files for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20938: Error occurred while handling component plan validation event handler. Message: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20939: Error at column {0}, line {1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20940: Error occurred while handling move plan validation event handler. Message: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20941: Unable to validate domain connection , and exception is = {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20942: The wlst error for configuring {0} is {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20943: An error occurred while running the wlst offline command to update the server configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20944: An error occurred while running the wlst offline command to update the server administration port configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20945: An error occurred while running the wlst offline command to update the server frontend configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20946: An error occurred while running the wlst offline command to update the server default filestore configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20947: An error occurred while running the wlst offline command to update the server custom identity keystore configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20948: An error occurred while running the wlst offline command to update the server custom trust keystore configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20949: An error occurred while running the wlst offline command to update the custom identity private key configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20950: An error occurred while running the wlst offline command to update the cluster configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20951: An error occurred while running the wlst offline command to update the datasource configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20952: An error occurred while running the wlst offline command to update the datasource configuration for OnsNodeList.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20953: An error occurred while running the wlst offline command to update the datasource configuration for OnsWalletFile.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20954: An error occurred while running the wlst offline command to update the authenticator configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20955: An error occurred while running the wlst command to reassociate security store.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20956: An error occurred while running the wlst offline command to update the machine configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20957: An error occurred while running the wlst offline command to update the system component configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20958: An error occurred while running the wlst offline command to update the SSL configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20959: An error occurred while running the wlst command to import default authenticator data.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20960: An error occurred while running the wlst command to import application metadata.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20961: An error occurred while running the wlst command to export application metadata.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20962: An error occurred while running the wlst command to configure deployment plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20963: "copyConfig" operation of J2EE domain failed. Check the clone log and error files for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20964: "copyConfig" operation of standalone domain failed. Check the clone log and error files for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20965: An error occurred while importing keystore certificates to OPSS Service.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20966: An error occurred while setting keystores of server.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20967: An error occurred while running the wlst offline command to update the server log file location.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20968: An error occurred while running the wlst offline command to update the coherence configuration of server.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20969: An error occurred while running the wlst offline command to update the filestore configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20970: An error occurred while running the wlst online command to export Default Authenticator data.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20971: An error occurred while running the wlst offline command to update the listen address of the server.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20972: An error occurred while running the wlst offline command to update the network channel configuration of the server.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21001: Domain {0} is a WebLogic managed domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21002: Domain {0} is a standalone domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21003: Execute "{0}" command using the movement script to see the exact help message.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21004: Some files are missing. Check the clone log file to see all the missing files.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21006: Total time taken by T2P process was {0} seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21007: Cloning operation completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21008: Cloning operation completed with warnings.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21009: Updating permission of files in Oracle home {0}, if required ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21010: Permissions of all files in Oracle home {0} are correct. Nothing to update.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21016: Adding Oracle Home "{0}" binaries to the archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21017: Adding Oracle Home binaries to the archive finished.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21018: Extracting Oracle Home binaries from the archive at "{0}" location started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21019: Extracting Oracle Home binaries from the archive finished.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21020: Configuration of Oracle Home is in progress ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21021: Configuration of Oracle Home completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21022: Applying permission for {0} started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21023: Applying permission for {0} finished. Operation complete in "{1}" seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21024: A configuration script needs to be run as root at the end of clone operation. Run "{0}/oracleRoot.sh" as root.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21025: Validating permission of all files in new Oracle Home ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21026: Permission of all files in new Oracle Home are correct.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21028: Unable to find component detail from Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21029: Unable to find top component detail from Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21030: Adding "{0}" to the archive is successful.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21031: Time taken to add all the cloners to archive was "{0}" seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21032: Archive created successfully at {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21035: Restoring the home finished successfully at {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21036: Restoring the component finished successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21037: Time taken to restore all cloners from archive was "{0}" seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21039: Gathering all sourceid(s) present in the archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21040: Oracle Home archive # {0}, home location {2}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21042: Component archive # {0}, instanceName@componentName {1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21044: Unable to find JRockit JAVA HOME from registry.xml file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21045: Permission file created successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21046: Permission file creation failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21047: Permission for new Oracle Home {0} is not set properly, and permissionFilePath relative to Oracle Home is {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21048: Adding all required files to the main archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21049: Canonical path of the following files did not exist, and their absolute path is:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21050: List of files without read permission:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21051: Adding permission file to the archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21052: Adding permission file to the archive finished. Operation completed in "{0}" milliseconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21053: Total size of the file(s), to be included in the main jar from source location {0}={1} GB.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21054: Unable to read "{0}" file while adding files to the jar file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21056: Time taken for adding files to archive was {0} seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21057: Execution of system prerequisites started from directory "{0}" ...

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-21067: Unregistering all asinstances(which were present in source domain) from target domain ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21068: Trying to unregister asinstances {0} from domain ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21069: All the asinstances are unregistered from domain successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21071: Permission file created with warnings.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21081: Parsing move plan to get component name and component type ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21082: Parsing multi archive move plan ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21083: Creating updated move plan for component name "{0}" and component type "{1}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21084: Checking if any config property still has a reference to another config property.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21085: Updating component specific move plan from multi archive move plan ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21086: Updating component specific move plan from multi archive move plan 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: To execute {0} operation(s), press any key to continue:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21089: Status of the server is {0} . Press any key to continue:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21090: To proceed, press any key :

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21092: For help on a particular command, use [ <path to java> -jar <path to cloningclient.jar> -help <command>]

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21093: To proceed enter "yes", or any other text to abort:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21094: Clone operation was aborted.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21095: Create archive for {0} started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21105: Archive is invalid as it has home(s) and component(s).

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21106: Execution of system prerequisites has completed with warnings and/or to be verified. To proceed enter "yes", or any other text to abort:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21118: Adding symbolic link files detail to the archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21119: Adding symbolic link files detail to the archive finished. Operation complete in "{0}" milliseconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21122: File "{0}" is missing.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21125: All the symbolic link files are present in the Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21126: Operation is {0}% complete, in "{1}" seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21127: Performing inventory validation ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21128: Performing symbolic link files validation ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21129: Performing source Oracle Home reference validation ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21130: No file has any reference to source Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21131: Inventory validation is successful.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21141: CloningClient build label is "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21142: CloningClient version is "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21143: Log File: "{0}". Error File: "{1}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21144: Unable to create log directory {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21145: The message id "{0}" is invalid for message type {1}, It did not start with "CLONE", or it did not end with "-INFO" where message type=INFO or it did not end with "-TRC" where message type=TRACE or it did not end with "-SVR" where message type=SEVERE or it did not end with "-ERR" or "-CAUSE" or "-ACTION" where message type=ERROR or its length was not be equal to "{2}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21146: Oracle Home {0} is registered with the Oracle Inventory {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21147: Oracle Home {0} is registered by the name "{1}" with the Oracle Inventory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21148: Oracle Home {0} passed post validation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21149: Oracle Home {0} failed post validation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21154: Checking for availability of {0} MB free space at {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21155: Required free space is available.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21156: Extracting OUI and engine binaries to temporary location ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21157: OUI and engine binaries are extracted to temporary location successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21158: Validating if Oracle Home location is already registered with Oracle inventory ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21159: Oracle Home location is valid as it is not yet registered with the Oracle inventory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21160: Validating if Oracle Home name "{0}" is already registered with Oracle inventory ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21161: Oracle Home name "{0}" is valid as it is not yet registered with the Oracle inventory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21162: This Oracle home is not registered with the OraInventory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21163: Adding details regarding files without read permission to the archive, started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21164: Adding details regarding files without read permission to the archive, finished. Operation complete in "{0}" milliseconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21165: In the source Oracle Home, some files have no read permission. Those files are not present in the cloned Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21166: Permission of all files in new Oracle Home is not correct and details can be found at {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21173: Unable to find Oracle home name from inventory; configuration did not happen properly for Oracle home {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21174: Configuration of Oracle home {0} will be started again after delay of {1} milli seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21175: Configuring Oracle Home {0} again (re-attempt={1}) ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21176: Configuration of Oracle Home {0} in clone mode will not be performed anymore as it has reached its maximum number of retries({1}).

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21193: Error while parsing "{0}" password file: "{1}" for password.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21196: The port "{0}" is free for use.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21197: The port "{0}" is not free for use.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21198: Trying to use source port "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21199: Trying to get a new port between lower port {0} and higher port {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21200: Unable to calculate new port.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21201: New value for port "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21203: The {0} password file: "{1}", either does not exist or is zero size.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21204: ERROR

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21205: CAUSE

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21206: ACTION

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21207: {0} T2P Summary Begin{1}{2}{3}{4} T2P Summary End{5}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21208: Error Message

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21209: Warning Message

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21210: WARNING

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21216: Performing post operation, if any ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21217: Post operation completed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21218: Post operation failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21221: SEVERE

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21223: Deleting half-created archive file ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21226: Creating move plan ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21227: Extracting 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 Node Manager 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 move plan.

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 if 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. Administration Server will now be restarted.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21266: {0} does not appear to contain an obfuscated password. Assuming plaintext ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21267: Failed to create the deployment plan file at specified location for application "{0}". Copying the deployment plan file to "{1}"

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21268: Examining Node Manager configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21269: Validating Node Manager config properties.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21270: Configuring Node Manager.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21271: Validation of node manager config properties failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21272: {0} OPSS data ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21273: Examining Coherence Server configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21274: Examining Coherence Cluster configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21275: Validating Coherence Server configuration to update domain template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21276: Validating Coherence Cluster configuration to update domain template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21277: Failed to create the deployment plan file at specified location for adapter "{0}". Copying the deployment plan file to "{1}"

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21279: Warning: The following optimizationHints flag(s) are not supported and hence ignoring - {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21280: Warning: -domainAdminPassword argument has been deprecated. Use -domainAdminPasswordFile instead.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21281: Ignoring the argument {0} for this operation

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21282: Warning: MDS Import of following applications failed. {0}. Check Managed Server and the clone log for details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21283: Warning: MDS export of some applications failed. Check the following list of applications and verify that MDS data is not associated with these applications. {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21284: Warning: Java vendor information is missing.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21285: Warning: Java version information is missing.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21286: Warning: Unable to save Java vendor and version information into manifest file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21287: Warning: Exception occurred while fixing file {0} SRC : {1} TAR : {2}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21288: Warning: Invalid Oracle home as unable to find Oracle home name from inventory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21289: Warning: OUI major version is not {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21290: Warning: File {0} will not be archived as it is locked by other process.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21291: Warning: File {0} will not be archived as unable to read.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21292: Examining Server Template configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21293: Validating Server Template configuration to update domain template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21294: Updating Node Manager username and password.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21295: Warning: Unable to load {0}, skipping the validation for datasource {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21296: Source Id is invalid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21297: Unable to find the move plan file or is an invalid configuration archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21298: Bad log level {0} was set via T2P system property {1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21299: Empty command array for execution

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21300: Unable to derive move plan from move plan file {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21301: Unable to derive move plan from multi archive move plan {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21302: Unable to determine Source Id.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21303: Error while validating FMWClonerBean parameters.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21304: Validation failed for {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21305: Required oui classes are not available in class path and location of oui jar files is invalid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21306: Unable to load oui jars.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21307: Inventory pointer location file is invalid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21308: Inventory location specified in invPtrLoc file {0} is invalid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21309: Invalid Oracle home {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21310: Unable to update java library path.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21311: Exception occurred after reading file atleast once.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21312: Entryname cannot be empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21313: Required oui and engine binaries are not extracted properly from the archive under {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21314: Unable to archive oui,engine and ojdl binaries to archive file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21315: Unable to extract packed domain jar file from archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21316: Failed to unpack the domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21317: PasteConfig in offline mode failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21318: Unable to populate domain specific move plan from multi archive move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21319: PasteConfig in online mode failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21320: Unable to get domain runtime connection.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21321: Somebody else is already editing.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21322: Import keystore commands to kss is empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21323: Server list is empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21324: Failed to create the data source

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21325: Unable to locate {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21326: Deployment plan provided for adapter {0} is not a valid file

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21327: Failed to write the deployment file location to a property file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21328: Failed to load the deployment file location from property file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21329: Deployment plan provided for application {0}, is not a valid file

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21330: Error validating Component Create Clone Info object.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21331: Error in importing DefaultAuthenticator

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21333: Invalid configGroup present in target move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21334: Invalid number of servers present under SERVER_CONFIG configGroup in target move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21335: Keystore properties of some or all servers are incorrect.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21336: Listen ports specified for all servers in move plan are incorrect.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21337: Keystores are invalid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21338: Invalid configGroup.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21339: Invalid configGroup as its type is not {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21340: Error in validating command line parameters. Check log for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21341: Error occurred while trying to derive WebLogic Server Home and Java Home. Check log for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21342: Error occurred while updating {0} file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21343: Error occurred while registering Node Manager with each domain. Check log for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21344: Unable to derive Node Manager specific move plan from multi archive move plan {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21345: Unable to retrieve the Copy Argument Bean.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21346: Unable to retrieve the source Node Manager Home location from Bean.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21347: T2P action type was empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21348: T2P action type {0} is unsupported.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21349: Move plan file is invalid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21350: Unable to get URL representation of move plan xsd file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21351: Move plan is invalid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21352: Move plan is empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21353: Move plan path is empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21354: Move plan representation of the String is empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21355: Multi archive move plan file is either empty or does not exist or not readable.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21356: Unable to get URL representation of multi archive move plan xsd file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21357: Multi archive move plan is empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21358: Archive contains an invalid move plan because either ComponentName or componentType is empty in the move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21359: Invalid multi archive move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21360: Multi archive move plan contains no configurable properties.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21361: Multi archive move plan contains no READ_WRITE config properties. It is an invalid plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21362: Tpid is empty in multi archive move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21363: Tpid is corrupted in move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21364: Tpid {0} is corrupted in move plan as it has not matched key {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21365: Internal multi archive move plan is corrupted.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21366: Tpid is empty in internal multi archive move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21367: Unable to build multi archive move plan from multi archive move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21368: Unable to create moveplan_id.xml for {0} under {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21369: Unable to build move plan from multi archive move plan for {0} of type {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21370: Invalid multi archive move plan; source had file based OPSS, but multi archive move plan has empty or less number of OPSS.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21371: Unable to find proper mapping for file based OPSS from multi archive move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21372: Invalid port value: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21373: Port value is empty

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21374: Port value {0} contains non integer values.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21375: Port value {0} is not within the range.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21376: Unable to check port availability on {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21377: Invalid port range.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21378: MBeanServerConnection is null.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21379: All servers targeted to {0} seems to be down.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21380: File object cannot be null.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21381: An error occurred while copying the file: {0} to destination: {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21382: The persisted string is empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21383: The target file is invalid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21384: No write permission at {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21385: ERROR : The StartUtil DLL needs to be provided for starting WebLogic on Windows. The cloningclient jar might be invalid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21386: {0} stop failed

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21387: Stopping the Administration Server failed

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21388: Introspection of server configuration failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21389: Empty command array for execution

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21390: Empty command

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21391: Error in getting MBeanServerConnection.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21392: Error in getting JMXConnector object

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21393: Error in closing MBeanServerConnection.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21394: Node Manager type is {0}. Node Manager user name is same as compared to its source environment. As Node Manager password file was not provided, default value will be domain password file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21395: Node Manager Type is {0}. Update of the Node manager credentials in the domain will not be performed due to missing of Node Manager user name or password.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-22001: CreateClonerInfo object should not be empty at this point.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22002: Source type "{0}" was either empty or was not supported.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22003: The provided cloneType="{0}", does not match the required clone type "{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22004: ApplyClonerInfo object should not be empty at this point.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22005: Either cloneType="{0}" or visible sourceid="{1}" or actual sourceid="{2}" is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22008: During apply cloner object(s) build, all the sourceid(s) in the archive are {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22010: The archive entry point in the jar is="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22017: No cloner object was found.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22018: Setting actual sourceid for all cloner objects.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22019: Adding all sourceid(s) to the jar file started ...

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22020: Adding all sourceid(s) to the jar file finished.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22025: The content of the sourceid file is {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22040: The jar file path={0} is invalid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22041: Path represented by "{0}" was not a directory.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22042: Path represented by "{0}" did not exist.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22043: Path is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22044: Unable to create file "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22045: Directory {0} was not empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22046: File object is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22047: The specified path "{0}" is not a file.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22048: The file "{0}" is of zero size.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22049: The file "{0}" is not a directory.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22052: Target location {0} is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22053: The jar output stream is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22054: The exclude pattern of the files which will not be included in archive={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22055: Generating exclude file pattern list, if any pattern is provided.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22057: Generating list of files to be included.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22058: The statistics of the files are: Total number of files={0}. Non-readable files={1}. symbolic link files={2}. Exclude pattern={3}. Exclude pattern actual={4}. Included files only={5}. Included empty folders only={6}. Nonempty folders={7}. Invalid absolute path whose canonical path does not exist={8}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22061: The archive entry point={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22062: Counter={0}, and excluded file through file pattern is {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22063: The time taken for unarchiving the entry from main jar={0} milliseconds.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22064: Either jar file path or entryNameToBeExtracted or target location is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22065: The statistics of files whose permission will be handled:

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22066: The number of files with root privilege={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22067: The number of symbolic link files={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22069: The root privilege files are:

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22071: File permission is invalid where visible permission is={0} and its calculated permission is={1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22072: Permission file {0} was already existing, so it will be deleted.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22073: The command "ls -alR" is executed properly, and temporary file was {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22074: The command "ls -alR" is not executed properly, and temporary file was {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22075: Unable to generate document object from the xml file {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22076: The domainHost={0}, domainPort={1}, domainAdminUserName={2}, domainAdminPassword={3}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22077: The WebLogic home "{0}" was invalid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22078: The WebLogic jar "{0}" was invalid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22079: The Oracle Home "{0}" was invalid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22085: No parameter(s) should be empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22088: The jmx_connector is valid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22089: Connection obtained successfully.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22090: Unable to get server connection.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22094: Domain home {0} is configured with following system components : {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22140: Parameter validation is complete. Sourceid is set to : "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22141: Parameter validation is complete. TargetLocation is set to : "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22142: Parameter validation is complete. Sourceid map is set to : "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22152: parent_of_prereq="{0}", path_upto_oui="{1}", libDir_for_oui="{2}", platform_for_prereq="{3}", oui_lib_dir="{4}", sPrereqDir="{5}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22153: Before setting system environment property, prereq_bootstrap_dir="{0}", bootstrap_dir="{1}", prereq_config_loc="{2}", prereq_log_dir="{3}", oracle_install_scratch_path="{4}", oracle_install_lib_loc="{5}", oracle_install_engine_mode="{6}", java_lib_path="{7}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22154: To run prerequisites, oui lib directory is "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22156: To run prerequisites, platform_directory under prereq folder is "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22157: Operating system name="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22158: No jar will be added to system class loader as jarlist is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22159: Checking if 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 successfully added to System class loader.

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 if the following classes are available or not {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22165: Adding engine jars to system classloader from Oracle Home {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22166: Status of adding engine jars to system classloader from Oracle Home {0} is="{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22167: Adding oui jars to system classloader from {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22168: Status of adding oui jars to system classloader from {0} is="{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22169: Adding both engine and oui jars to system classloader.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22170: Status of adding both engine and oui jars to system classloader is="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22171: Adding oui jars from Oracle Home {0} to system class loader to know Oracle Home details.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22172: Trying to retrieve the top component name from Oracle Home {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22174: Extracting prerequisites jars under {0} location.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22175: Invoking engine prerequisites launcher.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22176: Status of parsing command-line argument="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22177: Status of first validation of command-line argument="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22178: Status of second validation of command-line argument="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22184: List of all valid symbolic link files is as follows.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22185: In file description "{0}", the first character is not "l", but has String "->"; assume it is symbolic link file.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22188: Adding jars from {0} to system class loader.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22189: Status of adding jars from {0} to system class loader is "{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22193: Updating file {0} where key={1} and value={2}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22194: Status of updating file {0} where key={1} and value={2}, is {3}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22195: All inputs from command-line are: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22199: List of all symbolic link files is as follows.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22200: Setting invPtrLoc with InventoryManager with user input value {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22204: OraInstaller library path={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22206: Size of the home {0}={1} byte or "{2}" MB.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22207: For location {0}, free space required="{1}" MB, and the available free usable space="{2}" MB.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22209: Number of entries in the file, which will contain all valid symbolic link files detail={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22211: Validating existence of symbolic link file by checking absolute path and canonical path.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22212: The command "{0}" is not executed properly, and temporary file was {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22217: {0}, file "{1}" is missing.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22218: During file existence check, number of files present={0} and number of file absent={1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22224: For sourceid="{0}", the target location="{1}", and space required="{2}" MB.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22238: Rename status of source file {0} to target file {1} is {2}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22239: Delete status for file {0} is {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22240: Before updating file, sourcefile="{0}", old value="{1}", new value="{2}" and temporary file="{3}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22241: Trying to overwrite the content of source file "{0}" into the target file "{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22242: From the inventory {0} , Oracle Home locations and their corresponding names are as follows: {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22244: Directory "{0}" was empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22245: Prereq execution result as follows: AllPrereqChecksCount ="{0}", prereqSuccessCount ="{1}", prereqFailedCount ="{2}", WarningsCount ="{3}", UserVerifyCount ="{4}", List of All Checks ="{5}", List of checks passed ="{6}", List of checks failed ="{7}", List of Warning checks ="{8}", List of checks to verify="{9}", List of checks to Retry ="{10}", Prereq Summery ="{11}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22247: Number of files with "no read access permission"={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22248: The file "{0}" was non-readable in the source Oracle Home, and now it is available in the cloned Oracle Home.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22249: ERROR, for the symbolic link path "{0}", the required canonical file {1} is not present.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22250: ERROR, the symbolic link path "{0}", did not exist.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22251: ERROR, for the symbolic link path "{0}", the absolute path {1} and canonical path {2} are same, which is incorrect.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22252: ERROR, for the symbolic link path "{0}", the canonical path {1} and required canonical path {2} are different, but should be same.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22253: Counter={0}, absolute path="{1}" and required canonical path="{2}"

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22254: The input from the user was="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22257: Unable to set the permission of the file {0} to {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22260: Executing following command: {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22262: Primary validation prior to clone operation is successful for {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22263: Restoring for the sourceid "{0}" started at {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22264: Time taken to restore sourceid "{0}" is "{1}" milliseconds.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22265: Adding cloningclient.jar to Archive.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22266: "StartupMode" is not set in move plan. Assuming PRODUCTION Mode.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22267: Extracted MDS metadata to {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22268: No MDS data found in archive. Skipping metadata import.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22269: Adapter deployment plan location is {0}. Make sure that configurable parameters specified in {1} deployment plan are correct.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22270: Commented OPSS_SECURITY "configGroup".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22271: OPSS_SECURITY "configGroup" commenting failed.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22274: Setting Listen Address of {0} to localhost to start it locally.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22275: Setting Listen Address of {0} to {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22277: Removing front end url setting for {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22278: Setting front 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-22285: Adding Node Manager files to archive.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22286: Derived WebLogic Server home to be {0} and Java Home to be {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22287: Loading Jar {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22288: Move plan has no Node Manager movable component.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22289: Number of Node Manager Movable Components is {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22290: Mismatch in number of Movable Components of node manager from derived and visible.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22291: Deriving node manager properties of {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22292: Retargeting owsm application and data sources.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22293: Detected CommonDomain. Exporting Fusion Apps Global Partition MDS docs..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22294: Not detected as CommonDomain. Fusion Apps Global Partition MDS docs will not be exported..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22295: Detected CommonDomain. Exporting ESS Global Partition MDS docs..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22296: Not detected as CommonDomain. ESS Global Partition MDS docs will not be exported..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22297: Detected CommonDomain. Exporting ESS Internal Partition MDS docs..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22298: Not detected as CommonDomain. ESS Internal Partition MDS docs will not be exported..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22299: Export location for embedded LDAP data = {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-23001: Copyright (c) 2004, 2015, Oracle and/or its affiliates. All rights reserved.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23002: Usage: Run {0} script with following parameters:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23003: Options(alias) with multiple names separated by comma:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23004: Absolute path of java home directory

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23005: T2P process cannot be executed without java home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23006: Absolute path of archive file

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23007: The archive file should not exist.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23008: Absolute path of Oracle Home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23009: To create archive of this Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23010: Absolute path of inventory pointer loc i.e. oraInst.loc

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23011: This argument is ignored from 12.1.2.0.0. It is used to validate source Oracle Home. Internally it is calculated. In case of unix, it is ORACLE_HOME/oraInst.loc. In case of Windows this argument is not required.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23012: Absolute path of a directory

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23013: Cloning log and error file will be created under this directory. Default location is system temporary location.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23014: Flag to run the T2P operation in a non-interactive mode. Default value is true.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23015: Flag for ignoring the results of free space check. Default value is false.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23016: Description:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23017: To create an archive of Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23018: Example:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23019: Usecase-{0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23021: Command:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23022: Requirement

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23023: The movement scripts require a minimum of Java version of 1.8 However, for the exact JRE version certified for the product, Refer to the System Requirements and Supported Platforms document, which is located at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23024: Assumption:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23025: NOTE:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23030: Absolute path of the target Oracle Home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23031: Absolute path of an existing archive file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23032: This argument is mutually exclusive with "{0}" argument.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23033: Flag to execute system prerequisites before restoring the Oracle Home. Default value is true.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23034: Absolute path of inventory pointer file

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23035: This flag is supported in UNIX platforms only. Default value is {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23036: This file has pointer to central inventory. Oracle Home will be registered with that central inventory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23037: The invPtrLoc should point to a file which contains the following information.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23038: Additional session variable for OUI runInstaller. Variables need to be passed as key=value pair.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23039: More than one session variable should be separated using comma (,).

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23040: In Windows, provide whole value within double quotes("").

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23041: Oracle Home name that will be used to register Oracle Home with the central inventory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23042: Flag to reconfigure an already existing Oracle Home(created using flexClone mechanism). Default value is false.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23043: Either to restore and configure the Oracle Home using an archive or reconfigure an Oracle Home created via flexClone mechanism.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23044: Make sure that the Oracle inventory has no entry for the target Oracle Home and target Oracle Home name.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23045: Restore Oracle Home from an archive

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23046: Archive was created using copyBinary script. Path specified for target Oracle Home needs to be either a non existing or an existing writable directory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23047: Reconfigure an already existing Oracle Home created using flexClone mechanism

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23048: The target Oracle Home exists. Binaries are moved from source to target using flexClone mechanism.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23049: The target Oracle Home location cannot be inside another Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23060: WebLogic managed domain specific parameters

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23061: Absolute path of source WebLogic domain

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23062: To capture configuration of this domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23063: Source domain Admin Server Host Name

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23064: Source domain Admin Server Port

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23065: Source domain Admin Server User Name

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23066: Absolute path of source domain Admin server user password file

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23067: Absolute path of Custom Trust KeyStore File

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23068: Additional parameters required for product specific operations. They must be passed as key=value pairs.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23069: Multiple parameters should be passed by separating each key=value pair by a comma (,).

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23070: In Windows, provide whole value within double quote("").

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23071: Standalone domain specific parameters

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23072: Absolute path of source standalone domain

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23073: Node Manager specific parameters

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23074: Absolute path of source Node Manager home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23075: If this argument is not provided, copyConfig utility will try to calculate the same.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23076: In case of failure to compute the argument, provide the argument explicitly.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23077: To create archive of a WebLogic managed domain or a standalone domain or a Node Manager.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23078: This Oracle Home needs to be associated with the domain specified via argument {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23079: Use this parameter if the -domainPortNum parameter represents either SSL or administration port and keystores of Administration Server is either {0} or {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23081: To create archive of {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23082: Target domain Admin Server User Name

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23083: It can be same or different from source env.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23085: Absolute path of an existing target Oracle Home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23086: Absolute path of the T2P move plan

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23087: Absolute path of the updated T2P move plan xml document (extracted during {0} operation).

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23088: Refer to the Chapter "Moving from a Test to a Production Environment" in Administering Oracle Fusion Middleware Guide for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23089: Absolute path of target WebLogic managed domain

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23090: Path can be either a non existing or an existing empty directory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23091: Absolute path of target domain Admin server user password file

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23092: Absolute path of target J2EE domain application directory

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23093: Absolute path of target Node Manager home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23094: To restore the full archive containing a WebLogic managed domain or a standalone domain or a Node Manager.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23095: To restore archive of {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23096: Absolute path of target Standalone domain

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23097: when additional parameters are required by some products to complete copyConfig operation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23098: Absolute path of target standalone domain application directory

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23101: Absolute path of the existing archive files.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23102: If multiple archives are provided, provide them as a comma separated list. (In Windows, provide the comma separated list within double quotes)

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23103: Absolute path to directory where move plan is to be extracted

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23104: The move plan and/or multi archive move plan will be extracted along with other J2EE Configuration Plans.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23105: Flags for optimization while creating move plan from single or multiple archives

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23106: Provide the flags as a comma separated list. (In case of Windows, provide the comma separated list within double quotes)

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23107: The supported values are :{0} and the aliases for these flags are {1} respectively.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23108: Based on flag, specific optimization of multi archive move plan will take place.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23109: Flag description:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23110: You need to provide this hint always. This simplifies the move plan(s).

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23111: The same password is used for all schemas associated with a particular database specified in {0} section of the move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23112: The passwords for APPID users are different. You are prompted to provide the password only once for each database.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23113: You need to pass a separate password for each of the APPID users.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23114: The same password is used for all schemas associated with a particular database specified in {0} section of the move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23115: If {0} flag is provided, then automatically this flag will be set to true.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23116: To extract move plan or multi archive move plan along with other J2EE configuration plans.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23117: The t2p move plan or multi archive move plan contains the endpoint configuration for J2EE and system components configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23118: For details on how to modify the move plan, refer to Administering Oracle Fusion Middleware document.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23119: Source domain was configured with external java home. So target domain will be configured with external java home, which is system java home {0} .

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23120: Unpacking domain template to the target domain location ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23121: Updating machine, datasource configuration changes in the unpacked domain ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23122: Validating and updating Machine configuration in the unpacked domain ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23123: Validating and updating DataSource configuration in the unpacked domain ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23124: Validating and updating system component configuration in the unpacked domain ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23125: Executing script to update configuration changes in the unpacked domain ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23170: Invoking all system components which supports movement scripts.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23171: Following system components are configured in the domain: "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23172: No system components are configured in the domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23173: The following types system components support movement scripts : "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23174: There are no system components in the domain which support movement scripts.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23175: Following types of system components {0} are configured in the domain. T2P is not possible for following components types {1} as there is no T2P support for them.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23176: Following system components (COMPTYPE_COMPNAME Vs machineName) are configured in the domain "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23177: Execution of "{0}" T2P plugin started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23178: Execution of "{0}" T2P plugin completed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23190: Executing system component specific T2P for following component types: {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23191: No system component specific T2P will be executed as no system component (which supports T2P) was configured.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23200: System property "{0}" is set to "{1}" .

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23255: Updating domain template with target end points ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23256: Peforming offline operations if any ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23257: Peforming T2P plugin specific offline operations if any ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23258: Setting up admin account in embedded LDAP ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23259: Validating admin user ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23260: User has provided packed domain jar file {0}. So excluding pack operation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23261: Name of the packed domain jar file is not {0} . So copying it to temporary location {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23262: Packed domain jar file is included in the archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23263: Validating FileStore configuration to update domain template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23264: Examining FileStore ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23265: Use the "-help" option for more information about cloning options and arguments.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23266: Connecting to runtime ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23267: Pack domain - {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23268: Adding Packed domain to archive ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23269: Successfully connected to runtime.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23270: Connecting to domain runtime ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23271: Trying to connect to {0}:{1} ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23272: Successfully connected to the domain Runtime.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23273: Examining Servers.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23274: Examining Machines.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23275: Examining Clusters.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23276: Examining Datasources.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23277: Examining Security Policy.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23278: Examining all J2EE plugin implementations.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23279: Credential and Policy Store is LDAP type.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23280: Credential and Policy Store is File based.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23281: Extracting packed domain from archive to temporary location.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23282: Reading extracted domain template and updating target server, machine, cluster, datasource and many more configuration changes ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23283: Unpacking updated domain template to the target domain location ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23284: Starting Administration Server and pasting security policy configuration changes ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23285: Find all J2EE plugin pasteConfig implementations and apply the configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23286: Pasting security policy configuration changes ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23287: Validating Server configuration to update domain template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23288: Validating Cluster configuration to update domain template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23289: Validating DataSource configuration to update domain template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23290: Validating Machine configuration to update domain template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23291: Validating system component configuration to update domain template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23292: Examining Adapters.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23293: Examining Resource Adapters. The Resource Adapters with deployment plan will be added to 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: Domain template is updated successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23300: Configplans have been extracted at "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23301: ExtractMovePlan operation completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23302: Serialize and write bean to a temp file, then add that temp file to jar.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23303: Write archive file list to a temp file , then add that temp file to jar.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23304: ****************** PACK ******************

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23305: Details for Packing domain ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23306: Oracle Home Source Location: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23307: Source domain Location: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23308: Packed jar Location: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23309: Command to execute for pack: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23311: Specified adapter deployment plan {0} is not a valid file. Using the default plan from archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23312: Examining LDAP Authenticators.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23313: Validating LDAP Authenticator configuration to update domain template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23314: Exporting metadata of applications. Make sure that all Managed Servers in the specified domain are started.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23315: Importing metadata of applications.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23316: Starting Managed Server "{0}" to import MDS data.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23317: Importing metadata of application {0} from archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23318: Unpack of updated domain template to target domain location completed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23319: Exporting metadata may take several minutes. Check the logs for monitoring the progress ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23320: Importing keystores of servers to KSS ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23321: Import of keystores of servers to KSS completed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23322: Updating keystores of servers to {0} as keystore type was kss.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23323: Keystores of servers are updated.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23324: Importing keystores of Node Manager to KSS ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23325: Import of keystores of Node Manager to KSS completed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23326: Keystores for all servers set to "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23327: Keystore type for all servers set to "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23328: Metadata export is not needed as the applications configured in the domain do not have any data in MDS.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23351: MDS data export flag is set to false. Skipping MDS configurations.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23352: [Deprecated - As of release 11.1.1.7.0, replaced by "-mdsDataExport|-mde"] Flag to execute MDS export/import. Default value is true.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23353: Error in validating "pasteConfig" parameters.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23356: Error in validating "SERVER_CONFIG" parameters in "move plan".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23357: {0} is already running on port {1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23358: Stopping all Managed Servers.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23359: Credential and Policy Store is database based.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23360: Values for re-associating and migrating "OPSS_SECURITY" are not provided. Assuming File store for OPSS.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23361: Re-associate security store to database : {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23362: Examining RDBMS Security Store.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23363: Validating RDBMS Security Store Configuration to update domain template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23364: {0} is not in running state. It is still in process of starting ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23372: Validating move plan {0} ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23373: Move plan is valid.

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-23394: Exporting default providers ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23395: Importing default providers ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23500: Error while archiving Node Manager. Check log for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23502: Unarchiving Node Manager files at location {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23503: Target Oracle Home Location is either null or an empty string.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23504: Unable to derive target WebLogic Server Home from the Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23505: Unable to derive Java Home from the target Oracle Home .

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23506: The file {0} does not exist.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23507: Updating file {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23508: Examining each domain to enroll Node Manager.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23509: Unable to retrieve properties of the domain from move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23510: Domain Name is either null or an empty string in the move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23511: Domain Location is either null or an empty string in the move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23512: Incorrect format of Administration Server Listen Port for domain {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23513: Checking if the Administration Server for domain {0} is up...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23514: Could not connect to Administration Server for domain {0}. Make sure values provided are correct in the move plan. If "Administration Server Listen Port" is an SSL port, provide the 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 Node Manager with domain {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23516: Successfully enrolled Node Manager with domain {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23517: WebLogic Server Home value is either null or empty string.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23518: Starting Node Manager from location {0} ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23519: Node Manager ListenPort mentioned in nodemanager.properties is not valid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23520: Checking if port {0} is available for Node Manager ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23521: Port is available.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23522: -targetNMHomeLoc is either null or an empty string.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23530: Re-associating security store ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23533: Absolute path of Custom Trust KeyStore File Location. Specify this property to specify the "CustomKeyStore" if SSL port is specified for Administration Server.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23534: The move plan - {0} was not extracted using the archive - {1}. Extract the move plan once again using the archive - {1} and re-run the script.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23535: Warning: Starting of {0} is taking longer than expected. Check the server logs to make sure {1} start is in progress.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23536: Warning: Stopping of {0} is taking longer than expected. Check the server logs to make sure {1} shutdown is in progress.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23537: [Deprecated - As of release 11.1.1.7.0, replaced by"-domainAdminPasswordFile"]

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23538: Starting Administration Server ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23539: Stopping Administration Server ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23540: Starting Managed Server {0} ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23541: Stopping Managed Server {0} ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23542: Archive file {0} is either not a file or of zero size.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23543: No archive file is provided.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23544: Number of move plans and number of archives are not same.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23545: Unable to load prerequisites jars, proceeding without executing system prerequisites.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23546: The sameDBTopology flag is false. No optimization will happen for data source.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23547: Prereq will not be executed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23548: Warning: Valid values are not provided for Custom Identity KeyStore configuration. Source configuration will be retained in the target.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23549: Warning: Following Node Manager properties are missing from move plan: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23550: Administration Server stopped successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23551: Managed Server {0} stopped successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23552: Administration Server started successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23553: Managed Server {0} started successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23554: Managed Server {0} is already in shut down state.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23555: Configuring Wallet and storing Admin user credentials ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23556: Enabling Network channel configuration ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23557: Network channel configuration enabled successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23950: An empty file path was provided.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23951: An empty password was provided.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23952: An environment variable was provided as part of the path, but the environment variable does not exist or is empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23953: Password file successfully created at {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23954: The path you've provided for the password file is a directory. Enter a valid filename that does not currently exist.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23955: Filename provided already exists. Provide a new filename

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23956: Unable to create password file. Ensure that the directory path exists and is writable

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23957: Object persisted successfully

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23958: Password to obfuscate:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23959: Path of password file to be created:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23960: Password file was not created successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26001: OHS T2P property file is invalid.

Cause: Either property file does not exist or has invalid inputs.

Action: Make sure that the property file {0} has a valid entry.
Level: 1

Type: ERR

Impact: T2P

CLONE-26002: OHS cloning has failed.

Cause: OHS creation failed.

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

Type: ERR

Impact: T2P

CLONE-26003: Error in validating listen host and port.

Cause: The causes were: {0}

Action: Make sure the listen host and port values provided are correct and the ports are free on the corresponding host.
Level: 1

Type: ERR

Impact: T2P

CLONE-26004: Moveplan validation failed for OHS component.

Cause: There was no movable component of type {0} and name {1} in the source moveplan.

Action: Make sure that the movable component type and name are not chnaged in the moveplan.
Level: 1

Type: ERR

Impact: T2P

CLONE-26005: Moveplan validation failed for OHS component.

Cause: The possible causes are: {0}

Action: Make sure that you have updated only values of READ_WRITE config properties of OHS component.
Level: 1

Type: ERR

Impact: T2P

CLONE-26006: Moveplan validation failed for OHS component.

Cause: Ipv6 addresses are not supported for ServerName directive.

Action: Make sure that you have provided valid value for ServerName.
Level: 1

Type: ERR

Impact: T2P

CLONE-26101: Following OHS components are configured in the domain :{0}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26102: Performing copyConfig operation for component {0} ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26103: CopyConfig operation for component {0} is completed.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26104: Capturing configuration in the moveplan ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26105: Captured configuration in the moveplan.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26106: Archiving configuration files ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26107: Archive of configuration files completed.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26108: Capturing WebGate configuration, if any ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26110: Validating config properties of config group {0}...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26111: Config properties of config group {0} are validated and updated.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26113: Virtual port {0} is not in listen port list.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26114: Setting virtual port to {0}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26115: Virtual port is not in the new listen port list. Leaving this virtual host port as it is.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26116: Updating webgate specific configuration, if any ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26117: The port {0} is not free. Assigning new port {1}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26118: Archive of {0} files started, if any...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26119: Archive of {0} files finished.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26120: Restoring {0} files from the archive started ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26121: Restoring {0} files from the archive completed.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26122: Updating instance location, component name and Oracle Home ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26123: Instance location, component name and Oracle Home updated successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26124: Updating directive and container...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26125: Directive and container are updated successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26127: Performing validation of Listen and Virtualhost ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26128: Updating all xml files under {0}...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26129: All xml files under {0} are updated successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26130: Updating all configuration files ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26131: All configuration files are updated successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26133: Configuration file {0} does not exist. Unable to run file fixer.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26134: In source environment, configuration file {0} was outside of the instance home. In target environment, trying to restore to same location.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26135: An attempt was made to restore configuration file at {0}, but this path already exists. So configuration file will not be restored again.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26136: Extracting configuration file under {0}...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26137: Configuration file {0} is restored successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26138: An attempt was made to restore {0} directive at {1}, but this path already exists. So directive will not be restored again.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26139: Extracting directive files under {0}...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26143: Obfuscating PLSQL database password, if exists.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26144: No configuration file carries PLSQL database password.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26145: Obfuscation of PLSQL database password did not happen.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26146: Configuration file {0} was not restored from the archive. Obfuscate will not be performed.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26147: Configuration file {0} does not exist. Obfuscate will not be performed.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26148: Updating password field in the configuration file {0}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26149: Unable to retrieve password for {0} from file {1}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26150: Unable to update password field in the configuration file {0}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26151: Password field is updated in the configuration file {0} successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26152: Obfuscating PLSQL database password...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26153: PLSQL database password obfuscated successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26154: Unable to obfuscate PLSQL database password.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26155: Restoring permission of configuration files...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26156: Permission of configuration files are restored successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26157: Unable to restore permission of configuration files.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26158: Unable to update password field in the configuration file {0}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26159: Validating move plan for OHS component "{0}" ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26160: From move plan, the name of the property is {0}, and its value is empty. Value cannot be empty.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26161: From move plan, the name of the property is {0}, and its value {1} is not a valid integer. It should be a valid integer.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26162: Updating oradav configuration file, if exists ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26163: Updating oradav configuration file ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26164: Obfuscating oradav password...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26165: Oradav password is obfuscated successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26166: Unable to obfuscate oradav password.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26167: Oradav configuration file is updated successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26168: Unable to update oradav configuration file.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26169: Updating webgate install directory, if present ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26170: Webgate install directory is updated successfully in configuration files.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26171: Validating config properties of config group {0}...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26172: Config properties of config group {0} are validated.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26181: Following OHS components are present in the moveplan :{0}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26182: Executing pasteConfig for OHS component {0} started ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26183: Execution of pasteConfig for OHS component {0} completed.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26201: No OHS component is configured in the domain.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26202: Following OHS components are configured in the domain :{0}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26203: Restarting admin server so that configuration files will be in sync ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26205: Starting following components {0} as they were targeted for admin server in the src env and expecting that they are targeted for admin server in target env ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26207: OHS component {0} is started successfully..

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26301: Building OracleASComponent object for OHS component...

Cause:

Action:
Level: 1

Type: TRC

Impact: T2P

CLONE-26302: OracleASComponent object is created successfully.

Cause:

Action:
Level: 1

Type: TRC

Impact: T2P

CLONE-26303: Building OracleASComponentProperties object for OHS component ...

Cause:

Action:
Level: 1

Type: TRC

Impact: T2P

CLONE-26304: OracleASComponentProperties object is created successfully.

Cause:

Action:
Level: 1

Type: TRC

Impact: T2P

CLONE-26305: OHS parameters for pasteConfig operation are : {0}.

Cause:

Action:
Level: 1

Type: TRC

Impact: T2P

CLONE-26306: Printing {0} move plan ...

Cause:

Action:
Level: 1

Type: TRC

Impact: T2P

CLONE-26307: Updating configuration file {0} through file fixer ...

Cause:

Action:
Level: 1

Type: TRC

Impact: T2P

CLONE-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-32030: ADF Connection MBean {0}.isEditable() return false, no moveplan content generated for this MBean.

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-32040: ADF Connection MBean {0}.isEditable() return false, any updates in source moveplan will not be saved in target domain.

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: Start to run T2P ADF Connection Plugins.

Action: No Action.
Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33020: Finish running T2P ADF Connection Plugins.

Cause: Finish running T2P ADF Connection Plugins.

Action: No Action.
Level: 1

Type: NOTIFICATION

Impact: Other

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

Cause: Starting WLS managed server.

Action: No Action.
Level: 1

Type: NOTIFICATION

Impact: Other

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

Cause: Stopping WLS managed server.

Action: No Action.
Level: 1

Type: NOTIFICATION

Impact: Other

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

Cause: Processing ADF Connection MBean attributes at server.

Action: No 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: Successfully saved ADF Connection MBean attributes update for application.

Action: No Action.
Level: 1

Type: NOTIFICATION

Impact: Other

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

Cause: No ADF Connection MBean attributes changed for application.

Action: No 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-92100: In method doCopyConfigValidation.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92101: In method doCopyConfig.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92102: In method doPostCopyConfig..

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92103: In method doPasteConfigValidation.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92104: In method doPrePasteConfig.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92105: In method doPasteConfig.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92106: In method doPostPasteConfig.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92107: Download data for User Preferences.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92109: Extract driver configuration.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92110: Extract configuration from {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92111: Value was null for property {0}. Skip.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92112: No UMS config found. Skip driver configuration.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92113: Update configuration on {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92114: Upload data for User Preferences.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92115: UMS application not present in domain. Skip doCopyConfig (no-op).

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92116: UMS application not present in domain. Skip doPasteConfig (no-op).

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92117: Starting server {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92118: Stopping server {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92119: Handle User Preferences.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92120: Found User Preferences on {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92130: No DriverConfigExtractor found for driver type {0}. Skip.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92300: doCopyConfig failed. msg={0} stackTrace={1}

Cause: Failure during copyConfig.

Action: See log for details.
Level: 1

Type: ERROR

Impact: Process

CLONE-92301: doPasteConfig failed. msg={0} stackTrace={1}

Cause: Failure during pasteConfig.

Action: See log for details.
Level: 1

Type: ERROR

Impact: Process

CLONE-92302: Skipped corrupted ConfigGroup for {0}

Cause: Expected one ConfigProperty within ConfigGroup.

Action: Edit moveplan.xml or configure manually in the production system.
Level: 1

Type: ERROR

Impact: Process

12 DFW-40000 to DFW-40210

DFW-40000: Diagnostic dump {0} has been registered as system scoped.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

DFW-40001: Diagnostic dump {0} has been registered scoped to application {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

DFW-40003: executing diagnostic dump {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

DFW-40004: The requested diagnostic dump {0} is unknown.

Cause: The diagnostic dump {0} has either not been registered or the given name is incorrect.

Action: Ensure that a valid dump name is specified.
Level: 1

Type: WARNING

Impact: Configuration

DFW-40005: The mandatory dump argument {0} is not specified.

Cause: A request to execute a dump was made without specifying all mandatory arguments.

Action: Ensure that all mandatory arguments are specified.
Level: 1

Type: WARNING

Impact: Programmatic

DFW-40006: ignoring dump argument {0} as it is not defined for diagnostic dump {1}

Cause: The dump does not accept the specified argument.

Action: Ensure that only arguments defined by the dump are specified.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

DFW-40007: The diagnostic dump argument {0} should be of type {1}.

Cause: The specified argument is of the wrong type.

Action: Ensure that arguments are of the correct type.
Level: 1

Type: WARNING

Impact: Programmatic

DFW-40008: failed to execute diagnostic dump {0}

Cause: An error occurred during the execution of the dump.

Action: Check process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40009: failure creating dump file

Cause: An error occurred creaing a dump file

Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40010: failure registering Java Flight Recorder diagnostic dump

Cause: This could be due to JRockit or Java HotSpot not being used as the JVM.

Action: See the reported Exception for more information.
Level: 1

Type: WARNING

Impact: Other

DFW-40011: Dump {0} cannot be executed manually.

Cause: Dumps that are designed to be run synchronously during incident creation cannot be executed manually.

Action: No further action is required.
Level: 1

Type: WARNING

Impact: Process

DFW-40100: failed to create ADR Base directory {0}

Cause: An error occurred whilst attempting to create the ADR Base directory required to store captured diagnostics data. This may be due to file or process permissions.

Action: Check that the process has permission to create the directory.
Level: 1

Type: ERROR

Impact: Operating System

DFW-40101: An incident has been signalled with the incident facts: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

DFW-40102: failure during incident rule processing of incident {0}

Cause: During the processing of the incident rules an error occurred.

Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Other

DFW-40103: failed to execute dump during creation of incident {0}

Cause: An error occurred during the execution of a diagnostic dump.

Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Other

DFW-40104: incident {0} created with problem key "{1}"

Cause:

Action:
Level: 1

Type: INCIDENT_ERROR

Impact: Other

DFW-40105: failed to execute dump {0} during creation of incident {1}

Cause: An error occurred during the execution of the dump.

Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40106: failed to load diagnostic rules schema {0}

Cause: The diagnostic rules schema could not be loaded.

Action: Check that the specified schema exists and is readable.
Level: 1

Type: WARNING

Impact: Process

DFW-40107: failed to parse diagnostic rules

Cause: The diagnostic rules do not conform to the schema.

Action: Fix the diagnostic rules XML to make the rules valid.
Level: 1

Type: WARNING

Impact: Process

DFW-40108: invalid diagnostic rules document

Cause: The diagnostic rules document has invalid content.

Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Configuration

DFW-40109: failed to write and register incident {0} readme file with ADR

Cause: An issue occurred during the registration of the readme file. This does not impact the associated diagnostic dump data.

Action: Check that the process writing the readme file has sufficient privileges.
Level: 1

Type: NOTIFICATION

Impact: Process

DFW-40110: failure parsing ADRCI XML output

Cause: The XML returned by the ADRCI show incidents command could not be parsed.

Action: Check the process logs for more information.
Level: 1

Type: NOTIFICATION

Impact: Other

DFW-40111: failed to determine incident id and path from adrci output "{0}"

Cause: There was an error executing the command to create an incident using ADRCI.

Action: Ensure that command line tool "adrci" can be executed from the command line.
Level: 1

Type: ERROR

Impact: Data

DFW-40112: failed to execute the adrci commands "{0}"

Cause: There was an error executing adrci commands; the following errors have been found "{0}"

Action: Ensure that command line tool "adrci" can be executed from the command line.
Level: 1

Type: ERROR

Impact: Other

DFW-40113: failed to execute adrci commands; adrci returned "{0}"

Cause: There was an error executing adrci commands.

Action: Ensure that command line tool "adrci" can be executed from the command line.
Level: 1

Type: ERROR

Impact: Other

DFW-40114: The ADR Product ID exceeds the maximum length {0}.

Cause: The given ADR Product ID is too long.

Action: The ADR Product ID will automatically be truncated. No further action is required.
Level: 1

Type: WARNING

Impact: Files

DFW-40115: The ADR Instance ID exceeds the maximum length {0}.

Cause: The given ADR Instance ID is too long.

Action: The ADR Instance ID will automatically be truncated. No further action is required.
Level: 1

Type: WARNING

Impact: Files

DFW-40116: failure creating incident

Cause: An error occurred during the creation of an incident.

Action: See base error for root cause anc check process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40117: Invalid fact name "{0}" specified for rule "{1}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

DFW-40118: ADR incident creation is disabled; incident not created.

Cause: Diagnostics Framework was unable to initialize ADR, resulting in ADR creation being disabled.

Action: Check the process logs for more information on why ADR could not be initialized.
Level: 1

Type: NOTIFICATION

Impact: Process

DFW-40119: file {0} cannot be added to incident {1} as it exceeds the maximum filename length of {2} characters

Cause: The specified filename length exceeds the maximum allowed by ADR.

Action: Specify a filename whose length does not exceed the maximum alloweed length.
Level: 1

Type: WARNING

Impact: Files

DFW-40120: failure initializing incident detection log filter

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

DFW-40121: failure creating incident from WLDF notification

Cause: An error occurred whilst attempting to create an incident.

Action: See the base exception for details, and check the process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40122: incident {0} does not exist

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

DFW-40123: file {0} is not registered with incident {1}

Cause: The specified filename is not associated with the incident

Action: Specify the name of a file that is registered with the incident
Level: 1

Type: NOTIFICATION

Impact: Programmatic

DFW-40124: failure adding file {0} to incident {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Files

DFW-40125: incident flood controlled with Problem Key "{0}"

Cause: The specified Problem Key is under flood control, due to the volume of incidents with that Problem Key exceeding the maximum incident count.

Action: Inspect the reason for the creation of incidents with the specified Problem Key and resolve the issue.
Level: 1

Type: WARNING

Impact: Other

DFW-40126: incident with Problem Key "{0}" could not be created due to lack of available disk space for incidents; configured maximum is {1} bytes and used is {2} bytes

Cause: The incident with the specified Problem Key could not be created due to lack of available disk space allocated for incidents.

Action: Purge old incidents or increase the maximum allowed disk space for incidents in dfw_config.xml.
Level: 1

Type: WARNING

Impact: Other

DFW-40127: incident filtered with Problem Key "{0}"

Cause: The specified Problem Key is configured to be filtered.

Action: If the problem key should not be filtered modify the DFW configuration to remove the appropriate filter.
Level: 1

Type: WARNING

Impact: Other

DFW-40128: invalid Problem Key filter pattern "{0}"

Cause: The specified Problem Key filter pattern is invalid.

Action: See the base error for the specific error and fix the pattern
Level: 1

Type: WARNING

Impact: Other

DFW-40129: failed to parse incident query "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DFW-40130: failed to load custom rules file "{0}": {1}

Cause: The specified custom rules file could not be loaded.

Action: See the reported exception message for further details.
Level: 1

Type: WARNING

Impact: Other

DFW-40131: the version of the ADR binaries in use are not compatible with the existing ADR data files; backing up existing data from {0} to {1}

Cause: The Windows 64bit ADR binaries cannot read/write ADR data created with the Windows 32bit ADR binaries.

Action: The 32bit ADR data has been backed up. To read/write the backed up data you must use the 32bit ADR binaries.
Level: 1

Type: WARNING

Impact: Other

DFW-40200: failed to load diagnostics configuration schema {0}

Cause: The diagnostics configuration schema could not be loaded. See base exception for root cause

Action: Check that the specified schema exists and is readable.
Level: 1

Type: WARNING

Impact: Configuration

DFW-40201: failed to parse diagnostics configuration

Cause: The diagnostics configuration document does not conform to the schema.

Action: Fix the diagnostic configuration XML to make the configuration valid.
Level: 1

Type: WARNING

Impact: Process

DFW-40202: failed to create diagnostics configuration XML

Cause:

Action:
Level: 1

Type: TRACE

Impact: Process

DFW-40203: failure initializing diagnostics security context

Cause: An error occurred initializing the internal Diagnostic Framework security context.

Action: See the base exception for details, and check the process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40204: invalid ADR Home path {0}

Cause: The specified ADR Home is not a valid path.

Action: Specify a valid ADR Home path of the form diag/<productType>/<productId>/<instanceId>
Level: 1

Type: WARNING

Impact: Programmatic

DFW-40205: failure loading diagnostic framework configuration file {0}; the default configuration will be used.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Files

DFW-40206: failure registering diagnostic rules file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Files

DFW-40207: Failure getting WebSphere Cell name for use as ADR Product Id; defaulting it to 'cell'

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

DFW-40208: failure setting default uncaught exception handler

Cause:

Action:
Level: 1

Type: WARNING

Impact: Files

DFW-40209: SYNCHRONOUS dump {0} cannot be configured for sampling

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DFW-40210: Not allow to configure {0} for sampling

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

13 DMS-50700 to DMS-58075

DMS-50700: initialization error

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50701: security error

Cause: (See message)

Action: Review the exception chain in log files for the cause and make sure that the appropriate permission has been granted.
Level: 1

Type: ERROR

Impact: Security

DMS-50702: The DMS Java class "{0}" could not be found.

Cause: (See message)

Action: Review the classpath of the application and ensure that the class is available in a jar file or directory listed therein.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50703: The LogWriter name "{0}" is reserved.

Cause: (See message)

Action: Use a different name.
Level: 1

Type: ERROR

Impact: Logging

DMS-50704: unable to create a new LogWriter: {0}

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: ERROR

Impact: Logging

DMS-50705: attempting to create a concrete LogWriter instance with an invalid class ({0})

Cause: (See message)

Action: Correct the declaration for the LogWriter to use a valid class.
Level: 1

Type: ERROR

Impact: Logging

DMS-50706: invalid configuration property: name = "{0}", value = "{1}"

Cause: (See message)

Action: Remove the property or correct its name or value to comply with the set of supported property names. If the property value is at fault then reviewing the base exception may provide more information on the manner of the fault (e.g. missing class, invalid directory name).
Level: 1

Type: WARNING

Impact: Configuration

DMS-50707: unable to load configuration file "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and make sure that the configuration file exists and the permissions on the file permit it to be read.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50708: unable to parse metric rule document

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50709: The metric rule resource {0} could not be read. Aggregation is off.

Cause: (See message)

Action: Check that the resource is available and if necessary correct the content of the classpath.
Level: 1

Type: WARNING

Impact: Files

DMS-50710: duplicated table "{1}" in metric table "{0}"

Cause: (See message)

Action: Remove the <Union> or <Select> table from the metric table (it is already in use therein).
Level: 1

Type: WARNING

Impact: Other

DMS-50711: Value "{1}" is invalid for attribute "{0}".

Cause: (See message)

Action: Review the documentation for the correct use of the specific attribute.
Level: 1

Type: WARNING

Impact: Other

DMS-50713: invalid metric rule syntax

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to the metric rule documentation.
Level: 1

Type: WARNING

Impact: Other

DMS-50714: no DMS Archiver found

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50715: no ONS found

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50716: unable to create DMS ONS RPC server

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: WARNING

Impact: Other

DMS-50717: unable to create DMS Publisher "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: WARNING

Impact: Other

DMS-50719: unable to connect to the server and retrieve metrics at "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and make sure that the server starts up.
Level: 1

Type: WARNING

Impact: Requests/Responses

DMS-50720: unable to retrieve DMS metrics

Cause: The HTTP server failed to handle the metric request.

Action: Make sure the HTTP server is able to handle metric requests.
Level: 1

Type: WARNING

Impact: Other

DMS-50722: unable to parse DMS metric document

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: WARNING

Impact: Other

DMS-50723: The reference to table {0} for aggregating DMS metrics is invalid.

Cause: Columns from tables created by select and union elements are not valid in this context.

Action: Correct the aggregation statement in the metric rules.
Level: 1

Type: WARNING

Impact: Other

DMS-50725: unable to bind to port "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and make sure port is free.
Level: 1

Type: ERROR

Impact: Ports

DMS-50726: The metric configuration resource {0} could not be read.

Cause: (See message)

Action: Check that the resource is available and if necessary correct the content of the classpath.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50727: invalid metric configuration syntax

Cause: (See message)

Action: Refer to XML schema "metric_config.xsd" and correct the configuration.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50728: No writable metric repository directory "{0}" is available. The default metric archiving is off.

Cause: (See message)

Action: Make sure that a writable metric repository exists.
Level: 1

Type: WARNING

Impact: Files

DMS-50730: The repository directory "{0}" is not readable.

Cause: (See message)

Action: Make sure that a readable metric repository exists.
Level: 1

Type: WARNING

Impact: Files

DMS-50731: invalid value type "{0}" for column "{1}"

Cause: (See message)

Action: Refer to the metric rule documentation for valid value types.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50732: invalid value type for "Concat" operation: should be string

Cause: (See message)

Action: Refer to the metric rule documentation for valid value types.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50733: Arithmetic expression cannot be string type.

Cause: (See message)

Action: Refer to the metric rule documentation for details of defining metrics.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50734: missing value type for column <{0} Name="{1}">

Cause: (See message)

Action: Refer to the metric rule documentation and add an explicit value type to the column.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50735: invalid system function <Function Name="{0}">

Cause: (See message)

Action: Refer to the metric rule documentation for a list of valid system functions.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50736: missing an argument in <Expression> for column "{0}"

Cause: (See message)

Action: Refer to the metric rule documentation and add an argument for the expresstion.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50737: circular dependency found on aggregated metric tables {0}

Cause: (See message)

Action: Remove circular dependency among aggregated tables.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50738: invalid operation "{0}"

Cause: (See message)

Action: Refer to the metric rule documentation for a list of valid operations.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50742: Exception occurred while performing individual refresh operation for metric "{0}".

Cause: (See message)

Action: Refer to log files for the cause and, if possible, correct the problem.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50743: Exception occurred while performing group refresh operation for metric "{0}". This failed refresh may have affected other metrics too.

Cause: (See message)

Action: Refer to log files for the cause and, if possible, correct the problem.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50744: illegal argument values passed to method: {0}

Cause: This is in internal error: a set of arguments have been passed to a method within the DMS component that are not appropriate for that method. This state should not have occurred and is indicative of a series of conditions that were not anticipated during development.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

DMS-50745: illegal program state detected: {0}

Cause: This is in internal error: a program state has been detected within the DMS component that is unexpected or contradictory.

Action: Refer to log files for the cause and, if possible, correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

DMS-50747: attempt to read an older metric rule document "{0}"

Cause: Metric rule document "{0}" was older than the one currently used in the system.

Action: Make sure the version of the metric rules is equal to or higher than the one currently used in the system.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50748: attempt to read an metric rule document "{0}" that is equal to or older than the one currently used in the system

Cause: The version of the metric rule document "{0}" was equal to or older than the one currently used in the system.

Action: Make sure the version of the metric rules is higher than the one currently used in the system.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50749: OPMN is down.

Cause: (See message)

Action: Start OPMN.
Level: 1

Type: WARNING

Impact: Requests/Responses

DMS-50750: Metric parameter is null.

Cause: (See message)

Action: Pass in a non-null metric.
Level: 1

Type: WARNING

Impact: Data

DMS-50751: Metric "{0}" passed in does not belong to "{1}".

Cause: (See message)

Action: Pass in an appropriate metric.
Level: 1

Type: WARNING

Impact: Data

DMS-50752: At least one of the parameters for "{0}" is null or empty: {1}

Cause: (See message)

Action: Do not pass in null or empty parameters.
Level: 1

Type: WARNING

Impact: Data

DMS-50753: wrong value type

Cause: (See message)

Action: Pass in value with appropriate type.
Level: 1

Type: WARNING

Impact: Data

DMS-50754: One of the parameters for "{0}" has unexpected value "{1}".

Cause: (See message)

Action: Pass in correct values.
Level: 1

Type: WARNING

Impact: Data

DMS-50755: server unavailable: {0}

Cause: (See message)

Action: Specify valid server or cluster names.
Level: 1

Type: WARNING

Impact: Data

DMS-50756: invalid value for property "{0}": "{1}"

Cause: (See message)

Action: Specify a valid property value.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50757: Property "{0}" cannot have null or empty value.

Cause: (See message)

Action: Specify a valid property value.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50758: Invalid configuration value for metric caching: "{0}"

Cause: (See message)

Action: Specify a valid configuration value.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50759: invalid property: "{0}"

Cause: (See message)

Action: Specify a valid property.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50760: DMS startup class is not started. DMS runs with reduced functionality.

Cause: (See message)

Action: Make sure to start DMS startup class.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50761: Could not derive a translation using key {0} and locale {1} for parameter descriptor {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-50762: No NounDescriptor found for anonymous phase.

Cause: An anonymous phase has been started or aborted but there is no NounDescriptor associated with this phase. Some derived data, such as trace data, may be incomplete or partially corrupted.

Action: Correct the code that starts or aborts the anonymous phase.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50763: Attempt to create pre-existing noun {0}, of type {1}, with a conflicting type {2}.

Cause: An attempt has been made to create a noun that already exists and has a type that is different from the current attempt to create it.

Action: Correct the code responsible for creating this noun.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50764: Noun at path {0} is of type {1} which conflicts with asserted type {2}.

Cause: A piece of code has attempted to find a noun with a specific path but the type of that noun discovered does not match the type expected by the caller.

Action: Correct the code responsible for creating this noun.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50903: Metric aggregation is off due to errors.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50904: unable to parse metric rule document: {0}

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50905: missing name for metric table

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50906: conflicting table space for metric table: {0}

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50907: Metric table "{0}" will not be built due to exception.

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50908: Name attribute is invalid in <ColumnDef> for metric table "{0}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50909: duplicated <ColumnDef Name="{1}"> for metric table "{0}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50910: Type attribute is invalid in <ColumnDef Name="{1}"> for metric table "{0}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50911: Duplicated metric table. Metric table {0} will be ignored.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50915: wrong value type "{2}" for column "{1}" in metric table "{0}". Expect value type "{3}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50916: Column "{0}" is missing in table "{1}" for metric table "{2}".

Cause: (See message)

Action: Make sure to match <ColumnDef> with <Column>.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50917: Name attribute is empty in <ColumnGroup>.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50918: Type attribute is invalid in <ColumnGroup Name="{1}">.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50919: empty group member in <ColumnGroup Name="{1}">

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50920: Attribute "{3}" of <{0}> is invalid in table "{1}" for metric table "{2}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50921: Column "{0}" is not defined in table "{1}" for metric table "{2}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50922: Attribute "{4}" of <{3} Name="{0}"> is invalid in table "{1}" for metric table "{2}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50923: Number of arguments for column "{3}" in <Expression> is "{0}" in table "{1}" for metric table "{2}", which is less that expected.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

Cause: (See message)

Action: Make sure to have at least two arguments.

DMS-50924: Arguments for column "{2}" in <Expression> are missing in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50925: unexpected <Aggregation> in <Where> in table "{0}" for metric table "{1}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50926: Metric table "{2}" should not reference column "{0}" defined in table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50927: duplicated <{0}> in table "{1}" for metric table "{2}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50928: missing <{0}> in table "{1}" for metric table "{2}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50929: unexpected <{0}> in <Union Name="{1}"> for metric table "{2}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50930: unable to resolve column "{2}" in table "{0}" for metric table "{1}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50932: The value of attribute "{0}", "{1}", is less then the minimum "{2}".

Cause: (See message)

Action: Review the documentation for the correct use of the specific attribute and give a valid value.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50933: unable to convert the value of attribute "{0}", "{1}", to a number

Cause: (See message)

Action: Review the documentation for the correct use of the specific attribute and give a valid value.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50934: Sampling is not enabled for metric table "{0}".

Cause: (See message)

Action: Refer to log files for the cause and, if possible, correct the problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50935: unable to convert value "{0}" to a number

Cause: (See message)

Action: Refer to log files for the cause and, if possible, correct the problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50938: duplicated <{3} Name="{0}"> in table "{1}" for metric table "{2}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50940: The value of Attribute "Name" for <OrderBy> fails to match one of column names in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50941: unable to convert the value of <RowRetained>, "{0}", in table "{1}" to a number for metric table "{2}"

Cause: (See message)

Action: Review the documentation for the correct use of the specific element and give a valid value.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50942: Only two tables can be referred to in outer join in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50943: Some of the values of <Column Name="{0}"> from metric table "{1}" contained by <Select Name="{2}"> inside <Table Name="{3}"> will be lost after aggregation. It is recommended to use <Aggregation Name="{0}"> or <GroupBy Name="{0}">.

Cause: (See message)

Action: It is recommended to use <Aggregation Name="{0}"> or <GroupBy Name="{0}">.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50944: Some of the values of <Column Name="{0}"> from metric table "{1}" contained inside <Having> by <Select Name="{2}"> inside <Table Name="{3}"> will be lost after aggregation. It is recommended to use <Aggregation Name="{0}"> or <GroupBy Name="{0}">.

Cause: (See message)

Action: It is recommended to use <Aggregation Name="{0}"> or <GroupBy Name="{0}">.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50945: missing <And>, <Or>, <Not>, or <Condition> in table "{0}" for metric table "{1}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50946: invalid <{0}> in table "{1}" for metric table "{2}"

Cause: (See message)

Action: Specify one of <And>, <Or>, <Not>, or <Condition>.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50947: Number of arguments for condition is "{0}" in table "{1}" for metric table "{2}", which is less that expected.

Cause: (See message)

Action: Make sure to have at least two arguments.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50948: missing condition argument in table "{0}" for metric table "{1}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50949: <Null> is not valid when operator is "{0}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50950: Exception occurred while retrieving metrics from metric repository.

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50951: wrong number of tokens in auto aggregation table name "{0}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50952: invalid auto aggregation table name "{0}"

Cause: (See message)

Action: Make sure that auto aggregation table names follow the patterns of <prefix>/<opcode>//<table_name> or <prefix>/<opcode>/groupby/<column_name1>/.../<column_nameN>//<table_name>.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50953: invalid aggregation operation "{1}" in auto aggregation table name "{0}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50954: invalid metric cache size "{0}"

Cause: (See message)

Action: Make sure to give a valid value for the metric cache size in megabytes.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50955: invalid metric prefetch interval "{0}"

Cause: (See message)

Action: Make sure to give a valid value for the metric prefetch interval in seconds.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50956: invalid metric prefetch removal cycle "{0}"

Cause: (See message)

Action: Make sure to give a valid value for the metric prefetch removal cycle.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50957: Value of column "{1}" in table "{0}" is not a number.

Cause: (See message)

Action: Review the documentation for the correct use of the specific element and make sure to give valid value.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50958: invalid DMS queue timeout interval "{0}"

Cause: (See message)

Action: Make sure to give a valid value for the DMS queue timeout in seconds.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50959: invalid DMS queue maximum size "{0}"

Cause: (See message)

Action: Make sure to give a positive value for the DMS queue maximum size.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50960: Column <{2}> should not be type "{3}" in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50961: Operation "{2}" should be type "{3}" in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50962: Arithmetic expression should not be String type in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50963: Column "{0}" expects a number.

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50964: Column <{2} Name="{3}"> is missing value type in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50965: <Function Name="{0}"> has invalid function name in table "{1}" for metric table "{2}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50966: Metric table "{0}" has no key column. It will not be collected.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50967: invalid Object Name "{0}" in dms_config.xml

Cause: (See message)

Action: Make sure to give an valid Object Name.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50968: Missing Object Name in dms_config.xml

Cause: (See message)

Action: Make sure to give an valid Object Name.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50973: Caught Exception.

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50976: The use of one or more of the following deprecated properties [{0}] has been detected.

Cause: (See message)

Action: Cease use of the deprecated properties and use one or more of these properties [{1}] instead.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50977: a potentially conflicting use of properties. The use of one or more of the following deprecated properties [{0}] has been detected.

Cause: (See message)

Action: Cease use of the deprecated properties and use one or more of these properties [{1}] instead. The deprecated properties will be ignored.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50978: Exception occurred while registering metric rules "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50980: Exception occurred while looking up runtime mbean server by JNDI name "{0}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.

DMS-50981: Exception occurred while reading metric rules "{0}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50982: Exception occurred while reading metric dump server configuration file "{0}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50983: Exception occurred while reading metric configuration file "{0}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50984: no data available for streaming.

Cause: (See message)

Action: Modify input parameters and try again.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50985: Exception occurred while retrieving metrics from address "{0}" with query string "{1}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50986: Task rejected because the collector queue reaches maximum size.

Cause: (See message)

Action: Allocate or free up more resources and try again later.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50989: Exception occurred while retrieving metrics from address "{0}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50990: Unable to register MBean "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50991: metric rule file "{0}" has the following XML parsing error: {1}

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50992: Invalid Java system property "{0}"

Cause: (See message)

Action: Specify a valid Java system property "{0}".
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50993: invalid metric dump interval "{0}"

Cause: (See message)

Action: Make sure to give a valid metric dump interval in seconds.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50994: invalid maximum size for the metric dump "{0}"

Cause: (See message)

Action: Make sure to give a valid maximum size in megabytes for the metric dump.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-57001: Failed to update WorkContextMap.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-57002: Exception raised while attempting to reset WorkContextMap in order to resolve a previous exception raised when updating WorkContextMap.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-57003: Failed to process the serialized DMS execution context {0} sent by {1} (user-agent: {2}) when requesting the resource {3}.

Cause: By scrutinizing the incoming HTTP request DMS has attempted to detect and, if appropriate, make use of a wrapped execution context. That process has failed. This should not affect the processing of the servlet handling the request, but the ability to correlate the processing of this request with others to which it may related will have been adversely affected. A DMS execution context is an object that contains context information about the piece of work being performed at a particular moment in time. The type of context information carried by the DMS execution context may include the URL of the http request, the unique correlation key (ECID) assigned to that piece of work, etc - information that is useful for tracking requests though the system. The execution context does not carry user names, passwords or general application parameters. The DMS execution context should not be confused with application specific context objects, such as ADF-context or Faces-context, which are vital to the accurate execution of the application concerned.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

DMS-57004: Failed to initialize the DMS trace to be associated with DMS execution context {0}, that itself is associated with a request of resource {1}.

Cause: A problem has occurred in the initialization of the trace system for this request. This should not affect the processing of the servlet handling the request but will be a problem if the trace (aggregate, debug or triggered) data was of value to the system's administrator.

Action: If the trace of this request was important, and has been affected by this error, then contact Oracle Support Services
Level: 1

Type: WARNING

Impact: Other

DMS-57005: Failed to terminate the DMS trace associated with DMS execution context {0}, that itself is associated with a request of resource {1}.

Cause: A problem has occurred in the finalization of the trace system for this request. This should not affect the processing of the servlet handling the request but will be a problem if the trace (aggregate, debug or triggered) data was of value to the system's administrator.

Action: If the trace of this request was important, and has been affected by this error, then contact Oracle Support Services
Level: 1

Type: WARNING

Impact: Other

DMS-57006: Failed to deactivate the DMS execution context, {0}, associated with a request of resource {1}.

Cause: A problem has occurred in the termination of the DMS execution context in place during the processing of the HTTP request. This should not affect the servlet handling the request, but may result in an invalid execution context being in place for the processing of future requests and possibly prevent accurate trace data from being gathered.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

DMS-57007: Failed to url-decode a serialized execution context ({0}) due to a problem in the decoding process itself: {1}

Cause: A problem has occurred while trying to url-decode a wrapped execution context found as a url-parameter. The consequence is that the execution context being passed from client to server can not be used. A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.

Action: Determine if there is any code in the system that integrates with the Oracle DMS Context API (java package oracle.dms.context) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code, and if necessary contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

DMS-57008: The execution context put in place at the start of the request, {0}, is not the execution context in place at the end of the request, {1}. The request is as follows: {2}

Cause: When enabled to do so DMS associates an execution context with the resources (typically a thread) assigned to process an incoming request. In this case the context that DMS assigned at the start of the processing is not the one in place at the end of the processing. At some point during the processing the context has been changed. This could result in the loss of the ability to correlate the work performed across the complete request lifecycle for this request. A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.

Action: Determine if there is any code in the system that integrates with the Oracle DMS Context API (java package oracle.dms.context) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code, and if necessary contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

DMS-57009: An error prevented selection of an appropriate execution context implementation for this environment - the feature will be disabled.

Cause: At the point of initialization DMS needs to determine the environment in which it is operating in order to select the most appropriate implementation of the execution context feature. An unexpected error has occurred during that process. The DMS execution context feature will be disabled.

Action: Review the error to see if it can be resolved and then restart the server.
Level: 1

Type: ERROR

Impact: Other

DMS-57010: Failed to select appropriate execution context implementation for this environment - the feature will be disabled.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

DMS-57011: Unexpected program state detected: {0}

Cause: The component has detected a state or behaviour that it can not accomodate or rectify.

Action: A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.
Level: 1

Type: WARNING

Impact: Other

DMS-57012: WorkContextMap access failed for execution context {0}.

Cause: DMS delegates certain operations to the WLS WorkContextMap. On this occasion the operation has failed, and therefore DMS can not complete this operation.

Action: A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.
Level: 1

Type: WARNING

Impact: Other

DMS-57013: WorkContextMap is not available for execution context {0}.

Cause: DMS delegates certain operations to the WLS WorkContextMap, but the WorkContextMap is not available, and therefore DMS can not complete this operation.

Action: A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.
Level: 1

Type: WARNING

Impact: Other

DMS-57014: ExecutionContext activation has failed - the incumbant context may not be the one expected.

Cause: (See message)

Action: A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.
Level: 1

Type: WARNING

Impact: Other

DMS-57015: The size of the proposed value for context parameter {0} is {1} and exceeds the permitted size of {2} for that parameter.

Cause: The execution context does not permit the storing of arbitrarily large context values; an attempt has been made to store a value which is longer that declared maximum size for that value.

Action: Determine if there is any code in the system that integrates with the Oracle DMS Context API (java package oracle.dms.context) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code, and if necessary contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

DMS-57016: The setting that controls the eager fetching of some types of execution context data has been set to {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-57017: Failed to acquire lock on context family {0} in a reasonable period of time. The lock was last acquired by thread {1}.

Cause:

Action:
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-57018: Failed to fetch data required to complete current method - will proceed by assuming the data is null.

Cause: In order to respond to a request for data the current thread needed to acquire a (read) lock on the data being accessed. The current thread waited for a period of time in order to acquire the lock but ultimately the lock was not acquired. This can happen if there is high thread contention on the lock protecting access to the data concerned. Rather than block this thread from further progress it is preferable that is it allowed to continue without fetching the data of interest.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Performance

DMS-57030: Execution context being decoded has invalid ECID or RID ({0}).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-57031: The version of the serialized string is not supported ({0}).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-57032: Decoding process failed for serialized string {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-58002: Could not create trace output directory ({0}) - Disabling {1} traces.

Cause: An attempt to create a file system directory, into which trace files were to be written, has failed. Consequently no trace information can be saved and therefore, to save unnecessary burden on the system, trace information will not be collected.

Action: Check that the system user that owns the process has permissions to create such a directory. Check that the system has sufficient disk space to create a new directory.
Level: 1

Type: WARNING

Impact: Files

DMS-58005: ignoring exception: {0}

Cause: An unanticipated problem has occurred for which the runtime code can not take automatic remedial action.

Action: Refer to the base exception to see if there is a problem with the system that can be addressed (e.g. run low in disk space, run out of memory, etc).
Level: 1

Type: WARNING

Impact: Other

DMS-58006: Problem encountered while removing old files from trace output directories.

Cause: DMS was attempting to remove old files from the trace output directories but for some reason (see base exception) has failed.

Action: The system is unlikely to fail as a consequence of this error, but disk space will be used that would otherwise have been released. Refer to the base exception to see if the problem can be addressed, and consider deleting unrequired files manually (DMS no longer needs these old files so any or all of them can be removed).
Level: 1

Type: WARNING

Impact: Files

DMS-58007: Problem encountered when closing file and associated streams.

Cause: As part of the termination of a normal read or write operation on a file the file could not be closed.

Action: If a file can not be properly closed then the operating system's file-handle associated with that file may not be properly released. An operating system can manage only a finite number of file-handles and if they are not released then new file-handles can not be created. One consequence of a depletion of file-handles is that file input/outpt on the machine concerned may be forced to come to a stop. It is more likely, however, that this is a one-off problem and that Java will tidy up the file-handle internally. This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs.
Level: 1

Type: WARNING

Impact: Files

DMS-58008: error writing trace data to disk

Cause: DMS has failed to create or use the objects required to write trace output to disk. The output intended to be written will be discarded.

Action: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs.
Level: 1

Type: WARNING

Impact: Other

DMS-58013: Problem encountered aggregating trace: {0}.

Cause: DMS has failed to perform the aggregation process on the trace data collected during the handling of this particular task or servlet request. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.

Action: Review exception details and the log for any seemingly related messages. If the problem has come from the JVM itself: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs. Otherwise the problem is with the code written to run on the JVM: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.
Level: 1

Type: WARNING

Impact: Other

DMS-58014: Failed to handle REQUEST_BEGIN for {0}. The trace will not be aggregated.

Cause: DMS did not find the trace event that marks the start of the series of trace events to be associated with an HTTP request. Without that particular trace event DMS can not be sure that the set of collected trace events will accurately represent the actions performed during that HTTP request and consequently will not process them further. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.

Action: Review exception details and the log for any seemingly related messages. If the problem has come from the JVM itself: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs. Otherwise the problem is with the code written to run on the JVM: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.
Level: 1

Type: WARNING

Impact: Other

DMS-58015: Can not get the current task's execution context and therefore the trace events that occurred during this task's lifecycle can not be used to contribute to the aggregate trace associated with the task's URL.

Cause: In order to perform the process of trace aggregation for a completed task the execution context for that task is required. In this case the execution context could not be found; without the execution context object the trace aggregation process can not be performed. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.

Action: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.
Level: 1

Type: WARNING

Impact: Other

DMS-58016: Can not get the URI associated with the current thread's recent activities.

Cause: In order to perform the process of trace aggregation for a completed task the URI associated with that task is required. In this case the URI could not be found; without the URI the trace information collected cannot be aggregated. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.

Action: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.
Level: 1

Type: WARNING

Impact: Other

DMS-58017: The maximum number of allowed aggregates has already been reached. Traces referring to URLs not already being aggregated will not contribute to aggregate information.

Cause: In order to prevent too much memory being consumed by the DMS trace system the current request will not be added to the aggregate trace set because the maximum number of URIs for which trace data will be aggregated has already been reached. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI.

Action: If aggregate trace information is not required for this request there is no action required. Otherwise please review the value of the system property oracle.dms.trace.maxAggregates.
Level: 1

Type: WARNING

Impact: Other

DMS-58018: Cannot delete old trace file: {0}.

Cause: An attempt to delete a file system file has failed (the deletion attempt was intended to keep files organized and their number manageable). The system is unlikely to fail as a consequence of this error, but disk space will be used that would otherwise have been released.

Action: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs.
Level: 1

Type: WARNING

Impact: Files

DMS-58019: Cannot generate aggregate trace data because the trace system failed initialization.

Cause: (See message)

Action: Review the log files for reports of other problems relating to initialization failure. Where possible correct those other problems and restart the system. Failure of the trace subsystem should not affect the ability of the system to execute, but will prevent traces from being produced.
Level: 1

Type: WARNING

Impact: Other

DMS-58020: failure writing DMS configuration file {0}

Cause: An error occurred attempting to save the DMS configuration file.

Action: Check that the process has permission to write the configuration file. Review log files for more information on this issue.
Level: 1

Type: WARNING

Impact: Files

DMS-58021: failure loading DMS configuration file {0}

Cause: An error occurred attempting to load the DMS configuration file.

Action: Check that the process has permission to read the configuration file, and the file exists. Review log files for more information on this issue.
Level: 1

Type: WARNING

Impact: Files

DMS-58022: failure registering DMS configuration MBean {0}

Cause: An error occurred attempting to register the DMS configuration MBean.

Action: Check that the J2EE container is up. Review log files for more information.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58023: There has been a failure activating the DMS configuration. Failed to close the event configuration file for server "{0}".

Cause: An error occurred attempting to activate the DMS configuration.

Action: Review the log files for more information.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58025: cannot instantiate class {0} for destination with id = {1}

Cause: A Destination could not be created at runtime.

Action: Check that the Destination has been configured correctly.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58026: cannot not set property {0} on an instance of class {1} for destination with id = {2}

Cause: The configuration of a destination specified one or more properties to be set on the destination before the destination was used. A problem was encountered trying to set the property listed in the message the precise details of which are also shown in the message.

Action: Verify that the property exists on the class being instantiated as the destination, and that the value is legal for that property.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58028: will not associate filter {0} and destination {1} - one or both are null or have null IDs.

Cause: (See message)

Action: Check the configuration of the filter and destination, and search the log file for other messages that may report problems creating instances of the filter or destination.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58029: initialization error when calling initDestination on destination with id {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58030: Can not disassociate filter {0} and destination {1} - no matching eventRoutes were found.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58031: shutdown error when calling shutdownDestination on destination with id {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58032: Can not remove a filter using a null or empty filter ID.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58033: Can not associate a destination, id={0}, with a filter, id={1} if the filter declares that it will not pass any events.

Cause: An instance of a filter should declare the set of event types in which it has an interest. In this particular case the set is empty and thus the filter is apparently interested in no events at all. Such a filter serves no sensible purpose and therefore will be ignored.

Action: Check the log file for other error relating to this filter to see if there were problems in its construction. Also verify the configuration of the filter and its associated destination (some filters are created implicitly to cooperate with a destination, so the configuration may only specify details of the destination).
Level: 1

Type: WARNING

Impact: Configuration

DMS-58034: Error detected while sending DMS internal http request start or stop notification.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-58035: The required Java Flight Recorder classes can not be found. The JFRDestination can not function without them.

Cause: The Java Flight Recorder classes are not available on all JVMs.

Action: Check that the system is running using a JVM that has this feature.
Level: 1

Type: WARNING

Impact: Other

DMS-58036: An exception was encountered while creating a JFR Dynamic Event to which DMS events would have been reported: eventTypeName="{0}", eventTypeDescription="{1}", eventTypePath="{2}", exception="{3}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-58037: An exception was encountered while creating a JFR Dynamic Value for nouns of type "{1}" using a value-id of "{2}" and value-name "{3}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-58038: An exception was encountered while creating a JFR Producer using the producer name "{0}", and producer path "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-58041: The FlightRecorder class is declaring that it is not active and thus DMS will not use it.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-58042: The DMS configuration file is invalid, and may not be viewed. No updates are allowed until the file has been fixed manually.

Cause: The DMS configuration file is invalid. No updates are allowed until the file has been fixed.

Action: Review the log files for more information, and correct the problem in the configuration file
Level: 1

Type: WARNING

Impact: Configuration

DMS-58043: The destination with id={0} has failed shutdown or initialization as part of the process of associating it with filter id={1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58045: DMS classic tracing will not be performed because the DMS context manager is disabled.

Cause: The classic trace features of DMS are dependent upon the DMS context manager being enabled. The DMS context manager is not enabled, and therefore the classic trace features can not operate.

Action: Review the java startup parameters to see if the DMS context manager has been disabled (check for properties with a prefix of 'oracle.dms.context')
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-58046: Classic tracing of all types (debug, triggered and aggregate) is disabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-58047: Classic tracing is already statically configured. It is not possible to reconfigure it.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58048: Classic tracing has been dynamically configured. It is not possible to configure it statically.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58049: Classic tracing has been dynamically configured. It is not possible to add another dynamic configuration. The incumbant configuration should be removed first.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58050: The directory {0} does not exist and therefore can not be used to save {1} trace data.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58051: The value {0} is not a valid integer and can not be applied to {2}. It will be ignored.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58052: Too many flight recorder destination instances

Cause: There can be at most one active flight recorder destination executing in the system at any one time (because there can be at most one DMS recording being written to the flight recorder at any one point in time).

Action: Remove the current flight recorder instance from active service (e.g. disable all related event routes in the DMS configuration) before attempting to make active the new or modified configured instance.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58053: The filter with id={0} is invalid in the dms configuration file, and will be ignored, and may be removed from the configuration file during the next update.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58054: The event route with filter id={0} and destination id={0} is invalid in the dms configuration file, and will be ignored, and may be removed from the configuration file during the next update.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58074: Unable to instantiate DiagnosticsFramework. The DMSTraceProvider will not be able to add traced data to incidents.

Cause: A problem with the DiagnosticsFramework has prevented it from being used.

Action: Check log files for any reference to failures or errors in the DiagnosticsFramework, and if possible correct them.
Level: 1

Type: WARNING

Impact: Other

DMS-58075: Failed to create a logger to which DMS trace events can be logged.

Cause: A problem has been encountered creating a logger that is required by the DMSTraceProvider.

Action: Review the exception that prevented the logger from being created, and if possible correct it.
Level: 1

Type: WARNING

Impact: Other

14 DVT-02012 to DVT-26021

DVT-02012: Column {0} exceeds boundary {1}.

Cause: The specified column number was greater than the total number of columns.

Action: Get the total number of columns, by calling the getColumnCount method of the graph or of the column header in the pivot table. Then specify a column that does not exceed the total number of columns.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02013: Row {0} exceeds boundary {1}.

Cause: The specified row number was greater than the total number of rows.

Action: Get the total number of rows, by calling the getRowCount method of the graph or of the column header in the pivot table. Then specify a row that does not exceed the total number of rows.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02015: Slice {0} exceeds boundary {1}.

Cause: The specified slice number was greater than the total number of slices.

Action: Specify a slice that does not exceed the total number of slices.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02016: Layer {0} exceeds boundary {1}.

Cause: The specified layer was greater than the total number of layers that are available on the given edge.

Action: Specify a layer that does not exceed the total number of layers.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02017: Series {0} exceeds boundary {1}.

Cause: The specified series was greater than the total series that is available in the graph.

Action: Specify a zero-based series index that does not exceed the total series. The Graph.getDisplaySeries method should provide the number of series that are displayed in the graph. Or, if Graph.isDataRowShownAsASeries returns true, then Graph.getRowCount returns the number of series that can be displayed. If Graph.isDataRowShownAsASeries returns false, then Graph.getColumnCount returns the total number of series that can be displayed.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02018: Edge {0} exceeds boundary {1}.

Cause: The specified edge was greater than the total number of edges that are available on the given edge. Valid edges for methods that require an edge are: DataDirector.COLUMN_EDGE, DataDirector.ROW_EDGE, and DataDirector.PAGE_EDGE.

Action: Specify a valid edge constant.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02019: Current DataSource does not support required type: {0}.{1}.

Cause: The DataSource did not support the required type of data in its DataMap. For example, the view requested DataMap.DATA_GROUPSORT information, and the DataSource that the view uses did not supply group sort information.

Action: Request support for the required data types in the DataSource, or use a different DataSource.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02020: DTD file cannot be found.

Cause: The specified DTD could not be found. The XML parser needed the DTD in order to validate XML files.

Action: Ensure that the specified DTD file exists, or disable XML validation. DTDs for Data Visualization components are in their respective packages. To turn off validation, call Dataview.setXMLValidated(false);.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-03000: No Mergeable object is provided.

Cause: No default Mergeable object was provided to resolve rules.

Action: Provide at least one default Mergeable object, so that rules can be resolved. For more information about Mergeable objects, see the Javadoc for the oracle.dss.rules.Mergeable interface.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-03001: attempt to call merge(Mergeable) on an incompatible Mergeable class

Cause: An attempt was made to merge incompatible Mergeable classes. Only Mergeable objects of the same class can be merged. For example, ViewStyle objects can be merged, but a ViewStyle cannot be merged with a ViewFormat.

Action: Merge two classes that are compatible. For more information, see the Javadoc for the oracle.dss.rules.RuleBundle class.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-06000: unexpected data error from Pivot Table data model

Cause: An unexpected exception was thrown by the Pivot Table's data model.

Action: Log a bug against the application. Verify that the Pivot Table's data model is configured properly.
Level: 1

Type: ERROR

Impact: Data

DVT-06001: no Converter for data type {0} during Pivot Table text formatting

Cause: The application could not create a Converter for a specific data type. The most likely reason was that a Converter was not registered for that data type.

Action: Log a bug against the application. Verify that the application can create a default Converter for all data types rendered by the Pivot Table.
Level: 1

Type: TRACE

Impact: Configuration

DVT-07001: cannot create Graph image

Cause: Under heavy loads, there was not enough memory to create the BufferedImage, or the Graphics instance from the BufferedImage. Therefore, the generated image file is empty.

Action: Reduce the memory load; for example, reduce the image size or allocate more memory to the JVM.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-08000: unexpected data error from Data Model

Cause: An invalid operation was performed by Data Model.

Action: Log a bug against the application. Verify that the Data model is configured properly.
Level: 1

Type: ERROR

Impact: Data

DVT-22004: cannot create Gauge image

Cause: Under heavy loads, there was not enough memory to create the BufferedImage, or the Graphics instance from the BufferedImage. Therefore, the generated image file is empty.

Action: Reduce the memory load; for example, reduce the image size or allocate more memory to the JVM.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-23000: End date cannot be earlier than start date.

Cause: The end date specified for the Gantt chart was earlier than the specified start date.

Action: Specify a correct start date and end date for the Gantt chart.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-23001: The time unit in the major axis must be greater than the time unit in the minor axis.

Cause: The time unit specified in the major axis was not greater than the time unit specified in the minor axis. For example, if "days" was specified as the time unit for the minor axis, then the time unit specified in the major time axis must be greater than "days", such as "months", and not anything less, such as "hours".

Action: Ensure that the time unit in the major axis is greater than the time unit in the minor axis.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-23002: An invalid time scale is specified.

Cause: The specified time scale in the major or minor axis was not recognized.

Action: Specify a valid time scale for the axis.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-23003: End date of a task cannot be earlier than its start date. Start date: {0}, End date: {1}

Cause: The end date specified for the task was earlier than its start date.

Action: Check the data to ensure that the start date and end date are loaded correctly.
Level: 1

Type: WARNING

Impact: Data

DVT-23004: No tooltip keys or labels are specified.

Cause: No tooltip keys or labels were specified in the Gantt tag.

Action: Specify keys and labels for the tooltip to ensure that the tooltip is not empty.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23005: No legend keys or labels are specified.

Cause: No legend keys or labels were specified in the Gantt tag.

Action: Specify keys and labels for the legend to ensure that the legend is not empty.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23006: The number of tooltip keys does not match the number of tooltip labels.

Cause: The number of tooltip keys did not match the number of tooltip labels specified in the Gantt tag.

Action: Ensure that the number of tooltip keys specified in the Gantt tag (tooltipKeys attribute) matches the tooltip labels specified in the Gantt tag (tooltipLabels attribute).
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23007: The number of legend keys does not match the number of legend labels.

Cause: The number of legend keys did not match the number of legend labels specified in the Gantt tag.

Action: Ensure that the number of legend keys specified in the Gantt tag (legendKeys attribute) matches the legend labels specified in the Gantt tag (legendKeyLabels attribute).
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23008: The start date of the task is out of range. Value: {0}

Cause: The start and end date of a task was outside of the time range specified for the Gantt chart.

Action: No action necessary, if it is okay not to show the task. Otherwise, verify data is correct or specify a wider time range for the Gantt chart (using the startTime and endTime attributes)
Level: 1

Type: WARNING

Impact: Data

DVT-23009: cannot find format for type {0}; skipping task: {1}

Cause: No format for type {0} was registered.

Action: Register a TaskbarFormat with the TaskbarFormatManager for the type indicated.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23010: The specified day of the week is invalid. Value: {0}

Cause: The day of the week specified was not recognized.

Action: Specify a value for the day of the week that is one of these seven constants from the java.util.Calendar class: Calendar.SUNDAY, Calendar.MONDAY, Calendar.TUESDAY, Calendar.WEDNESDAY, Calendar.THURSDAY, Calendar.FRIDAY, Calendar.SATURDAY.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23011: The value specified for alignment is invalid. Task ID: {0}

Cause: The alignment value specified for the label or icon was invalid.

Action: Specify a value for alignment that is one of these three constants from the oracle.adf.view.faces.bi.component.gantt.GanttConstants class: GanttConstants.LEFT, GanttConstants.RIGHT, GanttConstants.INSIDE.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23012: GanttDropTarget can only be attached to a Gantt component.

Cause: The GanttDropTarget tag was added as a child of a non-Gantt component.

Action: Ensure that the GanttDropTarget tag is a child tag of either a Project Gantt or Scheduling Gantt component.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23013: The start date of a task is null.

Cause: The start date of a task was null.

Action: Check the data to ensure that the start date is not null.
Level: 1

Type: WARNING

Impact: Data

DVT-23014: The task ID is null.

Cause: The task ID or split task ID was null.

Action: Check the data to ensure that the task ID or split task ID is not null.
Level: 1

Type: WARNING

Impact: Data

DVT-23015: The next date cannot be earlier than the previous date.

Cause: The next date returned by custom timescale was earlier than the previous date.

Action: Specify a correct next date.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-23016: The value supplied for the attribute is returning a wrong type.

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

Action: Chech the attribute and modify to return correct type.
Level: 1

Type: WARNING

Impact: Data

DVT-23017: The taskID is not unique in the resource. resourceID: {0}, taskID: {1}

Cause: The taskID is not unique in the resource.

Action: Check the data to ensure that the task ID is unique.
Level: 1

Type: WARNING

Impact: Data

DVT-26000: unable to find connection in {0}

Cause: Either the map configuration was not valid, or connection information was missing.

Action: Check the map configuration file.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26001: theme \"{0}\" cannot be displayed: missing value property

Cause: The value attribute of the theme was null.

Action: Check the value attribute of the theme.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26002: theme \"{0}\" cannot be displayed: invalid row key at row {1}

Cause: The specified row either did not have a row key, or the row id in the row key was null.

Action: Check the key and row id for the specified row.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26004: theme \"{0}\" cannot be displayed: row {1} with id={2} does not have a data value

Cause: The specified row did not have a data value.

Action: Check the data value for the specified row.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26005: theme \"{0}\" cannot be displayed: row {1} with id={2} does not have a location value

Cause: The specified row did not have a location value.

Action: Check the location value for the specified row.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26006: Labels for one or more rows of theme \"{0}\" are missing.

Cause: Some rows in the theme did not have a location label.

Action: Check the location labels in the theme.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-26008: Theme \"{0}\" does not have any data.

Cause: The specified theme did not return any rows.

Action: Check whether the specified theme is correctly returning no data.
Level: 1

Type: WARNING

Impact: Data

DVT-26009: unable to geocode data at row {0} of theme \"{1}\": {2}

Cause: The specified data could not be geocoded.

Action: Change the location value for the specified row.
Level: 1

Type: WARNING

Impact: Data

DVT-26010: The mouse click behavior of {0} is to render a popup, but there is no popup facet in the map.

Cause: The map had no popup facet, but the leftClickBehavior property was specified to render a popup.

Action: Check whether the mouse click behavior is correct.
Level: 1

Type: WARNING

Impact: Data

DVT-26011: The right-click behavior of {0} is to render a popup, but there is no popup facet in the map.

Cause: The map had no popup facet, but the rightClickBehavior property was specified to render a popup.

Action: Check whether the right-click behavior is correct.
Level: 1

Type: WARNING

Impact: Data

DVT-26012: The number of labels specified in legendLabels does not match the number of buckets. Legend labels: {0}, Buckets: {1}

Cause: The number of legend labels and buckets did not match.

Action: Check the number of legend labels.
Level: 1

Type: WARNING

Impact: Data

DVT-26013: unable to geocode the theme data: no Geocoder URL specified in {0}

Cause: Either the map configuration was not valid, or connection information for the Geocoder was missing.

Action: Check the map configuration file.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26014: unable to show all theme data for theme \"{0}\": multiple data values for {1} are specified but only the first data value is shown

Cause: Duplicate location data values were found.

Action: Check the data for duplicate location values.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-26015: theme \"{0}\" cannot be displayed: no longitude data at row {1}

Cause: The specified row did not have a longitude value.

Action: Check the longitude for the specified row.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26016: theme {0} cannot be displayed: no latitude data at row {1}

Cause: The specified row did not have a latitude value.

Action: Check the latitude for the specified row.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26017: unable to connect to MapViewer at {0}

Cause: A MapViewer server was not found at the specified map URL.

Action: Check whether the connection URL is correct and the MapViewer servlet can accept new requests.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26018: unable to connect to Geocoder at {0}

Cause: The component was unable to connect to the Geocoder at the specified URL.

Action: Check whether the connection URL is correct and the Geocoder can accept new requests.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26019: unable to find a map of id {0} for mapToolbar {1}

Cause: The mapId attribute of the specified mapToolbar was not correct.

Action: Check the mapId attribute of the specified mapToolbar.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26020: A map tag cannot have more than one mapOverview tag.

Cause: There were more than one mapOverview tags in the map tag.

Action: Remove any extra mapOverview tags.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26021: A map tag cannot have more than one mapLegend tag.

Cause: There were more than one mapLegend tags in the map tag.

Action: Remove any extra mapLegend tags.
Level: 1

Type: ERROR

Impact: Programmatic

15 EDQ-00300 to EDQ-10722

EDQ-00300: Could not get the properties for the database

Cause: Could not get the properties for the database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00301: Autorun dbscript chore failed to run. No database script file at {0}

Cause: Autorun dbscript chore failed to run. No database script file at {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00302: SQL error while processing dbscript chore in file {0}. Error: {1}

Cause: SQL error while processing dbscript chore in file {0}. Error: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00303: AutoRun: file {0} already exists. Aborting package!

Cause: AutoRun: file {0} already exists. Aborting package!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00304: {0} node "{1}" not found in autorun package export

Cause: {0} node "{1}" not found in autorun package export

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00305: Schema ''{0}'' load failed!

Cause: Schema ''{0}'' load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00306: Failed to encode chores {0}

Cause: Failed to encode chores {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00307: Failed to decode chores {0}

Cause: Failed to decode chores {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00308: AutoRun: file does not exist: {0}

Cause: AutoRun: file does not exist: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00309: AutoRun: Executing file: {0}

Cause: AutoRun: Executing file: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-00310: AutoRun: File does not exist, event though previously checked {0}

Cause: AutoRun: File does not exist, event though previously checked {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00311: AutoRun: error reading file: {0}

Cause: AutoRun: error reading file: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00312: Invalid chores xml

Cause: Invalid chores xml

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00313: AutoRun: {0}

Cause: AutoRun: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00314: AutoRun: has nothing to do!

Cause: AutoRun: has nothing to do!

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-00315: AutoRun: Package export complete.

Cause: AutoRun: Package export complete.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-00316: AutoRun: file {0} already exists. Aborting download {1}

Cause: AutoRun: file {0} already exists. Aborting download {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00317: AutoRun: From url: {0}, To file: {1}

Cause: AutoRun: From url: {0}, To file: {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-00318: AutoRun: Download complete: {0}

Cause: AutoRun: Download complete: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-00319: AutoRun: Package import: {0}

Cause: AutoRun: Package import: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-00320: AutoRun: Package import: {0}

Cause: AutoRun: Package import: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-00321: AutoRun: Cannot run job - project {0} not found

Cause: AutoRun: Cannot run job - project {0} not found

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00322: AutoRun: Cannot run job - job {0} not found

Cause: AutoRun: Cannot run job - job {0} not found

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00323: AutoRun: Load chore failed to run. No file at {0}

Cause: AutoRun: Load chore failed to run. No file at {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00500: JSJMS: InitialContext failure: {0}

Cause: JSJMS: InitialContext failure: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00501: JSJMS: failed to lookup connection factory ''{0}'': {1}

Cause: JSJMS: failed to lookup connection factory ''{0}'': {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00502: JSJMS: failed to lookup destination ''{0}'': {1}

Cause: JSJMS: failed to lookup destination ''{0}'': {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00503: JSJMS: failed to create connection: {0}

Cause: JSJMS: failed to create connection: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00504: JSJMS: failed to create session: {0}

Cause: JSJMS: failed to create session: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00505: JSJMS: failed to message producer: {0}

Cause: JSJMS: failed to message producer: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00506: JSJMS: error closing producer: {0}

Cause: JSJMS: error closing producer: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00507: JSJMS: error closing session: {0}

Cause: JSJMS: error closing session: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00508: JSJMS: error closing connection: {0}

Cause: JSJMS: error closing connection: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00509: JSJMS: error closing initial context: {0}

Cause: JSJMS: error closing initial context: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00510: JSJMS: error sending message: {0}

Cause: JSJMS: error sending message: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00511: JSJMS: error creating text message: {0}

Cause: JSJMS: error creating text message: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00512: JSJMS: error creating map message: {0}

Cause: JSJMS: error creating map message: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00513: JSJMS: error setting field {0} in map message: {1}

Cause: JSJMS: error setting field {0} in map message: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00514: JSJMS: error creating object message: {0}

Cause: JSJMS: error creating object message: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00600: Blueprints: problem reading blueprints schema file: {0}

Cause: Blueprints: problem reading blueprints schema file: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00601: Blueprints: problem opening local blueprint definition file {0}: {1}

Cause: Blueprints: problem opening local blueprint definition file {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00602: Blueprints: file {0} : problem parsing XML definition: {1}

Cause: Blueprints: file {0} : problem parsing XML definition: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00603: Blueprints: file {0} : root element must be {1}

Cause: Blueprints: file {0} : root element must be {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00604: Blueprints: file {0} : unknown from item "{1}" in wire

Cause: Blueprints: file {0} : unknown from item "{1}" in wire

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00605: Blueprints: file {0} : unknown to item "{1}" in wire

Cause: Blueprints: file {0} : unknown to item "{1}" in wire

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00606: Blueprints: file {0} : filter element should contain type and/or payload attributes

Cause: Blueprints: file {0} : filter element should contain type and/or payload attributes

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00607: Blueprints: file {0} : invalid isolation in wire from "{1}" to "{2}"

Cause: Blueprints: file {0} : invalid isolation in wire from "{1}" to "{2}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00608: Blueprints: file {0} : unexpected item type {1}

Cause: Blueprints: file {0} : unexpected item type {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00609: Blueprints: file {0} : constraints should be omitted for root or splitpane item

Cause: Blueprints: file {0} : constraints should be omitted for root or splitpane item

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00610: Blueprints: file {0} : constraints element for gridbag layout must be gbc, not {1}

Cause: Blueprints: file {0} : constraints element for gridbag layout must be gbc, not {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00611: Blueprints: file {0} : constraints element for border layout must be brc, not {1}

Cause: Blueprints: file {0} : constraints element for border layout must be brc, not {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00612: Blueprints: file {0} : constraints element for split pane must be spc, not {1}

Cause: Blueprints: file {0} : constraints element for split pane must be spc, not {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00613: Blueprints: file {0} : constraints element for internal layout must be plain, not {1}

Cause: Blueprints: file {0} : constraints element for internal layout must be plain, not {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00614: Blueprints: file {0} : unexpected error getting value of gbc value {1}: {2}

Cause: Blueprints: file {0} : unexpected error getting value of gbc value {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00615: Blueprints: file {0} : unexpected error getting value of gbc value {1}: {2}

Cause: Blueprints: file {0} : unexpected error getting value of gbc value {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00616: Blueprints: file {0} : failed to open link script: {1}

Cause: Blueprints: file {0} : failed to open link script: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00617: Blueprints: file {0} : link script: missing class {1}

Cause: Blueprints: file {0} : link script: missing class {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00618: Blueprints: file {0} : failed to create {1} link script engine: {2}

Cause: Blueprints: file {0} : failed to create {1} link script engine: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00619: Blueprints: file {0} : error setting importing link script root: {1}

Cause: Blueprints: file {0} : error setting importing link script root: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00620: Blueprints: file {0} : ''getLink'' function missing in link script

Cause: Blueprints: file {0} : ''getLink'' function missing in link script

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00621: Blueprints: file {0} : {1} not found - skipping file

Cause: Blueprints: file {0} : {1} not found - skipping file

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00622: Blueprints: file {0} : error scanning jar: {1}

Cause: Blueprints: file {0} : error scanning jar: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00623: Blueprints: reloaded blueprints from {0}

Cause: Blueprints: reloaded blueprints from {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-00624: Blueprints: Failed to get blueprints list: {0}

Cause: Blueprints: Failed to get blueprints list: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00625: Blueprints: Failed to get blueprint {0}: {1}

Cause: Blueprints: Failed to get blueprint {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00626: Blueprints: bph: failed to write local jar {0}: {1}

Cause: Blueprints: bph: failed to write local jar {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00627: Blueprints: bph: no loader for jarkey {0} in blueprint {1}: ignoring

Cause: Blueprints: bph: no loader for jarkey {0} in blueprint {1}: ignoring

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00628: Blueprints: error in wire filter type pattern "{0}": {1}

Cause: Blueprints: error in wire filter type pattern "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00629: Blueprints: payload class {0} in wire filter not found

Cause: Blueprints: payload class {0} in wire filter not found

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00630: Blueprints: null source in update command state

Cause: Blueprints: null source in update command state

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00631: Blueprints: unknown update command state payload from {0}: {1}

Cause: Blueprints: unknown update command state payload from {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00632: Blueprints: command {0} when not active

Cause: Blueprints: command {0} when not active

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00633: Blueprints: svg transcoder exception: {0}

Cause: Blueprints: svg transcoder exception: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00634: Blueprints: svg was {0}

Cause: Blueprints: svg was {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00635: Blueprints: No handler class declared for type {0}

Cause: Blueprints: No handler class declared for type {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00636: Blueprints: Handler class {0} not found for type {1}

Cause: Blueprints: Handler class {0} not found for type {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00637: Blueprints: Missing class ({0}) when loading handler for type {1}

Cause: Blueprints: Missing class ({0}) when loading handler for type {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00638: Blueprints: Handler class {0} does not implement {1}

Cause: Blueprints: Handler class {0} does not implement {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00639: Blueprints: Access error creating handler of class {1}

Cause: Blueprints: Access error creating handler of class {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00640: Blueprints: Error creating handler of class {1}

Cause: Blueprints: Error creating handler of class {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00641: Blueprints: error calling {0}({1} function: {2}

Cause: Blueprints: error calling {0}({1} function: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00642: Blueprints: error calling {0}({1} function: {2}

Cause: Blueprints: error calling {0}({1} function: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00643: Blueprints: SVG: no source object named {1}

Cause: Blueprints: SVG: no source object named {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00644: Blueprints: SVG: source object {0} is not a text generator

Cause: Blueprints: SVG: source object {0} is not a text generator

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00645: Blueprints: SVG: failed to create SVG document: {0}

Cause: Blueprints: SVG: failed to create SVG document: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00646: Blueprints: No tab with name {0}

Cause: Blueprints: No tab with name {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00647: Blueprints: No tab template with name {0}

Cause: Blueprints: No tab template with name {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00648: Blueprints: Tab with name {0} already exists

Cause: Blueprints: Tab with name {0} already exists

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00649: Blueprints: Failed to create new tab contents: {0}

Cause: Blueprints: Failed to create new tab contents: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00650: Blueprints: No dynamic tab with name {0}

Cause: Blueprints: No dynamic tab with name {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00651: Blueprints: bad webroot url "{0}": {1}

Cause: Blueprints: bad webroot url "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00652: Blueprints: Passing fatal error in {0} to controller: {1}

Cause: Blueprints: Passing fatal error in {0} to controller: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00700: BusinessRules: Loading XLS Business Rules ''{0}'': {1}

Cause: BusinessRules: Loading XLS Business Rules ''{0}'': {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00701: BusinessRules: Loading XLS Business Rules ''{0}'': {1}

Cause: BusinessRules: Loading XLS Business Rules ''{0}'': {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00702: BusinessRules: Failed to encode Business Rules processor config document

Cause: BusinessRules: Failed to encode Business Rules processor config document

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00703: BusinessRules: Failed to decode Business Rules processor config document

Cause: BusinessRules: Failed to decode Business Rules processor config document

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00704: BusinessRules: Error opening/reading ref data

Cause: BusinessRules: Error opening/reading ref data

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00705: BusinessRules: Error opening/reading ref data

Cause: BusinessRules: Error opening/reading ref data

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00900: Capscan: Bad Connection: {0}

Cause: Capscan: Bad Connection: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00901: Capscan: Failed to get pool info for pool {0} with error {1}

Cause: Capscan: Failed to get pool info for pool {0} with error {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-00902: Capscan: Capscan failed to connect to server: {0}, pool: {1}

Cause: Capscan: Capscan failed to connect to server: {0}, pool: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00903: Capscan: Failed to switch to pool {0} on {1}

Cause: Capscan: Failed to switch to pool {0} on {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-00904: Capscan: Capscan failed to disconnect connection to pool {1}

Cause: Capscan: Capscan failed to disconnect connection to pool {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01000: CaseManagement: Invalid set attribute name {0}

Cause: CaseManagement: Invalid set attribute name {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01001: CaseManagement: Invalid get attribute name {0}

Cause: CaseManagement: Invalid get attribute name {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01002: CaseManagement: Bulk update error

Cause: CaseManagement: Bulk update error

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01003: CaseManagement: Truncated value error

Cause: CaseManagement: Truncated value error

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01004: CaseManagement: Bulk update transaction error: {0}

Cause: CaseManagement: Bulk update transaction error: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01005: CaseManagement: Bulk update failed: {0}

Cause: CaseManagement: Bulk update failed: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01006: CaseManagement: Case Aggregator setup failed

Cause: CaseManagement: Case Aggregator setup failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01007: CaseManagement: Case Aggregator failed

Cause: CaseManagement: Case Aggregator failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01008: CaseManagement: Case Aggregator wait for threads failed

Cause: CaseManagement: Case Aggregator wait for threads failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01009: CaseManagement: Case creation worker failed

Cause: CaseManagement: Case creation worker failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01010: CaseManagement: Batch Match case creator failed

Cause: CaseManagement: Batch Match case creator failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01011: CaseManagement: String truncated to: {0}

Cause: CaseManagement: String truncated to: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01012: CaseManagement: Error in case export to landing area

Cause: CaseManagement: Error in case export to landing area

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01013: CaseManagement: Error in case export to temporary file

Cause: CaseManagement: Error in case export to temporary file

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01014: CaseManagement: Error in case import from landing area

Cause: CaseManagement: Error in case import from landing area

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01015: CaseManagement: Error in case import from temporary file

Cause: CaseManagement: Error in case import from temporary file

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01016: CaseManagement: Failed to load filter document schema: {0}

Cause: CaseManagement: Failed to load filter document schema: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01017: CaseManagement: Failed to load filter export document schema: {0}

Cause: CaseManagement: Failed to load filter export document schema: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01018: CaseManagement: Failed to load filter schema: {0}

Cause: CaseManagement: Failed to load filter schema: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01019: CaseManagement: Schema {0} load failed!

Cause: CaseManagement: Schema {0} load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01020: CaseManagement: Flag restriction Regex ''{0}'' is not valid. This will not be applied as a restriction

Cause: CaseManagement: Flag restriction Regex ''{0}'' is not valid. This will not be applied as a restriction

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01021: CaseManagement: Case History indexer failed

Cause: CaseManagement: Case History indexer failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01022: CaseManagement: Case indexer failed

Cause: CaseManagement: Case indexer failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01023: CaseManagement: Case Transition indexer failed

Cause: CaseManagement: Case Transition indexer failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01024: CaseManagement: Case Comments indexer failed

Cause: CaseManagement: Case Comments indexer failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01025: CaseManagement: No metadata for case {0}

Cause: CaseManagement: No metadata for case {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01026: CaseManagement: Supplementary Data indexer failed

Cause: CaseManagement: Supplementary Data indexer failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01027: CaseManagement: Close index writer failed

Cause: CaseManagement: Close index writer failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01028: CaseManagement: Reopen index writer failed

Cause: CaseManagement: Reopen index writer failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01029: CaseManagement: Deleting documents from index failed

Cause: CaseManagement: Deleting documents from index failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01030: CaseManagement: Deleting source ''{0}'' documents from index failed

Cause: CaseManagement: Deleting source ''{0}'' documents from index failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01031: CaseManagement: Deleting case documents from index failed

Cause: CaseManagement: Deleting case documents from index failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01032: CaseManagement: Indexing thread failed

Cause: CaseManagement: Indexing thread failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01033: CaseManagement: Index {0} submitting {1} requests

Cause: CaseManagement: Index {0} submitting {1} requests

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-01034: CaseManagement: Index submitter failed

Cause: CaseManagement: Index submitter failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01035: CaseManagement: Indexing commit failed

Cause: CaseManagement: Indexing commit failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01036: CaseManagement: Reindexing already running

Cause: CaseManagement: Reindexing already running

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01037: CaseManagement: Attempt to commit all indexes failed

Cause: CaseManagement: Attempt to commit all indexes failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01038: CaseManagement: Escalte case thread failed

Cause: CaseManagement: Escalte case thread failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01039: CaseManagement: Case escalation failed

Cause: CaseManagement: Case escalation failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01040: CaseManagement: Lock error when deleting cases for source {0} : {1}

Cause: CaseManagement: Lock error when deleting cases for source {0} : {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01041: CaseManagement: Deleting cases for source {0} failed

Cause: CaseManagement: Deleting cases for source {0} failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01042: CaseManagement: Error reloading sources

Cause: CaseManagement: Error reloading sources

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01043: CaseManagement: n. Report Info: {0}

Cause: CaseManagement: n. Report Info: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-01044: CaseManagement: Case group {0} does not exist in creator map

Cause: CaseManagement: Case group {0} does not exist in creator map

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01045: CaseManagement: Failed to get derived states for cases

Cause: CaseManagement: Failed to get derived states for cases

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01046: CaseManagement: Failed to get metadata renderer

Cause: CaseManagement: Failed to get metadata renderer

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01047: CaseManagement: Search execution failed

Cause: CaseManagement: Search execution failed

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01048: CaseManagement: Parameter selection function failed for parameter {0}

Cause: CaseManagement: Parameter selection function failed for parameter {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01049: CaseManagement: Failed to create source {0}

Cause: CaseManagement: Failed to create source {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01050: CaseManagement: Source Workflow schema ''{0}'' load failed!

Cause: CaseManagement: Source Workflow schema ''{0}'' load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01051: CaseManagement: Failed to decode source

Cause: CaseManagement: Failed to decode source

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01052: CaseManagement: Failed to encode source

Cause: CaseManagement: Failed to encode source

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01053: CaseManagement: Failed to load SMD schema: {0}

Cause: CaseManagement: Failed to load SMD schema: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01054: CaseManagement: SMD decode: rendering hint {0}

Cause: CaseManagement: SMD decode: rendering hint {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01055: CaseManagement: Failed to load Display schema: {0}

Cause: CaseManagement: Failed to load Display schema: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01056: CaseManagement: Case Notification trigger failed

Cause: CaseManagement: Case Notification trigger failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01057: CaseManagement: Case Type schema ''{0}'' load failed!

Cause: CaseManagement: Case Type schema ''{0}'' load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01058: CaseManagement: Failed to decode case types

Cause: CaseManagement: Failed to decode case types

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01059: CaseManagement: Script error in transition: {0} with message {1}

Cause: CaseManagement: Script error in transition: {0} with message {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01060: CaseManagement: Workflow Schema ''%s'' load failed!

Cause: CaseManagement: Workflow Schema ''%s'' load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01061: CaseManagement: Failed to decode workflow

Cause: CaseManagement: Failed to decode workflow

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01062: CaseManagement: Failed to encode workflow

Cause: CaseManagement: Failed to encode workflow

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01063: CaseManagement: Error decoding workflow from database: {0}

Cause: CaseManagement: Error decoding workflow from database: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01064: CaseManagement: Cannot find workflows config directory: {0}

Cause: CaseManagement: Cannot find workflows config directory: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01065: CaseManagement: Cannot load case management workflows

Cause: CaseManagement: Cannot load case management workflows

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01066: CaseManagement: Cannot load workflow file: {0}

Cause: CaseManagement: Cannot load workflow file: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01067: CaseManagement: Cannot save workflow from file: {0}

Cause: CaseManagement: Cannot save workflow from file: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01068: CaseManagement: Error with waiting for bulk indexing

Cause: CaseManagement: Error with waiting for bulk indexing

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01069: Error collating supplementary data: {0}

Cause: CaseManagement: Error collating supplementary data

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01070: Error exporting cases: {0}

Cause: CaseManagement: Error exporting cases

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01071: Error releasing index queue {0}

Cause: CaseManagement: Error releasing queue

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01072: Error on case management startup {0}

Cause: CaseManagement: Error starting up case management

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01073: Report has too many results. User {0}, Filter {1}, Axis {2}

Cause: CaseManagement: Report has too many columns

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01100: CaseMigration: SMD decode: rendering hint not recognised: {0}

Cause: CaseMigration: SMD decode: rendering hint not recognised: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01101: Database error occurred: {0}

Cause: Database error occurred: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01700: DashboardExport: Undefined process id

Cause: DashboardExport: Undefined process id

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01701: DashboardExport: Publish failed: {0}

Cause: DashboardExport: Publish failed: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01702: DashboardExport: Publish failed: {0}

Cause: DashboardExport: Publish failed: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01703: DashboardExport: Finished export job

Cause: DashboardExport: Finished export job

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-01704: DashboardExport: Problem with XML subsystem configuration {0}

Cause: DashboardExport: Problem with XML subsystem configuration {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01705: DashboardExport: Problem getting list of projects.

Cause: DashboardExport: Problem getting list of projects.

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01706: DashboardExport: Problem getting list of projects.

Cause: DashboardExport: Problem getting list of projects.

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01707: DashboardExport: Problem getting spigot count

Cause: DashboardExport: Problem getting spigot count

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01708: DashboardExport: Failed to build report.

Cause: DashboardExport: Failed to build report.

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01800: Error in database operation: {0}

Cause: Error in database operation: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01801: Error executing SQL {1} on database: {0}

Cause: Error executing SQL {1} on database: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01802: Next exception: {0}

Cause: Next exception: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-01803: {0}.class not in {1}

Cause: {0}.class not in {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-01804: Bad regex "{0}" in {1}: {2}

Cause: Bad regex "{0}" in {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02000: Databases: system landing area directory is {0}

Cause: Databases: system landing area directory is {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02001: Databases: error canonicalizing landing area path "{0}": {1}

Cause: Databases: error canonicalizing landing area path "{0}": {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02002: Databases: error canonicalizing landing area file "{0}": {1}

Cause: Databases: error canonicalizing landing area file "{0}": {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02003: Databases: problem opening local definition file {0}: {1}

Cause: Databases: problem opening local definition file {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02004: Databases: problem reading database XML file {0}: {1}

Cause: Databases: problem reading database XML file {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02005: Databases: {0}: database type {1}: must include url or drivers element

Cause: Databases: {0}: database type {1}: must include url or drivers element

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02006: Databases: {0}: database type {1}: cannot use driver/url and drivers element

Cause: Databases: {0}: database type {1}: cannot use driver/url and drivers element

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02007: Databases: {0}: database type {1}: driver {2} rejected because {3} does not exist

Cause: Databases: {0}: database type {1}: driver {2} rejected because {3} does not exist

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02008: Databases: {0}: database type {1}: driver {2} rejected because no files matched pattern {3}

Cause: Databases: {0}: database type {1}: driver {2} rejected because no files matched pattern {3}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02009: Databases: {0}: database type {1} has no valid drivers

Cause: Databases: {0}: database type {1} has no valid drivers

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02010: Databases: {0}: database type {1}: fields ignored if configuration class is used

Cause: Databases: {0}: database type {1}: fields ignored if configuration class is used

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02011: Databases: {0}: unknown choice default "{1}" in field {2}

Cause: Databases: {0}: unknown choice default "{1}" in field {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02012: Databases: {0}: bad numeric default {1} for field {2}

Cause: Databases: {0}: bad numeric default {1} for field {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02013: Databases: error reading option properties file {0}: {1}

Cause: Databases: error reading option properties file {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02014: Databases: error loading option properties file {0}: {1}

Cause: Databases: error loading option properties file {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02015: Databases: {0}: invalid regex "{1}" in {2}: {3}

Cause: Databases: {0}: invalid regex "{1}" in {2}: {3}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02016: Databases: {0}: invalid expression "{1}" in {2}: {3}

Cause: Databases: {0}: invalid expression "{1}" in {2}: {3}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02017: Databases: {0}: bad ''invalid'' character set "{1}" for {2}: {3}

Cause: Databases: {0}: bad ''invalid'' character set "{1}" for {2}: {3}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02018: Databases: species {0} not found: mapping to zombie

Cause: Databases: species {0} not found: mapping to zombie

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02019: Databases: {0} not found in database jar {1} - skipping file

Cause: Databases: {0} not found in database jar {1} - skipping file

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02020: Databases: error scanning species jar {0}: {1}

Cause: Databases: error scanning species jar {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02021: Databases: bad OS match regex {0}: {1}

Cause: Databases: bad OS match regex {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02022: Databases: {0}: cannot load driver class {1}

Cause: Databases: {0}: cannot load driver class {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02023: Databases: Error creating instance of driver class {0}: {1}

Cause: Databases: Error creating instance of driver class {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02024: Databases: failed to get columns for "{0}": {1}

Cause: Databases: failed to get columns for "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02025: Databases: could not retrieve primary key information for {0} table {1}: {2}

Cause: Databases: could not retrieve primary key information for {0} table {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02026: Databases: unknown column {0} in index {1}

Cause: Databases: unknown column {0} in index {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02027: Databases: could not retrieve index information for {0} table {1}: {2}

Cause: Databases: could not retrieve index information for {0} table {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02028: Databases: error getting local db file {0}: {1}

Cause: Databases: error getting local db file {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02029: Databases: local db file {0} no longer exists

Cause: Databases: local db file {0} no longer exists

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02030: Databases: error in expression "{0}": {1}

Cause: Databases: error in expression "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02031: Databases client: failed to get initial database type list: {0}

Cause: Databases client: failed to get initial database type list: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02032: Databases client: species {0} not found: mapping to zombie

Cause: Databases client: species {0} not found: mapping to zombie

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02033: Databases client: recreating database of species {0} because of generation change: {1} -> {2}

Cause: Databases client: recreating database of species {0} because of generation change: {1} -> {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02034: Databases client: error recreating {0} database: {1}

Cause: Databases client: error recreating {0} database: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02035: Databases client: failed to write local jar {0}: {1}

Cause: Databases client: failed to write local jar {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02036: Databases client: no loader for jarkey {0} in species {1}: ignoring

Cause: Databases client: no loader for jarkey {0} in species {1}: ignoring

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02037: Databases JDBC: invalid fetchsize parameter {0}

Cause: Databases JDBC: invalid fetchsize parameter {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02038: Databases JDBC: failed to set fetchsize to {0}: {1}

Cause: Databases JDBC: failed to set fetchsize to {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02039: Databases JDBC: bad batchsize setting {0}

Cause: Databases JDBC: bad batchsize setting {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02040: Databases XML: {0}: cannot find xsllist resource {1}

Cause: Databases XML: {0}: cannot find xsllist resource {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02041: Databases XML: {0}: incorrect number of fields in xsllist line "{1}"

Cause: Databases XML: {0}: incorrect number of fields in xsllist line "{1}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02042: Databases XML: {0}: XML template resource {1} not found

Cause: Databases XML: {0}: XML template resource {1} not found

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02043: Databases XML: {0}: XML template is required with JS decoder {1}

Cause: Databases XML: {0}: XML template is required with JS decoder {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02044: Databases XML: {0}: element path is required with JS decoder {1}

Cause: Databases XML: {0}: element path is required with JS decoder {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02045: Databases XML: {0}: XSL resource {1} not found

Cause: Databases XML: {0}: XSL resource {1} not found

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02046: Databases XML: {0}: error reading xsllist: {1}

Cause: Databases XML: {0}: error reading xsllist: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02047: Database species {0}: failed to create provider: {1}

Cause: Database species {0}: failed to create provider: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02100: Unknown interface attribute {0} in mapping

Cause: Unknown interface attribute {0} in mapping

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02101: Unknown real attribute {0} in mapping

Cause: Unknown real attribute {0} in mapping

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02102: Types of virtual attribute {0} and real attribute {1} do not match

Cause: Types of virtual attribute {0} and real attribute {1} do not match

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02103: Error parsing xml

Cause: Error parsing xml

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02104: Error encoding {0} "{1}"

Cause: Error encoding {0} "{1}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02105: Data interface "{0}", mapping "{1}": {2}

Cause: Data interface "{0}", mapping "{1}": {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02106: Error loading {0} "{1}": {2}

Cause: Error loading {0} "{1}": {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02107: Error loading {0} "{1}"

Cause: Error loading {0} "{1}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02108: Schema "{0}" load failed!

Cause: Schema "{0}" load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02109: Failed to decode interface

Cause: Failed to decode interface

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02110: Error encoding interface

Cause: Error encoding interface

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02111: Failed to get the Data Interface for Dependency Object: {0}, Project: {1}

Cause: Failed to get the Data Interface for Dependency Object: {0}, Project: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02112: Failed to decode interface mapping

Cause: Failed to decode interface mapping

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02113: Error encoding interface mapping

Cause: Error encoding interface mapping

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02114: Error creating staged data: {0}

Cause: Error creating staged data: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02115: Error during data interface diff

Cause: Error during data interface diff

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02116: Error deleting data interface implementations for: {0}

Cause: Error deleting data interface implementations for: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02200: Augment {0}: species {1}: table does not have any columns!!

Cause: Augment {0}: species {1}: table does not have any columns!!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02201: Augment {0} for species {1}: database error: {2}

Cause: Augment {0} for species {1}: database error: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02202: Schema "{0}" load failed!

Cause: Schema "{0}" load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02203: Failed to decode data source

Cause: Failed to decode data source

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02204: Failed to encode data source

Cause: Failed to encode data source

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02205: Error during data source diff

Cause: Error during data source diff

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02206: There was a problem deleting the data sources for project {0}

Cause: There was a problem deleting the data sources for project {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02207: Cannot retrieve data source for id: {0} in project: {1}

Cause: Cannot retrieve data source for id: {0} in project: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02208: Error ending transaction

Cause: Error ending transaction

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02209: {0} XStore items found in import file: {1}, {2}, {3}

Cause: {0} XStore items found in import file: {1}, {2}, {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02210: RmiJdbc server bound to registry

Cause: RmiJdbc server bound to registry

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02211: Failed to register RmiJdbcServer: {0}

Cause: Failed to register RmiJdbcServer: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02212: RmiJdbc server unbound from registry

Cause: RmiJdbc server unbound from registry

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02213: Failed to unbind RmiJdbcServer: {0}

Cause: Failed to unbind RmiJdbcServer: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02300: Data upload is cancelled so returning from data insert without inserting

Cause: Data upload is cancelled so returning from data insert without inserting

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02301: Total number of snapshot rows loaded for table {0} is {1}

Cause: Total number of snapshot rows loaded for table {0} is {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02302: Cancelling queue for table {0}

Cause: Cancelling queue for table {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02303: Error cancelling upload

Cause: Error cancelling upload

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02304: Uploader client: transporter exception thrown

Cause: Uploader client: transporter exception thrown

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02400: Error initialising asset tree for asset type: {0}

Cause: Error initialising asset tree for asset type: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02401: Schema "{0}" load failed!

Cause: Schema "{0}" load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02402: Asset type "{0}" ignored. {1} is wrong type

Cause: Asset type "{0}" ignored. {1} is wrong type

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02403: Asset type "{0}" ignored. {1} cannot be instantiated.

Cause: Asset type "{0}" ignored. {1} cannot be instantiated.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02404: Error executing script: {0}

Cause: Error executing script: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02405: Error loading asset tree: {0}

Cause: Error loading asset tree: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02406: Error loading asset tree

Cause: Error loading asset tree

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02407: Cannot create java script engine

Cause: Cannot create java script engine

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02408: Error deleting object with zero dependency references

Cause: Error deleting object with zero dependency references

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02409: Message from diff: {0}

Cause: Message from diff: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02410: Error performing diff

Cause: Error performing diff

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02411: Diff complete in {0}ms

Cause: Diff complete in {0}ms

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02412: Malformed UUID in {0}/{1}/{2}

Cause: Malformed UUID in {0}/{1}/{2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02413: Updating xtree cache

Cause: Updating xtree cache

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02414: XTree data does not have a version 0: nodeId: {0}, nodeType: {1}, ver:{2}

Cause: XTree data does not have a version 0: nodeId: {0}, nodeType: {1}, ver:{2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02415: Error loading the source (xml) for: {0}

Cause: Error loading the source (xml) for: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02416: Data bean creation for type {0} on {1} failed: {2}

Cause: Data bean creation for type {0} on {1} failed: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02417: Failed to encode xtree node data

Cause: Failed to encode xtree node data

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02418: Failed to decode processor runtime

Cause: Failed to decode processor runtime

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02419: Permission error: {0}

Cause: Permission error: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02500: Error during diff

Cause: Error during diff

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02501: Error creating diff support

Cause: Error creating diff support

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02700: Publishing widget: Loading shape {0}.{1}.{2}

Cause: Publishing widget: Loading shape {0}.{1}.{2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02700: Notification error: {0}

Cause: Notification error: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02701: Error loading dg systems remotely

Cause: Error loading dg systems remotely

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02701: EventLogManager: User not found for id {0}

Cause: EventLogManager: User not found for id {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02702: Error loading divisions

Cause: Error loading divisions

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02702: EventLogManager: Project not found for id {0}

Cause: EventLogManager: Project not found for id {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02703: PublishingWidget: Failed to encode processor config document

Cause: PublishingWidget: Failed to encode processor config document

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02703: Error logging event: {0}

Cause: Error logging event: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02704: PublishingWidget: Failed to decode processor config document

Cause: PublishingWidget: Failed to decode processor config document

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02704: Export error: {0}

Cause: Export error: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02705: PublishingWidget: Failed to load divisions

Cause: PublishingWidget: Failed to load divisions

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02706: PublishingWidget: Failed to load data sets

Cause: PublishingWidget: Failed to load data sets

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02707: PublishingWidget: Failed to load data sets

Cause: PublishingWidget: Failed to load data sets

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02708: PublishingWidget: Failed to load data governance systems

Cause: PublishingWidget: Failed to load data governance systems

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02709: PublishingWidget: Failed to load divisions for system {0}

Cause: PublishingWidget: Failed to load divisions for system {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02710: PublishingWidget: Failed to load data sets for system {0}, division {1}

Cause: PublishingWidget: Failed to load data sets for system {0}, division {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02800: Schema "{0}" load failed!

Cause: Schema "{0}" load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02801: Failed to decode snapshot

Cause: Failed to decode snapshot

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02802: Failed to encode export

Cause: Failed to encode export

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02803: Error retrieving export: {0}

Cause: Error retrieving export: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02804: There was a problem deleting the exports for project {0}

Cause: There was a problem deleting the exports for project {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02805: Error formulating message: {0}

Cause: Error formulating message: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02806: Error during export diff

Cause: Error during export diff

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02807: Reopened export writer on attempt {0}

Cause: Reopened export writer on attempt {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02808: Error ending transaction

Cause: Error ending transaction

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02809: There was an error retrieving exports for projectId {0} returning no export streaming consumers

Cause: There was an error retrieving exports for projectId {0} returning no export streaming consumers

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02810: Finished execution in {0}s

Cause: Finished execution in {0}s

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02811: Error running export task

Cause: Error running export task

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02812: Non-numeric found expected for column {0} in export {1} (table {2})

Cause: Non-numeric found expected for column {0} in export {1} (table {2})

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02813: Insert error for {0}: {1}

Cause: Insert error for {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02814: Unable to close results read: {0}

Cause: Unable to close results read: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02815: Execution thread notifying cancel thread that job is ended.

Cause: Execution thread notifying cancel thread that job is ended.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02816: Problem closing db inserter to table {0}

Cause: Problem closing db inserter to table {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02817: Problem closing db insertion creator to table {0}

Cause: Problem closing db insertion creator to table {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02818: Starting execution of export batch {0}

Cause: Starting execution of export batch {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02819: Export batch {0} terminated by exception

Cause: Export batch {0} terminated by exception

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02820: Export batch {0} complete

Cause: Export batch {0} complete

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02821: Numeric value expected for column {0} in export {1} to table {2} but was {3}. Setting column value to null.

Cause: Numeric value expected for column {0} in export {1} to table {2} but was {3}. Setting column value to null.

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02822: Date value expected for date type column {0} in export {1} to table {2} but was {3}. Setting column value to null.

Cause: Date value expected for date type column {0} in export {1} to table {2} but was {3}. Setting column value to null.

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02823: Time value expected for date type column {0} in export {1} to table {2} but was {3}. Setting column value to null.

Cause: Time value expected for date type column {0} in export {1} to table {2} but was {3}. Setting column value to null.

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-02824: Cancelling job

Cause: Cancelling job

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-02825: Unable to make thread wait: {0}

Cause: Unable to make thread wait: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-02900: Bad regex "{0}"

Cause: Bad regex "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03000: Schema "{0}" load failed!

Cause: Schema "{0}" load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03001: More than one tree item found for externalized property

Cause: More than one tree item found for externalized property

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03002: Error ending transaction

Cause: Error ending transaction

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03003: {0} XStore items found in import file: {1}, {2}, {3}

Cause: {0} XStore items found in import file: {1}, {2}, {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03100: Processing resource jars

Cause: Processing resource jars

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03101: Failed to parse schema: {0}

Cause: Failed to parse schema: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03102: Processing resource jar {0}

Cause: Processing resource jar {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03103: {0} not found in resources file {1}

Cause: {0} not found in resources file {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03104: Could not parse {0} in {1}: {2}

Cause: Could not parse {0} in {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03105: No resources listed in {0}

Cause: No resources listed in {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03106: Cannot locate resource class {0} in {1}

Cause: Cannot locate resource class {0} in {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03107: Cannot initialize resource class {0} in {1}: {2}

Cause: Cannot initialize resource class {0} in {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03108: Resource class {0} in {1} does not extend {2}

Cause: Resource class {0} in {1} does not extend {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03109: Error creating a {0}: {1}

Cause: Error creating a {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03110: Configure failed for {0} in {1}: {2}

Cause: Configure failed for {0} in {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03111: Error reading from resources file {0}: {1}

Cause: Error reading from resources file {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03112: Invalid database species type for resource: {0}

Cause: Invalid database species type for resource: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03113: Error initialising external database resource handle: {0}

Cause: Error initialising external database resource handle: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03114: Error querying datastore {0}: {1}

Cause: Error querying datastore {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03115: Failed to encode external lookup xml

Cause: Failed to encode external lookup xml

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03116: Failed to decode external lookup xml

Cause: Failed to decode external lookup xml

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03117: DataSourceException trying to retrieve data source {0} for lookup {1}

Cause: DataSourceException trying to retrieve data source {0} for lookup {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03118: Schema "{0}" load failed!

Cause: Schema "{0}" load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03119: Failed to load external resource configuration: {0}

Cause: Failed to load external resource configuration: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03120: Failed to encode external resource

Cause: Failed to encode external resource

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03121: {0} XStore items found in import file: {1}, {2}, {3}

Cause: {0} XStore items found in import file: {1}, {2}, {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03122: Starting migration of file {0} as current version is less than file version.

Cause: Starting migration of file {0} as current version is less than file version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03123: Could not convert file {0} as the resource structure is different from the existing user data.

Cause: Could not convert file {0} as the resource structure is different from the existing user data.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03124: Finished migration of file. Migrated {0} rows.

Cause: Finished migration of file. Migrated {0} rows.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03125: Starting migration of file {0} as no current version found.

Cause: Starting migration of file {0} as no current version found.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03126: Failed to create/update User Data {0} where migrating file

Cause: Failed to create/update User Data {0} where migrating file

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03127: Failed to create Lookup {0} when migrating file

Cause: Failed to create Lookup {0} when migrating file

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03128: Failed to save User Data data for {0}

Cause: Failed to save User Data data for {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03129: Failed to save User Data data for {0}, unable to get lock

Cause: Failed to save User Data data for {0}, unable to get lock

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03130: Failed to save User Data data for {0}, insufficient permission: {1}

Cause: Failed to save User Data data for {0}, insufficient permission: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03131: There was a problem deleting the lookup for project {0}

Cause: There was a problem deleting the lookup for project {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03132: Unable to get dependencies for lookups based on : {0}

Cause: Unable to get dependencies for lookups based on : {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03133: Unable to get data profile for lookup based upon underlying with name {0}

Cause: Unable to get data profile for lookup based upon underlying with name {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03134: Error when updating node with id {0}

Cause: Error when updating node with id {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03135: Error during lookup diff: {0} --- {1}

Cause: Error during lookup diff: {0} --- {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03136: Error trying to retrieve staged data underlying {0} for lookup {1}

Cause: Error trying to retrieve staged data underlying {0} for lookup {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03137: Error initialising staged data resource handle: {0}

Cause: Error initialising staged data resource handle: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03138: Error initialising staged data resource

Cause: Error initialising staged data resource

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03139: Error trying to retrieve user data underlying {0} for lookup {1}

Cause: Error trying to retrieve user data underlying {0} for lookup {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03140: Error initialising user data resource handle: {0}

Cause: Error initialising user data resource handle: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03141: Discarded cache entry for ID {0}

Cause: Discarded cache entry for ID {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03142: Cache clear for {0} [{1}]

Cause: Cache clear for {0} [{1}]

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03143: {0}: {1} records loaded to {2} distinct keys in {3}s

Cause: {0}: {1} records loaded to {2} distinct keys in {3}s

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03144: Error validating reference data ''{1}'', column ''{0}'' has a mismatching data type

Cause: Error validating reference data ''{1}'', column ''{0}'' has a mismatching data type

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03145: Error validating reference data ''{1}'', column ''{0}'' is missing

Cause: Error validating reference data ''{1}'', column ''{0}'' is missing

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03200: Error getting default JPS Context: {0}

Cause: Error getting default JPS Context: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03210: Error querying reading credential using map {0} and key {1}: {2}

Cause: Error querying reading credential using map {0} and key {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03211: Access error querying credential using map {0} and key {1}: {2}

Cause: Access error querying credential using map {0} and key {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03212: Error reading credential using map {0} and key {1}: {2}

Cause: Error reading credential using map {0} and key {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03213: Access error reading credential using map {0} and key {1}: {2}

Cause: Access error reading credential using map {0} and key {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03214: Credential at map {0} and key {1} is not a PasswordCredential

Cause: Credential at map {0} and key {1} is not a PasswordCredential

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03215: Error setting credential using map {0} and key {1}: {2}

Cause: Error setting credential using map {0} and key {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03216: Access error setting credential using map {0} and key {1}: {2}

Cause: Access error setting credential using map {0} and key {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03220: Error getting keystore {0} from stripe {1}: {2}

Cause: Error getting keystore {0} from stripe {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03221: Access error getting keystore {0} from stripe {1}: {2}

Cause: Access error getting keystore {0} from stripe {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03230: Error getting EDQ JPS auditor: {0}

Cause: Error getting EDQ JPS auditor: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03231: Permission denied getting EDQ JPS auditor: {0}

Cause: Permission denied getting EDQ JPS auditor: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03232: Error generating audit event: {0}

Cause: Error generating audit event: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03234: Error generating group audit event: {0}

Cause: Error generating group audit event: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03240: Error lookup up system MBean server at "{0}": {1}

Cause: Error lookup up system MBean server at "{0}": {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03241: Error making MBean ObjectName "{0}": {1}

Cause: Error making MBean ObjectName "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03242: Error registering MBean "{0}": {1}

Cause: Error registering MBean "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03243: Error unregistering "{0}": {1}

Cause: Error unregistering "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03244: Error initializing EM support MBeans: {0}

Cause: Error initializing EM support MBeans: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03250: Error initializing server state monitoring: {0}

Cause: Error querying MBean: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03260: TaskMaster: error getting executor for DMS cleanup: {0}

Cause: TaskMaster: error getting executor for DMS cleanup: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03261: TaskMaster: non-leaf task node {0} not instrumented!

Cause: TaskMaster: non-leaf task node {0} not instrumented!

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03300: {0} Error getting given name cultures: {1}

Cause: {0} Error getting given name cultures: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03301: {0} Error getting surname cultures: {1}

Cause: {0} Error getting surname cultures: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03302: {0} Error getting name cultures: {1}

Cause: {0} Error getting name cultures: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03303: {0} Error writing summary metric

Cause: {0} Error writing summary metric

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03304: {0} Error getting given name culture: {1}

Cause: {0} Error getting given name culture: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03305: {0} Error getting surname culture: {1}

Cause: {0} Error getting surname culture: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03306: {0} Error getting name culture: {1}

Cause: {0} Error getting name culture: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03307: {0} Failed to get configuration file list from server

Cause: {0} Failed to get configuration file list from server

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03400: Error buffering image from url "{0}" : {1}

Cause: Error buffering image from url "{0}" : {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03401: Unable to load icon for {0} with icon {1}

Cause: Unable to load icon for {0} with icon {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03402: Unable to load small icon for {0} with icon {1}

Cause: Unable to load small icon for {0} with icon {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03500: Error opening dialog : {1}

Cause: Error opening dialog : {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03501: Schema "{0}" load failed!

Cause: Schema "{0}" load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03600: Initialising...

Cause: Initialising...

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03601: Locale: {0}

Cause: Locale: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03602: Management port: {0}

Cause: Management port: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03603: Closing down...

Cause: Closing down...

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03604: Finished.

Cause: Finished.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03605: Error storing login preferences

Cause: Error storing login preferences

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03606: Error storing user guid preference

Cause: Error storing user guid preference

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03607: Accessing preferences to reset session ports: {0}

Cause: Accessing preferences to reset session ports: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03608: An error has occurred: {0}

Cause: An error has occurred: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03609: Attempting to handoff to existing port: {0}

Cause: Attempting to handoff to existing port: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03610: Handoff accepted on port: {0}

Cause: Handoff accepted on port: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03611: Handoff refused on port: {0}

Cause: Handoff refused on port: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03612: Error logging in

Cause: Error logging in

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03613: Aborting after timeout

Cause: Aborting after timeout

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03614: Schema "{0}" load failed!

Cause: Schema "{0}" load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03615: Login to "{0}" as "{1}" successful

Cause: Login to "{0}" as "{1}" successful

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03616: Login to "{0}" as "{1}" failed: {2}

Cause: Login to "{0}" as "{1}" failed: {2}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03617: Logging out from server: {0}

Cause: Logging out from server: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-03618: Error in thread {0}

Cause: Error in thread {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03619: Error during event dispatching

Cause: Error during event dispatching

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03700: Error creating action

Cause: Error creating action

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03701: Error loading xml: {0}

Cause: Error loading xml: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03702: Runtime Error

Cause: Runtime Error

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03703: Server Error

Cause: Server Error

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03704: Error

Cause: Error

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-03705: Icon not found: {0}

Cause: Icon not found: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-03900: Error loading xml: {0}

Cause: Error loading xml: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04000: Failed to find cleaning task named: {0}

Cause: Failed to find cleaning task named: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-04001: Cleaning task named: {0} isn't actually a cleaning task

Cause: Cleaning task named: {0} isn't actually a cleaning task

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-04002: Failed to parse housekeeping configuration

Cause: Failed to parse housekeeping configuration

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04003: Failed to read housekeeping configuration file

Cause: Failed to read housekeeping configuration file

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04004: Failed to parse start time for {0} defaulting to now

Cause: Failed to parse start time for {0} defaulting to now

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-04005: Failed to find cleaning task named: {0}

Cause: Failed to find cleaning task named: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-04006: Cleaning task named: {0} isn't actually a cleaning task

Cause: Cleaning task named: {0} isn't actually a cleaning task

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-04007: Cleaning task error in task named: {0}

Cause: Cleaning task error in task named: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04300: Failed to decode image from {0}

Cause: Failed to decode image from {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04301: Failed to decode images

Cause: Failed to decode images

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04302: Failed to encode image

Cause: Failed to encode image

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04303: Error loading image {0} from database

Cause: Error loading image {0} from database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04304: Error storing image in database

Cause: Error storing image in database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04305: Permission error storing image:

Cause: Permission error storing image:

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04306: Error storing image in database

Cause: Error storing image in database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04307: Permission error updating image:

Cause: Permission error updating image:

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04308: Error storing image in database

Cause: Error storing image in database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04309: Error updating image in database

Cause: Error updating image in database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04310: Error deleting image from database

Cause: Error deleting image from database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04311: Permission error deleting image:

Cause: Permission error deleting image:

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04312: Error deleting image from database

Cause: Error deleting image from database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04313: Error loading image xtree node from database

Cause: Error loading image xtree node from database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04314: This error will not affect normal operation. Image data for: {0}

Cause: This error will not affect normal operation. Image data for: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-04315: {0} XStore items found in import file: {1}, {2}, {3}

Cause: {0} XStore items found in import file: {1}, {2}, {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04500: Error loading issue list for xtree

Cause: Error loading issue list for xtree

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04501: [retrieveProjectIssues] Invalid parameters for dao method

Cause: [retrieveProjectIssues] Invalid parameters for dao method

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04502: [retrieveAllIssuesByAssginedTo] Invalid parameters for dao method

Cause: [retrieveAllIssuesByAssginedTo] Invalid parameters for dao method

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04503: DNInvalidQueryParametersException. Invalid parameters for dao method. Unable to insert issue data. The message was {0}

Cause: DNInvalidQueryParametersException. Invalid parameters for dao method. Unable to insert issue data. The message was {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04504: DNInvalidQueryParametersException. Invalid parameters for dao method. Unable to update issue data. The message was {0}

Cause: DNInvalidQueryParametersException. Invalid parameters for dao method. Unable to update issue data. The message was {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04505: DNInvalidQueryParametersException. Invalid parameters for dao method. Unable to update issue data. The message was {0}

Cause: DNInvalidQueryParametersException. Invalid parameters for dao method. Unable to update issue data. The message was {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04506: Error running trigger. {0}

Cause: Error running trigger. {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04600: Schema '{0}' load failed!

Cause: Schema '{0}' load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04601: Failed to decode job

Cause: Failed to decode job

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04602: Cannot find option transcoder for option "{0}"

Cause: Cannot find option transcoder for option "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-04603: Error during job diff {0}

Cause: Error during job diff {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-04604: Error encoding job: {0}

Cause: Error encoding job: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04605: Database error creating job: {0}

Cause: Database error creating job: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04606: Error adding dependencies when creating job: {0}

Cause: Error adding dependencies when creating job: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04607: Error encoding job: {0}

Cause: Error encoding job: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04608: Database error saving job: {0}

Cause: Database error saving job: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04609: Error replacing dependencies when saving job: {0}

Cause: Error replacing dependencies when saving job: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04610: Database error renaming job: {0}

Cause: Database error renaming job: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04611: Database error deleting job: {0}

Cause: Database error deleting job: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04612: Error deleting dependencies when deleting job: {0}

Cause: Error deleting dependencies when deleting job: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04613: A database error occurred loading XTree nodes: {0}

Cause: A database error occurred loading XTree nodes: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04614: A database error occurred loading an XTree node: {0}

Cause: A database error occurred loading an XTree node: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04615: A database error occurred loading a job: {0}

Cause: A database error occurred loading a job: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04616: An error occurred decoding job: {0}

Cause: An error occurred decoding job: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04617: Error, job id: {0} could not be loaded

Cause: Error, job id: {0} could not be loaded

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04618: Unknown task type: {0}

Cause: Unknown task type: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-04619: A database error occurred retrieving node for dependency subject: {0}

Cause: A database error occurred retrieving node for dependency subject: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04620: A database error occurred retrieving node for dependency object: {0}

Cause: A database error occurred retrieving node for dependency object: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04621: {0} XStore items found in import file: {1}, {2}, {3}

Cause: {0} XStore items found in import file: {1}, {2}, {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04622: An error occurred retrieving trigger names: {0}

Cause: An error occurred retrieving trigger names: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04623: Error starting job: {0}

Cause: Error starting job: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04700: loadLicence error: {0}

Cause: loadLicence error: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04701: Error reading licence file {0}: {1}

Cause: Error reading licence file {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04702: Error reading additional licence file {0}: {1}

Cause: Error reading additional licence file {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04800: Error releasing locks when helper destroyed

Cause: Error releasing locks when helper destroyed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04900: A system error has occurred

Cause: A system error has occurred

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04901: Details: {0}

Cause: Details: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04902: Please contact support for assistance

Cause: Please contact support for assistance

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-04910: Problem parsing log records: {0}

Cause: Problem parsing log records: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05000: Error ending transaction

Cause: Error ending transaction

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05001: Schema '{0}' load failed!

Cause: Schema '{0}' load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05002: Failed to decode user data attributes

Cause: Failed to decode user data attributes

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05003: Failed to encode user data attributes

Cause: Failed to encode user data attributes

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05100: Error in initialisation {0}

Cause: Error in initialisation {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05200: Error storing local remote object {0}: {1}

Cause: Error storing local remote object {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05201: Problem managing {0} object

Cause: Problem managing {0} object

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05202: Bean at {0} already registered

Cause: Bean at {0} already registered

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05203: Error registering {0} bean

Cause: Error registering {0} bean

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05204: Invalid ObjectName {0}: {1}

Cause: Invalid ObjectName {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05205: ObjectName {0} not found in server when unregistering

Cause: ObjectName {0} not found in server when unregistering

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05206: Error unregistering bean: {0}

Cause: Error unregistering bean: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05207: MBeanServer at JNDI name {0} not found: {1}

Cause: MBeanServer at JNDI name {0} not found: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05208: Problem registering a platform bean: {0}

Cause: Problem registering a platform bean: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05209: Bad value "{0}" for ssl clientauth property

Cause: Bad value "{0}" for ssl clientauth property

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05210: Error creating key manager for JMX SSL: {0}

Cause: Error creating key manager for JMX SSL: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05211: Error creating SSL server socket factory: {0}

Cause: Error creating SSL server socket factory: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05212: Error creating registry for JMX SSL: {0}

Cause: Error creating registry for JMX SSL: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05213: Problem exporting management remote objects: {0}

Cause: Problem exporting management remote objects: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05214: Problem creating the RMI registry on port {0}: {1}

Cause: Problem creating the RMI registry on port {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05215: Export exception creating RMI registry on port {0}: {1}

Cause: Export exception creating RMI registry on port {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05216: Problem reading {0} managed beans XML file: {1}

Cause: Problem reading {0} managed beans XML file: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05217: Cannot load bean class {0}

Cause: Cannot load bean class {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05218: Notifier class {0} is not a public interface

Cause: Notifier class {0} is not a public interface

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05219: Cannot load notifier class {0}

Cause: Cannot load notifier class {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05220: <notification> element in {0} ignored because no notifier interface

Cause: <notification> element in {0} ignored because no notifier interface

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05221: Problem creating the JMXConnectorServer URL {0}: {1}

Cause: Problem creating the JMXConnectorServer URL {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05222: Problem creating JMXConnectorServer with URL {0}: {1}

Cause: Problem creating JMXConnectorServer with URL {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05223: Problem starting the JMXConnectorServer with URL {0}: {1}

Cause: Problem starting the JMXConnectorServer with URL {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05224: Bean class {0}: attribute {1} is not known

Cause: Bean class {0}: attribute {1} is not known

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05225: Bean class {0}: read-only attribute {1} does not have a getter

Cause: Bean class {0}: read-only attribute {1} does not have a getter

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05226: Bean class {0}: write-only attribute {1} does not have a setter

Cause: Bean class {0}: write-only attribute {1} does not have a setter

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05227: Bean class {0}: read-write attribute {1} does not have getter and setter

Cause: Bean class {0}: read-write attribute {1} does not have getter and setter

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05228: Bean class {0}: unknown operation {1}

Cause: Bean class {0}: unknown operation {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05230: Bean class {0}: unknown notification method {1}

Cause: Bean class {0}: unknown notification method {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05250: System management: name script file {0} not found

Cause: System management: name script file {0} not found

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05251: System management: error loading script from file {0}: {1}

Cause: System management: error loading script from file {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05252: System management: name maker class {0} not found

Cause: System management: name maker class {0} not found

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05253: System management: name maker class {0} does not implement {1}

Cause: System management: name maker class {0} does not implement {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05254: System management: name maker class {0} does not have zero arg constructor

Cause: System management: name maker class {0} does not have zero arg constructor

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05255: System management: error creating name maker class {0}: {0}

Cause: System management: error creating name maker class {0}: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05256: System management: failed to create namer script engine: {0}

Cause: System management: failed to create namer script engine: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05257: System management: failed to set namer script root object: {0}

Cause: System management: failed to set namer script root object: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05258: System management: failed to open namer script: {0}

Cause: System management: failed to open namer script: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05259: System management: failed to open namer script: missing class {0}

Cause: System management: failed to open namer script: missing class {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05260: System manaegment: ''{0}'' function missing in namer script

Cause: System manaegment: ''{0}'' function missing in namer script

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05261: System management: ''{0}'' namer script call failed: {1}

Cause: System management: ''{0}'' namer script call failed: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05270: Configuration method "{0}" in class "{1}" has more than one of @ConfigRead, @ConfigWrite or @ConfigDelete annotations

Cause: Configuration method "{0}" in class "{1}" has more than one of @ConfigRead, @ConfigWrite or @ConfigDelete annotations

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05271: Configuration read method "{0}" in class "{1}" has void result

Cause: Configuration read method "{0}" in class "{1}" has void result

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05272: Configuration write method "{0}" in class "{1}" has invalid parameters

Cause: Configuration write method "{0}" in class "{1}" has invalid parameters

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05273: Configuration class "{0}" has no valid methods

Cause: Configuration class "{0}" has no valid methods

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05274: Invalid path pattern "{0}" on method "{1}" in class "{2}: {3}

Cause: Invalid path pattern "{0}" on method "{1}" in class "{2}: {3}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05275: Config payload of type {0} cannot be converted to {1}/{2}

Cause: Config payload of type {0} cannot be converted to {1}/{2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05276: Validation error in config payload for path {0}: {1}: {2}

Cause: Validation error in config payload for path {0}: {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05277: Unsupported annotations on ConfigContext parameter in method "{0}" in class "{1}"

Cause: Unsupported annotations on ConfigContext parameter in method "{0}" in class "{1}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05278: Multiple parameter extractor annotations on parameter "{0}" of method "{1}" in class "{2}"

Cause: Multiple parameter extractor annotations on parameter "{0}" of method "{1}" in class "{2}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05279: Payload and parameter extractor annotations present on parameter "{0}" of method "{1}" in class "{2}"

Cause: Payload and parameter extractor annotations present on parameter "{0}" of method "{1}" in class "{2}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05280: No parameter extractor defined for class "{0}"

Cause: No parameter extractor defined for class "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05281: Multiple payload parameters on method "{0}" in class "{1}"

Cause: Multiple payload parameters on method "{0}" in class "{1}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05282: Payload parameter not allowed on read method "{0}" in class "{1}"

Cause: Payload parameter not allowed on read method "{0}" in class "{1}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05283: Unrecognized parameter "{0}" of method "{1}" in class "{2}"

Cause: Unrecognized parameter "{0}" of method "{1}" in class "{2}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05284: No payload parameter on method "{0}" in class "{1}"

Cause: No payload parameter on method "{0}" in class "{1}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05285: Error constructing parameter decoder of class "{0}": {1}

Cause: Error constructing parameter decoder of class "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05290: Error calling object namer class {0}: {1}

Cause: Error calling object namer class {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05300: Unable to parse BulkReview XML record: {0}

Cause: Unable to parse BulkReview XML record: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05301: Failed to load xml with error {0}

Cause: Failed to load xml with error {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05302: Failed to create Bulk Review schema: {0}

Cause: Failed to create Bulk Review schema: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05303: Failed to save bulk review details with error {0}

Cause: Failed to save bulk review details with error {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05304: Failed to delete bulk review details xml with error {0}

Cause: Failed to delete bulk review details xml with error {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05305: Failed to read column ordering xml with error {0}

Cause: Failed to read column ordering xml with error {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05306: Failed to create and configure schema {0}

Cause: Failed to create and configure schema {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05307: Unable to read custom decisions xml: {0}

Cause: Unable to read custom decisions xml: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05308: Unable to read decision statistics xml: {0}

Cause: Unable to read decision statistics xml: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05309: Unable to read review statistics xml: {0}

Cause: Unable to read review statistics xml: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05310: Unable to read match statistics xml: {0}

Cause: Unable to read match statistics xml: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05311: Match relationships output contains references to unknown flag: {0}

Cause: Match relationships output contains references to unknown flag: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05312: Unable to parse Match document xml: {0}

Cause: Unable to parse Match document xml: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05313: Failed to add transformation to comparison: {0}

Cause: Failed to add transformation to comparison: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05314: Failed to move transformation up in the list: {0}

Cause: Failed to move transformation up in the list: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05315: Failed to move transformation down in the list: {0}

Cause: Failed to move transformation down in the list: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05316: Failed to add decision detail to document: {0}

Cause: Failed to add decision detail to document: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05317: Unable to initialise helper: {0}

Cause: Unable to initialise helper: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05318: Unable to add attribute: {0}

Cause: Unable to add attribute: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05319: There was a problem reading from makeBundle

Cause: There was a problem reading from makeBundle

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05320: Match library has no search path configured

Cause: Match library has no search path configured

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05321: Match library has no configuration Jars to load

Cause: Match library has no configuration Jars to load

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05322: Error exporting decisions

Cause: Error exporting decisions

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05323: Search groups, error accessing results database

Cause: Search groups, error accessing results database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05324: Data access error selecting group IDs when clearing search: {0}

Cause: Data access error selecting group IDs when clearing search: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05325: Results database error selecting group IDs when clearing search: {0}

Cause: Results database error selecting group IDs when clearing search: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05326: Data access error selecting group IDs when caching groups: {0}

Cause: Data access error selecting group IDs when caching groups: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05327: Results database error selecting group IDs when caching groups: {0}

Cause: Results database error selecting group IDs when caching groups: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05328: Unable to retrieve match process: {0}

Cause: Unable to retrieve match process: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05329: Could not get a lock on this group. This is not an error if this group is already locked.

Cause: Could not get a lock on this group. This is not an error if this group is already locked.

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05330: Results database error retrieving records for group: {0}

Cause: Results database error retrieving records for group: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05331: I/O error retrieving records for group: {0}

Cause: I/O error retrieving records for group: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05332: Data access error retrieving records for group: {0}

Cause: Data access error retrieving records for group: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05333: Process failed when retrieving records for group: {0}

Cause: Process failed when retrieving records for group: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05334: Data access error when adding a comment: {0}

Cause: Data access error when adding a comment: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05335: Results Database error when adding a comment: {0}

Cause: Results Database error when adding a comment: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05336: Failed to delete comment, since it wasn't found in db

Cause: Failed to delete comment, since it wasn't found in db

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05337: Data access error when deleting a comment: {0}

Cause: Data access error when deleting a comment: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05338: Results Database error when deleting a comment: {0}

Cause: Results Database error when deleting a comment: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05339: Data access error in review decision: {0}

Cause: Data access error in review decision: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05340: Process failed in review decision: {0}

Cause: Process failed in review decision: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05341: Results Database error in review decision: {0}

Cause: Results Database error in review decision: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05342: Data access error in querying review group state: {0}

Cause: Data access error in querying review group state: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05343: Results Database error querying review group state: {0}

Cause: Results Database error querying review group state: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05344: Data access error retrieving comment history: {0}

Cause: Data access error retrieving comment history: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05345: Results Database error retrieving comment history: {0}

Cause: Results Database error retrieving comment history: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05346: Data access error retrieving decision history: {0}

Cause: Data access error retrieving decision history: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05347: Results Database error retrieving decision history: {0}

Cause: Results Database error retrieving decision history: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05348: Manual decisions deleted by {0} on {1}

Cause: Manual decisions deleted by {0} on {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05349: An error occurred updating statistics when deleting decisions: {0}

Cause: An error occurred updating statistics when deleting decisions: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05350: Error dropping table when deleting decisions: {0}

Cause: Error dropping table when deleting decisions: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05351: Error creating match review incident when deleting decisions: {0}

Cause: Error creating match review incident when deleting decisions: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05352: Realtime review tables deleted by {0} on {1}

Cause: Realtime review tables deleted by {0} on {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05353: Unable to drop table when deleting realtime review records: {0}

Cause: Unable to drop table when deleting realtime review records: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05354: Error creating match review incident when deleting real-time review records: {0}

Cause: Error creating match review incident when deleting real-time review records: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05355: Could not get a lock on this group. This is not an error if this group is already locked.

Cause: Could not get a lock on this group. This is not an error if this group is already locked.

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05356: Unknown comparison '{0}'

Cause: Unknown comparison '{0}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05357: Unknown attribute '{0}' on identifier '{0}'

Cause: Unknown attribute '{0}' on identifier '{0}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05358: Unknown identifier '{0}'

Cause: Unknown identifier '{0}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05359: Unknown selection '{0}'

Cause: Unknown selection '{0}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05360: Unknown transformation '{0}'

Cause: Unknown transformation '{0}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05361: {0} groups exceeded the limit of {1}

Cause: {0} groups exceeded the limit of {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05362: {0} groups of size {1}

Cause: {0} groups of size {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05363: Error while importing decisions: {0}

Cause: Error while importing decisions: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05364: Invalid incoming decision record: {0}

Cause: Invalid incoming decision record: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05365: Error migrating comments: {0}

Cause: Error migrating comments: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05366: Error migrating decisions: {0}

Cause: Error migrating decisions: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05367: Exception occurred reading output decisions: {0}

Cause: Exception occurred reading output decisions: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05368: A problem occurred reading relationship sets from the database: {0}

Cause: A problem occurred reading relationship sets from the database: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05369: A problem occurred reading relationships from the database: {0}

Cause: A problem occurred reading relationships from the database: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05370: A problem occurred reading cluster records from the database: {0}

Cause: A problem occurred reading cluster records from the database: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05371: A problem occurred processing clusters: {0}

Cause: A problem occurred processing clusters: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05372: Relationship found with records not in the same group. Ensure that working records share group option is selected if comparing against self.

Cause: Relationship found with records not in the same group. Ensure that working records share group option is selected if comparing against self.

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05373: Unable to read case '{0}'

Cause: Unable to read case '{0}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05374: Unable to read case issues:

Cause: Unable to read case issues:

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05375: A Problem occurred reading clusters as output groups: {0}

Cause: A Problem occurred reading clusters as output groups: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05376: A Problem occurred reading records grouped by issue: {0}

Cause: A Problem occurred reading records grouped by issue: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05377: A Problem occurred reading output groups: {0}

Cause: A Problem occurred reading output groups: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05378: Migrating decisions

Cause: Migrating decisions

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05379: Relationship found with records not in the same group. Ensure that working records share group option is selected if comparing against self.

Cause: Relationship found with records not in the same group. Ensure that working records share group option is selected if comparing against self.

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05380: Unable to read case '{0}'

Cause: Unable to read case '{0}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05381: Unable to read case issues:

Cause: Unable to read case issues:

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05382: A problem occurred processing issue group: {0}

Cause: A problem occurred processing issue group: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05383: A problem occurred processing review group: {0}

Cause: A problem occurred processing review group: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05384: Unexpected decision record received (batch mode)

Cause: Unexpected decision record received (batch mode)

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05385: A data related error occurred in clear up: {0}

Cause: A data related error occurred in clear up: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05386: Process aborted on clear up: {0}

Cause: Process aborted on clear up: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05387: An XML parse error occurred importing decisions: {0}

Cause: An XML parse error occurred importing decisions: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05388: A data error occurred importing decisions: {0}

Cause: A data error occurred importing decisions: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05389: A transfer error occurred importing decisions: {0}

Cause: A transfer error occurred importing decisions: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05390: An I/O error occurred importing decisions: {0}

Cause: An I/O error occurred importing decisions: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05391: Unexpected decision record received

Cause: Unexpected decision record received

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05392: A data related error occurred in clear up: {0}

Cause: A data related error occurred in clear up: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05393: Process aborted on clear up: {0}

Cause: Process aborted on clear up: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05394: Unexpected decision record received (real-time mode)

Cause: Unexpected decision record received (real-time mode)

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05395: Real-time buckets, there was a problem closing a writer: {0}

Cause: Real-time buckets, there was a problem closing a writer: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05396: Unable to create table {0} as it already exists

Cause: Unable to create table {0} as it already exists

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05397: Unable to close decision audit migration data writer: {0}

Cause: Unable to close decision audit migration data writer: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05398: Unable to close bulk review data writer: {0}

Cause: Unable to close bulk review data writer: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05399: Unable to close bulk review persistent record writer: {0}

Cause: Unable to close bulk review persistent record writer: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05400: failed to decode iostreamingconfiguration string: {0}

Cause: failed to decode iostreamingconfiguration string: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05401: failed to encode ExportWriterMaps: {0}

Cause: failed to encode ExportWriterMaps: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05402: Skipping job with xml {0}

Cause: Skipping job with xml {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05403: Invalid xml, did not conform to xsd schema for jobs to be migrated: {0}: {1}

Cause: Invalid xml, did not conform to xsd schema for jobs to be migrated: {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05404: Property values different

Cause: Property values different

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05405: Mapped values different

Cause: Mapped values different

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05406: Parameter '{0}' in Source '{1}' for Case Type '{2}' using Selection Function '{3}' is using an attribute under input '{4}' that is not mapped to case management. This input will not be added automatically mapped and must be manually configured.

Cause: Parameter '{0}' in Source '{1}' for Case Type '{2}' using Selection Function '{3}' is using an attribute under input '{4}' that is not mapped to case management. This input will not be added automatically mapped and must be manually configured.

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05600: Application helper: bad file pattern {0}: {1}

Cause: Application helper: bad file pattern {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05601: ServerConnector: error looking up management bean "{0}": {1}

Cause: ServerConnector: error looking up management bean "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05602: ServerConnector: error invoking name mapper on management bean: {0}

Cause: ServerConnector: error invoking name mapper on management bean: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05603: Operation queue: [{0}]: operation {1} failed: {2}

Cause: Operation queue: [{0}]: operation {1} failed: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05604: SQL operation {0} failed: {1}

Cause: SQL operation {0} failed: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05605: Property set: error calling {0} on a {1}: {2}

Cause: Property set: error calling {0} on a {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05606: Bad boolean property "{0}" for {1}

Cause: Bad boolean property "{0}" for {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05607: Bad boolean value "{0}"

Cause: Bad boolean value "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05608: Bad integer property "{0}" for {1}

Cause: Bad integer property "{0}" for {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05609: Bad numeric property "{0}" for {1}

Cause: Bad numeric property "{0}" for {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05610: Bad date property "{0}" for {1}

Cause: Bad date property "{0}" for {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05611: Key provider error: {0}

Cause: Key provider error: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05612: Cannot allocate cipher using algorithm {0}

Cause: Cannot allocate cipher using algorithm {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05613: Key loading error: {0}

Cause: Key loading error: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05614: Error generating security key using algorithm {0}: {1}

Cause: Error generating security key using algorithm {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05615: Key store error: {0}

Cause: Key store error: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05616: {0} encryption failed: {1}

Cause: {0} encryption failed: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05617: {0} decryption failed: {1}

Cause: {0} decryption failed: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05618: SSLTrustManagement: error opening certificate URL {0}: {1}

Cause: SSLTrustManagement: error opening certificate URL {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05619: SSLTrustManagement: error loading certificate in {0}: {1}

Cause: SSLTrustManagement: error loading certificate in {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05620: Native library manager: error opening {0} as jar: {1}

Cause: Native library manager: error opening {0} as jar: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05621: Native library manager: error getting CRC of {0}: {1}

Cause: Native library manager: error getting CRC of {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05622: Native library manager: error copying jar entry {0} to {1}: {2}

Cause: Native library manager: error copying jar entry {0} to {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05623: Property evaluation: Error in expression "{0}": {1}

Cause: Property evaluation: Error in expression "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05624: Transactions: commit failed on non-critical activity {0}: {1}

Cause: Transactions: commit failed on non-critical activity {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05625: Transactions: rollback failed on non-critical activity {0}: {1}

Cause: Transactions: rollback failed on non-critical activity {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05626: XML: cannot find schema file "{0}"

Cause: XML: cannot find schema file "{0}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05627: XML: error on line {0} when parsing schema: {1}

Cause: XML: error on line {0} when parsing schema: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05628: XML: error parsing schema: {0}

Cause: XML: error parsing schema: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05629: XML: IO error during XML parsing: {0}

Cause: XML: IO error during XML parsing: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05630: XML: failed to parse XML: {0}

Cause: XML: failed to parse XML: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05631: XML: error during document validation: {0}

Cause: XML: error during document validation: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05632: XML: error during parsing: {0}

Cause: XML: error during parsing: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05633: XML: error at {0} during parsing: {1}

Cause: XML: error at {0} during parsing: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05634: XML: fatal error during parsing: {0}

Cause: XML: fatal error during parsing: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05635: XML: fatal error at {0} during parsing: {1}

Cause: XML: fatal error at {0} during parsing: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05636: XML: warning during parsing: {0}

Cause: XML: warning during parsing: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05637: XML: warning at {0} during parsing: {1}

Cause: XML: warning at {0} during parsing: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05638: Stax: unthrowable exception in StAXTrAXFilterFactory.Reader.haxNext

Cause: Stax: unthrowable exception in StAXTrAXFilterFactory.Reader.haxNext

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05660: Credentials provider error: {0}

Cause: Credentials provider error: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05661: Error loading credentials for prefix "{0}": {1}

Cause: Error loading credentials for prefix "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05670: Keystore provider error: {0}

Cause: Keystore provider error: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05680: WLS support: error lookup in runtime MBean server: {0}

Cause: WLS support: error lookup in runtime MBean server: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05681: WLS support: object "{0}" at {1} is not an MBeanServer

Cause: WLS support: object "{0}" at {1} is not an MBeanServer

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05682: WLS support: error querying MBeans at {0}: {1}

Cause: WLS support: error querying MBeans at {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05683: WLS support: got {0} MBeans for {1}

Cause: WLS support: got {0} MBeans for {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05684: WLS support: error querying initial value of "{0}" on "{1}": {2}

Cause: WLS support: error querying initial value of "{0}" on "{1}": {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05685: WLS support: error adding listener to "{0}": {1}

Cause: WLS support: error adding listener to "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05686: WLS support: error calling startup listener: {0}

Cause: WLS support: error calling startup listener: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05700: An error occurred cancelling task: {0}

Cause: An error occurred cancelling task: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05701: An error occurred running task: {0}

Cause: An error occurred running task: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05702: An error occurred releasing locks: {0}

Cause: An error occurred releasing locks: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05703: An error occurred storing event log for task: {0}

Cause: An error occurred storing event log for task: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05704: Error during mission diff

Cause: Error during mission diff

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05705: thread limit is: unconstrained

Cause: thread limit is: unconstrained

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05706: thread limit is: {0}

Cause: thread limit is: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05707: streaming is allowed

Cause: streaming is allowed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05708: streaming is not allowed

Cause: streaming is not allowed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05709: Mission Manager expiry date is {0}

Cause: Mission Manager expiry date is {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05710: An error occurred cancelling task immediately: {0}

Cause: An error occurred cancelling task immediately: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05711: No trigger found for {0}

Cause: No trigger found for {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05712: Error constructing event message: {0}

Cause: Error constructing event message: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05713: Error archiving progress information: {0}

Cause: Error archiving progress information: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05714: Error parsing XML document: {0}

Cause: Error parsing XML document: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05715: Error creating new transformer for outputting match process: {0}

Cause: Error creating new transformer for outputting match process: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05716: Error transforming match process to XML: {0}

Cause: Error transforming match process to XML: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05717: Error creating XML parser for outputting match process: {0}

Cause: Error creating XML parser for outputting match process: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05718: A problem occurred retrieving application purge rules: {0}

Cause: A problem occurred retrieving application purge rules: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05719: An error occurred running the purging thread: {0}

Cause: An error occurred running the purging thread: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05720: A problem occurred deleting results for job {0} with runlabel "{1}": {2}

Cause: A problem occurred deleting results for job {0} with runlabel "{1}": {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05721: A error occurred running trigger: {0}

Cause: A error occurred running trigger: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05722: Task factory for task type {0} is being replaced

Cause: Task factory for task type {0} is being replaced

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05723: A problem occurred deleting results for job {0} with runlabel "{1}": {2}

Cause: A problem occurred deleting results for job {0} with runlabel "{1}": {2}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05724: Job {0} with runlabel "{1}" was successfully deleted

Cause: Job {0} with runlabel "{1}" was successfully deleted

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05725: Purge Rules are invalid and can not be saved

Cause: Purge Rules are invalid and can not be saved

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05726: Purge Rules schema could not be loaded

Cause: Purge Rules schema could not be loaded

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05800: {0} is not a valid subfolder of landing area {1}

Cause: {0} is not a valid subfolder of landing area {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05801: URL is malformed: {0}

Cause: URL is malformed: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05802: Download task {0} starting to download from {1} to {2}

Cause: Download task {0} starting to download from {1} to {2}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05803: Download task {0} failed to fetch data from {1}

Cause: Download task {0} failed to fetch data from {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05804: Download task {0} finished in {1} seconds

Cause: Download task {0} finished in {1} seconds

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05805: An I/O error occurred during download: {0}

Cause: An I/O error occurred during download: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05806: A security violation occurred during download: {0}

Cause: A security violation occurred during download: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05807: An I/O occurred reading log output from external task: {0}

Cause: An I/O occurred reading log output from external task: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05808: Error running external task: {0}

Cause: Error running external task: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05809: Setting working directory to {0}

Cause: Setting working directory to {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05810: Executing {0} {1}

Cause: Executing {0} {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05811: finished execution in {0}

Cause: finished execution in {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05812: External task failed with exit status {0}

Cause: External task failed with exit status {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05813: An I/O error occurred running external task {0}

Cause: An I/O error occurred running external task {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05814: Error canonicalizing command area file '{0}': {1}

Cause: Error canonicalizing command area file '{0}': {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05815: Error canonicalizing config command area '{0}': {1}

Cause: Error canonicalizing config command area '{0}': {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05816: {0} XStore items found in import file: {1}, {2}, {3}

Cause: {0} XStore items found in import file: {1}, {2}, {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05817: Error during external task diff

Cause: Error during external task diff

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05818: An error occurred retrieving XTreeNode for dependency object: {0}

Cause: An error occurred retrieving XTreeNode for dependency object: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05819: An error occurred retrieving XTreeNode for dependency subject: {0}

Cause: An error occurred retrieving XTreeNode for dependency subject: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05820: An database error occurred deleting all external tasks for project: {0}

Cause: An database error occurred deleting all external tasks for project: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05821: An error occurred deleting all external tasks for project: {0}

Cause: An error occurred deleting all external tasks for project: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05822: An error occurred cancelling task: {0}

Cause: An error occurred cancelling task: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05823: An error occurred run task: {0}

Cause: An error occurred run task: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05824: Handle returned that we didn't know about

Cause: Handle returned that we didn't know about

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05825: An error occurred saving run process model: {0}

Cause: An error occurred saving run process model: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05826: An error occurred retrieving mission for run identifier: {0}

Cause: An error occurred retrieving mission for run identifier: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05827: An error occurred renaming missions for document: {0}

Cause: An error occurred renaming missions for document: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05828: A database error occurred renaming missions for document: {0}

Cause: A database error occurred renaming missions for document: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05829: An error occurred running a mission: {0}

Cause: An error occurred running a mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05830: An error occurred cleaning up mission: {0}

Cause: An error occurred cleaning up mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05831: Error purging project {0}

Cause: Error purging project {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05832: Error {0} creating job for process {1}

Cause: Error {0} creating job for process {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05833: Error {0} deleting jobs for document {1}

Cause: Error {0} deleting jobs for document {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05834: Error {0} deleting jobs for project {1}

Cause: Error {0} deleting jobs for project {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05835: Error storing log for {0} (taskExecId {1}): {2}

Cause: Error storing log for {0} (taskExecId {1}): {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05836: Error loading log for exec id {0}: {1}

Cause: Error loading log for exec id {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05837: Error deleting stats for {0}:{1}: {2}

Cause: Error deleting stats for {0}:{1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05838: Error storing stats for {0}:{1}: {2}

Cause: Error storing stats for {0}:{1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05839: Error loading stats for {0}:{1}: {2}

Cause: Error loading stats for {0}:{1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05840: An error occurred asynchronously running an ops mission: {0}

Cause: An error occurred asynchronously running an ops mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05841: An error occurred running an ops mission: {0}

Cause: An error occurred running an ops mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05842: An error occurred loading override properties: {0}

Cause: An error occurred loading override properties: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05843: A database error occurred inserting task status information: {0}

Cause: A database error occurred inserting task status information: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05844: An error occurred inserting task status information: {0}

Cause: An error occurred inserting task status information: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05845: A database error occurred retrieving task status information: {0}

Cause: A database error occurred retrieving task status information: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05846: A database error occurred retrieving run mission labels: {0}

Cause: A database error occurred retrieving run mission labels: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05847: A database error occurred finding task status information: {0}

Cause: A database error occurred finding task status information: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05848: A database error occurred loading mission by ID: {0}

Cause: A database error occurred loading mission by ID: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05849: A database error occurred loading mission: {0}

Cause: A database error occurred loading mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05850: A database error occurred loading missions for project: {0}

Cause: A database error occurred loading missions for project: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05851: A database error occurred loading nodes for project: {0}

Cause: A database error occurred loading nodes for project: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05852: A database error occurred updating tables while saving mission: {0}

Cause: A database error occurred updating tables while saving mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05853: An error occurred updating tables when saving mission: {0}

Cause: An error occurred updating tables when saving mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05854: A permissions error occurred updating tables when saving mission: {0}

Cause: A permissions error occurred updating tables when saving mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05855: A database error occurred inserting new entries when saving mission: {0}

Cause: A database error occurred inserting new entries when saving mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05856: An error occurred inserting new entries when saving mission: {0}

Cause: An error occurred inserting new entries when saving mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05857: A database error occurred saving mission: {0}

Cause: A database error occurred saving mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05858: An error occurred saving mission: {0}

Cause: An error occurred saving mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05859: A permissions error occurred saving mission: {0}

Cause: A permissions error occurred saving mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05860: A database error occurred deleting a mission: {0}

Cause: A database error occurred deleting a mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05861: An error occurred deleting dependencies when deleting a mission: {0}

Cause: An error occurred deleting dependencies when deleting a mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05862: A permissions error occurred deleting mission: {0}

Cause: A permissions error occurred deleting mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05863: An error occurred deleting external properties when deleting a mission: {0}

Cause: An error occurred deleting external properties when deleting a mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05864: A database error occurred deleting missions for a document: {0}

Cause: A database error occurred deleting missions for a document: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05865: An error occurred deleting dependencies when deleting missions for a document: {0}

Cause: An error occurred deleting dependencies when deleting missions for a document: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05866: A permissions error occurred deleting missions for a document: {0}

Cause: A permissions error occurred deleting missions for a document: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05867: An error occurred deleting external properties when deleting missions for a document: {0}

Cause: An error occurred deleting external properties when deleting missions for a document: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05868: A database error occurred deleting missions for a project: {0}

Cause: A database error occurred deleting missions for a project: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05869: An error occurred deleting dependencies when deleting missions for a project: {0}

Cause: An error occurred deleting dependencies when deleting missions for a project: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05870: A permissions error occurred deleting missions for a document: {0}

Cause: A permissions error occurred deleting missions for a document: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05871: An error occurred deleting external properties when deleting missions for a project: {0}

Cause: An error occurred deleting external properties when deleting missions for a project: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05872: A database error occurred renaming a mission: {0}

Cause: A database error occurred renaming a mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05873: A permissions error occurred renaming a mission: {0}

Cause: A permissions error occurred renaming a mission: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05874: A database error occurred loading XTree node for dependency object: {0}

Cause: A database error occurred loading XTree node for dependency object: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05875: A database error occurred loading XTree node for dependency subject: {0}

Cause: A database error occurred loading XTree node for dependency subject: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05876: Error during purge: {0}

Cause: Error during purge: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05877: Task factory for task type : {0} is being replaced

Cause: Task factory for task type : {0} is being replaced

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05878: No queueable task factory for: {0}

Cause: No queueable task factory for: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05879: No queueable task executor defined for: {0}

Cause: No queueable task executor defined for: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05880: An error occurred running task: {0}

Cause: An error occurred running task: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05881: Error occurred with system task {0} : {1}

Cause: Error occurred with system task {0} : {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05882: Failed to load schedules!

Cause: Failed to load schedules!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05883: Error executing scheduled job : {0}

Cause: Error executing scheduled job : {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05884: Permissions error executing scheduled job : {0}

Cause: Permissions error executing scheduled job : {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05885: An error occurred updating schedule: {0}

Cause: An error occurred updating schedule: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05886: Error executing schedule : {0}

Cause: Error executing schedule : {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05887: Failed to delete schedule

Cause: Failed to delete schedule

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05888: Mission scheduler executing startup schedules

Cause: Mission scheduler executing startup schedules

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-05889: Runtime exception in scheduler thread

Cause: Runtime exception in scheduler thread

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05890: Error importing data for node: {0}

Cause: Error importing data for node: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05891: Failed to decode MissionStatement XML string: {0}

Cause: Failed to decode MissionStatement XML string: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05892: Failed to encode MissionBean: {0}

Cause: Failed to encode MissionBean: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05893: Cannot find option transcoder for option "{0}"

Cause: Cannot find option transcoder for option "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05894: Error executing method "{0}" within cluster

Cause: Error executing method "{0}" within cluster

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05895: Cluster currently unavailable for method "{0}"

Cause: Cluster currently unavailable for method "{0}"

Action: Try again.
Level: 1

Type: WARNING

Impact: Other

EDQ-05896: Bad search parameter format "{0}"

Cause: Bad search parameter format "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05897: Bad search parameter date "{0}"

Cause: Bad search parameter date "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05898: Bad search parameter date "{0}"

Cause: Bad search parameter date "{0}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05900: Call made to transport before login/after logout: {0}

Cause: Call made to transport before login/after logout: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05901: Unknown throwable class returned: {0}

Cause: Unknown throwable class returned: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-05902: Problem instantiating output when calling {0}

Cause: Problem instantiating output when calling {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05903: Transport exception

Cause: Transport exception

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05904: Serializing 'Output' object

Cause: Serializing 'Output' object

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05905: Transport: Error invoking method on server

Cause: Transport: Error invoking method on server

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-05906: Server transport error:

Cause: Server transport error:

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06100: Column indexing interrupted: {0}

Cause: Column indexing interrupted: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06101: An error occurred indexing columns: {0}

Cause: An error occurred indexing columns: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06102: An error occurred retrieving staged data definition: {0}

Cause: An error occurred retrieving staged data definition: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06103: An error occurred retrieving the staged data data profile: {0}

Cause: An error occurred retrieving the staged data data profile: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06200: No content in XML

Cause: No content in XML

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06201: Unsupported type: {0}

Cause: Unsupported type: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06202: An error occurred loading resource: {0}

Cause: An error occurred loading resource: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06203: An error occurred loading resource by key: {0}

Cause: An error occurred loading resource by key: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06204: Text value changed so calling setRegularExpression with {0}

Cause: Text value changed so calling setRegularExpression with {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06205: {0} Exception creating writer for metric {1}

Cause: {0} Exception creating writer for metric {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06206: {0} Could not find metric: {1}

Cause: {0} Could not find metric: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06207: {0} Exception writing metric {1}

Cause: {0} Exception writing metric {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06208: {0} Exception writing classification view by attribute

Cause: {0} Exception writing classification view by attribute

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06209: {0} Exception writing classification view metric

Cause: {0} Exception writing classification view metric

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06210: {0} Exception writing reclassification dependent rules view

Cause: {0} Exception writing reclassification dependent rules view

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06211: {0} Exception writing reclassification rules patterns view

Cause: {0} Exception writing reclassification rules patterns view

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06212: {0} Exception writing pre-selection patterns metric

Cause: {0} Exception writing pre-selection patterns metric

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06213: {0} Exception writing resolution rule view

Cause: {0} Exception writing resolution rule view

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06214: {0} Exception writing results view

Cause: {0} Exception writing results view

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06215: {0} Exception writing selection view metric

Cause: {0} Exception writing selection view metric

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06216: {0} Exception writing token frequency by decision

Cause: {0} Exception writing token frequency by decision

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06217: {0} Exception writing tokenisation view metric

Cause: {0} Exception writing tokenisation view metric

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06218: {0} Exception writing unclassified token by attribute detail view

Cause: {0} Exception writing unclassified token by attribute detail view

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06219: {0} Exception writing unclassified tokens by attribute view

Cause: {0} Exception writing unclassified tokens by attribute view

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06220: Unknown type of source for source id = {0}. Type of source specified = {1}

Cause: Unknown type of source for source id = {0}. Type of source specified = {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06221: Could not parse source id = {0}

Cause: Could not parse source id = {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06222: {0} Parser configuration does not accept attribute {1}

Cause: {0} Parser configuration does not accept attribute {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06223: {0} An error occurred parsing XML document: {1}

Cause: {0} An error occurred parsing XML document: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06224: {0} Invalid parser configuration

Cause: {0} Invalid parser configuration

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06225: {0} Checker ({1}) has not been implemented

Cause: {0} Checker ({1}) has not been implemented

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06226: {0} Found reclassification circular dependency at: {1}

Cause: {0} Found reclassification circular dependency at: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06227: {0} Security exception when trying to load class: {1}

Cause: {0} Security exception when trying to load class: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06228: {0} Illegal argument exception when creating metric handler instance for: {1}

Cause: {0} Illegal argument exception when creating metric handler instance for: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06229: {0} Instantiation exception when creating metric handler instance for: {1}

Cause: {0} Instantiation exception when creating metric handler instance for: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06230: {0} Illegal access exception when creating metric handler instance for: {1}

Cause: {0} Illegal access exception when creating metric handler instance for: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06231: {0} Invocation target exception when creating metric handler instance for: {1}

Cause: {0} Invocation target exception when creating metric handler instance for: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06232: Error decoding parser configuration: {0}

Cause: Error decoding parser configuration: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06300: EDQP server at {0}:{1} appears to be alive

Cause: EDQP server at {0}:{1} appears to be alive

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-06301: EDQP server at {0}:{1} does not appear to be alive

Cause: EDQP server at {0}:{1} does not appear to be alive

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06302: Bad EDQP batchsize property "{0}"

Cause: Bad EDQP batchsize property "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06303: Error getting DSA information from datalens server at {0}:{1}: {2}

Cause: Error getting DSA information from datalens server at {0}:{1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06304: DSA {0} not found on server when getting output step names

Cause: DSA {0} not found on server when getting output step names

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06305: DSA {0} not found on server when getting output value names

Cause: DSA {0} not found on server when getting output value names

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06306: Output step {0} not found in DSA {1} when getting output value names

Cause: Output step {0} not found in DSA {1} when getting output value names

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06307: Failed to get deployed DSA names from server

Cause: Failed to get deployed DSA names from server

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06308: Failed to get output names for a DSA from server

Cause: Failed to get output names for a DSA from server

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06309: Error getting attribute names for the output process of a DSA from server: {0}

Cause: Error getting attribute names for the output process of a DSA from server: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06500: Error in schema while loading permissions

Cause: Error in schema while loading permissions

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06501: LoadPerms: {0} missing in file "{1}"

Cause: LoadPerms: {0} missing in file "{1}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06502: LoadPerms: error parsing {0} in file "{1}"

Cause: LoadPerms: error parsing {0} in file "{1}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06503: LoadPerms: error reading file "{0}"

Cause: LoadPerms: error reading file "{0}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06504: Failed to load schema file {0}: {1}

Cause: Failed to load schema file {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06505: Error looking up /WEB-INF/{0}: {1}

Cause: Error looking up /WEB-INF/{0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06506: Error looking up /META-INF/{0}: {1}

Cause: Error looking up /META-INF/{0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06507: Error parsing actions configuration file at {0}: {1}

Cause: Error parsing actions configuration file at {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06508: Error reading from actions configuration file at {0}: {1}

Cause: Error reading from actions configuration file at {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06509: Error committing group for project id: {0}

Cause: Error committing group for project id: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06600: Runtime exception in phrase profiler: {0}

Cause: Runtime exception in phrase profiler: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06601: Aborted process in phrase profiler: {0}

Cause: Aborted process in phrase profiler: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06700: Failed to convert gui data for process model: {0}

Cause: Failed to convert gui data for process model: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06701: Process model not found in list of config docs!

Cause: Process model not found in list of config docs!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06702: Reference Processor update aborted. Non-composite '{0}' has incorrect dependency '{1}'

Cause: Reference Processor update aborted. Non-composite '{0}' has incorrect dependency '{1}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06703: Reference Processor update aborted. Reference Processor '{0}' has wrong processor count: {1}

Cause: Reference Processor update aborted. Reference Processor '{0}' has wrong processor count: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06704: Reference Processor update aborted. Reference Processor '{0}' is wrong type: {1}

Cause: Reference Processor update aborted. Reference Processor '{0}' is wrong type: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06705: Error loading process: id = '{0}'

Cause: Error loading process: id = '{0}'

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06706: Process does not exist

Cause: Process does not exist

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06707: Process cannot be saved

Cause: Process cannot be saved

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06708: Error ending transaction

Cause: Error ending transaction

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06709: Last run process cannot be saved

Cause: Last run process cannot be saved

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06710: Cannot load data interfaces for process model {0}

Cause: Cannot load data interfaces for process model {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06711: Failed to start transaction

Cause: Failed to start transaction

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06712: Process model '{0}': cannot delete

Cause: Process model '{0}': cannot delete

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06713: Process model '{1}': cannot purge

Cause: Process model '{1}': cannot purge

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06714: Error exporting process to file '{0}'

Cause: Error exporting process to file '{0}'

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06715: IO error {0}

Cause: IO error {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06716: Error exporting process

Cause: Error exporting process

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06717: Invalid processor type {0}

Cause: Invalid processor type {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06718: Failed to convert xml property

Cause: Failed to convert xml property

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06719: The following XML failed validation against schema '{0}':{1}

Cause: The following XML failed validation against schema '{0}':{1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06720: Process import file '{0}' not found

Cause: Process import file '{0}' not found

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06721: Process import failed during parse

Cause: Process import failed during parse

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06722: Process import no content found in input

Cause: Process import no content found in input

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06723: Process import invalid version: {0}

Cause: Process import invalid version: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06724: Failed validation against schema: {0}

Cause: Failed validation against schema: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06725: Error loading document for promulgation: {0}

Cause: Error loading document for promulgation: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06726: Failed to clean DI records for model {0}: {1}

Cause: Failed to clean DI records for model {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06727: Widget type not allowed: {0}

Cause: Widget type not allowed: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06728: Attribute in composite graph outputs but not in composite: {0}

Cause: Attribute in composite graph outputs but not in composite: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06729: Error copying composite processor graph

Cause: Error copying composite processor graph

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06730: Cannot remove processor - does not exist in this graph: {0}

Cause: Cannot remove processor - does not exist in this graph: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06731: WidgetInfo not found: {0}

Cause: WidgetInfo not found: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06732: Processor not visible at process model level: {0}

Cause: Processor not visible at process model level: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06733: Attempting to add an invalid pipe

Cause: Attempting to add an invalid pipe

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06734: Cannot remove pipe because from processor not visible at process model level: {0}

Cause: Cannot remove pipe because from processor not visible at process model level: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06735: Error creating widget facade

Cause: Error creating widget facade

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06736: Cannot find xsl resource: {0}

Cause: Cannot find xsl resource: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06737: Cannot configure transformer with stylesheet: {0}

Cause: Cannot configure transformer with stylesheet: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06738: Cannot perform transform with stylesheet: {0}

Cause: Cannot perform transform with stylesheet: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06739: Failed to encode process data interfaces

Cause: Failed to encode process data interfaces

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06740: Failed to decode process data interfaces

Cause: Failed to decode process data interfaces

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06741: Schema '{0}' load failed!

Cause: Schema '{0}' load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06742: Failed to decode process display info

Cause: Failed to decode process display info

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06743: Failed to encode process display info

Cause: Failed to encode process display info

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06800: Error importing bucket

Cause: Error importing bucket

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06801: Error during source view diff

Cause: Error during source view diff

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06802: Provider {0} auto-realize failed: {1}

Cause: Provider {0} auto-realize failed: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06803: Consumer {0} auto-realize failed: {1}

Cause: Consumer {0} auto-realize failed: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06804: Error loading Xitem {0}/{1}: {2}

Cause: Error loading Xitem {0}/{1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06805: Error loading old realizations: {0}

Cause: Error loading old realizations: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06806: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06807: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06808: Virtual bucket not realized for reading

Cause: Virtual bucket not realized for reading

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06809: Virtual bucket not realized for writing

Cause: Virtual bucket not realized for writing

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06810: No mapping for real attribute {0} in writer

Cause: No mapping for real attribute {0} in writer

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06811: No mapping for virtual attribute {0} in writer

Cause: No mapping for virtual attribute {0} in writer

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06812: Unknown virtual attribute {0} in realization

Cause: Unknown virtual attribute {0} in realization

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06813: Unknown real attribute {0} in realization

Cause: Unknown real attribute {0} in realization

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06814: Types of virtual attribute {0} and real attribute {1} do not match

Cause: Types of virtual attribute {0} and real attribute {1} do not match

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06815: Failed to open virtual bucket configuration file {0}

Cause: Failed to open virtual bucket configuration file {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06816: Failed to decode realizations string: {0}

Cause: Failed to decode realizations string: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06817: Bucket deposition failed

Cause: Bucket deposition failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06818: Bucket update failed

Cause: Bucket update failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06819: Problem whilst deleting {0} buckets for {1}: {2}

Cause: Problem whilst deleting {0} buckets for {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06820: Bucket transaction refused

Cause: Bucket transaction refused

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06821: Problem querying XTree for type {0}: {1}

Cause: Problem querying XTree for type {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06822: Error retrieving %s XTree data {0}: {1}

Cause: Error retrieving %s XTree data {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06823: Failed to write XML to '{0}'

Cause: Failed to write XML to '{0}'

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06824: Failed to load labels from '{0}': {1}

Cause: Failed to load labels from '{0}': {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06825: Failed to save labels from '{0}': {1}

Cause: Failed to save labels from '{0}': {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06826: CodePointClassifier: bad character code definition '{0}'

Cause: CodePointClassifier: bad character code definition '{0}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06827: CharacterClassifier: bad character code definition '{0}'

Cause: CharacterClassifier: bad character code definition '{0}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06828: Failed to deposit {0} store '{1}'

Cause: Failed to deposit {0} store '{1}'

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06829: Failed to update {0} store '{1}'

Cause: Failed to update {0} store '{1}'

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06830: Error deleting dependencies for {0} {1}: {2}

Cause: Error deleting dependencies for {0} {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06831: Failed to remove {0} store '{1}'

Cause: Failed to remove {0} store '{1}'

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06832: Error deleting {0} dependencies for project {1}: {2}

Cause: Error deleting {0} dependencies for project {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06833: Error writing %s dependencies for {0}: {1}

Cause: Error writing %s dependencies for {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06834: Failed to open filters configuration document {0}

Cause: Failed to open filters configuration document {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06835: Bad decimal format '{0}'

Cause: Bad decimal format '{0}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06836: Bad date format '{0}'

Cause: Bad date format '{0}'

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06837: Bad default value '{0}' for {1}

Cause: Bad default value '{0}' for {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06838: Failed to open filing cabinet configuration file {0}

Cause: Failed to open filing cabinet configuration file {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06839: Array types not supported for file input

Cause: Array types not supported for file input

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06840: Recordid element may not be used more than once

Cause: Recordid element may not be used more than once

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06841: Could not open '{0}'

Cause: Could not open '{0}'

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06842: Error reading file

Cause: Error reading file

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06843: Failed to read randomator configuration {0}

Cause: Failed to read randomator configuration {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06844: {0}: undefined shared range {1}

Cause: {0}: undefined shared range {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06845: {0} : types do not match in copy with source {1}

Cause: {0} : types do not match in copy with source {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06846: {0} : <{1}> cannot return {2} values

Cause: {0} : <{1}> cannot return {2} values

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06847: {0} : fixed should not include both value attribute and content

Cause: {0} : fixed should not include both value attribute and content

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06848: {0} : bad fixed numeric value '{0}'

Cause: {0} : bad fixed numeric value '{0}'

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06849: {0} : invalid nested copy reference to {1}

Cause: {0} : invalid nested copy reference to {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06850: {0} : bad decimal format '{1}'

Cause: {0} : bad decimal format '{1}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06851: Dictionary and resource cannot both be used in randomwords

Cause: Dictionary and resource cannot both be used in randomwords

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06852: {0} : differing word sets in same group '{1}'

Cause: {0} : differing word sets in same group '{1}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06853: Bad date {0}

Cause: Bad date {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06854: Bad time {0}

Cause: Bad time {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06855: {0} : bad date format '{1}'

Cause: {0} : bad date format '{1}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06856: Could not find dictionary resource {0}

Cause: Could not find dictionary resource {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06857: Error reading from dictionary file

Cause: Error reading from dictionary file

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06858: Could not open resource {0} : {1}

Cause: Could not open resource {0} : {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06859: Could not query resource {0} : {1}

Cause: Could not query resource {0} : {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06860: {0}: range {1} defined more than once

Cause: {0}: range {1} defined more than once

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06861: {0}: multi-level range %s is not supported

Cause: {0}: multi-level range %s is not supported

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06862: DataPump: Unable to make thread wait: {0}

Cause: DataPump: Unable to make thread wait: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06863: starting execution of data batch {0}

Cause: starting execution of data batch {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-06864: data batch {0} terminated by exception

Cause: data batch {0} terminated by exception

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06865: failed to encode Realizations: {0}

Cause: failed to encode Realizations: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06866: data batch {0} complete

Cause: data batch {0} complete

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-06900: problem dropping temp counter table {0}

Cause: problem dropping temp counter table {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06901: problem dropping temp stuffer table {0}

Cause: problem dropping temp stuffer table {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06902: problem dropping temp record dump table {0}

Cause: problem dropping temp record dump table {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06903: {0} : {1} Process started

Cause: {0} : {1} Process started

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06904: {0} : {1} Process end after {2}

Cause: {0} : {1} Process end after {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06905: {0} : Error loading last process model for job {0} process {1}: {2}

Cause: {0} : Error loading last process model for job {0} process {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06906: {0} : could not retrieve ProcessorRuntime: {0}

Cause: {0} : could not retrieve ProcessorRuntime: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06907: {0} : failed to write process statistics

Cause: {0} : failed to write process statistics

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06908: {0} : failed to write last process model

Cause: {0} : failed to write last process model

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06909: {0} : problem saving basic run information: {0}

Cause: {0} : problem saving basic run information: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06910: {0} : problem updating run information: {0}

Cause: {0} : problem updating run information: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06911: {0} : error during cloud preparation

Cause: {0} : error during cloud preparation

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06912: {0} : absolutely nothing to do

Cause: {0} : absolutely nothing to do

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-06913: {0} : [{1}] batch {2} terminated by exception: {3}

Cause: {0} : [{1}] batch {2} terminated by exception: {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06914: {0} : error during process preparation

Cause: {0} : error during process preparation

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06915: {0} : error during {1} preparation: {2}

Cause: {0} : error during {1} preparation: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06916: {0} : [{1}.{2}] batch {3} terminated by exception: {4}

Cause: {0} : [{1}.{2}] batch {3} terminated by exception: {4}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06917: {0} : started execution

Cause: {0} : started execution

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-06918: {0} : finished execution in {1}

Cause: {0} : finished execution in {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-06919: {0} : runtime process terminated uncleanly: {1}

Cause: {0} : runtime process terminated uncleanly: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06920: {0} : Failed to build new interval cloud: {1}

Cause: {0} : Failed to build new interval cloud: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06921: job {0}: invalid {1} option {2}

Cause: job {0}: invalid {1} option {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06922: job {0}: error loading process by name {1}

Cause: job {0}: error loading process by name {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06923: job {0}: process {1} loaded but is not valid

Cause: job {0}: process {1} loaded but is not valid

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06924: job {0}: unknown execution mode {1}

Cause: job {0}: unknown execution mode {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06925: job {0}: preparation and interval modes both set

Cause: job {0}: preparation and interval modes both set

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06926: job {0}: interval mode specified but no interval defined

Cause: job {0}: interval mode specified but no interval defined

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06927: job {0}: interval mode specified but interval is zero

Cause: job {0}: interval mode specified but interval is zero

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06928: job {0}: process {1}: '{2}' mode is not licensed

Cause: job {0}: process {1}: '{2}' mode is not licensed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-06929: job {0}: invalid {1} option {2} for item {3}

Cause: job {0}: invalid {1} option {2} for item {3}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06930: job {0}: process {1} item {2}: '{3}' mode is not licensed

Cause: job {0}: process {1} item {2}: '{3}' mode is not licensed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-06931: job {0}: process {1}: ignoring 'force run' because interval mode is set

Cause: job {0}: process {1}: ignoring 'force run' because interval mode is set

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-06932: job {0}: process {1}: removing interval mode

Cause: job {0}: process {1}: removing interval mode

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-06933: job {0}: process {1}: error creating runtime process

Cause: job {0}: process {1}: error creating runtime process

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06934: unknown interface attribute {0} in mapping

Cause: unknown interface attribute {0} in mapping

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06935: unknown real attribute {0} in mapping

Cause: unknown real attribute {0} in mapping

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06936: types of virtual attribute {0} and real attribute {1} do not match

Cause: types of virtual attribute {0} and real attribute {1} do not match

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06937: {0}: expression property missing for output {1}

Cause: {0}: expression property missing for output {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06938: {0}: error in expression '{1}': {2}

Cause: {0}: error in expression '{1}': {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06939: Preparing cloud for interval {0}

Cause: Preparing cloud for interval {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-06940: Switching execution to interval {0}

Cause: Switching execution to interval {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-06941: finished execution in {0}

Cause: finished execution in {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-06942: could not retrieve RunInformaiton for runId {0}: {1}

Cause: could not retrieve RunInformaiton for runId {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06943: Schema '{0}' load failed!

Cause: Schema '{0}' load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06944: Failed to encode processor runtime

Cause: Failed to encode processor runtime

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06945: Failed to decode processor runtime

Cause: Failed to decode processor runtime

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06946: data mode name {0} not recognised

Cause: data mode name {0} not recognised

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06947: error importing process {0}

Cause: error importing process {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06948: error creating munger result writer

Cause: error creating munger result writer

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06949: error closing result writer

Cause: error closing result writer

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06950: error preparing persister

Cause: error preparing persister

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06951: error opening resource {0}

Cause: error opening resource {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06952: error creating result writer

Cause: error creating result writer

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06953: error closing record source: {0}

Cause: error closing record source: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06954: Error cleaning up results publishing

Cause: Error cleaning up results publishing

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06955: Error closing writer

Cause: Error closing writer

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-06960: Error creating server load plugin; {0} - falling back to default

Cause: Error creating server load plugin; {0} - falling back to default

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-06961: Error computing server load; {0}

Cause: Error computing server load; {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07200: Error doing processor validation

Cause: Error doing processor validation

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07201: Error loading all projects

Cause: Error loading all projects

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07202: Error loading project {0}

Cause: Error loading project {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07203: Error deleting project {0}

Cause: Error deleting project {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07204: Error saving project {0} {1}

Cause: Error saving project {0} {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07205: Error deleting doc {0}

Cause: Error deleting doc {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07206: Error saving doc {0} {1}

Cause: Error saving doc {0} {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07207: Error creating doc {0} {1}

Cause: Error creating doc {0} {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07208: Error publishing template {0}

Cause: Error publishing template {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07209: Error deleting composite {0}

Cause: Error deleting composite {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07210: Error loading node: {0} {1}

Cause: Error loading node: {0} {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07211: Error loading compound processors

Cause: Error loading compound processors

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07212: There is no document version for process '{0}'

Cause: There is no document version for process '{0}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07213: Error getting runtime process model for {0}

Cause: Error getting runtime process model for {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07214: Error loading process {0}

Cause: Error loading process {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07215: Project exception whilst formulating dependency message

Cause: Project exception whilst formulating dependency message

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07216: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07217: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07218: Failed load published processor: {0} Project: {1}

Cause: Failed load published processor: {0} Project: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07219: {0} XStore items found in import file: {1} {2} {3}

Cause: {0} XStore items found in import file: {1} {2} {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07220: Error ending transaction

Cause: Error ending transaction

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07221: Error inserting note

Cause: Error inserting note

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07222: Error updating note

Cause: Error updating note

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07223: Error deleting note

Cause: Error deleting note

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07224: Error loading notes

Cause: Error loading notes

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07225: Error loading note

Cause: Error loading note

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07300: Bad port number {0} - net promulgation disabled

Cause: Bad port number {0} - net promulgation disabled

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07301: Client key {0} cleared by death of session {1}

Cause: Client key {0} cleared by death of session {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-07302: Promulgation server bound to port {0}

Cause: Promulgation server bound to port {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-07303: Setting select timeout to avoid promulgation deadlocks

Cause: Setting select timeout to avoid promulgation deadlocks

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-07304: Failed to set up promulgation listener

Cause: Failed to set up promulgation listener

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07305: Problem closing

Cause: Problem closing

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07306: Error in select

Cause: Error in select

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07307: Server connection from {0}

Cause: Server connection from {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07308: Error accepting socket

Cause: Error accepting socket

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07309: Quite unexpected error in queueing an incident!

Cause: Quite unexpected error in queueing an incident!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07400: Error loading native library: {0}

Cause: Error loading native library: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07401: QAS Batch Error Code: {0}

Cause: QAS Batch Error Code: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07402: Error loading QA Batch layout '{0}': {1}

Cause: Error loading QA Batch layout '{0}': {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07500: Realtime functional pack enabled

Cause: Realtime functional pack enabled

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-07501: Realtime messenger type {0} not supported

Cause: Realtime messenger type {0} not supported

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07502: Realtime messenger type {0} does not support synchronous mode

Cause: Realtime messenger type {0} does not support synchronous mode

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07503: Realtime: incoming configuration must include <incoming>

Cause: Realtime: incoming configuration must include <incoming>

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07504: Realtime: outgoing configuration must include <outgoing>

Cause: Realtime: outgoing configuration must include <outgoing>

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07505: Realtime: could not convert {0} to a duration: {1}

Cause: Realtime: could not convert {0} to a duration: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07506: Realtime: error creating payload demolisher for {0} messages: {1}

Cause: Realtime: error creating payload demolisher for {0} messages: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07507: Realtime: {0} record read failed: {1}

Cause: Realtime: {0} record read failed: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07508: Realtime: error closing {0} receiver: {1}

Cause: Realtime: error closing {0} receiver: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07509: Realtime: error finishing {0} receiver: {1}

Cause: Realtime: error finishing {0} receiver: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07510: Realtime: error creating payload builder for {0} messages: {1}

Cause: Realtime: error creating payload builder for {0} messages: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07511: Realtime: synchronous output message must contain a single record (has {0})

Cause: Realtime: synchronous output message must contain a single record (has {0})

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07512: Realtime: error transmission failed: {0}

Cause: Realtime: error transmission failed: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07513: Realtime: error transmitting packet to {0}: {1}

Cause: Realtime: error transmitting packet to {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07514: Realtime: error transmitting {0} terminator: {1}

Cause: Realtime: error transmitting {0} terminator: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07515: Realtime: error closing {0} transmitter: {1}

Cause: Realtime: error closing {0} transmitter: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07516: Realtime: error on {0} messenger close: {1}

Cause: Realtime: error on {0} messenger close: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07520: Realtime: error in XPath expression "{0}": {1}

Cause: Realtime: error in XPath expression "{0}": {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07521: Realtime: error parsing XML from message: {0}

Cause: Realtime: error parsing XML from message: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07522: Realtime: error evaluating XPath {0}: {1}

Cause: Realtime: error evaluating XPath {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07523: Realtime: error evaluating string XPath {0}: {1}

Cause: Realtime: error evaluating string XPath {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07524: Realtime: error evaluating array XPath {0}: {1}

Cause: Realtime: error evaluating array XPath {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07525: Realtime: bad value "{0}" for attribute {1}

Cause: Realtime: bad value "{0}" for attribute {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07526: Realtime: xmltemplate must contain exactly one child element

Cause: Realtime: xmltemplate must contain exactly one child element

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07527: Realtime: '} missing after $'{ in expansion document

Cause: Realtime: '} missing after $'{ in expansion document

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07528: Realtime: unknown $'{...'} attribute {0}

Cause: Realtime: unknown $'{...'} attribute {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07529: Realtime: error parsing XSL template: {0}

Cause: Realtime: error parsing XSL template: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07530: Realtime: bean set exception for {0} on {1}: {2}

Cause: Realtime: bean set exception for {0} on {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07531: Realtime: bean get exception for {0} on {1}: {2}

Cause: Realtime: bean get exception for {0} on {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07532: Realtime: bean create exception for {0} on {1}: {2}

Cause: Realtime: bean create exception for {0} on {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07540: Realtime: failed to get JNDI credentials: {0}

Cause: Realtime: failed to get JNDI credentials: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07541: Realtime: failed to get JMS connection credentials: {0}

Cause: Realtime: failed to get JMS connection credentials: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07542: Realtime: failed to create JNDI InitialContext: {0}

Cause: Realtime: failed to create JNDI InitialContext: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07543: Realtime: failed to lookup ConnectionFactory {0}: {1}

Cause: Realtime: failed to lookup ConnectionFactory {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07544: Realtime: failed to lookup destination {0}: {1}

Cause: Realtime: failed to lookup destination {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07545: Realtime: failed to create JMS connection: {0}

Cause: Realtime: failed to create JMS connection: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07546: Realtime: JMS autoacknowledge option "{0}" should be ''true'' or ''false''

Cause: Realtime: JMS autoacknowledge option "{0}" should be ''true'' or ''false''

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07547: Realtime: bad value "{0}" for JMS maxpendingmessages

Cause: Realtime: bad value "{0}" for JMS maxpendingmessages

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07548: Realtime: bad value "{0}" for JMS maxpendingtime

Cause: Realtime: bad value "{0}" for JMS maxpendingtime

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07549: Realtime: error closing JMS connection: {0}

Cause: Realtime: error closing JMS connection: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07550: Realtime: failed to create JMS session: {0}

Cause: Realtime: failed to create JMS session: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07551: Realtime: failed to create JMS message producer: {0}

Cause: Realtime: failed to create JMS message producer: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07552: Realtime: failed to create {0} JMS message: {1}

Cause: Realtime: failed to create {0} JMS message: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07553: Realtime: failed to send {0} JMS message: {1}

Cause: Realtime: failed to send {0} JMS message: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07554: Realtime: failed to create JMS message consumer: {0}

Cause: Realtime: failed to create JMS message consumer: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07555: Realtime: could not start JMS connection: {0}

Cause: Realtime: could not start JMS connection: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07556: Realtime: error receiving JMS message: {0}

Cause: Realtime: error receiving JMS message: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07560: Realtime: problem stopping WS listener for {0}/{1}: {2}

Cause: Realtime: problem stopping WS listener for {0}/{1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07561: Realtime: no registry available, RMI messenger will not be visible

Cause: Realtime: no registry available, RMI messenger will not be visible

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07562: Realtime: RMI messenger bound to registry with name {0}

Cause: Realtime: RMI messenger bound to registry with name {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-07563: Realtime: Failed to bind RMI messenger to registry: {0}

Cause: Realtime: Failed to bind RMI messenger to registry: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07564: Realtime: RMI messenger unbound from registry with name {0}

Cause: Realtime: RMI messenger unbound from registry with name {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-07565: Realtime: Failed to unbind RMI messenger from registry: {0}

Cause: Realtime: Failed to unbind RMI messenger from registry: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07566: Realtime: Error unexporting RMI object: {0}

Cause: Realtime: Error unexporting RMI object: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07570: Realtime: bad value "{0}" for attribute {1}

Cause: Realtime: bad value "{0}" for attribute {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07571: Realtime: non-scalar JSON value for attribute {0}

Cause: Realtime: non-scalar JSON value for attribute {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07700: Closing JDBC resource iterator

Cause: Closing JDBC resource iterator

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07900: Table remover error : {0}

Cause: Table remover error : {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07901: Work unit error: {0}

Cause: Work unit error: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07902: Explain error: {0}

Cause: Explain error: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07903: Unable to index table '{0}' : {1}

Cause: Unable to index table '{0}' : {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07904: Unable to analyse table '{0}' : {1}

Cause: Unable to analyse table '{0}' : {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07905: Index error: {0}

Cause: Index error: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07906: Malformed UUID in {0}/{1}/{2}

Cause: Malformed UUID in {0}/{1}/{2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07907: Error while dropping table '{0}' : {1}

Cause: Error while dropping table '{0}' : {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07908: There was an error inserting entry for {0} and processId {1} into the DNProcessOwnedDataTable table because it exists already

Cause: There was an error inserting entry for {0} and processId {1} into the DNProcessOwnedDataTable table because it exists already

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07909: There was an error retrieving existing tables for processId {0} from the processowneddata table

Cause: There was an error retrieving existing tables for processId {0} from the processowneddata table

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07910: Table did not exist {0} although the processowneddata table indicates that it should for process with id {1}

Cause: Table did not exist {0} although the processowneddata table indicates that it should for process with id {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07911: There was an error deleting table entries from DNRunOwnsResultsTable for process {0}

Cause: There was an error deleting table entries from DNRunOwnsResultsTable for process {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07912: Could not get the properties for the results database

Cause: Could not get the properties for the results database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07913: Not inserting value into dn_identity table for dn_runinformation as it already exists

Cause: Not inserting value into dn_identity table for dn_runinformation as it already exists

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-07914: SQLException when trying to enter value into dn_identity table for dn_runinformation

Cause: SQLException when trying to enter value into dn_identity table for dn_runinformation

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07915: There was an error retrieving existing tables for processId {0} from the DNProcessOwnsResultTable table

Cause: There was an error retrieving existing tables for processId {0} from the DNProcessOwnsResultTable table

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07916: Table did not exist {0} although the DNProcessOwnsResultTable indicates that it should for process with id {1}

Cause: Table did not exist {0} although the DNProcessOwnsResultTable indicates that it should for process with id {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-07917: There was an deleting table entries from DNProcessOwnsResultsTable for process {0}

Cause: There was an deleting table entries from DNProcessOwnsResultsTable for process {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-07918: A recoverable database error has occurred.

Cause: A recoverable database error has occurred.

Action: Contact the database administrator.
Level: 1

Type: ERROR

Impact: Other

EDQ-07919: A transient database error has occurred.

Cause: A transient database error has occurred.

Action: Contact the database administrator.
Level: 1

Type: ERROR

Impact: Other

EDQ-07920: Unable to recover from database error. {0}

Cause: A database error has occurred.

Action: Contact the database administrator.
Level: 1

Type: ERROR

Impact: Other

EDQ-08000: Starting execution of results export {0}

Cause: Starting execution of results export {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-08001: Error running results export {0} : result set is null

Cause: Error running results export {0} : result set is null

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08002: Export error : {0}

Cause: Export error : {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08003: Finished execution in {0}s

Cause: Finished execution in {0}s

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-08004: Cancelling job

Cause: Cancelling job

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-08005: Interrupted while waiting: {0}

Cause: Interrupted while waiting: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08006: Error ending transaction

Cause: Error ending transaction

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08007: {0} XStore items found in import file: {1}, {2}, {3}

Cause: {0} XStore items found in import file: {1}, {2}, {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08008: Schema '{0}' load failed!

Cause: Schema '{0}' load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08009: Failed to decode result set export

Cause: Failed to decode result set export

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08010: Failed to encode result

Cause: Failed to encode result

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08011: Error getting result set export : {0}

Cause: Error getting result set export : {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08012: Error deleting result set export

Cause: Error deleting result set export

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08013: Error importing result set export: {0}

Cause: Error importing result set export: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08014: Prepare error: {0}

Cause: Prepare error: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08015: There was a problem deleting the result set exports for project {0}

Cause: There was a problem deleting the result set exports for project {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08016: Error retrieving details of result set export for dependencies

Cause: Error retrieving details of result set export for dependencies

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08017: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08018: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08019: Error during result set export diff

Cause: Error during result set export diff

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08020: Results book export run with runlabel. No results will be exported since results are not created when run with a runlabel.

Cause: Results book export run with runlabel. No results will be exported since results are not created when run with a runlabel.

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08100: Error retrieving data

Cause: Error retrieving data

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08101: Error loaading resultset {0} in project {1}: {2}

Cause: Error loaading resultset {0} in project {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08102: {0} XStore items found in import file: {1}, {2}, {3}

Cause: {0} XStore items found in import file: {1}, {2}, {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08103: Provider error: {0}

Cause: Provider error: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08104: Error ending transaction

Cause: Error ending transaction

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08105: Failed to load view definition

Cause: Failed to load view definition

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08106: Schema '{0}' load failed

Cause: Schema '{0}' load failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08107: Failed to decode result

Cause: Failed to decode result

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08108: Failed to encode result

Cause: Failed to encode result

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08109: Unable to retrieve process id from name while migrating results book

Cause: Unable to retrieve process id from name while migrating results book

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08110: Unable to retrieve run information while migrating results book

Cause: Unable to retrieve run information while migrating results book

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08111: Unable to retrieve staged data definition id from name while migrating results book

Cause: Unable to retrieve staged data definition id from name while migrating results book

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08112: Unable to find results item from previous xml definition

Cause: Unable to find results item from previous xml definition

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08113: Unable to match results book page mapping columns from previous xml definition for {0}. This view will be reconstructed

Cause: Unable to match results book page mapping columns from previous xml definition for {0}. This view will be reconstructed

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08114: Unable to find candidate from previous xml definition, the id was: {0}

Cause: Unable to find candidate from previous xml definition, the id was: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08115: Error retrieving result set: {0}

Cause: Error retrieving result set: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08116: Error deleting result set: {0}

Cause: Error deleting result set: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08117: Error importing result set: {0}

Cause: Error importing result set: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08118: There was a problem deleting the results books for project {0}

Cause: There was a problem deleting the results books for project {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08119: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08120: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08121: Error during result set diff

Cause: Error during result set diff

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08200: An error has occurred : {0}

Cause: An error has occurred : {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08201: enable to retrieve process name: {0}

Cause: enable to retrieve process name: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08300: Schema '{0}' load failed!

Cause: Schema '{0}' load failed!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08301: Failed to decode results publishing job option XML string: {0}

Cause: Failed to decode results publishing job option XML string: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08302: Result publish info cannot be saved

Cause: Result publish info cannot be saved

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08303: Failed to start transaction

Cause: Failed to start transaction

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08304: Error ending transaction

Cause: Error ending transaction

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08305: Error loading results publishing info for process: id = '{0}'

Cause: Error loading results publishing info for process: id = '{0}'

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08306: Failed to decode result publishing info

Cause: Failed to decode result publishing info

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08400: Results retrieval - Error loading data

Cause: Results retrieval - Error loading data

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08600: Error deleting run

Cause: Error deleting run

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08601: Error accessing run information

Cause: Error accessing run information

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08602: Error purging results for job with id {0}

Cause: Error purging results for job with id {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08603: Marking runs for deletion failed

Cause: Marking runs for deletion failed

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08604: Error getting runs for job with id {0}

Cause: Error getting runs for job with id {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08605: Error deleting job results with id {0}

Cause: Error deleting job results with id {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08606: Error deleting job results for run label {0}

Cause: Error deleting job results for run label {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08607: Error cleaning up for project {0}

Cause: Error cleaning up for project {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08608: Error deleting job results for project {0} with run label

Cause: Error deleting job results for project {0} with run label

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08609: Error deleting job results for job {0} with run label

Cause: Error deleting job results for job {0} with run label

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08610: Error deleting job results for job {0} with run label {1}

Cause: Error deleting job results for job {0} with run label {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08700: SCCS workspace is {0}

Cause: SCCS workspace is {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-08701: SCCS scan failed: {0}

Cause: SCCS scan failed: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08702: SCCS: Configuration database is not compatible with workspace: {0}

Cause: SCCS: Configuration database is not compatible with workspace: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08703: SCCS: Scan request for unrecognized file "{0}": ignored

Cause: SCCS: Scan request for unrecognized file "{0}": ignored

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08704: SCCS: File system commit/rollback failed: CHECK CONSISTENTY!

Cause: SCCS: File system commit/rollback failed: CHECK CONSISTENTY!

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08705: SCCS: State query failed: {0}

Cause: SCCS: State query failed: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08706: SCCS RevsionStore: diff with empty path and no local file: ignored

Cause: SCCS RevsionStore: diff with empty path and no local file: ignored

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08707: SCCS: Clear dependencies for {0} failed: {1}

Cause: SCCS: Clear dependencies for {0} failed: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08708: SCCS: Error during project delete: {0}

Cause: SCCS: Error during project delete: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08709: VCS: system version property not set on workspace

Cause: VCS: system version property not set on workspace

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08710: VCS: Incorrect system version on workspace: "{0}" found, "{1}" expected

Cause: VCS: Incorrect system version on workspace: "{0}" found, "{1}" expected

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08711: VCS: Invalid server credentials mode "{0}": ignored

Cause: VCS: Invalid server credentials mode "{0}": ignored

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08712: SCCS meta-data migrated to database: directory {0} is no longer required

Cause: SCCS meta-data migrated to database: directory {0} is no longer required

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-08713: SCCS: error reading patch information in {0}: {1}

Cause: SCCS: error reading patch information in {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08714: SCCS: rescanning workspace due to patch addition:

Cause: SCCS: rescanning workspace due to patch addition:

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-08715: SCCS: rescanning workspace due to patch removal:

Cause: SCCS: rescanning workspace due to patch removal:

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-08716: {0}: {1}

Cause: {0}: {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-08750: SCCS: SVNKit commit error: {0}

Cause: SCCS: SVNKit commit error: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08751: SCCS: SVNKit error reverting "{0}" after failed commit: {1}

Cause: SCCS: SVNKit error reverting "{0}" after failed commit: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08752: SCCS: GSS exception using delegated credentials: {0}

Cause: SCCS: GSS exception using delegated credentials: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08760: SCCS: JavaHL commit error: {0}

Cause: SCCS: JavaHL commit error: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08761: SCCS: JavaHL error reverting "{0}" after failed commit: {1}

Cause: SCCS: JavaHL error reverting "{0}" after failed commit: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08800: script cleanup failed: %s

Cause: script cleanup failed: %s

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-08900: Scripting: {0} schema load failed: {1}

Cause: Scripting: {0} schema load failed: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08901: Scripting: {0}: plugin script file not specified;

Cause: Scripting: {0}: plugin script file not specified;

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08902: Scripting: {0}: class {1} not found

Cause: Scripting: {0}: class {1} not found

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08903: Scripting: {0}: class {1} does not implement {2}

Cause: Scripting: {0}: class {1} does not implement {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08904: Scripting: {0}: class {1} does not have zero arg constructor

Cause: Scripting: {0}: class {1} does not have zero arg constructor

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08905: Scripting: {0}: failed to create plugin instance: {1}

Cause: Scripting: {0}: failed to create plugin instance: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08906: Scripting: {0}: plugin script file {1} not found

Cause: Scripting: {0}: plugin script file {1} not found

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08907: Scripting: {0}: error loading script from file {1}: {2}

Cause: Scripting: {0}: error loading script from file {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08908: Scripting: {0}: failed to create plugin script engine: {1}

Cause: Scripting: {0}: failed to create plugin script engine: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08909: Scripting: {0}: failed to import plugin classes: {1}

Cause: Scripting: {0}: failed to import plugin classes: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08910: Scripting: {0}: failed to set plugin root object: {1}

Cause: Scripting: {0}: failed to set plugin root object: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08911: Scripting: {0}: failed to compile script: {0}

Cause: Scripting: {0}: failed to compile script: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-08912: Scripting: {0}: ''{1}'' function missing in script

Cause: Scripting: {0}: ''{1}'' function missing in script

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09000: Error ending transaction

Cause: Error ending transaction

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09001: Unsupported data type {0} from external database

Cause: Unsupported data type {0} from external database

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09002: Error closing data uploader for staged data id {0}

Cause: Error closing data uploader for staged data id {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09003: Error closing results

Cause: Error closing results

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09004: Error closing query

Cause: Error closing query

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09005: Error updating snapshot data profile and optimizing for browsing

Cause: Error occurred accessing the configuration database while writing the snapshot data profile.

Action: Check the server logs for errors.
Level: 1

Type: ERROR

Impact: Other

Cause: Error occurred submitting the optimize for browsing task for execution

Action: Check the server logs for errors.

EDQ-09006: {0} XStore items found in import file: {1}, {2}, {3}

Cause: {0} XStore items found in import file: {1}, {2}, {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09007: {0} staged data XTree nodes found in import file: {1}, {2}

Cause: {0} staged data XTree nodes found in import file: {1}, {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09008: Attribute defns not found for snapshot {0}

Cause: Attribute defns not found for snapshot {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09009: {0} externalized property XTree nodes found in import file: {1}, {2}

Cause: {0} externalized property XTree nodes found in import file: {1}, {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09010: Error importing snapshot

Cause: The package (DXI) file is incomplete or corrupt.

Action: Create a new copy of the package file.
Level: 1

Type: ERROR

Impact: Other

Cause: Error occurred accessing the configuration database while writing the imported snapshot.

Action: Correct the error and retry, contact support if problem persists

EDQ-09011: Failed to decode snapshot

Cause: The XML document for the snapshot was invalid.

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09012: Failed to encode snapshot

Cause: The generated XML did not conform to the schema or there was an XML configuration error

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09013: Error purging project snapshots

Cause: Error removing snapshot tables from the results database.

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09014: Snapshot executing: {0}

Cause: Snapshot executing: {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-09015: Error preparing optimize task during snapshot execution

Cause: Error preparing optimize task during snapshot execution

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09016: Snapshot ending execution immediately

Cause: Snapshot ending execution immediately

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-09017: Error uploading snapshot data

Cause: Error uploading snapshot data

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09018: Error ending upload of snapshot data

Cause: Error ending upload of snapshot data

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09019: Error during snapshot execution: {0}

Cause: Error during snapshot execution: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09020: Snapshot {0} finished execution in {1}

Cause: Snapshot {0} finished execution in {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-09021: Error during snapshot configuration analysis

Cause: Error during snapshot configuration analysis

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09022: Error getting snapshot

Cause: Error getting snapshot

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09023: Error deleting staged data

Cause: Error deleting staged data

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09024: Problem retrieving snapshot providers

Cause: Problem retrieving snapshot providers

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09025: There was a problem updating the local flag on snapshots dependent on data source

Cause: There was a problem updating the local flag on snapshots dependent on data source

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09026: There was a problem deleting the snapshots for project {0}

Cause: There was a problem deleting the snapshots for project {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09027: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09100: Error ending transaction

Cause: Error ending transaction

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09101: Error deleting staged data

Cause: Error deleting staged data

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09102: Error importing data for node: {0}

Cause: Error importing data for node: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09103: Error creating staged data: {0}

Cause: Error creating staged data: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09104: Failed to decode staged data data profile

Cause: Failed to decode staged data data profile

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09105: Failed to encode staged data profile

Cause: Failed to encode staged data profile

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09106: Failed to decode staged data attributes

Cause: Failed to decode staged data attributes

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09107: Failed to encode staged data attributes

Cause: Failed to encode staged data attributes

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09108: Error during staged data configuration analysis

Cause: Error during staged data configuration analysis

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09109: Error retrieving known consumers for staged data in project id {0}

Cause: Error retrieving known consumers for staged data in project id {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09110: Error retrieving known providers for staged data in project id {0}

Cause: Error retrieving known providers for staged data in project id {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09111: Purging staged data: {0}

Cause: Purging staged data: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09112: Deleting staged data: {0}

Cause: Deleting staged data: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09113: Error optimizing staged data for browsing: {0}

Cause: Error optimizing staged data for browsing: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09114: Error deleting staged data in project

Cause: Error deleting staged data in project

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09115: Unable to get attributes for staged data Id: {0}

Cause: Unable to get attributes for staged data Id: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09116: Error refreshing data profile for staged data from database

Cause: Error refreshing data profile for staged data from database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09117: Error closing staged data writer: {0}

Cause: Error closing staged data writer: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09118: Error updating data profile for staged data: {0}

Cause: Error updating data profile for staged data: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09119: Error occurred creating staged table catalogue entries: {0}

Cause: Error occurred creating staged table catalogue entries: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09300: Error during copy/paste: {0}

Cause: Error during copy/paste: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09301: Failed to export to file ''{0}''

Cause: Failed to export to file ''{0}''

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09302: Error importing from server

Cause: Error importing from server

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09303: Error importing from file

Cause: Error importing from file

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09304: Error loading associated nodes for ''{0}''

Cause: Error loading associated nodes for ''{0}''

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09305: Incorrect file handle usage during transfer

Cause: Incorrect file handle usage during transfer

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09400: Trigger configuration: bad default trigger level "{0}"

Cause: Trigger configuration: bad default trigger level "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09401: Trigger configuration: bad trigger override pattern "{0}": {1}

Cause: Trigger configuration: bad trigger override pattern "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09402: Trigger configuration: bad trigger override level "{0}"

Cause: Trigger configuration: bad trigger override level "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09403: Trigger manager: problem reading schema file: {0}

Cause: Trigger manager: problem reading schema file: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09404: Trigger file {0}: error opening as jar file: {1}

Cause: Trigger file {0}: error opening as jar file: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09405: Trigger file {0}: {1} not found - skipping file

Cause: Trigger file {0}: {1} not found - skipping file

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09406: Trigger file {0}: error reading contents: {1}

Cause: Trigger file {0}: error reading contents: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09407: Trigger file {0}: cannot open: {1}

Cause: Trigger file {0}: cannot open: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09408: Trigger file {0}: error reading: {1}

Cause: Trigger file {0}: error reading: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09409: Trigger file {0}: root element of {1} must be ''triggers''

Cause: Trigger file {0}: root element of {1} must be ''triggers''

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09410: Trigger file {0}: no path provided for type {1}

Cause: Trigger file {0}: no path provided for type {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09411: Trigger file {0}: bad path regex "{1}": {2}

Cause: Trigger file {0}: bad path regex "{1}": {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09412: Trigger file {0}: error in filter expression "{1}": {2}

Cause: Trigger file {0}: error in filter expression "{1}": {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09413: Trigger file {0}: argument class {1} not found

Cause: Trigger file {0}: argument class {1} not found

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09414: Trigger file {0}: class {1} not found

Cause: Trigger file {0}: class {1} not found

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09415: Trigger file {0}: class {1} does not implement ITrigger

Cause: Trigger file {0}: class {1} does not implement ITrigger

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09416: Trigger file {0}: class {1} does not have a zero-arg constructor

Cause: Trigger file {0}: class {1} does not have a zero-arg constructor

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09417: Trigger file {0}: error creating {0} instance: {1}

Cause: Trigger file {0}: error creating {0} instance: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09418: Trigger file {0}: error constructing {1} instance: {2}

Cause: Trigger file {0}: error constructing {1} instance: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09419: Trigger file {0}: error injecting class {1}: {2}

Cause: Trigger file {0}: error injecting class {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09420: Trigger file {0}: error loading script from resource {1}: {2}

Cause: Trigger file {0}: error loading script from resource {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09421: Trigger file {0}: script not defined

Cause: Trigger file {0}: script not defined

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09422: Trigger file {0}: error reading script: {1}

Cause: Trigger file {0}: error reading script: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09423: Trigger file {0}: no path specified by trigger script

Cause: Trigger file {0}: no path specified by trigger script

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09424: Trigger file {0}: invalid path regex "{1}": {2}

Cause: Trigger file {0}: invalid path regex "{1}": {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09425: Trigger file {0}: no loader provider named {1}

Cause: Trigger file {0}: no loader provider named {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09426: Trigger file {0}: runtime loader {1} not available: pending initialization

Cause: Trigger file {0}: runtime loader {1} not available: pending initialization

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-09427: Trigger file {0}: invalid loaderprovider attribute "{1}"

Cause: Trigger file {0}: invalid loaderprovider attribute "{1}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09428: Trigger file {0}: error reading icon file {1}: {2}

Cause: Trigger file {0}: error reading icon file {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09429: Triggers reloaded from {0}

Cause: Triggers reloaded from {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-09430: Triggers: arguments not compatible with trigger for path {0}

Cause: Triggers: arguments not compatible with trigger for path {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09431: Trigger on path {0} failed: {1}

Cause: Trigger on path {0} failed: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09432: Triggers: no action runner for type {0}

Cause: Triggers: no action runner for type {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09433: Triggers: invalid action configuration object for type {0}

Cause: Triggers: invalid action configuration object for type {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09434: Triggers: action type {0} failed with unchecked exception: {1}

Cause: Triggers: action type {0} failed with unchecked exception: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09435: Trigger file {0}: failed to create script engine: {1}

Cause: Trigger file {0}: failed to create script engine: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09436: Trigger file {0}: error importing script trigger classes: {1}

Cause: Trigger file {0}: error importing script trigger classes: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09437: Trigger file {0}: failed to open script: {1}

Cause: Trigger file {0}: failed to open script: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09438: Trigger file {0}: failed to open script: missing class {1}

Cause: Trigger file {0}: failed to open script: missing class {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09439: Trigger file {0}: ''runtrigger'' and ''run'' functions missing in script

Cause: Trigger file {0}: ''runtrigger'' and ''run'' functions missing in script

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09440: Trigger file {0}: error calling ''getPath'' in script trigger: {1}

Cause: Trigger file {0}: error calling ''getPath'' in script trigger: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09441: Trigger file {0}: error calling script ''run'' function failed: {1}

Cause: Trigger file {0}: error calling script ''run'' function failed: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09442: Trigger file {0}: error calling script ''getLevel'' function: {1}

Cause: Trigger file {0}: error calling script ''getLevel'' function: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09443: Trigger file {0}: error calling script ''filter'' function: {1}

Cause: Trigger file {0}: error calling script ''filter'' function: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09444: Trigger file {0}: error calling script ''getTriggerNames'' function: {1}

Cause: Trigger file {0}: error calling script ''getTriggerNames'' function: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09445: Triggers: invalid configuration for {0} cancel: {1}

Cause: Triggers: invalid configuration for {0} cancel: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09450: JMS trigger instance {0}: InitialContext failed: {1}

Cause: JMS trigger instance {0}: InitialContext failed: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09451: JMS trigger instance {0}: connection factory "{1}" lookup failed: {2}

Cause: JMS trigger instance {0}: connection factory "{1}" lookup failed: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09452: JMS trigger instance {0}: failed to create connection: {1}

Cause: JMS trigger instance {0}: failed to create connection: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09453: JMS trigger instance {0}: error looking up source "{1}": {2}

Cause: JMS trigger instance {0}: error looking up source "{1}": {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09454: JMS trigger instance {0}: error creating session for reception: {1}

Cause: JMS trigger instance {0}: error creating session for reception: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09455: JMS trigger instance {0}: error creating message consumer: {1}

Cause: JMS trigger instance {0}: error creating message consumer: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09456: JMS trigger instance {0}: bad interval "{1}": ignored

Cause: JMS trigger instance {0}: bad interval "{1}": ignored

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09457: JMS trigger instance {0}: bad max work value "{1}": ignored

Cause: JMS trigger instance {0}: bad max work value "{1}": ignored

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09458: JMS trigger instance {0}: unknown message header "{1}": ignored

Cause: JMS trigger instance {0}: unknown message header "{1}": ignored

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09459: JMS trigger instance {0}: error starting connection: {1}

Cause: JMS trigger instance {0}: error starting connection: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09460: JMS trigger instance {0}: error looking up destination "{1}": {2}

Cause: JMS trigger instance {0}: error looking up destination "{1}": {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09461: JMS trigger instance {0}: error creating session for transmission: {1}

Cause: JMS trigger instance {0}: error creating session for transmission: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09462: JMS trigger instance {0}: error creating message producer: {1}

Cause: JMS trigger instance {0}: error creating message producer: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09463: JMS trigger instance {0}: error closing connection: {1}

Cause: JMS trigger instance {0}: error closing connection: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09464: JMS trigger instance {0}: error closing initial context: {1}

Cause: JMS trigger instance {0}: error closing initial context: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09465: JMS trigger instance {0}: message reception error: {1}

Cause: JMS trigger instance {0}: message reception error: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09466: JMS trigger instance {0}: error retrieving header {1}: {2}

Cause: JMS trigger instance {0}: error retrieving header {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09467: JMS trigger instance {0}: error getting message text: {1}

Cause: JMS trigger instance {0}: error getting message text: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09468: JMS trigger instance {0}: non text message ignored

Cause: JMS trigger instance {0}: non text message ignored

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09469: JMS trigger instance {0}: error closing message consumer: {1}

Cause: JMS trigger instance {0}: error closing message consumer: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09470: JMS trigger instance {0}: error closing message consumer session: {1}

Cause: JMS trigger instance {0}: error closing message consumer session: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09471: JMS trigger instance {0}: error creating text message: {1}

Cause: JMS trigger instance {0}: error creating text message: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09472: JMS trigger instance {0}: unknown header ''{1}'' for new message

Cause: JMS trigger instance {0}: unknown header ''{1}'' for new message

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09473: JMS trigger instance {0}: value "{1}" is not suitable for header {2}

Cause: JMS trigger instance {0}: value "{1}" is not suitable for header {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09474: JMS trigger instance {0}: error setting header {1}: {2}

Cause: JMS trigger instance {0}: error setting header {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09475: JMS trigger instance {0}: error sending message: {1}

Cause: JMS trigger instance {0}: error sending message: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09476: JMS trigger instance {0}: error closing message producer: {1}

Cause: JMS trigger instance {0}: error closing message producer: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09477: JMS trigger instance {0}: error closing message producer session: {1}

Cause: JMS trigger instance {0}: error closing message producer session: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09478: {0}

Cause: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09479: JMS trigger instance {0}: attempting restart after error

Cause: JMS trigger instance {0}: attempting restart after error

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09500: Realm {0}: realm name not set

Cause: Realm {0}: realm name not set

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09501: Realm {0}: creation error: {1}

Cause: Realm {0}: creation error: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09502: Realm {0}: ldap.profile or auth not set

Cause: Realm {0}: ldap.profile or auth not set

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09503: Realm {0}: invalid LDAP profile: {0}

Cause: Realm {0}: invalid LDAP profile: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09504: Realm {0}: LDAP profile "{1}" not found

Cause: Realm {0}: LDAP profile "{1}" not found

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09505: Realm {0}: error crearing GSS configuration: {1}

Cause: Realm {0}: error crearing GSS configuration: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09506: Realm {0}: error in matching regex: {1}

Cause: Realm {0}: error in matching regex: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09507: Realm {0}: error querying DNS for LDAP servers in domain {1}: {2}

Cause: Realm {0}: error querying DNS for LDAP servers in domain {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09508: Realm {0}: no LDAP servers defined

Cause: Realm {0}: no LDAP servers defined

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09509: Realm {0}: unknown Sasl qop setting {1}

Cause: Realm {0}: unknown Sasl qop setting {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09510: Realm {0}: unknown security option {1}

Cause: Realm {0}: unknown security option {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09511: Realm {0}: invalid credential lifetime {1}

Cause: Realm {0}: invalid credential lifetime {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09512: Realm {0}: error getting canonical SPN: {1}

Cause: Realm {0}: error getting canonical SPN: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09513: Realm {0}: error getting credentials for LDAP server: {1}

Cause: Realm {0}: error getting credentials for LDAP server: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09514: Realm {0}: LDAP user or password not specified

Cause: Realm {0}: LDAP user or password not specified

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09515: Realm {0}: unknown LDAP server authentication method: {1}

Cause: Realm {0}: unknown LDAP server authentication method: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09516: Realm {0}: error creating LDAP server: {1}

Cause: Realm {0}: error creating LDAP server: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09517: Realm {0}: invalid basedn "{1}": {2}

Cause: Realm {0}: invalid basedn "{1}": {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09518: Realm {0}: basedn not specified;

Cause: Realm {0}: basedn not specified;

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09519: Realm {0}: error creating {1} authenticator: {2}

Cause: Realm {0}: error creating {1} authenticator: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09520: Realm factory class {0} not found

Cause: Realm factory class {0} not found

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09521: Realm factory class {1} does not implement RealmFactory

Cause: Realm factory class {1} does not implement RealmFactory

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09522: Error creating RealmFactory {0}: {1}

Cause: Error creating RealmFactory {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09523: Error attempting client Kerberos login: {0}

Cause: Error attempting client Kerberos login: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09524: Error performing server Kerberos login with SPN {0}: {1}

Cause: Error performing server Kerberos login with SPN {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09525: Error getting KRB5 server credentials: {0}

Cause: Error getting KRB5 server credentials: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09526: Error getting SPNEGO server credentials: {0}

Cause: Error getting SPNEGO server credentials: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09530: Failed to load login configuration: {0}

Cause: Failed to load login configuration: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09531: Error running filter for {0}: {1}

Cause: Error running filter for {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09532: Error creating GSS accept context: {0}

Cause: Error creating GSS accept context: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09533: Error accepting GSS token: {0}

Cause: Error accepting GSS token: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09534: Error querying GSS client identity: {0}

Cause: Error querying GSS client identity: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09535: Sessions: error looking up user {0}: {1}

Cause: Sessions: error looking up user {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09536: Sessions: error getting history for last {0} days: {1}

Cause: Sessions: error getting history for last {0} days: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09537: Sessions: error getting history: {0}

Cause: Sessions: error getting history: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09538: User cache persistence initialization failed: {0}

Cause: User cache persistence initialization failed: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09539: Realm {0}: error retrieving user list: {1}

Cause: Realm {0}: error retrieving user list: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09540: Realm {0}: error retrieving users in group with key {1}: {2}

Cause: Realm {0}: error retrieving users in group with key {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09541: Password checker: script call failed: {0}

Cause: Password checker: script call failed: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09542: User Management: filter call failed: {0}

Cause: User Management: filter call failed: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09543: User Management: failed to create filter instance: {0}

Cause: User Management: failed to create filter instance: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09544: LDAP password compare failed: {0}

Cause: LDAP password compare failed: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09545: Invalid DN "{0}" in member list for "{1}": {2}

Cause: Invalid DN "{0}" in member list for "{1}": {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09600: Problem getting known providers

Cause: Problem getting known providers

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09601: There was a problem deleting the user data for project {0}

Cause: There was a problem deleting the user data for project {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09602: Unable to delete user data table for imported user data whose definition has not been successfully created {0}

Cause: Unable to delete user data table for imported user data whose definition has not been successfully created {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09603: Error getting user data when validating lookup {0}

Cause: Error getting user data when validating lookup {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09604: Error closing user data writer to user data table with id {0}

Cause: Error closing user data writer to user data table with id {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09605: Error updating user data profile for user data {0}, when closing user data writer

Cause: Error updating user data profile for user data {0}, when closing user data writer

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-09606: Error creating user data data: {0}

Cause: Error creating user data data: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09607: Error creating staged data for user data: {0}

Cause: Error creating staged data for user data: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09608: Failed to decode user data data profile

Cause: Failed to decode user data data profile

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09609: Failed to decode user data attributes

Cause: Failed to decode user data attributes

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09610: Failed to encode user data attributes

Cause: Failed to encode user data attributes

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09611: Failed to encode user data data profile

Cause: Failed to encode user data data profile

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09612: Error initialising data base table {0} to import user data {1}

Cause: Error initialising data base table {0} to import user data {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09613: Error closing data base table during import of user data {0}

Cause: Error closing data base table during import of user data {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09615: Error clearing user data table {0}

Cause: Error clearing user data table {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09900: Error loading source view node after import

Cause: Error loading source view node after import

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09901: Error importing source view

Cause: Error importing source view

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-09902: Error parsing source view node

Cause: Error parsing source view node

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10000: Web Services: Unknown authentication method "{0}"

Cause: Web Services: Unknown authentication method "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10001: Web Services: no valid web services authentication methods configured

Cause: Web Services: no valid web services authentication methods configured

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10002: Web Services: failed to publish web service with id {0}: {1}

Cause: Web Services: failed to publish web service with id {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10003: Web Services: error republishing on project change: {0}

Cause: Web Services: error republishing on project change: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10004: Web Services: error during web service diff: {0}

Cause: Web Services: error during web service diff: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10005: Web Services: problem opening jar file {0}: {1}

Cause: Web Services: problem opening jar file {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10006: Web Services: {0} missing in {1}

Cause: Web Services: {0} missing in {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10007: Web Services: {0} missing in {1}

Cause: Web Services: {0} missing in {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10008: Web Services: error reading {0} from {1}: {2}

Cause: Web Services: error reading {0} from {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10009: Web Services: error reading {0} from {1}: {2}

Cause: Web Services: error reading {0} from {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10010: Web Services: skipping services in {0} because it contains a service with duplicate local name {1}

Cause: Web Services: skipping services in {0} because it contains a service with duplicate local name {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10011: Web Services: error reading {0} from {1}: {2}

Cause: Web Services: error reading {0} from {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10012: Web Services: error decoding XML in {0} from {1}: {2}

Cause: Web Services: error decoding XML in {0} from {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10013: Web Services: problem creating URI for wsdl: {0}

Cause: Web Services: problem creating URI for wsdl: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10014: Web Services: error creating binding definitions for {0}: {1}

Cause: Web Services: error creating binding definitions for {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10015: Web Services: error during publish for {0}: {1}

Cause: Web Services: error during publish for {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10016: Web Services: problem loading web service data: {0}

Cause: Web Services: problem loading web service data: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10017: Web Services: could not find project {0}

Cause: Web Services: could not find project {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10018: Web Services: failed to encode WSDLInfo: {0}

Cause: Web Services: failed to encode WSDLInfo: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10019: Web Services: package name missing with {0} binding

Cause: Web Services: package name missing with {0} binding

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10020: Web Services: failed to decode webservices XML: {0}

Cause: Web Services: failed to decode webservices XML: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10021: Web Services: error handing sccs item creation: {0}

Cause: Web Services: error handing sccs item creation: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10022: Web Services: error handing sccs item update: {0}

Cause: Web Services: error handing sccs item update: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10023: Web Services: {0} xitems for webservice {1} in project {2}

Cause: Web Services: {0} xitems for webservice {1} in project {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10024: Web Services: problem opening form mappings file {0}: {1}

Cause: Web Services: problem opening form mappings file {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10025: Web Services: problem parsing form mappings XML file {0}: {1}

Cause: Web Services: problem parsing form mappings XML file {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10026: Web Services: invalid project pattern "{0}" in {1}: {2}

Cause: Web Services: invalid project pattern "{0}" in {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10027: Web Services: invalid service pattern "{0}" in {1}: {2}

Cause: Web Services: invalid service pattern "{0}" in {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10028: Web Services: invalid page pattern "{0}" in {1}: {2}

Cause: Web Services: invalid page pattern "{0}" in {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10029: Web Services: form mapping file {0}: failed to create JS engine: {1}

Cause: Web Services: form mapping file {0}: failed to create JS engine: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10030: Web Services: form mapping file {0}: error importing {1}: {2}

Cause: Web Services: form mapping file {0}: error importing {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10031: Web Services: form mapping file {0}: failed to open script: {1}

Cause: Web Services: form mapping file {0}: failed to open script: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10032: Web Services: form mapping file {0}: failed to open script: missing class {1}

Cause: Web Services: form mapping file {0}: failed to open script: missing class {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10033: Web Services: form mapping file {0}: ''map'' function missing in script mapper

Cause: Web Services: form mapping file {0}: ''map'' function missing in script mapper

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10040: Web Services: error publishing endpoint: {0}

Cause: Web Services: error publishing endpoint: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10041: Web Services: error stopping endpoint: {0}

Cause: Web Services: error stopping endpoint: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10050: Web Services: malformed JSON in REST payload: {0}

Cause: Web Services: malformed JSON in REST payload: {0}

Action: Correct errors in message.
Level: 1

Type: WARNING

Impact: Other

EDQ-10051: Web Services: malformed XML in REST payload: {0}

Cause: Web Services: malformed XML in REST payload: {0}

Action: Correct errors in message.
Level: 1

Type: WARNING

Impact: Other

EDQ-10100: Processor library: {0} not found in processor file {1}

Cause: Processor library: {0} not found in processor file {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10101: Processor library: read error verifying processor file {0}: {1}

Cause: Processor library: read error verifying processor file {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10102: Processor library: verification error in processor file {0}: {1}

Cause: Processor library: verification error in processor file {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10103: Processor library: {0} in {1} cannot be verified

Cause: Processor library: {0} in {1} cannot be verified

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10104: Processor library: error reading from processor file {0}: {1}

Cause: Processor library: error reading from processor file {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10105: Processor library: verification error reading from processor file {0}: {1}

Cause: Processor library: verification error reading from processor file {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10106: Processor library: error generating processor transmission data: {0}

Cause: Processor library: error generating processor transmission data: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10107: Processor library: reloading processors because of change in licences or jar list

Cause: Processor library: reloading processors because of change in licences or jar list

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-10108: Processor library: processor bean {0} reported as failed: {1}

Cause: Processor library: processor bean {0} reported as failed: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10109: Processor library: exception initializing processor bean {0}: {1}

Cause: Processor library: exception initializing processor bean {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10110: Processor library: exception deactivating processor bean {0}: {1}

Cause: Processor library: exception deactivating processor bean {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10111: Processor library: duplicate processor {0} detected in {1} - ignored

Cause: Processor library: duplicate processor {0} detected in {1} - ignored

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10112: Processor library: skipping processor {0} because of bean creation problem

Cause: Processor library: skipping processor {0} because of bean creation problem

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10113: Processor library: exception calling {0} on {1} in processor {2}: {3}

Cause: Processor library: exception calling {0} on {1} in processor {2}: {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10114: Processor library: error creating a {0} bean: {1}

Cause: Processor library: error creating a {0} bean: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10115: Processor library: reading error during XML parsing in {0}: {1}

Cause: Processor library: reading error during XML parsing in {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10116: Processor library: failed to parse XML in {0}: {1})

Cause: Processor library: failed to parse XML in {0}: {1})

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10117: Processor library: skipping {0} due to errors in XML

Cause: Processor library: skipping {0} due to errors in XML

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10118: Processor library: no content in XML in {0}

Cause: Processor library: no content in XML in {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10119: Processor library: all processors in {0} rejected by available test

Cause: Processor library: all processors in {0} rejected by available test

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-10120: Processor library: permissions entry not allowed in unsigned jar {0} - skipping

Cause: Processor library: permissions entry not allowed in unsigned jar {0} - skipping

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10121: Processor library: failed to parse permissions element in {0}: {1}

Cause: Processor library: failed to parse permissions element in {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10122: Processor library: error reading permissions entry in {0}: {1}

Cause: Processor library: error reading permissions entry in {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10123: Processor library: regex error in {0} in {1}: {2}

Cause: Processor library: regex error in {0} in {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10124: Processor library: error parsing {0} in {1}: {2}

Cause: Processor library: error parsing {0} in {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10125: Processor library: error reading {0} in {1}: {2}

Cause: Processor library: error reading {0} in {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10126: Processor library: no <processor> or <munger> elements in {0}

Cause: Processor library: no <processor> or <munger> elements in {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10127: Processor library: invalid available expression "{0}" on <{1}> element in {2}: {3}

Cause: Processor library: invalid available expression "{0}" on <{1}> element in {2}: {3}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10128: Processor library: processor bean class {0} could not be found

Cause: Processor library: processor bean class {0} could not be found

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10129: Processor library: bean class {0} must implement ICustomizableProcessorBean to use parameters

Cause: Processor library: bean class {0} must implement ICustomizableProcessorBean to use parameters

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10130: Processor library: bean class {0} does not have the permission required to inject server object "{1}"

Cause: Processor library: bean class {0} does not have the permission required to inject server object "{1}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10131: Processor library: injection errors in bean class {0}: {1}

Cause: Processor library: injection errors in bean class {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10132: Processor library: errors in bean class {0}: {1}

Cause: Processor library: errors in bean class {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10133: Processor library: no resource named {0} in jar {1}

Cause: Processor library: no resource named {0} in jar {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10134: Processor library: problem reading resource {0} from {1}: {2}

Cause: Processor library: problem reading resource {0} from {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10135: Processor library: error during XML parsing: {0}

Cause: Processor library: error during XML parsing: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10136: Processor library: error during XML parsing at {0}: {1}

Cause: Processor library: error during XML parsing at {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10137: Processor library: fatal error during XML parsing: {0}

Cause: Processor library: fatal error during XML parsing: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10138: Processor library: fatal error during XML parsing at {0}: {1}

Cause: Processor library: fatal error during XML parsing at {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10139: Processor library: processor id {0} used more than once in in {1}

Cause: Processor library: processor id {0} used more than once in in {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10140: Processor library: processor {0} in {1} rejected by available test

Cause: Processor library: processor {0} in {1} rejected by available test

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-10141: Processor library: processor {0} in {1} rejected by licence

Cause: Processor library: processor {0} in {1} rejected by licence

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-10142: Processor library: {0}: info class {1} is not derived from {2}

Cause: Processor library: {0}: info class {1} is not derived from {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10143: Processor library: {0}: failed to create {1} object: {2}

Cause: Processor library: {0}: failed to create {1} object: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10144: Processor library: {0}: cannot load info class {1}

Cause: Processor library: {0}: cannot load info class {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10145: Processor library: {0}: cannot load processor class {1}

Cause: Processor library: {0}: cannot load processor class {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10146: Processor library: processor {0} in {1} is not signed by {2}

Cause: Processor library: processor {0} in {1} is not signed by {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10147: Processor library: {0}: processor class {1} does not have the permission required to inject server object "{2}"

Cause: Processor library: {0}: processor class {1} does not have the permission required to inject server object "{2}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10148: Processor library: {0}: UI class {1} in {2} is not signed by {3}

Cause: Processor library: {0}: UI class {1} in {2} is not signed by {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10149: Processor library: {0}: cannot load UI class {1}

Cause: Processor library: {0}: cannot load UI class {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10150: Processor library: {0}: processor results class {1} in {2} is not signed by {3}

Cause: Processor library: {0}: processor results class {1} in {2} is not signed by {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10151: Processor library: {0}: cannot load results class {1}

Cause: Processor library: {0}: cannot load results class {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10152: Processor library: {0}: processor facade class {1} in {2} is not signed by {3}

Cause: Processor library: {0}: processor facade class {1} in {2} is not signed by {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10153: Processor library: {0}: cannot load facade class {1}, facadeclazz);

Cause: Processor library: {0}: cannot load facade class {1}, facadeclazz);

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10154: Processor library: cannot include both bean attribute and <bean> element in processor {0}

Cause: Processor library: cannot include both bean attribute and <bean> element in processor {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10155: Processor library: reference to invalid bean {1} in processor {0}

Cause: Processor library: reference to invalid bean {1} in processor {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10156: Processor library: reference to unknown bean {1} in processor {0}

Cause: Processor library: reference to unknown bean {1} in processor {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10157: Processor library: skipping processor {0} because of bad bean class

Cause: Processor library: skipping processor {0} because of bad bean class

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10158: Processor library: reading processor {0}: completed with errors

Cause: Processor library: reading processor {0}: completed with errors

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10159: Processor library: invalid structureguid "{0}" in {1}

Cause: Processor library: invalid structureguid "{0}" in {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10160: Processor library: could not verify signers: {0}

Cause: Processor library: could not verify signers: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10161: Processor library: could not verify certificates: {0}

Cause: Processor library: could not verify certificates: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10162: Processor library: invalid X.500 signer name "{0}"

Cause: Processor library: invalid X.500 signer name "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10163: Processor library: failed to load trust data from stream: {0}

Cause: Processor library: failed to load trust data from stream: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10164: Processor library: problem opening jar {0}: {1}

Cause: Processor library: problem opening jar {0}: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10165: Processor library: problem closing jar {0}: {1}

Cause: Processor library: problem closing jar {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10166: Processor library: problem reading data for jar entry {0} in file {1}: {2},

Cause: Processor library: problem reading data for jar entry {0} in file {1}: {2},

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10167: Processor library: unsupported class version for class {0} in file {1}

Cause: Processor library: unsupported class version for class {0} in file {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10168: Processor library: error getting stream for resource {0} from {1}: {2}

Cause: Processor library: error getting stream for resource {0} from {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10169: Processor library: getWidgets: Server indicated cache hit but cache did not return parcel

Cause: Processor library: getWidgets: Server indicated cache hit but cache did not return parcel

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10170: Processor library: problem reading from WidgetsParcel: {0}

Cause: Processor library: problem reading from WidgetsParcel: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10171: Processor library: problem with class in WidgetsParcel: {0})

Cause: Processor library: problem with class in WidgetsParcel: {0})

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10172: Processor library: unhandled error in call to {0}.{1} on {2}: {3}

Cause: Processor library: unhandled error in call to {0}.{1} on {2}: {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10174: Could not verify certificates in "{0}": {1}

Cause: Could not verify certificates in "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10180: Processor library: invalid security mode "{0}" - defaulting to HIGH

Cause: Processor library: invalid security mode "{0}" - defaulting to HIGH

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10181: Processor library: security mode OFF selected - processors will run with no security checks

Cause: Processor library: security mode OFF selected - processors will run with no security checks

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10182: Processor library: security mode {0} selected but Java Security Manager is not present - some processors will be disabled

Cause: Processor library: security mode {0} selected but Java Security Manager is not present - some processors will be disabled

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10183: Processor library: permissions entry in {0} has been removed - processors rejected

Cause: Processor library: permissions entry in {0} has been removed - processors rejected

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10184: Processor library: error reading {0} class bytes from resource {1}: {2}

Cause: Processor library: error reading {0} class bytes from resource {1}: {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10185: Processor library: {0}: processor class {1} is not located in jar file

Cause: Processor library: {0}: processor class {1} is not located in jar file

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10186: Processor library: processor bean class {0} is not located in jar file

Cause: Processor library: processor bean class {0} is not located in jar file

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10187: Processor library: {0}: processor information class {1} is not located in jar file

Cause: Processor library: {0}: processor information class {1} is not located in jar file

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10188: Processor library: {0}: processor UI class {1} is not located in jar file

Cause: Processor library: {0}: processor UI class {1} is not located in jar file

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10189: Processor library: {0}: processor results helper class {1} is not located in jar file

Cause: Processor library: {0}: processor results helper class {1} is not located in jar file

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10190: Processor library: {0}: processor facade class {1} is not located in jar file

Cause: Processor library: {0}: processor facade class {1} is not located in jar file

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10191: Processor library: ignoring extra premissions in {0}: parse error {1}

Cause: Processor library: ignoring extra premissions in {0}: parse error {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10192: Processor library: ignoring extra premissions in {0}: read error {1}

Cause: Processor library: ignoring extra premissions in {0}: read error {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10200: Error storing zip file in database

Cause: Error storing zip file in database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10201: Error deleting zip file from database

Cause: Error deleting zip file from database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10202: Error loading zip {0} from database

Cause: Error loading zip {0} from database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10203: Error listing entries in zip {0}

Cause: Error listing entries in zip {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10204: Error getting entry from zip {0}

Cause: Error getting entry from zip {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10205: Error storing zip file in database

Cause: Error storing zip file in database

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10206: Error in zip servlet

Cause: Error in zip servlet

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10207: During zip transfer: {0} XStore items found in import file: {1}, {2}, {3}

Cause: During zip transfer: {0} XStore items found in import file: {1}, {2}, {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10400: All realms rejected - falling back to internal realm

Cause: All realms rejected - falling back to internal realm

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10401: Bad certificate checker for internal realm: {0}

Cause: Bad certificate checker for internal realm: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10402: Realm {0}: no LDAP servers found in DNS lookup in domain {1}

Cause: Realm {0}: no LDAP servers found in DNS lookup in domain {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10403: Login configuration: bad boolean value "{0}"

Cause: Login configuration: bad boolean value "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10404: Bad sessionlimit value: "{0}"

Cause: Bad sessionlimit value: "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10410: User {0} rejected by filter

Cause: User {0} rejected by filter

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10411: GSS handshake complete: client identity is {0}

Cause: GSS handshake complete: client identity is {0}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-10412: No delegated credentials available for {0}

Cause: No delegated credentials available for {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10413: Failed to get delegated credentials for {0}: {1}

Cause: Failed to get delegated credentials for {0}: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10414: GSS successful, but no realm matching {0}

Cause: GSS successful, but no realm matching {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10415: Identity {0} not found in realm {1}

Cause: Identity {0} not found in realm {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10416: Negotiate: createContext failed: {0}

Cause: Negotiate: createContext failed: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10417: Negotiate: realm not found for identity {0}

Cause: Negotiate: realm not found for identity {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10418: Negotiate: user {0} not found in realm {1}

Cause: Negotiate: user {0} not found in realm {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10419: Negotiate: delegation reported but no credentials returned

Cause: Negotiate: delegation reported but no credentials returned

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10420: Negotiate: delegation reported but credentials failed: {0}

Cause: Negotiate: delegation reported but credentials failed: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10421: Negotiate: error getting user info: {0}

Cause: Negotiate: error getting user info: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10422: Negotiate: context not established after single accept

Cause: Negotiate: context not established after single accept

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10423: Negotiate: accept failed: {0}

Cause: Negotiate: accept failed: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10424: No realm matching identity {0}

Cause: No realm matching identity {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10425: Invalid number "{0}" in session retention

Cause: Invalid number "{0}" in session retention

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10426: Unknown unit in retention setting "{0}"

Cause: Unknown unit in retention setting "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10427: Bad permissions expression "{0}": {1}

Cause: Bad permissions expression "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10428: Session for user {0} rejected by {1} limit

Cause: Session for user {0} rejected by {1} limit

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-10429: Account for {0} blocked due to repeated login failures

Cause: Account for {0} blocked due to repeated login failures

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-10430: LDAP user search failed: {0}

Cause: LDAP user search failed: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10431: Realm {0}: bad maxPwdAge attribute "{1}"

Cause: Realm {0}: bad maxPwdAge attribute "{1}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10432: Realm {0}: error getting maxPwdAge: {1}

Cause: Realm {0}: error getting maxPwdAge: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10433: Realm {0}: unparseable userAccountControl value "{1}"

Cause: Realm {0}: unparseable userAccountControl value "{1}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10434: Realm {0}: unparseable pwdLastSet value "{1}"

Cause: Realm {0}: unparseable pwdLastSet value "{1}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10435: Realm {0}: error getting pwdLastSet for {1}: {2}

Cause: Realm {0}: error getting pwdLastSet for {1}: {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10436: Invalid ADS password policy pattern "{0}": {1}

Cause: Invalid ADS password policy pattern "{0}": {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10437: Bad duration value "{0}" for property {1}

Cause: Bad duration value "{0}" for property {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10438: Realm {0}: user identity {1} not valid

Cause: Realm {0}: user identity {1} not valid

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10439: Realm {0}: user key {1} not valid

Cause: Realm {0}: user key {1} not valid

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10440: Realm {0}: group key {1} not valid

Cause: Realm {0}: group key {1} not valid

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10441: Realm {0}: default user group {1} not found

Cause: Realm {0}: default user group {1} not found

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10442: Realm {0}: no user search filter

Cause: Realm {0}: no user search filter

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10443: Realm {0}: group {1} not found

Cause: Realm {0}: group {1} not found

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10444: Default user group {0} not found

Cause: Default user group {0} not found

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10445: Realm {0}: User {1} ({2}) has a null key and will be ignored

Cause: Realm {0}: User {1} ({2}) has a null key and will be ignored

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10460: Default user group {0} not found

Cause: Default user group {0} not found

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10500: Processor library: {0}: no property corresponding to ''derivedfrom'' attribute "{1}" in input ID {2}

Cause: Processor library: {0}: no property corresponding to ''derivedfrom'' attribute "{1}" in input ID {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10501: Processor library: {0}: error in metric ID {1} expression "{2}": {3}

Cause: Processor library: {0}: error in metric ID {1} expression "{2}": {3}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10502: Processor library: {0}: output name is required if cardinality is n:1

Cause: Processor library: {0}: output name is required if cardinality is n:1

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10503: Processor library: {0}: visibility and metadata attributes may not be used together

Cause: Processor library: {0}: visibility and metadata attributes may not be used together

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10504: Processor library: {0}: output type may not be ''match'' with N:M cardinality

Cause: Processor library: {0}: output type may not be ''match'' with N:M cardinality

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10505: Processor library: {0}: output type may not be ''match'' with more than one input

Cause: Processor library: {0}: output type may not be ''match'' with more than one input

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10506: Processor library: {0}: widget with derived output must have custom info class

Cause: Processor library: {0}: widget with derived output must have custom info class

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10507: Processor library: {0}: widget with user defined output must have custom UI class

Cause: Processor library: {0}: widget with user defined output must have custom UI class

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-10508: Processor library: {0}: output ID {1}: ''multiple'' must be used with type=derived or type=userdefined

Cause: Processor library: {0}: output ID {1}: ''multiple'' must be used with type=derived or type=userdefined

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10509: Processor library: {0}: no output id available for filter

Cause: Processor library: {0}: no output id available for filter

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10510: Processor library: {0}: in filter: no output with id {1}

Cause: Processor library: {0}: in filter: no output with id {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10511: Processor library: {0}: type of output attribute used in filter must be number or string

Cause: Processor library: {0}: type of output attribute used in filter must be number or string

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10512: Processor library: {0}: bad filter value "{1}" for numeric output

Cause: Processor library: {0}: bad filter value "{1}" for numeric output

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10513: Processor library: {0}: ''multiple'' output attribute cannot be used in filter

Cause: Processor library: {0}: ''multiple'' output attribute cannot be used in filter

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10514: Processor library: {0}: child elements not allowed in <options> with ref= attribute

Cause: Processor library: {0}: child elements not allowed in <options> with ref= attribute

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10515: Processor library: {0}: no <options> element matching ref="{0}"

Cause: Processor library: {0}: no <options> element matching ref="{0}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10516: Processor library: {0}: property options allowed with text properties only

Cause: Processor library: {0}: property options allowed with text properties only

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10517: Processor library: {0}: bad default for number property "{0}" ("{1}")

Cause: Processor library: {0}: bad default for number property "{0}" ("{1}")

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10518: Processor library: {0}: bad default for integer property "{0}" ("{1}")

Cause: Processor library: {0}: bad default for integer property "{0}" ("{1}")

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10519: Processor library: {0}: non-editable property {1} should not have an enabledif condition

Cause: Processor library: {0}: non-editable property {1} should not have an enabledif condition

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-10520: Processor library: {0}: property expression "{1}" does not return a number

Cause: Processor library: {0}: property expression "{1}" does not return a number

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10521: Processor library: {0}: error in property expression "{1}": {2}

Cause: Processor library: {0}: error in property expression "{1}": {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10522: Processor library: {0}: range constraint must be used with a numeric property

Cause: Processor library: {0}: range constraint must be used with a numeric property

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10523: Processor library: {0}: length constraint must be used with a text property;

Cause: Processor library: {0}: length constraint must be used with a text property;

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10524: Processor library: {0}: format constraint must be used with a string property

Cause: Processor library: {0}: format constraint must be used with a string property

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10525: Processor library: {0}: source {1} and derivation {2} attributes must match in datum {3}

Cause: Processor library: {0}: source {1} and derivation {2} attributes must match in datum {3}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10526: Processor library: {0}: metric datum type must be specified if source is omitted

Cause: Processor library: {0}: metric datum type must be specified if source is omitted

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10527: Processor library: {0}: bad datum type for {1}

Cause: Processor library: {0}: bad datum type for {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10528: Processor library: {0}: datum type derivation must match source

Cause: Processor library: {0}: datum type derivation must match source

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10529: Processor library: {0}: datum type derivation must match derivation

Cause: Processor library: {0}: datum type derivation must match derivation

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10530: Processor library: {0}: meteoric derivation cannot be used with multiple attributes and multiple sets

Cause: Processor library: {0}: meteoric derivation cannot be used with multiple attributes and multiple sets

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10531: Processor library: {0}: datum {1} with element attribute is not derived from multiple attributes

Cause: Processor library: {0}: datum {1} with element attribute is not derived from multiple attributes

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10532: Processor library: {0}: datum {1} with element attribute must not have a source specifier

Cause: Processor library: {0}: datum {1} with element attribute must not have a source specifier

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10533: Processor library: {0}: destid, source and destype not allowed on datdrill with nested datamatch elements

Cause: Processor library: {0}: destid, source and destype not allowed on datdrill with nested datamatch elements

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10534: Processor library: {0}: metricdrill target {1} does not exist in metric {2}

Cause: Processor library: {0}: metricdrill target {1} does not exist in metric {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10535: Processor library: {0}: dest and source not allowed on metricdrill with nested metricmatch elements

Cause: Processor library: {0}: dest and source not allowed on metricdrill with nested metricmatch elements

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10536: Processor library: {0}: metricdrill view "{1}" does not exist in metric {2}

Cause: Processor library: {0}: metricdrill view "{1}" does not exist in metric {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10537: Processor library: {0}: anonymous drilldown in metric {1} not allowed with default specified

Cause: Processor library: {0}: anonymous drilldown in metric {1} not allowed with default specified

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10538: Processor library: {0}: anonymous drilldown in metric {1} must be first in list

Cause: Processor library: {0}: anonymous drilldown in metric {1} must be first in list

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10539: Processor library: {0}: default drilldown "{1}" not defined in metric {2}

Cause: Processor library: {0}: default drilldown "{1}" not defined in metric {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10540: Processor library: {0}: no input corresponding to {1} in metric {2}

Cause: Processor library: {0}: no input corresponding to {1} in metric {2}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-10541: Processor library: {0}: input:N attribute type may not be an array

Cause: Processor library: {0}: input:N attribute type may not be an array

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-10542: Processor library: {0}: no output corresponding to {1} in metric {2}

Cause: Processor library: {0}: no output corresponding to {1} in metric {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10543: Processor library: {0}: data match input {1} does not exist

Cause: Processor library: {0}: data match input {1} does not exist

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10544: Processor library: {0}: data match output {1} does not exist

Cause: Processor library: {0}: data match output {1} does not exist

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10545: Processor library: {0}: metricdrill dest {1} does not exist in metric {2}

Cause: Processor library: {0}: metricdrill dest {1} does not exist in metric {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10546: Processor library: {0}: ''elementlevel'' attribute must not be present if ''element'' is not present

Cause: Processor library: {0}: ''elementlevel'' attribute must not be present if ''element'' is not present

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10547: Processor library: {0}: metric {1}: datum {2} element refers to itself

Cause: Processor library: {0}: metric {1}: datum {2} element refers to itself

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10548: Processor library: {0}: metric {1}: no matching datum element {2}

Cause: Processor library: {0}: metric {1}: no matching datum element {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10549: Processor library: {0}: default view {1} cannot contain an element reference

Cause: Processor library: {0}: default view {1} cannot contain an element reference

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10550: Processor library: {0}: metric {1} does not contain datum {2} used in parent element

Cause: Processor library: {0}: metric {1} does not contain datum {2} used in parent element

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10551: Processor library: {0}: no metrics have drilldowns for element reference {1}

Cause: Processor library: {0}: no metrics have drilldowns for element reference {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10552: Processor library: {0}: element reference datum {1} in metric {2} must be integer

Cause: Processor library: {0}: element reference datum {1} in metric {2} must be integer

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10553: Processor library: {0}: <fixedrecords> element not allowed with variable format metric {1}

Cause: Processor library: {0}: <fixedrecords> element not allowed with variable format metric {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10554: Processor library: {0}: nested <record> elements and outputid attribute not allowed with fromspigots=true

Cause: Processor library: {0}: nested <record> elements and outputid attribute not allowed with fromspigots=true

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10555: Processor library: {0}: equals=false filters are not supported with fromspigots=true

Cause: Processor library: {0}: equals=false filters are not supported with fromspigots=true

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10556: Processor library: {0}: filters used with fromspigots=true must use string attributes

Cause: Processor library: {0}: filters used with fromspigots=true must use string attributes

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10557: Processor library: {0}: must not use both nested <filter> and filter attribute on <record>

Cause: Processor library: {0}: must not use both nested <filter> and filter attribute on <record>

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10558: Processor library: {0}: <summaryrecords> element not allowed with variable format metric {1}

Cause: Processor library: {0}: <summaryrecords> element not allowed with variable format metric {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10559: Processor library: {0}: unknown metric {1} in <summaryrecords> in metric {2}

Cause: Processor library: {0}: unknown metric {1} in <summaryrecords> in metric {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10560: Processor library: {0}: metric with <summaryrecords> may not have additional data items

Cause: Processor library: {0}: metric with <summaryrecords> may not have additional data items

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10561: Processor library: {0}: <variablerecords> element not allowed with fixed format metric {1}

Cause: Processor library: {0}: <variablerecords> element not allowed with fixed format metric {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10562: Processor library: {0}: in <variablerecords> one of keyval and key must be used but not both

Cause: Processor library: {0}: in <variablerecords> one of keyval and key must be used but not both

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10563: Processor library: {0}: <variablerecords> input keyval must be of string type

Cause: Processor library: {0}: <variablerecords> input keyval must be of string type

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10564: Processor library: {0}: <variablerecords> output keyval must be of string type

Cause: Processor library: {0}: <variablerecords> output keyval must be of string type

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10565: Processor library: {0}: <variablerecords> key datum {1} does not exist in metric {2}

Cause: Processor library: {0}: <variablerecords> key datum {1} does not exist in metric {2}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10566: Processor library: {0}: variablerecords input:N reference must allow single attribute only

Cause: Processor library: {0}: variablerecords input:N reference must allow single attribute only

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10567: Processor library: {0}: <variablerecords>: source attribute omitted on datum "{1}" in metric {2}

Cause: Processor library: {0}: <variablerecords>: source attribute omitted on datum "{1}" in metric {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10568: Processor library: {0}: view "{1}" in default list does not exist

Cause: Processor library: {0}: view "{1}" in default list does not exist

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10569: Processor library: {0}: view "{1}" repeated in default list

Cause: Processor library: {0}: view "{1}" repeated in default list

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10570: Processor library: {0}: unknown metric {1} used in view {2}

Cause: Processor library: {0}: unknown metric {1} used in view {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10571: Processor library: {0}: metricid is required on variable type view

Cause: Processor library: {0}: metricid is required on variable type view

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10572: Processor library: {0}: unknown column "{1}" in sortby string "{2}"

Cause: Processor library: {0}: unknown column "{1}" in sortby string "{2}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10573: Processor library: {0}: inconsistent metric & view types in {1} and metric {2}

Cause: Processor library: {0}: inconsistent metric & view types in {1} and metric {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10574: Processor library: {0}: no metric defined as source for drilldown "{1}"

Cause: Processor library: {0}: no metric defined as source for drilldown "{1}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10575: Processor library: {0}: drilldown "{1}" does not exist for metric {2} in view

Cause: Processor library: {0}: drilldown "{1}" does not exist for metric {2} in view

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10576: Processor library: {0}: invalid reference "{1}" in view column

Cause: Processor library: {0}: invalid reference "{1}" in view column

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10577: Processor library: {0}: type of "{1}" column must be string

Cause: Processor library: {0}: type of "{1}" column must be string

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10578: Processor library: {0}: selector is not allowed in "{1}" column

Cause: Processor library: {0}: selector is not allowed in "{1}" column

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10579: Processor library: {0}: metric definition missing for datum="{1}" column in view

Cause: Processor library: {0}: metric definition missing for datum="{1}" column in view

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10580: Processor library: {0}: no global columnset named "{1}"

Cause: Processor library: {0}: no global columnset named "{1}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10581: Processor library: {0}: unknown datum name "{1}"

Cause: Processor library: {0}: unknown datum name "{1}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10582: Processor library: {0}: unknown metric {1} on view

Cause: Processor library: {0}: unknown metric {1} on view

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10600: Error creating group table for match process, process id {0} processor num {1} : {2}

Cause: Error creating group table for match process, process id {0} processor num {1} : {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10601: New decision Id: {0} has an unrecognised match type and will be ignored. The allowed match types are {match, nomatch, possiblematch, pending}

Cause: New decision Id: {0} has an unrecognised match type and will be ignored. The allowed match types are {match, nomatch, possiblematch, pending}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10602: New decision Id: {0} replaces a default decision but has a different Match Type. This is not allowed and so will be ignored

Cause: New decision Id: {0} replaces a default decision but has a different Match Type. This is not allowed and so will be ignored

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10603: Reference to unknown formal attribute in cluster "{0}"

Cause: Reference to unknown formal attribute in cluster "{0}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10604: Reference to unknown source attribute in cluster "{0}"

Cause: Reference to unknown source attribute in cluster "{0}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10605: A problem occurred adding a formal attribute to a cluster configuration: {0}

Cause: A problem occurred adding a formal attribute to a cluster configuration: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10606: A problem occurred loading result band configuration: {0}

Cause: A problem occurred loading result band configuration: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10607: A problem occurred loading decisions output attribute configuration: {0}

Cause: A problem occurred loading decisions output attribute configuration: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10608: Formal attribute {0}.{1} contains mapping from unknown source object {2}

Cause: Formal attribute {0}.{1} contains mapping from unknown source object {2}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10609: A problem occurred processing source attribute: {0}

Cause: A problem occurred processing source attribute: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10610: A problem occurred loading groups output attribute configuration: {0}

Cause: A problem occurred loading groups output attribute configuration: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10611: A problem occurred loading identifier configuration: {0}

Cause: A problem occurred loading identifier configuration: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10612: A problem occurred loading input configuration: {0}

Cause: A problem occurred loading input configuration: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10613: A problem occurred loading merged output configuration: {0}

Cause: A problem occurred loading merged output configuration: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10614: A problem occurred loading merged output configuration: {0}

Cause: A problem occurred loading merged output configuration: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10615: A problem occurred loading input configuration in persistent input loader: {0}

Cause: A problem occurred loading input configuration in persistent input loader: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10616: A problem occurred loading relationship output configuration: {0}

Cause: A problem occurred loading relationship output configuration: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10617: A problem occurred loading rule configuration: {0}

Cause: A problem occurred loading rule configuration: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10618: Merged attribute "{0}" contains reference to unknown source attribute "{1}"

Cause: Merged attribute "{0}" contains reference to unknown source attribute "{1}"

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10619: A problem occurred loading a transformation set configuration: {0}

Cause: A problem occurred loading a transformation set configuration: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10620: Unable to create new cluster: {0}

Cause: Unable to create new cluster: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10621: Unable to add formal attribute: {0}

Cause: Unable to add formal attribute: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10622: Unable to add transformation to attribute: {0}

Cause: Unable to add transformation to attribute: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10623: Transformation lists are not equivalent

Cause: Transformation lists are not equivalent

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10624: Unable to move transformation up: {0}

Cause: Unable to move transformation up: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10625: Unable to move transformation down: {0}

Cause: Unable to move transformation down: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10626: Unable to replace old attribute list with new one: {0}

Cause: Unable to replace old attribute list with new one: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10627: Unable to swap attributes: {0}

Cause: Unable to swap attributes: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10628: Transformation lists are not equivalent

Cause: Transformation lists are not equivalent

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10629: Rule lists are not equivalent

Cause: Rule lists are not equivalent

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10630: Unable to automatically map identifiers: {0}

Cause: Unable to automatically map identifiers: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10631: A problem occurred mapping a source attribute to a formal attribute instance: {0}

Cause: A problem occurred mapping a source attribute to a formal attribute instance: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10632: A problem occurred adding an identifier: {0}

Cause: A problem occurred adding an identifier: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10633: A problem occurred adding multiple identifiers: {0}

Cause: A problem occurred adding multiple identifiers: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10634: A problem occurred reordering attributes: {0}

Cause: A problem occurred reordering attributes: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10635: A problem occurred when setting up the match process inputs: {0}

Cause: A problem occurred when setting up the match process inputs: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10636: A problem occurred updating persistent inputs with new information: {0}

Cause: A problem occurred updating persistent inputs with new information: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10637: A problem occurred parsing the results comparison default element: {0}

Cause: A problem occurred parsing the results comparison default element: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10638: Unable to parse attribute XML when reading identifier definition: {0}

Cause: Unable to parse attribute XML when reading identifier definition: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10639: Unable to parse identifier definition XML: {0}

Cause: Unable to parse identifier definition XML: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10640: Identifier definition '{0}' has no formal attributes

Cause: Identifier definition '{0}' has no formal attributes

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10641: Import Match Library: Match library file '{0}' not found in '{1}'

Cause: Import Match Library: Match library file '{0}' not found in '{1}'

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10642: Import Match Library: Match Library: In file '{0}': {1}

Cause: Import Match Library: Match Library: In file '{0}': {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10643: Import Match Library Mappings: Match library file '{0}' not found in '{1}'

Cause: Import Match Library Mappings: Match library file '{0}' not found in '{1}'

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10644: Import Match Library Mappings: Match Library: In file '{0}': {1}

Cause: Import Match Library Mappings: Match Library: In file '{0}': {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10645: Parse Match Library: Unable to parse identifier definition XML: {0}

Cause: Parse Match Library: Unable to parse identifier definition XML: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10646: Parse Match Library: Unable to parse comparison default result XML: {0}

Cause: Parse Match Library: Unable to parse comparison default result XML: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10647: Parse Match Library Mappings: Unable to parse identifier comparison mapping XML: {0}

Cause: Parse Match Library Mappings: Unable to parse identifier comparison mapping XML: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10648: The match configuration is null.

Cause: The match configuration is null.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-10649: The match configuration is null, unable to obtain a process.

Cause: The match configuration is null, unable to obtain a process.

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10650: Unable to load lookup information for checking dependencies : {0}

Cause: Unable to load lookup information for checking dependencies : {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10651: Match encountered a record from an unknown connection {0}

Cause: Match encountered a record from an unknown connection {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10652: Match encountered a message from an unknown connection {0} on port {1}

Cause: Match encountered a message from an unknown connection {0} on port {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-10653: A failure occurred in the mission manager: {0}

Cause: A failure occurred in the mission manager: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10654: An error occurred copying table

Cause: An error occurred copying table

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10655: Unable to determine match status for decision: {0}

Cause: Unable to determine match status for decision: {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10656: Using record count of 0 due to error: {0}

Cause: Using record count of 0 due to error: {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10657: Unable to read case issues:

Cause: Unable to read case issues:

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10658: Error creating table {0} for writing relationship comments

Cause: Error creating table {0} for writing relationship comments

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10659: Error creating table {0} for writing relationship decisions

Cause: Error creating table {0} for writing relationship decisions

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10660: Error creating the merged comment table {0}

Cause: Error creating the merged comment table {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10661: Error creating the merged decision table {0}

Cause: Error creating the merged decision table {0}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10662: Error creating the merged decision details table {0}

Cause: Error creating the merged decision details table {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10663: Error creating the merged output status table {0}

Cause: Error creating the merged output status table {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10664: Unable to read case issues:

Cause: Unable to read case issues:

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10665: Error creating merge decision table {0}

Cause: Error creating merge decision table {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10666: Error creating merge decision detail table {0}

Cause: Error creating merge decision detail table {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10667: Error creating merge comment table {0}

Cause: Error creating merge comment table {0}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10668: Unable to read case issues:

Cause: Unable to read case issues:

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10670: Error deleting temporary tables: {0}

Cause: Error deleting temporary tables:

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10671: Unknown Calculation Gadget: {0}

Cause: Unknown Calculation Gadget

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10700: {0} Error writing summary metric

Cause: {0} Error writing summary metric

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10701: {0} Patternmap resource missing

Cause: {0} Patternmap resource missing

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10702: {0} Bad preprocess parameter "{1}"

Cause: {0} Bad preprocess parameter "{1}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10703: {0} Error writing counter metric

Cause: {0} Error writing counter metric

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10704: {0} Invalid number format "{1}"

Cause: {0} Invalid number format "{1}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10705: {0} Invalid date format "{1}"

Cause: {0} Invalid date format "{1}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10706: {0} Unknown postprocess option {1}

Cause: {0} Unknown postprocess option {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10707: {0} Expression missing

Cause: {0} Expression missing

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10708: {0} Expression error: logic check expression is not conditional

Cause: {0} Expression error: logic check expression is not conditional

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10709: {0} Expression error: {1}

Cause: {0} Expression error: {1}

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10710: {0} Invalid band minimum "{1}"

Cause: {0} Invalid band minimum "{1}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10711: {0} Invalid format "{1}"

Cause: {0} Invalid format "{1}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10712: Regex Match expression is invalid "{0}"

Cause: Regex Match expression is invalid "{0}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10713: {0} The regular expression entered is invalid: {1}

Cause: {0} The regular expression entered is invalid: {1}

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10714: {0} Resource {1} contains an invalid pattern "{2}"

Cause: {0} Resource {1} contains an invalid pattern "{2}"

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10715: {0} {1} resource missing

Cause: {0} {1} resource missing

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10716: {0} Resource query error

Cause: {0} Resource query error

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10717: {0} Resource count error

Cause: {0} Resource count error

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10718: Issued non blocking call - waiting

Cause: Issued non blocking call - waiting

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-10719: Wait complete

Cause: Wait complete

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Other

EDQ-10720: Failed to get properties from server

Cause: Failed to get properties from server

Action: Correct the error and retry, contact support if problem persists
Level: 1

Type: ERROR

Impact: Other

EDQ-10721: {0}: invalid regex "{1}" in input

Cause: {0}: invalid regex "{1}" in input

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

EDQ-10722: {0}: invalid regex "{1}" in input - further warnings suppressed from this processor

Cause: {0}: invalid regex "{1}" in input - further warnings suppressed from this processor

Action: Monitor, contact support if problem persists
Level: 1

Type: WARNING

Impact: Other

16 ES-07001 to ES-07017

ES-07001: Error while starting the hosted FTP server: {0}.

Cause: An error occurred while starting the hosted FTP server.

Action: Check the FTP server configuration in metadata repository. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: PROCESS

ES-07002: Initialization of hosted server {0} failed.

Cause: An error occurred while initializing hosted server.

Action: Check the FTP/SSH-FTP server configuration in metadata repository.
Level: CRITICAL

Type: ERROR

Impact: PROCESS

ES-07003: Error while starting the server instance {0} on configured port {1}.

Cause: An error occurred while starting hosted server on a configured port. Check if the port is used by any other process.

Action: Check the ports definition in metadata repository and database config parameters. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: PROCESS

ES-07004: Error while starting the hosted SSH-FTP server instance: {0}.

Cause: An error occurred while starting hosted SSH-FTP server.

Action: Check the SSH-FTP server configuration in metadata repository. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: PROCESS

ES-07005: The operation {0} is not implemented by hosted server {1}.

Cause: This operation is not supported or implemented by the hosted server.

Action: This operation is not supported or implemented by the hosted server. No action required.
Level: LOW

Type: ERROR

Impact: PROCESS

ES-07006: Error while stopping the hosted SSH-FTP server instance.

Cause: An error occurred while stopping hosted SSH-FTP server.

Action: Check the SSH-FTP server configuration in metadata repository. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: PROCESS

ES-07007: Error while stopping the hosted FTP server instance.

Cause: An error occurred while stopping hosted FTP server.

Action: Check the SSH-FTP server configuration in metadata repository. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: PROCESS

ES-07008: Unsupported configuration parameter/type for hosted servers.

Cause: Unsupported configuration parameter for hosted servers.

Action: Check the FTP/SSH-FTP server configuration in metadata repository. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: CONFIGURATION

ES-07009: Problem with hosted server configuration.

Cause: Problem found with hosted server configuration.

Action: Check the root directory and port assigned to the hosted server. For FTP over SSL and SSH Servers, verify that all the required keys are configured. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: CONFIGURATION

ES-07010: Error while starting the hosted SSH-FTP server instance. SSH-FTP server can not start without a valid a host key.

Cause: No valid private key (SSH2 RSA/DSA) is configured.

Action: Check the SSH-FTP server configuration in metadata repository and make sure that a valid host key is configured. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: CONFIGURATION

ES-07011: Exception while creating FTP SSL Configuration: {0}.

Cause: Invalid FTP SSL configuration.

Action: Check the Keystore configuration. Verify that all the required keys are configured. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: CONFIGURATION

ES-07012: At least one FTP listener must be defined.

Cause: Invalid FTP configuration.

Action: Check the FTP configuration. At least one FTP listener must be defined.
Level: CRITICAL

Type: ERROR

Impact: CONFIGURATION

ES-07014: BC (Bouncy Castle) is not registered as a security provider.

Cause: BC jar files are not available in the classpath.

Action: Add Bouncy Castle jar files to the classpath. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: PROCESS

ES-07015: SSH-FTP Server can not start without a configured authentication type.

Cause: SSH-FTP Server cannot start without a configured authentication type.

Action: Check the SSH FTP server configuration. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: CONFIGURATION

ES-07016: Authorization failed. Cause: {3} Resource: {0}, Action: {1}, Server: {2}.

Cause: Authorization failed for Resource.

Action: Check and assign correct Access Privileges for the resources. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: PROCESS

ES-07017: Crypto JsafeJCE is not registered as a security provider.

Cause: Crypto JsafeJCE jar files are not available in the classpath.

Action: Add Crypto JsafeJCE jar files to the classpath. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: PROCESS

17 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-00503: MetadataServiceHandle is null.

Cause: The ESS metadata service handle is null.

Action: Specify a valid ESS metadata service handle.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00800: Error attempting notification for SQL job request {0}.

Cause: Failed to create notification that SQL job executable completed.

Action: Review the log file to determine the nature of the problem.
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-01021: Failed to create DMS context for new request.

Cause: Failed to create a DMS context for a new request.

Action: Review any linked exceptions to identify the root cause of the error.
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-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-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: WARNING

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 occurred 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: Query for application registration information failed.

Cause: An error occurred while querying the application 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}, metadata {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-01170: Failed to retrieve runtime store information.

Cause: An error occurred attempting to retrieve runtime store information.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01171: Runtime store compatibility information is not available.

Cause: Unable to retrieve Enterprise Scheduler Service runtime store compatibility information.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

ESS-01172: Runtime store compatibility check failed; mid-tier check version: {0}, runtime store version: {1}, schema name: {2}

Cause: The Enterprise Scheduler Service mid-tier is not compatible with the database runtime store.

Action: Upgrade database schema or mid-tier to be compatible
Level: 1

Type: ERROR

Impact: Other

ESS-01173: Runtime store status check failed; runtime store status: {0}, schema name: {1}

Cause: The Enterprise Scheduler Service runtime store is not valid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

ESS-01174: Runtime store compatibility check failed; mid-tier check version: {0}, runtime store version: {1}, schema name: {2}. Check disabled, allowing operation to continue.

Cause: The Enterprise Scheduler Service mid-tier is not compatible with the database runtime store.

Action: Upgrade database schema or mid-tier to be compatible.
Level: 1

Type: WARNING

Impact: Other

ESS-01175: Runtime store status check failed; runtime store status: {0}, schema name: {1}. Check disabled, allowing operation to continue.

Cause: The Enterprise Scheduler Service runtime store is not valid.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

ESS-01176: Triggers are not supported.

Cause: A trigger was specified to the metadata service or when submitting a request.

Action: Do not create triggers and specify a null value for any trigger parameter.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01177: Failed to delete job incompatibility references for request {0} from runtime store.

Cause: An error occurred attempting to remove job incompatibility references.

Action: Review the causeBy exception chain to determine the specific failure.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01178: Query for server coordination information failed.

Cause: An error occurred while querying the server coordination table.

Action: Check that database is running and data source is correct.
Level: 1

Type: WARNING

Impact: Other

ESS-01179: Schedule includes explicit times that are before the start time.

Cause: Attempted to submit a reuqest with Adhoc schedule that contains time that are before the current time.

Action: Retry the operation after modifying the times in Adhoc Schedule.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01180: Unable to determine database type.

Cause: Unable to determine the database type being used for 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-01181: Failed to delete information for request {0}.

Cause: An error occurred attempting to remove request information from 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-01182: Failed to update wait queue element for request {0}.

Cause: An error occurred attempting to update 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-01183: Wait queue operation failed.

Cause: An error occurred attempting a wait queue operation.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01184: Update of server coordination information failed.

Cause: An error occurred attempting to update the server coordination table.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01185: Failed to get async request information for request {0}.

Cause: Failed to retrieve information for web service asynchronous callback.

Action: Check the logs.
Level: 1

Type: WARNING

Impact: Other

ESS-01186: Failed to update async request information for message {0}.

Cause: Failed to update information for web service asynchronous callback.

Action: Check the logs.
Level: 1

Type: WARNING

Impact: Other

ESS-01187: Failed to add or modify attribute {0} of namespace {1} for request {2}.

Cause: An error occurred attempting to modify request attribute information.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01188: Failed to access attribute {0} of namespace {1} for request {2}.

Cause: An error occurred attempting to access request attribute information.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01189: Failed to delete attribute {0} of namespace {1} for request {2}.

Cause: An error occurred attempting to remove request attribute information.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01190: Value for attribute {0} of namespace {1} has an invalid data type: {2}.

Cause: The value for a request attribute has an unsupported data type.

Action: Specify a value which has a supported data type for the attribute.
Level: 1

Type: ERROR

Impact: Other

ESS-01191: Failed to get storable value for attribute {0} of namespace {1}.

Cause: An error occurred converting a request attribute value to its stored representation.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-01192: Failed to get typed value for attribute {0} of namespace {1} for data type {2}.

Cause: An error occurred converting a request attribute value from its stored representation to a typed value.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-01193: Value for attribute {0} of namespace {1} has data type {2} instead of the expected data type {3}

Cause: Data type for request attribute value does not match the type already estabished for that attribute.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-01195: Error attempting to access parameter, {0}, for request {1}.

Cause: An error occurred attempting to access request parameter information.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

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-01290: Invalid logical cluster name value {0}.

Cause: An invalid logical cluster name was specified.

Action: Specify a valid logical cluster name.
Level: 1

Type: ERROR

Impact: Other

ESS-01291: A logical cluster name is not allowed to contain the character '.'.

Cause: An invalid logical cluster name was specified.

Action: Specify a valid logical cluster name.
Level: 1

Type: ERROR

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-01323: Invalid content open options for request {0} content category {1}, content name {2}.

Cause: The content open options are invalid.

Action: Ensure that the content open options contain a single operation, and if applicable, options that are consistent with that operation.
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-01608: Error occurred while processing request {0} by request dispatcher.

Cause: Failed to perform dispatch proccessing for the specified request.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: ERROR

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-01970: Error during request purge processing.

Cause: An error was encountered during purge of request data.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01971: Error while purging request data from table {0} for request {1}.

Cause: An error was encountered during purge of request data from the specified table.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01972: Error during request purge processing for session {0}.

Cause: An error was encountered during purge of request data.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01973: Error while purging request data from table {0} for session {1}.

Cause: An error was encountered during purge of request data from the specified table.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01974: Error while purging request data from table {0} for request {1}, session {2}.

Cause: An error was encountered during purge of request data from the specified table.

Action: Review the log file for attached exceptions to determine the nature of the problem.
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 operation.

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-01995: Failed to create delete session.

Cause: Failed to initialize delete session used for request data delete or purge.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01996: Failed to lock delete session table.

Cause: Failed to lock delete session table used for request data delete or purge.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01997: Failed to access delete session information.

Cause: Failed to access delete session information used for request data delete or purge.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01998: Runtime store operation failed for delete session {0}.

Cause: Runtime store error occurred during delete session operation.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

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 identity store.

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} that job {1} runs as is not a valid entry in the identity store.

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-02008: Invalid value {0} specified for FADataSecurityPolicyOverrides property in ess-config. Continuing permission checks using default FND policy.

Cause: Invalid value specified for FADataSecurityPolicyOverrides property in ess-config

Action: Use a supported value.
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-02221: Invalid web service request message {0} for getCompletionStatus operation.

Cause: The web service request to getCompletionStatus was invalid.

Action: Check the attached exceptions and fix the web service request.
Level: 1

Type: WARNING

Impact: Other

ESS-03000: Metadata name cannot contain character '/'

Cause: Invalid metdata type name

Action: Provide a valid metadata name
Level: 1

Type: ERROR

Impact: Other

ESS-03001: Both explicit date and recurrence cannot be null.

Cause: Both explicit date and recurrence cannot be null.

Action: Provide explicit date or recurrence.
Level: 1

Type: ERROR

Impact: Other

ESS-03002: ExclusionDefinition must contain at least one exclusion

Cause: ExclusionDefinition is empty

Action: Include atleast one exclusion in ExclusionDefinition.
Level: 1

Type: WARNING

Impact: Other

ESS-03003: Incompatibility already has an entity for job definition:{0}

Cause: Incompatibility already has the corresponding job definition.

Action: Don't add the job definition to the Incompatibility.
Level: 1

Type: WARNING

Impact: Other

ESS-03004: Incompatibility defined for a single entity must be self-incompatible on that entity.

Cause: Incompatibility defined for a single entity must be self-incompatible on that entity

Action: A valid incompatibility definition must have at least two entities or one self-incompatible entity
Level: 1

Type: WARNING

Impact: Other

ESS-03005: Identifier not specified for incompatibility entity.

Cause: Identifier not specified for incompatibility entity.

Action: Specify identifier for incompatibility entity.
Level: 1

Type: WARNING

Impact: Other

ESS-03006: Property not specified for an entity of a {0} incompatibility

Cause: Property not specified for Incompatibility entity.

Action: Specify property for Incompatibility entity.
Level: 1

Type: WARNING

Impact: Other

ESS-03007: Property {0} is defined as read-only in the JobType definition.

Cause: Read-only property is defined in JobType definition

Action: Make sure that no read-only property is specified for Jobtype Definition.
Level: 1

Type: WARNING

Impact: Other

ESS-03008: Unable to convert steps to XML Document

Cause: Conversion of JobSet's JobSetStep objects to an XML Document failed

Action: Internal error
Level: 1

Type: ERROR

Impact: Other

ESS-03009: Failed to validate Jobset/JobsetSteps document against the schema :{0}

Cause: Failed to validate Jobset/JobsetSteps document against the schema

Action: Internal error
Level: 1

Type: ERROR

Impact: Other

ESS-03010: Unable to convert XML steps to objects

Cause: Unable to convert XML steps to objects

Action: Internal error
Level: 1

Type: ERROR

Impact: Other

ESS-03011: First step must be defined for serial job set.

Cause: Jobset has steps, but the first step is not defined.

Action: First step must be defined for serial jobset.
Level: 1

Type: WARNING

Impact: Other

ESS-03012: First step id does not specify a defined step:{0}

Cause: First step id of Jobset does not specify a defined step

Action: First step must be a defined one for serial jobset.
Level: 1

Type: WARNING

Impact: Other

ESS-03013: Invalid link step id for {0}

Cause: Invalid link step id

Action: Check that step links are valid step ids..
Level: 1

Type: WARNING

Impact: Other

ESS-03014: Jobset has no steps.

Cause: Jobset has no steps

Action: Ensure Jobset have steps
Level: 1

Type: WARNING

Impact: Other

ESS-03015: Invalid Serial JobSet:loops are not allowed. See step {0}

Cause: Invalid Serial JobSet:loops are not allowed

Action: Avoid loops in serial Jobset
Level: 1

Type: ERROR

Impact: Other

ESS-03016: Step already exists:{0}

Cause: Step already exists in Jobset

Action: Avoid adding duplicate step
Level: 1

Type: WARNING

Impact: Other

ESS-03020: Both FREQUENCY and ICAL Expression cannot be null

Cause: Both FREQUENCY and ICAL Expression cannot be null

Action: Specify either Frequency or Ical expression.
Level: 1

Type: ERROR

Impact: Other

ESS-03021: Cannot have start date after end date

Cause: Cannot have start date after end date

Action: Correct the start or end date
Level: 1

Type: WARNING

Impact: Other

ESS-03022: Cannot specify Recurrence Fields WEEK_OF_MONTH without DAY_OF_WEEK

Cause: Cannot specify recurrence fields WEEK_OF_MONTH without DAY_OF_WEEK

Action: Given weeks of month, days of week is must.
Level: 1

Type: WARNING

Impact: Other

ESS-03023: Cannot specify MONTH_OF_YEAR for MONTHLY frequency. MONTH_OF_YEAR can be specified for YEARLY frequency.

Cause: Cannot specify recurrence fields MONTH_OF_YEAR for MONTHLY frequency.

Action: Month of year can be specified for yearly frequency.
Level: 1

Type: WARNING

Impact: Other

ESS-03024: Cannot specify MONTH_OF_YEAR, WEEK_OF_MONTH or DAY_OF_MONTH for WEEKLY frequency

Cause: Cannot specify recurrence fields MONTH_OF_YEAR, WEEK_OF_MONTH or DAY_OF_MONTH for WEEKLY frequency

Action: Other fields cannot have bigger scope then frequency
Level: 1

Type: ERROR

Impact: Other

ESS-03025: Only TIME_OF_DAY field can be specified with DAILY frequency

Cause: Only time of day field can be specified with daily frequency.

Action: Only time of day field can be specified with daily frequency.
Level: 1

Type: ERROR

Impact: Other

ESS-03026: RecurrenceFields cannot be specified with 'HOURLY', 'MINUTELY' or 'SECONDLY' frequency

Cause: Recurrence fields cannot be specified with HOURLY, MINUTELY or SECONDLY frequency

Action: Recurrence fields cannot be specified with HOURLY, MINUTELY or SECONDLY frequency
Level: 1

Type: WARNING

Impact: Other

ESS-03027: RecurrenceFields have invalid Month, Date combinations.

Cause: Recurrence fields have invalid Month, Date combinations.

Action: Specify correct month, date combinations.
Level: 1

Type: WARNING

Impact: Other

ESS-03028: RecurrenceSet can''t have more than {0} recurrences

Cause: RecurrenceSet cannot have more than 5 recurrences

Action: Reduce the number of recurrences
Level: 1

Type: WARNING

Impact: Other

ESS-03029: Event filters should have no more than one operator

Cause: Event filters have more than one operator.

Action: Correct Event filters to have no more than one operator.
Level: 1

Type: ERROR

Impact: Other

ESS-03030: {0} and {1} are the only supported fields for event filters

Cause: EventType and EventName are the only supported fields for event filters.

Action: EventType and EventName are the only supported fields for event filters.
Level: 1

Type: WARNING

Impact: Other

ESS-03031: Work Assignment must specify at least one Workshift

Cause: Work Assignment has no Workshift.

Action: Work Assignment must specify at least one Workshift.
Level: 1

Type: WARNING

Impact: Other

ESS-03033: Illegal value provided for Actions in parameter

Cause: Illegal value provided for Metadata permission actions in parameter.

Action: Illegal value provided for Metadata permission actions in parameter.
Level: 1

Type: ERROR

Impact: Other

ESS-03034: MetadataPermissionStrings parameter cannot be null.

Cause: MetadataPermissionStrings parameter cannot be null or empty.

Action: Specify non-empty metadata permission strings
Level: 1

Type: ERROR

Impact: Other

ESS-03035: Actions parameter cannot be null.

Cause: Actions parameter cannot be null or empty.

Action: Actions parameter cannot be null or empty.
Level: 1

Type: WARNING

Impact: Other

ESS-03036: Failed to commit changes and close service handle. Referential Integrity violation detected. Referencing objects exist for the object(s) being deleted.

Cause: Deletion of object not possible as it is referenced by some other object

Action: Check the dependent objects before deletion.
Level: 1

Type: WARNING

Impact: Other

ESS-03037: Invalid options due to missing operation: {0}

Cause: Invalid options.

Action: Provide valid options.
Level: 1

Type: WARNING

Impact: Other

ESS-03038: Invalid options for Read operation: {0}

Cause: Invalid options for Read operation.

Action: Specify correct options for read operation.
Level: 1

Type: WARNING

Impact: Other

ESS-03039: Invalid options for Write operation: {0}

Cause: Invalid options for Write operation.

Action: Specify correct options for write operation.
Level: 1

Type: WARNING

Impact: Other

ESS-03040: Invalid options for Import operation: {0}

Cause: Invalid options for Import operation.

Action: Specify correct options for import operation
Level: 1

Type: WARNING

Impact: Other

ESS-03041: Invalid options for Log content: {0}

Cause: Invalid options for Log content.

Action: Specify correct options for log content.
Level: 1

Type: WARNING

Impact: Other

ESS-03042: Definition is required

Cause: Job or jobset definition Id is missing

Action: Job or jobset definition Id is required
Level: 1

Type: ERROR

Impact: Other

ESS-03043: Incompatibility definition, {0}, from runtime store is {1} incompatibility type. Expected type is {2}

Cause: Incompatibility type mismatch between metadata store and runtime store for the request

Action: There should be no mismatch. Internal error
Level: 1

Type: ERROR

Impact: Other

ESS-03044: Incompatibility definition, {0},from runtime store does not contain an entity for {1}

Cause: Incompatibility definition from runtime store does not contain an entity for Job/Jobset

Action: Entity must be present in Incompatibility definition. Internal error.
Level: 1

Type: ERROR

Impact: Other

ESS-03045: Map parameter cannot be null.

Cause: Config properties map is null

Action: Config properties map cannot be null
Level: 1

Type: ERROR

Impact: Other

ESS-03046: Application parameter cannot be null.

Cause: Application parameter provided to fetch config properties is null

Action: Provide non null application name.
Level: 1

Type: ERROR

Impact: Other

ESS-03047: PropertyType enum cannot be null.

Cause: PropertyType enum is null.

Action: PropertyType enum cannot be null.
Level: 1

Type: ERROR

Impact: Other

ESS-03048: PropertyName parameter cannot be null.

Cause: PropertyName parameter is null.

Action: PropertyName parameter cannot be null.
Level: 1

Type: ERROR

Impact: Other

ESS-03049: PropertyValue parameter cannot be null.

Cause: PropertyValue parameter is null.

Action: PropertyValue parameter cannot be null.
Level: 1

Type: WARNING

Impact: Other

ESS-03050: Trigger definition cannot be null.

Cause: Trigger definition is null.

Action: Trigger definition cannot be null.
Level: 1

Type: ERROR

Impact: Other

ESS-03051: No specialization in configured bindings for {0}

Cause: No specialization in configured bindings.

Action: Specify specialization in configured bindings.
Level: 1

Type: WARNING

Impact: Other

ESS-03052: {0} is not bound on this instance

Cause: Work Assignment not bound on this instance.

Action: Work Assignment not bound on this instance.
Level: 1

Type: WARNING

Impact: Other

ESS-03053: Request parameters cannot be null.

Cause: Request parameters are null.

Action: Request parameters cannot be null.
Level: 1

Type: ERROR

Impact: Other

ESS-03054: Illegal value provided for Actions in parameter.

Cause: Illegal value provided for Actions in parameter.

Action: Provide proper values for Actions in parameter.
Level: 1

Type: ERROR

Impact: Other

ESS-03055: Invalid binding mode: name={0},exclusiveMode={1}

Cause: Invalid binding mode.

Action: Invalid binding mode.
Level: 1

Type: ERROR

Impact: Other

ESS-03056: Filter parameters with DATETIME datatype are not supported

Cause: Filter parameters with DATETIME datatype are not supported.

Action: DATETIME datatype cannot be used with Filter parameters
Level: 1

Type: WARNING

Impact: Other

ESS-03058: Value of deltaStart or deltaEnd cannot be negative

Cause: Value of deltaStart or deltaEnd is negative.

Action: Value of deltaStart or deltaEnd cannot be negative
Level: 1

Type: ERROR

Impact: Other

ESS-03059: Datatype is not supported for a parameter value:{0}

Cause: Unsupported datatype for parameter.

Action: Unsupported datatype for parameter.
Level: 1

Type: ERROR

Impact: Other

ESS-03060: Failed to convert parameter value to data type:{0}

Cause: Failed to convert parameter value to data type.

Action: Failed to convert parameter value to data type.
Level: 1

Type: ERROR

Impact: Other

ESS-03061: Value of parameter {0} has data type {1} instead of the expected data type {2}

Cause: Parameter value datatype mismatch.

Action: Parameter value datatype mismatch.
Level: 1

Type: ERROR

Impact: Other

ESS-03062: Step must be JobDefinition or JobSet

Cause: Invalid step type.

Action: Step must be JobDefinition or JobSet.
Level: 1

Type: ERROR

Impact: Other

ESS-03063: Unknown data type for parameter {0}

Cause: Unknown datatype for parameter.

Action: Unknown datatype for parameter.
Level: 1

Type: ERROR

Impact: Other

ESS-03064: Operation not supported for scoped parameter {0}

Cause: Operation not supported for scoped parameter.

Action: Operation not supported for scoped parameter.
Level: 1

Type: ERROR

Impact: Other

ESS-03065: RecurrenceSet must contain at least one recurrence

Cause: RecurrenceSet is empty.

Action: RecurrenceSet must contain atleast one recurrence.
Level: 1

Type: ERROR

Impact: Other

ESS-03066: Unable to delete workshift {0} that is referenced by a work assignment.

Cause: Wokshift deletion failed as it is referenced by a work assignment

Action: Ensure that workshift is not referenced in a work assignment before deletion
Level: 1

Type: ERROR

Impact: Other

ESS-03067: Unable to delete schedule {0} that is referenced by a workshift.

Cause: Schedule deletion failed as it is referenced by a work shift

Action: Ensure that schedule is not referenced by a work shift before deletion
Level: 1

Type: ERROR

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-05015: Oracle Enterprise Scheduler. Release Version: {0}, Build: {1}

Cause: Information about release version and build label of Oracle Enterprise Scheduler.

Action: No action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-05016: Oracle Enterprise Scheduler runtime store. Schema Name: {0}, Version: {1}, Status: {2}

Cause: Information about the runtime store used by Oracle Enterprise Scheduler.

Action: No action is necessary.
Level: 1

Type: NOTIFICATION

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-05025: Error in transaction processing. The transaction is eligible to be retried.

Cause: A recoverable SQL error was encountered

Action: None
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-05111: Bulk metadata customization input file {0} does not exist or is not readable.

Cause: Invalid XML input file specified for bulk customization.

Action: Provide the correct input XML file for bulk customization.
Level: 1

Type: ERROR

Impact: Other

ESS-05112: Bulk metadata customization output file {0} is not writable.

Cause: Invalid XML output file specified for bulk customization.

Action: Provide the correct output XML file absolute pathname.
Level: 1

Type: ERROR

Impact: Other

ESS-05113: Argument type is not supported: {0}

Cause: The type of argument is unsupported.

Action: Use a supported argument type.
Level: 1

Type: WARNING

Impact: Other

ESS-05114: Failed to check in {0} work unit {1}. {2}

Cause: The work unit 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-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 occurred 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 occurred 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-06534: {0} is an unversioned ESS hosting application. Unversioned hosting applications are deprecated and will not be supported in subsequent releases. Some features are only supported for versioned applications.

Cause: The ESS hosting application does is not versioned.

Action: Make the application versioned or expect certain features not to work.
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-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-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-06630: Error starting work manager work.

Cause: An error occurred starting work mananger work.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-06631: Cannot allocate thread. The maximum number of threads has been allocated for this pool: {0}

Cause: The maximum threads for a work pool has been reached.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06632: Cannot allocate thread. The client maximum number of threads has been allocated for this pool: {0}

Cause: The client maximum threads for a work pool has been reached.

Action: None
Level: 1

Type: NOTIFICATION

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-06647: Exclusive mode is not allowed for {1} scoped binding, work assignment {0}.

Cause: Invalid binding mode for binding with the given scope.

Action: Either bind the work assignment in standard mode or use a different scope (standard or group).
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-06835: Performing automatic refresh of metadata for request {0}, metadata {1}.

Cause: Metadata used by the request has changed and is being automatically refreshed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06836: Changes to metadata prevent automatic refresh for request {0}, metadata {1}.

Cause: Metadata used by the request has changed but cannot be refreshed because the changes are not allowed for automatic refresh.

Action: No action is required. For automatic refresh, only customizable parameters may have been changed.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06837: Unable to refresh job metadata at this time for request {0}.

Cause: Temporarily unable to refresh changed metadata for the request.

Action: No action is required. The request may be refreshed in the future.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06838: Unable to access metadata in runtime store for request {0}, metadata {1}.

Cause: Unable to access cached metadata for the request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06839: Metadata already exists in runtime store for request {0}, metadata {1}.

Cause: The metadata already exists in the cache in the runtime store for the request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06840: Failed to insert metadata change notification for application {0}, change type {1}, metadata id {2}.

Cause: Failed to add the metadata change notification to the runtime store.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06841: Failed to insert metadata change notification for application {0}, change type {1}, metadata id {2}.

Cause: Failed to add the metadata change notification to the runtime store.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06842: Unable to access metadata change notifications.

Cause: Unable to access metadata change notifications.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06843: Unable to determine the logical application name for deployed application ''{0}''.

Cause: Unable to determine the logical application that should be used for a metadata change notification.

Action: Review the log file for information to determine the nature of the problem, and ensure the logical application name is defined.
Level: 1

Type: WARNING

Impact: Other

ESS-06844: Failed to remove parameter {0} for request {1}.

Cause: Unable to remove the parameter for the request during a metadata refresh.

Action: Review the log file for information to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06845: Failed to remove the read-only constraint for parameter {0}, request {1}.

Cause: Unable to remove the read-only constraint for the request parameter during a metadata refresh.

Action: Review the log file for information to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06846: Parameter ''{0}'' is now read only for request {1}. Previous update is discarded.

Cause: Due to a metadata refresh, the parameter is now read-only. The parameter had been updated previously, and that update has been discarded.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06847: Failed to remove runtime metadata for request {0}.

Cause: Unable to remove cached runtime metadata for the request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

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-07044: Failed to instantiate EJB job request {0}

Cause: Failed to instantiate RemoteExecutable object for a EJB request.

Action: Make sure the bean implements RemoteExecutable and the parameters JNDI_MAPPED_NAME, JNDI_PROVIDER_URL are specified in job definition.
Level: 1

Type: ERROR

Impact: Other

ESS-07045: Failed to execute EJB job request {0}. Reason: {1}

Cause: Failed to execute RemoteExecutable object for a EJB request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-07046: Failed to cancel EJB job request {0}

Cause: Failed to cancel RemoteCancellableExecutable object for a EJB request.

Action: Review the log file for attached exceptions to determine the nature of the problem. Make sure the EJB implement RemoteCancellableExecutable interface.
Level: 1

Type: WARNING

Impact: Other

ESS-07047: Metadata parameter {0} not specified in job definition for request {1}.

Cause: Validation failed for EJB request. One or more mandatory parameters of EJB job not set.

Action: Make sure the mandatory parameters are specified in job definition.
Level: 1

Type: ERROR

Impact: Other

ESS-07048: Error while retrieving credentials for CSF Key {0} while processing request {1}.

Cause: Error while retrieving CSF credentials. The configuration is either null or invalid.

Action: Make sure the CSF configuration is proper.
Level: 1

Type: WARNING

Impact: Other

ESS-07049: Error while retrieving Ess Configuration for application {0} while processing request {1}.

Cause: Error while retrieving values of EssConfiguration . The configuration is either null or invalid.

Action: Make sure the configuration is proper.
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-07060: Invalid work unit action {0} for work unit {1}.

Cause: Invalid work unit action.

Action: Report the failure to Oracle support as it could be a bug in ESS.
Level: 1

Type: ERROR

Impact: Other

ESS-07061: An error occurred initiating processing of an update work unit for request {0}.The incoming asynchronous status is {1}.Error message: [{2}] {3}

Cause: The asynchronous java job callback to update the status could not be processed.

Action: Examine error message
Level: 1

Type: WARNING

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-07216: Using Java SpawnAgent from {1} for spawned job request {0}.

Cause: Using Java SpawnAgent from {1} for spawned job request {0}.

Action: None
Level: 1

Type: NOTIFICATION

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-07300: Invalid WebServiceJobDefinition for request {0}, {1} property value is invalid.

Cause: Invalid WebServiceJob Definition: identified property value is invalid.

Action: Specify a valid value for the identified property in WebServiceJobDefinition.
Level: 1

Type: ERROR

Impact: Other

ESS-07301: Post-substitution WebService INVOKE_MESSAGE for request {0}: {1}

Cause: PostSubstitution WebService Invoke Message.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-07302: WebService INVOKE_MESSAGE Substitution Error for request {0}.

Cause: Substitution error while processing WebService INVOKE_MESSAGE.

Action: Specify a valid xml for INVOKE_MESSAGE property in WebServiceJobDefinition.
Level: 1

Type: ERROR

Impact: Other

ESS-07303: WebService WSDL URL Substitution Error for request {0}.

Cause: Substitution error while processing WebService Wsdl URL.

Action: Review WS_WSDL_URL property value in WebServiceJobDefinition.
Level: 1

Type: ERROR

Impact: Other

ESS-07304: WebService WSDL URL Retrieval Error for request {0}.

Cause: Error retrieving WebService Wsdl from substituted URL.

Action: Review WS_WSDL_URL property value in WebServiceJobDefinition.
Level: 1

Type: ERROR

Impact: Other

ESS-07305: Invalid WebService Endpoint URL for request {0} in wsdl retrieved from {1}.

Cause: Invalid WebService Endpoint URL in retrieved wsdl.

Action: Review WS_WSDL_URL property value in JobDefinition and Endpoint URL value in specified wsdl.
Level: 1

Type: ERROR

Impact: Other

ESS-07306: WS_SECURITY_OPTION property not specified OR Invalid WS_SECURITY_OPTION property value in WebServiceJob JobDefinition for request {0}.

Cause: WS_SECURITY_OPTION property not specified OR Invalid WS_SECURITY_OPTION property value in WebServiceJobDefinition.

Action: Review WS_SECURITY_OPTION property value in JobDefinition, if specified.
Level: 1

Type: WARNING

Impact: Other

ESS-07307: WS_HTTP_BASIC_AUTH_CSF_KEY not configured in JobDefinition for request {0}.

Cause: WS_HTTP_BASIC_AUTH_CSF_KEY not configured in WebServiceJob Definition.

Action: Specify a valid CSF key for WS_HTTP_BASIC_AUTH_CSF_KEY property in WebServiceJobDefinition.
Level: 1

Type: ERROR

Impact: Other

ESS-07308: Error using JRF PortConfig API to determine ESS WebService URL Prefix.

Cause: Error using JRF PortConfig API to determine ESS WebService URL Prefix.

Action: JRF Portability issue. Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

ESS-07309: Computed WebService Callback URL for Async WebServiceJob: {0}.

Cause: Computed WebService Callback URL.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-07310: Error invoking webservice operation {1} for request {0}.

Cause: Error invoking webservice operation.

Action: Review log file for attached exception and update JobDefinition.
Level: 1

Type: ERROR

Impact: Other

ESS-07311: WebService operation {1} for request {0} results in SOAPFault with FaultCode={2} and FaultString={3}.

Cause: Invoking webservice operation results in a SOAPFault.

Action: Review SOAPFault and update WebService JobDefinition properties.
Level: 1

Type: ERROR

Impact: Other

ESS-07312: Error saving WebService operation messageId for request {0}.

Cause: Error saving WebService operation messageId.

Action: Review log file for attached exception.
Level: 1

Type: ERROR

Impact: Other

ESS-07313: Error retrieving WebService operation messageId for request {0}.

Cause: Error retrieving WebService operation messageId.

Action: Review log file for attached exception.
Level: 1

Type: ERROR

Impact: Other

ESS-07314: WebService operation for request {0} cannot be cancelled as Cancel Operation properties not specified in WebServiceJobDefinition.

Cause: WebService operation for request cannot be cancelled as Cancel operation properties not specified in WebServiceJobDefinition.

Action: Review Cancel operation properties in WebServiceJobDefinition.
Level: 1

Type: ERROR

Impact: Other

ESS-07315: WebService operation for request {0} cannot be cancelled, as Cancel message specified in WebServiceJobDefinition is invalid.

Cause: WebService operation for request cannot be cancelled as Cancel message specified in WebServiceJobDefinition is invalid.

Action: Review Cancel operation properties in WebServiceJobDefinition.
Level: 1

Type: ERROR

Impact: Other

ESS-07316: WebService WS_CANCEL_MESSAGE Substitution Error for request {0}.

Cause: Substitution error while processing WebService Cancel message.

Action: Review WS_CANCEL_MESSAGE property in WebServiceJobDefinition.
Level: 1

Type: ERROR

Impact: Other

ESS-07317: Error invoking webservice Cancel operation {1} for request {0}.

Cause: Error Cancelling webservice operation.

Action: Review log file for attached exception and update Cancel operation properties in JobDefinition.
Level: 1

Type: ERROR

Impact: Other

ESS-07318: WebService Cancel operation {1} for request {0} results in SOAPFault with FaultCode={2} and FaultString={3}.

Cause: Invoking webservice Cancel operation results in a SOAPFault.

Action: Review SOAPFault and update WebService JobDefinition properties.
Level: 1

Type: ERROR

Impact: Other

ESS-07319: Error retrieving webservice SOAPResponse payload for request {0}.

Cause: Error retrieving webservice SOAPResponse payload.

Action: Review log file for attached exception and and update WebService JobDefinition properties.
Level: 1

Type: WARNING

Impact: Other

ESS-07320: Error capturing webservice response as Job Output for request {0}.

Cause: Error capturing webservice response as Job Output.

Action: Review log file for attached exception.
Level: 1

Type: ERROR

Impact: Other

ESS-07321: WebService Job Output for request {0}: {1}.

Cause: WebServiceJob Output.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-07322: Error retrieving credentials from CredentialStore using CSF key {0}.

Cause: Error retrieving CSF Credentials from CredentialStore.

Action: Review CSF key in WebServiceJobDefinition.
Level: 1

Type: ERROR

Impact: Other

ESS-07323: No base URL is specified for relative URL {0} = {1} for request {2}.

Cause: A required base URL was not specified for the given relative URL

Action: Specify the corresponding base URL as an ESS system property or in the application configuration.
Level: 1

Type: WARNING

Impact: Other

ESS-07324: Error retrieving WebService JobDefinition for request {0}.

Cause: Error retrieving WebService JobDefinition for request {0}.

Action: Review log file for attached exception.
Level: 1

Type: ERROR

Impact: Other

ESS-07325: Error retrieving wsa:relatesTo addresssing header from callback message using DISI ServiceRequestTransport.

Cause: Error retrieving wsa:relatesTo addresssing header from callback message using DISI ServiceRequestTransport.

Action: Review log file for attached exception.
Level: 1

Type: ERROR

Impact: Other

ESS-07326: Invalid SOAP response message, error processing message by WebServiceJob Callback servlet.

Cause: Invalid SOAP response message, error processing message by WebServiceJob Callback servlet.

Action: Review log file for attached exception. Verify async callback message is a valid SOAP response
Level: 1

Type: ERROR

Impact: Other

ESS-07327: Error processing WebServiceJob callback response in ServiceResponseTransport.

Cause: Error processing WebServiceJob callback response in ServiceResponseTransport.

Action: Review log file for attached exception.
Level: 1

Type: ERROR

Impact: Other

ESS-07328: Error processing WebServiceJob callback message in ProviderRequest.

Cause: Error processing WebServiceJob callback message in ProviderRequest.

Action: Review log file for attached exception.
Level: 1

Type: ERROR

Impact: Other

ESS-07329: WebServiceJob Progress message not permitted for request {0}.

Cause: WebServiceJob Progress message not permitted for request {0}.

Action: Review WebServiceJob progress message usage recommendations.
Level: 1

Type: WARNING

Impact: Other

ESS-07332: Error registering Policy Assembly {0} with OWSM.

Cause: Error registering Policy Assembly {0} with OWSM.

Action: Review PolicyAssembly ResourcePattern.
Level: 1

Type: ERROR

Impact: Other

ESS-07360: EssPolicyManager instance lookup attempted passing a NULL PolicyContext.

Cause: EssPolicyManager instance lookup attempted passing a NULL PolicyContext

Action: Review log file for details. Contact administrator.
Level: 1

Type: WARNING

Impact: Other

ESS-07361: EssPolicyManager instance lookup attempted passing empty or NULL application name.

Cause: EssPolicyManager instance lookup attempted passing empty or NULL application name

Action: Review log file for details. Contact administrator.
Level: 1

Type: WARNING

Impact: Other

ESS-07362: Error publishing WsmPolicyUpdateEvent for application {0}.

Cause: Error publishing WsmPolicyUpdateEvent for application {0}.

Action: Review log file and contact Administrator.
Level: 1

Type: ERROR

Impact: Other

ESS-07364: Error deregistering Policy Assembly {0} with OWSM.

Cause: Error deregistering Policy Assembly {0} with OWSM.

Action: Review PolicyAssembly ResourcePattern.
Level: 1

Type: ERROR

Impact: Other

ESS-07365: Error creating Policy Assembly for request {0}.

Cause: Error creating Policy Assembly for request {0}.

Action: Review log file for attached exception.
Level: 1

Type: ERROR

Impact: Other

ESS-07366: Error retrieving Policy Assembly for job definition {0}.

Cause: Error retrieving Policy Assembly for job definition {0}.

Action: Review log file for attached exception.
Level: 1

Type: ERROR

Impact: Other

ESS-07367: Error validating {0} Policy Subject registration with OWSM Policy Access Point for request {1}.

Cause: Error validating {0} Policy Subject registration with OWSM Policy Access Point for request {1}.

Action: Review log file for owsm . Contact Administrator.
Level: 1

Type: ERROR

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.

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}, isolation group{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}, isolation group {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}, isolation group {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}, isolation group {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-07552: Failed to insert configuration for application {0} in process group {1}.

Cause: Failed to insert the entry from essconfig table.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07553: Failed to delete configuration for application {0} in process group {1}.

Cause: Failed to delete the entry from essconfig table.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07554: Failed to update configuration for application {0} in process group {1}.

Cause: Failed to update the configuration for the given application.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07555: Failed to query configuration for application {0} in process group {1}.

Cause: Failed to query the entry from essconfig table.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07556: Failed to find configuration for application {0} in process group {1}.

Cause: The configuration for the given application could not be found

Action: Check if the ESS logical application name is correct and that it is deployed to the current cluster.
Level: 1

Type: WARNING

Impact: Other

ESS-07557: Configuration exists for application {0} in process group {1}.

Cause: Configuration is already present for the given application.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07558: Failed to convert {2} for application {0} in process group {1}.

Cause: Conversion for an EssConfig or Customization object failed

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07559: Property {0} is immutable defined in the base application.

Cause: The given application configuration property is immutable and cannot be customized.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07560: Property {0} is immutable.

Cause: The given application configuration property is immutable and cannot be customized.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07561: Property name {0} is a reserved ESS property name.

Cause: The given application configuration property name is a reserved name.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07562: Property {0} has been defined. An update operation should be used.

Cause: The given application configuration property has been defined.

Action: Use update operation to customize the property.
Level: 1

Type: WARNING

Impact: Other

ESS-07563: Failed to insert configuration for server {0} in process group {1}.

Cause: Failed to insert the entry into the server configuration table.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07564: Failed to delete configurations in process group {0}.

Cause: Failed to delete the entry from server configuration table.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07565: Failed to update configuration for server {0} in process group {1}.

Cause: Failed to update the configuration for the given server.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07566: Failed to query configuration for server {0} in process group {1}.

Cause: Failed to query the entry from ess server config table.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07567: Failed to find configuration for server {0} in process group {1}.

Cause: The configuration for the given server could not be found.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07568: Configuration already exists for server {0} in process group {1}.

Cause: Configuration is already present for the given server name.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07569: An error occurred while updating the Scheduler server configuration for server {0} in process group {1}.

Cause: An error occurred updating the ESS server configuration.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07575: Error inserting wiring {0} with value {1} for group {2}.

Cause: Failed to store cross component wiring information.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07576: Error retrieving wiring {0} from group {1}.

Cause: An error occurred retrieving cross component wiring information from the runtime store.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07577: Error deleting all entries in wirings table.

Cause: An error occurred deleting cross component wiring information from the runtime store.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07578: Failed to register listener for CCW configuration.

Cause: The cross component wiring configuration listener could not be registered.

Action: Review the log file for the cause.
Level: 1

Type: WARNING

Impact: Other

ESS-07579: Failed to unregister listener for CCW configuration.

Cause: The cross component wiring configuration listener could not be registered.

Action: Review the log file for the cause.
Level: 1

Type: WARNING

Impact: Other

ESS-07580: Cross component wiring configuration listener failed to process document change event.

Cause: An error occurred processing the notification from the ESS CCW configuration.

Action: Review the log file for the cause.
Level: 1

Type: WARNING

Impact: Other

ESS-07581: Failed to delete wirings for URNs {0} from group {1}.

Cause: An error occurred deleting cross component wiring information from the runtime store.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07582: A logical cluster name must be specified for cross-component wiring enabled jobs. Parameter {0} for request {1} has substitution prefix WIRING.

Cause: The WIRING substitution prefix was used for a job without a logical cluster name.

Action: Either specify a logical cluster name for the job or explicitly specify the property value.
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-08002: Invalid value passed to ''name'' of RuntimeDataPermission: {0}. Please check the server logs.

Cause: Invalid value passed to 'name' of RuntimeDataPermission

Action: Provide the correct permission name.
Level: 1

Type: ERROR

Impact: Other

ESS-08003: Unsupported query field {0} specified in RuntimeDataPermission name Please check the server logs.

Cause: Unsupported query field name passed to 'name' of RuntimeDataPermission

Action: Provide a valid queryField in permission name.
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

18 FRC-60003 to FRC-60107

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

19 FRM-41838 to FRM-99999

FRM-41838: runtime process: unable to open temporary record buffer file

Cause: The runtime process was unable to open the file used as the temporary record buffer. A preceding FRM-91180 or FRM-91181 error message provides more detail. (FRM-91181 will occur if the error was on the first write attempt).

Action: Refer to error message FRM-91180 and FRM-91181.
Level: 1

Type: ERROR

Impact: Files

FRM-41839: runtime process: disk I/O error on temporary record buffer file

Cause: An I/O error occurred while the runtime process was attempting to read or write a record to the temporary record buffer file. A preceding FRM-91181 or FRM-91182 error message provides more detail.

Action: Refer to error message FRM-91181 and FRM-91182.
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-60006: error obtaining the managed server URL

Cause: Failed to obtain the managed server URL during Windows application deployment.

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-60007: error creating Windows shortcuts

Cause: Failed to create Windows shortcuts during configuration.

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-60008: error creating Forms instance {0}

Cause: Failed to create Forms instance.

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-60009: error updating Forms instance {0}

Cause: Failed to update Forms instance.

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-60010: error deleting Forms instance {0}

Cause: Failed to update Forms instance.

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-60011: error creating non-managed instance configuration

Cause: Failed to create Forms instance non-managed configuration.

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-60012: error updating/deleting instance: invalid Forms instance contents {0}

Cause: Failed to update Forms instance.

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-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-60104: error reading the Forms System component instance

Cause: An error occurred while reading the Forms system component instance information.

Action: Do one of the following:1. If there are multiple Forms system component instance on the same Weblogic machine, make sure that you have followed the steps in the Forms deployment guide.2. 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-60114: error reading default configuration path

Cause: An error occurred while obtaining the default configuration location.

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 initializing identity store

Cause: An error occurred while reading the identity store 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-60202: Forms J2EE application {0} is already registered with Oracle Internet Directory host {1} under the container {2}. Deregistering it.

Cause: An attempt was made to re-create an existing Forms J2EE application footprint in Oracle Internet Directory. 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 associating Forms application with Oracle Internet Directory host {0}

Cause: The Forms application footprint in Oracle Internet Directory failed to be created due to one of the following causes: 1. Oracle Internet Directory was not accessible. 2. The Forms J2EE application footprint password failed to be seeded in Oracle Platform Security Services on the mid-tier. 3. An I/O error occurred during storing of Oracle Internet Directory information from the Forms Oracle Internet Directory 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-60205: error disassociating Forms application with Oracle Internet Directory host {0}

Cause: Failed to remove the Forms J2EE application footprint from Oracle Internet Directory due to one of the following causes: 1. Oracle Internet Directory was not accessible. 2. An error status was returned while deregistering the Forms J2EE application footprint with Oracle Internet Directory. 3. Failed to fetch the Forms J2EE application footprint password from Oracle Platform Security Services on the mid-tier. 4. An I/O error occurred while cleaning Oracle Internet Directory information from the Forms Oracle Internet Directory properties file.

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 Oracle Internet Directory host is valid. 3. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60207: error storing credentials to Oracle Platform Security Services

Cause: An error occurred while storing the credentials to Oracle Platform Security Services.

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 Oracle Platform Security Services

Cause: An error occurred while deleting the credentials from Oracle Platform Security Services.

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 Oracle Platform Security Services

Cause: An error occurred while reading the credentials from Oracle Platform Security Services.

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: An error occurred while connecting 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-60211: error migrating Resource Access Descriptor

Cause: An error occurred migrating Resource Access Descriptor to Oracle Platform Security Services.

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-60212: Resource Access Descriptor migration process interrupted

Cause: A running Resource Access Descriptor migration process was interrupted.

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

Impact: Configuration

FRM-60213: error recording the Resource Access Descriptor migration result

Cause: An error occurred while recording the Resource Access Descriptor migration results.

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-60214: Forms Resource Access Descriptor migration thread awaken

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-60215: error reading the Resource Access Descriptor migration results

Cause: An error occurred while reading the Resource Access Descriptor migration results.

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-60216: error starting Forms Resource access migration to Oracle Platform Security Services

Cause: The Forms Resource Access Descriptor migration to Oracle Platform Security Services failed to start because the previous migration process is still running.

Action: Wait for the exiting migration process to complete before running migration again.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60217: invalid Single Sign-on user

Cause: The user passed an invalid Single Sign-on user name to create a Resource Access Descriptor.

Action: Provide a valid existing Single Sign-on user name and run the request again.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60218: error connecting to LDAP server

Cause: An error occurred while connecting the LDAP server due to one of the following causes: 1. Invalid connection credentials were entered. 2. Invalid hostname, port information was entered.3. LDAP server is down.

Action: Examine the cause, and take the appropriate remedial action.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60220: error initializing the Forms Identity store

Cause: An error occurred while initializing the Forms Identity store.

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-60221: error obtaining the Forms identity store access

Cause: An error occurred while obtaining the Forms Identity store.

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-60249: error creating Resource Access Descriptor for Forms application {0}: Resource Access Descriptor already exists

Cause: An error occurred while creating the Resource Access Descriptor because it already exists.

Action: Edit the existing Resource Access Descriptor rather than adding it.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60250: error creating Resource Access Descriptor for Forms application {0}

Cause: An error occurred while creating the Resource Access Descriptor.

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-60251: error updating Resource Access Descriptor for Forms application {0}

Cause: An error occurred while updating the Resource Access Descriptor.

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-60252: error deleting Resource Access Descriptor for Forms application {0}

Cause: An error occurred while deleting the Resource Access Descriptor.

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-60253: error reading Resource Access Descriptor for Forms application {0}

Cause: An error occurred while reading the Resource Access Descriptor.

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-60254: error obtaining Resource Access Descriptor

Cause: An error occurred while obtaining the Resource Access Descriptor.

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-60255: error stashing Single Single-on user information in the Forms session

Cause: An error occurred while stashing Single Sign-on user information in the Forms session.

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-60256: permission error reading the Resource Access Descriptor from Oracle Internet Directory

Cause: Single Sign-on user does not have the right permission to read the Resource Access Descriptor.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-60257: error reading Forms application {0}, Resource Access Descriptor for Single Sign-on User {1} from Oracle Internet Directory

Cause: An error occurred while obtaining the Forms application Resource Access Descritor from Oracle Internet Directory.

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

Impact: Configuration

FRM-60258: error reading Forms application Resource Access Descriptor from Oracle Internet Directory

Cause: An error occurred while obtaining the Forms application Resource Access Descritor from Oracle Internet Directory.

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

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 character 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: 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. Execution of the runtime process might have been terminated, or it might have continued. In the latter case, the functionality that required this environment variable was disabled.

Action: If this error message appears for DOMAIN_HOME or FORMS_INSTANCE_NAME, and the problem persists, contact Oracle Support Services. Otherwise, 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 {2}

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: 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. Execution of the runtime process might have been terminated, or it might have continued. In the latter case, the functionality that required this environment variable was disabled.

Action: If this error message appears for DOMAIN_HOME or FORMS_INSTANCE_NAME, and the problem persists, contact Oracle Support Services. Otherwise, set the environment variable to a non-empty value.
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-91134: fatal error in runtime process: NLS_LANG specifies unsupported character set

Cause: The NLS_LANG environment variable specified a character set which is not ASCII-based, e.g. fixed-width Unicode or an EBCDIC-based character set.

Action: Correct the NLS_LANG environment variable value.
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-91137: runtime process: unable to open log file {0}

Cause: An invalid name was specified for a log file or a trace file. The name might be too long, or it might specify a non-existent or read-only directory. In the former case, the error message shows the name truncated at the maximum allowable length, followed by 3 dots. Execution of the runtime process might have been terminated, or it might have continued. In the latter case, messages that subsequently would have been written to the file were silently discarded.

Action: Correct the environment variable used to specify the directory (e.g. FORMS_TRACE_DIR), and/or the file name proper (which might have been specified e.g. by the value of the 'log' configuration parameter). If no environment variable or configuration parameter was set to specify the directory or the file name proper, and the problem persists, contact Oracle Support Services.
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-91145: fatal error in runtime process: missing serverArgs parameter

Cause: If this error occurred when using the Forms Servlet, both the serverArgs configuration parameter and the serverArgs applet parameter (either of which can represent the command-line arguments that are passed to the frmweb executable) were either missing or had a blank value. If this error occurred for static HTML (HTML that's not generated by the Forms Servlet), the serverArgs applet parameter was either missing or had a blank value.

Action: If this error occurred for static HTML, add a serverArgs parameter to the applet. Otherwise, ensure that the Forms Servlet configuration file or the base HTML files correctly define a serverArgs parameter. [Note that the base HTML files that are shipped with the produce omit the serverArgs parameter, but the shipped Forms Servlet configuration file specifies a non-blank value.]
Level: 1

Type: ERROR

Impact: Configuration

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-91180: fatal error in runtime process: error {0} ({1}) attempting to open temporary record buffer file

Cause: An attempt to open the temporary record buffer file encountered the indicated error. Both the error number (errno on Unix and GetLastError() on Windows) and the corresponding error string are given. The runtime process was terminated.

Action: Examine the error string, and take appropriate remedial 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-91181: runtime process: error {0} ({1}) attempting to write {2} bytes to offset {3} of temporary record buffer file {4}

Cause: The specified 'write' operation to the temporary record buffer file encountered the indicated error. Both the error number (errno on Unix and GetLastError() on Windows) and the corresponding error string are given. Execution continued, for the moment at least; however, an error other than "out of space" is likely to cause subsequent termination of the runtime process (message FRM-91195).

Action: Examine the error string, and take appropriate remedial 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-91182: runtime process: error {0} ({1}) attempting to read {2} bytes from offset {3} of temporary record buffer file {4}

Cause: The specified 'read' operation to the temporary record buffer file encountered the indicated error. Both the error number (errno on Unix and GetLastError() on Windows) and the corresponding error string are given. Execution continued, for the moment at least; however, the error is likely to cause subsequent termination of the runtime process (message FRM-91195).

Action: Examine the error string, and take appropriate remedial action.
Level: 1

Type: ERROR

Impact: Files

FRM-91183: runtime process: error {0} ({1}) attempting to allocate {2} bytes at offset {3} of temporary record buffer file {4}

Cause: The specified 'allocate' operation ('fallocate' on Linux and 'posix_fallocate' on other Unix platforms) to the temporary record buffer file encountered the indicated error. Both the error number (errno) and the corresponding error string are given. Execution continued, for the moment at least; however, an error other than "out of space" is likely to cause subsequent termination of the runtime process (message FRM-91195).

Action: Examine the error string, and take appropriate remedial 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-91184: runtime process: error {0} ({1}) attempting to truncate or extend temporary record buffer file {2} to {3} bytes

Cause: The specified 'ftruncate' operation to the temporary record buffer file encountered the indicated error. Both the error number (errno) and the corresponding error string are given. Execution continued, for the moment at least; however, an error other than "out of space" is likely to cause subsequent termination of the runtime process (message FRM-91195).

Action: Examine the error string, and take appropriate remedial 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-91185: runtime process: error {0} ({1}) attempting to close temporary record buffer file {2}

Cause: An attempt to close the temporary record buffer file encountered the indicated error. Both the error number (errno on Unix and GetLastError() on Windows) and the corresponding error string are given. Execution continued; however, it's possible that the temporary record buffer file was not deleted properly.

Action: Examine the error string, and take appropriate remedial action.
Level: 1

Type: WARNING

Impact: Files

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 space, or rerun the application when the system is less heavily loaded.
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 space, or rerun the application when the system is less heavily loaded.
Level: 1

Type: ERROR

Impact: Memory

FRM-91192: fatal error in runtime process: unable to memory-map {0} bytes of memory

Cause: A memory-map request failed. This probably indicates insufficient swap space. Execution of the runtime process was terminated.

Action: Increase the size of the swap space, or rerun the application when the system is less heavily loaded.
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 space, or rerun the application when the system is less heavily loaded.
Level: 1

Type: ERROR

Impact: Memory

FRM-91194: fatal error in runtime process: unable to allocate memory for critical record manager operation

Cause: A memory allocation failure (reported in a preceding FRM-91191 message) occurred while attempting a record manager operation, and the operation was subsequently deemed critical. Execution of the runtime process was terminated.

Action: Increase the size of the swap space, or rerun the application when the system is less heavily loaded.
Level: 1

Type: ERROR

Impact: Memory

FRM-91195: fatal error in runtime process: cannot recover from disk I/O error on temporary record buffer file

Cause: A disk I/O error on the temporary record buffer file (reported in a preceding FRM-41839 message and in a FRM-91181 or FRM-91182 message preceding that) caused a critical operation to fail. Execution of the runtime process was terminated. Note that an "out of space" error on a write is *not* fatal.

Action: Examine the preceding FRM-91181 or FRM-91182 message.
Level: 1

Type: ERROR

Impact: Files

FRM-91196: fatal error in runtime process: unable to memory-map {0} bytes of memory backed by a file

Cause: A memory-map request backed by a file failed. This probably indicates insufficient space in the file system (e.g. /tmp). Execution of the runtime process was terminated.

Action: Increase the size of the file system, or rerun the application when the system is less heavily loaded.
Level: 1

Type: ERROR

Impact: Memory

FRM-91197: runtime process: unable to memory-map {0} bytes of memory backed by a file; attempting to continue execution

Cause: A memory-map request backed by a file failed. This probably indicates insufficient space in the file system (e.g. /tmp). 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 file system, or rerun the application when the system is less heavily loaded.
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-91279: runtime process unable to restrict IPv6 socket to IPv6 only: {0}

Cause: The runtime process was unable to configure the socket that it allocated for IPv6, to restrict its use to IPv6 only (as opposed both IPv6 and IPv4). The error message from the operating system is displayed. The runtime process attempted to continue execution, but a subsequent attempt to bind the socket might fail with the error "address already in use".

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-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-91930: message from Forms application: {0}

Cause: The Forms application called the MESSAGE built-in with an option of ODL_DEBUG.

Action: Respond as directed by the application developer.
Level: 32

Type: TRACE

Impact: Other

FRM-91934: message from Forms application: {0}

Cause: The Forms application called the MESSAGE built-in with an option of ODL_NOTIFICATION.

Action: Respond as directed by the application developer.
Level: 1

Type: NOTIFICATION

Impact: Other

FRM-91935: message from Forms application: {0}

Cause: The Forms application called the MESSAGE built-in with an option of ODL_WARNING.

Action: Respond as directed by the application developer.
Level: 1

Type: WARNING

Impact: Other

FRM-91936: message from Forms application: {0}

Cause: The Forms application called the MESSAGE built-in with an option of ODL_ERROR.

Action: Respond as directed by the application developer.
Level: 1

Type: ERROR

Impact: Other

FRM-91990: runtime process: A maximum of {0}K bytes were simultaneously allocated for archived record data.

Cause: The runtime process allocated the indicated amount of memory without reserving swap space or /tmp file space. The memory will be included in many reports of memory usage (such as the output of the Linux pmap command), but it will not consume system resources (real memory or disk) until it is actually used for archived record data. (See FRM-91992).

Action: No action is required.
Level: 1

Type: TRACE

Impact: Performance

FRM-91991: runtime process: A maximum of {0}K bytes were simultaneously allocated and reserved for archived record data.

Cause: The runtime process allocated the indicated amount of memory, and reserved swap space or /tmp file space for it.

Action: No action is required. However, if the number reported by this message is significantly larger than the number reported by FRM-91992 and you are using mapped-memory archiving (FORMS_RECMGR_ARCHIVE unset, or set to MAP_SWAP or MAP_TMPFILE), you may want to reduce the value of FORMS_RECMGR_BLOCK_SIZE (which defaults to 64K when memory is being reserved, but can be set as low as 32K). Better yet, don't reserve memory that's allocated for archived record data, if possible. (This can be accomplished in most Unix installations, by setting FORMS_RECMGR_RESERVE_SPACE to '0').
Level: 1

Type: TRACE

Impact: Performance

FRM-91992: runtime process: A maximum of {0}K bytes were simultaneously in use for archived record data.

Cause: The runtime process used the indicated amount of memory for archived record data. Specifically, at time of maximum usage, it (the runtime process) had written data into the pages of memory, and the data was still needed at that point (because there was a possibility that the record might subsequently need to be activated). Note that when FORMS_RECMGR_ARCHIVE has been set to WRITE_TMPFILE, the runtime process has no way of notifying the file system when it no longer needs a page, and so the file system may retain an unneeded page in a real-memory buffer for a while. Thus, in this case the number reported by this message should be viewed as lower bound.

Action: No action is required. However, the numbers reported by this message for various applications may help to determine an appropriate value for FORMS_RECMGR_ARCHIVE_THRESHOLD.
Level: 1

Type: TRACE

Impact: Performance

FRM-91994: runtime process: Record groups required {0}K bytes for archived record data, plus approximately {1}K additional bytes for active record data and record anchors. If FORMS_RECMGR_USED_FOR_RECGRPS were set to FALSE, a total of approximately {2}K bytes would instead have been required.

Cause: At the point in time when total memory for archived record data was at its maximum (as reported by FRM-91992), the runtime process used the sum of the first two amounts for all data and anchors for all records in record groups, but would instead have used the third amount if FORMS_RECMGR_USED_FOR_RECGRPS had been set to FALSE.

Action: No action is required. However, the numbers reported by this message for various applications may help to determine the appropriate value for FORMS_RECMGR_USED_FOR_RECGRPS. [Bear in mind that TRUE (the default) requires more CPU than FALSE.]
Level: 1

Type: TRACE

Impact: Performance

FRM-91995: runtime process: The record manager is currently consuming the following for {0}: {1}

Cause: The Forms application issued a call to the GET_RECMGR_STATS built-in, which then issued this message. The parameter {1} in this message is a formatted report of the amount of various types of memory currently being consumed for record data of the type indicated by the parameter {0} in this message (which corresponds to the argument passed to GET_RECMGR_STATS: all_record_data, archived_record_data, active_record_data, or record_anchors). The formatted report lists Kbytes of memory for the following 6 types of memory: MALLOCED, MAPPED, MAPPED_IN_USE, MAPPED_RESERVED, WRITTEN, WRITTEN_IN_USE.

Action: No action is required.
Level: 1

Type: TRACE

Impact: Performance

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-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: Java Web Start was not enabled, but 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: Java Web Start was not enabled, but the specified base HTML 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 or JNLP 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-93134: No base JNLP file is specified.

Cause: Java Web Start was enabled or a JNLP file was embedded in the HTML file, but the basejnlp configuration parameter was not specified. The FRM-93140 error message provides details about which configuration sections were searched.

Action: Specify the basejnlp configuration parameter.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93135: Cannot find base JNLP file {0}.

Cause: Java Web Start was enabled or a JNLP file was embedded in the HTML file, but the specified base JNLP file was not found. This file is specified by the basejnlp 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 basejnlp parameter specifies the correct file. Create the file if necessary.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93136: no base TXT file specified for Oracle Forms Standalone Application

Cause: The baseSAAfile configuration parameter was not specified.

Action: Specify the baseSAAfile configuration parameter.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93137: Oracle Forms Standalone Application session not allowed when ssoMode enabled

Cause: The configuration parameter ssoMode was enabled for an Oracle Forms Standalone Application request.

Action: Disable ssoMode, or use a browser to launch Oracle Forms.
Level: 1

Type: ERROR

Impact: Configuration

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-93143: Oracle Forms Standalone Launcher checksum failed.

Cause: The checksum received from the client did not match the Oracle Forms Standalone Launcher jar.

Action: Contact your system administrator or get the latest Oracle Forms Standalone Launcher file.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93144: error while generating checksum of Oracle Forms Standalone Launcher file

Cause: An I/O error occurred while generating the checksum.

Action: Check if Oracle Forms Standalone Launcher file exists.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93145: Oracle Forms Standalone Launcher version parameter is missing.

Cause: The request received from Oracle Forms Standalone Launcher does not contain Oracle Forms Standalone Launcher version information.

Action: Get the latest Oracle Forms Standalone Launcher file.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93146: Oracle Forms Standalone Launcher version {0} does not match server version {1}.

Cause: Oracle Forms Standalone Launcher jar is outdated.

Action: Get the latest Oracle Forms Standalone Launcher file.
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-93198: unexpected error while obtaining the cluster name from JRF

Cause: An Exception was encountered while obtaining the cluster 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-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-93242: serverURL applet parameter refers to an HTTP session that no longer exists.

Cause: The serverURL applet parameter specified an encoding (e.g. jsessionid) for a non-existant HTTP session. This probably resulted from the user double-clicking on a downloaded JNLP file that was created for Java Web Start with SSO enabled.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Session

FRM-93243: Static HTML is not allowed.

Cause: The serverURL applet parameter did not specify an ifcfs parameter and did not specify an encoding (e.g. jsessionid) for an HTTP session. The request for this URL was sent directly to the Forms Listener Servlet, but no HTTP session was associated with the request. This indicates that the HTML that defines the applet is "static", i.e. that it was not generated by the Forms Servlet. Static HTML is not allowed unless the envFile servlet initialization parameter for lservlet is set to a non-blank value.

Action: If you wish to allow static HTML, set the envFile servlet initialization parameter for lservlet to a non-blank value. This parameter specifies the full path of a file that defines values for environment variables (e.g. default.env). If you don't need such a file for static HTML (e.g. because all necessary environment variables are set in the Windows registry or in the script that launches webLogic), then set the envFile servlet initialization parameter for lservlet to ".".
Level: 1

Type: ERROR

Impact: Session

FRM-93244: URL could not be rewritten for a Java Web Start application or an Oracle Forms Standalone application.

Cause: Oracle Forms was attempting to run a Java Web Start application or an Oracle Forms Standalone application. Either URL rewriting was disabled (url-rewriting-enabled set to false in weblogic.xml), or else SSO was enabled (for Java Web Start: SSO is not allowed for Oracle Forms Standalone applications) and cookies were enabled (cookies-enabled not set or set to true in weblogic.xml). The application was terminated.

Action: If you wish to support Java Web Start or Oracle Forms Standalone applications when SSO is not enabled, ensure that url-rewriting-enabled is not set or is set to true in weblogic.xml. If, in addition, you wish to support Java Web Start applications when SSO is enabled, then also ensure that cookies-enabled is set to false weblogic.xml.
Level: 1

Type: ERROR

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-93302: error running Forms in SSO mode.

Cause: The OHS instance front-ending Forms managed server is not configured to run with Webgate.

Action: Configure OHS with the Webgate access client. Refer to the Forms documentation.
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-93308: Unable to get the User Distinguished Name (DN) for the User or the Subscriber

Cause: An Exception occurred while attempting to get the User Distinguished Name for the Oracle Access Manager user from Oracle Internet Directory

Action: Verify that the Oracle Internet Directory is Up.
Level: 1

Type: ERROR

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 Oracle Platform Security Services

Cause: The Forms servlet could not retrieve application credential from Oracle Platform Security Services to connect to OID. One of the following was true: 1. The Forms application did not have privileges to connect to Oracle Platform Security Services. 2. Oracle Platform Security Services 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.

Cause: The user did not have proper credentials configured in the Identity Store (Oracle Internet Directory or Oracle Platform Security Services), 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 ssoErrorURL configuration parameter was not defined. The preceding FRM-93140 error message provides more detail.

Action: Add the user credentials to the Identity Store (Oracle Internet Directory or Oracle Platform Security Services), 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-93331: Fatal authentication error: Invalid Single Sign-On User.

Cause: There was a failure to obtain the Single Sign-On user information after authentication.

Action: Re-login using SSO credentials. If the problem persists, contact Oracle Support Services.
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-93366: error creating Forms application's Resource Access Descriptor in Oracle Internet Directory.

Cause: The Forms application failed to dynamically create a Resource Access Descriptor (RAD) in Oracle Internet Directory.

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

FRM-93367: invalid parameters {0} passed to the Forms Rad Servlet

Cause: Invalid parameters were passed to the Forms Rad Servlet.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

FRM-93368: Forms Rad Servlet is in an invalid state.

Cause: Invalid Http session detected in the Forms Rad Servlet. This should never happen.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

FRM-93369: Direct user access of Forms RadServlet is not allowed.

Cause: User tried to access the Forms RadServlet directly.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Security

FRM-93370: error reading the Resouce Access Descriptor for update

Cause: Forms Rad Servlet failed to read the Resouce Access Descriptor to update it due to an internal error.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

FRM-93371: error closing connection with Oracle Internet Directory

Cause: Forms encountered an eorror closing connection with Oracle Internet Directory.

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

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-93430: scheduling prestart event: {0}.

Cause: A scheduled prestart timer event was processed, resulting in the prestart of one or more Forms runtime processes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93431: unexpected error while prestarting Forms runtime processes for the pre-start event: {0}

Cause: An Exception was encountered while prestarting Forms runtime processes for a scheduled prestart event.

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-93432: error adding notification listener to the Timer MBean

Cause: An Exception was encountered while adding notification listener to the Timer MBean.

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-93433: schedules restored from prestart archive file

Cause: Notifications were added to the prestart Timer MBean from the prestart archive file.

Action: No action is required
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93434: error restoring schedule {0} from the prestart archive file

Cause: An Exception was encountered while restoring a schedule from the prestart archive file.

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-93435: error restoring schedules from the prestart archive file

Cause: An Exception was encountered while restoring the schedules from the prestart archive file.

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-93436: schedules are written to the prestart archive file

Cause: Schedules from the prestart Timer MBean were dumped to the prestart archive file before the Forms application was shutdown.

Action: No action is required
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93437: error writing schedules to the prestart archive file

Cause: An Exception was encountered while writing schedules to the prestart archive file.

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-93438: error prestarting Forms runtime processes for the event: {0}

Cause: The scheduled Forms runtime processes could not be prestarted because of an invalid entry in the notification event from the prestart Timer MBean.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Process

FRM-93439: scheduled prestart event not processed for configuration section [{0}]

Cause: The prestart scheduling event was not processed because the prestartRuntimes parameter is not set in formsweb.cfg.

Action: Enable the prestartRuntimes parameter in formsweb.cfg.
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-93660: unable to get the hostname, using localhost instead of hostname in the Forms DMS table

Cause: The runtime process was unable to read the hostname from the server.

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-93661: error writing JVM Controller pid file

Cause: The runtime process was unable to write the JVM Controller pid file to the disk.

Action: Ensure that ORACLE_INSTANCE/FRComponent/frcommon/tools/jvm/proc directory exists, the user running Weblogic server has write permissions to write to it and there is adequate disk space.
Level: 1

Type: ERROR

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-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-94173: Value of serverArgs generated from configuration file and URL 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-94253: 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-94433: prestart archive file does not exist

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-96910: runtime process: OS page size is {0}.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-96911: runtime process: preferred file system block size for temporary record buffer 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-96912: runtime process: page size for temporary record buffer 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-96913: runtime process: record manager record segment size for block {0}.{1} is {2}, adjusted to {3}.

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

20 FMWPLATFORM-00001 to FMWPLATFORM-020010

FMWPLATFORM-00001: Command {0} is invalid.

Cause: Invalid command used with apatch tool

Action: Refer to the help message and provide valid command
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00002: Option {0} is not valid for command {1}.

Cause: An invalid option is passed

Action: Refer to the help message and provide the correct set of options
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00003: Invalid format specified.

Cause: Invalid format specified. "-" might be missing for options

Action: Refer to the help message and provide the correct syntax.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00004: Mandatory argument "{0}" is not entered.

Cause: Mandatory argument for the command is not entered.

Action: Please enter the required argument.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00005: Value "{0}" provided for argument "{1}" is invalid.

Cause: Invalid value provided for the argument.

Action: Please enter a valid value.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00006: Value "{0}" provided for argument "{1}"; this must be a boolean value.

Cause: Invalid value provided for boolean argument.

Action: Please enter a valid value.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00007: Value "{0}" provided for argument "{1}"; this must be a numeric value.

Cause: Invalid value provided for Integer argument.

Action: Please enter a valid value.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00008: Context creation failed, check that following paths are correct: {0}: {1}; {2}: {3};

Cause: Exception thrown from OPatch API during Context creation.

Action: Validate the given OracleHome, and make sure it contains inventory at given location.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00009: Patch top directory does not exist. Provide a valid directory path.

Cause: Invalid value provided for patchdir option

Action: Please enter a valid directory path
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00010: Unable to execute "opatch lspatches" command.

Cause: Unable to execute opatch lspatches command

Action: Verify OPatch directory exists under given ORACLE_HOME
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00011: Unable to execute script due to I/O error {0}.

Cause: Unable to execute given script due to I/O related issues

Action: Verify the cause specified in the error message
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00012: Current thread was interrupted when waiting for process to return: {0}.

Cause: InterruptedException occured when waiting for process to return

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00013: Unexpected error "{0}" occurred while executing post install step.

Cause: Unexpected error while executing post install action

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00014: Unexpected error "{0}" occurred while writing execution plan : {1}.

Cause: Unexpected error while writing execution plan to disk

Action: Verify file permissions for the given path
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00015: Help file does not exist in path {0}.

Cause: help.txt is not found in the given path

Action: help.txt is bundled along with conigpatch class in the package structure. Verify for the help file in configpatch.jar
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00016: Error while saving execution plan to disk.

Cause: JAXB exception when writing execution plan to disk

Action: Verify the path to execution plan is writable.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00017: Error: {0} while parsing patch metadata file {1}.

Cause: XML parse error while parsing patch metadata

Action: Verify the given metadata file for corruption
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00018: Error: {0} while reading patch metadata file {1}.

Cause: IO Error while reading patch metadata

Action: Verify the metadata file is present in the specified location`
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00019: Unexpected error {0} while marshalling patch metadata {1}.

Cause: JAXB error while unmarshalling path metadata

Action: Veryfiy metadata is valid and wellformed
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00020: The provided Oracle home does not exist.

Cause: Invalid value provided for Oracle home directory

Action: Please enter a valid directory path
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00021: The provided domain home does not exist.

Cause: Invalid value provided for config directory

Action: Please enter a valid directory path
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00022: Inventory prereq check for key {0} failed.

Cause: Prerequisite inventory entry, not found

Action: Apply the relevant patch to get the inventory entry
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00023: Metadata file for parsing config-actions not present in path: {0}.

Cause: patch metadata file (config-metadata.xsd) is not present in the specified directory

Action: The metadata file has to be part of the core.jar file. If not present, the jar might not be archived properly
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00024: Class {0} not found in classpath {1}.

Cause: The specified action action class could not be loaded

Action: The classpath set might not correct. Verify and provide the correct classpath
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00025: The provided domain home is not a directory.

Cause: Invalid value provided for config directory

Action: Please enter a valid directory path
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00026: Inventory entry {0} does not exist.

Cause: Designated inventory does not exist

Action: Enter an inventory existent entry.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00027: Inventory entry {0} already exists.

Cause: Designated inventory already exists. Cannot add new entry.

Action: Add the an entry with a unique key or remove the existing entry first.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00028: Domain home is not undefined.

Cause: -configdir is undefined in application arguments

Action: Specify -configdir in application parameters
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00029: Domain home path {0} does not exist.

Cause: -configdir path does not point to an existing directory

Action: Specify -configdir value that is a path to an existing directory.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00030: Inventory type {0} not implemented.

Cause: Requested inventory type is not implemented.

Action: Specify a different inventory type in command options
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00031: Prerequisite inventory element {0} does not exist.

Cause: Prerequisite inventory entry does not exist.

Action: Ensure prerequisite entries have been defined.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00032: Prerequisite inventory element {0} is self referencing.

Cause: Inventory entry has a prerequisite element that references the entry.

Action: Ensure prerequisite entries are not self referencing.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00033: Prerequisite inventory element produces a referential loop {0}.

Cause: Inventory entry has a prerequisite element that creates a referential loop.

Action: Ensure prerequisite entries do not refer to entries that, in turn, reference this inventory entry as a prerequisite.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00034: Failed to marshal inventory file.

Cause: Unexpected failure to marshal inventory file to disk

Action: Check associated stack trace in logs for cause of inventory marshal failure
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00035: Failed to unmarshal inventory file.

Cause: Unexpected failure to unmarshal inventory file from disk

Action: Check associated stack trace in logs for cause of inventory unmarshal failure
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00036: Action {0} prerequisites are not all met.

Cause: Prerequisites are not satisfied for the executing action

Action: Make sure all prerequisites have completed successfully.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00037: Patch {0} must be applied successfully before action execution.

Cause: Patch associated with executing action was not applied successfully beforehand.

Action: Apply the patch before action execution.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00038: Unknown action execution state {0}.

Cause: Action execution state is unhandled.

Action: The application is in an unstable state.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00039: Action {0} has failed.

Cause: Action has failed to execution successfully

Action: See log for action execution failure details.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00040: Multiple options supplied; the options are mutually exclusive.

Cause: Too many options supplied to inventory query command.

Action: You may specify only one value-providing option to the inventory query command.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00041: Failed to write execution plan XML to file {0}.

Cause: Could not write execution plan XML to file

Action: Check stack trace for root cause.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00042: Failed to read credential store password from standard input.

Cause: Password was not passed to the application via standard input.

Action: Ensure the credential store password is being passed to the application via standard input.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00043: Failed to read credential store password from console.

Cause: No console available to query user for password.

Action: Make sure the invocation method provides a means of console input. Otherwise, use STDIN to pass password in conjunction with -password-noprompt flag.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00044: Error parsing command line arguments: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00045: Logging configuration file could not be found.

Cause: Logging configuration file does not exist

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00046: Logging not configured correctly. Logging config file may be malformed.

Cause: Logging not configured correctly

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00047: Version command failure loading properties. Application properties file undefined.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00049: Error while executing command.

Cause: Required parameter not found in action invocation

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00050: Command name must be specified.

Cause: Command name was not specified

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00051: Unknown option {0}.

Cause: Unknown option

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00052: Option {0} must have a value defined.

Cause: Option value missing

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00053: Missing command line parameter(s): {0}.

Cause: Missing command line parameter

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00054: {0} is not a valid value for command line option {1}.

Cause: Invalid command line option

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00055: Could not execute OPatch to check patch list.

Cause: Could not execute opatch

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00056: Failed to marshal action metadata field to XML during serialization.

Cause: failed to marshal action metadata field

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00057: Invalid type specified.

Cause: Invalid action type specified.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00058: Invalid category specified.

Cause: Invalid action category specified.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00059: Invalid order specified.

Cause: Invalid action order specified.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00060: Invalid failure mode specified.

Cause: Invalid action failure mode specified.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00061: Invalid parameter name specified.

Cause: Invalid parameter name specified.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00062: Invalid parameter value specified.

Cause: Invalid parameter value specified.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00063: Invalid inventory reference key specified.

Cause: Invalid inventory reference key specified.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00064: Invalid inventory reference type specified.

Cause: Invalid inventory reference type specified.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00065: Invalid prereq inventory reference key specified.

Cause: Invalid prereq inventory reference key specified.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00066: Invalid prereq inventory reference type specified.

Cause: Invalid prereq inventory reference type specified.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00067: Invalid execution directive specified.

Cause: Invalid execution directive specified.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00068: Invalid lifecycle hint specified.

Cause: Invalid lifecycle hint specified.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00069: Action ID cannot be empty.

Cause: Action ID can not be empty.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00070: Action name cannot be empty.

Cause: Action name can not be empty.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00071: There were problems with the metadata for patch {0}, action {1}: {2}

Cause: Patch metadata validation error.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00072: Error reading patch metadata.

Cause: Error reading patch metadata.

Action: The patch metadata appears to be incorrect, or incompatible with this version.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-00073: Some patches have not been applied to the Oracle Home using OPatch: {0}.

Cause: Some patches have not been applied to the Oracle Home using OPatch.

Action: Make sure patches are applied to Oracle Home using OPatch.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-01000: Action execution completed successfully

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01001: Enter credential store password:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01002: Oracle Configuration Patcher

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01003: Could not find action with id {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01004: Could not find action with key {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01005: See log file for associated stack trace

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01006: {0} {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01007: Executing command {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01008: Command not implemented.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01011: Could not find patch with id {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01012: Checking which patches are applied, before executing actions

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01013: Executing action plan

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01014: Executing configuration action: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01015: Completed execution for: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01016: Action already exists in inventory, skipping

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01017: Executing all {0} actions

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01018: Analyzing Patch Directory....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01019: Found {0} candidate patches

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01020: Execution plan:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01021: Added inventory entry {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01022: Successfully removed inventory entry {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01023: Usage: ocp COMMAND [OPTIONS]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01024: Display help information

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01025: Print help for this command.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01026: OPTIONS:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01027: -help

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01028: Prints this help message.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01029: Terminate the current session

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01030: Displays the execution plan

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01031: Displays the execution plan, which shows what actions will be taken

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01032: Execute the plan

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01033: Apply all actions for the specified phase

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01034: Add an entry to the configuration change inventory

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01035: Removes an entry from the configuration change inventory

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01036: Display any prerequisite actions

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01037: Retry the current 'apply'

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01038: Display version information.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01039: Display version of this tool.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01040: Full path to DOMAIN_HOME

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01041: Full path to the credential store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01042: Full path to the Oracle home

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01043: Patch staging dir

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01044: Phase of execution (OFFLINE, ONLINE)

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01045: Domain name

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01046: If set, read credential store password from STDIN. Otherwise, prompt

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01047: OFFLINE

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01048: ONLINE

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01049: Unique name by which this change is referenced

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01050: Unique identifier of the action

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01051: ID of the patch containing the action

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01052: Query inventory

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01053: Reading patch metadata from {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01054: Reading in metadata for patch {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01055: Reading patch: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01056: Patch contains no patchDeployArtifacts, skipping.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01057: Patch contains no actions, skipping.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01058: Reading action: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01059: Patch contains actions: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-01060: Patches binary applied in Oracle Home: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-02001: Error in EmbeddedWLSTInvoker

Cause: Invalid command used with a patch tool

Action: Refer to the help message and provide valid command
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-02002: CFWLSTAction

Cause: Trace message

Action: Trace message
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-02003: invokeAction

Cause: Trace message

Action: Trace message
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-02004: Interpreter already closed

Cause: Exception thrown

Action: ActionClosedException is thrown
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-02005: Python Name Error

Cause: PyAttributeErrorException is thrown

Action: throws UnknownMethodException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-02006: Internal conversion error

Cause: PyConversionErrorException is thrown

Action: throws InternalErrorException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-02007: Generic Python Error: {0}

Cause: PyGenericErrorException is thrown

Action: throws BadActionException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-02008: Python Indentation Error

Cause: PyIndentationErrorException is thrown

Action: throws BadActionException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-02009: Python Syntax Error

Cause: PySyntaxErrorException is thrown

Action: throws BadActionException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-02011: Interpreter invocation failed

Cause: InterpreterInvocationFailedException is thrown

Action: throws InternalErrorException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-02012: Generic Interpreter exception

Cause: InterpreterException is thrown

Action: throws InternalErrorException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-02013: wlstInvoker cleanup

Cause: Exception occurred

Action: warning
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-02014: The module {0} is invalid, It must match the regular expression {1}

Cause: An invalid module name was detected

Action: throws InvalidModuleNameException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-02015: methodName not in <module>.<method> format

Cause: An invalid methodName was detected

Action: throws UnknownMethodException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-02016: Importing module {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-02017: preInvocationValidation

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04001: Oracle Home must be specified

Cause: Caller tried to get the EmbeddedWLSTInvoker without specifying an Oracle Home

Action: InterpreterCreationFailedException is thrown
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04002: Specified Oracle Home {0} is not a directory

Cause: Caller tried to get the EmbeddedWLSTInvoker without specifying an Oracle Home

Action: InterpreterCreationFailedException is thrown
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04003: Creating new interpreter for Oracle Home: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04004: New interpreter created for Oracle Home: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04005: Calling {0}()

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04006: Calling {0}({1})

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04007: Calling {0}({1}, {2})

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04008: Found loaded class: {0} (classloader = {1})

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04009: Trying to find class {0} in {1} classpath

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04010: Found class {0} in {1} classpath

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04011: {0} did not find class {1} so delegating to parent classloader

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04012: Class {0} was not found in any classpath

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04013: ChildFirstClassLoader did not try to find class {0} since the class is on the blacklist...delegating to parent classloader

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04014: Trying to find resource {0} in {1} classpath

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04015: {0} found resource {1} at {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04016: {0} did not find resource {1} so delegating to parent classloader

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04017: Resource {0} was not found in any classpath

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04018: Inside {0}()

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04019: Inside {0}({1})

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04020: Inside {0}({1}, {2})

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04021: {0} found {1} resources for {2}:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04022: Resources list for resource {0} has {1} elements after adding local and parent resources

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04023: getResourceAsStream() failed to open stream for resource {0} at {1}: {2}

Cause: Failed to open specified resource as a stream

Action: IOException is thrown
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04024: New {0} created:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04025: {0}Parent classloader is a {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04026: Creating embedded WLST environment with {0} = {1} and {2} = {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04027: Failed to create embedded WLST environment: {0}

Cause: MalformedURLException is thrown while initializing the WLST classpath

Action: throws RuntimeException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04028: Initializing embedded WLST classpath with {0} elements:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04029: {0}classpath[{1}] = {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04030: Unable to load interpreter class {0}: {1}

Cause: ClassNotFoundException is thrown while trying to load the embedded WLST interpreter

Action: throws InterpreterCreationFailedException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04031: Creating a new instance of the embedded WLST interpreter

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04032: New instance of the embedded WLST interpreter created

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04033: Unable to create new embedded WLST interpreter: {0}

Cause: Exception is thrown while creating a new embedded WLST interpreter

Action: throws InterpreterCreationFailedException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04034: Initializing the new embedded WLST interpreter

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04035: New embedded WLST interpreter initialized

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04036: Unable to initialize new embedded WLST interpreter: {0}

Cause: Exception is thrown while initializing a new embedded WLST interpreter

Action: throws InterpreterCreationFailedException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04037: {0}() returned {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04038: {0}({1}) returned {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04039: {0}({1}, {2}) returned {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04040: {0}() completed successfully

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04041: {0}({1}) completed successfully

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04042: {0}({1}, {2}) completed successfully

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04043: Interpreter.getAsJavaObject({0}, {1}) call failed: {2}

Cause: Exception is thrown during call to embedded WLST interpreter

Action: throws InterpreterInvocationFailedException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04044: Interpreter.set({0}, {1}) call failed: {2}

Cause: Exception is thrown during call to embedded WLST interpreter

Action: throws InterpreterInvocationFailedException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04045: Interpreter.setAsPyObject({0}. {1}) call failed: {2}

Cause: Exception is thrown during call to embedded WLST interpreter

Action: throws InterpreterInvocationFailedException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04046: Interpreter.exec({0}) call failed: {1}

Cause: Exception is thrown during call to embedded WLST interpreter

Action: throws InterpreterInvocationFailedException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04047: Interpreter.execfile({0}) call failed: {1}

Cause: Exception is thrown during call to embedded WLST interpreter

Action: throws InterpreterInvocationFailedException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04048: Interpreter.cleanup() call failed: {0}

Cause: Exception is thrown during call to embedded WLST interpreter

Action: throws InterpreterInvocationFailedException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04049: Interpreter.setWlstEnv() call failed: {0}

Cause: Exception is thrown during call to embedded WLST interpreter

Action: throws InterpreterInvocationFailedException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04050: Setting the active embedded WLST interpreter to {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04051: WLST dependency jar loading is disabled because Java System property wlst.disablePluginJarLoadingMode is set to true

Cause: System property wlst.disablePluginJarLoadingMode is set to true

Action: Remove system property wlst.disablePluginJarLoadingMode
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04501: Starting WLST interpreter

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04502: {0} classloader is {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04503: WLSTInterpreter classloader not a child of the EmbeddedWLSTInterpreter classloader so setting interpreter classloader to {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04504: WLSTInterpreter classloader is a child of the EmbeddedWLSTInterpreter classloader so skipping setting interpreter classloader

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04505: {0} classpath element {1} = {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04506: WLST interpreter started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04507: {0} failed to convert return value into specified type {1}

Cause: Could not convert return value into specified type

Action: PyConversionErrorException is thrown
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04508: Embedded WLST interpreter was already closed

Cause: Embedded WLST interpreter was already closed when the method was invoked

Action: InterpreterAlreadyClosedException is thrown
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04509: Calling {0}()

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04510: Calling {0}({1})

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04511: Calling {0}({1}, {2})

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-04512: {0} call failed with AttributeError: {1}

Cause: Python AttributeError thrown from WLST interpreter

Action: PyAttributeErrorException is thrown
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04513: {0} call failed with NameError: {1}

Cause: Python NameError thrown from WLST interpreter

Action: PyNameErrorException is thrown
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04514: {0} call failed with TypeError: {1}

Cause: Python TypeError thrown from WLST interpreter

Action: PyTypeErrorException is thrown
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04515: {0} call failed with SyntaxError: {1}

Cause: Python SyntaxError thrown from WLST interpreter

Action: PySyntaxErrorException is thrown
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04516: {0} call failed with IndentationError: {1}

Cause: Python IndentationError thrown from WLST interpreter

Action: PyIndentationErrorException is thrown
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04517: {0} call failed with {1}

Cause: Python Error thrown from WLST interpreter

Action: PyGenericErrorException is thrown
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04518: The EmbeddedWLSTInterpreter class was loaded by the wrong classloader: expected {0}, actual {1}.

Cause: wlst-impl.jar was mistakenly added to the system classpath. Please ensure that the wlst-impl.jar is not on the system CLASSPATH.

Action: InterpreterRuntimeException is thrown
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-04519: {0} call failed with ImportError: {1}

Cause: Python Error thrown from WLST interpreter

Action: PyImportErrorException is thrown
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-06001: Completed successfully

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-06002: Failed

Cause: A failure occurred during action execution

Action: Refer to the detailed message which was returned to the caller
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-06003: Started Action

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-06004: Finished Action

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-06005: Calling the component {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-06006: Calling the component {0} and logging will now performed using named logger {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-06007: Resuming execution upon the return from the component {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-06008: Log this very important sample message at INFO level.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-06009: Reading domain...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-06010: Selecting template...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-06011: Loading template...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-06012: Updating domain...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-06013: Closing domain...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-06501: The EnvironmentModel parameter must be supplied.

Cause: The EnvironmentModel parameter must be supplied.

Action: Specify a valid EnvironmentModel parameter when calling the action
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-06502: The EnvironmentModelTarget parameter must be supplied and contain at least one valid EnvironmentModelTarget.

Cause: The EnvironmentModelTarget parameter must be supplied and contain at least one valid EnvironmentModelTarget.

Action: Supply an appropriate EnvironmentModelTarget parameter when calling the action
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-06503: The action requires valid Credentials set on the EnvironmentModel to complete successfully.

Cause: The action requires valid Credentials set on the EnvironmentModel to complete successfully.

Action: Supply and appropriate Credentials parameters when calling the action
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-06504: The action requires a valid Topology set on the EnvironmentModel to complete successfully.

Cause: The action requires a valid Topology set on the EnvironmentModel to complete successfully.

Action: Supply an appropriate Topology parameters when calling the action
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-06505: Stopping {0} "{1}"

Cause: The process to stop an environment element is beginning

Action: None
Level: 3

Type: INFO

Impact: Other

FMWPLATFORM-06506: Stopping {0} "{1}" on {2} "{3}"

Cause: The process to stop an environment element is beginning on a specified containing element

Action: None
Level: 3

Type: INFO

Impact: Other

FMWPLATFORM-06507: Stopped {0} "{1}"

Cause: The process to stop an environment element has completed

Action: None
Level: 3

Type: INFO

Impact: Other

FMWPLATFORM-06508: Unable to stop {0} "{1}" {2}

Cause: The process to stop an environment element has failed

Action: Identify the cause of the failure from the message provided and correct it
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06509: Starting {0} "{1}"

Cause: The process to start an environment element is beginning

Action: None
Level: 3

Type: INFO

Impact: Other

FMWPLATFORM-06510: Starting {0} "{1}" on {2} "{3}"

Cause: The process to start an environment element is beginning on a specified containing element

Action: None
Level: 3

Type: INFO

Impact: Other

FMWPLATFORM-06511: Started {0} "{1}"

Cause: The process to start an environment element has completed

Action: None
Level: 3

Type: INFO

Impact: Other

FMWPLATFORM-06512: Unable to start {0} "{1}" {2}

Cause: The process to start an environment element has failed

Action: Identify the cause of the failure from the message provided and correct it
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06513: No ScopeType was specified for Scope "{0}"

Cause: If a Scope is specified in an EnvironmentModelTarget then a ScopeType is also required

Action: Add a ScopeType to the specified Scope
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06514: ScopeType must be either "Server" or "Cluster" but found "{0}" instead

Cause: A ScopeType other than "Server" or "Cluster" was found

Action: Correct the ScopeType value in the EnvironmentModelTarget
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06515: No result was produced from the action

Cause: A result is expected to be returned from an action but the action failed to return one

Action: Examine the log to determine why the action did not return a result
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06516: Could not find a Server Binding for "{0}"

Cause: The Server Binding for the specified Environment Element could not be found

Action: The Topology must be updated to include a Server Binding for the specified Environment Element
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06517: An EnironmentModelTarget must always specify a TargetId

Cause: An EnironmentModelTarget must always specify TargetId

Action: Identify the cause of the failure from the message provided and correct it
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06518: The TargetId "{0}" could not be found as a Domain, Host or OracleHome in the Topology

Cause: The specified TargetId must be either a Domain, Host or OracleHome in the Topology

Action: Either the TargetId is incorrect or the Topology needs to be updated to include the TargetId specified
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06519: Unable to find the Admin Server for Domain "{0}"

Cause: Unable to find the Admin Server for the specified Domain

Action: Identify the cause of the failure from the message provided and correct it
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06520: No Domains found for Host "{0}"

Cause: No Domains are configured for the Host specified

Action: Examine the configuration for the Host to determine if Domains need to be configured
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06521: Timeout trying to connect to NodeManager "{0}": "{1}"

Cause: Timeout trying to connect to the NodeManager specified

Action: Make sure that the NodeManager has been started and that the identifier is correct
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06522: Unable to start the Admin Server "{0}" for Domain "{1}": "{2}"

Cause: Unable to start the Admin Server for the specified Domain

Action:
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06523: Started the Admin Server for Domain "{0}"

Cause: Started the Admin Server for the specified Domain

Action:
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06524: Unable to find the NodeManager for Domain "{0}"

Cause: Unable to find the NodeManager for specified Domain

Action: None
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06525: Unable to find the Tuning Parameters for {0} "{1}"

Cause: Unable to find the Tuning Parameters for the environment element specified

Action: None
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06526: Unable to find the appropriate Credential for {0} with Credential reference "{1}"

Cause: Unable to find the appropriate Credential based on the Credential reference specified

Action: None
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06527: Connected to Admin Server "{0}"

Cause: Connected to Admin Server

Action: None
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06528: Connected to NodeManager

Cause: Connected to NodeManager

Action: None
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06529: Admin Server connect failed : {0}

Cause: Admin Server connect failed

Action: None
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-06530: NodeManager connect failed : {0}

Cause: NodeManager connected

Action: None
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-07002: A domain could not be identified for target {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-07003: An error occurred executing readDomain().

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-07004: An error occurred executing selectTemplate().

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-07005: An error occurred executing loadTemplates().

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-07006: An error occurred executing updateDomain().

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-07007: An error occurred executing closeDomain().

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-07008: ApplyTemplate.invokeAction completed successfully.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-07009: The parameters envModel and targets are required.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-07010: The attribute topology from envModel is required.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-07011: The extra parameter {0} is required.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-07012: The ApplyTemplate action is only applicable for a single target.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-07013: The ApplyTemplate action requires that the target be specified.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-07014: The ApplyTemplate action requires that the scope attribute on target be specified.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-07015: The ApplyTemplate action requires that the type attribute on target is be specified.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-07016: The ApplyTemplate action is only applicable with {0} targets.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08001: Found a null ID

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08003: Duplicate {0} ID found: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08004: More than one admin server found in domain {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08005: No admin server found in domain: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08006: {0} is null in Domain {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08007: {0} name is null or empty in Domain {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08008: {0} is null or its ID or name is null in Domain {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08009: {0} has a null or empty reference in Domain {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08010: Duplicate {0} name found: {1} in Domain {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08011: Duplicate bindings found for {0} with ID {1} in Domain {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08012: No binding in Domain {0} for {1} with ID {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08013: No bindings found in Domain {0} for {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08014: Binding found in Domain {0} with name {1} for a {2} with ID {3} but no such {2} found

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08015: ID is null or empty for {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08016: Failed to read file object from String {0}

Cause: IO error in reading string as a filestream

Action: Check IO
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08017: No listen port in Server Binding with name {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08018: {0} ID is null or empty in Domain {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08019: Template is marked as custom but no location is specified

Cause: Location of the template not specified for the custom template

Action: Set location on the template
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08020: Alias Mapping for Tuning Parameters cannot be retrieved since its entity type is not known

Cause: Tried to retrieve Alias mapping for Tuning Parameters but its Entity type is not set

Action: Set references on the Tuning Parameters to set its entity type
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08021: Setting is null for Tuning Parameters

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-08022: Invalid alias {0} in Setting in Tuning Parameters

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-08023: Tuning Parameters Setting with alias {0} and value {1} is not of expected type {2}

Cause: Tuning Parameters setting has a value that does not match the data type expected for that setting

Action: Correct the value of the setting
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08024: Schema with Component Id Reference {0} does not reference a database

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08025: Tuning Parameters for {0} have a Setting with an invalid alias {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08026: Tuning parameters has a setting with alias {0} and value {1} that should be of type CREDENTIAL_ID but does not match a credential with username

Cause: Setting of type CREDENTIAL_ID has a value that does not match a credential with username

Action: Change the value of the Setting to a credential with username
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08027: Tuning parameters has a setting with alias {0} and value {1} that should be of type {2} but no matching credential object found

Cause: Setting of type CREDENTIAL_ID or CREDENTIAL_SECRET has a value that does not match any credential in the model

Action: Change the value of the Setting to a valid credential reference
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08028: Tuning parameters has a setting with alias {0} and value {1} that should be of type {2} but no credentials found in the model

Cause: Setting of type CREDENTIAL_ID or CREDENTIAL_SECRET found but no credentials found in the model

Action: Set credentials in the model
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08029: Failed to read file {0} {1}

Cause: IO Exception in reading the file

Action: Check that file exists and is readable
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08030: Failed to write file {0} {1}

Cause: IO Exception in writing to a file

Action: Check that file can be written into filesystem
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08031: {0} with ID or name {1} has a credential reference {2} which is not found in the credentials in the model

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08032: {0} with ID or name {1} has a null credential reference

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08033: Schema with Component Id Reference {0} has a credential reference {1} which is not found in the credentials in the model

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08034: Schema with Component Id Reference {0} has a null credential reference

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08035: MappedDomain with ID {0} in host {1} is not associated with any domain

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08036: MappedDomain with ID {0} in host {1}, for domain {2} has server reference {3} that is not found in the domain

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08037: Data Source Names defined in Schemas in Domain {0} - {1} do not match the ones defined in the Templates - {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08038: Unable to get template reporter at path {0} due to exception {1}

Cause: Exception in getting TemplateReporter

Action: Check the oracle home path for the domain or check the exception msg for more details
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08039: Error in template {0} retrieval: {1}

Cause: Exception in retrieval of template

Action: Check the template files or check the exception msg for more details
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08040: Error in template {0} loading: {1}

Cause: Exception in loading template

Action: Check the template files or check the exception msg for more details
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08041: Tried to setParent() on a Tunable entity with the incorrect type. Expected object of type {0} but found {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08042: Tried to replace variable %x% in string {0} but could not find the value to replace with in map {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08500: Cannot start an embedded WLST session {0}

Cause: Exception in starting embedded WLST

Action: Check the OracleHome path variables in the EnvironmentModel or OracleHome is not compatible for embedded WLST
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08501: Cannot close the embedded WLST session {0}

Cause: Exception in closing embedded WLST

Action: Check the OracleHome path variables in the EnvironmentModel or OracleHome is not compatible for embedded WLST
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08502: Generic Python Error

Cause: PyGenericErrorException is thrown

Action: throws BadActionException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08503: Generic Interpreter exception

Cause: InterpreterException is thrown

Action: throws InternalErrorException
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08504: Cannot load the {0} WLST module {1}

Cause: Exception in loading the environment discovery python module from the classpath

Action: Check the OracleHome path variables in the EnvironmentModel or OracleHome is not compatible for embedded WLST
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08505: Cannot read domain {0} {1}

Cause: Exception in reading the WebLogic Domain, offline mode

Action: Check the Domain path in the EnvironmentModel
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08506: Cannot close domain {0}

Cause: Exception in closing the WebLogic Domain, offline mode

Action: Check the OracleHome
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08507: Cannot connect to domain with url: {0} and username: {1} {2}

Cause: Exception in connecting to the WebLogic Domain, online mode

Action: Check the adminUrl and credentials in the EnvironmentModel
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08508: Cannot disconnect from domain {0}

Cause: Exception in disconnecting from the WebLogic Domain, online mode

Action: Check the OracleHome
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08509: Cannot retrieve the value of attribute {0} in WLST offline mode

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-08510: Loading of {0} jython module was successful

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08511: Result of the echo jython method is {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08512: WLST Found {0} of type {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08513: WLST Offline exception for {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08514: EnvironmentTarget with type {0} does not match with requested Environment {1}

Cause: Provided EnvironmentTarget Type does not match with the requested discovery

Action: Change the EnvironmentTarget
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08515: Expected parameter {0} should not be null in this EnvironmentTarget type

Cause: EnvironmentTarget parameter(s) cannot be null

Action: Provide all the EnvironmentTarget parameter(s)
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08516: EnvironmentTarget cannot be empty

Cause: EnvironmentTarget cannot be null

Action: Provide an EnvironmentTarget
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08517: EnvironmentTarget with {0} as domainId cannot be found in the topology object

Cause: Cannot find the Topology domain in the EnvironmentModel

Action: Check the EnvironmentTarget domain id parameter matches with the id of a Topology Domain
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08518: Cannot find path in the topology OracleHome object

Cause: Cannot find the path in the OracleHome Topology object

Action: Provide the OracleHome path with an EnvironmentModelBuilder bootstrap method or update the topology
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08519: Cannot find domain path in the topology domain object

Cause: Cannot find the path in the WebLogic Domain Topology object

Action: Provide the Domain path with an EnvironmentModelBuilder bootstrap method or update the topology
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08520: Cannot find domain admin url in the topology domain object

Cause: Cannot find the adminUrl in the WebLogic Domain Topology object

Action: Provide the adminUrl with an EnvironmentModelBuilder bootstrap method or update the topology
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08521: Cannot find admin credential reference in the topology domain object

Cause: Cannot find the admin credential reference in the WebLogic Domain Topology object

Action: Provide the admin credential reference with an EnvironmentModelBuilder bootstrap method or update the topology
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08522: Cannot find credential with {0} as reference

Cause: Cannot find the user credential in the Credentials object

Action: Add an user credential or update admin credential reference in the WebLogic Domain Topology object
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08523: Found credential with {0} as reference is not an UserPassword Credential

Cause: Cannot find the user credential in the Credentials object

Action: Add an user credential or update admin credential reference in the WebLogic Domain Topology object
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08524: Found credential with {0} as reference has an empty username or password

Cause: The username or password of the Credentials object cannot be empty

Action: Add an user credential with a username and password
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08525: Credential is empty

Cause: Credential parameter cannot be empty

Action: Add an user credential to the EnvironmentBuilder bootstrap methods
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08526: Oracle home cannot be empty

Cause: Oracle Home parameter cannot be empty

Action: Add an Oracle Home path to the EnvironmentBuilder bootstrap methods
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08527: Oracle domain attributes cannot be empty

Cause: The WebLogic Domain parameter cannot be empty

Action: Add all the WebLogic Domain parameters to the EnvironmentBuilder bootstrap methods
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08528: ID reference cannot be empty

Cause: The id parameter cannot be empty

Action: Add the id parameter to the EnvironmentBuilder bootstrap methods
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08529: Found a {0} filter with {1} as value

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08530: Retrieve all the bootstrap parameters from the Topology

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08531: Got all bootstrap parameters and are valid

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08532: Try to start embedded WLST and make a connection to the domain

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08533: Successful made a connection to the domain

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08534: Environment model cannot be empty

Cause: The EnvironmentModel parameter cannot be empty

Action: Add the EnvironmentModel parameter to the EnvironmentBuilder bootstrap methods
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08535: Oracle home path cannot be empty

Cause: The OracleHome path parameter cannot be empty

Action: Add the OracleHome path parameter to the EnvironmentBuilder bootstrap methods
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08536: Domain path already contains a value

Cause: The path of the WebLogic Domain already contains a value

Action: Do not update the path of the WebLogic Domain in the topology object
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08537: Cannot find a host in this environment model

Cause: Cannot find a host in the topology object

Action: Use one of the EnvironmentBuilder bootstrap methods to add the right bootstrap information
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08538: Cannot find an Oracle Home in this environment model

Cause: Cannot find an OracleHome in the topology object

Action: Use one of the EnvironmentBuilder bootstrap methods to add the right bootstrap information
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08539: Cannot find an domain with this {0} as id in this environment model

Cause: Cannot find an WebLogic Domain with this ID in the topology object

Action: Change the id of the EnvironmentTarget or use one of the EnvironmentBuilder bootstrap methods
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08540: Cannot find an host mapping, together with an Oracle home and domain id {0} in this environment model

Cause: Cannot find an Host mapping together with an OracleHome and a WebLogic Domain in the topology object

Action: Use one of the EnvironmentBuilder bootstrap methods to add the right bootstrap information
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08541: Cannot find an host mapping, together with an Oracle home and domain id {0} in this environment model

Cause: Cannot find an Host mapping together with an OracleHome and a WebLogic Domain in the topology object

Action: Use one of the EnvironmentBuilder bootstrap methods to add the right bootstrap information
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08542: Domain admin url already contains a value

Cause: The adminUrl of the WebLogic Domain already contains a value

Action: Do not update the adminUrl of the WebLogic Domain in the topology object
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08543: Domain admin credential ref already contains a value

Cause: The admin credential reference of the WebLogic Domain already contains a value

Action: Do not update the admin credential reference of the WebLogic Domain in the topology object
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08544: Cannot find credentials on the Environment Model

Cause: Credentials cannot be empty on the EnvironmentModel

Action: Provide the credentials to the EnvironmentModel object
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08545: Discovery of the OracleHome failed {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-08546: Discovery of a WebLogic Domain in offline mode failed {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-08547: Discovery of a WebLogic Domain in online mode failed {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-08548: Try to discover the OracleHome and its WebLogic Domains

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08549: The discovery of the OracleHome and the WebLogic Domains has stopped because of this target type {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08550: End of the Environment discovery

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08551: Try to discover all the OracleHome information

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08552: Try to discover a WebLogic Domain in offline mode

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08553: Try to discover a WebLogic Domain in online mode

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08554: Unknown envType class parameter value

Cause: EnvType parameter contains an unknown value

Action: Provide the right class name to the EnvType parameter
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08555: Unknown {0} class for adding tuning parameters

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-08556: Did not find the WLST {1} alias mapping for class {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-08557: Invoke method {1} class {0} went wrong {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-08558: Cannot find method {1} class {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-08559: envType class parameter cannot be null

Cause: EnvType parameter cannot be empty

Action: Provide a class name to the EnvType parameter
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08560: Could not determine the database vendor for this datasource drivername {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-08561: Could not extract the hostname,database and portnumber details for this datasource jdbc url {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-08562: Could not process the following datasource {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-08563: WLST Domain discovery in {0} mode failed {1}

Cause: The Domain part in the WebLogic Domain discovery failed

Action: Check the domain part of the WebLogic Domain
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08564: WLST Managed Server discovery in {0} mode failed {1}

Cause: The Server part in the WebLogic Domain discovery failed

Action: Check the managed server part of the WebLogic Domain
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08565: WLST Cluster discovery in {0} mode failed {1}

Cause: The Cluster part in the WebLogic Domain discovery failed

Action: Check the cluster part of the WebLogic Domain
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08566: WLST Datasource discovery in {0} mode failed {1}

Cause: The Datasource part in the WebLogic Domain discovery failed

Action: Check the datasource part of the WebLogic Domain
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08567: WLST Node Manager discovery in {0} mode failed {1}

Cause: The Node Manager part in the WebLogic Domain discovery failed

Action: Check the Node Manager part of the WebLogic Domain
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08568: Not a valid WebLogic managed server url {0}

Cause: The WebLogic Domain t3 url is not valid

Action: Change the adminUrl to a valid t3 url
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08569: Discover WebLogic domain step with refreshOnly is {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08570: Discover WebLogic Node Managers/machines step with refreshOnly is {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08571: Discover WebLogic managed servers step with refreshOnly is {0}, EnvironmentTarget type is domain

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08572: Discover WebLogic clusters step with refreshOnly is {0}, EnvironmentTarget type is domain

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08573: Discover WebLogic cluster managed servers step with refreshOnly is {0}, EnvironmentTarget type is cluster

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08574: Discover WebLogic cluster step with refreshOnly is {0}, EnvironmentTarget type is cluster

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08575: Discover WebLogic datasources step with refreshOnly is {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08576: Discover WebLogic managed server with refreshOnly is {0}, EnvironmentTarget type is server

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08577: Found datasource {0} with JDBC connect url {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08578: Create a Topology Database object {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08579: Found an existing Topology Database object {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08580: Datasource vendor is {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08581: Found an existing Topology Domain Schema object based on Database {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08583: Create a Topology Domain Schema object based on Database {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08584: Found DatasourceBinding {0} on Schema object based on Database {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08585: Add a DatasourceBinding {1} to Schema object based on Database {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08586: Update all tuning parameters for DatasourceBinding {1} and Schema object based on Database {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08587: Refresh only existing tuning parameters for DatasourceBinding {1} and Schema object based on Database {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08588: Update all tuning parameters of the Topology Domain

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08589: Refresh only existing tuning parameters of the Topology Domain

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08590: Add a ClusterBinding {1} to Domain object {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08591: Refresh only existing tuning parameters for ClusterBinding {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08592: Update all tuning parameters for ClusterBinding {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08593: Add Cluster {0} to the Domain profile object

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08594: Update Cluster {0} on the Domain profile object

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08595: Add Server {0} to the Domain profile object

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08596: Update Server {0} on the Domain profile object

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08597: Refresh only existing tuning parameters for ServerBinding {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08598: Update all tuning parameters for ServerBinding {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08599: Add a ServerBinding {1} to Domain object {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08600: Add a ServerBinding {1} to Domain object {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08601: Add a server reference {0} to Domain {1} on OracleHome {2} on Host {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08602: Create a Topology Node Manager object {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08603: Found an existing Topology Node Manager object {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08604: Update all tuning parameters for Node Manager object {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08605: Refresh only existing tuning parameters for Node Manager object {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08606: Create a Topology Host object {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08607: Found an existing Topology Host object {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08608: Add a OracleHome mapping for OracleHome {1} on Host {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08609: Add a Domain mapping for Domain {2} with OracleHome {1} on Host {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08610: Create a Topology object {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08611: Add Domain {1} to Topology object {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08612: Add OracleHome {1} to Topology object {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08613: Add Host {1} to Topology object {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08614: Add Node Manager {0} to Domain mapping {1} OracleHome mapping {2} on Host {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08615: Failed to write object to String {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08616: Resource reference is not initialized properly for {0} model file for {1} version {2}

Cause: Initialization error

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08617: Unable to locate {0} model file for {1} version {2}

Cause: The specified model file was not found

Action: Check if the file exists
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08618: Couldn't find pattern {0} in {1}

Cause: The given url doesn't match the jdbc url pattern

Action: Check if the given url adheres to the jdbc url pattern
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08620: Could not read Alias Lookup information for validating tuning parameters

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08621: Path to oracle home not defined for domain in the host mapping. Hence, cannot read templates to validate data source names

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08622: Could not read settings for tuning parameters in {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-08623: Number can't start with 0 - {0}

Cause: Version number (major, minor and incremental) cannot start with zero

Action: Check and fix the version number
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08624: Unable to load Blueprint "{0}" with version "{1}"

Cause: Could not find the Blueprint in the search path

Action: Make sure that the Blueprint file with the specified version is located in the search path
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08625: Unable to load DomainProfile "{0}" with version "{1}"

Cause: Could not find the DomainProfile in the search path

Action: Make sure that the DomainProfile file with the specified version is located in the search path
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08626: Unable to load TuningParameters "{0}" with version "{1}"

Cause: Could not find the TuningParameters in the search path

Action: Make sure that the TuningParameters file with the specified version is located in the search path
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08627: The Blueprint "{0}" must be written to a file prior to writing out its parent model element

Cause: A parent of a Blueprint element was expecting to be able to use a resource reference for the Blueprint

Action: Write the Blueprint to a file using the writing mechanisms provide by Envspec
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08628: The DomainProfile "{0}" must be written to a file prior to writing out its parent model element

Cause: A parent of a DomainProfile element was expecting to be able to use a resource reference for the DomainProfile

Action: Write the DomainProfile to a file using the writing mechanisms provide by Envspec
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-08629: The TuningParemeters "{0}" must be written to a file prior to writing out its parent model element

Cause: A parent of a TuningParameters element was expecting to be able to use a resource reference for the TuningParemeters

Action: Write the TuningParameters to a file using the writing mechanisms provide by Envspec
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-10001: Usage: java -Dtopology.file=<directory and topology filename> -Dcredentials.location=<directory of wallet> -Dcredentials.password=<wallet password> -Dmodel.target=<domain id> [-Dstandard.action=<action name> -Dschema.password=<shared schema wallet password> -Dschema.location=<shared schema location of wallet>]

Cause: Invalid command line parameters. (Used in testing only)

Action: Read usage statement and correct command line Parameters
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10002: Calling component {0}

Cause: About to call another component

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-10003: Returned from calling component {0}

Cause: Returned from calling another component

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-10005: No domain found in the model for the target {0}

Cause: Domain not located in the model for the provided domain target

Action: Verify the target id and the model for the domain
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10006: Database credential not found for credential alias {0}

Cause: The credential for the database is not found in the credentials

Action: Verify the credential ref or add the credential to the credentials
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10007: Standard actions require a valid environment model

Cause: Standard action was requested without a model

Action: Provide the standard action required environment model
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10008: Severe exception encountered during environment model validation. Exception details {0}

Cause: Exception during environment model validation

Action: Correct based on the details of the validation exception
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10009: Oracle Home with name {0} does not exist at location {1}

Cause: Oracle Home does not exist at the indicated location

Action: Correct the environment model
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10010: Domain {0} is not accessible at location {1}

Cause: Domain directory is not accessible

Action: Check the permissions and structure of the indicated model directory
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10011: Domain {0} already exists at location {1}

Cause: Domain directory already exists

Action: Correct the environment model or remove the existing domain
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10013: Cannot open the shared schema credentials file with the provided password and location {0}

Cause: Cannot open the shared schema credentials file

Action: Check the provided location and password
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10014: Unknown or missing standard action name {0}

Cause: Unable to perform validation routine

Action: Internal error
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10015: Oracle Home not found for domain {0}

Cause: Oracle Home not found for the indicated target domain

Action: Correct the environment model
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10016: Shared schema options require both the the wallet location and wallet password

Cause: Invalid shared schema options

Action: Provide both the wallet location and wallet password
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10017: The directory {0} provided for the shared schema wallet option is invalid

Cause: Invalid shared schema wallet location

Action: Provide both a valid directory for the shared schema wallet
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10020: Successfully completed action {0} for domain target {1}

Cause: Successfully completed action

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-10021: Action {0} was unsuccessful for domain target {1}

Cause: Action completed unsuccessfully

Action: Check result message and logs
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-10101: RCU command script not found in the Oracle Home location {0}

Cause: Unable to locate the RCU script in the Oracle Home

Action: Check that the model has the correct Oracle Home installation
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10102: Unable to generate the password file stream : {0}

Cause: Unable to generate the password file for the schema standard action

Action: Check the exception message. This is potentially a transient problem. Retry action
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10103: Unable to complete the RCU action : {0}

Cause: Exception thrown from the RCU script invocation

Action: Check the exception message and correct based on its contents
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10104: Unable to complete the RCU action : {0}

Cause: script invocation returned with invalid return code

Action: Check the exception messages return in result
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10106: Schema action {0} is not supported

Cause: Schema standard action not supported

Action: Check the documentation for supported actions
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10107: Invalid role {0} specified for the schema standard action {1}

Cause: Invalid Role for the schema standard action

Action: Check the RCU documentation for valid role values
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10108: Unable to locate the database in the model for the schema {0}

Cause: Unable to find the database for the schema in the model

Action: Verify the database reference id in the schema or add the database entry
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10109: Conflicting configuration information xml file found for database {0} and prefix {1}

Cause: Multiple configuration info files found for the database and schema prefix components

Action: Correct the schema in the model
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10110: Cannot perform standard actions against shared schema for domain {0}

Cause: Attempting to perform a schema standard action against a shared schema

Action: Cannot use the schema standard actions to manipulate shared schema. Use external RCU process
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10111: Cannot perform schema action against database {0} prefix {1} which has a shared schema

Cause: Attempting to perform a schema action against a database and prefix for which the model contains at least one shared schema

Action: Correct the schema in the model
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10112: Schema standard action {0} requires schema for the domain

Cause: Requesting a schema standard action for a domain that contains no schema

Action: Correct the the model
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10113: RCU script not found or is not executable from Oracle Home {0}

Cause: The RCU script not found or not executable in the domain Oracle Home

Action: Check the model and Oracle Home
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10114: Schema action requires a database role with SYSDBA privileges

Cause: The schema standard action requires SYSDBA privileges

Action: Change the standard action or provide a database role with correct privileges
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10201: Unexpected exception occurred on script invocation

Cause: Exception running script from java process

Action: Check the exception message details
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10202: Unable to write to script process standard files {0}

Cause: Exception running script from java process

Action: Check the exception message details
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10203: WLST scripting standard action {0} returned an unexpected exception {1}

Cause: Exception incurred invoking wlst standard action

Action: Check the exception message details
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10204: Action Initialization failed with exception {0}

Cause: Action initialization failed

Action: Check the exception message details
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10205: Unable to access file system for directory validation. Exception details {1}

Cause: Validation failure on directory

Action: Check the exception message details
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-10206: Internal error attempting to access file {0}. Unable to continue

Cause: Unable to read the provided file stream

Action: Internal error
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11006: Cannot open the shared schema credentials file with the provided password and location {0}. Exception Information {1}

Cause: Cannot open the shared schema credentials file

Action: Check the provided location and password
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11007: Administration credentials required when creating domain. Exception information {0}

Cause: Unable to apply the administration credentials to the domain

Action: Provide an valid credentials for the administration server
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11008: Unable to read the newly created domain at location {0}. Exception information: {1}

Cause: Unable to read the newly created domain

Action: Correct error as indicated from exception
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11009: Error creating cluster {0}. Exception information: {1}

Cause: Error creating the cluster

Action: Correct error as indicated from exception
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11010: Error creating server {0}. Exception information: {1}

Cause: Error creating the server

Action: Correct error as indicated from exception
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11011: Error assigning server {0} to node manager machine {1}. Exception information: {2}

Cause: Error assigning server to machine

Action: Correct error as indicated from exception
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11012: Error assigning server {0} to cluster {1}. Exception information: {2}

Cause: Error assigning server to cluster

Action: Correct error as indicated from exception
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11013: Error creating machine {0}. Exception information: {1}

Cause: Error creating machine

Action: Correct error as indicated from exception
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11014: Error creating node manager {0}. Exception information: {1}

Cause: Error creating node manager

Action: Correct error as indicated from exception
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11015: domain creation failed with exception {0}

Cause: Unable to create the domain with the create domain or update domain action

Action: Correct error as indicated from exception
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-11016: Unable to create node {0} at location {1}. Exception information: {2}

Cause: Unable to create the mbean node location

Action: Correct error as indicated from exception
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11017: Unable to create attribute with alias {0} at location {1}. Exception information: {2}

Cause: Unable to set the tuning parameter at the attribute location

Action: Correct error as indicated from exception
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11018: Unable to load the selected templates. Exception information: {0}

Cause: Unable to load and apply the selected templates

Action: Correct error as indicated from exception
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11019: Server {0} is not mapped to a domain node manager

Cause: Server is not mapped to a domain node manager

Action: Validate this is the expectation
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-11020: No base template selected for create domain action

Cause: No base template has been applied for create domain

Action: Validate this is expected behavior
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-11021: Unable to set server {0} listen port to {1}. Exception information: {2}

Cause: Unable to set the server listen port

Action: Validate the listen port value in the environment model
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11022: Unable to set server {0} listen address to {1}. Exception information: {2}

Cause: Unable to set the server listen address

Action: Validate the listen address value in the environment model
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11023: Unable to set data source {0} user to {1}. Exception information: {2}

Cause: Unable to set the data source user name

Action: Check the value in the environment model and look at the details of the exception
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11024: Schema credential is required for data source {0}

Cause: Schema credential required when creating data source

Action: Add a credential to the environment model
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11025: Unable to remove server {0} from domain.

Cause: Unable to remove a server from the domain. Ignore error and continue

Action: Check the result of the standard action for this server
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-11026: Unable to remove cluster {0} from domain.

Cause: Unable to remove a cluster and its servers from the domain. Ignore error and continue

Action: Check the result of the standard action for this cluster
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-11027: Unable to remove data source {0} from domain.

Cause: Unable to remove the data source when preparing for a multi data source configuration. Ignore error and continue

Action: Check the result of the standard action for the multi data source configuration.
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-11028: Data source {0} does not exist after applying product template

Cause: The data source should have existed after applying the product template

Action: None
Level: 1

Type: INFO

Impact: Other

FMWPLATFORM-11029: Unable to add data source list to domain. Exception information: {0}

Cause: Unable to add the list of data sources to the domain

Action: Check the exception information and the environment model configuration
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11030: Unable to add the target list to the data source {0}. Exception information: {1}

Cause: Unable to add the target list to the data source

Action: Check the exception information and the environment model configuration
Level: 1

Type: SEVERE

Impact: Other

FMWPLATFORM-11031: Unable to apply the template {0} to the domain. Exception information: {1}

Cause: Unable to apply the template to the domain

Action: Check the exception information and the environment model configuration
Level: 1

Type: WARNING

Impact: Other

FMWPLATFORM-12001: Unable to create wallet {0}

Cause: An OracleSecretStoreException or IOException occurred when tried to create a new OracleWallet file.

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12002: Exception saving wallet store {0}

Cause: An OracleSecretStoreException or IOException occurred when tried to save an OracleWallet file.

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12003: Removed credential from wallet with credential name {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-12004: Problem retrieving credentials from wallet store {0}

Cause: An OracleSecretStoreException occurred when tried to retrieve a credential from credentialStore.

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12005: Deleted wallet at location {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-12006: Unable to delete wallet {0}

Cause: An IOException occurred when tried to delete an Oracle Wallet file.

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12007: Unable to locate wallet {0}

Cause: An OracleSecretStoreException occurred when tried to retrieve the credentialStore from OracleWallet.

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12008: Unable to create credential in wallet

Cause: An OracleSecretStoreException occurred when tried to create a credential in credentialStore.

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12009: Unable to delete credential from wallet

Cause: An OracleSecretStoreException occurred when tried to delete a credential from credentialStore.

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12010: Cannot open wallet {0}

Cause: An IOException occurred when tried to open or create an Oracle Wallet file.

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12011: Invalid file path

Cause: The wallet file directory is not a valid file directory.

Action: Specify a correct file directory.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12012: Cannot load a wallet with a current wallet has not been saved

Cause:

Action:
Level: 10

Type: WARNING

Impact: Other

FMWPLATFORM-12013: Could not delete key with name as null

Cause: The alias key being deleted does not exist in the wallet file.

Action: Specify a correct alias key.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12014: Could not create a new wallet as wallet already exist

Cause: The new wallet file being created already exists in the file directory.

Action: Specify a different wallet file directory.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12015: Wallet cannot be deleted because it does not exist at location {0}

Cause: The Wallet file does not exist in the file directory.

Action: Specify a different wallet file directory.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12016: Cannot add a new credential with duplicated alias {0}

Cause: The credential alias field already exist in credential store.

Action: Specify a different alias name.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12017: Cannot update credential, alias {0} does not exist

Cause: The credential alias field does not exist in credential store.

Action: Specify a correct alias name.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12018: alias is required when creating or updating credential.

Cause: The credential alias field is missing when instantiate a Credential object.

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12019: Credential password is required when creating or updating credential.

Cause: The password field is missing when instantiate a Credential object.

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12020: Credential store has not been initialized.

Cause: The underlying credentialStore object in CredentialBuilder is not initialized properly.

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12021: Wallet has not been initialized.

Cause: The underlying wallet object in walletStore provider is not initialized properly.

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12022: Can not change username for a password-only credential

Cause: Try to change the username of a password-only credential.

Action:
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12023: -walletDirectory

Cause: The wallet file directory command line argument is not specified.

Action: Specify a wallet file directory.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12024: -alias

Cause: The credential alias command line argument is not specified.

Action: Specify a credential alias.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12025: -password

Cause: The credential password command line argument is not specified.

Action: Specify a credential password.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12026: Could not find key with name {0} to delete

Cause: The credential alias is not found in credential store.

Action: Specify correct alias name.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-12027: Added/Updated credential to wallet with credential alias name {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

FMWPLATFORM-12028: Cannot create a new encrypted wallet file because an auto-login wallet file already exists at the same location {0}

Cause: An auto-login wallet file already exists in the same file directory.

Action: Specify a different PKI wallet file directory.
Level: 1

Type: ERROR

Impact: Other

FMWPLATFORM-020010: Python Type Error

Cause: PyTypeErrorException is thrown

Action: throws BadActionException
Level: 1

Type: ERROR

Impact: Other

21 GGSTU-60000 to GGSTU-65036

GGSTU-60000: Unable to deploy.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Deployment

GGSTU-60001: Unable to deploy as rest api service failed.

Cause: OGG Rest Service for Process Status is down.

Action: Restart OGG Manager and Jagent Process.
Level: 32

Type: ERROR

Impact: Request

GGSTU-60002: Unable to deploy as rest api service failed.

Cause: OGG Rest Service for Monitoring Points is down.

Action: Restart OGG Manager and Jagent Process.
Level: 32

Type: ERROR

Impact: Request

GGSTU-60003: Unable to deployment OGG Instance Resource is not assigned.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Deployment

GGSTU-60004: Unable to deployment Datastore Resource is not assigned.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Deployment

GGSTU-60005: Unable to delete trail file.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Deployment

GGSTU-60006: Unable to connect to OGG Instance.

Cause: Jagent in OGG is down or configuration of OGG Instance Resource is wrong.

Action: Please check Jagent should be running in OGG or check configuraion of OGG Instance Resource.
Level: 32

Type: ERROR

Impact: Deployment

GGSTU-60007: Unable to create root or temp directory

Cause: The root directory of oracledi and temp directory inside could not be verified.

Action: Please check to see if the directory oracledi and temp directory inside it are accessible.
Level: 32

Type: ERROR

Impact: Deployment

GGSTU-60008: Unable to process obey header template file

Cause: The file /oracle/oggstudio/deploy/resources/templateHeader.vm may have accessibility issues.

Action:
Level: 32

Type: WARNING

Impact: Deployment

GGSTU-60050: Rest Service failure. Unable to open connection to REST service

Cause: Failure in connecting to REST service.

Action: Please check to see REST service is up. Check to see if the URL used to connect to REST service is correct.
Level: 32

Type: ERROR

Impact: Deployment

GGSTU-60051: Rest Service failure. Unable to get status

Cause: Error in parsing of status response received from REST service.

Action: Please check to see REST service is up and sending correct format response for status.
Level: 32

Type: ERROR

Impact: Deployment

GGSTU-60052: Rest Service failure. Unable to get monitorying data.

Cause: Error in parsing of Monitoring data response received from REST service.

Action: Please check to see REST service is up and sending correct format response for monitoring.
Level: 32

Type: ERROR

Impact: Deployment

GGSTU-60200: Unable to start/stop process.

Cause: Error in starting or stoping process.

Action: Please check if the JAgent service is up and running.
Level: 32

Type: ERROR

Impact: UI

GGSTU-60201: Unable to create deployment archive.

Cause: Error in creating deployment archive.

Action: Critical error UI after creation of deployment archive failed.
Level: 32

Type: ERROR

Impact: UI

GGSTU-60202: Unable to do online deployment.

Cause: Error in executing job of online deployment.

Action: Critical error UI after job of online deployment failed.
Level: 32

Type: ERROR

Impact: UI

GGSTU-60203: Unable to create deployment agent dialog box.

Cause: Error in showing dialog box for deployment agent.

Action:
Level: 32

Type: WARNING

Impact: UI

GGSTU-60250: Framework error in opening a CEF editor.

Cause: Error in initializing the UI for a CEF editor.

Action: Critical error in UI module in opening a CEF editor.
Level: 32

Type: ERROR

Impact: UI

GGSTU-60251: Framework error in closing a CEF editor.

Cause: Error in closure of the UI for a CEF editor.

Action: Critical error in UI module in closing a CEF editor.
Level: 32

Type: ERROR

Impact: UI

GGSTU-60300: Error while adding a page to the panel for the Initial load wizard.

Cause: Exception while adding page to the Initial load panel wizard.

Action: Page addition to Initial load wizard failed. Check to see if the Initial load is configured properly.
Level: 32

Type: ERROR

Impact: WIZARD

GGSTU-60301: Error while adding a page to the panel for the Instance assignment wizard.

Cause: Exception while adding page to the Instance assignment wizard.

Action: Page addition to Instance Assignemnt wizard failed. Check to see if the Instances are configured properly.
Level: 32

Type: ERROR

Impact: WIZARD

GGSTU-60302: Error while adding a page to the panel for the Datastore assignment wizard.

Cause: Exception while adding page to the Datastore assignment wizard.

Action: Page addition to Datastore Assignemnt wizard failed. Check to see if the Datastores are configured properly.
Level: 32

Type: ERROR

Impact: WIZARD

GGSTU-61000: Addin failed to initialize.

Cause: Exception while trying to initialize the Studio addin.

Action: The addin failed. Try to restart the application.
Level: 32

Type: ERROR

Impact: UI

GGSTU-61001: Exception while checking if CEF node can be duplicated

Cause: Exception while trying to check if the CEF node can be duplicated.

Action:
Level: 32

Type: WARNING

Impact: UI

GGSTU-61002: Exception while handling duplicate CEF node event.

Cause: Exception while trying to process the duplicate CEF node event.

Action:
Level: 32

Type: WARNING

Impact: UI

GGSTU-61003: Exception while handling repository export event.

Cause: Exception while trying to process the repository export event.

Action:
Level: 32

Type: WARNING

Impact: UI

GGSTU-61004: Exception while handling repository import event.

Cause: Exception while trying to process the repository import event.

Action:
Level: 32

Type: WARNING

Impact: UI

GGSTU-61100: Overall exception in loading metadata for OGG Studio.

Cause: Generic Exception in loading metadata.

Action: Overall failure of loading metadata. Please check for other error codes for specific action.
Level: 32

Type: ERROR

Impact: UI

GGSTU-61101: Exception in loading resource bundle of metadata for OGG Studio.

Cause: Error during loading resource bundle for meta data.

Action: Please check and see if the resource bundle for meta data is present in correct location.
Level: 32

Type: ERROR

Impact: UI

GGSTU-61102: Exception in parsing the metadata xml for OGG Studio.

Cause: Error during parking the meta data file.

Action: Please check and see if the format of meta data file is correct. Check for any missing tags etc.
Level: 32

Type: ERROR

Impact: UI

GGSTU-61103: Exception in reading the metadata properties file for OGG Studio.

Cause: Error during reading the meta data properties file.

Action: Please check and see if the meta data properties file is present at the correct location. Also check if the directory has correct permissions.
Level: 32

Type: ERROR

Impact: UI

GGSTU-61104: Exception in reading and parsing the metadata xml file for OGG Studio.

Cause: Error during reading and parsing the meta data xml file.

Action: Please check and see if the meta data xml file is present at the correct location. Also check if the directory has correct permissions. Also check for any missing tags in the xml file.
Level: 32

Type: ERROR

Impact: UI

GGSTU-64000: Connection context creation failure. Unable to get OGG Resources connection context.

Cause: Error while getting OGG Resources Connection context

Action: Please make sure connection context configuration is correct
Level: 32

Type: ERROR

Impact: Resources

GGSTU-64001: Unable to destroy adf connection context.

Cause: Error while destroying adf connection context.

Action: Please make sure connection context exists and the user has permissions to destroy the context.
Level: 32

Type: ERROR

Impact: Resources

GGSTU-64002: JNDI Context creation failure. Unalbe to create jndi context.

Cause: Error while creating jndi context.

Action: Please make sure JNDI configuration is correct.
Level: 32

Type: ERROR

Impact: Resources

GGSTU-64003: ADF Config creation failure. Unable to create adf config files.

Cause: Error while creating adf config files.

Action: Please make sure PROVIDER URL is correctly configured.
Level: 32

Type: ERROR

Impact: Resources

GGSTU-64004: Unable to create adf connection context document

Cause: Error while creating adf connection context document.

Action: Please make sure ADF connection context is configured correctly.
Level: 32

Type: ERROR

Impact: Resources

GGSTU-64005: JNDI Context initialization failure. Unable to initialize JNDI context factory.

Cause: Error while initializing jndi context.

Action: Please make sure JNDI is correctly configured.
Level: 32

Type: ERROR

Impact: Resources

GGSTU-64006: Resource save failure. Unable to save resource in adf config.

Cause: Error while saving resource in adf config.

Action: Kindly retry by using a different resource name. Also, make sure all the resource parameters are correct.
Level: 32

Type: ERROR

Impact: Resources

GGSTU-64007: Resource persist failure. Unable to save/persist resource in repository.

Cause: Error while saving resource in repository

Action: Please try to use a different resource name. Also, make sure that the parameters of resource are correct.
Level: 32

Type: ERROR

Impact: Resources

GGSTU-64008: Resource already exists in repository.

Cause: Resource already exists in repository.

Action: Please use a different resource name.
Level: 32

Type: ERROR

Impact: Resources

GGSTU-64009: Resource not found error. Unable to find the specified resource

Cause: Error while retrieving the resource.

Action: Please use a resource that exists in repository.
Level: 32

Type: ERROR

Impact: Resources

GGSTU-64010: Resource Modification failure. Not able to modify/update the specified resource.

Cause: Error while updating the resource.

Action: Please retry with different properties of resource. Some of the values modifed might be incorrect.
Level: 32

Type: ERROR

Impact: Resources

GGSTU-64011: Resource deletion failure. Not able to delete the specified resource.

Cause: Error while deleting resource

Action: Please make sure this resource is not used by some other object. Kindly delete any association of this resource with others before trying again.
Level: 32

Type: ERROR

Impact: Resources

GGSTU-64012: Unable to load adf context document.

Cause: Error while loading adf context document

Action: Please make sure the adf configuration is correctly configured.
Level: 32

Type: ERROR

Impact: Resources

GGSTU-65010: Unable to open the Conflict Resolution edit dialog

Cause: Component definition file is missing.

Action: Make sure component definition file exists in the location
Level: 32

Type: ERROR

Impact: PI

GGSTU-65011: Unable to open the edit dialog

Cause: Component definition file is missing.

Action: Make sure component definition file exists in the location
Level: 32

Type: ERROR

Impact: PI

GGSTU-65012: Failed to open the component panel.

Cause: Component definition file is missing or component file has error.

Action: Make sure component definition file exists in the location
Level: 32

Type: ERROR

Impact: PI

GGSTU-65013: Unable to initialize the component.

Cause: Component definition file is missing or component file has error.

Action: Make sure component definition file exists in the location
Level: 32

Type: ERROR

Impact: PI

GGSTU-65030: Unable to get the node graphic

Cause: Unable to read/write the stream

Action: Make sure that read/write permission is available or the file exists
Level: 32

Type: ERROR

Impact: Diagram Node

GGSTU-65031: Invalid destination

Cause: Invalid Target

Action: Please select a valid destination
Level: 32

Type: ERROR

Impact: Diagram Node

GGSTU-65032: Unable to get the graph

Cause: The controller is not available.

Action: Make sure the controller exists
Level: 32

Type: ERROR

Impact: Diagram Node

GGSTU-65033: Unable to assign the source

Cause: Invalid source selected

Action: Make sure that the selected source is valid
Level: 32

Type: ERROR

Impact: Diagram Node

GGSTU-65034: Unable to delete the node

Cause: Controller is not valid

Action: Make sure the controller is valid
Level: 32

Type: ERROR

Impact: Diagram Node

GGSTU-65035: Unable to attach the model to the graphic

Cause: model is not available or does not exist

Action: Make sure that the model for the graphic available.
Level: 32

Type: ERROR

Impact: Diagram Node

GGSTU-65036: Unable layout the diagram

Cause: layout failed due to various reasons.

Action:
Level: 32

Type: WARNING

Impact: Diagram Node

22 HC-50006 to HC-53104

HC-50006: Exception Received

Cause: HCFP received an exception message from an endpoint.

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

HC-50007: Notification of failure received

Cause: HCFP received a notification of failure - out of band exception from an endpoint

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

HC-50008: Document Level Reattempt Count is exhausted

Cause: Maximum number of document level reattempt count has been reached

Action: Increase document level reattempt count
Level: 1

Type: INCIDENT_ERROR

Impact: Process

HC-50009: Failed to Send

Cause: HCFP cannot send message to endpoint

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

HC-50010: Endpoint identification error

Cause: HCFP cannot identify an endpoint 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

HC-50011: Message Correlation Error

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

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

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

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

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

HC-50021: User request to set error for all pending batch messages with same batch id [{0}].

Cause: User request to set error for all pending batch messages with same batch id [{0}]

Action: User request to set error for all pending batch messages with same batch id [{0}]
Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

HC-50026: Repository error

Cause: Error accessing stream data store

Action: Review the diagnostic log to verify the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

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

HC-50029: HCFP 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

HC-50031: HCFP 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

HC-50032: HCFP exchange protocol negative acknowledge received

Cause: Received a negative exchange acknowledge message.

Action: Review the negative exchange acknowledge message to determine the cause.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

HC-50033: HCFP 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

HC-50034: HCFP negative functional acknowledgment

Cause: A negative functional acknowledgment is received.

Action: Review the negative functional acknowledge message to determine the cause.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

HC-50035: HCFP 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

HC-50036: HCFP endpoint identification error

Cause: An error had occurred during identify endpoint.

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

HC-50037: HCFP 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

HC-50038: HCFP_INVALID_INPUT_MESSAGE_APP_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

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

HC-50042: HCFP 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

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

HC-50051: Failed to shut down the HCFP 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

HC-50052: Engine already initialized.

Cause: Attempt made to initialize HCFP engine which has been initialized already.

Action: Ensure that the engine is stopped before attempting to initialize
Level: 1

Type: NOTIFICATION

Impact: Process

HC-50059: Error in starting HCFP 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

HC-50060: Error in stopping HCFP 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

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

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

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

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

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

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

HC-50081: Duplicate exchange protocol message error

Cause: Duplicate exchange protocol message generated by an endpoint.

Action: Report this error to the message sender.
Level: 1

Type: ERROR

Impact: Process

HC-50082: Duplicated Control Number error

Cause: Message received with duplicate control number {0}.

Action: Report this error to the message sender.
Level: 1

Type: ERROR

Impact: Process

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

HC-50084: No service found

Cause: Requested service was not registered in system

Action: Check requested web service URL
Level: 1

Type: ERROR

Impact: Process

HC-50547: Document support for doc {2} not found for endpoint {0}.

Cause: Failed to identify the endpoint from the given input values.

Action: Make sure there is an endpoint configured for the From/To and document information that presents in the message.
Level: 1

Type: ERROR

Impact: Process

HC-50548: Endpoint {0} not in active state.

Cause: Endpoint was not in active state.

Action: Make sure the endpoint is enabled.
Level: 1

Type: ERROR

Impact: Process

HC-50549: Cannot uniquely identify the endpoint. The following endpoints {0} are not uniquely identifiable

Cause: The endpoints {0} are not unique

Action: Make sure the endpoints are uniquely identifiable
Level: 1

Type: ERROR

Impact: Process

HC-50601: Endpoint found but the certificate used for client authentication may not represent the Endpoint {0} whom it claims to be.

Cause: Certificate used for client authentication may not belong to the Endpoint.

Action: Please make sure Endpoint alias has been configured correctly against Security Identifier. If it is not, then it is a serious security error, please consult your security administrator for further course of action.
Level: 1

Type: ERROR

Impact: Process

HC-50602: Keystore not available to validate the incoming certificate over SSL.

Cause: Keystore may not be properly configured to validate the incoming SSL client certificate.

Action: Please make sure keystore has been configured properly.
Level: 1

Type: ERROR

Impact: Process

HC-50603: Endpoint found but authenticated principal(user) over http do not represent the Endpoint {0} whom it claims to be.

Cause: Authenticated user may not represent the Endpoint.

Action: Please make sure the Security Identifier configuration in HCFP against the Endpoint 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

HC-50701: The endpoint {0} cannot be activated because a similar endpoint {1} found in active state

Cause: Similar endpoint found in active state. There cannot be two endpoints with the same document type, version, and direction.

Action: Make inactive existing active endpoint which has the same document type, version, and direction.
Level: 1

Type: ERROR

Impact: Process

HC-50702: Endpoint {0} does not exist in the repository.

Cause: Endpoint {0} does not exist in the repository.

Action: Endpoint does not exist in the repository. Get the latest list of endpoints.
Level: 1

Type: ERROR

Impact: Process

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

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

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

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

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

HC-50708: Mandatory parameter value missing.

Cause: Mandatory Parameter can not be null.

Action: Provide the mandatory parameter value.
Level: 1

Type: ERROR

Impact: Process

HC-50709: Endpoint Disablement Failed.

Cause: Endpoint can not disabled

Action: Endpoint Disablement Failed. Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

HC-50710: Document Protocol {0} does not supported

Cause: Document Protocol {0} not supported.

Action: Document Protocol not supported.
Level: 1

Type: ERROR

Impact: Process

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

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

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

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

HC-50715: No document attached to endpoint

Cause: There is no document attached to endpoint.

Action: There is no document attached to endpoint.There should be at least one document attached to enable the endpoint.Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

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

HC-50717: Block characters missing

Cause: Block characters parameters values are missing.

Action: Provide the Block characters parameters.
Level: 1

Type: ERROR

Impact: Process

HC-50718: Channel is associated with {0} Endpoint(s) and associated Endpoint(s) are {1}

Cause: Channel is associated with {0} Endpoint(s) and associated Endpoint(s) are {1}

Action: Make sure channel is not associated with any Endpoint(s).
Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

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

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

HC-50744: Keystore details missing or invalid.

Cause: Keystore details have not been provided or are invalid.

Action: Provide Keystore details.If provided then check the validity of keystore location and password.
Level: 1

Type: ERROR

Impact: Process

HC-50801: No input value is specified. At least one input value is needed: Endpoint name or Document or Action

Cause: Missing input values

Action: Specify input values such as From/To Endpoint name or Document or Action
Level: 1

Type: ERROR

Impact: Process

HC-50901: Failed to find a business message with HCFPMessageId {0}.

Cause: Failed to find a business message with HCFPMessageId.

Action: Review the UI report to verify that a message exists with HCFPMessageId.
Level: 1

Type: ERROR

Impact: Process

HC-50902: Failed to find a wire message with HCFPMessageId {0}.

Cause: Failed to find a wire message with HCFPMessageId.

Action: Review the UI report to verify that a message exists with HCFPMessageId.
Level: 1

Type: ERROR

Impact: Process

HC-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 endpoint.
Level: 1

Type: NOTIFICATION

Impact: Process

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

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

HC-51000: General packaging Error

Cause: Packaging details were incorrect.

Action: Correct the packaging details in delivery channel.
Level: 1

Type: INTERNAL_ERROR

Impact: Process

HC-51001: Packaging fail

Cause: Packaging information were insufficient.

Action: Correct the packaging details in delivery channel.
Level: 1

Type: ERROR

Impact: Process

HC-51002: Unpacking fail

Cause: Packaging headers were incorrect.

Action: Correct the packaging details in delivery channel.
Level: 1

Type: ERROR

Impact: Process

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

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

HC-51005: Validating packaging metadata failed.

Cause: Packaging metadata was insufficient.

Action: Verify packaging metadata to pack the message.
Level: 1

Type: ERROR

Impact: Process

HC-51006: Invalid input parameter

Cause: Packaging input parameters were invalid.

Action: Verify the packaging parameters and packaging metadata.
Level: 1

Type: ERROR

Impact: Process

HC-51007: Missing packaging metadata information.

Cause: Missing few packaging metadata.

Action: Verify the packaging metadata.
Level: 1

Type: ERROR

Impact: Process

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

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

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

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

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

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

HC-51014: Missing data for message component.

Cause: Invalid data for message component.

Action: Verify message has component data.
Level: 1

Type: ERROR

Impact: Process

HC-51015: Missing security information.

Cause: Invalid security information.

Action: Verify security information is exist in packaging.
Level: 1

Type: ERROR

Impact: Process

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

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

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

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

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

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

HC-51022: Digest algorithm does not match.

Cause: Invalid digest algorithm.

Action: Verify digest algorithm.
Level: 1

Type: ERROR

Impact: Process

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

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

HC-51025: Keystore resource location incorrect

Cause: Incorrect keystore location specified.

Action: Specify correct keystore location.
Level: 1

Type: ERROR

Impact: Process

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

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

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

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

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

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

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

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

HC-51057: Invalid or corrupted message.

Cause: Invalid message format.

Action: Verify the message format.
Level: 1

Type: ERROR

Impact: Process

HC-51075: Missing signer certificate.

Cause: Signer certificate not found.

Action: Provide the certificate to sign the message.
Level: 1

Type: ERROR

Impact: Process

HC-51076: Missing encryption certificate.

Cause: Encryption certificate not found.

Action: Provide the certificate to encrypt the message.
Level: 1

Type: ERROR

Impact: Process

HC-51077: Missing certificate chain.

Cause: Invalid certificate chain was exist.

Action: Provide the proper certificate with certificate chain.
Level: 1

Type: ERROR

Impact: Process

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

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

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

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

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

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

HC-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.
Level: 1

Type: ERROR

Impact: Process

HC-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 certificate.
Level: 1

Type: ERROR

Impact: Process

HC-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.
Level: 1

Type: ERROR

Impact: Process

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

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

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

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

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

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

HC-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 the certificate used to encrypt the message is correct.
Level: 1

Type: ERROR

Impact: Process

HC-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 endpoint.
Level: 1

Type: ERROR

Impact: Process

HC-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 endpoint.
Level: 1

Type: ERROR

Impact: Process

HC-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 endpoint to send the message with the single signer.
Level: 1

Type: ERROR

Impact: Process

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

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

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

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

HC-51107: Digest mismatch

Cause: Document might have been corrupted during transport.

Action: Request a re-send from the endpoint.
Level: 1

Type: ERROR

Impact: Process

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

HC-51112: An invalid CRL has been found in the incoming message.

Cause: Invalid CRL.

Action: Check if the CRL is correct and request a re-send from the endpoint.
Level: 1

Type: ERROR

Impact: Process

HC-51114: CRL missing issuer

Cause: Issuer not found in CRL.

Action: Check that CRL issuer is correct and request a re-send from the endpoint.
Level: 1

Type: ERROR

Impact: Process

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

HC-51121: Empty recipient list

Cause: No recipient list was exist in the encrypted message.

Action: Check the message and request a re-send with recipient list.
Level: 1

Type: ERROR

Impact: Process

HC-51122: Certificate decode error

Cause: Certificate was not correct.

Action: Check if the certificate is in correct format.
Level: 1

Type: ERROR

Impact: Process

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

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

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

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

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

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

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

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

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

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

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

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

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

HC-51197: LDAP error

Cause: LDAP error

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

HC-51198: LDAP connect failed.

Cause: LDAP connect failed.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

HC-51199: LDAP bind failed.

Cause: LDAP bind failed.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

HC-51200: LDAP search failed.

Cause: LDAP search failed.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

HC-51201: LDAP entry missing attribute.

Cause: LDAP entry missing attribute.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

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

HC-51203: Error compressing data.

Cause: An error has occurred while compressing data.

Action: Check the payload.
Level: 1

Type: ERROR

Impact: Process

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

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

HC-51500: Document exchange success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

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

HC-51503: General create message error.

Cause: Failed to create message components.

Action: Verify values for message creation components.
Level: 1

Type: ERROR

Impact: Process

HC-51504: General decode error.

Cause: Failed to decode the message.

Action: Verify the incoming message contents.
Level: 1

Type: ERROR

Impact: Process

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

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

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

HC-51508: EDI group header validation error.

Cause: An error occurred in EDI document group header processing.

Action: Verify the EDI group header parameters of the message validity against the document definition.
Level: 1

Type: ERROR

Impact: Process

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

HC-51510: EDI batch message processing error.

Cause: An error occurred during EDI document batch message processing.

Action: Verify the batch message payload validity against the document definition.
Level: 1

Type: ERROR

Impact: Process

HC-51511: EDI interchange header validation error.

Cause: An error occurred in interchange header of EDI document during message payload processing.

Action: Verify the EDI Interchange header parameters of the message validity against the document definition
Level: 1

Type: ERROR

Impact: Process

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

HC-51518: Mandatory parameter {0} {1} is missing.

Cause: Mandatory parameter {0} {1} is missing.

Action: Verify mandatory parameter in payload and configuration.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

HC-51551: Invalid timestamp.

Cause: Timestamp was not in the correct format.

Action: Correct timestamp format is CCYYMMDDThhmmss.sssZ.
Level: 1

Type: ERROR

Impact: Process

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

HC-51568: encoding error

Cause: An unexpected error occurred while encoding data.

Action: Verify encoded type is base64.
Level: 1

Type: ERROR

Impact: Process

HC-51569: decoding error

Cause: An unexpected error occurred while decoding data.

Action: Verify the decode type is base64.
Level: 1

Type: ERROR

Impact: Process

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

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

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

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

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

HC-51575: Incorrect document exchange version.

Cause: Document exchange version mismatch.

Action: Verify the document exchange header value.
Level: 1

Type: ERROR

Impact: Process

HC-51576: Incorrect document exchange.

Cause: Document exchange mismatch.

Action: Verify the document exchange name.
Level: 1

Type: ERROR

Impact: Process

HC-51577: Document exchange validation error

Cause: Document exchange validation failed.

Action: Verify the document exchange header values
Level: 1

Type: ERROR

Impact: Process

HC-51578: Exception Reported: {0}

Cause: HC is unable to continue processing due to Control Number sequence generation failure.

Action: Please refer to documentation for EM property : hc.useSequenceControlNum for further information.
Level: 1

Type: ERROR

Impact: Process

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

HC-51705: Unable to read the preamble.

Cause: Failed to read preamble.

Action: Ensure the correctness of preamble content.
Level: 1

Type: ERROR

Impact: Process

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

HC-52251: Error identifying endpoint 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 endpoint is configured as in the trading partner identification section or the anonymous trading partner is configured.
Level: 1

Type: ERROR

Impact: Process

HC-52252: Endpoint can not have hosted=true.

Cause: Endpoint has hosted=true.

Action: Make sure none of the endpoint in the system has hosted=true.
Level: 1

Type: ERROR

Impact: Process

HC-52253: Endpoint {0} must have endpoint name as one of the identification.

Cause: Endpoint must have endpoint name as one of the identification.

Action: Make sure endpoint has an identification with value as name of endpoint.
Level: 1

Type: ERROR

Impact: Process

HC-52254: Endpoint {0} must have exchange protocol, if listening=false.

Cause: Outbound endpoint did not have exchange protocol.

Action: Make sure outbound endpoint has exchange protocol.
Level: 1

Type: ERROR

Impact: Process

HC-52255: Certificate alias not specified in the secure endpoint {0}.

Cause: Security was enabled in endpoint, but no certificate alias specified.

Action: Make sure certificate alias specified in the endpoint.
Level: 1

Type: ERROR

Impact: Process

HC-52256: In endpoint {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

HC-52257: In endpoint {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

HC-52258: In endpoint {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

HC-52259: In endpoint {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

HC-52260: The effectiveToDate {0} in endpoint must be a date in the future.

Cause: Date specified in effectiveToDate was not a future date.

Action: Ensure that the effectiveToDate in the endpoint is a date in the future.
Level: 1

Type: ERROR

Impact: Process

HC-52261: The effectiveFromDate {0} should be less than effectiveToDate {1} in endpoint.

Cause: The effectiveFromDate should be less than effectiveToDate.

Action: Make sure the effectiveFromDate is less than effectiveToDate.
Level: 1

Type: ERROR

Impact: Process

HC-52262: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

HC-52263: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

HC-52264: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

HC-52266: Identification type {0} and value {1} must be unique in the endpoint.

Cause: Identification type and value occurred more than once in the endpoint.

Action: Make sure type and value of identification unique in the endpoint.
Level: 1

Type: ERROR

Impact: Process

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

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

HC-52269: Endpoint cannot have more than one identification of the same type {1}.

Cause: Endpoint has more than one identification of the same type.

Action: Make sure endpoint is not referring to more than one identification of same type.
Level: 1

Type: ERROR

Impact: Process

HC-52270: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

HC-52271: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

HC-52272: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

HC-52273: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

HC-52274: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

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

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

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

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

HC-52280: Endpoint group {0} must have at least one exchange identification.

Cause: None of the exchange identification found in endpoint.

Action: Add at least one exchange identification in endpoint.
Level: 1

Type: ERROR

Impact: Process

HC-52281: Endpoint group {0} must have ID {1} starts with tp_

Cause: Endpoint group has ID which did not start with tp_

Action: Make sure endpoint group has ID which starts with tp_
Level: 1

Type: ERROR

Impact: Process

HC-52282: Endpoint group {0} reference must be tp_id.xml

Cause: Endpoint group reference was not in the form of tp_id.xml

Action: Make sure endpoint group has reference in the form of tp_id.xml
Level: 1

Type: ERROR

Impact: Process

HC-52283: In endpoint {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

HC-52284: Outbound endpoint {0} which has transport protocol {1} cannot be a listening endpoint.

Cause: Selected transport protocol was not capable of listening

Action: Select listening transport to create listening endpoint
Level: 1

Type: ERROR

Impact: Process

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

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

HC-52287: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

HC-52288: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

HC-52289: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

HC-52290: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

HC-52291: Duplicate endpoint {1} found for same document type {3} and document protocol version {4}.

Cause: More than one endpoint has same combination of document type and version.

Action: Make sure only one endpoint has same combination of document type and version.
Level: 1

Type: ERROR

Impact: Process

HC-52292: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

HC-52293: Endpoint is not referring the internal delivery channel.

Cause: Instead of the internal delivery channel, other delivery channel referred.

Action: Make sure host is not referring to other than internal delivery channel.
Level: 1

Type: ERROR

Impact: Process

HC-52294: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

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

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

HC-52298: Transport URL {0} already used in system.

Cause: More than once same endpoint used in system.

Action: Make sure same endpoint is not exist in system.
Level: 1

Type: ERROR

Impact: Process

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

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

HC-52301: MDSReference {0} is not referring to the endpoint.

Cause: MDSReference did not refer to the endpoint.

Action: Make sure given reference is pointing to the endpoint.
Level: 1

Type: ERROR

Impact: Process

HC-52302: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

HC-52304: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

HC-52305: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

HC-52307: Listening endpoint {0} must have a polling interval value.

Cause: Listening endpoint did not have value for polling interval.

Action: Make sure listening endpoint has polling interval value.
Level: 1

Type: ERROR

Impact: Process

HC-52308: Listening endpoint {0} with transport {1} does not have user name and password.

Cause: Listening endpoint did not have user name and password in transport.

Action: Make sure listening endpoint has user name and password in transport.
Level: 1

Type: ERROR

Impact: Process

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

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

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

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

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

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

HC-52315: Duplicate identification type {1} and value {2} found in source endpoint {0}.

Cause: More than one identification type found in source endpoint(s) for a same value and type.

Action: Make sure combination of identification type and value unique in the endpoint.
Level: 1

Type: ERROR

Impact: Process

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

HC-52317: Endpoint metadata is invalid.

Cause: Endpoint metadata was corrupted while importing or creating endpoint.

Action: Purge and recreate this endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

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

HC-52320: Endpoint supported document definition {0}, functional acknowledge can be enabled only when translate=true.

Cause: Endpoint supported document definition 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

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

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

HC-52323: Out-bound endpoint supported document definition {0} has to have only one exchange identifier type - {1}, in both participants

Cause: Out-bound endpoint supported document definition 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 endpoint.
Level: 1

Type: ERROR

Impact: Process

HC-52324: Listening endpoint {0} has duplicate endpoint {1}

Cause: New endpoint cannot be activated with same name.

Action: Make sure all listening endpoints are unique.
Level: 1

Type: ERROR

Impact: Backup and Recovery

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

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

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

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

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

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

HC-52331: Translated content is not available

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

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

HC-52333: received data from endpoint 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

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

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

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

HC-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 99994 bytes.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

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

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

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

HC-52341: Interface Sequence Message discarded. Message id {0}. Dependent Outbound Rows discarded {1}

Cause: Interface Sequence Message discarded.

Action: N/A
Level: 3

Type: ERROR

Impact: Process

HC-53100: Unable to create sequencing entry for message

Cause: An error occurred while creating a sequencing entry 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: ERROR

Impact: Process

HC-53101: Unable to update sequencing state for message

Cause: An error occurred while updating the sequencing state 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: ERROR

Impact: Process

HC-53102: Failure occurred while persisting messages asynchronously in {0} repository

Cause: An error occurred while persisting messages to the {0} repository asynchronously.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: ERROR

Impact: Process

HC-53103: Unable to update Message state in the repository for message id {0}.

Cause: Unable to update Message state in the repository for message id {0}.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: ERROR

Impact: Process

HC-53104: Unable to enqueue event to Event Manager.

Cause: Unable to enqueue event to Event Manager

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: ERROR

Impact: Process

23 INST-01000 to INST-10117

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

INST-01001: Abnormal Program Termination.

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

INST-01003: Error: Response file not specified.

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

INST-01008: Internal Error: Operation not specified

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Incompatible operation specified

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Incompatible modes specified

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Default mode not specified

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Default Operation not specified

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Default Next Page is mandatory for each page.

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Duplicate definition of pages detected.

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Page name not specified

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Page name mismatch

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

Type: INTERNAL_ERROR

Impact: Installation

INST-01023: Internal Error: Unable to provide usage

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: WARNING

Impact: Installation

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

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

Action: Delete the invalid checkpoint file
Level: 1

Type: WARNING

Impact: Installation

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

Cause: The response file may be corrupted or has errors

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

INST-01028: Error: No Section defined.

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

INST-01030: Response File Parse Error

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

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

Type: ERROR

Impact: Installation

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

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

Action: Specify the corresponding value.
Level: 1

Type: WARNING

Impact: Installation

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

Cause: Configuration Files are not proper:{0}

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Configuration Actions are improper:{0}

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Configuration Actions are improper:{0}

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Class: {0} not found.

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Lifecycle Error

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Error in copying files

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: WARNING

Impact: Installation

INST-01046: Internal Error: Invalid Install Session.

Cause: Data Model is empty.

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

INST-01048: Internal Error: Aborting Silent Install.

Cause: Error while running silent install

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Failed Prerequisite: {0}

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

Type: NOTIFICATION

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

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

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

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

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Installation

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

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

Action: Correct the file and retry
Level: 1

Type: WARNING

Impact: Installation

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

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

Action: Specify a valid log level.
Level: 1

Type: WARNING

Impact: Installation

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

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

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

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

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

Cause: Prerequisite check: {0} has failed

Action: Correct the failed prerequisite and retry
Level: 1

Type: NOTIFICATION

Impact: Installation

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

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

Cause: Directory specified for the inventory cannot be created.

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

Type: ERROR

Impact: Installation

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

Cause: Required Oracle home value not set

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Required library not found

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

Type: INTERNAL_ERROR

Impact: Installation

INST-01066: Configuration Data Store not found.

Cause: Required Configuration Data Store not found

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Problem while loading the configuration actions

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

Type: INTERNAL_ERROR

Impact: Installation

INST-01068: No configurations defined for this installation.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

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

Cause: Class not found: {0}

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Entry point not found

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Resource Key name provided is blank

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Error while constructing the Navigation Tree

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Error occurred while preparing the Action Queue

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: The format of displayConfig.xml is corrupt.

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Error occurred launching the welcome window

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Error occurred launching the Wizard

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Error occurred while setting the UI default properties

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

Type: INTERNAL_ERROR

Impact: Installation

INST-03012: Internal Error: Unknown Exception occurred.

Cause: Unknown exception occurred during installation

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Error occurred while creating the validation tree

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Error occurred while selecting the next page

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: The checkpoint data is corrupted.

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

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

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

Type: INTERNAL_ERROR

Impact: Installation

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

Cause: Connect String is missing

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-03021: Error in connecting to the Database

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

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

Type: ERROR

Impact: Installation

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

Cause: Schema Type is missing

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-03023: Error in validating Database details

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

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

Type: ERROR

Impact: Installation

INST-03024: Error in validating Database details

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

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

Type: ERROR

Impact: Installation

INST-03025: Error in validating Database details

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

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

Type: ERROR

Impact: Installation

INST-03026: Error in validating Database details

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

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

Type: ERROR

Impact: Installation

INST-03027: Error in validating Database details

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

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

Type: ERROR

Impact: Installation

INST-03028: Error in validating Database details

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

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

Type: ERROR

Impact: Installation

INST-03029: Error in validating Database details

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

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

Type: ERROR

Impact: Installation

INST-05100: Error in obtaining default DN Value

Cause: Error in processing the handler

Action: No default DN provided
Level: 1

Type: ERROR

Impact: Installation

INST-05115: Error in selection of component configuration.

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

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

Type: ERROR

Impact: Installation

INST-05116: Error in obtaining Schema names.

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

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

Type: ERROR

Impact: Installation

INST-05117: Error in obtaining Schema names.

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

INST-05120: Error in retrieving schema version.

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

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

Type: ERROR

Impact: Installation

INST-05121: An unsupported schema is detected.

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

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

Type: ERROR

Impact: Installation

INST-05122: Upgrade Scenario Detected

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

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

Type: ERROR

Impact: Installation

INST-05123: Error while retrieving the schema Name.

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

Action: Enter valid Database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05124: Error in connecting to the Database.

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

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

Type: ERROR

Impact: Installation

INST-05125: Error in retrieving schema details.

Cause: Database schemas were not found in the Database

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

Type: ERROR

Impact: Installation

INST-05126: Error in connecting to the LDAP.

Cause: One or more of LDAP Connection parameters is missing

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

Type: ERROR

Impact: Installation

INST-05127: Error in connecting to the LDAP.

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

INST-05129: Error in connecting to the LDAP.

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

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

Type: ERROR

Impact: Installation

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

Cause: No components selected for Oracle Identity Management installation.

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

Type: ERROR

Impact: Installation

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

Cause: The LDAP hostname is missing.

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

Type: ERROR

Impact: Installation

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

Cause: The LDAP port number is missing.

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

INST-05139: Upgrade Scenario Detected

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

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

Type: ERROR

Impact: Installation

INST-05141: Missing Schema Detected

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

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

Type: ERROR

Impact: Installation

INST-05142: Missing Schema Detected

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

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

Type: ERROR

Impact: Installation

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

Cause: Exception thrown during second OID installation check.

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

Type: ERROR

Impact: Installation

INST-05146: ODS Schema in use

Cause: ODS Schema is in use.

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

Type: ERROR

Impact: Installation

INST-05147: Missing Schemas Detected

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

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

Type: ERROR

Impact: Installation

INST-05149: Error in selection of component configuration.

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

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

Type: ERROR

Impact: Installation

INST-05150: Error in selection of component configuration.

Cause: None of the components are selected for configuration.

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

Type: ERROR

Impact: Installation

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

Cause: One or more of LDAP Connection parameters is missing

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

Type: ERROR

Impact: Installation

INST-05152: Error in validating LDAP Attributes.

Cause: Error in validating LDAP Attributes.

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

Type: ERROR

Impact: Installation

INST-05155: Error in JPS Attributes validation.

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

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

Type: ERROR

Impact: Installation

INST-05156: Error in connecting to LDAP.

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

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

Type: ERROR

Impact: Installation

INST-05159: Partial Schema Detected.

Cause: Partial Schema Detected.

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-05162: Error in connecting to LDAP.

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

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

Type: ERROR

Impact: Installation

INST-05163: Error in connecting to LDAP.

Cause: Error in connecting to LDAP.

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

Type: ERROR

Impact: Installation

INST-05164: {0} is missing.

Cause: {0} is missing.

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

Type: ERROR

Impact: Installation

INST-05165: {0} is not valid.

Cause: Error in validating {0}.

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

Type: ERROR

Impact: Installation

INST-05166: An unsupported database version is detected.

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

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

Type: ERROR

Impact: Installation

INST-05167: Database Initialization Parameter Warning

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

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

Type: ERROR

Impact: Installation

INST-05168: Prereqs Error

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

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

Type: ERROR

Impact: Installation

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

Cause: The host name entered is not valid

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

Type: ERROR

Impact: Installation

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

Cause: The host URL entered is not valid

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

Type: ERROR

Impact: Installation

INST-05171: Error in validating LDAP Credentials

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

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

Type: ERROR

Impact: Installation

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

Cause: Specified {0} schema account is locked

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

Type: ERROR

Impact: Installation

INST-05173: Multilingual Support Warning

Cause: Multilingual Support Warning

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

Type: ERROR

Impact: Installation

INST-05174: Schemas existing in Database

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

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

Type: ERROR

Impact: Installation

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

Cause: The LDAP type entered is not valid

Action: Provide a valid LDAP type.
Level: 1

Type: ERROR

Impact: Installation

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

Cause: The host URL entered is not valid.

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

Type: ERROR

Impact: Installation

INST-05177: Invalid Oracle Identity Federation schema

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

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

Type: ERROR

Impact: Installation

INST-05178: Error in connecting to LDAP.

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

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

Type: ERROR

Impact: Installation

INST-05179: Error in validating Database details

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

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

Type: ERROR

Impact: Installation

INST-05180: Error in validating Database details

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

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

Type: ERROR

Impact: Installation

INST-05181: Error in validating Database details

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

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

Type: ERROR

Impact: Installation

INST-05182: Error in validating Database details

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

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

Type: ERROR

Impact: Installation

INST-05183: Error in validating Database details

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

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

Type: ERROR

Impact: Installation

INST-05184: Error in validating Database details

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

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

Type: ERROR

Impact: Installation

INST-05185: Error in validating login table

Cause: The Login Table is not valid.

Action: Enter valid Login Table name.
Level: 1

Type: ERROR

Impact: Installation

INST-05186: Error in validating user id attribute

Cause: The User ID Attribute is not valid.

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

Type: ERROR

Impact: Installation

INST-05187: Error in validating user id attribute

Cause: The User Description Attribute is not valid.

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

INST-05189: An unsupported database version is detected.

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

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

Type: ERROR

Impact: Installation

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

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

Action: Enter a valid host name
Level: 1

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

Action: Enter a valid port
Level: 1

Type: ERROR

Impact: Installation

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

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

Action: Enter a valid admin user name
Level: 1

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

INST-05197: Error in validating LDAP Attributes.

Cause: Error in validating Domain Name.

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

Type: ERROR

Impact: Installation

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

Cause: Error in validating Oracle Identity Federation schema.

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

Type: ERROR

Impact: Installation

INST-05199: Error in validating {0}.

Cause: Unable to validate the field {0}.

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

Type: ERROR

Impact: Installation

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

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

Action:
Level: 1

Type: ERROR

Impact: Installation

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

Cause: Specified {0} home location does not exist

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-05206: Error in validating Database block size.

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

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

Type: ERROR

Impact: Installation

INST-05207: Error in connecting to OID.

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

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

Type: ERROR

Impact: Installation

INST-05208: Missing Schema Detected

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

INST-05211: Error in selection of component configuration.

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

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

Type: ERROR

Impact: Installation

INST-05212: Error in selection of component configuration.

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

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

Type: ERROR

Impact: Installation

INST-05213: Warning

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

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

Type: ERROR

Impact: Installation

INST-05214: Error in providing cluster connection information.

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

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

Type: ERROR

Impact: Installation

INST-05215: Error in finding cluster.

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

Cause: Unable to detect machine platform or JVM bits.

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

Cause: OID version is incompatible.

Action: Provide OID with compatible version.
Level: 1

Type: ERROR

Impact: Installation

INST-05223: Error in validating Domain.

Cause: Specified domain is not a valid IDM Domain.

Action: Provide valid IDM domain details.
Level: 1

Type: ERROR

Impact: Installation

INST-07000: Error in validating {0} location

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

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

Type: ERROR

Impact: Installation

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

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

Action:
Level: 1

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

Cause: {0} location is not absolute path

Action: Provide an absolute path
Level: 1

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

INST-07009: Error in validating {0} location

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

Action: Enter a valid directory
Level: 1

Type: ERROR

Impact: Installation

INST-07010: 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 {3} characters
Level: 1

Type: ERROR

Impact: Installation

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

Cause: Provide a valid value for Front End URL

Action:
Level: 1

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

INST-07013: Validation of Hostname failed. Invalid Host

Cause: The hostname entered is not valid

Action: Provide a valid hostname
Level: 1

Type: ERROR

Impact: Installation

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

Cause: The port entered is not valid

Action: Provide a valid port number
Level: 1

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

INST-07016: Error in validating the Front End URL

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

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07017: Error in obtaining free space

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

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

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

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

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07019: Error in obtaining free space

Cause: An unexpected error occurred while calculating available free space

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

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

Cause: An unexpected error occurred while obtaining default home location

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07021: Error in obtaining available Oracle homes

Cause: An unexpected error occurred while obtaining available Oracle homes

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

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

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

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

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

Cause: Provide a value for {0}

Action:
Level: 1

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

Action: Enter valid characters
Level: 1

Type: ERROR

Impact: Installation

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

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

Action: Enter valid start character
Level: 1

Type: ERROR

Impact: Installation

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

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

Action: Enter a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07040: Error in Password Check

Cause: Passwords entered were null or contained invalid characters

Action: Provide valid values
Level: 1

Type: ERROR

Impact: Installation

INST-07041: Error in Password Check

Cause: An unexpected error occurred while processing the handler

Action: Enter passwords that match
Level: 1

Type: ERROR

Impact: Installation

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

Cause: Password value is null

Action: Enter a valid value for password
Level: 1

Type: ERROR

Impact: Installation

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

Cause: Confirm Password value is null

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

Type: ERROR

Impact: Installation

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

Cause: Passwords entered do not match

Action: Enter identical passwords
Level: 1

Type: ERROR

Impact: Installation

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

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

Action: Enter a valid number
Level: 1

Type: ERROR

Impact: Installation

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

Cause: Provide a valid value for {0}

Action:
Level: 1

Type: ERROR

Impact: Installation

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

Cause: {0} field value is not a number

Action: Enter a valid number
Level: 1

Type: ERROR

Impact: Installation

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

Cause: Values specified are null or contain invalid characters

Action: Provide valid values
Level: 1

Type: ERROR

Impact: Installation

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

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

Action: Enter values that do not match
Level: 1

Type: ERROR

Impact: Installation

INST-07050: Error in Validating {0} and {1}. Null Value

Cause: Provide a valid value for {0}

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07051: Error in Validating {0} and {1}. Values do not match

Cause: {0} and {1} are different

Action: Enter same values
Level: 1

Type: ERROR

Impact: Installation

INST-07052: Error in Validating {0} and {1}. Values match

Cause: {0} and {1} are the same

Action: Enter different values
Level: 1

Type: ERROR

Impact: Installation

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

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

Action: Provide valid values
Level: 1

Type: ERROR

Impact: Installation

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

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

Action: Enter a valid host name
Level: 1

Type: ERROR

Impact: Installation

INST-07055: Error in validating the {0} field value. Host name value null

Cause: Provide a valid value for {0}

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07056: Error in validating the {0} field value. Invalid host name

Cause: {0} field value is not a valid host name

Action: Enter a valid value for host name
Level: 1

Type: ERROR

Impact: Installation

INST-07057: Error in validating the {0} field value. Host is not up and running

Cause: Error in validating the {0} field value. Entered host is not up and running

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

Type: ERROR

Impact: Installation

INST-07058: Error in validating Oracle home location

Cause: An unexpected error occurred while validating Oracle home location

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07059: Error in validating Oracle home location

Cause: Oracle home location Specified is missing. Provide a valid Oracle home location

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07060: Error in validating Oracle home location

Cause: The Oracle home location specified is not a valid {0} home location

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

Type: ERROR

Impact: Installation

INST-07061: Error in obtaining default port file location

Cause: An unexpected error occurred while obtaining default port file location

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07062: Error in connecting to the Database

Cause: An unexpected error occurred while trying to connect to the Database

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

Type: ERROR

Impact: Installation

INST-07063: Error in connecting to the Database. Connect String is missing

Cause: Connect string is missing

Action: Provide a valid value for Connection String
Level: 1

Type: ERROR

Impact: Installation

INST-07064: Error in connecting to the Database

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

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

Type: ERROR

Impact: Installation

INST-07065: Error in validating Database details

Cause: An unexpected error occurred while trying to connect to the Database

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

Type: ERROR

Impact: Installation

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

Cause: Schema type is missing

Action: Provide a valid value for Schema Type
Level: 1

Type: ERROR

Impact: Installation

INST-07067: Error in validating Database details. Schema name is missing

Cause: Schema is missing

Action: Provide a valid value for Schema Name
Level: 1

Type: ERROR

Impact: Installation

INST-07068: Error in validating Database details. Invalid Schema

Cause: Specified {0} schema does not exist in the given Database

Action: Check the schema name and the Database credentials
Level: 1

Type: ERROR

Impact: Installation

INST-07069: Validation of {0} location failed. Existing Oracle home

Cause: Validation of {0} location failed. The location specified is an existing Oracle home

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

Type: ERROR

Impact: Installation

INST-07072: Error in validating Oracle home location

Cause: The Oracle home location specified is an existing Oracle home

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

Type: ERROR

Impact: Installation

INST-07073: Error in validating Oracle home location

Cause: The Oracle home location specified is not a valid {0} home location

Action: Provide an empty or nonexistent directory location or a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07074: Error in validating Database details. Null Value

Cause: User name is missing

Action: Provide a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07075: Error in validating Database details. Invalid user

Cause: User does not have DBA privileges

Action: Provide a user with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07076: Error in validating Database details

Cause: An unexpected error occurred while trying to connect to the Database

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

Type: ERROR

Impact: Installation

INST-07077: Error in validating Oracle home and Oracle Instance home

Cause: Oracle home is inside the Oracle Instance home

Action: Enter a different location
Level: 1

Type: ERROR

Impact: Installation

INST-07078: Error in validating LDAP credentials

Cause: An unexpected error occurred while validating LDAP credentials

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07079: Error in validating LDAP credentials

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

Action: Verify the credentials. Make sure that hostname, port and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07080: Error in validating available disk space

Cause: Space required is missing or not a valid value

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07081: Error in validating available disk space

Cause: Insufficient space to install the selected components

Action: Specify a different Oracle Home or increase disk space.
Level: 1

Type: ERROR

Impact: Installation

INST-07082: Error in validating available disk space

Cause: An unexpected error occurred while validating available disk space

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07083: Error in validating port file

Cause: Specified port file location is missing

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07084: Error in validating port file

Cause: Specified port file is invalid

Action: Specify a valid file
Level: 1

Type: ERROR

Impact: Installation

INST-07085: Error in validating port file

Cause: Specified port file does not exist

Action: Specify a valid file
Level: 1

Type: ERROR

Impact: Installation

INST-07086: Error in validating port file

Cause: An unexpected error occurred while parsing the port file

Action: Verify the file. Check if the values are provided in the proper format. There should be at least one section in the file.
Level: 1

Type: ERROR

Impact: Installation

INST-07087: Error in validating port file

Cause: An unexpected error occurred while validating port file

Action: Provide a valid value. Check if the values are provided in the proper format. There should be at least one section in the file.
Level: 1

Type: ERROR

Impact: Installation

INST-07088: Error in validating available disk space

Cause: Insufficient disk space to install the product

Action: Specify a different Oracle Home or increase disk space.
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: Database details are invalid.

Cause: The specified schema {0} was invalid.

Action: Check the schema name and database credentials.
Level: 1

Type: ERROR

Impact: Installation

INST-07240: {0} components cannot be obtained from the Oracle WebLogic Middleware Administration Server.

Cause: The Oracle WebLogic Middleware Administration Server may be unresponsive or may not recognize the given credentials.

Action: Make sure the Oracle WebLogic Middleware Administration Server is up. Verify that the host name, port number, user name, and administrator password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07241: Connection to the Oracle WebLogic Middleware Administration Server has failed.

Cause: The provided credentials were null or contained 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: Connection to the Oracle WebLogic Middleware Administration Server has failed.

Cause: The Oracle Middleware Administration Server may be down. The provided credentials may be incorrect.

Action: Make sure the Oracle Middleware Administration Server is up and running. Verify that the host name, port number, user name, and administrator password are all correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07243: Connection to the Oracle WebLogic Middleware Administration Server has failed.

Cause: Host name was missing.

Action: Enter a valid host name.
Level: 1

Type: ERROR

Impact: Installation

INST-07244: Connection to the Oracle WebLogic Middleware Administration Server has failed.

Cause: The port number was missing.

Action: Enter a valid port number.
Level: 1

Type: ERROR

Impact: Installation

INST-07245: Connection to the Oracle WebLogic Middleware Administration Server has failed.

Cause: The administrator user name is missing.

Action: Enter a valid administrator user name.
Level: 1

Type: ERROR

Impact: Installation

INST-07246: {0} home location cannot be validated.

Cause: The home location is invalid.

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

Type: ERROR

Impact: Installation

INST-07247: {0} home location cannot be validated.

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: {0} home location cannot be validated.

Cause: Specified {0} home location was not valid.

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

Type: ERROR

Impact: Installation

INST-07249: {0} home location cannot be validated.

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 that 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: Default Middleware home and WebLogic home directories cannot be obtained.

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: Instance name cannot be validated.

Cause: Specified instance name is not valid.

Action: Enter a valid instance name associated with the specified instance home.
Level: 1

Type: ERROR

Impact: Installation

INST-07254: Instance name cannot be validated.

Cause: An unexpected error occurred.

Action: Check the inputted values.
Level: 1

Type: ERROR

Impact: Installation

INST-07255: Instance name cannot be validated.

Cause: The specified instance name was incorrect.

Action: Enter a valid instance name.
Level: 1

Type: ERROR

Impact: Installation

INST-07256: {0} component name cannot be validated.

Cause: Component type failed validation.

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

Type: ERROR

Impact: Installation

INST-07257: Component type cannot be validated.

Cause: The specified component type failed validation.

Action: Enter a valid value for component type.
Level: 1

Type: ERROR

Impact: Installation

INST-07258: Component name cannot be validated.

Cause: The provided component name could not be located.

Action: Verify the instance home location. Ensure that the component name is correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07259: {0} component name cannot be validated.

Cause: The specified value for {0} component name already exists.

Action: Provide a different value.
Level: 1

Type: ERROR

Impact: Installation

INST-07260: Error in validating {0} component name

Cause: Specified value for {0} component name is not valid. A directory with the same name already exists under INST_HOME/config/{0}

Action: Provide a different value
Level: 1

Type: ERROR

Impact: Installation

INST-07261: Error in validating component name

Cause: Specified component name is not a valid component name

Action: Enter a valid component name associated with the specified instance
Level: 1

Type: ERROR

Impact: Installation

INST-07262: Error in validating instance details in the domain

Cause: Specified instance details are not valid

Action: Enter a valid instance name available in the domain. Make sure the instance home entered is in conjunction with the instance name.
Level: 1

Type: ERROR

Impact: Installation

INST-07263: Error in validating instance name

Cause: Specified instance name is not valid

Action: Enter a valid instance name available in the domain.
Level: 1

Type: ERROR

Impact: Installation

INST-07264: Error in validating instance details in the domain

Cause: An unexpected error occurred during the validation of instance details

Action: Check the values. Verify the instance name and instance home location
Level: 1

Type: ERROR

Impact: Installation

INST-07265: Error in validating instance name

Cause: An unexpected error occurred during the validation of instance name

Action: Check the values. Verify the instance name
Level: 1

Type: ERROR

Impact: Installation

INST-07266: Error in validating component name in the domain

Cause: Specified {0} component name already exists in the domain

Action: Provide a different value
Level: 1

Type: ERROR

Impact: Installation

INST-07267: Error in validating component name in the domain

Cause: An unexpected error occurred during the validation of component name

Action: Check the values. Verify the component name
Level: 1

Type: ERROR

Impact: Installation

INST-07268: Error in validating component name in the domain

Cause: Specified {0} component name does not exist in the domain

Action: Enter an existing component name
Level: 1

Type: ERROR

Impact: Installation

INST-07269: Error while obtaining default values for instance name and instance location

Cause: An unexpected error occurred while obtaining default values for instance name and instance location

Action: Check the values and try again
Level: 1

Type: ERROR

Impact: Installation

INST-07270: Error in validating instance name in the domain

Cause: Specified instance name already exists in the domain

Action: Provide a different value
Level: 1

Type: ERROR

Impact: Installation

INST-07271: Error in validating instance name in the domain

Cause: An unexpected error occurred during the validation of instance name

Action: Check the values. Verify the instance name
Level: 1

Type: ERROR

Impact: Installation

INST-07272: Error while obtaining the component names from the instance home

Cause: An unexpected error occurred while obtaining the component names from the instance home

Action: Check the values. Verify the instance home location
Level: 1

Type: ERROR

Impact: Installation

INST-07273: Error while obtaining the component names of a given component type from the instance home

Cause: An unexpected error occurred while obtaining the component names of a given component type from the instance home

Action: Check the values. Verify the instance home location
Level: 1

Type: ERROR

Impact: Installation

INST-07274: Error in validating port value

Cause: Port {0} is not valid. Privileged ports are not allowed

Action: Provide a different value
Level: 1

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

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

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

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07277: Error in validating {0} name

Cause: Specified {0} name is either not valid or the corresponding location is not empty

Action: Enter a valid {0} name
Level: 1

Type: ERROR

Impact: Installation

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

Cause: Specified {0} home location does not have Read/Write permissions

Action: Provide Read/Write permissions for the specified {0} home location
Level: 1

Type: ERROR

Impact: Installation

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

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

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07280: Error in validating domain credentials

Cause:

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07281: Error in validating domain credentials

Cause: {0} is not set up in the specified domain

Action: Enter a domain which has {0} set up
Level: 1

Type: ERROR

Impact: Installation

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

Cause: Specified {0} home location does not exist

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

Type: ERROR

Impact: Installation

INST-07283: Error in validating My Oracle Support Details

Cause: Specified My Oracle Support Details are not proper

Action: Enter valid values
Level: 1

Type: ERROR

Impact: Installation

INST-07284: Error in validating My Oracle Support Details

Cause: An unexpected error occurred while validating My Oracle Support Details

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07285: Error in validating Database details. Invalid Schema

Cause: The schema name {0} and schema type {1} do not match

Action: Provide a valid schema name for {1}
Level: 1

Type: ERROR

Impact: Installation

INST-07286: Error in validating Middleware home location

Cause: Specified Oracle Middleware home location does not have minimum version {0} of WebLogic server. If the version is incorrect then configuring with the Weblogic server will fail.

Action: Provide a Oracle Middleware home location which contains WebLogic server with minimum version {0} or upgrade the Weblogic server to {0} or higher version and restart the install.
Level: 1

Type: ERROR

Impact: Installation

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

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server. Server is not running.

Action: Make sure the Middleware Administration Server is up
Level: 1

Type: ERROR

Impact: Installation

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

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server. Invalid username/password

Action: Enter a valid username and password
Level: 1

Type: ERROR

Impact: Installation

INST-07289: Error in validating WebLogic Server Directory

Cause: Specified WebLogic Server Directory is either not valid or empty

Action: Enter a valid WebLogic Server Directory
Level: 1

Type: ERROR

Impact: Installation

INST-07290: Error in validating Oracle home location

Cause: Specified Middleware home already has a {0} home. Only one {0} home location can reside under a Middleware home.

Action: Provide a different Middleware home location
Level: 1

Type: ERROR

Impact: Installation

INST-07291: Error in validating Oracle home location

Cause: Top Component name specified is null.

Action: Provide a valid component name
Level: 1

Type: ERROR

Impact: Installation

INST-07292: Error in validating Middleware home location

Cause: Middleware home location specified is not a valid location. Provide a valid Middleware home location

Action: Provide a valid Middleware home location.
Level: 1

Type: ERROR

Impact: Installation

INST-07293: Error in validating SSO credentials

Cause: Given OID does not have a proper SSO.

Action: Provide an OID with a 10g SSO.
Level: 1

Type: ERROR

Impact: Installation

INST-07294: Error in validating SSO credentials

Cause: Could not retrieve SSO information with the given credentials.

Action: Verify the credentials. Make sure that hostname, port and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07295: Error in validating UCM Installer Location

Cause: Specified UCM Installer Location is not valid

Action: Provide a valid value for UCM Installer Location.
Level: 1

Type: ERROR

Impact: Installation

INST-07296: Error in validating UCM Installer Location

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07297: Error in validating Web Server HTTP Address

Cause: Webserver HTTP Address is missing

Action: Provide a valid value for Webserver HTTP Address
Level: 1

Type: ERROR

Impact: Installation

INST-07298: Error in validating Web Server HTTP Address

Cause: Specified Web Server HTTP Address is not valid

Action: The Web Server HTTP Address has to be in http(s)://[host]:[port]?/[webroot] format
Level: 1

Type: ERROR

Impact: Installation

INST-07299: Error in validating Web Server HTTP Address

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07300: Error in validating UCM Installer Location

Cause: UCM Installer Location is missing

Action: Provide a valid value for UCM Installer Location
Level: 1

Type: ERROR

Impact: Installation

INST-07301: Error in validating UCM Installer Location

Cause: Specified UCM Installer Location is empty

Action: Provide a valid value for UCM Installer Location.
Level: 1

Type: ERROR

Impact: Installation

INST-07302: Error in validating Domain

Cause: Specified domain cannot be used for Expand Cluster configuration

Action: Specify a domain which has clusters
Level: 1

Type: ERROR

Impact: Installation

INST-07303: Error in validating Domain

Cause: Specified domain cannot be used for Extend Domain configuration

Action: Specify a domain which has at least one component not configured
Level: 1

Type: ERROR

Impact: Installation

INST-07304: Validation of User Name failed. Invalid User Name

Cause: The user name entered is not valid

Action: Provide a valid user name
Level: 1

Type: ERROR

Impact: Installation

INST-07305: Validation of password value failed. Invalid password

Cause: The password entered is not valid

Action: Provide a valid password
Level: 1

Type: ERROR

Impact: Installation

INST-07306: Error in validating Database details. RAC Dabase is not supported

Cause: RAC Database is not supported for {0}

Action: {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07307: Error in validating Oracle home location

Cause: Oracle home location specified is not inside Middleware home location. Provide a valid location for Oracle home.

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07308: Oracle Universal Content Management is already installed and configured at location {0}

Cause: Oracle Universal Content Management is already installed and configured at location {0}

Action: Either select not to configure again or uninstall Oracle Universal Content Management and then try to reconfigure
Level: 1

Type: ERROR

Impact: Installation

INST-07309: Error in validating master repository details

Cause: Specified Master Repository credentials are not valid.

Action: Verify the values. Make sure the Master Database is up and running and connect string, user name, password, ODI supervisor username and ODI supervisor password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07310: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:servicename
Level: 1

Type: ERROR

Impact: Installation

INST-07311: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:sid
Level: 1

Type: ERROR

Impact: Installation

INST-07312: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:servicename , For Real Application Cluster Database hostname1:port1^hostname2:port2@servicename
Level: 1

Type: ERROR

Impact: Installation

INST-07313: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:sid , For a Real Application Cluster Database, use hostname1:port1^hostname2:port2@servicename
Level: 1

Type: ERROR

Impact: Installation

INST-07314: Error in validating port file

Cause: Port {0} is not valid

Action: Provide a valid port number ( a number between {0} )
Level: 1

Type: ERROR

Impact: Installation

INST-07315: Error in validating port value

Cause: An unexpected error occurred while validating port value

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07316: Error in validating port file

Cause: Port {0} is not free or not valid

Action: Ensure that the port ( a number between 1024 - 65535 ) is free and it is not used by any other Oracle Home. If ports are specified using a file, check if proper values are given for key.
Level: 1

Type: ERROR

Impact: Installation

INST-07317: Validation of {0} location failed. Directory does not exist.

Cause: Validation of {0} location failed. The location specified does not exist.

Action: Enter a valid existing directory
Level: 1

Type: ERROR

Impact: Installation

INST-07318: Validation of {0} location failed. Directory s empty.

Cause: Validation of {0} location failed. The location specified is empty.

Action: Enter a nonempty directory
Level: 1

Type: ERROR

Impact: Installation

INST-07319: Validation of {0} location failed. Directory already exists and is not a valid Oracle Home directory.

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

Action: Provide an empty or nonexistent directory location, or a valid existing Oracle Home
Level: 1

Type: ERROR

Impact: Installation

INST-07320: 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 256 characters
Level: 1

Type: ERROR

Impact: Installation

INST-07404: Error in validating Oracle home

Cause: Specified Oracle home value is null

Action: Specify the correct Oracle home name
Level: 1

Type: ERROR

Impact: Installation

INST-07405: Error in validating Oracle home

Cause: The specified Oracle home does not match with the Domain Oracle home

Action: Specify Oracle home name same as that of the Domain Oracle home
Level: 1

Type: ERROR

Impact: Installation

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

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

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

Type: ERROR

Impact: Installation

INST-07407: Error in detecting machine platform or JVM bits.

Cause: Unable to detect machine platform or JVM bits.

Action: Make sure machine platform and JVM are supported.
Level: 1

Type: ERROR

Impact: Installation

INST-07408: Cannot install or configure the product on a 32-bit JVM on a 64-bit machine.

Cause: Unable to install or configure the product on a 32-bit JVM on a 64-bit machine.

Action: Make sure to install and configure the product in supported modes.
Level: 1

Type: ERROR

Impact: Installation

INST-07409: Error in validating instance name

Cause: Unexpected error in validating instance name

Action: Make sure entered values are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07410: Error in validating instance name

Cause: Specified instance name is not valid, a windows service with the specified instance name already exists

Action: Provide a different instance name
Level: 1

Type: ERROR

Impact: Installation

INST-07411: Error in validating oracle home

Cause: Provide valid value for Oracle Home Directory.

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07412: Error in validating Oracle Home

Cause: Oracle Home Directory name cannot be oracle_common.

Action: Provide a different value for Oracle Home Directory.
Level: 1

Type: ERROR

Impact: Installation

INST-07413: Error in validating Oracle Home

Cause: Unexpected error in validating Oracle Home Directory

Action: Make sure entered values are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07414: Error in validating {0}

Cause: Specified {0} is not valid

Action: Provide a valid value {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07415: Error in validating Home Type

Cause: Home Type Specified is not Correct

Action: Provide a valid a valid Home Type
Level: 1

Type: ERROR

Impact: Installation

INST-07416: Error in validating {0}

Cause: An unexpected error occurred while validating {0}

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07417: Error in validating the {0}

Cause: {0} has not been installed in the specified {1}. Provide a different Location

Action: Provide a different {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07420: Error in validating Oracle Home

Cause: Oracle Home Directory name cannot be {0}.

Action: Provide a different value for Oracle Home Directory.
Level: 1

Type: ERROR

Impact: Installation

INST-07421: Error in executing the software update flow

Cause: An error occurred while validating the values for software updates

Action: Make sure entered values are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07422: Error in validating library

Cause: The library {0} does not exists in the provided location

Action: Make sure the library {0} exists in the provided location
Level: 1

Type: ERROR

Impact: Installation

INST-07423: Error in validating library

Cause: The library {0} does not exists in the provided location

Action: Make sure the library {0} exists in the provided location
Level: 1

Type: ERROR

Impact: Installation

INST-07424: Error in validating library

Cause: The version of library at the provided location is not as expected

Action: Make sure the version of library at the provided location is correct
Level: 1

Type: ERROR

Impact: Installation

INST-07425: Error in verifying version of Application Server

Cause: Could not access versionInfo script under the Application Server Directory provided

Action: Make sure the the Application Server directory has versionInfo script under bin folder
Level: 1

Type: ERROR

Impact: Installation

INST-07426: Error in verifying version of Application Server

Cause: The version of Application Server is not valid

Action: Make sure the the version of Application Server is at least {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07427: Error in verifying Application Server

Cause: The Application Server Directory does not refer to WebSphere Application Server

Action: Provide the directory location of WebSphere Application Server
Level: 1

Type: ERROR

Impact: Installation

INST-07440: Error in validating Application Server Type

Cause: Validation of Application Server Type failed. Supported Application Server Types are WLS and WAS.

Action: Specify a valid Application Server Type. Supported Application Server Types are WLS and WAS.
Level: 1

Type: ERROR

Impact: Installation

INST-07441: Error in validating Application Server Type

Cause: Validation of Application Server Type failed. Specified Application Server Type does not match with the Application Server detected in the Middleware home.

Action: Specify a valid Application Server Type.
Level: 1

Type: ERROR

Impact: Installation

INST-07509: Error in validating master repository details

Cause: Specified Master Repository schema details are not valid.

Action: Verify the values. Make sure the Master Database schema version is correct and master repository is created with appropriate Repository Creation Utility.
Level: 1

Type: ERROR

Impact: Installation

INST-07520: Error in validating {0} location

Cause: Enter a valid value for {0} location

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07521: Error in validating {0} home location

Cause: Specified {0} home location does not exist

Action: Provide an exisiting {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07522: Error in validating {0} home location

Cause: Specified {0} home location does not have read/write permissions

Action: Provide read/write permissions for the {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07523: Error in validating {0} home location

Cause: Specified {0} home location is either not valid or empty

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07524: Error in validating {0} home location

Cause: Specified {0} home location is not a valid location

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07525: Error in validating {0} home location

Cause: An unexpected error occurred during the validation of {0} home location

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07526: Error in validating {0} home location

Cause: Specified {0} home location is not a valid location

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07527: Error in validating Middleware home location

Cause: Specified Oracle Middleware home location does not have appropriate version of WebLogic server

Action: Provide a Oracle Middleware home location which contains WebLogic server with a supported version
Level: 1

Type: ERROR

Impact: Installation

INST-07528: Validation of {0} location failed. Directory does not exist.

Cause: Validation of {0} location failed. The location specified does not exist.

Action: Enter a valid existing directory
Level: 1

Type: ERROR

Impact: Installation

INST-07529: Error in validating Farm Name

Cause: Farm Name cannot be {0}.

Action: Enter a different Farm Name.
Level: 1

Type: ERROR

Impact: Installation

INST-07530: Patchset component found in Oracle home

Cause: This Patchset has already been applied to the Oracle home

Action: Specify an Oracle home where the patchset has not already been applied.
Level: 1

Type: ERROR

Impact: Installation

INST-07531: Error in validating contents of Oracle home

Cause: The Oracle home provided does not contain {0}.

Action: In order to patch your existing version please provide an Oracle home that contains the product mentioned above. If you choose to continue, only the oracle_common directory and any components that both products have in common will be patched.
Level: 1

Type: ERROR

Impact: Installation

INST-07532: Error in validating contents of Oracle home

Cause: The Oracle home provided does not contain {0}.

Action: In order to patch your existing version please provide an Oracle home that contains the product mentioned above. If you choose to continue, only the oracle_common directory and any components that both products have in common will be patched.
Level: 1

Type: ERROR

Impact: Installation

INST-07533: Error in validating Middleware home location

Cause: Middleware home location specified is missing.

Action: Provide a valid Middleware home location
Level: 1

Type: ERROR

Impact: Installation

INST-07534: Error in validating Oracle home location

Cause: Oracle home location specified is not inside Middleware home location. Provide a directory name only for Oracle home.

Action: Provide a different Oracle home location which is inside Middleware home.
Level: 1

Type: ERROR

Impact: Installation

INST-07535: Error in obtaining hostname

Cause: An unexpected error occurred while retrieving hostname

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07536: Error in validating Oracle home location

Cause: Middleware home location specified does not have the required Oracle homes installed in it. The Oracle homes for the following components are not installed: {0}.

Action: Provide a different Middleware home location or install the required Oracle Products and try the install again
Level: 1

Type: ERROR

Impact: Installation

INST-07537: The weblogic server processes are still running.

Cause: Unable to install while the weblogic processes are running.

Action: Make sure that the node manager and the weblogic servers are shutdown before the installation.
Level: 1

Type: ERROR

Impact: Installation

INST-07538: The OPMN processes are still running.

Cause: Unable to install while the OPMN processes are running.

Action: Make sure that opmnctl stopall is run before the installation.
Level: 1

Type: ERROR

Impact: Installation

INST-07539: {0} found in Oracle home

Cause: This Oracle home already contains a version of {0} which cannot be updated by this installation

Action: Specify either a new Oracle Home Directory or an Oracle Home which can be updated by this installer.
Level: 1

Type: ERROR

Impact: Installation

INST-07540: Missing Dependent Feature sets in {0}

Cause: Enter a valid {0} which has all required dependent featuresets

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07541: Error in validating Feature set Dependencies in {0}

Cause: Unexpected Error

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07542: Error in validating Oracle Home location.

Cause: The distribution {0} is not installed in the given Oracle Home.

Action: Choose a different Oracle Home location.
Level: 1

Type: ERROR

Impact: Installation

INST-07543: Error in validating Oracle Home location.

Cause: {0} cannot be installed in an Oracle Home that has {1} already installed.

Action: Choose a different Oracle Home location.
Level: 1

Type: ERROR

Impact: Installation

INST-07544: Error in validating Oracle Home location.

Cause: Oracle Home provided is null or empty

Action: Provide a different Oracle Home location.
Level: 1

Type: ERROR

Impact: Installation

INST-07545: Error in validation. Unexpected Error

Cause: Unexpected Error. {0}

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07546: Error in validating installation type.

Cause: Unable to find install type {0}

Action: Provide a valid install type
Level: 1

Type: ERROR

Impact: Installation

INST-07547: Incompatible installation type.

Cause: Incompatible installation type provided. {0}

Action: Select a valid install type. Check http://www.oracle.com/pls/topic/lookup?ctx=fmw122110&id=installhome for details about compatible products and install types.
Level: 1

Type: ERROR

Impact: Installation

INST-07548: No compatible installation type found.

Cause: The selected distribution does not have any compatible install type for the selected Oracle Home.

Action: Provide a different oracle Home. Check http://www.oracle.com/pls/topic/lookup?ctx=fmw122110&id=installhome for details about compatible products and install types.
Level: 1

Type: ERROR

Impact: Installation

INST-07549: No compatible installation type found.

Cause: Incompatible Installation Type : {0}

Action: Incompatibility Details : {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07550: Unable to find dependent featuresets for the selected installation type

Cause: Unable to find dependent featuresets for the selected installation type. {0}

Action: Select a different install type or provide a different Oracle Home having all dependencies. Check http://www.oracle.com/pls/topic/lookup?ctx=fmw122110&id=installhome for details about compatible products and install types.
Level: 1

Type: ERROR

Impact: Installation

INST-07551: Unable to find dependent featuresets for the selected installation type

Cause: Not all dependent featuresets for install type "{0}" could be found. {1}

Action: Select a different Oracle Home having all dependencies. Check http://www.oracle.com/pls/topic/lookup?ctx=fmw122110&id=installhome for details about compatible products and install types.
Level: 1

Type: ERROR

Impact: Installation

INST-07939: Error in validating install types

Cause: Unexpected error in validating install types

Action: Make sure entered values are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07940: Error in validating install types

Cause: This installation type cannot be installed, because the selected Oracle Home contains Oracle Fusion Middleware Infrastructure.

Action: For more information about the prerequisites for this install type, see Installing and Configuring Oracle HTTP Server in the Oracle Fusion Middleware documentation library.
Level: 1

Type: ERROR

Impact: Installation

INST-07941: Error in validating install types

Cause: This installation type cannot be installed, because Oracle Fusion Middleware Infrastructure is not installed in the selected Oracle Home.

Action: For more information about the prerequisites for this install type, see Installing and Configuring Oracle HTTP Server in the Oracle Fusion Middleware documentation library.
Level: 1

Type: ERROR

Impact: Installation

INST-08001: Validation of Middleware home location failed. Directory path invalid

Cause: Validation of Middleware home location failed. The location specified contains missing, mandatory directories

Action: Make sure that Oracle/Middleware is in the path
Level: 1

Type: ERROR

Impact: Installation

INST-10001: Error in validating Component Dependency Details

Cause: Dependency for {0} is missing. Missing dependent component ids are {1}.

Action: Make sure to select / specify all dependent components
Level: 1

Type: ERROR

Impact: Installation

INST-10002: Error in validating Component Dependency Details

Cause: Component Ids {0} are invalid

Action: Provide valid component id
Level: 1

Type: ERROR

Impact: Installation

INST-10003: Error in validating Component Dependency Details

Cause: An unexpected error occurred while validating Component Dependency Details

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-10101: Error in validating {0} Base Image Location

Cause: {0} Base Image Location is null or blank.

Action: Provide a valid {0} Base Image Location
Level: 1

Type: ERROR

Impact: Installation

INST-10102: Error in validating {0} Base Image Location

Cause: The {0} Base Image Location provided is not existing or not a valid file

Action: Provide a valid {0} Base Image Location
Level: 1

Type: ERROR

Impact: Installation

INST-10103: Error in validating the {0} Base Image Location for Assembly Builder

Cause: An unexpected error occurred while validating the {0} Base Image Location for Assembly Builder

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-10104: Error in validating {0} Base Image Location

Cause: The {0} Base Image File name must be {1}

Action: Provide a valid {0} Base Image Location
Level: 1

Type: ERROR

Impact: Installation

INST-10105: Error in validating {0} Base Image Virtual Machine configuration file Location

Cause: The {0} Base Image Virtual Machine configuration File (vm.cfg) is not existing

Action: The vm.cfg file must be present in same directory as the Base Image ({1}), provide a valid {0} Base Image Location
Level: 1

Type: ERROR

Impact: Installation

INST-10106: Error in validating Keystore

Cause: An unexpected error occurred while validating the {0} Keystore for Assembly Builder

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-10107: The Keystore path must not be null or blank

Cause: The Keystore path must not be null or blank

Action: Provide a valid Keystore path
Level: 1

Type: ERROR

Impact: Installation

INST-10108: The Keystore password must not be null or blank

Cause: The Keystore password must not be null or blank

Action: Provide a valid Keystore password
Level: 1

Type: ERROR

Impact: Installation

INST-10109: Invalid keystore.

Cause: Failed to validate the Keystore.

Action: Provide a valid Keystore
Level: 1

Type: ERROR

Impact: Installation

INST-10110: The Key password must not be null or blank

Cause: The Key password must not be null or blank

Action: Provide a valid Key password
Level: 1

Type: ERROR

Impact: Installation

INST-10111: The Key alias must not be null or blank

Cause: The Key alias must not be null or blank

Action: Provide a valid Key alias
Level: 1

Type: ERROR

Impact: Installation

INST-10112: Invalid key alias

Cause: Invalid key alias and password combination.

Action: Provide a valid Key alias and password combination
Level: 1

Type: ERROR

Impact: Installation

INST-10113: Error in validating Component Version

Cause: Component Version is null or blank.

Action: Provide a valid Component Version.
Level: 1

Type: ERROR

Impact: Installation

INST-10114: Error in validating Component List

Cause: Component List is null or blank.

Action: Provide a valid Component List.
Level: 1

Type: ERROR

Impact: Installation

INST-10115: Error in validating Oracle Home

Cause: Oracle Home is null or blank.

Action: Provide a valid Oracle Home.
Level: 1

Type: ERROR

Impact: Installation

INST-10116: Installation of Studio and Deployer detected in the selected Oracle Home. Installing into an existing Oracle Home is done to either reinstall binaries or to upgrade an Oracle Home from one release to another

Cause: Installation of Studio and Deployer detected in the selected Oracle Home.

Action: Installing into an existing Oracle Home is done to either reinstall binaries or to upgrade an Oracle Home from one release to another.
Level: 1

Type: ERROR

Impact: Installation

INST-10117: Error in validating the installed component in {0} Oracle Home

Cause: An unexpected error occurred while validating the installed component in {0} Oracle Home

Action: An unexpected error occurred while validating the installed component in {0} Oracle Home
Level: 1

Type: ERROR

Impact: Installation

24 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

25 JBO-24000 to JBO-80008

JBO-24000: no JAAS Context. Permission information is not available.

Cause: An error occurred while initializing the Java Authentication and Authorization Service (JAAS).

Action: Make sure that the JAAS configuration is correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-24001: Role {0} is not found.

Cause: An error occurred while retrieving the role.

Action: Make sure that the role information is correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-24002: User {0} is not found.

Cause: An error occurred while retrieving the user.

Action: Make sure that the user information is correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-24003: Attribute {2} in entity {1} is not updatable.

Cause: An attempt was made to update the attribute, but the user did not have permission or the attribute was not updatable.

Action: Make sure that the user permission and updatable setting for the attribute are correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-24004: Rows cannot be removed from entity {0}.

Cause: An attempt was made to remove the row, but the user did not have permission or the entity was read-only.

Action: Make sure that the user permission and read-only setting for the entity are correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-24005: Rows cannot be created in entity {0}.

Cause: An attempt was made to create a row, but the user did not have permission or the entity was read-only.

Action: Make sure that the user permission and read-only setting for the entity are correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-24006: The entity already has permission defined.

Cause: The entity already has permission defined.

Action: Modify permission def is not allowed.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-24007: Unable to get system property {0} when security manager is enable.

Cause: The property is not defined.

Action: Get property value is not allowed.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25000: SQL type {0} is invalid.

Cause: An attempt was made to generate a null value for a domain with an invalid SQL type.

Action: Provide a valid SQL type name for the domain. Examples include VARCHAR, CHAR and NUMBER. See oracle.jbo.server.OracleTypeMapEntries for a full list.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25001: Object {1} of type {0} already exists.

Cause: An attempt was made to load a business component with the same name and type as another business component already loaded by the application module.

Action: Provide a different name for the business component. If a null value or null string is provided for the name, the framework will create a unique name within the scope of the application module.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25002: Definition {1} of type {0} is not found.

Cause: A definition object with the given name could not be found.

Action: Provide a correct name for the business component definition (using the format 'packagename.objectname') and ensure that the definition is available on the classpath. This error can also occur if there is a case conflict, as when the database expects 'DEPTNO' and receives 'Deptno' instead.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25003: Object {1} of type {0} is not found.

Cause: A business component object with the given name could not be found in the application module.

Action: Provide a different name for the business component object or create a new business component with the given name.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25004: Definition name {1} of type {0} is invalid.

Cause: An attempt has been made to load an invalid definition name or associate a definition name with a type for which it is not valid.

Action: Ensure that the name is a valid Java identifier with no spaces or punctuation, and conforms to the format 'packagename.objectname'.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25005: Object name {1} of type {0} is invalid.

Cause: An attempt has been made to associate a business component name with an object for which it is not valid.

Action: Ensure that the name is a valid Java identifier with no spaces or punctuation, and conforms to the format 'packagename.objectname'.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25006: Value {2} passed as parameter {1} to method {0} is invalid: {3}.

Cause: An attempt was made to invoke a business components method with an invalid parameter value.

Action: Pass a correct value for the parameter. To determine the allowed values for a given parameter, check the Javadoc for the method that throws this exception. For example, Javadoc indicates that the 'DBTransactionImpl.executeCommand' method throws this exception when the 'command' parameter is empty.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25007: The validation flag cannot be reset for a default iterator.

Cause: An attempt was made to reset the row validation flag for the default iterator of a rowset or view object.

Action: Reset the row validation flag for the rowset or view object instead. This will create a secondary iterator to allow the rowset or viewobject to navigate to another row without validating.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25008: Object {0} cannot be removed because it is referenced by object {1}.

Cause: An attempt was made to remove a view object that is participating in a view link.

Action: Remove the view link before removing the view object.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25009: Cannot create an object of type:{0} from type:{2} with value:{1}

Cause: A domain object could not be created with the given value. Either a domain constructor that accepts the given value does not exist, or there is no conversion method in the domain object for the given value type, or the domain constructor threw an unexpected exception.

Action: Ensure that the value being passed is valid with respect to the domain type being created. For example, passing the string value 'one' to the 'oracle.jbo.domain.Number' constructor will throw this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25010: A validation failure has occurred while creating a domain with value {0}.

Cause: Validation failed with the given value in a domain constructor. This exception is thrown in the domain type 'validate()' method.

Action: Provide a valid value for the domain type.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25011: Rowset {0} is forward only.

Cause: An attempt was made to invoke an invalid navigation method on a forward-only view object or rowset.

Action: Either remove the forward-only setting for the view object or rowset, or do not invoke navigation methods other than 'next()' on the forward-only view object or rowset.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25012: View object {0} does not have entity {1} as its primary base.

Cause: The client attempted to locate a view row that has the given entity row as its primary entity row. However, the entity row's entity definition does not match the entity definition of the view object's primary entity object base.

Action: Ensure that the entity row used to locate view rows is based on the same entity definition as the view object's primary entity object base.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25013: Too many objects match the primary key {0}.

Cause: An attempt was made to add a newly fetched or created entity to the cache, but the new entity has the same primary key as an existing entity. The primary key must be unique for this entity type.

Action: Add more attributes to the key definition for the entity type, so that each row for this entity is uniquely identifiable. Or fix the primary key value so that this entity has a unique key identifier.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25014: Another user has changed the row with primary key {0}.

Cause: The database value does not match the cached value for this entity object. This could happen when another user or operation has committed modifications to the same entity row in the database. This exception can also be thrown if the 'equals' method on one of the domain type attributes in the entity fails.

Action: Choose from the following options: 1. Verify that another user or operation has not modified the same row in the database. If this entity has attributes of a domain type verify that the <code>equals()</code> method on these domains do not fail when comparing the existing cached value with the newly fetched value. 2. For any attributes/columns that are updated by the database, modify the entity attribute definition by selecting 'Refresh after update' on the Attribute Settings page of the Entity Object Wizard. 3. Use 'view.executeQuery()' frequently, especially after any operations that result in data being changed.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25015: Query collection {0} is closed.

Cause: An attempt was made to execute a query or access a row from a closed or removed view object or rowset.

Action: Verify that the view object or rowset is not removed or closed.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25016: View object {0} is read-only.

Cause: An attempt was made to modify data for a view object which is declared to be read-only. This includes creating a new row for this view object, removing a row, or modifying attributes of a view row for this view object.

Action: Create a view object with the read-only flag set to 'false' in order to modify data.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25017: New entity row of type {0} cannot be created.

Cause: An unexpected exception occurred while creating a new entity instance.

Action: Ensure that the entity has a public default constructor. Fix the cause of the InstantiationException or IllegalAccessException that appears in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25018: New view row of type {0} cannot be created.

Cause: An unexpected exception occurred while creating a new view row instance.

Action: Ensure that the view row has a public default constructor. Fix the cause of the InstantiationException or IllegalAccessException that appears in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25019: Entity row with key {1} is not found in {0}.

Cause: An attempt was made to lock a nonexistent row in the database. This could occur when the cache has an entity which was subsequently deleted from the database by another user or operation.

Action: Remove the current entity from the entity cache by calling 'remove'. Or, synchronize the cache with the database by rolling back the current transaction or by committing the existing set of changes and then dropping the entity cache.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25020: View row with key {1} is not found in {0}.

Cause: An attempt to find a referenced entity in the view row failed due to a changed foreign key value.

Action: Provide a valid foreign key value or remove the current one.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25021: Domain object type {0} cannot be created.

Cause: A domain object could not be created with the given value. Either a domain constructor that accepts the given value does not exist, or there is no conversion method in the domain object for the given value type, or the domain constructor threw an unexpected exception.

Action: Ensure that the value being passed is valid with respect to the domain type being created. For example, passing the string value 'one' to the 'oracle.jbo.domain.Number' constructor will throw this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25022: A view link {0} already exists between source view object {1} and destination view object {2}.

Cause: An attempt was made to set the master rowset for this rowset more than once.

Action: Do not invoke 'setMasterRowSetIterator' more than once on a rowset.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25023: Operation {0} on domain value {1} of class {2} cannot be performed.

Cause: An unexpected domain exception occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25024: Method {0} is obsolete.

Cause: An attempt was made to use an obsolete type map constructor.

Action: Verify that the type map is compatible with this version of the framework. See example type maps in 'oracle.jbo.server.OracleTypeMapEntries'.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25025: Rowset with XML tag {0} cannot be loaded.

Cause: An error occurred while reading the XML data for a view object. This exception might contain other ReadXMLExceptions.

Action: Fix the contained row-level or attribute-level exceptions in the details for this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25026: Row {1} with XML tag {0} cannot be loaded.

Cause: An error occurred while reading the XML data for a view row. This exception might contain other ReadXMLExceptions for contained rowsets or attributes.

Action: Fix the rowset-level or attribute-level exceptions in the details for this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25027: Attribute {1} at index {2} with XML tag {0} cannot be loaded.

Cause: An error occurred while reading the XML data for an attribute of a view row. This exception might contain other JboExceptions thrown from the set method for this attribute.

Action: Fix the JboException in the details for this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25028: Domain object type {0} cannot be created: {1}.

Cause: A domain object could not be created with the given value. Either a domain constructor that accepts the given value does not exist, or there is no conversion method in the domain object for the given value type, or the domain constructor threw an unexpected exception.

Action: Ensure that the value being passed is valid with respect to the domain type being created. For example, passing the string value 'one' to the 'oracle.jbo.domain.Number' constructor will throw this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25029: Domain class {0} is not found.

Cause: The named data class (typically a domain) could not be found.

Action: Ensure that the data class is accessible from the CLASSPATH and is a valid data class.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25030: Detail entity {0} with row key {1} cannot find or invalidate its owning entity.

Cause: No container entity was found for a detail entity in a composition association. This could occur if a nonexistent master key value was passed in during creation of a new detail entity instance, or if the foreign key value of this entity was modified so that it no longer matched any master entity.

Action: Pass a valid foreign key value to the 'create' method or 'setAttribute' method so that an appropriate master row is found for this entity.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25031: View row for view object {0} is missing entity row for {1}.

Cause: The client attempted to access an attribute of a view which is mapped to an entity row, but the corresponding entity row is null. If the view object consists of multiple entity object bases and if the secondary entity object bases are reference-only, the entity rows could be null if the foreign key linking the primary entity to the secondary entity object is null.

Action: Do not try to access attributes of missing entity rows in this situation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25032: Passivation to target store {1} is unsuccessful.

Cause: A failure occurred while trying to passivate the application module or transaction state.

Action: Resolve the detail exception raised by the passivation target store (Database, File or Memory).
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25033: Activating state with id {0} from target store {1} is unsuccessful.

Cause: A failure occurred while trying to activate the application module or transaction state.

Action: Resolve the detail exception raised by the passivation target store (Database, File or Memory) and ensure that the state snapshot ID exists in the target store.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25034: Row with handle {1} is not found in rowset {0}.

Cause: The client attempted to locate a row with a stale row handle. This error might be raised if the client tries to take a row out of one query collection and use its handle to find a row in another query collection. Note that if the client calls executeQuery on a rowset, it might receive a new query collection. Thus, this error might occur if the client retrieves a row from a rowset, takes its row handle, calls executeQuery, and then tries to locate the row using the saved handle. This exception might also be raised if a row reference is used across transaction boundaries and the row handle has become stale and hence the corresponding row cannot be found.

Action: Make sure that the row handle is not stale. One approach is to find the row again using its primary key before attempting to act on the row.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25035: The application module passivation store is invalid.

Cause: An application attempted to change an application module's passivation store after it had been initialized. The passivation store (Database, File or Memory) can only be initialized once. If the customer application logic has not specified a passivation store when the serialization framework is invoked, the passivation store is initialized by the framework.

Action: Check the client application logic for invocations of ApplicationModuleImpl.setStoreForPassiveState which are invoked after the application module passivation store has been initialized.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25036: An invalid object operation was invoked on type {0} with name {1}

Cause: An application invoked an object operation that is not supported in the object's current state.

Action: Remove the invalid operation invocation or provide exception handling logic.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25037: Detail row set {0} is missing a master row set iterator for view link {1}, master view object {2}.

Cause: This row set is a detail in a master-detail relationship, but it is missing a master row set iterator. Most likely, this occurred because a master row set iterator was removed through a call to removeMasterRowSetIterator() and has not been replaced with an appropriate one.

Action: Call setMasterRowSetIterator() to provide a valid master row set iterator.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25038: Value {2} passed as parameter {1} to method {0} is invalid.

Cause: An attempt was made to invoke a business components method with an invalid parameter value.

Action: Refer to the documentation of error message JBO-25006 (EXC_INVALID_PARAMETER) for more information. The difference between this error message and EXC_INVALID_PARAMETER is that this version does not include an explanation. In general, Oracle recommends using JBO-25006 instead of JBO-25038.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25039: No current row in row set iterator {0}

Cause: The client attempted to work with the current row of a row set iterator, but the iterator has no current row.

Action: Position the iterator to the correct row and perform the operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25040: Row should be locked before getting an output stream from an attribute.

Cause: The row containing a large object was not locked before attempting to call a method on the large object that could potentially change the data of the object.

Action: Lock the row before attempting to get an output stream or write into a large object domain instance.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25041: Type map cannot convert data from {1} to {0} with operation {2}.

Cause: The TypeFactory class asked the TypeMapEntries class to convert data, but the TypeMapEntries class did not know how to perform the conversion. This is typically an issue with the TypeMapEntries implementation.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25042: Row of trans post listener handle {0} not found in list.

Cause: Entity row of the given handle is not found in transaction post listener list. Most likely cause of this error is as follows: the user requests certain operation. The operation tries to get access to the row in database. This fails for whatever reason (this exception's detail might have further information). The system tries to fix the problem at the entity level. It looks for the entity row in the transaction post listener list. The specified row is not found.

Action: Look at the details and see if the cause can be determined from them. Check to see if concurrent updates to database could have caused the problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25043: Extraneous key {0} of index {1} (in key-value array) passed to findByKey for view object {2}.

Cause: Extraneous key passed in to findByKey(). For example, suppose the View Object expects no more than a two-part key, but the key passed into findByKey is a three-part key. Then, this exception will be thrown.

Action: Provide a valid key.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25044: Application state snapshot is based on an older version of the application definition metadata.

Cause: An attempt was made to activate application module or transaction state based on an older metadata definition into an application module with a later metadata definition.

Action: Ensure that snapshots used for state activation were generated from the currently running version of the application definition metadata.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25045: Row set iterator {0} has detected an implicit synchronization attempt.

Cause: An attempt was made to implicitly synchronize an iterator in a 3-tier running environment. When the application module synchronization mode is set to SYNC_BATCH, iterator synchronization must be done explicitly.

Action: Remove code that attempts to synchronize the iterator implicitly.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25046: Requested row not available in row set iterator {0}.

Cause: This exception is thrown when running in 3 tier SYNC_BATCH mode. The user requested a row, but that row is not available in the cache.

Action: Make appropriate API calls to bring the required row into cache. Then, try to get the row again.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25047: Attempt to make call to server detected for application module {0}.

Cause: An attempt to make a call to server detected for an operation that is supposed to work only with client cache.

Action: Remove code/operation that attempts to call server.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25048: Operation {0} is invalid for a working set object.

Cause: This operation is invalid for this working set object. It might be because the operation doesn't make sense in batch mode, or because the batch communication mode (WSApplicationModuleImpl.getBatchCommMode()) does not allow this operation.

Action: Remove code/operation that calls the named method of set the batch communication mode to allow this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25049: Entity {0} cannot be set to batch mode because a key attribute is marked as refresh-on-insert or refresh-on-update.

Cause: An attempt was made to set batch mode on an entity that has a primary key marked as refresh-on-insert or refresh-on-update.

Action: Remove the refresh-on-insert or refresh-on-update setting of the primary key attribute.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25050: Batch mode post operation failed. See Exception details for a list of failures.

Cause: Posting entities in batch mode failed with a set of exceptions

Action: Fix the cause for each of the exceptions in the details array.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25051: Row of range index {1} is not found in RowSetIterator {0}.

Cause: The client has attempted to locate a row with a range index, but the Row Set Iterator's range does not have a row at the index. It might be that the range index is too big (>= the range size), or that the range is at the bottom and the range index is beyond the last row of the Row Set. Or, the Row Set might have been reset because of operations like rollback and clear-cache. Hence, the range is empty and no row is found

Action: Make sure that the row set iterator is open and has rows in its range. Also, make sure that the range index falls between the first and the last row of the range.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25052: View object {0} with no key attributes cannot be activated.

Cause: A view object with no key attributes was configured to passivate one or more of its transient attributes. However, a view object without key attributes cannot participate in state passivation.

Action: Define one or more key attributes for this view object.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25053: Cannot navigate with unposted rows in a RangePaging RowSet.

Cause: An attempt has been made to navigate a rowset in Range Paging mode when the rowset has inserted/removed rows.

Action: Post this transaction before navigating.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25054: Cannot locate the specified stack snapshot id: {0}

Cause: An attempt has been made to activate a stack snapshot that does not exist. The specified snapshot might already have been activated or the stack might already have been cleared by a previous rollback/commit.

Action: Ensure that stack snapshot ids are maintained by the application across transaction boundaries.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25055: Snapshot {0} cannot be removed.

Cause: An attempt was made to remove a persistent snapshot that is referenced by the snapshot stack.

Action: Clear the snapshot stack before attempting to remove the referenced snapshot.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25056: Cannot call removeFromCollection() or removeAndRetain() on an Entity row: Entity name {0}

Cause: An attempt has been made to call removeFromCollection() on an Entity row. It is illegal to call removeFromCollection() on an Entity row.

Action: Remove code that calls removeFromCollection() on an Entity row.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25057: Entity row update operation did not find matching row: Entity name {0}, key {1}

Cause: In LOCK_OPTUPDATE locking mode, an attempt was made to update an Entity row. The update operation failed to update any row.

Action: Another user might have modified the row and committed the changes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25058: Definition {1} of type {0} is not found in {2}.

Cause: No business component definition found with the given name in the project classpath.

Action: Provide a correct name for the business component definition and ensure the definition is available on the classpath. Names are of the format <code>myProjectPackage.BusinessPackage.BusinessComponent</code>. This error can also occur if there is a case conflict, as when the database expects 'DEPTNO' and receives 'Deptno' instead.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25059: View Object {0} has ManageRowsByKey turned on, but its key definition is empty

Cause: This View Object is not Entity based, and its ManageRowsByKey flag is true. Yet, its key definition is empty. Restated, the user has asked for the View rows to be managed by keys, but the key definition is empty (which would produce empty keys for all rows).

Action: In order to manage EO-less View Object by key, a meaningful (non-empty) key definition must be supplied.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25060: Unexpected error encountered while trying to retrieve the next row from JDBC ResultSet for collection {0}

Cause: An unexpected exception was thrown while retrieving the next row from JDBC ResultSet.

Action: Take a look at the detail exception for further information and fix underlying problems.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25061: Cannot enable passivation for internal ViewObjects and rowsets.

Cause: ViewRowSetImpl.setPassivationEnabled called for internal rowset

Action: Create a datamodel ViewObject instance and use rowsets from that ViewObject to make them passivation enabled.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25062: Cannot find a matching detail ViewObject. Link definition: {0}, master row set iterator {1}.

Cause: An attempt was made to create detail rowset. However, no matching detail view object could be found.

Action: Ensure that a matching view object is present before attempting to create a detail rowset.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25063: Operation {0} cannot be performed because the working set object is not bound.

Cause: This operation is invalid for this working set object because the working set object is not bound to actual implementation object.

Action: This action must be performed after the working set object is bound.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25064: Variable {1} in RowSet {0} is not a where-clause parameter. It is of kind {2}.

Cause: A call was made to define or set a named where-clause parameter value. However, the named variable's 'kind' is not 'where'. That is, the variable is not a where-clause parameter.

Action: Make sure that the variable name is correct and that the named variable is a where-clause parameter.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25065: Named where-clause parameter {0} does not belong to ViewObject {1}. It belongs to an object of type {2}.

Cause: An attempt was made to remove a named where-clause parameter. However, this where-clause parameter is owned by neither the RowSet nor the ViewObject. Therefore, the parameter cannot be removed.

Action: It is illegal to try to remove a named where-clause parameter that does not belong to either the RowSet or the ViewObject.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25066: View Object {0} is based on an Entity built from Row Set. For such a View Object, cannot include QUERY_MODE_SCAN_DATABASE_TABLES in its query mode.

Cause: An attempt was made to include QUERY_MODE_SCAN_DATABASE_TABLES in the View Object's query mode (through a call to setQueryMode()). However, this View Object can perform query only through Entity Object. Hence, QUERY_MODE_SCAN_DATABASE_TABLES is inappropriate.

Action: The View Object is probably based on an Entity, which in turn is based on a RowSet (EntityDefOverRowSet). It is illegal to use QUERY_MODE_SCAN_DATABASE_TABLES for a View Object built on top of an Entity which is built over a Row Set. Do not include QUERY_MODE_SCAN_DATABASE_TABLES in the setQueryMode() invocation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25067: Entity {0} has a subclass EO {1} and no discriminator. Therefore this base Entity cannot be used to create an Entity Row.

Cause: An attempt was made to create a new instance of an Entity Row. However, this Entity Definition has a subclass Entity Definition with no discriminator. That is, this Entity Definition should really be abstract.

Action: Typically in this situation, the base class should not instantiate any row. Use the subclass Entity to create the row
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25068: Entity {0} has a base EO {1} with no discriminator, but base EO has rows in its cache. Cannot populate both caches.

Cause: An attempt was made to create a new instance of an Entity Row. However, this Entity Definition is a subclass Entity Definition with no discriminator, and a base EO has a row already instantiated. A conflict exists because nothing discriminates this Entity from the base Entity.

Action: Typically in this situation, the base class should not instantiate any row. Use the subclass Entity to create the row
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25069: Row definition {0} has two sibling subclasses defs, {1} and {2}, but no discriminator to distinguish them.

Cause: Two sibling subclasses of a Row Definition are found, but the Row Definition has no discriminator. This condition is disallowed because when a row is either retrieved or created, the framework cannot determine the correct row class. That is, the hierarchy forks withouth a discriminator. The only situation whether subclassing is allowed without discriminator is when the tree is straight lined and only one of the classes in the hierarchy line is used to instantiate rows.

Action: Either define discriminator attributes, or do not create siblings in the row class hierarchy.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25070: Where-clause param variable {0} needs ordinal index array.

Cause: This view object of entity is using Oracle number style binding (:1, :2, ... binding, not named binding) or JDBC style (? binding). A variable of where-clause-param kind is found, but the extended int array that designates where the value should be bound is missing.

Action: When defining a variable for where-clause param in conjunction with a binding style which is not Oracle named binding, specify an int array that designates where the value should be bound.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25071: Applying List binding {1} with given set of values leads to multiple matching rows for a row of type:{0}, key {2}

Cause: ListBinding results in more than one matching row for the given set of mapping values. Only one matching row is expected.

Action: Provide a new set of mapping values that will end up in a single matching row or adjust the StructureDef metadata to allow defaulting to the first matching row.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25072: Applying List binding {1} with given set of values leads to no matching row for a row of type :{0}, key {2}

Cause: ListBinding failed to find any matching row for the given set of mapping values.

Action: Provide a new set of mapping values that will end up in a single matching row or adjust the StructureDef metadata to allow defaulting to the first matching row.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25073: Definition {1} of type {0} is hidden

Cause: Def object is hidden. An attempt was made to access a hidden def object.

Action: This particular operation is disallowed on a hidden def object. Avoid this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25074: Definition {1} of type {0} is hidden in {2}, operation: {3}

Cause: Def object is hidden. An attempt was made to access a hidden def object in the specified container object.

Action: This particular operation is disallowed on a hidden def object. Avoid this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25075: Definition {0} of type {1} is read-only. Cannot modify it

Cause: Attempting to modify or save data for a def object which is read-only.

Action: If the def object is shared, do not attempt to modify anything. If the def object is session scoped, do not modify it if there are running instances of that definition. If the def object is session scoped and is not being used by any running instance, mark it editable before modifying it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25076: Expression validator does not allow setting a value to source attribute:{0}.

Cause: Expression validator does not allow direct assignment of a value to an attribute. This is to avoid possible cycle of assignments/validations.

Action: Remove direct assignments. If assignment is necessary, verify there is no cycle, and then use constructs like 'source.MyVar = ..'.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25077: Name {0} not found in the given object: {1}.

Cause: An invalid name was passed in an expression.

Action: Fix the expression by passing in a correct name for a property.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25078: Key attribute {1} for {0} not populated

Cause: While building the where-clause statement for an entity row operation (e.g., fault-in, delete, or update), the named key attribute value is not populated.

Action: This entity row operation requires the key attributes to be populated. Make sure that all key attributes have values in them.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25079: The list of discriminator attributes for subclass {0} is different from that of the base {1}

Cause: In a subclass hierarchy of RowDefs, found a subclass RowDef whose discr attr list has more attrs than the base class. It is disallowed for a subclass to change discr attr list in the subclass hierarchy.

Action: Make sure that subclass RowDefs have the same set of discr attributes as the base class.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25080: Definition name: {0} does not match the file in which it is loaded from: {1}

Cause: An attempt has been made to load a definition metadata file named differently from the name or id of the top level xml element in the file.

Action: The name should be a valid Java identifier with no spaces or punctuation. The name or id of the top level xml element in the file should match the file name.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25081: The new fetch size {0} passed into setFetchSize() for a view object {2} is invalid. It is smaller than the old value {1}.

Cause: The fetch size passed into <code>ViewObjectImpl.setFetchSize()</code> is smaller than the previous value. Fetch size of a view object cannot decrease.

Action: Specify a value which is bigger than the current value.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25082: Cannot change the access mode for the row set {0} because either the VO has more than one RS or the RS has more than one iterator.

Cause: An attempt has been made to change the row set's access mode from scrollable/forward-only to range-paging or vice versa. This is allowed only if the VO has one or no row set. Or, an attempt has been made to set the row set's access mode to forward-only, but this is allowed only if the row set has one or no iterator.

Action: Close other row sets or iterators before changing the access mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25083: Cannot create a secondary iterator on row set {0} because the access mode is forward-only or range-paging

Cause: An attempt has been made to create a new row set iterator on a row set whose access mode is either forward-only or range-paging.

Action: Creation of secondary row set iterator is allowed if the row set's access mode is scrollable.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25084: Cannot call last() on row set {0} because the access mode uses range-paging

Cause: An attempt has been made to jump to the last row on a row set whose access mode uses range-paging.

Action: Replace 'last' with 'setRangeStart' for the range-paging based access mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25085: The value being set for attribute {0} does not match the value derived from list binding {1}

Cause: An attribute value being set does not match the attribute value derived from a list binding. This typically happens in the following situations. First, suppose the user sets values for Deptno from 10 to 20 and Dname from ABC to DEF. If a list binding is triggered by Deptno and if it sets Dname to XYZ, the result is an inconsistent state where DEF does not match XYZ. In this situation, this exception is thrown. Second, suppose there is an EmpDept view object with Emp and Dept entity bases. Suppose Dept is reference and read-only and there is a list binding on Dept.Dname whose derived attribute is Emp.Deptno. If the user selects a new Dept through the dept name, a new Dept entity row is brought in (because a new Emp.Deptno is chosen). After this, the framework checks to make sure that the Dname coming from the new entity row matches the original selection from the list bindng. If they do not match, this exception is thrown.

Action: Make sure the list binding definition and attribute set values end up in a consistent result (i.e., the derived values from the list binding match the row's attribute values).
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25086: Operation {1} cannot be performed until definition {0} is resolved.

Cause: An attempt was made to use a def object before resolving it. The def object must be resolved first.

Action: Make sure resolveDefObject() is called before this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25087: Cannot call getRowCount() on row set {0} because the access mode uses range-paging

Cause: An attempt has been made to get the row count of a row set whose access mode uses range-paging.

Action: Replace getRowCount() with getEstimatedRowCount() for range-paging based access mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25088: Persdef {0} has no static definition set

Cause: An attempt was made to perform an operation on a persdef that requires the static definition object, but the persdef has no static definition.

Action: Set the static definition object before attempting the operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25089: Too many matching records found. Specify additional criteria to limit the number of records.

Cause: The view object attempted to fetch rows beyond a global row limit.

Action: If in a search region narrow down the results by providing more search criteria otherwise contact your system administrator.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25090: Attribute value {3} leads to duplicate keys for this entity type {1}.

Cause: An attempt was made to set an attribute value that leads to addition of a newly fetched or created entity to the cache, but tut this value makes the entity key same as another existing entity. The primary key must be unique for this entity type.

Action: Add more attributes to the key definition for the entity type, so that each row for this entity is uniquely identifiable. Or fix the key value so that this entity has a unique key identifier.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25091: View object {0} has no primary entity

Cause: An attempt was made to get the primary post state of a view row that has no entity usages.

Action: Only call this method on a view row with one or more entity usages
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25092: Programmatically accessible view object definition {0} is not found.

Cause: An attempt has been made to find a view definition using a short name and no corresponding custom or standard object can be found.

Action: Use a shortname that corresponds to the name of a custom object in a registered custom object base package or elsethe name of a standard object that has been registered to be programmatically accessible.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25093: Attribute {0} is being modified, while it is being validated causing an infinite loop.

Cause: An attempt was made within an expression or validation rule to update an attribute while that attribute is being validated.

Action: Remove the call to set the erring attribute value
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25094: Row finder {0} found more than expected rows on rowset {1}.

Cause: The number of rows found by a row finder exceeded the expected maximum.

Action: Ensure no more than the specified number of rows exists.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25095: Invalid bind name value pairs passed into row finder {0} on rowset {1}.

Cause: An attempt was made to invoke RowFinder execute method with an invalid AttributeList.

Action: Pass the correct value for AttributeList.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25096: Accessor {0} was not correctly resolved in view def {1}. Locate the resolution error and address the issue.

Cause: An attempt was made to access a view link or view accessors which was not correctly resolved.

Action: At the time of view link or view accessor resolution, something failed. Most likely, that failure was reported, but the application decided to continue to work with the view def with the problem. Locate the error reported during the initial accessor resolution attempt and address the issue.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25097: Attempt to modify sealed comp oper {0}. This is not allowed.

Cause: An attempt was made to modify a comp oper object which has been sealed.

Action: It is illegal to attempt to modify sealed comp oper. Check the code that is attempting edit and avoid this.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25098: Programmatically accessible view criteria {0} is not found.

Cause: An attempt has been made to use a view criteria that does not exist or which has not been marked to allow untrusted script access.

Action: Use the name of a view criteria that exists and has been marked to allow untrusted script access.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25099: Programmatically accessible view variable {0} is not found.

Cause: An attempt has been made to use a view variable that does not exist or which has not been marked to allow untrusted script access.

Action: Use the name of a view variable that exists and has been marked to allow untrusted script access.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25100: The configured Row Finder parent is not supported.

Cause: The RowFinder could not process this operation because it doesn't have a valid parent.

Action: The RowFinder instance must be constructed using a valid parent.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25101: View object {0} includes a non-row storage attribute {1} in its key. This is not allowed

Cause: The view object's key definition includes a non-row storage attribute. A view object's key may only include row storage attributes.

Action: Contact the view object owner to redefine its key.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25102: Requested change of ADF session options is rejected because of the root AM {0} of type {1} has pending changes in transaction.

Cause: An attempt was made to modify ADF session options, but this change cannot be allowed because the transaction is dirty.

Action: End (commit/rollback) the transaction before requesting change of ADF session options. Or, change may be requested with the 'force' switch, but that will automatically roll back the pending transaction.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25103: ADF session options should be changed with caution because the root AM {0} of type {1} has an object based on site/session definition: {2} of type {3}.

Cause: Change of ADF session options must be performed with care because the root AM has a component object, whose definition is either a session def or a site def.

Action: The user should be notified that the root AM will be cleaned out (components removed) when the ADF session options are changed.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25104: The XML document for def {1} of type {0} is found, but it is marked as EmptyDoc.

Cause: The XML document for the named def is found, but it is marked as EmptyDoc

Action: The XML document is found, but its EmptyDoc attribute is true. This typically means that the 'empty' base XML doc is present, but the customization doc for the current set of customization classes is not found. I.e., the empty base doc was created by another customization class. So, the current customization class proceed as if the def does not exist.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25105: Attribute {0} in {1} is marked for collection storage, but its Java type {2} does not implement java.io.Serializable

Cause: The attribute is marked as collection storage, but its Java type is not serializable. As collection storage attribute values are stored in the session, they must be serializble.

Action: Make sure that the attribute Java type implements java.io.Serializable. If not, the attribute may not be stored with 'collection storage'.
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-25172: Expression exceeded the maximum number of {0} active scripts using new view instances.

Cause: An untrusted expression exceeded an allowed use of resources.

Action: Change your expression to use fewer resources.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25180: Exception in expression "{0}": {2}

Cause: An exception has occurred within a Transient Expression.

Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25181: Exception in expression "{0}" recalc expression {1} : {2}

Cause: An exception has occurred within a Recalc Expression.

Action: Examine the details to find the root cause, and modify the Expression to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25182: Exception in expression "{0}" validation rule {1} : {2}

Cause: An exception has occurred within a Validation Rule expression.

Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25183: Exception in expression "{0}" trigger {1} : {2}

Cause: An exception has occurred within a Trigger expression.

Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25184: Exception in expression "{0}" object function {1} : {2}

Cause: An exception has occurred within an Object Fucntion.

Action: Examine the details to find the root cause, and modify the function to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25185: Exception in expression "{0}" global function {1} : {2}

Cause: An exception has occurred within an Object Fucntion.

Action: Examine the details to find the root cause, and modify the function to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25186: Exception in expression "{0}" of unknown type {1} : {2}

Cause: An exception has occurred within an expression of unknown type.

Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25187: Duplicate signature for method "{0}" when attempting to add to {1}

Cause: An attempt to add two methods of identical signature to an Object or Global Function.

Action: Change the method signatures to be different, and re-add the function.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25188: Exception in expression "{0}" property expression {1} : {2}

Cause: An exception has occurred within a Property 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-25189: Exception in expression "{0}" message parameter values expression {1} : {2}

Cause: An exception has occurred within a MessageParameterValues 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-25190: Exception in expression "{0}" default value {1} : {2}

Cause: An exception has occurred within a Transient Default Value 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-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-25304: Cannot mark entity batchable when base entity:{0} is not.

Cause: An entity whose base type is not batchable cannot set BatchThreshold to a number greater than zero.

Action: Do not set BatchThreshold for the entity to a number greater than zero.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25306: Design-time attribute {0} of type {1} could not be persisted

Cause: Could not persist a design-time attribute into the XML file.

Action: Identify the offending design-time attribute and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25307: XML file not open

Cause: XML file is not open.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25308: The primary key of an existing entity bean cannot be modified for entity facade {0}.

Cause: An attempt was made to modify the primary key of an existing entity bean. This is disallowed by EJB.

Action: Do not modify primary key of an old (not-new) entity bean.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25309: The primary key of an entity bean cannot be null for entity facade {0}.

Cause: The primary key of an entity bean is null. This is disallowed by EJB.

Action: Set the primary key to be not null.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26000: A Generic exception occurred during loading Customizations.

Cause: Metadata objects failed to load due to unexpected or corrupt data in the XML file.

Action: Verify that the XML metadata for various components is valid.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26001: XML File not found for the Container {0}

Cause: Could not open the named XML file for reading.

Action: Try the following: Make sure that the file is present. In particular, if the file is to be found in a Zip/JAR file, make sure that the Zip/JAR file is included in the CLASSPATH. This error is also reported if the name of the XML file does not match the object Name specified in the XML file. If the file system supports case insensitive file names (e.g., Windows NT), make sure that the file name matches the object Name in the XML file in case-sensitive fashion. For a JPX file, this error is reported if the JPX file is missing the JboProject XML tag. Check the JPX file to make sure that the valid tag is in there. One XML file might be extending another XML file (specified by the Extends element in this XML file). This error is reported if the base XML file is not found. When loading the XML file for a package (JboPackage tag), this error is reported if some unexpected error occurs while loading a contained object. In all of the above cases, a more descriptive message might be printed on Diagnostic. To see these messages, run the application with Diagnostic turned on, as in 'java -Djbo.debugoutput=console ...', to see Diagnostic messages.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26002: Error Parsing the XML file "{0}".

Cause: Some XML parsing exception (<code>oracle.xml.parser.v2.XMLParseException</code>) was thrown.

Action: The XMLParseException information is output to Diagnostic. To see diagnostic messages, run the application with diagnostic turned on, for example 'java -Djbo.debugoutput=console ...'
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26003: Mismatch in the attribute indices declared in Java versus the indices in the definition for entity {0}.

Cause: An error occurred while loading entity object definitions. An attribute index in the Java class for this entity has a mismatch with the index in the definition, or an attribute index is missing in the Java class.

Action: Ensure that the indices of attributes in the definition for this entity match the indices defined in the Java class for this entity.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26004: A recursive base definition is found while attempting to set the base definition of {0} to {1}.

Cause: An attempt was made to set the base definition of another definition object, e.g., setting B's base definition to A (i.e., B Extends A). However, A already extends B. Setting a recursive (circular) subclassing relationship among definition objects is illegal.

Action: Review the subclassing hierarchy of the definition objects and correct errors.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26005: FetchMode must be either FETCH_AS_NEEDED, FETCH_ALL or FETCH_DEFAULT. View object {0}

Cause: The fetch mode specified in the view definition XML file is not valid.

Action: Check the content of the XML file for the view definition. Look for an XML element named 'FetchMode'. Make sure that the value for that element is valid. Valid values are: 'FETCH_AS_NEEDED', 'FETCH_ALL', and 'FETCH_DEFAULT'
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26006: FetchSize must be a positive integer. View object {0}

Cause: The fetch size specified in the view definition XML file is not valid.

Action: Check the content of the XML file for the view definition. Look for an XML element named 'FetchSize'. Make sure that the value for the element is a positive integer.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26007: MaxFetchSize should be MAX_FETCH_UNLIMITED, MAX_FETCH_DEFAULT or integer. View object {0}

Cause: The maximum fetch size specified in the view definition XML file is not valid.

Action: Check the content of the XML file for the view definition. Look for an XML element named 'MaxFetchSize'. Make sure that the value for the element is a non-negative integer, or 'MAX_FETCH_UNLIMITED', or 'MAX_FETCH_DEFAULT'. A MaxFetchSize of 0 is the same as MAX_FETCH_UNLIMITED.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26008: Could not resolve reference to "{0}".

Cause: A problem is found in resolving a view link definition or an association. In case of a view link, this error might be caused by the fact that the source or destination view object cannot found. Or, if the view link ends have attribute names, this error might indicate that the named attributes cannot be found. Similarly, for an association, this error indicates that either source or destination entity object or attributes involved in the association cannot be found.

Action: Make sure the XML definition for the view link/association has correct view object/entity object/attribute names.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26009: Serialized file "{0}" is invalid. The root object is not a Business Component object.

Cause: This error occurs if the application uses meta object serialization files (.ser files) instead of XML files. It indicates that after the .ser file was deserialized, the top level object returned from deserialization was not an instance of oracle.jbo.server.xml.JboElementImpl.

Action: Repair the corrupt .ser file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26010: Invalid Entity Attribute Name "{1}" specified for the View Attribute "{0}"

Cause: Entity attribute name in the view definition XML file is invalid or is not found.

Action: Make sure that the entity name is valid. Also, check to make sure that the named attribute does exist in the entity object. The entity object is identified by the EntityUsage element.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26011: SQLType not specified for the View Attribute "{0}"

Cause: Attribute definition found in XML file is invalid. It is missing SQLType value.

Action: Correct the error in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26012: Invalid View Link Definition "{0}". View Link must have two ViewLinkDefEnds.

Cause: The view link definition in the XML file is missing either the source or destination view link end. For a view link XML file, two elements named ViewLinkDefEnd should be found.

Action: Correct the error in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26013: Naming Exception occurred while looking up the object "{0}".

Cause: Meta object name passed for lookup is invalid.

Action: Normally, the meta object name is a dot-separated name of the meta object. For an entity object named Emp in package1.example, the correct name would be <code>package1.example.Emp</code>. To correct, locate where the invalid name is coming from (could be meta object names mentioned in an XML file, or the name of the project, etc.) and change the name to a valid one.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26015: View object {0} does not include a discriminator column {2} of entity base {1}.

Cause: A view definition does not include a discriminator column of an entity base. If an entity base has discriminator columns, it must include all of them in the view object's attribute mapping.

Action: Change the view definition to include discriminator column attributes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26016: Cannot set user query to view "{0}" because it is a destination in a view link

Cause: An attempt was made to call 'setQuery()' on a detail view object in a master detail view link.

Action: Do not call setQuery() if the view object is a detail.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26017: Association or view link definition {0} has an invalid attribute list.

Cause: The association or view link definition has a missing or invalid attribute list.

Action: Correct the error(s) in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26018: Entity {0} cannot be posted to the database because it has no attributes set.

Cause: An attempt was made to post a row with no attribute set. Some databases (Oracle Database in particular) do not allow an INSERT statement with no VALUE specified.

Action: Set some attributes on the row before attempting to insert it into the database.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26019: Attempting to remove a parent entity without removing all children entities

Cause: Attempting to remove a master which has detail entities. In the case of a composition, a master cannot be removed if it has details.

Action: Remove all the details of this master by accessing the details via an association and removing all of them.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26020: Attempting to insert row with no matching EO base

Cause: The application code tried to take a row from one row set (or view object) and insert it into another row set (view object). In response, the framework will make a copy of the row in the new row set. This new row will share references to the underlying entity objects. However, if the source and destination row sets do not share any entity object bases at all, this operation will fail as it does not find any entity rows to share.

Action: When attempting to take a row from one row set and insert into another, make sure that they share at least one entity object base.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26021: NullPointerException while parsing XML file "{0}". Perhaps missing DTD file?

Cause: A NullPointerException was thrown while parsing an XML file. A possible cause for this is that the DTD file is missing (oracle.jbo.dtd.jbo.dtd).

Action: Make sure the appropriate DTD file is present.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26022: Custom class {0} cannot be found.

Cause: A custom class could not be found and loaded. The custom class might be for a component (for example, view object), a definition (for example, view definition), or a row (for example, view row or entity row).

Action: Make sure that the named class is reachable from the CLASSPATH. The detail exception (if present) provides more specific reasons why the attempt to locate and load the custom class failed.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26023: Custom class {0} is not assignable to {1}

Cause: Custom class was found and loaded, but it is invalid in that it is not assignable to a framework (super) class.

Action: Make sure that the custom class subclasses the appropriate framework (super) class.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26024: An error occurred while creating InitialContext

Cause: An error occurred while creating initial context. This error usually carries a detail exception which will give further information on the cause of the error.

Action: When running inside JServer, make sure that the database user (schema) has the setContextClassLoader permission. To grant this, the database system administrator can invoke the following PL/SQL procedure: EXEC DBMS_JAVA.GRANT_PERMISSION('&&1', 'SYS:java.lang.RuntimePermission', 'setContextClassLoader', null);
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26025: An error occurred while trying to get System properties

Cause: An error occurred while trying to get System properties. Specifically, System.getProperties() call failed.

Action: When running inside JServer, make sure that the database user (schema) has the proper property permission. To grant this, database system can invoke the following PL/SQL procedure: EXEC DBMS_JAVA.GRANT_PERMISSION('&&1', 'SYS:java.util.PropertyPermission', '', 'read');
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26026: An error occurred while loading properties from a properties file {0}

Cause: An error occurred while trying to get load properties.

Action: Check to see if the named properties file contains valid Java properties.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26027: Unable to find resource. {0}

Cause: Unable to find a resource

Action: Check to see if the resource exists and the framework code has adequate permissions to load the resource.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26028: View object {0} does not include a primary key attribute {2} of entity base {1}.

Cause: A view definition does not include a primary key attribute of an entity base. When a view object uses an entity as one of its entity bases, it must include all primary key attributes of the underlying entity object.

Action: Change the view definition to include all primary key attributes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26029: Could not find and load the type map class {0}

Cause: Custom type map class could not be found and loaded.

Action: Make sure that the named class is reachable from the CLASSPATH. If jbo.TypeMapEntries property is specified, make sure that the property value is correct. Also, though unlikely, this might be caused by an improper implementation of SQLBuilder where it is returning an incorrect value for type map class name. The detail exception (if present) will provide more specific reasons why the attempt to locate and load the custom class failed.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26030: Failed to lock the record, another user holds the lock.

Cause: This row has already been locked by another user or transaction.

Action: Try locking the row again and the operation should succeed after the other user or transaction has released the lock.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26031: Association end {0} of assoc {1} invalid for entity base {2} in view object {3}.

Cause: Problem in secondary entity base definition in view definition. The named entity base is supposed to use the named entity association end to join it with another entity base, but, when resolved with the association definition, the association end does not resolve to the same entity. For example, suppose one builds a view object with Dept and Emp. Emp is supposed to join with Dept using the EmpEnd of the DeptEmp association. For such a view definition, the framework verifies that EmpEnd indeed is from Emp entity. If EmpEnd was from another entity, say Person (or Dept), it would not be correct to use that association end to perform join.

Action: Most commonly, this is caused by incorrect information in the view object XML file. Make sure that the association end for the named entity usage is not pointing at the wrong end of association.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26032: Operation {0} is invalid for a ViewCriteria or ViewCriteriaRow.

Cause: The attempted operation is invalid for a ViewCriteria or ViewCriteriaRow.

Action: Remove code that attempts this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26033: Cannot find Application Data Model with name :{0}

Cause: Cannot find application definition of the given name

Action: Fix the application definition name or make the appropriate .cpx file available in the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26034: Cannot find Configuration with name :{0}

Cause: Cannot find configuration information in the application definition file

Action: Fix the Configuration name or make the appropriate .cpx file available in the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26035: Secondary entity usage {0} is missing parts of association description.

Cause: A view definition is found with an entity usage definition where the secondary entity usage's association description is incomplete.

Action: Examine the view object's XML file. A secondary entity usage's association description should have the following elements: 'Association', 'AssociationEnd', and 'SourceUsage'. Check to see if any of these are missing.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26036: The configuration of meta object {0} causes recursive substitution.

Cause: An attempt was made to set up meta object substitution that leads to recursion. For example, consider a substitution where C substitutes B, and B substitutes A, and A substitutes C. This results in a recursive substitution and will cause this error.

Action: Review the meta object substitution and correct errors.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26037: Cannot find matching EO from discriminator columns for view object {0}, entity base {1}, discr value {2}.

Cause: While creating a new view row, the system found an entity object base with discriminator column attributes. However, the discriminator column values coming from the view row do not match any of the entity objects (the entity for the entity object base or any of its extended entities).

Action: Make sure that the view row discriminator column values match one and only one entity object.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26038: Cannot find an entity usage for entity {1} in view link definition {0}, view link end {2}.

Cause: The view link definition is based on an entity association. One of its ends specifies the named entity definition, but the view definition for that view link end does not have an entity usage for that entity definition.

Action: Correct the error in the view link definition (XML file). In particular, check to see if the view link source and destination are not switched with those of the entity association.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26039: View object {0} does not include an alternate key attribute {2} of entity base {1}, entity key {3}.

Cause: A view definition does not include an alternate key attribute of an entity base. When a view object uses an entity as one of its entity bases, and when it defines a view object level alternate key using one of the entity alternate keys, it must map the entity attributes that make up the alternate key.

Action: Change the view definition to include all necessary alternate key attributes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26040: Failed to post entity {1} to database during "{0}" : SQL Statement "{2}".

Cause: Some database error occurred while posting (writing) an entity to the database in JDBC batch mode. This error normally carries a detail exception from the database which will give further information about the database failure.

Action: Look at the details of the exception and address the database problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26041: Failed to post data to database during "{0}": SQL Statement "{1}".

Cause: Some database error occurred while posting (writing) an entity to the database. This error normally carries a detail exception from the database which will give further information about the database failure.

Action: Look at the details of the exception and address the database problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26042: Failed to generate REF and OID on entity {0}.

Cause: A database failure occurred while trying to generate an object ID (OID) and object reference (REF). When a new row is created on an entity which maps to an Oracle object table, an OID and REF for the new row are generated. This executes a SQL statement like select a.oid, make_ref(table-name, a.oid) ... Somehow, this statement is failing.

Action: Ensure that : The Oracle database version is correct. The table in question is an object table. This error normally carries a detail exception from the database, which will give further information about the database failure. Take a look at the detail exception and address the database problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26043: REF and OID not supported by this SQLBuilder on entity {0}.

Cause: An attempt was made to generate an object ID (OID) and/or a reference (REF) on a database system that does not support Oracle objects.

Action: Do not try to create OID or REF on a database system that does not support Oracle objects.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26044: Error while getting estimated row count for view object {0}, statement {1}.

Cause: The application tried to get an estimated row count (getEstimatedRowCount()) on a row set. While building the appropriate query statement, executing it, and retrieving the estimated count, an error occurred. This error is accompanied by the SQL statement that caused the error. Also, it normally carries a detail exception from database, which will give further information about the database failure.

Action: Take a look at the SQL statement and the detail exception and address the database problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26045: Failed to generate PK-Based REF on entity {0}.

Cause: A database error occurred while trying to generate an object ID (OID) from the primary key. This operation is valid only if the table in question is an object table and if the table specifies that the reference (REF) is PK based.

Action: Ensure that: The Oracle database version is correct. The table in question is an object table. The object table uses a PK-based REF. This error normally carries a detail exception from database which will give further information about the database failure. Take a look at the detail exception and address the database problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26046: PK-Based REF not supported by this SQLBuilder on entity {0}.

Cause: An attempt was made to generate Oracle o8 object ref from a non-Oracle database SQLBuilder. This is not supported.

Action: Make sure that the correct SQLFlavor (i.e., SQLBuilder) is being used for the application and switch to the right one.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26047: LOCK_OPTUPDATE mode update operation missing change indicator value: Entity {0}, key {1}.

Cause: An attempt was made to update a row in LOCK_OPTUPDATE mode and the change indicator attribute value is not present.

Action: Look at the attribute mapping of the View Object that read in this Entity row and make sure that the View Object includes the change indicator attribute. The LOCK_OPTUPDATE mode requires the value to be present.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26048: Constraint "{2}" is violated during post operation "{0}" using SQL statement "{1}".

Cause: A constraint violation occurred in the database while posting (writing) an entity to the database. This error carries a detail exception from the database which will give further information about the database failure.

Action: Fix the cause for the constraint violation. Look at the details of the exception and address the database problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26049: An error occurred during loading definition {0}.

Cause: Metadata objects failed to load due to unexpected or corrupt data in the XML file.

Action: Verify that the XML metadata for various components is valid.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26050: An error occurred while writing personalization definition {0}.

Cause: An I/O error occurred while writing personalization definition.

Action: Check the detail I/O exception and make necessary correction.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26051: Unrecognized XML element tag {1} found in meta object {0}.

Cause: The element tag of the XML file is not recognized.

Action: Examine the XML file and make sure that the element tag is one of the recognized ones.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26053: Invalid association or view link definition "{0}". Invalid unbound attribute list.

Cause: An association or view link definition end has an invalid unbound attribute list. This error is raised if the unbound attribute is not one of the association/view link end attributes.

Action: Correct the error(s) in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26054: Invalid version number for {0}. Require {1} or greater, but found {2}.

Cause: The XML document is either missing the version number or has a version number which is lower than the required version number.

Action: Check to see if the XML document has gone through a proper migration process. If not, migrate the application.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26055: Failed to delete XML document {0}.

Cause: An attempt was made to delete an XML document from disk, but this operation failed.

Action: When running with MDS, make sure that the metadata store supports the delete operation. Check the detail exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26056: Multiple occurrences of XML element {1} found in {0}. Only one expected.

Cause: Multiple occurrences of an element were found in the XML document when only one was expected.

Action: Examine the XML document and see which element shows up mutiple times. If the issue looks like a problem in the framework's persistence code, report it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26057: Recursive entity references found in view def {0}. Entity refs: {1}

Cause: An attempt was made to create a view definition whose entity references have a cycle in it. For example, a view definition contains two entity references E and F, where E's source reference is F, and F's is E.

Action: Review your code that builds the view def. Make sure that entity references do not have a recursion in it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26058: Cannot define view link {0} in application module {1}. The view object {2} is in application module {3} and the view link''s application module is not a child of the view object''s application module.

Cause: An attempt was made to establish a data model view link in an application module, but either the master or the detail view object is in an AM which is not the same AM as the view link's, or is not a parent of the view link's AM.

Action: When creating a data model VL, the VL's AM must be the same as the VO's, or must be a child (nested) AM of the VO (for both master and detail).
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26059: Invalid View Link Usage "{0}". Either the source "{1}" or the destination "{2}" is not defined.

Cause: The ViewLink Usage is not correctly defined.

Action: Specify both source and destination for the ViewLink Usage.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26060: Error while registering JDBC driver.

Cause: A SQLException occurred while trying to register a JDBC driver.

Action: Fix the underlying SQLException.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26061: Error while opening JDBC connection.

Cause: A SQLException occurred while trying to open a JDBC connection.

Action: Fix the underlying SQLException.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26062: Error while closing JDBC connection.

Cause: A SQLException occurred while trying to close a JDBC connection.

Action: Fix the underlying SQLException.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26063: MetaObjectManager loadFromXML called with unknown object type {0}.

Cause: Metadata object manager cannot load XML for this document type.

Action: Check to see if MetaObjectManager::loadFromXML is being called for an unsupported object type.
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 created the doc with same name. Cannot create it as new.

Cause: The client requested to create a new document. However, one of the following two problems are found; either before creating the doc, MDS finds that the doc is there, or while flushing the new doc, MDS throws a document-exists-exception. In either case, the problem is that the document was created by another user and the current user cannot create the document any more.

Action: Load the new document created by the other user and update it, instead of trying to create it as new.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26076: Merge for definition {0} failed for elem {1}. Inserted elem [{2} -> {3}] was deleted by another user.

Cause: During object merge, found a metadata element which was marked for insertion by the current user, but was deleted by another transaction committed or published by another user.

Action: Resolve this metadata merge conflict.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26077: Merge for definition {0} failed for elem {1}. Updated elem [{2} -> {3}] was deleted by another user.

Cause: During object merge, found a metadata element which was marked for update by the current user, but was deleted by another transaction committed or published by another user.

Action: Resolve this metadata merge conflict.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26078: Merge for definition {0} failed for elem {1}. Inserted elem [{2} -> {3}] was inserted by another user.

Cause: During object merge, found a metadata element which was marked for insertion by the current user, but was inserted by another transaction committed or published by another user.

Action: Resolve this metadata merge conflict.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26079: Merge for definition {0} failed for elem {1}. Updated elem [{2} -> {3}] was updated by another user.

Cause: During object merge, found a metadata element which was marked for update by the current user, but was updated by another transaction committed or published by another user.

Action: Resolve this metadata merge conflict.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26080: Error while selecting entity for {0}

Cause: An unexpected exception occurred while executing the SQL to fetch data for an entity instance or lock it.

Action: Fix the cause for the SQLException in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26081: Error while getting datum for attribute {1} in {0}

Cause: A SQLException occurred when converting data from JDBC to <code>oracle.jbo.domain.Struct</code> attributes.

Action: Fix the conversion errors as suggested in SQLException.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26083: Comparison operator {0} has a string code for its description, but the message bundle class cannot be found.

Cause: A comparison operator was specified with string code, but the message bundle class could not be loaded. When specifying a string code for translatable operator description, the framework first checks to see if the operator specification includes a message bundle class name. If so, it attempts to find the string in that message bundle. If not, then the framework tries to find the string in the owning object's (either view object or entity object) message bundle. If both fail, this error is raised.

Action: Make sure that the comparison operator specification is correct in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26084: Invalid association definition "{0}". Association must have two AssociationEnds.

Cause: The association definition in the XML file is missing either the source or destination association end. For an association XML file, two elements named AssociationEnd should be found.

Action: Correct the error in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26085: Missing association name in EO-exists validator {0} of {1}.

Cause: The EO-exists validator is missing the association name in its definition.

Action: Correct the error in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26086: Association attributes do not match the destination EO''s primary keys in EO-exists validator {0} of {1}.

Cause: The EO-exists validator's source side attribute list does not match the desination EO's primary keys. For example, suppose there is a PurchaseOrder EO which includes an EO-exists validator to Customer EO. PurchaseOrder EO is using association CustToPurch to validate. In this case, the association attribute list on the PurchaseOrder side match with Customer's PK exactly (order does not matter--they must equal as sets).

Action: Correct the error in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26087: The master end accessor {0} of composition assoc {1} has an invalid attribute kind: {2}.

Cause: The composition association's master end has attribute kind of RowSetIterator (cardinality -1 or > 1), i.e., it returns an iterator, rather than a row.

Action: Master end in an association must return a single row. Thus, the attribute kind must be Row (cardinality = 1).
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26088: An attempt was made to edit property {1} of def object {0}, but this property may not be edited.

Cause: An attempt was made to edit a def object, but this property or object may not be edited.

Action: Do not try to edit this property. Instead, consider deleting and creating the def object.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26089: An attempt was made to edit def object {0} but another user edited and saved the def object. Orig version: {1}, tip version: {2}.

Cause: The client made a request to edit a def object. However, either the major version number or the minor version number do match between the original def object and the def object found on the tip of the MDS repository. This means another user has modified and saved the def object between the time when this client loaded the original def object.

Action: Reload the def object to refresh to the tip and request edit.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26091: An attempt was made to refresh def object {0} to tip, but another user made structural changes and saved. Orig major version: {1}, tip major version: {2}.

Cause: The def object from the tip of the repos shows that the object's major edit version number was incremented. This means that another user made structural changes to the def object and it may not be refreshed with the latest def object.

Action: The def object cache should be refreshed to the tip of the repos.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26092: Failed to lock the record in table {0} with key {1}, 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-26093: Definition {0} has unresolved merge conflicts.

Cause: Not all merge conflicts have been resolved. This exception is used to signal to MDS that some merge conflicts were not resolved, and another round of merge conflict resolution is necessary.

Action: Merge conflict resolution must be performed again.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26099: An instance of type {0} cannot be created from string {1}. The string value must be in format {2}.

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 type conversion 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-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 a sessiondef package. Sessiondef packages are {0}

Cause: The specified session definition full name is invalid.

Action: Session definition full name must start with one of the sessiondef packages.
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-27038: Argument {1} to {0} may not be null

Cause: The method parameter may not be null.

Action: Please provide a non-null value.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27039: Site definition full name must start with a sitedef package. Sitedef packages are {0}

Cause: The specified site definition full name is invalid.

Action: Site definition full name must start with one of the sitedef packages.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27040: Value {3} for field {2} exceeds the maximum length allowed.

Cause: For strings, the length of the string value provided for an attribute is more than the max-length this attribute expects.

Action: Reduce the length of the attribute value for the failing attribute.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27041: Value {3} for field {2} exceeds the number of decimal places allowed.

Cause: 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 decimal values information for the failing attribute.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27101: Attempt to access dead entity in {0}, key={1}

Cause: Trying to refer to an invalid/obsolete entity. This could occur if some business logic has held on to an entity reference which was removed and the transaction has been posted or committed. It could also occur if a reference entity has been removed from the cache and any ViewRow is attempting to access it.

Action: Use findByPrimaryKey to find a valid entity of the desired key instead of holding on to a reference to an entity instance.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27102: Attempt to access dead view row of persistent id {0}

Cause: Trying to access a ViewRow which is part of an obsolete/invalid collection. This could happen if a reference to the ViewRow is held by some business logic while the containing view object was removed.

Action: Find the referenced ViewRow either by re-querying or using findByKey methods to get a valid reference to the ViewRow.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27120: SQL error during query execution. Statement: {0}

Cause: Failed to execute a query. This could occur when trying to execute a query for a SQLValue domain class or a Sequence domain.

Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27121: SQL error during statement execution. Statement: {0}

Cause: Failed to execute a SQL statement.

Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27122: SQL error during statement preparation. Statement: {0}

Cause: Failed to prepare a JDBC PreparedStatement.

Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27123: SQL error during call statement preparation. Statement: {0}

Cause: Failed to prepare a JDBC CallableStatement.

Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27124: SQL error during empty statement creation

Cause: Failed to create a JDBC Statement object with the given set of parameters.

Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27125: Cannot find matching type-map entries for all columns in a dynamic ViewObject-query

Cause: Failed to find a Java type for a column-type in the given dynamic ViewObject query.

Action: Either provide a typemap that maps the selected columns in the query or leave out the erring column-type from the query.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27126: Long running query "{0}" has been canceled.

Cause: The view object's query timeout was reached or the user requested cancellation of a long query.

Action: Review the query implementation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27127: The effective date operation for Entity {0} will introduce gaps or overlaps. key={1}

Cause: Effective date constraint violation while creating or updating a row. The operation will cause gaps or overlaps in the effective date timeline

Action: Change the start or end effective date if it is a new row. If it is an update choose a different mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27128: The effective date update operation for Entity {0} failed because an existing row has the effective start date that matches the effective date. key={1}

Cause: Effective date row update with UPDATE mode is disallowed because the start effective date of an existing row matches the effective date.

Action: Choose a different mode to update the row like correction mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27129: The effective date row for Entity {0} has end date less than start date, key={1}

Cause: Effective end date is greater than the start date.

Action: Change the start or end effective date.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27130: Current mode {0} is not supported in Multiple Changes Per Day.

Cause: Current mode is not supported in Multiple Changes Per Day.

Action: Switch to Update Change Insert mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27131: Current mode {0} is supported only in Multiple Changes Per Day.

Cause: Current mode is not supported in Multiple Changes Per Day.

Action: Switch to Update Change Insert mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27132: Current operation cannot be performed in {0} mode because no future rows exist. key={1}

Cause: Current operation cannot be performed when no future rows exist.

Action: Switch to Update mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27133: Current operation cannot be performed in {0} mode because no previous rows exist. key={1}

Cause: Current operation cannot be performed when no previous rows exist.

Action: Switch to a different mode or navigate to a row where previous rows exist.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27134: Current Multiple Changes Per Day operation can be performed only on first sequenced row. key={0}

Cause: Current Multiple Changes Per Day operation can be performed only on first sequenced row.

Action: Navigate to first sequenced row.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27200: JNDI failure. Unable to lookup {0} at context {1}

Cause: JNDI lookup failed. It can be caused by an incorrect data source name, particularly for the internal connection, or an internal error.

Action: Check the internal data source name to see if it is valid. If the error is not caused by the internal connection problem, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27201: Error suspending current transaction

Cause: An error occurred while suspending a global transaction for JTA pcoll manager.

Action: Check the detail exception to determine the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27202: Error resuming current transaction

Cause: An error occurred while resuming a global transaction for JTA pcoll manager.

Action: Check the detail exception to determine the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27203: Cannot use the default connection for persistence with global transactions.

Cause: While using global transactions, an attempt was made to use the transactional data source for acquiring the internal connection.

Action: Explicitly specify the jdbc url that should be used for creating the internal connection by setting the oracle.jbo.common.PropertyConstants.INTERNAL_CONNECTION_PARAMS property
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27500: The informed query string could not be processed.

Cause: The query string could not be proccessed. It may have wrong information or structure.

Action: Check the content/structure of the query string.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27501: The action was not found. Resource name: "{0}" action name: "{1}"

Cause: The action was not found in the resource/resource collection

Action: Check the resource definition and the request content
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27502: Invalid Resource Type.

Cause: The request is trying to execute an operation in resource collection that is only available for a specific resource. The cause also can be the opposite scenario.

Action: Check the resource path and the operation that was used in the request.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27503: The request content does not represent an action or it has an invalid structure.

Cause: The request content does not represent an action or it has an invalid structure.

Action: Check the request content.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27504: The request content doesn't match the specified resource

Cause: The request content doesn't match the specified resource.

Action: Check the request content and the resource path.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27505: The requested operation is not supported for this HTTP method.

Cause: The requested operation is not supported for this HTTP method.

Action: Check the http method, the URL and the verb that are being used.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27506: The requested operation could not be found for this resource type. Resource Type: {0}; Operation Type: {1}

Cause: The requested operation could not be found for this resource type.

Action: Check the http method, the URL and the verb that are being used.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27507: The action is not enabled. Action name: "{0}"

Cause: The action is not enabled for the resource/resource collection

Action: Check the resource definition and the request
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27508: The action is not bound to a resource. Action name: "{0}"

Cause: The action is not bound to a resource

Action: Check the detail exception to determine the root cause of the problem
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27509: There is no action binding associated with this action. Action name: "{0}"

Cause: There is no action binding associated with this action

Action: Check the detail exception to determine the root cause of the problem
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27510: Error occurred due to applying a search criteria on an attribute with queriable property set to false. Attributes: "{0}"

Cause: Attempt to apply a search criteria on an attribute with queriable property set to false.

Action: Remove search criteria for this attribute and search again.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27511: Error occurred due to invalid attribute being passed in input payload. Attribute: "{0}"

Cause: The input payload in the request contains an invalid attribute.

Action: Check the input payload and try again after removing the invalid attribute.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27512: Metadata Context cannot be changed while in sandbox. Current Sandbox: {0}; Requested: {1}

Cause: An attempt was made to change the Metadata Context after joining a sandbox.

Action: It is illegal to change Metadata Context after joining a sandbox. Specify the same sandbox name in the request header.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27513: Header value is not valid. Header: {0}; Value: {1}

Cause: The request header could not be proccessed. It may have wrong information or structure.

Action: Check the content/structure of the request header.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27514: Resource item to be updated cannot be found using the following search parameters: {0}

Cause: A resource item that needs to be updated is not found with the provided search parameters.

Action: The resource does not exist. To expand the search provide more attribute values.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27515: Failed to execute action as it requires an input payload

Cause: No input payload has been provided for this action.

Action: Provide an input payload when executing this action.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27516: Validation errors were found while processing this request.

Cause: The request header could not be proccessed. It may have wrong information or structure.

Action: Check the request payload.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27517: Invalid framework version. API version provided: {0}. Default framework version based on the API version: {1}. Framework version provided: {2}.

Cause: Invalid framework version

Action: Check the API version and the framework version header
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28000: PersistManager class {0} not found

Cause: The client specified a custom persistent collection through the jbo.pcoll.mgr property. However, the class specified could not be located or loaded.

Action: Make sure that the name specified for jbo.pcoll.mgr is for a valid class name. The class name should be fully qualified with the package name. A special keyword None represents no persistent collection manager, i.e., no spilling to disk will occur.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28001: Cannot connect to database

Cause: An error occurred while attempting to get a JDBC connection for persistent collection management.

Action: Make sure that the database connection URL is correct. The detail to this exception will give further information on the problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28002: Could not create persistence control table {0}

Cause: An error occurred while creating the persistent collection control table. Normally, the control table's name is PCOLL_CONTROL.

Action: Check to make sure that the connection has appropriate authority to create a table. The detail to this exception will give further information on the problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28003: Could not delete row in control table for table {0}

Cause: An unexpected error occurred while attempting to delete the persistent collection control row.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28004: Could not lock row in control table for table {0}

Cause: An error occurred while trying to lock the persistent collection control row. This error is thrown in two situations: An unexpected database error occurred while attempting to lock the row. After the persistent collection manager committed changes to database, it tried to lock the control row. Between the time of commit and lock attempt, another user somehow managed to lock the row and not release it within a set time. In this case, the detail will be null.

Action: In the first case, see the details of this exception for further information on the database problem. In the second case, make sure that no other user locks the control rows outside the Business Components framework.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28005: Could not update row in control table for table {0}

Cause: An unexpected error occurred while attempting to update the persistent collection control row.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28006: Could not create persistence table {0}

Cause: An error occurred while attempting to create a database table to store persistent collection material.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28007: Could not commit while working on persistence table {0}

Cause: An unexpected error occurred while attempting to commit persistent collection changes

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28008: Could not create an index {0} on table {1} for persistent collection

Cause: An error occurred while attempting to create an index on a database table that stores persistent collection material.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28009: Error while getting current time from database

Cause: An unexpected error occurred while attempting to get the system date from the database. For the Oracle persistent manager, the SQL statement used for this would be 'select sysdate from dual'.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28010: Error while getting next sequence value for {0} from database

Cause: An error occurred while attempting to get the next value of a database sequence.

Action: Make sure that the sequence object exists in the database. Also look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28011: Error while querying for the next id from column {1} of table {0}, collection id {2}

Cause: An error occurred while attempting to query for the next id from a pers coll table.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28012: Could not add key column {0} to table {1}

Cause: An error occurred while attempting to create add a key column on a database table that stores persistent collection material.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28013: Could not create key info table {0}

Cause: An error occurred while attempting to create a database table to store key info for persistent collection material.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28020: Passivation error on collection {0}, collection id {1}, persistent id {2}

Cause: An unexpected error occurred while passivating objects into the persistent store. An exception might have been thrown during serialization.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28021: Activation error on collection {0}, collection id {1}, persistent id {2}

Cause: An unexpected error occurred while activating objects from the persistent store. An exception might have been thrown during deserialization.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28030: Could not insert row into table {0}, collection id {1}, persistent id {2}

Cause: An unexpected error occurred while inserting a passivation row into the persistent store table.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28031: Could not update row into table {0}, collection id {1}, persistent id {2}

Cause: An unexpected error occurred while updating a passivation row in the persistent store table.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28032: Could not delete row from table {0}, collection id {1}, persistent id {2}

Cause: An unexpected error occurred while deleting a passivation row from the persistent store table.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28033: Could not retrieve row from table {0}, collection id {1}, persistent id {2}

Cause: An unexpected error occurred while retrieving a passivation row from the persistent store table.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28034: Retrieval by id not supported for collection {0}, collection id {1}. Call enableAccessById()

Cause: The client attempted to retrieve a row in a persistent collection by an id, but the by-id access is not enabled on the persistent collection.

Action: Enable by-id access by calling PCollection.enableIdAccess.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28035: Persistent id {1} is invalid for a collection {0}, collection id {1}. It should be > 0

Cause: The client attempted to retrieve a row by an id, but the id value is invalid. The id must be greater than 0.

Action: Give a valid id.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28036: Object of id {2} is already active in its parent {3} in a persistent collection {0}, collection id {1}

Cause: While attempting to activate an object of a given id, an internal integrity problem was found. In particular, a node which was thought to be passivated was found to be active.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28037: Object of id {2} not found in its parent {3} in a persistent collection {0}, collection id {1}

Cause: While attempting to activate an object of a given id, an internal integrity problem was found. In particular, a child node/element expected to be found in a node is missing.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28038: Could not delete all rows for collection of id {1} from table {0}

Cause: An unexpected error occurred while deleting all passivation rows from the persistent store table.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28039: Root node for collection {0} is invalid, collection id {1}, persistent id {2}

Cause: While attempting to activate an object of a given id, an internal integrity problem was found. In particular, the root node of the persistent collection is no good. It is either (1) <code>null</code>, (2) has younger or older sibling, or (3) has a parent node. None of these should apply to the root node.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28040: Could not retrieve ids of rows whose key id is {1} and hash is {2} from table {0}

Cause: An unexpected error occurred while retrieving an array of persistent ids of rows from the persistent store table of given key hash code at the given key index.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28041: Update found multiple rows or no matching row. Persistence table {0}, collection id {1}, persistent id {2}

Cause: The system tried to update a row in the persistence store table, but it found either no row or more than one matching row.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28100: The resource pool, {0}, failed to create a pooled resource instance.

Cause: Either the JDBC connection pool or the application pool were unable to create a new pooled JDBC connection or application module.

Action: If the exception details indicate that an exception occurred while creating a JDBC connection then check the JDBC connection description to ensure that it references a valid, live database instance. If the exception details indicate that an exception occurred while creating an application module then check the application module configuration to ensure that it references a valid, live application server and application application module class.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28101: An application attempted to set a pooled resource that might be in use as available.

Cause: The application attempted to mark a pooled resource which has already been available in the resource pool as available.

Action: Remove the application logic that invokes {@link oracle.jbo.pool.ResourcePool#setAvailable(Object)}, or move the application logic such that it occurs only once before the resource is made available.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28102: A request was timed out while waiting for a resource to be returned to the resource pool, {0}.

Cause: A client request timed out while waiting for a resource to be returned to the resource pool.

Action: Increase the maximum resource pool size in order to accommodate the maximum expected active request size. If the exception details indicate that the exception was thrown while waiting for an application module in the application pool then the maximum pool size can be increased with the property, jbo.ampool.maxpoolsize. If the exception details indicate that the exception was thrown while waiting for a JDBC connection in the JDBC connection pool then the maximum pool size can be increased with the property, jbo.maxpoolsize.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28103: A pool operation was specified for a pooled resource that does not belong to the resource pool.

Cause: A pool request was made for a resource that does not belong to the pool.

Action: Ensure that the pool request is accessing the same pool instance that was used to acquire the resource instance.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28200: Validation threshold limit reached. Invalid Entities still in cache

Cause: Invalid entities still found in the validation list of the transaction after attempting to validate all invalid entities for the VALIDATION_THRESHOLD 10 times (by default).

Action: Fix any logic that invalidates entity instances in the validation cycle (perhaps in overridden validateEntity() methods) such that all entities are valid before the VALIDATION_THRESHOLD limit is reached.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28201: Post threshold limit reached. Some entities yet to be posted.

Cause: There are invalid entities or entities in the post list of the transaction after trying to post all changes for the POST_THRESHOLD 10 times (by default).

Action: Fix any logic that places entities in the transaction's list of entities to be validated or posted in the post cycle, such that all entities get posted before the POST_THRESHOLD is reached.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28202: Entities invalidated in beforeCommit(). Need to revalidate and post.

Cause: Invalid entity instances found in the transaction in the beforeCommit phase.

Action: Fix any business logic that invalidates entity instances in postChanges() such that there are no more invalid entities after all changes are posted during the commit cycle.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28203: The updated row cannot be refreshed because its key values are unset or modified by database triggers.

Cause: The row could not be refreshed after update because the value of its primary or unique key was not set or unknown.

Action: Ensure values are set for at least one primary or unique key that can be used to fetch the row that is being updated. If that is not possible, use a custom SQLBuilder with doRefreshSQL() defined to refresh the row.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28204: Too many objects match the alternate key {0} for entity {1}, key {2}.

Cause: Attempting to add a new entity to the cache with alternate key that is same as an existing entity. This exception is thrown when uniquing a newly fetched/created entity with the cached set of entities.

Action: Fix the named alternative value of the row. Or, the alternate key definition might have to be augmented with additional attributes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28205: Validator {0} needs a row from iterator {1} to perform its validation, but did not find any row. Validation fails for row with key {2}.

Cause: A validator needs a row to perform validation, but the view object could not find any matching row.

Action: Since the necessary row is not found, the validation failed. Check to ensure that it is not an application error that cause no row to be found.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28206: Row of index {0} not found in range for range-paging mode for query collection {1}.

Cause: The row of the specified index is not in the current range for range-paging mode. The requested operation requires the row to be in the range.

Action: The requested operation cannot be performed because the row is not in the range with range-paging mode. Scroll range to make sure that the desired row is in the range before performing the operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29000: Unexpected exception caught: {0}, msg={1}

Cause: If an unexpected exception occurs during a framework operation, this exception is thrown, with the unexpected exception included in the details of this exception.

Action: Fix the cause for the exception in the details for this JboException.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29001: Type mismatch. Expected {0}. Actual {0}

Cause: During creation of application module in the EJB deployment mode, the object returned by the EJB home is not an instance of oracle.jbo.common.remote.ejb.RemoteApplicationModule.

Action: This usually means that the wrong EJB home is being invoked to create a remote application module. Fix it to point to the correct home.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29004: Server-side configuration for creating the pool not specified.

Cause: A configuration was not specified for the remote ApplicationModule usage.

Action: Use the design time to specify a configuration for the remote ApplicationModule usage.
Level: 1

Type: ERROR

Impact: Configuration

JBO-29100: Attribute {0} is not selected

Cause: Def object is not selected. An attempt was made to access a nonselected def object.

Action: This particular operation is disallowed on a nonselected def object. Avoid this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29101: Attribute {0} is not selected in {1}, operation: {2}

Cause: Def object is not selected. An attempt was made to access a nonselected def object in the specified container object.

Action: This particular operation is disallowed on a nonselected def object. Avoid this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29102: The S_ROW_ID table is unable to generate a new row ID.

Cause: No more row IDs were available in the database's configured row ID range.

Action: Contact the system administrator. The row ID table in the database needs to be refreshed with a new row ID range.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29103: Internal error: {0} cannot be null

Cause: This is an internal exception. The specified argument cannot be NULL.

Action: Contact the System Administrator. The specified argument cannot be NULL.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29104: Unable to create RowId generator application Module. Add the RowIdAM application module in the AM Usage for the current application.

Cause: The RowIdAM application module is not a shared application module of the current application module.

Action: Add the RowIdAM application module in the AM Usage for the current application or contact the System Administrator.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29105: Attributes referenced in view criteria {0}.{1} with property AppliedIfJoinSatisfied do not map to the same entity usage.

Cause: The attributes used in the View Criteria do not map to the same entity usage.

Action: Make sure the attributes used in the View Criteria all map to the same entity usage if AppliedIfJoinSatisfied is set to true.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29106: Attributes referenced in view criteria {0}.{1} with property AppliedIfJoinSatisfied map to the primary entity usage.

Cause: The attributes used in the View Criteria cannot map to the primary entity usage.

Action: Make sure the attributes used in the View Criteria all map to a non-primary entity usage if AppliedIfJoinSatisfied is set to true.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29107: View criteria {0}.{1} with property AppliedIfJoinSatisfied must be used with an entity-based view object.

Cause: The view criteria cannot be used with a non-entity based view object

Action: The view criteria can only be used with an entity-based view object if AppliedIfJoinSatisfied is set to true.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29108: The value specified for the property {0} in the rowidam.properties file is invalid.

Cause: Invalid value specified in the rowidam.properties file. The values cannot be <= 0.

Action: Update the properties to specify accepted values. The property values should be > 0.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29109: The value specified for column {0} in the S_ROW_ID table is invalid.

Cause: One or more column values in S_ROW_ID table are invalid.

Action: Update the S_ROW_ID table with accepted values. The column values should be greater than zero.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29110: Unable to cast the class type specified for RowId comparison to GeneratorSequenceImpl or BigDecimal.

Cause: Invalid value specified for comparison.

Action: The value to be compared with the RowId should be of type BigDecimal or any other type that can converted to BigDecimal.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29111: View criteria {0} is a union VC and contains an invalid element of type {1} at index {2}

Cause: This view crieria is marked for union query but contains a view criteria element which is neither a ViewCriteria nor ViewCriteriaUsage.

Action: A union view criteria can only contain ViewCriteria or ViewCriteriaUsage. Correct the view criteria definition.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29112: The time zone ''{0}'' defined in adf-config.xml or TimeZone.getDefault().getID() does not exist in your Oracle database table V$TIMEZONE_NAMES. Please set an available time zone in your TZ environment variable or user.timezone Java system property.

Cause: The time zone could not be set as the value defined in adf-config.xml or TimeZone.getDefault().getID() does not exist in Oracle database table V$TIMEZONE_NAMES.

Action: Set an existing time zone defined in your Oracle database table V$TIMEZONE_NAMES in TZ environment variable or user.timezone Java system property.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29113: Encountered database recoverable exception. Please retry your request.

Cause: Encountered database recoverable exception.

Action: Retry your request after performing some recovery steps such asacquiring a new connection.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29114: ADF context is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is {1}

Cause: An error message cannot be constructed because ADF context is not setup on the thread.

Action: Use the error code and the stack trace to diagnose the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29115: Unable to get the error message due to error {1}. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is {2}

Cause: An error occured while constructing a display message for an underlying exception.

Action: Use the error code and the stack trace to diagnose the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29116: Data modification not allowed for readonly transaction.

Cause: An attempt was made to modify object in readonly transaction.

Action: Use view object in non read-only transaction for modification.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29117: Transaction security access type {0} does not allow application module {1} security access type {2}.

Cause: An attempt was made to activate application module with different transaction security access type.

Action: Use transaction with same or no security access type.
Level: 1

Type: ERROR

Impact: Security

JBO-29118: Viewobject {0} cannot be created in application with readonly access.

Cause: An attempt to create view object in an application module with unsecured view object.

Action: Create updateable view object in application module that do not contain unsecured view object.
Level: 1

Type: ERROR

Impact: Security

JBO-29119: Unsecured viewobject {0} cannot be created in non readonly access application module.

Cause: An attempt to create unsecured view object in an application module with updateable view object.

Action: Create unsecured view object in application module that do not contain unpdateable view object.
Level: 1

Type: ERROR

Impact: Security

JBO-29120: Unable to create data security provider {0}.

Cause: Unable to create data secured provider.

Action: Verify data security provider class is correct in adf-config.xml and available in classpath.
Level: 1

Type: ERROR

Impact: Security

JBO-29121: View criteria {0} has nested VC that uses variable {1} of type {2}, but variable {1} in view object {3} is of type {4}.

Cause: A correlated sub-query generated for an accessor view object uses a bind variable of the same name as the outer one but has a different type.

Action: Change the data type of the bind variable, or remove the nested view criteria.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29122: Cannot copy variable {0} from {1} to view object {2} for view criteria {3} because a variable of same name is already copied from {4}.

Cause: Two correlated sub-queries generated for two accessor view objects use a bind variable of the same name.

Action: Redefine the bind variable on the root view object, or remove one or both nested view criteria.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29123: View criteria {0} has nested VC on accessor VO {1} which uses bind variable(s). This cannot be applied on view object {2}.

Cause: A correlated sub-query generated for an accessor view object uses a bind variable but the outer view object is a composite view object.

Action: Remove the nested view criteria.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29124: Filter view criteria cannot be applied to iterator {0} of viewobject {1} because it was created from a different viewobject {2}

Cause: An attempt was made to apply a filter view criteria on a viewobject that is not its parent.

Action: Ensure that the filter criteria is applied on the same view object it was created on.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29125: Definition {1} of type {0} is not found. The binding container in use is {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-29126: {0} subclass of Programmatic View Object "{1}" needs to implement method: "{2}"

Cause: Executing a non-supported API on ProgrammaticViewObjectImpl

Action: Override this method in a component or row subclass of programmatic view object to provide custom implementation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29127: No row found in ViewInstance {0} with key {1}

Cause: While executing a query for view link accessor VO, failed to find corresponding row in master VO

Action: Verify, if the master Rowset contains this row
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29128: Programmatic Entity "{1}" needs to implement method: "{0}"

Cause: Executing a non-supported API on ProgrammaticEntityImpl

Action: Override this method in a row subclass of Programmatic Entity to provide custom implementation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29129: View Object information is missing at other end of Association: "{0}"

Cause: "viewobject" attribute is not specified at other association end. It's required for composition associations to perform cascade operations

Action: Define a "viewobject" attribute at other assocation end in AssociationDef
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29130: Unable to convert Attribute value:{0}, from type:{1}, to type:{2}. See details in the Caused By exception.

Cause: Unable to convert the attribute value to COLUMNTYPE or JAVATYPE

Action: Override "convertToSourceType" or "convertToAttributeType" API in ProgrammaticViewRowImpl class to provide custom implementation for conversion
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29131: Exception occurred while creating a new row for "{0}" Programmatic View Object

Cause: A failure occurred while creating a data provider for new programmatic row

Action: Resolve the detail exception raised by createRowData API of programmatic row subclass
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29132: Invalid Comparator object type "{0}" specified for SortCriteria on attribute "{1}"

Cause: Invalid Comparator object type

Action: Comparator object should be an instance of either oracle.i18n.text.OraCollator or java.text.Collator
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29133: Attempt to use a non-existent bind variable {0} in view criteria {1} applied on the view object {2}.

Cause: Invalid bind variable name

Action: Add the bind variable to the VO in it's create or other overridden method before attempting to use.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29140: Failed to build ViewCriteria from expression "{0}" using view object {1}. {2}

Cause: A failure occurred while trying to build a ViewCriteria from an 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-29141: Unable to create criteria item from node: "{0}".

Cause: A failure occurred while trying to create a ViewCriteriaItem from an 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-29142: Cannot create criteria item for an attribute with queriable property set to false. Attribute: {0}.

Cause: An attempt was made to create a ViewCriteriaItem for an attribute with queriable property set to false.

Action: Either mark the attribute as queriable or remove the attribute from the ViewCriteria expression.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29150: The requested version ''{0}'' is not defined or has been removed.

Cause: The requested version is not defined or has been removed.

Action: Specify a valid version.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29151: The requested version ''{0}'' has been desupported.

Cause: The requested version has been desupported.

Action: Specify a supported version.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30000: Application module pool {0} has already been created.

Cause: The application attempted to create an application pool with the same name as an existing application pool.

Action: Correct the application logic that is creating an application pool. Validate that a pool with the given name has not already been registered with the pool manager.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30001: Cookie {0} is invalid.

Cause: Deprecated.

Action: N/A
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30002: The pool signature for the cookie is invalid.

Cause: Deprecated.

Action: N/A
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30003: Application pool {0} fails to check out an application module due to the following exception:

Cause: The pool failed to create an application module instance during checkout. Typically this exception occurs when the pool has been configured with an invalid application module name, EJB server, etc. or when an invalid JDBC username, password, URL, or datasource name has been specified.

Action: See the exception details for more information regarding the failure. Correct the application's configuration properties appropriately.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30004: An application module that was not checked out was checked into the pool, {0}

Cause: The application attempted to check in an application module that was not checked out from the pool.

Action: Remove redundant releaseApplicationModule() invocations from the application logic.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30005: A pool operation was specified for an application module instance that was not created by that pool.

Cause: The application attempted to invoke an application pool method with an application module that was not created by that application pool instance.

Action: Correct the application logic. Use the session cookie that was used to acquire the application module instance to acquire a reference to the application pool that created that application module instance.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30006: The cookie for session {0} and application {1} is not a valid handle for application pool, {2}. The cookie cannot be used to access this pool instance.

Cause: The application attempted to access the application pool with a session cookie that is not registered with that application pool.

Action: Correct the application logic. The application should not reference the application pool directly. Use the session cookie interface for all application pool interaction.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30009: A thread attempted to set as 'available' an application module that could already be in use. An application module's availability cannot be changed from outside of the pool once it has been made available.

Cause: The application attempted to modify the availability status of an application module that is already in active pool use.

Action: Remove the application logic that is updating the application module availability status.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30010: The cookie for session {0} and application {1} cannot be replicated with an active cookie instance.

Cause: The web server attempted to replicate a session cookie with an existing, active cookie.

Action: Internal exception. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30011: A null session cookie application id, session id, or application pool reference ({0}, {1}, {2}) was specified during cookie construction. The cookie could not be constructed.

Cause: The application attempted to create a session cookie with an invalid set of cookie parameters.

Action: Correct the application logic that creates the session cookie. Verify that the cookie session id, application id, and application pool reference are all not null.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30012: A cookie for session {0} and application {1} has already been registered with application pool {2}. The cookie must be removed first.

Cause: The application attempted to create a session cookie in an application pool that already contains that session cookie.

Action: Correct the application logic that creates the session cookie. Remove the existing session cookie before creating a new one in that pool.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30013: The cookie environment for session {0} and application {1} cannot be reset after the cookie has become active.

Cause: The application attempted to change the session cookie environment after the session cookie became active.

Action: Correct the application logic that sets the session cookie environment. Move all logic that changes the session cookie such that it occurs before the session cookie becomes active. A session cookie is active after it is first used to acquire an application module.
Level: 1

Type: ERROR

Impact: Configuration

JBO-30014: The cookie for session {0} and application {1} cannot be removed from the application pool while it has an application module checked out.

Cause: Correct the application logic that sets the session cookie environment. Move all logic that changes the session cookie such that it occurs before the session cookie becomes active. A session cookie is active after it is first used to acquire an application module.

Action: Correct the application logic that removes the session cookie from the application pool. Be sure to invoke SessionCookie.releaseApplicationModule() before invoking ApplicationPool.removeCookie(SessionCookie).
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30015: The cookie for session {0} and application {1} cannot be serialized while in use.

Cause: The application attempted to serialize a session cookie while that cookie had an application module instance checked out or which the cookie was locked by a client request thread.

Action: Correct the serialization logic such that the session cookie is serialized after the session cookie application module has been released to the application pool and after all client requests have released their cookie locks.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30016: The request thread for session {0} and application {1} was timed out while waiting for an available application module in the pool, {2}.

Cause: The application request thread timed out while waiting for an available appliation module instance in the pool.

Action: Prevent wait timeouts by increasing the maximum pool size.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30017: The cookie for session {0} and application {1} cannot be reset while an ApplicationModule is reserved.

Cause: ApplicationModuleRef.resetState() was invoked while the ApplicationModuleRef was referencing a reserved ApplicationModule instance.

Action: Release the ApplicationModule with ApplicationModuleRef.releaseApplicationModule(true, boolean) before invoking resetState.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30018: The cookie configuration does not match the specified configuration. applicationId: {0}, sessionId: {1}, cookieConfig: {2}, specifiedConfig: {3}.

Cause: oracle.jbo.http.HttpContainer.findSessionCookie was invoked with a configName which was different than the configuration that was used to create the specified SessionCookie.

Action: Use a distinct applicationId to identify the cookie for each distinct Configuration.
Level: 1

Type: ERROR

Impact: Configuration

JBO-30019: An unavailable cookie state is detected while attempting to use a cookie from application {0}, session {1}.

Cause: An application pool method was invoked for a cookie that was not currently available. A cookie can be in an unavailable state if another thread is currently updating the cookie. For example, consider the following scenario: 1. cookie 1 releases an ApplicationModule with the managed state option 2. cookie 2 targets that ApplicationModule for recycling 3. Before cookie 2 has passivated the ApplicationModule state for cookie 1, cookie 1 requests another ApplicationModule In this instance the ApplicationPool could throw an unavailable exception. Note that most of the occurrences of this exception should be handled by the pooling framework.

Action: Report the exception to Oracle Support Services. Attempt the invalid operation again.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30020: An invalid SessionCookie release mode was specified. applicationId: {0}, sessionId: {1}.

Cause: oracle.jbo.common.ampool.SessionCookie.releaseApplicationModule was invoked with an unsupported releaseMode.

Action: Invoke releaseApplicationModule(int) with a valid releaseMode attribute. Valid releaseModes include: SessionCookie.SHARED_MANAGED_RELEASE_MODE SessionCookie.SHARED_UNMANAGED_RELEASE_MODE SessionCookie.RESERVED_MANAGED_RELEASE_MODE SessionCookie.RESERVED_UNMANAGED_RELEASE_MODE
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33000: Configuration file {0} is not found.

Cause: The requested configuration file could not be found.

Action: Provide a correct name for the configuration file. Or, make sure that the named configuration file can be found in one of the accessible paths.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33001: Configuration file {0} is not found in the classpath.

Cause: The requested configuration file could not be found in the class paths.

Action: Make sure that the named configuration file can be located in one of the class paths.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33003: Connection name {0} is not defined.

Cause: The specified connection could not be found. Or an error occurred during processing of the specified connection.

Action: Make sure that the connection name is correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33004: Configuration file cannot be parsed.

Cause: An error occurred while parsing configuration file.

Action: Check to make sure that the configuration file is a valid XML file. See the detail exception for further information.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33005: Configuration {0} is not found.

Cause: The named configuration parameter was not found in the configuration.

Action: The system expects to find the named configuration parameter, but could not. Check the configuration content to make sure that it contains the named configuration parameter.
Level: 1

Type: ERROR

Impact: Configuration

JBO-33006: Data source {0} is not supported.

Cause: This error message indicates that the underlying SQLBuilder does not support datasource.

Action: For this SQLBuilder, do not use datasource.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33007: Data source {0} is not found.

Cause: The specified datasource could not be found.

Action: Make sure that the datasource name is correct. See the detail exception for further info.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33020: Current time is not available from SQL statement "{0}".

Cause: An error occurred while getting the current time from the database.

Action: If there is a detail exception, it will give further information about what went wrong. If no detail exception was provided, that means the SQL statement to get the current time returned no result (no row). Check the SQL statement for correctness.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33021: User {0} cannot be authenticated.

Cause: An error occurred while authenticating the user.

Action: Make sure that the user authentication information is correct.
Level: 1

Type: ERROR

Impact: Security

JBO-33022: Thread {0} has timed out while waiting to acquire a lock.

Cause: A thread timed out while waiting for a resource that was protected with an 'oracle.jbo.common.Lock'.

Action: Verify that all threads that have acquired a lock have properly released that lock in a 'finally' code block.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33023: Thread {0} is attempting to release a session cookie lock that it did not acquire.

Cause: The application attempted to release a {@link oracle.jbo.common.Lock} that it did not hold.

Action: Internal exception. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33024: Graph nodes cannot be sorted due to a cycle in the graph.

Cause: A cycle was detected in the dependency graph.

Action: Check the edges in the graph and remove any cycles.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33025: Failed to release application module {0}. Cookie handle not found.

Cause: Failed to release application module due to missing cookie handle.

Action: Invoke the correct, counterpart releaseAM method.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33026: Value must be between {MinVal} and {MaxVal}

Cause: Input values failed the range validator test.

Action: Provide values that are within the range validator paramters.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33027: Value must be greater than {MinVal}

Cause: Input values failed the minimum validator test.

Action: Provide values that are greater than the minimum.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33028: Value must be less than {MaxVal}

Cause: Input values failed the maximum validator test.

Action: Provide values that are less than the maximum.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33029: Value must have exactly {MinLength} characters

Cause: Input values must be longer than minimum length.

Action: Provide values that are longer than the minimum length.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33030: Value can have at most {MaxLength} characters

Cause: Input values exceeded maximum length length.

Action: Provide values that are less than or equal to maximum length.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33031: Value must have at least {MinLength} and at most {MaxLength} characters

Cause: Value must have at least (minLen) and at most (maxLen) characters.

Action: Provide values that are between minimum and maximum length.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33032: Value must have exactly {MaxLength} characters

Cause: alue must be exactly (maxLen) characters.

Action: Provide values that is exactly the maximum length.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34000: Definition class name missing in XML file of type {0}

Cause: Name of the definition Java class missing in the JClient XML file.

Action: Every metaobject in JClient must have name of the definition object's Java class in the XML file. Correct the error by regenerating XML file in the design time.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34001: Iterator binding {0} is not of the expected class {1}

Cause: The iterator binding is of the wrong Java class. Some controls expect to work with a JUIterRowBinding, while others with JUIterRangeBinding. This error indicates that the supplied iterator binding is not of the expected class.

Action: If the error is caused by some client code that supplies an iterator binding, correct the code to supply an iterator binding of the correct class. If the error is caused by framework code, contact Oracle Support Services with the stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34002: The application obj has already been set for form binding {0}. Cannot do it again

Cause: The form binding has already been registered with an application (JUApplication) object. It is illegal to try to set the form binding's application object again.

Action: This error typically means a program error. Contact Oracle Support Services with the stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34003: No iterators bound with the given name :{0}

Cause: No iterator binding found with the given name.

Action: Fix the iterator binding name before attempting to change the iterator associated with it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34004: No matching row found for entered or selected item in the LOV iterator for a list-binding.

Cause: No matching row found for a selected value in a List binding.

Action: Enter/Select a valid item from the list so that the matching row in the LOV iterator can be found.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34005: Exceptions occurred in synchronizing updates from this application. Click Details to see the complete list.

Cause: Exceptions occurred in synchronizing data from the client Application into the Business Components tier.

Action: Fix the exceptions displayed in the details list and then reapply the changes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34006: Method that creates the iterator for this object returns null.

Cause: Collection to which this iterator is bound returns null.

Action: Fix the return value so that a valid collection is available for this iterator to bind to.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34007: A value is not passed for mandatory parameter {0}.

Cause: Mandatory Parameter was not set by the calling code either programmatically or by overriding it in a nested container usecase.

Action: Set the mandatory parameter value
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34008: Final parameter {0} cannot be modified.

Cause: Mandatory Parameter was not set by the calling code either programmatically or by overriding it in a nested container usecase.

Action: Set the mandatory parameter value
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34009: ListBinding definition :{0} not found.

Cause: Server side ListBinding could not be found with the given usage name.

Action: Fix the server side ListBinding usage name in List binding metadata
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34010: The "{0}" descriptor appears in the application classpath more than once: - {1} - {2}

Cause: The cpx classpath name has already been found at a different source in the classpath. It is illegal to have the same relative cpx name in the classpath more than once.

Action: Refactor one of the indicated URLs in the message so it appears under a different relative package in the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34011: Validator expression {0} did not result in a valid object for bindingContainer:{1}

Cause: Expression for custom validator does not resolve into a valid object that as a public method of name validateBindingContainer and that takes the bindingContainer as the only parameter.

Action: Provide a different expression or fix the expression so that an object whose class has a method with following signature: public validateBindingContainer(DCBindingContainer ctr)
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34012: Attempting to register a Swing binding factory when Faces version is already installed.

Cause: Faces binding factory is already installed for ADF Model bindings. Attempt to install a Swing version will break the application due to binding class incompatibilities.

Action: Remove or replace references to juimodel in namespace attributes, in pagedef xml files in the application with: http://xmlns.oracle.com/adfm/uimodel.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34013: Enter a nonempty string and a string not equal to ''%'' in the list:{0} to filter the list of values.

Cause: Empty string or % was entered to filter list datsource for a list binding.

Action: Enter any other string to filter by in the list component bound to this list binding.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34014: No matching child node found for row with key:{0} under parent node:{1}

Cause: No matching node in the current range of rows found for a row retrieved from the backend collection.

Action: Scroll the backend collection to the appropriate range where a node for this row will be found. If row keys are for rows outside of current range of rows in the RowIterator, use alternate client apis to access the row data avoiding calls into this node binding.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36000: An unexpected expression token is found.

Cause: Unexpected token found.

Action: Found an unexpected expression token. Make sure that the words are spelled correctly and that the expression makes sense.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36001: Mismatching parentheses are found.

Cause: Mismatching parentheses.

Action: Examine the expression and ensure that open parentheses match up with closing parentheses.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36002: The method call specification is invalid. "," or ")" is expected.

Cause: Invalid method call. After a method parameter, ',' or ')' is expected, but neither was found.

Action: Examine the expression and correct method invocation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36003: An expression token is not found.

Cause: Expecting a token. The expression string was terminated unexpectedly.

Action: Examine the expression and ensure that the expression does not end unexpectedly.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36004: Mismatching square brackets are found. An invalid array index is specified.

Cause: Mismatching square brackets.

Action: Examine the expression and ensure that open square brackets (for array index) match up with closing brackets.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36005: Variable {0} is not found.

Cause: Variable not found.

Action: Examine the expression and ensure that the variable name is correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36006: cannot convert {0} into {1}

Cause: Cannot convert data.

Action: Cannot convert data from one class to another. Examine the expression and ensure that the data assignment does not cause incompatible conversion of data.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36007: Binary operation {0} is invalid for strings.

Cause: An attempt was made to invoke an invalid binary operation on two strings.

Action: Examine the operation ID and correct the expression so that the invalid binary operation is not attempted on strings. The expression runtime only recognizes addition as a valid binary operation between two strings.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36008: The AND separator for a BETWEEN operator cannot be found. Token {0} is found instead.

Cause: A BETWEEN operator was found but no AND for the two comparison expressions.

Action: Take a look at the expression string. The correct syntax for BETWEEN is 'testVal BETWEEN value1 AND value2'. The expression parser could not find the AND keyword. Correct the expression.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-55001: A value of type {1} cannot be set to a value of type {0}.

Cause: Unexpected type was provided to Variant utility.

Action: Provide an expected type as reported in the exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-55002: Variant type {0} is invalid.

Cause: The data-type passed to the Variant utility from a Validation rule is invalid. This could be due to a corrupt XML-metadata definition in the component's XML file.

Action: Fix the component XML for the offending validation rule.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-55003: Variant name {0} is invalid.

Cause: The name of the variant type passed to the Variant utility from a Validation rule is invalid. This could be due to a corrupt XML meta data definition in the component's XML file.

Action: Fix the component XML for the offending validation rule.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56001: Row value is missing for data object {0}.

Cause: The Row Value for a SDOValueStore is null.

Action: Should not use SDOValueStore with a NULL row value.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56002: Operation {0} on object {1} is not supported.

Cause: An attempt was made to invoke an invalid service operation.

Action: Ensure that this service operation is defined at design time.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56003: Nonpersistent attribute {0} cannot be used in a database mode view criteria.

Cause: A nonpersistent attribute is used for DB ViewCriteriaItem.

Action: Make sure the attribute is persistent.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56004: Non-ViewLink accessor attribute {0} cannot be used for a view criteria item that has nested view criteria.

Cause: A non-ViewLink accessor is used for DB ViewCriteriaItem that has nested ViewCriteria.

Action: Make sure the attribute is a ViewLink accessor.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56005: SDO type is not found for ViewObject {0} with namespace {1} and name {2}.

Cause: SDO Type is not found for a ViewObject.

Action: Make sure the viewobject is SDO enabled.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56006: ComplexType or DataType SDO property {0} has conflict values {1} vs. {2} for attribute {3}.

Cause: Conflict input values for ComplexType non-value properties.

Action: Make sure the payload has the same values for the same ComplexType non-value properties.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56007: ViewObject not found for sdo dataobject {0} from base viewobject {1}.

Cause: Can't find corresponding ViewObject for one SDO Type.

Action: Make sure passing valid SDODataObject that maps to valid ViewObject.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56008: Mapped value for name {0} not found in viewobject {1} attribute {2}.

Cause: Can't find mapped value for one given name.

Action: Add neccessary name/value to PropertySet.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56009: Mapped name for value {0} not found in viewobject {1} attribute {2}.

Cause: Can't find mapped value for one given value.

Action: Add neccessary name/value to PropertySet.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56010: Comparision Operation {0} is invalid for ViewCriteriaItem of attribute {1}.

Cause: The attempted operation is invalid for a ViewCriteriaItem.

Action: Change the input value of this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56011: No valid lastUpdateTime found for service {1}.

Cause: SDOSchemaResolver can't figure out service schema lastUpdateTime.

Action: Turn on oracle.jbo FINEST log for more information.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56012: SQLException from preparing or executing sql statement with original Jbo error code JBO-{0}. Please contact service provider on details.

Cause: Sql statement preparation or execution errors.

Action: Contact service provider for details.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56013: Groovy Row Function {0} for ViewUsage {1} is not defined yet or not allowed to invoke.

Cause: Sql statement preparation or execution errors.

Action: Contact service provider for details.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56014: SDOProperty not found for ViewObject {0} attribute {1}. Please check this attribute's SDOHidden property!

Cause: SDO Property is not found for a ViewObject Attribute.

Action: Make sure the viewobject attribute is SDO enabled.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56101: Nonpersistent attribute {0} cannot be sorted upon.

Cause: A nonpersistent attribute is used for DB SortCriteria.

Action: Make sure the attribute is persistent.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56102: Dependencies specified for view attribute {0} conflict with dependencies specified on the underlying entity attribute.

Cause: View attribute dependencies conflict with the entity attribute dependencies.

Action: Ensure that the dependencies are not specified on both the view and entity attribute.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56103: View object {0} is not prepared.

Cause: This is the exception that gets thrown by ViewObjectImpl when attempting an operation on a declarative view object on which prepareVOForQuery has not been called, such as findByAltKey (bug 7455860) or createAndInitRow (bug 7504211).

Action: Call ViewObjectImpl.prepareVOForQuery before calling findByAltKey or createAndInitRow for the first time.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56104: Entity {0} cannot be set to batch mode because it has streaming attribute types (e.g., Blob, Clob).

Cause: An attempt was made to set batch mode on an entity that has streaming attribute types (e.g., Blob, Clob).

Action: Remove BatchThreshold value from this entity's metadata.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-57001: Invocation of service URL used in connection failed with status code {0}.

Cause: The service URL used in DataControl is not accessible or has returned an error condition.

Action: Contact your system administrator to make sure service URL used in datacontrol is accessible. If a network proxy has to be used, make sure proxy has been setup properly.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-57101: Unexpected error adding resource {0} to resource bundle {1}.

Cause: An unexpected error occured while adding the string to the resource bundle.

Action: Contact your system administrator to ensure that your application configurations for resource bundles are correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-57102: Could not find specified resource bundle: {0}.

Cause: Could not find the specified resource bundle

Action: Contact your system administrator to ensure that your application configurations for resource bundles are correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-57103: {0} is registered in the application, but it is not overrideable.

Cause: The specified resource bundle is not overridable

Action: Contact your system administrator to ensure that your application configurations for resource bundles are correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-57104: Unable to convert value of {0} in {1} to type {2}. {3}

Cause: Unable to convert the attribute to its java type

Action: Ensure that the underlying data type is compatible with the attribute's java type
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

26 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, OUD 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 {1}.

Cause: An invalid value was provided for this application.

Action: Provide the correct value for the application.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00027: There was an internal error: {0}

Cause: Internal system error was found.

Action: See the log files or contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-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 associated with policy store found.

Cause: No identity store associate with policy store found

Action: Contact system administrator
Level: 1

Type: ERROR

Impact: Configuration

JPS-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}, upgrade the Policy store schema to latest version.

Cause: Comparison of the Policy schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-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}, upgrade the Credential store schema to latest version.

Cause: Comparison of the Credential schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-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 parse 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} is not supported.

Cause: {0} is 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}, upgrade the Keystore schema to latest version.

Cause: Comparison of the Keystore schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-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 virtualizes flag, but references other service instance.

Cause: Failed to create identity store service instance {0}. Cause: the service does not enable the virtualize flag, but references other service instance.

Action: Either make the virtualize flag true, or directly define the ldap configuration instead of using service reference
Level: 1

Type: WARNING

Impact: Configuration

JPS-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} was invalid LdapName format, see javax.naming.ldap.LdapName

Cause: The DN {0} was invalid LdapName format, see javax.naming.ldap.LdapName

Action: Ensure property in format of javax.naming.ldap.LdapName.
Level: 1

Type: WARNING

Impact: Configuration

JPS-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}, upgrade the Audit store schema to latest version.

Cause: Comparison of the Audit schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-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-00166: Failed to retrieve Embedded LDAP store information.

Cause: Failed to retrieve embedded ldap store information.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00167: Invalid xml content was found. {0} Location: {1}.

Cause: Invalid xml content was found. {0} Location: {1}.

Action: Fix the invalid xml elements according to the xsd schema definition.
Level: 1

Type: WARNING

Impact: Security

JPS-00168: OID server version {0} is not supported

Cause: OID server version {0} is not supported

Action: Check the support matrix.
Level: 1

Type: ERROR

Impact: Other

JPS-00169: Cannot get server log directory. Reason: {0}.

Cause: Cannot get server log directory. Reason: {0}.

Action: Check server configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00170: Initializing OPSS Java Policy Provider.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00171: OPSS Java Policy Provider initialized.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00172: OPSS Java Policy Provider is set as the system-wide Policy object.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00173: OPSS Java Policy Provider is already set as the system-wide Policy object. Skipped setting the system-wide Policy object.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00174: Failed to create the enterprise user principal for "{0}". Reason: {1}.

Cause: Error on creating the enterprise user principal.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00175: Failed to create the enterprise group principal for "{0}". Reason: {1}.

Cause: Error on creating the enterprise group principal.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00176: Service instance of {0} is in state {1} that does not allow invocation of {2}.

Cause: Service instance is in a state that does not allow current invocation.

Action: Only invoke service instance's method when it is in right state.
Level: 1

Type: WARNING

Impact: Security

JPS-00177: Failed to clean up application security artifacts.

Cause: Error on cleaning up application security artifacts.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00178: Service provider " {0} " not available from configuration service.

Cause: Service provider not available.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00179: Service context configuration for " {0} " not available from configuration service.

Cause: Service context configuration not available.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00180: Failed to create service context for tenant ID " {0} ".

Cause: Failed to create service context.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00181: Your search criteria (current search iterator) has expired(stale). Start a new search.

Cause: Your search criteria (current search iterator) has expired(stale).

Action: Start a new search.
Level: 1

Type: ERROR

Impact: Other

JPS-00182: Method getView for JpsConfigurationP was not run for RuntimeViewAdapter object before calling getServiceProperties() of ServiceInstanceDescriptorAdapter

Cause: Method getView for JpsConfigurationP was not run for RuntimeViewAdapter object before calling getServiceProperties() of ServiceInstanceDescriptorAdapter

Action: Call method getView for JpsConfigurationP on RuntimeViewAdapter object before calling getServiceProperties() of ServiceInstanceDescriptorAdapter
Level: 1

Type: ERROR

Impact: Configuration

JPS-00183: Jps diagnostics started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

JPS-00184: Jps diagnostics startup failed.

Cause: Failed to start JPS diagnostics.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Other

JPS-00185: Tenant Context is not set

Cause: Tenant Context is not set

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Security

JPS-00186: Failed to validate the Tenant Context for the tenant with ID " {0} ".

Cause: Tenant Context is Invalid

Action: Only invoke services that you signed up for
Level: 1

Type: ERROR

Impact: Security

JPS-00187: A dump to execute JPS diagnostic tests.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

JPS-00188: Dumps security information in current execution thread, such as application name, subject, etc.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

JPS-00189: OPSS diagnostic test to execute.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

JPS-00190: Tenant ID cannot be found from user "{0}" profile.

Cause: Tenant ID cannot be found from authenticated user profile.

Action: Check user profile.
Level: 1

Type: WARNING

Impact: Other

JPS-00191: Identity context not found.

Cause: IdentityContext not found from request attributes.

Action: OAM IAP.
Level: 1

Type: WARNING

Impact: Other

JPS-00192: Service instance not found for the service type.

Cause: Service instance not available for the service type.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00193: Service instance "{0}" cannot be instantiated. Reason: {1}.

Cause: Service instance cannot be instantiated.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00194: OPSS diagnostic test parameters to execute. Example: username=user1;groupname=group1

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

JPS-00195: Dumps properties used to initialize User/Role Api when User/Role Api initialization fails.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

JPS-00196: Jps started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00197: Failed to migrate application credential during deployment.

Cause: Migration of Application credential failed during deployment.

Action: Check the server logs for details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00198: Custom product logger set (class: {0}, name: {1}). All JPS messages would be redirected to this logger.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00199: JpsLogger has initialized Loggers. Cannot set custom product Logger after initializing loggers.

Cause: Loggers have already been initialized.

Action: Set product logger before creating JpsLogger instance.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00200: Invalid path. Please make sure the provided config path is a directory.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00201: Invalid path. Please make sure the provided config directory has jps-config.xml and jps-config-jse.xml inside it.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00202: Jps post service activation operations started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00203: Upgrade of file based domain not supported

Cause: Upgrading of file based domain not supported

Action: Please move the file based domain to database based domain, then run reconfiguration
Level: 1

Type: ERROR

Impact: Configuration

JPS-00204: Migrate source or destination store context lookup failure

Cause: Migrate source or destination context in migration could not be looked up.

Action: Check the configuration file to verify service context settings
Level: 1

Type: ERROR

Impact: Configuration

JPS-00205: Security store version configured is incompatible

Cause: Security store version configured is incompatible with this release.

Action: Please use security store version 12.1.3 or lower
Level: 1

Type: ERROR

Impact: Configuration

JPS-00206: Jps is already started.

Cause: Can not start Jps again since it is already started.

Action: Please do not start JPS if it is already started
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00207: Service context {0} is not in active state

Cause: Service context is not in active state.

Action: Please check logs to see service context failure.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00208: Jps initializing.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00209: Jps startup failed.

Cause: Jps startup is failed due to some error.

Action: Please check logs to see Jps startup failure.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00210: Jps inactive.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00211: Not supported platform type {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00212: Error occurred while stopping jps due to: {0}.

Cause: Error occured while stopping the OPSS

Action: Check the server logs for details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00213: parameter "{0}" cannot be null

Cause: method parameter cannot be null

Action: provide a non-null value for the parameter
Level: 1

Type: ERROR

Impact: Data

JPS-00214: Operation "{0}" is not supported in OPSS Mode "{1}".

Cause: the invoked operation is not supported in JPS_API mode

Action: set the OPSS Mode to one of COMPATIBLE or MULTIPLE
Level: 1

Type: ERROR

Impact: Configuration

JPS-00215: executeAs: Switching SecurityContext from "{0}" to "{1}" is not permitted.

Cause: the requested SecurityContext Switch is not Permitted

Action: Look at documentation for allowed context switches
Level: 1

Type: ERROR

Impact: Configuration

JPS-00216: Failed to get a handle to the global audit service for tenant {0}.

Cause: Failed to get a handle to the global audit service

Action: Check configuration
Level: 1

Type: ERROR

Impact: Security

JPS-00217: The schema specified in {0} is already in use for security store. Please create a new schema.

Cause: The schema specified in {0} is already in use for security store.

Action: Please create a new schema.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00218: Comparison of credential failed for map : {0}, key : {1}.

Cause: Encryption key comparison failed.

Action: Retry importEncryptionKey command or api.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

JPS-00219: Expected keys not found in the credential map : {0}.

Cause: Expected keys not found in the credential map

Action: Verify the credential store content.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

JPS-00220: Cannot find datasource definition {0}. Reason: {1}.

Cause: Cannot find datasource definition {0}. Reason: {1}.

Action: Check weblogic configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00221: Error occurred while resetting jps due to: {0}.

Cause: Error occured while resetting OPSS

Action: Check the server logs for details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00222: Jps is reset.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00223: Specified JPS context "{0}" not found

Cause: Specified JPS context not found

Action: Check the input configuration that the correct context name is present and is the one supplied as input.
Level: 1

Type: WARNING

Impact: Security

JPS-00224: Invalid inputted migration parameters "{0}"

Cause: Invalid inputted migration parameters

Action: Check inputted migration parameters.
Level: 1

Type: ERROR

Impact: Security

JPS-00225: Commmand: {0} is not supported.

Cause: Commmand: {0} is not supported.

Action: Use a valid command. Try <command> --help for more information.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00226: Service setup check completed for configurator.

Cause: Service setup check completed for configurator.

Action: No Action Required
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00227: Completed the Migration of Policy Artifacts.

Cause: Completed the Migration of Policy Artifacts.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-00228: Security store is not seeded with the schema.

Cause: Security store is not seeded with the schema.

Action: Check the log files to resolve the warning.
Level: 1

Type: WARNING

Impact: Other

JPS-00229: Trying to load the schema into the security store ...

Cause: Trying to load the schema into the security store ...

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00230: BootStrap Wallet file is created.

Cause: BootStrap Wallet file is created.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Programmatic

JPS-00231: Completed the seeding of schema into the security store.

Cause: Completed the seeding of schema into the security store.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

JPS-00232: Successfully loaded the security store schema.

Cause: Successfully loaded the security store schema.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00233: Migration of Policy Artifacts failed.

Cause: Migration of Policy Artifacts failed.

Action: Check the log files for details.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00234: Persist jps-config.xml to directory: {0} - done.

Cause: Persist jps-config.xml to directory: {0} - done.

Action: No action Required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00235: Persist jps-config-jse.xml to directory: {0} - done.

Cause: Persist jps-config-jse.xml to directory: {0} - done.

Action: No action Required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00236: Bootstrap key store service instance already present in bootstrap credential store context.

Cause: Bootstrap key store service instance already present in bootstrap credential store context.

Action: No Action Required
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00237: Adding keystore service instance to bootstrap context for the {0} file.

Cause: Adding keystore service instance to bootstrap context for the {0} file.

Action: No Action Required
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00238: Error in loading the property file.

Cause: Error in loading the property file.

Action: Check the log files to resolve the error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00239: Exception while updating the keystore service instance to bootstrap context for {0} file.

Cause: Exception while updating the keystore service instance to bootstrap context for {0} file.

Action: Check the log files to resolve the error.
Level: 1

Type: ERROR

Impact: Process

JPS-00240: JpsConfiguration object is not passed, not able to add Keystore service instance to Bootstrap context.

Cause: JpsConfiguration object is not passed, not able to add Keystore service instance to Bootstrap context.

Action: Check the log files to resolve the error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00241: No file based keystore service instance is found, not able to add Keystore service instance to Bootstrap context.

Cause: This operation is not supported in restricted-JRF domain

Action: Please check document for supported operations in restricted-JRf domain
Level: 1

Type: ERROR

Impact: Configuration

JPS-00242: This operation is not supported in restricted-JRF domain

Cause: No file based keystore service instance is found, not able to add Keystore service instance to Bootstrap context.

Action: Check the log files to resolve the error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00243: {0} cannot be started as JRF Executor serivce retrieval got failed.

Cause: {0} cannot be started as JRF Executor serivce retrieval got failed.

Action: Check stack trace for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00244: No audit log directory is set. Cannot perform audit operations for component {0}.

Cause: Failed to get audit log directory. Audit calls may fail.

Action: Check if the audit log directory is set either in audit service properties or as a system property.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00245: No audit log directory is set. Disabling audit for component {0}.

Cause: Failed to get audit log directory.

Action: Check if the audit log directory is set either in audit service properties or as a system property.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00246: new Startup().start() is required to be called before using OPSS API.

Cause: OPSS API is used without calling new JpsStartup().start() first.

Action: Call new JpsStartup().start() before using OPSS API.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00247: Could not retrieve tenant context.

Cause: Tenant context could not be retrieved.

Action: Ensure tenant has been provisioned.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00248: This JpsStartup object was cleaned up. To start OPSS again, need create a new instance of JpsStartup.

Cause: The start() method is called on an JpsStartup object that was cleaned up.

Action: Create a new instance of JpsStartup, then call the start() method on it.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00249: Operation "{0}" can only be performed when OPSS is in state "{1}". Current state is {2}.

Cause: Operation "{0}" can only be performed when OPSS is in state "{1}". Current state is {2}.

Action: Perform operation "{0}" only when OPSS is in state "{1}".
Level: 1

Type: ERROR

Impact: Configuration

JPS-00250: OPSS is already pre-started.

Cause: preStart() is called when OPSS is already pre-started.

Action: Do not call preStart() if OPSS is already pre-started.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00251: This JpsStartup object is already reset.

Cause: reset() on a JpsStartup object is called when the object is already reset.

Action: Do not call reset() when the JpsStartup objet is already reset.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00252: The {0} operation starting for partition {1}.

Cause: Starting the operation for partition.

Action: No Action Required
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00253: The {0} operation completed for partition {1}.

Cause: Completed the operation for partition.

Action: No Action Required
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00254: Tenant services {0} successfully for partition {1}.

Cause: Tenant services operation done successfully for partition.

Action: No Action Required
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00255: JPS post service started.

Cause: JPS post service started.

Action: No Action Required
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00256: JPS default service started.

Cause: JPS default service started.

Action: No Action Required
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00257: JPS bootstrap service started.

Cause: JPS bootstrap service started.

Action: No Action Required
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00258: Bootstrap services are used by OPSS internally and clients should never need to directly read/write bootstrap credentials. If required, use Wlst or configuration management interfaces.

Cause: An attempt to obtain bootstrap context is made.

Action: Use WLST commands like addBootstrapCredential /modifyBootstrapCredential if required.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00259: Cannot terminate OPSS service context for partition {0}. Reason {1}.

Cause: Cannot terminate OPSS service context for partition {0}. Reason {1}.

Action: Check reason for detail
Level: 1

Type: WARNING

Impact: Configuration

JPS-00260: Database access error. SQL state: {0}, error code: {1}.

Cause: Database access error. SQL state: {0}, error code: {1}.

Action: Check log for detail.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00261: Invalid value for "order" : {0} in service instance reference {1}

Cause: Configuration is corrupt.

Action: Correct the configuration
Level: 1

Type: ERROR

Impact: Configuration

JPS-00262: Duplicate value for "order" : {0} in service instance reference {1}

Cause: Configuration is corrupt.

Action: Correct the configuration
Level: 1

Type: ERROR

Impact: Configuration

JPS-00263: Cannot modify read only artifacts

Cause: An attempt to modify/delete read only artifacts has been made.

Action: Read only artifacts cannot be modified at runtime.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-00264: Database is disconnected. SQL state: {0}, error code: {1}.

Cause: Database is disconnected. SQL state: {0}, error code: {1}.

Action: Check log for detail.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00265: executeAs: SecurityContext with name "{0}" does not exist

Cause: The requested SecurityContext does not exist

Action: Input a valid SecurityContxt name
Level: 1

Type: ERROR

Impact: Configuration

JPS-00648: Operation is not supported - unable to set key entry for non-existent stripe and keystore.

Cause: Combining certs from two truststores into a single truststore failed

Action: Look at the logs for any exceptions that could have caused this failure
Level: 1

Type: WARNING

Impact: Compliance

JPS-00649: ************************************************************** * Demonstration CA was found in use in this environment. * * This deployment may be vulnerable to security attacks. * * Replace the Demonstration CA with a custom CA immediately. * ****************************************************************

Cause: Demonstration CA was found in use in a production environment.

Action: Refer documentation to switch to a custom CA.
Level: 1

Type: WARNING

Impact: Compliance

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-01061: Access to boostrap credential store denied to application code.

Cause: Application code was trying to access a bootstrap credential store. Bootstrap credential store is intended only for the OPSS usage.

Action: bootstrap_credstore_context need not be used for credential store operations.
Level: 1

Type: ERROR

Impact: Security

JPS-01062: A backup of the bootstrap credential store could not be created.

Cause: A backup of the bootstrap cwallet.sso could not be created.

Action: Investigate the logs to find out the root cause of the exception in file operations
Level: 1

Type: ERROR

Impact: Security

JPS-01063: Credential compatibility check failed. Cannot migrate credential: {0}

Cause: There exists one or more generic credential in the store that cannot be migrated.

Action: Ensure that the store does not contain any generic credential with binary attribute before migration.
Level: 1

Type: WARNING

Impact: Security

JPS-01064: Invalid password: Passwords must have a minimum length of eight characters and contain alphabetic characters combined with numbers or special characters.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-01065: Could not decrypt credential due to encryption key mismatch.

Cause: Decryption of credential failed

Action: Ensure that the bootstrap wallet contains the correct encryption key that was used to encrypt the credentials in the store.
Level: 1

Type: ERROR

Impact: Security

JPS-01066: Cannot get credential due to database disconnected. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

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-01544: The provided configuration file path {0} is invalid or null.

Cause: The provided configuration file path {0} is invalid or null.

Action: Provide a valid configuration file path.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01545: Back up of JPS Config file {0} done.

Cause: Back up of JPS Config file {0} done.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-02000: The authentication of user {0} succeeded.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02001: The authentication of user {0} failed. Reason: {1}

Cause: User authentication failed.

Action: Ensure the user exists in the identity store. Check the user credentials that are being sent for authentication.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-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: Asserter class was configured as {0}, but does not implement {1}.

Cause: Assertor class was configured as {0}, but does not implement {1}.

Action: Provide an Assertor that implements {1}.
Level: 1

Type: ERROR

Impact: Other

JPS-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-02051: No auth module to validate request: auth context ID "{0}" of application context "{1}".

Cause: Server auth context did not have auth module to validate request.

Action: Ensure that the server auth module is properly configured and bound for use by applications.
Level: 1

Type: ERROR

Impact: Security

JPS-02052: No auth module to secure response: auth context ID "{0}" of application context "{1}".

Cause: Server auth context did not have auth module to secure response.

Action: Ensure that the server auth module is properly configured and bound for use by applications.
Level: 1

Type: ERROR

Impact: Security

JPS-02053: No auth module to validate response: auth context ID "{0}" of application context "{1}".

Cause: Client auth context did not have auth module to validate response.

Action: Ensure that the client auth module is properly configured and bound for use by applications.
Level: 1

Type: ERROR

Impact: Security

JPS-02054: No auth module to secure request: auth context ID "{0}" of application context "{1}".

Cause: Client auth context did not have auth module to secure request.

Action: Ensure that the client auth module is properly configured and bound for use by applications.
Level: 1

Type: ERROR

Impact: Security

JPS-02055: Cannot instantiate auth module class "{0}" for application context "{1}", cause: {2}.

Cause: Could not load the auth module.

Action: Ensure that the module class name is correctly supplied and the class is in the class path.
Level: 1

Type: ERROR

Impact: Security

JPS-02056: The auth module must support message type: {0}.

Cause: Auth module did not support the required message type.

Action: Ensure that the class correctly implements the required auth module interfaces.
Level: 1

Type: ERROR

Impact: Security

JPS-02057: The message layer "{0}" is not supported.

Cause: The specified message layer was not supported.

Action: Provide a valid message layer.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02058: Null callback handler is not supported.

Cause: The specified callback handler was null.

Action: Supply a non-null callback handler.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02059: The default auth provider "{0}" for layer "{1}" is not configured.

Cause: The default auth provider was not configured.

Action: Ensure that the provider is configured in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-02060: The auth module "{0}" is missing.

Cause: The specified auth module did not exist.

Action: Configure the auth module in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02061: No auth module configured for provider "{0}".

Cause: No auth module configured for the specified provider.

Action: Configure an auth module for the provider in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02062: Cannot determine the JDK vendor. Defaults to Oracle JDK Kerberos Login Module.

Cause: Cannot determine the JDK vendor. Defaults to Oracle JDK Kerberos Login Module.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-02063: Failed to create Kerberos Login Module instance "{0}". Reason: {1}.

Cause: Failed to create Kerberos Login Module instance "{0}". Reason: {1}.

Action: Ensure that the Login Module class name is correctly supplied and the class is in the class path.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02064: Cannot retrieve value for key {0}. Expecting key type {1}, found {2}.

Cause: Found invalid object type in role mapping map for key {0}. Expecting {1}, Found {2}.

Action: Check the role mapping values passed in the callback.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02066: Cannot map default service role

Cause: default service roles are missing in the role mapping provided.

Action: Check the role mapping values passed in the callback. Default service role should be provided if mapping of roles is enabled but mapping is not provided
Level: 1

Type: ERROR

Impact: Configuration

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, OUD, 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. Reason: {1}.

Cause: Enterprise user principal "{0}" cannot be created.

Action: Ensure the user principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02589: Enterprise role principal "{0}" cannot be created. Reason: {1}.

Cause: Enterprise role principal "{0}" cannot be created.

Action: Ensure the role principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-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-02601: Failed to get Ovd virtualization service for service instance "{0}" in JPS context "{1}", cause: {2}

Cause: Failed to get Ovd virtualization service for service instance "{0}" in JPS context "{1}", cause: {2}

Action: Check Ovd log for more details.
Level: 1

Type: ERROR

Impact: Security

JPS-03000: Cannot instantiate permission class "{0}", target "{1}", or actions "{2}" as defined in the application policy context "{3}". Cause {4}

Cause: Could not load a permission class.

Action: Ensure that the class name is correct and available in the current class loader.
Level: 1

Type: WARNING

Impact: Security

JPS-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-03029: Unable to Notify to external Application:{0} Refresh Event. Reason {1}

Cause: Unable to Notify to external Appliacation Refresh Event.

Action: Check the logs for more information to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03030: Catch exception in PDP registration, will retry later.

Cause: Catch exception in PDP registration, retry later.

Action: check the exception details and retry
Level: 1

Type: WARNING

Impact: Configuration

JPS-03031: Catch InterruptedException in PDP registration. Registration failed.

Cause: Catch InterruptedException in PDP registration. Registration failed

Action: check the exception details and retry
Level: 1

Type: ERROR

Impact: Configuration

JPS-03032: Can not access PD server web service during PDP registration, will retry later.

Cause: PD Server web service not available, retry later.

Action: wait retry to access to PD Server web service
Level: 1

Type: WARNING

Impact: Configuration

JPS-03033: Can not access PD client web service during PDP registration, will retry later.

Cause: PD client web service not available, retry later.

Action: wait retry to access to PD client web service
Level: 1

Type: WARNING

Impact: Configuration

JPS-03034: Policystore is not ready on admin server during PDP registration, will retry later.

Cause: Policystore isn't available from admin server, retry later.

Action: wait retry accessing policystore
Level: 1

Type: WARNING

Impact: Configuration

JPS-03035: PDP registration succeeded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-03036: No PDP Service is found in JPS Context {1}

Cause: PDPService service instance is not found in JPS Context.

Action: Configure a PDPService service instance in JPS Context
Level: 1

Type: ERROR

Impact: Configuration

JPS-03037: Exception happened during PDP initialization.

Cause: Exception happened during PDP Initialization

Action: check the exception details and retry
Level: 1

Type: ERROR

Impact: Configuration

JPS-03038: Unable to find PolicyStore or Schema Version. Check farm name and root name of policystore service instance in OPSS configuration file.

Cause: Unable to find PolicyStore or Schema Version.

Action: Check farm name and root name of policystore service instance in OPSS configuration file
Level: 1

Type: ERROR

Impact: Configuration

JPS-03039: Exception {0} happened during Policystore agent processing message {1}, the message will be ignored.

Cause: Exception happened during PolicyStore agent processing

Action: check the exception details and retry
Level: 1

Type: ERROR

Impact: Configuration

JPS-03040: Subject resolver cache initiation failed.

Cause: Subject resolver cache initiation failed.

Action: Make sure all jars are included in the classpath.
Level: 1

Type: ERROR

Impact: Security

JPS-03041: Subject resolver cache property, key: {0}, value: {1} is not valid.

Cause: Subject resolver cache property, key: {0}, value: {1} is not valid.

Action: Check pdp service configuration.
Level: 1

Type: ERROR

Impact: Security

JPS-03042: PDP Service property, key: {0}, value: {1} is not valid, use default value: {2}.

Cause: PDP Service property, key: {0}, value: {1} is not valid, use default value: {2}.

Action: Check pdp service configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-03043: Configuration property, key: {0}, value: {1} is not valid, use default value: {2}.

Cause: Configuration property, key: {0}, value: {1} is not valid, use default value: {2}.

Action: Check pdp service configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-03044: Mandatory property {0} of PDP service is missing.

Cause: Mandatory property of PDP service is missing.

Action: provide the required property
Level: 1

Type: ERROR

Impact: Configuration

JPS-03045: Can not clean application : {0} from runtime cache. Reason:mode : {1} it is not non-controlled mode or not non-bound application in mixed mode.

Cause: Can not clean application : {0} from runtime cache. Reason: mode : {1} it is not non-controlled mode or not non-bound application in mixed mode.

Action: Check pdp service configuration.
Level: 1

Type: ERROR

Impact: Security

JPS-03046: Application {0} is not found when being preloaded.

Cause: Application {0} is not found when being preloaded.

Action: Please check policy store, application might have been deleted.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-03047: Upsupported preload key type {0} with condition 'oracle.security.jps.policystore.policy.lazy.load.enable' being {1} .

Cause: Upsupported preload key type {0} with condition 'oracle.security.jps.policystore.policy.lazy.load.enable' being {1}

Action: Please check the preload key and the configuration parameters for PDP service.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-03048: Unable to remove application {0} from runtime cache, due to {1}

Cause: Unable to remove application {0} from runtime cache, due to {1}

Action: Check full stacktrace
Level: 1

Type: ERROR

Impact: Security

JPS-03150: Error during setting the field of a provider MBean. {0}

Cause: Error during setting the field of a provider MBean. {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03151: getSecurityService returning null for requested service type of {0} for realm {1}

Cause: getSecurityService returning null for requested service type of {0} for realm {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-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:==> {0}

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-03273: Application {0} attribute {1} is not available.

Cause: Application {0} attribute {1} is not available.

Action: None.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-04000: Cannot get the default policy store.

Cause: Could not find to the default policy store.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-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-04006: No results found for given Application Name:{0}, DN: {1}, Query: {2}.

Cause: No results found for application name.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04021: Application Policy "{0}" already exists.

Cause: Encountered two application policy contexts with identical names.

Action: Modify an application policy context to have a distinct name.
Level: 1

Type: WARNING

Impact: Security

JPS-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 or empty.

Cause: Supplied parameter {0} was null or empty.

Action: Verify that the supplied parameter is non-null. If it is of type String, ensure that its length is positive.
Level: 1

Type: WARNING

Impact: Security

JPS-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. Further migration of application policies halted. Reason: {0}.

Cause: Exception in migration of application policy

Action: Check application policy setup or contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-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: Application Role "{0}" already exists.

Cause: Encountered two roles with identical names.

Action: Modify a role to have a distinct name.
Level: 1

Type: WARNING

Impact: Security

JPS-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 "{0}".

Cause: Could not find application role in the application policy context.

Action: Ensure the application role is present in the application policy.
Level: 1

Type: WARNING

Impact: Security

JPS-04122: Cannot add principal to application role; principal(s) "{0}" is already a member of application role "{1}".

Cause: Found that principal {0} is already a member of the application role {1}.

Action: Correct the principal name.
Level: 1

Type: WARNING

Impact: Security

JPS-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-04135: Resource name not specified in application {0}.

Cause: Resource name not specified in application {0}.

Action: Ensure the resource name is not null.
Level: 1

Type: WARNING

Impact: Security

JPS-04136: Resource type name not specified in application {0}.

Cause: Resource type name not specified in application {0}.

Action: Ensure the resource type name is not null.
Level: 1

Type: WARNING

Impact: Security

JPS-04137: Permission set name not specified in application {0}.

Cause: Permission set name not specified in application {0}.

Action: Ensure the permission set name is not null.
Level: 1

Type: WARNING

Impact: Security

JPS-04138: Application role name not specified in application {0}.

Cause: Application role name not specified in application {0}.

Action: Ensure the application role name is not null.
Level: 1

Type: WARNING

Impact: Security

JPS-04140: Cannot complete application role search because search expression "{0}" is incorrect.

Cause: Found an invalid search pattern.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-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} in policy store.

Cause: Could not find PermissionSet in policy store.

Action: Provide the name of a valid PermissionSet.
Level: 1

Type: WARNING

Impact: Security

JPS-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: MemberResource {0} of type {1} not found in application {1}.

Cause: MemberResource {0} of type {1} not found in application {1}.

Action: Ensure the Resource exists in the PolicyStore.
Level: 1

Type: WARNING

Impact: Security

JPS-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 {0} in application {1} has a non existent resource type {2}. Ignoring this resource.

Cause: Resource {0} in application {1} has a non existent resource type {2}. Ignoring this resource.

Action: Ensure the ResourceType exists for every resource.
Level: 1

Type: WARNING

Impact: Security

JPS-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-04223: Access to tenant system policy is not allowed.

Cause: Access to tenant system policy is not allowed.

Action: Access global system policy instead.
Level: 1

Type: WARNING

Impact: Security

JPS-04227: The object name "{0}" is invalid.

Cause: The object name {0} is invalid.

Action: Pass a correct object name in.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-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-04305: Could not determine the work folder for controlled and mixed mode PD.

Cause: Could not determine the work folder for controlled and mixed mode PD.

Action: Ensure system property "oracle.security.jps.config" or "domain.home" is set and jps-config.xml is present under ${domain.home}/config/fmwconfig.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04410: Cannot create JACC module policy context "{0}" for application {1}.

Cause: Could not create application policy because found two application module contexts with identical names.

Action: Ensure that all application module context names are distinct.
Level: 1

Type: WARNING

Impact: Security

JPS-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-05657: Bootstrap credential store context {0} missing

Cause: Could not find bootstrap credential store context

Action: Contact aystem administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-05658: Bootstrap credential store service {0} missing from bootstrap credential store context {1}

Cause: Could not find bootstrap credential store service

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-05659: location attribute missing from bootstrap credential store service {0}

Cause: Could not find location attribute of bootstrap credential store service

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-06000: The source context {0} is missing in jps configuration file.

Cause: While migrating a security store, found that the context, specified as source {0}, did not exist in jps-config.xml.

Action: Provide a context for source that is present in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06001: The destination context {0} is missing in jps configuration file.

Cause: While migration of a security store, found that the context, specified as destination {0}, did not exist in jps-config.xml.

Action: Provide a context for destination that is present in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-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: {0}.

Cause: Invalid value for mode: {0}.

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-06092: Can not overwrite global policy.

Cause: Can not overwrite global policy.

Action: Do not set overwrite to true
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06100: Policy Store version {0} and Oracle Platform Security Services Version {1} are not compatible.

Cause: The policy store version and the version of Oracle Platform Security Services does not match

Action: Upgrade your binaries or your policy store.
Level: 1

Type: ERROR

Impact: Security

JPS-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 leates version and need to be upgraded

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-06104: Default Admin Role {0} not found in the application {1} in the destination policy store

Cause: The destination policy store may not conform to leates version and need to be upgraded

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-06105: Default system Admin Role {0} not found in the destination policy store

Cause: The destination policy store may not conform to leates 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-06120: Policystore is already upgraded, so it will not be upgraded again.

Cause: Policystore is already upgraded.

Action: Policystore will not be upgraded again.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06121: Keystore is already upgraded, so it will not be upgraded again.

Cause: Keystore is already upgraded.

Action: Keystore will not be upgraded again.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06122: Auditstore is already upgraded, so it will not be upgraded again.

Cause: Auditstore is already upgraded.

Action: Auditstore will not be upgraded again.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06123: XACML Policy/PolicySet Defaults not supported in OES.

Cause: XACML Policy/PolicySet Defaults not supported in OES.

Action: XACML Policy/PolicySet Defaults not supported in OES.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06124: XACML Policy/PolicySet Max Delegation Depth not supported in OES.

Cause: XACML Policy/PolicySet Max Delegation Depth not supported in OES.

Action: XACML Policy/PolicySet Max Delegation Depth not supported in OES.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06125: XACML attribute Issuer not supported in OES for the element {0}.

Cause: XACML attribute Issuer not supported in OES.

Action: XACML attribute Issuer not supported in OES.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06126: XACML PolicySet/Policy/Rule Combiner Parameters not supported in OES.

Cause: XACML Policy/Rule Combiner Parameters not supported in OES.

Action: XACML Policy/Rule Combiner Parameters not supported in OES.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06127: XACML Attribute Selector not supported in OES.

Cause: XACML Attribute Selector not supported in OES.

Action: XACML Attribute Selector not supported in OES.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06128: Unknown Policy/PolicySet Id reference {0}.

Cause: Unknown Variable reference.

Action: Provide an Id Reference of a Policy/PolicySet that exists in the application
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06129: Unknown Variable reference {0}.

Cause: Unknown Policy/PolicySet Id reference.

Action: Provide a variable Reference for which a vadiable definition exists in the policy
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06131: Migration of Audit Store data in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06132: Migration of Audit Store data completed, Time taken for migration is {0}

Cause: Migration of Audit Store data completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06133: Migration of Credential Store data in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06134: Migration of Credential Store data completed, Time taken for migration is {0}

Cause: Migration of Credential Store data completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06135: Migration of Credential folder data in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06136: Migration of Credential folder data completed, Time taken for migration is {0}

Cause: Migration of Credential folder data completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06137: Migration of Application Policies {0} in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06138: Migration of Application Policies {0} completed, Time taken for migration is {1}

Cause: Migration of Application Policies {0} completed, Time taken for migration is {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06139: Migration of Global Policies in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06140: Migration of Global Policies completed, Time taken for migration is {0}

Cause: Migration of System Policies completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06141: Migration of All[Application + Global] policies in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06142: Migration of All[Application + Global] policies completed, Time taken for migration is {0}

Cause: Migration of All[Application + Global] policies completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06143: Migration of Java Policies in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06144: Migration of Java Policies completed, Time taken for migration is {0}

Cause: Migration of Java Policies completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06145: Migration of Identity Store data in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06146: Migration of Identity Store data completed, Time taken for migration is {0}

Cause: Migration of Identity Store data completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06147: Migration of Admin Role Members started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06148: Migration of {0} Admin Role Members completed in {1}

Cause: Migration of {0} Admin Role Members completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06149: Migration of Grants started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06150: Migration of {0} Grants completed in {1}

Cause: Migration of {0} Grants completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06151: Migration of Policy Domains started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06152: Migration of {0} Policy Domains completed in {1}

Cause: Migration of {0} Policy Domains completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06153: Migration of Application Roles started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06154: Migration of {0} Application Roles completed in {1}

Cause: Migration of {0} Application Roles completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06155: Migration of Resources started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06156: Migration of {0} Resources completed in {1}

Cause: Migration of {0} Resources completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06157: Migration of Admin Roles started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06158: Migration of {0} Admin Roles completed in {1}

Cause: Migration of {0} Admin Roles completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06159: Migration of Policies started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06160: Migration of {0} Policies completed in {1}

Cause: Migration of {0} Policies completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06161: Migration of Resource Types started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06162: Migration of {0} Resource Types completed in {1}

Cause: Migration of {0} Resource Types completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06163: Migration of Permission Sets started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06164: Migration of {0} Permission Sets completed in {1}

Cause: Migration of {0} Permission Sets completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06165: Migration of Functions started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06166: Migration of {0} Functions completed in {1}

Cause: Migration of {0} Functions completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06167: Migration of Attributes started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06168: Migration of {0} Attributes completed in {1}

Cause: Migration of {0} Attributes completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06169: Migration of Role Policies started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06170: Migration of {0} Role Policies completed in {1}

Cause: Migration of {0} Role Policies completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06171: Failed to create policy store object, please check the logs.

Cause: Failed to create policy store object, please check the logs.

Action: Please check the logs.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06172: {0} service not found in default context, skipping upgrade for this service.

Cause: {0} service not found in default context of OPSS configuration

Action: Configure {0} service in default context of OPSS configuration files and run the upgrade again
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06173: Policystore upgrade from {0} to {1} not supported

Cause: Policystore upgrade from {0} to {1} not supported

Action: Policystore must be upgraded to a higher patchset first.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06174: OPSS data is not backed up as part of upgrade process in LDAP/DB based OPSS Store

Cause: OPSS data is not backed up as part of upgrade process in LDAP/DB based OPSS Store

Action: Back up data manually before running upgrade in LDAP/DB based OPSS Store.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06175: Migration of CombiningAlgorithms started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06176: Migration of {0} CombiningAlgorithms completed in {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06177: Migration of Policy Rule started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06178: Migration of {0} Policy Rule completed in {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06179: Migration of Policy Set started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06180: Migration of {0} Policy Set completed in {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06181: Migration of Key Store data in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06182: Migration of Key Store data completed, Time taken for migration is {0}

Cause: Migration of Key Store data completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06183: Migration of Key Store stripe data in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06184: Migration of Key Store stripe data completed, Time taken for migration is {0}

Cause: Migration of KeyStore stripe data completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06185: More than one properties set references present for policy store service instance in jps-config file {0}

Cause: More than one property set references present in policy store service instance in jps-config.xml file

Action: Make sure only one property set references under policy store service instance in jps-config.xml file
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06186: Either bootstrap credstore or key store service instance is not found in bootstrap context

Cause: Either bootstrap credstore or key store service instance is not found in bootstrap context

Action: Ensure both bootstrap credstore and keystore service instance reference in bootstrap context is present
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06187: Not able to find file based keystore service instance, while adding keystore service instance to bootstrap context

Cause: Not able to find file based keystore service instance, while adding keystore service instance to bootstrap context

Action: Ensure file based keystore service instance reference in jps-config.xml is present
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06188: New Application Policy {0} created during migration

Cause: Migration of Application Roles completed in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06189: Migrate Permission Name = {0}, Exception during modification of permission. Message = {1}.

Cause: Migrate Permission Name = {0}, Exception during modification of permission. Message = {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06190: Miagrtion failed in Perm Member : {0}.

Cause: Miagrtion failed in Perm Member : {0}

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06191: PermissionMigrator Thread {0} failed due to {1}.

Cause: PermissionMigrator Thread {0} failed due to {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06192: Cannot get source policy store.

Cause: While migrating a security store, cannot get source policy store.

Action: Check and make sure source policy store is configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06193: Cannot get destination policy store.

Cause: While migrating a security store, cannot get destionation policy store.

Action: Check and make sure destination policy store is configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06194: There are multiple logic security stores in the db schema : {0}. Please split them before doing upgrade.

Cause: Found multiple security stores in the db schema.

Action: Reassociate each security store to separated db schema.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06195: Security store is already transformed, so it will not be transformed again.

Cause: Security store is already transformed.

Action: Security store will not be transfromed again.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06196: Transformation of security store started.

Cause: Begin security store transformation.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06197: Transformation of security store completed in {0}.

Cause: Finish security store transformation.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06198: OPSS Schema is not upgraded. Current schema version is {0}. Schema version for upgrade is {1}

Cause: OPSS Schema is not upgraded.

Action: Upgrade OPSS Schema first before upgrading Opss Data and Config.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06199: Source application type dose not match the type of destination application.

Cause: Source application type dose not match the destination application type.

Action: No actions are required.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06200: Property {0} with value "{1}" is invalid in the meta data property file.

Cause: Property {0} with value "{1}" is invalid in the meta data property file.

Action: Check the meta data property file.
Level: 1

Type: ERROR

Impact: Security

JPS-06201: Property {0} is missing in the meta data property file.

Cause: Property {0} is missing in the meta data property file.

Action: Check the meta data property file.
Level: 1

Type: ERROR

Impact: Security

JPS-06202: Cannot migrate {0} named "{1}", policy object already exists in application policy with different metadata.

Cause: {0} named "{1}" already exists in application policy with differnt metadata.

Action: Check policy store data in source application policy, remove conflict data.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06500: Alias already exists in the keystore

Cause: The specified alias name already existed in the keystore.

Action: Specify a unique alias name.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06501: Keystore {0} in stripe {1} already exists

Cause: Keystore with the given name already existed.

Action: Specify a unique keystore name.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06502: Failed to read keystore. Reason {0}

Cause: Could not read the keystore.

Action: Verify the keystore location and that sufficient permissions are in place.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06503: Failed to write keystore. Reason {0}

Cause: Could not read the keystore.

Action: Verify the keystore location, that sufficient permissions are in place and that sufficient disk space is available.
Level: 1

Type: WARNING

Impact: Configuration

JPS-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 :

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06514: Opening of file based keystore failed. Reason :

Cause: Keystore could not be opened

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-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 with map {0} and key {1} in bootstrap credstore. Reason {2}

Cause: Credential store was not available or permissions were not in place.

Action: Verify credential store is correctly configured and permissions are granted.
Level: 1

Type: WARNING

Impact: Configuration

JPS-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}" either does not exist or is not of the specified keystore entry type for keystore "{1}" in stripe "{2}".

Cause: The alias value either did not exist or did not point to the specified keystore entry type.

Action: Specify a valid alias value that points to the specified keystore entry type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-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}. Reason {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06561: Failed to export the keystore {0} in stripe {1}. Reason {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-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. Reason {0}

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 as the public key in the certificate did not match the one in the keystore.

Cause: The public key in the certificate does not match the one in the keystore.

Action: Ensure that the certificate is imported into the alias used for generating certificate request.
Level: 1

Type: WARNING

Impact: Configuration

JPS-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: Operation not supported - unable to delete key store {0} in stripe {1}.

Cause: Deletion of domain trust store or the demo CA key store was not permitted.

Action: Choose a different key store.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06615: Operation not supported - unable to delete alias {0} in key store {1} in stripe {2}.

Cause: Deletion of demo CA key was not permitted.

Action: Choose a different key alias.
Level: 1

Type: WARNING

Impact: Configuration

JPS-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. Location: {0}

Cause: File keystore.xml has been manually edited.

Action: Restore the keystore file to the last working backup and try again.
Level: 1

Type: WARNING

Impact: Configuration

JPS-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-06623: Invalid KSS URI: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06624: Cannot synchronize centralized key store(s) from stripe {0} to bootstrap key store(s). Reason {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-06625: Invalid component type {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-06626: Could not get bootstrap key store service. Reason {0}

Cause: Could not get bootstrap key store service.

Action: Verify key store service is correctly configured and initialized.
Level: 1

Type: WARNING

Impact: Compliance

JPS-06627: Invalid keystore provider type. Value {0}

Cause: Value of keystore.provider.type is invalid.

Action: Assign a valid value to keystore.provider.type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06628: Key alias {0} corresponds to neither a key nor a trusted certificate in the imported keystore.

Cause: Given key alias corresponds to neither a key nor a trusted certificate.

Action: Given key alias should correspond to either a key or a trusted certificate.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06629: No alias specified so skipping import/export

Cause: Key aliases should not be null or empty string.

Action: Ensure that key aliases are neither null nor empty string.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06630: Import of entry with alias: {0} into appStripe:{1} keystore:{2} skipped as it already exists in the keystore.

Cause: Alias already exists in the keystore. Alias overwriting while importing not supported.

Action: Alias to be imported shouldn't pre-exist in the key store.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06631: Certificate import failed as the minimum number of certificates expected is {0}

Cause: K required were not given.

Action: Ensure that minimum number of certificates are imported.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06632: Invalid key store attribute {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06633: Cannot synchronize component key store(s) under stripe {0} into corresponding wallets. Reason {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-06634: One or more of keystores inside application stripe {0} are not permission protected.

Cause: One or more of keystores inside the application stripe are not permission protected.

Action: Ensure that all keystores in the application stripe are permission protected.
Level: 1

Type: WARNING

Impact: Compliance

JPS-06635: Either or both of stripe name {0} and keystore format {1} is null or empty string.

Cause: Either or both of stripe name and keystore format is null or empty string.

Action: Ensure that stripe name and keystore format are both non-empty string.
Level: 1

Type: WARNING

Impact: Compliance

JPS-06636: Application stripe {0} does not exist in keystore.

Cause: Given application stripe doesn't exist in keystore.

Action: Provide name of an application stripe that is already existing in keystore.
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06637: Trusted certificate with Subject DN {0} is missing from trust store of keystore.

Cause: A trusted certificate is missing from trust store of keystore.

Action: Ensure that the trusted certificate is present in trust store of keystore.
Level: 1

Type: WARNING

Impact: Compliance

JPS-06638: KeyStore Entry required were not given.

Cause: KeyStore Entry required were not given.

Action: Provide KeyStore Entry as input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06639: The following aliases were encountered in the keystore: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06640: Empty alias specified for importing wallet keystore, so skipping import

Cause: Key aliases of wallet keystore to import should not be empty string.

Action: Ensure that key aliases of wallet keystore to import are not empty string.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06641: Invalid keySize format : {0}

Cause: Cannot set key entry for non-existent stripe and keystore

Action: This operation is not supported
Level: 1

Type: WARNING

Impact: Compliance

JPS-06642: Can not determine the JAVA/JRE home,so could not find the cacerts file.

Cause: Neither environnment variable JAVA_HOME nor system property java.home is specified.

Action: Ensure that either environnment variable JAVA_HOME or system property java.home is specified.
Level: 1

Type: WARNING

Impact: Compliance

JPS-06643: JDK cacerts file {0} in use.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06644: Failed to import JDK cacerts to system/publiccacerts.

Cause: Importing JDK CA cert failed.

Action: check log for more details.
Level: 1

Type: WARNING

Impact: Compliance

JPS-06645: JDK cacerts {0} does not exist.

Cause: JDK cacerts file {0} does not exist.

Action: Check the location of JDK cacerts files.
Level: 1

Type: WARNING

Impact: Compliance

JPS-06646: Private or Secret key found in Trust Store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06647: Aggregation of two trust stores failed

Cause: There is a private or secret key entry in the truststore

Action: Remove the private or secret key entries from the truststore
Level: 1

Type: WARNING

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: Policy store doesn't suport metadata

Action: Update policy store
Level: 1

Type: ERROR

Impact: Security

JPS-07055: Policy entry is null.

Cause: {0} Policy entry is null.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

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: Addition Safe changes and Modification Safe changes have been applied.However, Deletion conflicts are not resolved.

Action: Resolve deletion conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-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-07081: Could not find policystore in "{0}" jps context in production config.

Cause: Could not find policystore in {0} jps context in production config.

Action: Provide a service instance for policystore in the {0} jps context in production config.
Level: 1

Type: ERROR

Impact: Security

JPS-07082: Loading base policy store complete in {0}.

Cause: Loading base policy store complete in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07083: Initializing Application Policy Comparator complete in {0}.

Cause: Initializing Application Policy Comparator complete in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07084: Loading new policy store complete in {0}.

Cause: Loading new policy store complete in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07085: Oracle Delta calculation complete in {0}.

Cause: Oracle Delta calculation complete in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07086: Production application policy store object created in {0}.

Cause: Production application policy store object created in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07087: Customer delta created in {0}.

Cause: Customer delta created in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07088: Patch delta created in {0}.

Cause: Patch delta created in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07089: Report File created in {0}.

Cause: Report file created in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07090: Customer delta files created in {0}.

Cause: Customer delta files created in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07093: The Role category object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Enusre to provide a valid RoleCategory Object.
Level: 1

Type: ERROR

Impact: Security

JPS-07101: Beginning to apply additions...

Cause: Beginning to apply additions...

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07102: Additions applied in {0}

Cause: Additions applied in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07103: Beginning to apply modifications...

Cause: Beginning to apply modifications...

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07104: Modifications applied in {0}

Cause: Modifications applied in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07105: Beginning to apply deletions...

Cause: Beginning to apply deletions...

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07106: Deletions applied in {0}

Cause: Deletions applied in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07107: {0} Application roles added.

Cause: {0} Application roles added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07108: {0} Role categories added.

Cause: {0} Role categories added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07109: {0} Resource type entries added.

Cause: {0} Resource type entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07110: {0} Resource entries added.

Cause: {0} Resource entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07111: {0} Permission set entries added.

Cause: {0} Permission set entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07112: {0} Application role membership entries added.

Cause: {0} Application role membership entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07113: {0} Application role categories entries added.

Cause: {0} Application role categories entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07114: {0} Resources to permission sets added.

Cause: {0} Resources to permission set entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07115: {0} Permission set membership entries added.

Cause: {0} Permission set membership entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07116: {0} Grantee to permission set entries added.

Cause: {0} Grantee to permission set entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07117: {0} Grantee to permission membership entries added.

Cause: {0} Grantee to permission membership entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07118: {0} Application roles modified.

Cause: {0} Application roles modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07119: {0} Role categories modified.

Cause: {0} Role categories modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07120: {0} Resource type entries modified.

Cause: {0} Resource type entries modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07121: {0} Resource entries modified.

Cause: {0} Resource entries modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07122: {0} Permission set entries modified.

Cause: {0} Permission set entries modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07123: {0} Resources to permission sets added.

Cause: {0} Resources to permission set entries modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07124: {0} Grantee to permission membership entries modified.

Cause: {0} Grantee to permission membership entries modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07125: Dissociated {0} members from application roles.

Cause: Deassociated {0} members and application roles.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07126: Dissociated {0} categories from application roles.

Cause: Deassociated {0} categories and application roles.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07127: Dissociated {0} resources from permission sets.

Cause: Deassociated {0} resources and permission sets.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07128: Revoked {0} permission sets from grantees.

Cause: Revoked {0} permission sets from grantees.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07129: Revoked {0} permissions from grantees.

Cause: Revoked {0} permissions from grantees.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07130: {0} Application roles deleted.

Cause: {0} Application roles deleted.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07131: {0} Role categories deleted.

Cause: {0} Role categories deleted.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07132: {0} Permission set entries deleted.

Cause: {0} Permission set entries deleted.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07133: {0} Resource entries deleted.

Cause: {0} Resource entries deleted.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07134: {0} Resource type entries deleted.

Cause: {0} Resource type entries deleted.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07135: Progress - Apply Additions ----------------------- {0}% Done

Cause: Progress...Apply additions

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07136: Progress - Apply Modifications -------------------- {0}% Done

Cause: Progress...Apply modifications

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07137: Progress - Apply Deletions ----------------------- {0}% Done

Cause: Progress...Apply deletions

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07138: Dissociated of members from application roles (skipped, not applicable).

Cause: Dissociation of members from application roles (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07139: Dissociation of categories from application roles (skipped, not applicable)

Cause: Disassociation of categories from application roles (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07140: Dissociation of resources from permission sets (skipped, not applicable).

Cause: Disassociation of resources from permission sets (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07141: Revoke of permission sets from grantees (skipped, not applicable).

Cause: Revoke of permission sets from grantees (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07142: Revoke of permissions from grantees (skipped, not applicable).

Cause: Revoke of permissions from grantees (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07143: Application roles deletion (skipped, not applicable).

Cause: Deletion of application roles (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07144: Role categories deletion (skipped, not applicable).

Cause: Deletion of role categories (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07145: Permission set entries deletion (skipped, not applicable).

Cause: Deletion of permission sets (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07146: Resource entries deletion (skipped, not applicable)

Cause: Deletion of resources (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07147: Resource type entries deletion (skipped, not applicable).

Cause: Deletion of resource types (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07148: Deletions not applicable when the silent flag is on.

Cause: Deletions not applicable when the silent flag is enabled

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07150: You can set only one of the two flags - {0} or {1} but not both.

Cause: Dual flags have been set. This is not permitted

Action: Set only one of the two flags - {0} or {1}
Level: 1

Type: ERROR

Impact: Security

JPS-07151: role member {0} of application role: {1} not found.

Cause: role member {0} of application role: {1} not found

Action: Add back role member: {0} or run patching analysis again
Level: 1

Type: ERROR

Impact: Security

JPS-07152: Name collisions have been identified. The patch process halted. Eliminate the collisions by renaming or removing artifacts in production store. Please find artifacts which have name collision between production store and patch version in file {0}.

Cause: Name collisions exist.

Action: Eliminate the name collisions by renaming or removing the policy artifacts in production store.
Level: 1

Type: ERROR

Impact: Security

JPS-07156: {0} Policy rule entries were added.

Cause: {0} Policy rule entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07157: {0} Policy entries were added.

Cause: {0} Policy entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07158: {0} Policy to permission set entries added.

Cause: {0} Policy to permission set entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07159: {0} Policy to policy rule entries were added.

Cause: {0} Policy to policy rule entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07160: {0} Policy to grantee entries added.

Cause: {0} Policy to grantee entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07161: {0} Policies entries were modified.

Cause: {0} Policies entries modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07162: {0} Policy rules entries were modified.

Cause: {0} Policy rules entries modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07163: {0} Policy rules were deleted from policies.

Cause: Deleted {0} policy rules from policies.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07164: {0} Principals were deleted from policy.

Cause: Deleted {0} principals from policy.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07165: {0} Permission Sets were deleted from policy.

Cause: Deleted {0} Permission Set from policy.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07166: {0} Policy entries were deleted.

Cause: {0} Policy entries deleted.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07167: {0} Policy rule entries were deleted.

Cause: {0} Policy rule entries deleted.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07168: Policy rule entry is null.

Cause: {0} Policy rule entry is null.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07169: Delta between patch jazn-data and production policystore was written to report in {0}.

Cause: Delta between patch jazn-data and production policystore was written to report in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07170: Delta between patch jazn-data and production policystore was calculated in {0}.

Cause: Delta between patch jazn-data and production policystore was calculated in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07171: Privilege changes of user or group report between baseline jazn-data and production policystore was created in {0}.

Cause: User or group's privilege changes report between baseline jazn-data and production policystore was created in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07172: Delta between production and baseline jazn-data was validated in {0}.

Cause: Policy customization between production and baseline jazn-data was validated in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07173: Enterprise role privilege changes between production and baseline jazn-data was validated in {0}.

Cause: Enterprise user or role privilege changes between production and baseline jazn-data was validated in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07174: Enterprise user or role privilege validation failed for record: {0}.

Cause: Enterprise user or role privilege validation failed for record

Action: Check the usergroup-privilege-validate-result file for more details
Level: 1

Type: WARNING

Impact: Security

JPS-07175: Policy change validation failed for record: {0}.

Cause: Policy change validation failed for record

Action: Check the policy-validate-result file for more details
Level: 1

Type: WARNING

Impact: Security

JPS-07176: Patch jazn data file {0} will be ignored since this is forceTag mod.

Cause: Patch jazn data file {0} will be ignored since this is forceTag mod.

Action: No action
Level: 1

Type: WARNING

Impact: Security

JPS-07177: Patch application policy name {0} will be ignored since this is forceTag mod.

Cause: Patch application policy name {0} will be ignored since this is forceTag mod.

Action: No action
Level: 1

Type: WARNING

Impact: Security

JPS-07178: Patch delta folder {0} will be ignored since this is forceTag mod.

Cause: Patch delta folder {0} will be ignored since this is forceTag mod.

Action: No action
Level: 1

Type: WARNING

Impact: Security

JPS-07179: Tagging {0} {1} completed in {2}.

Cause: Tagging {0} {1} completed in {2}.

Action: No action
Level: 1

Type: NOTIFICATION

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-07545: Invalid TokenContext class

Cause: Internal Error. The correct TokenContext class is not created.

Action: Provide the correct TokenProvider class in trust configurations.
Level: 1

Type: ERROR

Impact: Security

JPS-07546: Token cannot be issued for virtual or anonymous user

Cause: Trust token cannot be issued for anonymous or virtual users

Action: Ensure usage of Trust service is limited to users present in configured identity store.
Level: 1

Type: ERROR

Impact: Security

JPS-07600: Application policy for stripe name {0} not found. Nothing to undeploy

Cause: No associated application policies

Action: Check application policy setup or contact system administrator
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07601: Complete staging offline deployment for application {0} in {1}

Cause: Complete staging offline deployment for application {0} in {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07602: Removal of application policy failed. Reason: {0}.

Cause: Exception in removing application policy

Action: Check application policy setup or contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-07603: Cannot purge changelog. Reason {0}.

Cause: Purge changelog failed.

Action: Check policystore configuration.
Level: 1

Type: ERROR

Impact: Security

JPS-07604: Wrong policy combining algorithm name {0} is used.

Cause: wrong policy combining algorithm name was used

Action: Check combining algorithm name being used
Level: 1

Type: WARNING

Impact: Security

JPS-07605: Unsupported policy combining algorithm name {0} is used.

Cause: Unsupported policy combining algorithm name was used

Action: Check combining algorithm name being used
Level: 1

Type: WARNING

Impact: Security

JPS-07606: Cannot clean applications. Reason {0}.

Cause: Clean applications failed.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-07607: {0} is used in source, but it is not supported by destination policy store.

Cause: Source contains policy artifacts that is not supported by destination policy store

Action: Make sure source only contain policy artifacts which are compatible with destination policy store
Level: 1

Type: WARNING

Impact: Security

JPS-08000: Subject object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Subject.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-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-08019: Requested operation is not supported.

Cause: Requested operation is not supported.

Action: Do not invoke unsupported operation.
Level: 1

Type: ERROR

Impact: Security

JPS-08020: The authorization service instance is invalid.

Cause: The authorization service instance is invalid.

Action: Check the service instance and ensure that is a supported authorization service instance.
Level: 1

Type: ERROR

Impact: Security

JPS-08021: The input configuration parameter is invalid.

Cause: The input configuration parameter is invalid.

Action: Check the configuration parameter validity.
Level: 1

Type: ERROR

Impact: Security

JPS-08022: Incorrect authorization service instance type.

Cause: Incorrect authorization service instance type.

Action: Check the authorization service instance type.
Level: 1

Type: ERROR

Impact: Security

JPS-08023: The environment parameter is missing.

Cause: The environment paramater is missing.

Action: Check the environment paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08024: Policy context parameter is missing.

Cause: Policy context parameter is missing.

Action: Check the policy context paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08025: Session context parameter is missing.

Cause: Session context parameter is missing.

Action: Check the session paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08026: Database connection parameter is missing.

Cause: Database connection parameter is missing or not a right type.

Action: Check the database connection paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08027: Security predicate parameter is missing.

Cause: Security predicate parameter is missing.

Action: Check the security predicate paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08028: Cannot find appName attribute in resource collection.

Cause: Can't find appName attribute in resource collection.

Action: Add appName attribute to resource collection.
Level: 1

Type: ERROR

Impact: Security

JPS-08029: Privilege parameter is missing or not a right type

Cause: Privilege parameter is missing or not a right type.

Action: Check the privilege paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08030: DB object parameter is missing or not a right type.

Cause: DB object parameter is missing or not a right type.

Action: Check the DB object paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08031: Client env parameter is not a right type.

Cause: Client env parameter is not a right type.

Action: Check the client env paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08032: Client env parameter has unsupported value.

Cause: Client env parameter has unsupported value.

Action: Check the client env paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08033: Check privilege mode parameter has unsupported value.

Cause: Check privilege mode parameter has unsupported value.

Action: Check the Check privilege paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08034: Value of parameter {0} should be type {1}, but has a wrong type {2}.

Cause: Invalid parameter type

Action: Check the paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08035: Type of RAS parameter value is not supported.

Cause: Type of RAS parameter value is not supported.

Action: Do not use unsupported type for RAS parameter value.
Level: 1

Type: ERROR

Impact: Security

JPS-08036: Invalid data type in Subject collection, it only accepts RuntimeAttribute.

Cause: Invalid data type in Subject collection, it only accepts RuntimeAttribute.

Action: Use RuntimeAttribute in Subject collection.
Level: 1

Type: ERROR

Impact: Security

JPS-08037: Invalid data type in Action collection, it only accepts RuntimeAttribute.

Cause: Invalid data type in Action collection, it only accepts RuntimeAttribute.

Action: Use RuntimeAttribute in Action collection.
Level: 1

Type: ERROR

Impact: Security

JPS-08038: Invalid data type in Resource collection, it only accepts RuntimeAttribute.

Cause: Invalid data type in Resource collection, it only accepts RuntimeAttribute.

Action: Use RuntimeAttribute in Resource collection.
Level: 1

Type: ERROR

Impact: Security

JPS-08500: Component audit definition {0} already exists.

Cause: Component audit definition {0} already exists.

Action: Check given component type.
Level: 1

Type: WARNING

Impact: Security

JPS-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: Cannot search audit definition for component {0}. Reason: {1}.

Cause: Cannot search audit definition for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-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: Cannot register to audit service for component "{0}".

Cause: Cannot register component definition "{0}" to audit service. Reason {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-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-08554: Failed to register Component type "{0}" due to malformed version number in event definition.

Cause: Failed to register Component type "{0}" due to malformed version number in event definition.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08555: During provisioning operations, subscriptions will not be accepted

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08556: Component type value null is invalid.

Cause: Component type value null is invalid.

Action: Use the appropriate componentType while doing registration of component to AuditStore
Level: 1

Type: ERROR

Impact: Security

JPS-08557: Component events definition file is invalid. Reason - "{0}".

Cause: Component events definition file is invalid. Reason - "{0}".

Action: Correct the events definition file based on reason
Level: 1

Type: ERROR

Impact: Security

JPS-08558: Failed to rollback audit registration failure for component "{0}" , Reason "{1}".

Cause: Failed to rollback audit registration failure for component "{0}" , Reason "{1}".

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08559: No matching system event definition for EventRef "{0}" , regarded as a custom Event.

Cause: No matching system event definition for EventRef "{0}" , regarded as a custom Event.

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 inputted Hex Binary value {0}.

Cause: Invalid value provided for OpssHexBinary data type.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09064: Invalid extension manager, cannot be used to find constraint attributes and functions.

Cause: Internal error: invalid extension manager cannot be used to find constraint attributes or functions.

Action: Provide correct function.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09400: Attribute key cannot be null.

Cause: Attribute key was null.

Action: Provide a valid attribute key.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-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-09500: Template name is not initialized, please follow the document for method execution order

Cause: Template name is not initialized.

Action: Ensure that execution order is followed as per document
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09501: Either template name or target store or target key or credential object is passed as NULL, {0} is not inserted

Cause: Either template name or target store or target key or credential objcet is passed as NULL, corresponding credential/key object is not inserted

Action: Ensure that all the parameters are passed to insert credential/key object
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09502: Error occurred when initializing security artifacts. Reason {0}

Cause: Security Artifact initialization failed

Action: Check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09503: Error occurred when cleaning the environment, please clean it manually

Cause: Error occurred while cleaning the environment

Action: Please clean it manually
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09504: Error occurred when processing credentials for template {0}. Reason {1}

Cause: Failed while processing credentials

Action: Check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09505: Error occurred when processing keys for template {0}. Reason {1}.

Cause: Failed while processing keys

Action: Check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09506: Error occurred when commiting changes, calling abort method to clean up the environment

Cause: Failed while commiting changes

Action: Please check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09507: No templates are processed, please call processXXX() methods

Cause: No templates are processed, please call processXXX() methods

Action: Please call processXXX() methods before calling end() method
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09508: No artifacts found for template {0}

Cause: No templates specified in component-security-info.xml file

Action: Please add new template in component-security-info.xml file
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09509: No processing mode specified for template {0}

Cause: No processing mode specified for a template

Action: Please add processing mode for a template in component-security-info.xml file
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09510: No credentials found for template {0}

Cause: No credentials are available to seed into OPSS security store for template {0}

Action: Please check the logs or corresponding credential data file in template
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09511: Not able to instantiate credential store object for credential store {0}

Cause: Scratch directory credential store initialization failed

Action: Please check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09512: Not able to instantiate key store service object for key stores {0}

Cause: Scratch directory key store initialization failed

Action: Please check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09513: Not able to get the handle for bootstrap cwallet.sso {0}

Cause: Not able to get the handle for bootstrap wallet

Action: Please check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09514: Credential already exist for map {0} and key {1}

Cause: Credentials already exist in the Opss CredentialStore Implementation

Action: Pass credentials with unique map and key name
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09515: CIE CredentialsInfo object should not be null

Cause: Passed CIE CredentialStoreInfo object is NULL

Action: Please pass valid CIE credential object
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09516: CIE KeystoreInfo object should not be null

Cause: Passed CIE KeystoresInfo object is NULL

Action: Please pass valid CIE key store object
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09517: CIE PrivateKeyInfo object should not be null

Cause: Passed CIE PrivateKeyInfo object is NULL

Action: Please pass valid CIE private key object
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09518: Alias '''{0}''' already exist in key store {1}

Cause: Alias already exist in the Opss key store Implementation

Action: Please key object with unique alias
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09519: Error occurred when processing audit data for template {0}. Reason {1}

Cause: Failed while processing audit data

Action: Check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09520: Error occurred when processing authorization data for template {0}. Reason {1}.

Cause: Failed while processing authorization data

Action: Check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09521: More than one application stripe {0} found in authorization data file {1}.

Cause: More than one application stripe in authorization data file

Action: Ensure that the authorization file does not have more than one application stripe
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09522: Authorization data file {0} is not present.

Cause: No authorization data file found.

Action: Verify if the file is present
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09523: No keys found for template {0}

Cause: No keys are available to seed into OPSS security store for template {0}

Action: Please check the logs or corresponding keystore data file in template
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09524: More than one component types found in audit store data file {0} for template {1}.

Cause: More than one component types in audit store data file

Action: Ensure that the audit store file does not have more than one component type
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09600: File {0} is cannot be found. Check if the specified file is expected in the specified location.

Cause: File {0} cannot be found.

Action: Check if the specified file exists and accessible in the specified location.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09601: The value "{0}" is invalid for {1}.

Cause: An invalid value was provided for this configuration.

Action: Provide the correct value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09602: Fail to find default JPS Context in {0}.

Cause: Fail to find default JPS Context in the jps-config.xml.

Action: Check content of jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09603: SecurityContext.getSharedSecretStore and getSharedSecretStorePassword return inconsistent values.

Cause: SecurityContext.getSharedSecretStore and getSharedSecretStorePassword return inconsistent values.

Action: Both shared secret store name and password are required for configuring a domain with shared database security store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09604: JDBC Information {0} is missing for configuring security store to database.

Cause: JDBC Information is missing for configuring security store to database.

Action: Check if all required jdbc information is supplied.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09605: Fail to find JPS Context with id {0} in {1}.

Cause: Fail to find the specific JPS Context in the jps-config.xml.

Action: Check content of jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09606: Error encountered while importing encryption key in shared database security store.

Cause: Error encoutered while seeding encryption key in shared database security store.

Action: Check if encryption key is exported and imported properly.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09607: OpssSecurityConfiguration is in invalid state.

Cause: OpssSecurityConfiguration is in invalid state, it has not been initialized properly

Action: If creating expanded domain, check if database is up and all the required datasource information are provided.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09608: OpssSecurityConfiguration is in invalid state, start method is not invoked prior to other methods.

Cause: OpssSecurityConfiguration is in invalid state - start() method is not invoked by CIE prior to other methods

Action: Check if CIE is invoking OpssSecurityConfiguration in proper order.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09609: Failed to initialize OPSS security context based on SecurityContext object from CIE.

Cause: Failed to initialize OPSS security context based on SecurityConext object passed from CIE.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09610: Error during updating audit loader repositoryType. Exception {0}

Cause: Failed to update audit loader repository type to DB.

Action: Check the logs.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09611: Error updating audit loader credential in bootstrap wallet. Exception {0}

Cause: Failed to add audit loader credentials to bootstrap wallet

Action: Check the logs.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09612: JDBC password for {0} is missing for configuring security store to database.

Cause: JDBC password is missing for configuring security store to database.

Action: Check if jdbc password is supplied.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09613: JDBC username for {0} is missing for configuring security store to database.

Cause: JDBC username is missing for configuring security store to database.

Action: Check if jdbc username is supplied.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09614: The supplied password for property {0} is invalid.

Cause: The supplied password for property {0} is invalid.

Action: Please provide valid password.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09615: Update jps configuration file(s) failed for service {0}. Exception {1}

Cause: Update jps configuration file(s) failed for service {0}.

Action: Check log file for errors.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09616: The schema {0} is already in use for security store(s). Please create a new schema.

Cause: The schema {0} is already in use for security store(s).

Action: Please create a new schema.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09617: Failed to create a domain with shared security store because no security store was found in the database schema {0}.

Cause: Failed to create a domain with shared security store because no security store was found in the database schema {0}.

Action: Please check if a security store is configured properly for the database schema.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09618: Data migration failed for configurator {0}

Cause: Failed to migrate data for configurator {0}.

Action: Please check the logs and check if a security store is configured properly for the database schema.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09619: Jps test service failed for configurator

Cause: Jps test service failed for configurator.

Action: Please check the logs and check if a security store is configured properly for the database schema.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09620: Failed to rollback data.

Cause: Failed to rollback data.

Action: Please check the logs
Level: 1

Type: ERROR

Impact: Configuration

JPS-09621: No entry found for artifact type {0} in component-security-info.xml file of template {1}.

Cause: Artifact is not registered in component-security-info.xml file of template, but artifact data is present as part of template.

Action: Please register missing artifact in component-security-info.xml file
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09622: Error during configuring DB security store. Exception {0}.

Cause: Error occured during configuring DB security store.

Action: Check the logs
Level: 1

Type: ERROR

Impact: Configuration

JPS-09623: Error during updating JPS configuration in shared DB security store. Exception {0}.

Cause: Error updating JPS configuration in shared DB security store.

Action: Check the logs
Level: 1

Type: ERROR

Impact: Configuration

JPS-09624: JDBC database name for {0} is missing for configuring security store to database.

Cause: JDBC database name is missing for configuring security store to database.

Action: Check if jdbc database is supplied.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09625: Jps test service completed for configurator.

Cause: Jps test service completed for configurator.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-09626: Rolling back of data for configurator is completed.

Cause: Rolling back of data for configurator is completed.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-09627: Trying to rollback data for configurator.

Cause: Trying to rollback data for configurator.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-09630: Failed to seed MDS credential to bootstrap cwallet file with specified key/map '{0}'.

Cause: Failed to seed MDS credential to bootstrap cwallet file.

Action: Check the logs
Level: 1

Type: ERROR

Impact: Configuration

JPS-09631: Failed to create tenant config profile '{0}' in MDS.

Cause: Failed to create tenant config profiles in MDS.

Action: Check the logs
Level: 1

Type: ERROR

Impact: Configuration

JPS-09632: More than one config-security-file.xml are round in templates.

Cause: More than one config-security-file.xml in templates are found.

Action: Check the logs
Level: 1

Type: ERROR

Impact: Configuration

JPS-09633: Start to provisioning partition {0} with OPSS resource group. Parameters: {1}.

Cause: Start to provisioning a partition with OPSS resource group.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-09634: Rollback partition provisioning.

Cause: Rollback partition provisioning.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-09635: Partition provisioning with OPSS resource group is completed.

Cause: Successfully provisioning a partition with OPSS resource group.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-10000: There was an internal error in the policy store.

Cause: The opearion is not allowed for multivalued attribute.

Action: The opearion is not allowed for multivalued attribute.Supply a valid opearion
Level: 1

Type: WARNING

Impact: Security

JPS-10001: Exception happened while decoding value: {0}.

Cause: The encoding format is not correct.

Action: Check encoding format of String value.
Level: 1

Type: WARNING

Impact: Security

JPS-10002: Container is not ready. Reason: {0}.

Cause: Container is not ready.

Action: Wait for container to start up successfully.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10003: Null search value is not allowed, unless the matcher is ANY.

Cause: Query value is null but the matcher is not ANY.

Action: Do not use null query value if the matcher is not ANY.
Level: 1

Type: WARNING

Impact: Security

JPS-10004: The search value {0} is invalid.

Cause: Query value is invalid.

Action: Use an valid query value.
Level: 1

Type: WARNING

Impact: Security

JPS-10005: Access denied. {0}

Cause: Access to policy store is denied.

Action: Do not perform such operation on policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-10050: The application {0} cannot be found at runtime due to {1}.

Cause: Corresponding runtime application does not exist.

Action: Check if policy is properly distributed.
Level: 1

Type: ERROR

Impact: Security

JPS-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-10168: Error occurred while preparing the principal in {0} method of {1} class : {2}. In standalone mode, weblogic specific jars should not be in classpath. Please check the classpath and try again.

Cause: Fail to resolve principal.

Action: Check classpath which may contain weblogic specific jars.
Level: 1

Type: ERROR

Impact: Security

JPS-10169: Default SystemAdminRole should be granted to at least one principal.

Cause: Revoking last member of default admin role SystemAdmin

Action: Keep at least one member of default admin role SystemAdmin
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-10280: The resource attribute {0} does not exist in the resource type {1}.

Cause: The resource attribute does not exist in the resource type.

Action: Check all the valid resource attributes in the resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-10400: Resource reference should not be null.

Cause: The parameter resource reference is null.

Action: Use a valid object.
Level: 1

Type: WARNING

Impact: Security

JPS-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 {1} and can not be deleted.

Cause: The action is used by the permissionSet/permission and can not be deleted.

Action: Check if the action is used in any PermissionSet/Permission before deleting.
Level: 1

Type: WARNING

Impact: Security

JPS-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-10430: The Resource name {0} has an invalid format

Cause: Too many delimiters in the resurce name

Action: Limit the number of delimiters in the beginning and middle of resource name to one.
Level: 1

Type: WARNING

Impact: Security

JPS-10431: Wrong isSingle property for the attribute {0}; expected {1}, but {2}.

Cause: Wrong isSingle property of resource attribute

Action: Ensure isSingle property of the attribute in resource is the same as the definiton in resource type
Level: 1

Type: WARNING

Impact: Security

JPS-10432: Wrong DataType property for the attribute {0}; expected {1}, but {2}.

Cause: Wrong DataType property of resource attribute

Action: Ensure DataType property of the attribute on resource is the same as the definition in resource type
Level: 1

Type: WARNING

Impact: Security

JPS-10451: Permission set {0} does not belong to the context.

Cause: The permission set does not belong to current context

Action: Pass in correct permission set.
Level: 1

Type: WARNING

Impact: Security

JPS-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-10469: Cannot remove all the ResourceActionsEntrys in PermissionSet.

Cause: Try to remove all the ResourceActionsEntrys in existing PermissionSet.

Action: Check the updated resource actions, make sure PermissionSet does not have up empty resource actions.
Level: 1

Type: WARNING

Impact: Security

JPS-10470: The resource type name "{0}", does not match the resourceType in the encoded target name: "{1}". Permission class is "{2}"

Cause: Invalid resource type in permission target.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-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}" already 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-10549: The policy rule {0} is in use, could not be deleted.

Cause: The policy rule could not be deleted without cascade since it is in use.

Action: Cascade delete it or first remove all referring objects.
Level: 1

Type: WARNING

Impact: Security

JPS-10550: Attribute "{0}" already exists

Cause: Cannot have two attributes with the same name.

Action: Provide a new name to the attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-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 "{0}" already exists.

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 due to following exception {2}.

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-10628: Retry {0} for the {1} times.

Cause: Retry {0} for the {1} times.

Action: No actions are required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10629: SUCCESS: Retry {0} successfully after {1} times retries.

Cause: SUCCESS: Retry {0} successfully after {1} times retries.

Action: No actions are required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10630: The default DB policy store is missing for mixed mode.

Cause: The default DB policy store is missing for mixed mode.

Action: Configure one DB policy store instance.
Level: 1

Type: ERROR

Impact: Security

JPS-10631: Failed to distribute policy to Real Application Security Database, target RAS database {0}, exception {1}.

Cause: Failed to distribute policy to Real Application Security Database

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10632: Failed to obtain the datasource for Real Application Security Database, target RAS database {0}, exception {1}

Cause: Failed to obtain the datasource for Real Application Security Database

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10633: Failed to fetch the information from the intermediate table, target RAS database {0}, exception {1}"

Cause: Failed to fetch the information from the intermediate table

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10634: Failed to prepare data for distributing policy to Real Application Security Database, application name {0}, exception {1}.

Cause: Failed to prepare data for distributing policy to Real Application Security Database

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10635: Failed to update the intermediate table in the policy store database, target RAS database {0}, exception {1}.

Cause: Failed to update the intermediate table in the policy store database

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10636: Incorrect Real Application Security PDP address format.

Cause: Incorrect Real Application Security PDP address format

Action: Refer to the log files for details. The correct format should start with "ras:"
Level: 1

Type: ERROR

Impact: Security

JPS-10700: The value of attribute {0} should be unique

Cause: The unique attribute has duplicated values.

Action: Keep attribute value unique.
Level: 1

Type: WARNING

Impact: Security

JPS-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 "{0}" does not exist.

Cause: The role policy object does not exist.

Action: Check if the target role policy exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10801: The role policy object "{0}" already exists.

Cause: The policy object exists.

Action: Create a policy with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-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-10804: The advice {0} already exists.

Cause: The advice already exists in the policy entry.

Action: Check AdviceEntry passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10850: The SM Config Tool is used to configure the Security Modules for Oracle Entitlements Server Here are the various options that it will accept -smType <java, wls, ws, rmi, was, jboss> -smConfigId <config id of sm is always required> -serverLocation <in case of was, wls, jboss, this is the location of the server> -pdServer OES Admin Server hostName -pdPort SSL Port for OES Admin Server -pdClientPort SSL Port for WLS SM client -serverNodeName - server node name of websphere -serverName - server instance name of websphere -serverUserName - user name of application server -serverPassword - password of application server -prpFileName - path for the prp file used.

Cause: When help is asked for

Action: Help message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-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-10892: sys_subjectroles

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10893: List of unqualified role names granted to user for current request

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10900: The enrollment response is truncated.

Cause: Enrollment response is truncated.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10901: Keystore {0} does not exist.

Cause: Keystore {0} does not exist.

Action: Check the file system.
Level: 1

Type: ERROR

Impact: Security

JPS-10902: Enrollment server error.

Cause: Enrollment server error.

Action: Check enrollment server status.
Level: 1

Type: ERROR

Impact: Security

JPS-10903: Enrollment is proceeded successfully.

Cause: Enrollment is proceeded successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10904: Enrollment is not proceeded successfully.

Cause: Enrollment is not proceeded successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10905: The program works in console mode only.

Cause: The program works in console mode only.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-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: Passwords are not saved in credential store.

Cause: Passwords are not saved in credential store.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10911: {0} is not set.

Cause: {0} is not set.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10912: Keystores are initialized successfully.

Cause: Keystores are initialized successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10913: Keystores are not initialized successfully.

Cause: Keystores are not initialized successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10914: Enter username for {0}:

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 n GMT time zone during evaluation

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10991: The attribute will be assigned current date value n GMT time zone during evaluation

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-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-11000: Policy Set member with type: "{0}" and name "{1}" does not exist

Cause: The policy set member does not exist in policy store

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11001: Can not delete policy set "{0}" which is referred by other policy set

Cause: The policy set to be deleted is referred by other policy set

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11002: Policy set dependency loop could be introduced by modifyPolicySet operation

Cause: The policy set depdency could be introduced by modifyPolicySet operation

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11003: Policy set "{0}" does not exist

Cause: The policy set entry with specified name does not exist in policy store

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11004: Multiple principal entries provided have principal constraint

Cause: Multiple principal entries have principal constraint

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11005: Can not add AllResource to permission set: "{0}"

Cause: Adding AllResource to Permission set is not supported

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11006: Adding {0} combiner parameters for {0} "{1}" not referred in this policy set

Cause: Adding policy or policy set combiner paramers for policy or policy set not referred in this policy set

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11007: Can not add codesource, principals, resource actions or permission sets to {0}: "{1}" which has XACML3 target

Cause: Adding codesource, principals, resource actions or permissin sets to policy, policy set or rule which has XACML3 target

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11008: Can not add XACML3 target to {0}: "{1}" which has codesource, principals, resource actions or permission sets

Cause: Adding XACML3 target to policy, policy set or rule which has codesource, principals, resource actions or permissin sets

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11009: Policy set "{0}" already exists

Cause: The policy set entry with specified name already exists in the policy store

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-12000: No such Configuration Profile "{0}" exists in the system.

Cause: The specified configuration profile is not registered with configuration service.

Action: Check the name, or try listing the registered profiles.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12001: Cannot create ContextConfiguration, A JPS Context with name "{0}" already exists in the system.

Cause: A jpsContext with the specified contextId exists in the system.

Action: Use another unique contextId.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12002: Could not Construct the ConfigurationManagementService: Configuration Context Descriptor NOT FOUND in jps-config.xml or specifies an invalid Configuration serviceInstance descriptor.

Cause: A jpsContext by the name "ConfigContext" that references a Configuration Service Instance Descriptor is missing from jps-config.xml.

Action: Check the MultiTenancy Enablement steps and/or scripts.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12003: Could not Construct ConfigurationManagementService from its Descriptor in jps-config.xml, due to empty/missing configuration data in the Descriptor.

Cause: The configuration jpsContext does seem to contain a <serviceInstanceRef> pointing to the ConfigurationManagementService instance descriptor.

Action: Check the MultiTenancy Enablement steps and/or scripts.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12004: No such JpsContext "{0}" exists in jps-config.xml.

Cause: A jpsContext with the specified contextId does not exists in the system.

Action: Check jps-config.xml of the domain.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12005: A ContextConfiguration with "{0}" "{1}" already exists in the system.

Cause: A ContextConfiguration with the specified name already exists.

Action: Use another unique name.
Level: 1

Type: ERROR

Impact: Data

JPS-12006: No Registered ContextConfiguration with "{0}" "{1}" exists in the system.

Cause: The specified configuration profile is not registered with configuration service.

Action: Check the name, or try listing the registered profiles.
Level: 1

Type: ERROR

Impact: Data

JPS-12007: Cannot delete ContextConfiguration "{0}" in "{1}" state.

Cause: A ContextConfiguration in ACTIVE state cannot be deleted.

Action: DeActivate the context and then try deleting it.
Level: 1

Type: ERROR

Impact: Data

JPS-12008: Cannot DeActivate ContextConfiguration "{0}" as it is in state "{1}".

Cause: A ContextConfiguration ACTIVE state (only) can be DeActivated. DeActivation from other states is illegal.

Action: Make sure the context configuration is ACTIVE and then try deactivating it.
Level: 1

Type: ERROR

Impact: Data

JPS-12009: Cannot Activate ContextConfiguration "{0}" as it is in state "{1}".

Cause: A ContextConfiguration must be in COMPLETE or INACTIVE state for Activation to succeed.

Action: Check to make sure the state of the Context is COMPLETE or INACTIVE.
Level: 1

Type: ERROR

Impact: Data

JPS-12010: Cannot Update ContextConfiguration "{0}" as it is in state "{1}".

Cause: A ContextConfiguration must be in CREATED or INACTIVE state before it can be UPDATED.

Action: Check to make sure the state of the Context is CREATED or INACTIVE. A configuration in COMPLETE or ACTIVE states cannot be updated
Level: 1

Type: ERROR

Impact: Data

JPS-12011: OPSS Runtime Cannot fetch Configuration for context "{0}", The context does not exist or is not in ACTIVE state.

Cause: OPSS Runtime failed to fetch the Configuration for the context. Either the context does not exist or is not in ACTIVE state. The Runtime can only view ContextConfigurations in ACTIVE state

Action: Check to make sure the Context exists and is in ACTIVE state.
Level: 1

Type: ERROR

Impact: Data

JPS-12012: Cannot initialize Configuration Store : One of DataSource/JDBC-URL/FilePath for MetaDataStore should be Configured in the Configuration Service Descriptor.

Cause: The configuration serviceInstance descriptor does not seem to contain a property for DataSource/JDBC-URL/FilePath for connecting to the Configuration Store.

Action: Check MultiTenancy enablement steps/scripts.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12013: File based Configuration Store should be used only for Development and not in Production.

Cause: File based Configuration Store should be used only for Testing and not in Production.

Action: Nothing to do if this is a Test Environment, else check Multi-Tenancy enablement steps.
Level: 1

Type: WARNING

Impact: Configuration

JPS-12014: Map/Key name(s) for Credential required to bind to MetaDataStore with JDBC-URL not configured in the Configuration Service.

Cause: A Password Credential is required when JDBC-URL is used to connect to the Configuration Store.

Action: Check to see that the Configuration serviceInstance descriptor contains properties for the Map and Key name of the credential.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12015: Property JPS_CONFIG_PATH not set for use by PersistenceManager.

Cause: Internal Error/Bug: The Configuration Management Service is expected to set a property JPS.CONFIGSERVICE.PATH for use by the PersistenceManager.

Action: Report Bug on Oracle OPSS with relevant logs.
Level: 1

Type: ERROR

Impact: Process

JPS-12016: Internal Error: Unable to locate ContextConfiguration named "{0}" in the Configuration Profile "{1}".

Cause: Internal Error/Bug: The Configuration Service is in a state where it thinks the specified contextId should exist under the specified profileId, but the persisted information in the store does not match the expectation.

Action: Report Bug on Oracle OPSS with relevant logs.
Level: 1

Type: ERROR

Impact: Process

JPS-12017: Invalid Customization expression , specified XPath "{0}" does not evaluate to a "{1}".

Cause: The XPath expression specified in Customization spec does not point to the intended element in the Configuration Profile document.

Action: Check the XPath expression against the structure of the configuration Profile being referenced..
Level: 1

Type: ERROR

Impact: Data

JPS-12018: Invalid Location Override Customization in Global Scope. Location Customization can be specified for ServiceInstances only.

Cause: The Location Override in Customization spec is only applicable to a serviceInstance attribute and cannot be applied to an element in Global Scope.

Action: Check the XPath expression.
Level: 1

Type: ERROR

Impact: Data

JPS-12019: Cannot apply "{0}" overrides on element of type "{1}", expected an element of type "{2}", check the Element XPath specified in the customization.

Cause: The XPath expression specified in Customization spec does not point to the intended element in the Configuration Profile document.

Action: Check the XPath expression against the structure of the configuration Profile being referenced..
Level: 1

Type: ERROR

Impact: Data

JPS-12020: Cannot modify values of existing ExtendedProperty elements during customization.

Cause: Cannot modify values of existing ExtendedProperty elements during customization.

Action: This is an Unsupported Customization spec, change the customization instructions supplied to the Configuration Management Service.
Level: 1

Type: WARNING

Impact: Data

JPS-12021: Cannot create ContextConfiguration "{0}", No such profile "{1}" exists in the system.

Cause: Cannot create ContextConfiguration as the referenced Configuration Profile does not seem to exist.

Action: Check the name of the specified profile.
Level: 1

Type: ERROR

Impact: Data

JPS-12022: MetaDataObject "{0}" not found. Ensure ContextConfiguration "{1}" exists or first create it.

Cause: The PersistenceManager is unable to find the MetaDataObject corresponding to the specified contextId.

Action: Check the name of the context or make sure it is registered with the Configuration Service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12023: Mutable MetadataObject "{0}" cannot be obtained from MetadataStore specified since there are pending writes to other MetadataStores. Do flushChanges/cancelChanges on MDSSession to proceed.

Cause: Internal Error/Bug : The persistence manager is in a state where it is trying to perform multiple updates to the profile document concurrently.

Action: Report a Bug on Oracle OPSS with relevant logs.
Level: 1

Type: ERROR

Impact: Process

JPS-12024: A profile with name "{0}" already exists.

Cause: A configuration profile with the given name already exists.

Action: Try using a unique profileId.
Level: 1

Type: ERROR

Impact: Data

JPS-12025: Cannot Delete Profile "{0}" ,Named ContextConfigurations exist under the profile.

Cause: A configuration profile which has named ContextConfiguration's referencing it cannot be deleted.

Action: Try deleting the ContextConfiguration's before attempting to delete the profile.
Level: 1

Type: ERROR

Impact: Data

JPS-12026: No such ContextConfiguration "{0}" exists in the system.

Cause: The specified ContextConfiguration is not registered with the Configuration Service.

Action: Check the name or try listing the registered ContextConfigurations.
Level: 1

Type: ERROR

Impact: Data

JPS-12027: Required PasswordCredential at Map = "{0}",Key = "{1}" was not found in Specified Bootstrap CredentialStore.

Cause: A required PasswordCredential does not exist at the specified map, and key in the supplied bootstrap credential store.

Action: Check the bootstrap credential store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12028: Malformed jps-config.xml : stale service instance reference "{0}" from JpsContext.

Cause: The PersistenceManager found a STALE <serviceInstanceRef> that does not exist in the jps-config.xml.

Action: Check the jps-config.xml of the Profile or the Out-of-the-Box jps-config.xml as appropriate.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12029: Cannot set Name for ContextConfiguration "{0}" in state "{1}", deactivate it first.

Cause: Cannot set contextName for a ContextConfiguration in ACTIVE.

Action: DeActivate it first and then set a Name for it.
Level: 1

Type: ERROR

Impact: Data

JPS-12030: Cannot setContextName, ConfigurationContext "{0}" is already Named "{1}", unset the Name first.

Cause: A ContextConfiguration that is already has a Name cannot be Named again.

Action: Unset the current Name first and then set a new Name for it.
Level: 1

Type: ERROR

Impact: Data

JPS-12031: Cannot unset Name for ContextConfiguration "{0}" in state "{1}", deactivate it first.

Cause: Cannot unset the contextName for a ContextConfiguration in ACTIVE state.

Action: DeActivate the Context first and then unset the contextName.
Level: 1

Type: ERROR

Impact: Data

JPS-12032: Error in initializing JAXBContext.

Cause: Internal Error: JAXB context initialization in PersistenceManager Failed.

Action: Report a Bug on Oracle OPSS with relevant logs.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12033: Invalid profile jps-config.xml document, does not contain a required element "{0}".

Cause: Internal Error: the profile document does not contain a mandatory element.

Action: Check the jps-config.xml that was used as a Configuration Profile.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12034: MDSPersistenceManager Cannot handle Persistence of Element "{0}".

Cause: Unsupported operation : The persistence manager configured with the Configuration Service does not handle persistence of the specified element.

Action: Report a Bug on Oracle OPSS with relevant logs.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12035: Cannot setContextName for ConfigurationContext "{0}" to Name "{1}", as the Name is already assigned to "{2}".

Cause: Names used for ContextConfiguration must be unique, an attempt is being made to set the same Name for more than one ContextConfiguration.

Action: Use a different unique Name.
Level: 1

Type: ERROR

Impact: Data

JPS-12036: ContextConfiguration "{0}" does not have any name set for it, Naming a ContextConfiguration is mandatory before its configuration STATE can be set to COMPLETE.

Cause: An attempt is being made to set the STATE of an Un-Named ContextConfiguraton to COMPLETE.

Action: Use the setContextName(contextId) method to set a Name.
Level: 1

Type: ERROR

Impact: Data

JPS-12037: Service configuration update done for Configurator.

Cause: Service configuration update done for Configurator.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Data

JPS-12038: Failed to check if audit is enabled.

Cause: Configuration management events logging was not enabled.

Action: Check the audit configuration to ensure auditing enabled.
Level: 1

Type: WARNING

Impact: Configuration

JPS-12039: Failed to log audit record.

Cause: Configuration management audit event logging failed.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-12040: Missing Property set props.db.1.

Cause: No Prorperty Set props.db.1 in jps-config.xml

Action: Check the jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12100: The expiry time should be in format {0}

Cause: Invalid input

Action: Correct the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-12101: The filter value is {0} invalid

Cause: Invalid input

Action: Correct the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-12102: One of the attributes {0} is undefined

Cause: Invalid input

Action: Correct the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-12103: Parameter {0} is missing

Cause: Missing Parameter

Action: Correct the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-12104: Alias {0} did not exist or point to a key

Cause: Alias did not exist or point to a key

Action: Correct the input Alias.
Level: 1

Type: WARNING

Impact: Configuration

JPS-20000: GlobalPolicy can not be created by MAPI methods

Cause: GlobalPolicy can not be created by MAPI methods.

Action: Set up policy store using reassociation or upgrading
Level: 1

Type: WARNING

Impact: Programmatic

JPS-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-20003: Cannot add global role to application role

Cause: Attempted to add a global role {0} to members of an application role or grant a global role {0} to an applicaton role

Action: Do not add a global role to members of an application role and do not grant a global role to an application role.
Level: 1

Type: WARNING

Impact: Security

JPS-20004: Principals can not contain global role.

Cause: Principals contain global role {0}

Action: Remove global role from principals.
Level: 1

Type: WARNING

Impact: Security

JPS-20005: Cannot delete global role "{0}".

Cause: Global role "{0}" is referenced in a Policy defined in an Application.

Action: Make sure the global role is not referenced in any application policy,then remove it.
Level: 1

Type: WARNING

Impact: Security

JPS-20006: Authorization policy is not supported in global policy.

Cause: Authorization policy is not supported in global policy.

Action: Do not create authorization policies in global policy.
Level: 1

Type: WARNING

Impact: Security

JPS-20007: Permission grant is not supported in global policy

Cause: Permission grant is not supported in global policy.

Action: Do not grant permissions in global policy
Level: 1

Type: WARNING

Impact: Security

JPS-20008: {0} : {1} in global policy which are referenced in application have been changed but not distributed

Cause: {0} : {1} in global policy which are referenced in application have been changed but not distributed.

Action: Distribute global policy firstly
Level: 1

Type: WARNING

Impact: Security

JPS-20010: Attribute name {0} already exist in {1}.

Cause: Attribute name {0} already exist in {1}

Action: Choose another name
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20011: Function name {0} already exist in {1}.

Cause: Function name {0} already exist in {1}

Action: Choose another name
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20012: Global attribute {0} is used in application {1}.

Cause: Global attribute {0} is used in application policy {1}

Action: Make sure the global attribute is not used in any applications including global policy
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20013: Global function {0} is used in application {1}.

Cause: Global function {0} is used in application policy {1}

Action: Make sure the global function is not used in any applications including global policy
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20014: Policy domain is not supported in global policy

Cause: Policy domain is not supported in global policy.

Action: Do not use policy domain in global policy
Level: 1

Type: WARNING

Impact: Security

JPS-20020: Resource type name {0} already exists in application {1}.

Cause: Resource type name {0} already exists in application {1}

Action: Choose another name
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20021: Global resource type {0} is used in application {1}.

Cause: Resource type {0} is used in application {1}

Action: Make sure global resource type is not used in any application
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20022: Global policy can not be unbound from SM

Cause: Global policy can not be unbound from SM

Action: Do not unbind global policy from SM
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20050: Combining algorithm {0} not found.

Cause: Combining algorithm not found.

Action: Make sure the used combining algorithm exists.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-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-20054: A acl match type must be provided if policy is a RAS one.

Cause: RAS policy has no acl match type to be provided.

Action: Provide a ACL Match Type.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20055: A list of RAS policy rule must be provided if policy is a RAS one.

Cause: RAS policy has no policy rule to be provided.

Action: Provide policy rule(s).
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20056: A list of RAS resource must be provided if policy is a RAS one.

Cause: RAS policy has no resource to be provided.

Action: Provide resource(s).
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20060: Number of input parameters to the function and provided value types for them are not of same size.

Cause: Number of input parameters to the function and provided value types for them are not of same size.

Action: Parameter value types, if provided, must be provided for all input parameters
Level: 1

Type: ERROR

Impact: Programmatic

JPS-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-20100: Rules {0} for policy {1} is in use by other policies. It will not be deleted.

Cause: Rule {0} of policy {1} is shared by other policies.

Action: Provide correct Rule.
Level: 1

Type: ERROR

Impact: Security

JPS-20101: Policy {0} is referred by one or more policy sets. It can not be deleted if cascading is set to false.

Cause: Policy {0} is referred by other policie sets.

Action: Either use cascading delete or remove references from policy sets.
Level: 1

Type: ERROR

Impact: Security

JPS-20102: Rule {0} used in policy is not sharable. The policy will not be created or updated.

Cause: Rule {0} used in policy is not sharable.

Action: Provide correct Rule.
Level: 1

Type: ERROR

Impact: Security

JPS-20103: Policy can not have both private rules and sharable rules.

Cause: Policy can not have both private rules and sharable rules.

Action: Provide correct Rule.
Level: 1

Type: ERROR

Impact: Security

JPS-20104: Exclusive rule {0} can not be deleted explicitly.

Cause: Exclusive rule {0} can not be deleted explicitly.

Action: Delete the referred policy.
Level: 1

Type: ERROR

Impact: Security

JPS-20105: The permission {0} has no target name.

Cause: Permission has no target name.

Action: Make sure the usage is valid.If not revoke the permission.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20200: Adding attributes to data security resource type {0} is not allowed.

Cause: Attributes present in Data Security Resource Type.

Action: Remove Attributes present in Data Security Resource Type.
Level: 1

Type: WARNING

Impact: Security

JPS-20201: Adding matcher class to data security resource type {0} is not allowed.

Cause: Matcher Class present in Data Security Resource Type.

Action: Remove Matcher Class present in Data Security Resource Type.
Level: 1

Type: WARNING

Impact: Security

JPS-20202: Hierarchical data security resource type {0} is not allowed.

Cause: Data Security Resource Type is Hierarchial.

Action: Change Data Security Resource Type to Flat. It cannot be Hierarchial.
Level: 1

Type: WARNING

Impact: Security

JPS-20203: Adding both actions and action collection references to data security resource type {0} is not allowed.

Cause: Both Actions and Action Collection References are added to Data Security Resource Type.

Action: Add either Actions or Action Collection References to Data Security Resource Type.
Level: 1

Type: WARNING

Impact: Security

JPS-20204: Adding null data security information object to data security resource type {0} is not allowed.

Cause: Null data security information object found for data security resource type.

Action: Add data security information object to data security resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-20205: Data source name is required for a data security resource type {0}.

Cause: Data security information object found for data security resource type has no data source name.

Action: Provide valid data source name for data security information object for data security resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-20206: Invalid value for data source type of data security resource type {0}.

Cause: Data security information object found for data security resource type has invalid data source type.

Action: Data Security information object found for data security resource type has invalid data source type
Level: 1

Type: WARNING

Impact: Security

JPS-20207: Constraint required for data security resource type {0} as data source type is virtual.

Cause: Virtual data source type requires data source constraint to be present.

Action: Provide valid data source constraint for virtual data source.
Level: 1

Type: WARNING

Impact: Security

JPS-20208: Actions List cannot contain actions that are inherited by default for resource type {0}.

Cause: Actions list in resource type contains default inherited data security actions.

Action: Remove default data security actions from data security resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-20209: Duplicate column definition (same column names) not allowed in data source of resource type {0}.

Cause: Duplicate column definition (same names) in secured data source in resource type.

Action: Remove duplicate column definition from secured data source.
Level: 1

Type: WARNING

Impact: Security

JPS-20210: Action collection reference name {1} referred in resource type {0} not found in policy store.

Cause: Action collection reference in resource type not found in the policy store.

Action: Either create action collection in store or remove the reference from resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-20220: Data Security Resource Type should be present for Data Security Resource {0}.

Cause: No RAS resource type present for RAS resource OR is not of type RAS resource type.

Action: Add RAS resource type for RAS resource.
Level: 1

Type: WARNING

Impact: Security

JPS-20221: For data security resource {0} SQL predicate or XML expression is required.

Cause: Both SQL predicate and XML expression missing in data security resource.

Action: Add either SQL Predicate or XML expression to data security resource.
Level: 1

Type: WARNING

Impact: Security

JPS-20240: Multiple rules not allowed for triton policy {0}.

Cause: Multiple rules in triton data security policy.

Action: Add only one rule to triton data security policy.
Level: 1

Type: WARNING

Impact: Security

JPS-20241: Data security policy {0} has invalid type {1} and category {2}.

Cause: Invalid policy category and type combination.

Action: Provide valid policy category and type combination.
Level: 1

Type: WARNING

Impact: Security

JPS-20242: RAS policy only takes resources with same resource type.

Cause: RAS Policy have resources with different resource types.

Action: Provide resources just with same resource type for RAS policy.
Level: 1

Type: WARNING

Impact: Security

JPS-20243: For RASParameterValue, only EXACT matcher is supported.

Cause: Search RAS Policy by RASParameterValue ONLY support MATCHER.EXACT.

Action: Use MATCHER.EXACT for search by RASParameterValue.
Level: 1

Type: WARNING

Impact: Security

JPS-20244: For RASParameterValue, only EQUALITY comparator is supported.

Cause: Search RAS Policy by RASParameterValue ONLY support COMPARATOR.EQUALITY.

Action: Use COMPARATOR.EQUALITY for search by RASParameterValue.
Level: 1

Type: WARNING

Impact: Security

JPS-20260: RAS Resource type name referred in RAS policy set {0} is Null.

Cause: RAS resource type reference in RAS policy set is Null.

Action: Either create given resource type in store beforehand or use an existing one.
Level: 1

Type: WARNING

Impact: Security

JPS-20261: Data security policy set {0} has invalid type {1} and category {2}.

Cause: Invalid policy set category and type combination.

Action: Provide valid policy set category and type combination.
Level: 1

Type: WARNING

Impact: Security

JPS-20262: Policy set {0} is an ACL protecting an Attribute Collection and cannot be deleted.

Cause: Attempt to delete ACL that is protecting an Attribute Collection.

Action: Check that the ACL is not protecting any Attribute Collection.
Level: 1

Type: WARNING

Impact: Security

JPS-20263: RAS Policy set only takes policies whose ras resources are of same ras resource type.

Cause: RAS policy set only takes policies whose ras resources are of same ras resource type.

Action: Use ras policies with same ras resource type for ras policy set.
Level: 1

Type: WARNING

Impact: Security

JPS-20264: The length of RAS {0} name plus the length of RAS application name can not exceed 29.

Cause: The length of RAS artifact name plus the length of ras application name exceeds 29.

Action: Shorten the RAS artifact name
Level: 1

Type: WARNING

Impact: Security

JPS-20265: The name of RAS {0} is allowed to consist of only alphanumeric characters and the special characters $, _, and #, and MUST begin with a letter.

Cause: The RAS artifact name is allowed to consist of only alphanumeric characters and the special characters $, _, and #, and MUST begin with a letter.

Action: Change the RAS artifact name
Level: 1

Type: WARNING

Impact: Security

JPS-20300: The action or implied action "{0}" already exists in action collection "{1}" or its parent(s).

Cause: Duplicate action or implied action found in action collection or one of its parents.

Action: Verify the action and implied action lists of this action collection and its parents.
Level: 1

Type: WARNING

Impact: Security

JPS-20301: The action collection "{0}" is already referenced in action collection "{1}" or its parent(s).

Cause: Duplicate action collection reference found in action collection or one of its parents.

Action: Verify the action collection reference lists of this action collection and its parents.
Level: 1

Type: WARNING

Impact: Security

JPS-20302: The action collection "{0}" already exists in application policy "{1}".

Cause: Action collection already exists in the application.

Action: Verify the action collection in the application or try modify operation.
Level: 1

Type: WARNING

Impact: Security

JPS-20303: The action collection "{0}" was not found in application policy "{1}".

Cause: Action collection not found in application.

Action: Verify the action collection is present in the application.
Level: 1

Type: WARNING

Impact: Security

JPS-20304: The action collection "{0}" is in use by another policy object.

Cause: Action collection is in use by another policy object.

Action: Verify the usages of the action collection.
Level: 1

Type: WARNING

Impact: Security

JPS-20305: Create, modify & delete operations are not permitted on built-in action collection "{0}".

Cause: The action collection being deleted, created or modified is built-in in the database.

Action: Use a different name for the action collection.
Level: 1

Type: WARNING

Impact: Security

JPS-20306: Action {0} referred in implied action {1} is not defined in action collection {2} or any of its parents.

Cause: The mapping specified for given implied action is not found in action collection or its parents.

Action: Check the implied actions mappings.
Level: 1

Type: WARNING

Impact: Security

JPS-20307: The action or implied action "{0}" already exists in implied action "{1}".

Cause: The mapping specified for given implied action contains duplicate actions.

Action: Check the implied actions mappings.
Level: 1

Type: WARNING

Impact: Security

JPS-20308: The implied action "{0}" refers to itself.

Cause: The mapping specified for given implied action contains reference to itself.

Action: Check the implied actions mappings.
Level: 1

Type: WARNING

Impact: Security

JPS-20320: "{0}" is not a RAS target database.

Cause: The SM is not a RAS target database.

Action: make sure the name corresponds to a RAS target database
Level: 1

Type: WARNING

Impact: Security

JPS-20321: "{0}" is not a RAS application.

Cause: The application is not a RAS application.

Action: make sure the name corresponds to a RAS application
Level: 1

Type: WARNING

Impact: Security

JPS-20322: "{0}" is not found or it is not a RAS target database.

Cause: RAS target database not found

Action: make sure the name corresponds to a RAS target database
Level: 1

Type: WARNING

Impact: Security

JPS-20350: All of handlerSchemaName, handlerPackageName and handlerFunctionName must be present or must be null in an attribute collection.

Cause: Atleast one of schema name, package name or function name of handler function is null.

Action: Verify the schema name, package name and function name of handler function.
Level: 1

Type: WARNING

Impact: Security

JPS-20351: The attribute "{0}" already exists in attribute collection "{1}".

Cause: Duplicate attribute found in attribute collection.

Action: Verify the attribute list of this attribute collection and its parents.
Level: 1

Type: WARNING

Impact: Security

JPS-20352: Attributes in attribute collection must be of category DYNAMIC.

Cause: Category of added attribute was wrong.

Action: Verify the added attribute is of category DYNAMIC.
Level: 1

Type: WARNING

Impact: Security

JPS-20353: The attribute collection "{0}" already exists in application policy "{1}".

Cause: Attribute collection already exists in the application.

Action: Verify the attribute collection in the application or try modify operation.
Level: 1

Type: WARNING

Impact: Security

JPS-20354: The attribute collection "{0}" was not found in application policy "{1}".

Cause: Attribute collection not found in application.

Action: Verify the attribute collection is present in the application.
Level: 1

Type: WARNING

Impact: Security

JPS-20355: Attributes in attribute collection must be single-valued.

Cause: Multi-valued attributes not supported.

Action: Verify the added attribute(s) are all single-valued.
Level: 1

Type: WARNING

Impact: Security

JPS-20356: The ACE(Policy Rule) "{0}" is not present in the application.

Cause: ACE(policy rule) protecting Attribute collection not found in application.

Action: Verify the ACE(Policy Rule) is present in the application.
Level: 1

Type: WARNING

Impact: Security

JPS-20357: The attributes in an attribute collection "{0}" is null or empty.

Cause: RASAttribute list is null or empty

Action: Make sure RASAttribute list is not null or empty.
Level: 1

Type: WARNING

Impact: Security

JPS-20400: The definition for attribute "{0}" exists in the application policy with wrong category. Expected: {1}, Found: {2}

Cause: Attribute definition exists in application with different category than expected.

Action: Verify the attribute definition in the application.
Level: 1

Type: WARNING

Impact: Security

JPS-20401: The definition for attribute "{0}" exists in the application policy with wrong type. Expected: {1}, Found: {2}

Cause: Attribute definition exists in application with different type than expected.

Action: Verify the attribute definition in the application.
Level: 1

Type: WARNING

Impact: Security

JPS-20403: Attribute designator functionality is not supported for this schema version.

Cause: Attribute designator functionality is not supported for this schema version.

Action: Don't use designator functionality or upgrade to newer version.
Level: 1

Type: ERROR

Impact: Security

JPS-20411: Invalid match function. Match function for a constraint must take two input parameters, provided function requires {0} input parameters.

Cause: Match function for constraint does not take 2 input parameters.

Action: Provide a corret match function for constraint.
Level: 1

Type: WARNING

Impact: Security

JPS-20412: Invalid match function. Both input parameters to a match function must be of same data type; provided function takes input parameters of type {0} and {1}.

Cause: Match function for constraint musts take two input parameters of same data type.

Action: Provide a correct match function for constraint.
Level: 1

Type: WARNING

Impact: Security

JPS-20413: Invalid match function. First parameter for a match function must be a single value.

Cause: Match function for a constraint cannot take bag or set of values.

Action: Provide a correct match function for constraint.
Level: 1

Type: WARNING

Impact: Security

JPS-20414: Mismatch of attribute category in constraint. Expected {0}, actual {1}.

Cause: Category of attribute provided to the constraint must either be dynamic or match the constraint type.

Action: Provide attribute with correct category type to the constraint.
Level: 1

Type: WARNING

Impact: Security

JPS-20415: The data type {0} of attribute "{1}" does not match data type {2} of function second parameter passed to AttributeValueAssertion.

Cause: Attribute data type and expected function parameter data type are different.

Action: Verify the data type of attribute entry passed to AttributeValueAssertion.
Level: 1

Type: WARNING

Impact: Security

JPS-20416: Data type of value and expected input parameter type of function provided for attribute value assertion does not match. Expected type {0}, provided {1}

Cause: Data type of value and expected input parameter type of function provided for attribute value assertion does not match.

Action: Provide value with correct data type to the constraint.
Level: 1

Type: WARNING

Impact: Security

JPS-20417: Constraints are only supported for TargetEntry and SimpleTargetEntry

Cause: Constraints are supported only for TargetEntry and SimpleTargetEntry.

Action: If a constraint must be used, add it using a TargetEntry or SimpleTargetEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-20420: Function Element is not supported as return type of a function.

Cause: Function Element is not supported as return type of a function.

Action: Provide some other return type.
Level: 1

Type: WARNING

Impact: Security

JPS-20421: Data type for a Function Element input parameter must be OpssString.

Cause: Data type for a Function Element input parameter must be OpssString.

Action: Provide correct data type.
Level: 1

Type: WARNING

Impact: Security

JPS-20422: Function Element not supported for this version of policystore.

Cause: Function element not supported for this schema version.

Action: Don't use function element or upgrade.
Level: 1

Type: WARNING

Impact: Security

JPS-20423: AttributeAssignment can not be defined using a Function Element.

Cause: Attribute assignment cannot be defined using a function element.

Action: Don't use function element.
Level: 1

Type: WARNING

Impact: Security

JPS-20500: Quoted name for {0}, must be terminated by double-quote (").

Cause: Quoted id for triton entity needs to be terminated with double-quote(").

Action: Verify the id provided.
Level: 1

Type: WARNING

Impact: Security

JPS-20501: Length of {0} name must be between 1 and 30 characters (excluding the quotes ("), in case of quoted identifier), but was {1}

Cause: Id for triton entity has invalid length.

Action: Verify the id provided.
Level: 1

Type: WARNING

Impact: Security

JPS-20502: Quoted name for {0} contains invalid character ''{1}'' at position {2}. Quoted names must not contain null character(\0) or double-quote(") within the name

Cause: Quoted id for triton entity has invalid character.

Action: Verify the id provided.
Level: 1

Type: WARNING

Impact: Security

JPS-20503: Unquoted name for {0} contains invalid character ''{1}'' at position {2}. Unquoted names must begin with an alphabet. They may contain a letter, digit, underscore(_), dollar($), hash(#), or dot(.) symbols at other positions.

Cause: Unquoted id for triton entity has invalid character.

Action: Verify the id provided.
Level: 1

Type: WARNING

Impact: Security

JPS-20504: The name "{0}" is an implicit object name in the database and cannot be used as a name for {1}.

Cause: Id provided for triton entity is an implicit object name in the database.

Action: Verify the id provided.
Level: 1

Type: WARNING

Impact: Security

JPS-20505: The value "{0}" is of an unsupported type.

Cause: Parameter value is using an invalid type.

Action: Verify the parameter value provided.
Level: 1

Type: WARNING

Impact: Security

JPS-20521: A simple target must have at least one resource action entry or permission set reference.

Cause: A simple target must have at least one resource action entry or permission set reference.

Action: Provide resource actions or permission sets.
Level: 1

Type: WARNING

Impact: Security

JPS-20600: MetaData-Provisioned is true, but no meta data found in policy object {0}.

Cause: MetaData-Provisioned is true, but no meta data found in policy object {0}.

Action: Check the policy store, make sure it is in an consistent state.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20601: Provided version "{0}" is invalid. Only alphabetic characters, digits, underscores, and dots are allowed.

Cause: Provided version {0} is invalid. Only alphabetic characters, digits, underscores, and dots are allowed.

Action: Provide a valid version.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20602: Provided meta data {0} is invalid. Reason: {1}

Cause: Provided meta data {0} is invalid. Reason: {1}.

Action: Provide a valid meta data.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-90600: Security Module with the configuration id {0} already exists.

Cause: Security Module with the configuration id {0} already exists.

Action: Provide a unique configuration id.
Level: 1

Type: WARNING

Impact: Security

JPS-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

27 MAPVIEWER-00001 to MAPVIEWER-09007

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 a local theme.

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 a JDBC theme.

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 the 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-00022: Config file not specified.

Cause: Configuration file name is undefined.

Action: Use a valid configuration file name.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00023: Cannot find or create data source.

Cause: Invalid data source parameters.

Action: Verify the correct parameters for data source.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00024: Query prohibited:

Cause: Invalid query.

Action: This type of query is not allowed for requested operation.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00025: Config file name was not specified.

Cause: Undefined configuration file.

Action: Use a valid configuration file.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00026: Cannot determine parent directory of mapViewerConfig.xml.

Cause: Invalid file path.

Action: Verify MapViewer's configuration file path.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00027: Cannot create default images directory:

Cause: Unable to create default directory for storing images.

Action: Verify path or permissions to create directory.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00028: Cannot create directory for mapBuilder images, because a file with the same name already exists.

Cause: A file with same name as directory exists.

Action: Verify if file can be removed.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00029: Cannot create directory for mapBuilder images.

Cause: Unable to create directory for storing MapBuilder images.

Action: Verify path or permissions to create directory.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00030: Error in creating Mappers.

Cause: Unable to create map objects for data source.

Action: Verify data source parameters.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00032: Cannot create image directory:

Cause: Unable to create directory for storing images.

Action: Verify path or permissions to create directory.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00033: Cannot add custom image renderer.

Cause: Invalid custom image renderer parameters.

Action: Verify custom image renderer parameters definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00034: Cannot create the javaDB data directory:

Cause: Unable to create directory for javaDB.

Action: Verify path or permissions to create directory.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00035: No jdbc_host in the datasource.

Cause: Missing data source host parameter.

Action: Add host parameter to data source definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00036: No jdbc_port in the datasource.

Cause: Missing data source port parameter.

Action: Add port parameter to data source definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00037: No jdbc_sid in the datasource.

Cause: Missing data source SID parameter.

Action: Add SID parameter to data source definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00038: No jdbc_user in the datasource.

Cause: Missing data source user name parameter.

Action: Add user name parameter to data source definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00039: No jdbc_password in the datasource.

Cause: Missing data source password parameter.

Action: Add password parameter to data source definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00040: Non-Spatial data provider must have a class attribute.

Cause: Missing attribute 'class' for non-spatial provider.

Action: Add 'class' attribute to non-spatial provider definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00041: Could not create log output stream.

Cause: Unable to create directory output log file.

Action: Verify path or permissions to create file.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00042: Error in fetching theme names.

Cause: Query to themes metadata view failed.

Action: Verify database connection and chekc log for details.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00046: Non-Spatial data provider must have an id attribute.

Cause: Missing attribute 'id' for non-spatial provider.

Action: Add 'id' attribute to non-spatial provider definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00047: Failure in registering Non-Spaital data provider:

Cause: Unable to create an instance of non-spatial provider class.

Action: Verify 'class' attribute value in non-spatial provider definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00048: Spatial data provider must have an id attribute.

Cause: Missing attribute 'id' for spatial provider.

Action: Add 'id' attribute to spatial provider definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00049: Failed in registering Spatial Data Provider:

Cause: Missing attribute 'id' for spatial provider.

Action: Add 'id' attribute to spatial provider definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00050: Cannot create default cache root directory:

Cause: Unable to create default tile cache directory.

Action: Verify path or permissions to create directory.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00051: Exception in creating default cache root directory:

Cause: Exception happened while creating default tile cache directory.

Action: See log for additional details.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00052: Invalid default cache root directory:

Cause: Default tile cache directory may already exits.

Action: Verify tile cache directory name.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00053: Timed out waiting for a free MapMaker.

Cause: Unable to get a free map object to render request.

Action: Increase number of map objects for data source in configuration file.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00054: Cannot connection to the datasource:

Cause: Unable to access data source.

Action: Verify data source connection parameters.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00058: MapRequest is not instantiated.

Cause: Null map request received.

Action: Verify process of sending map request to server.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00059: Oracle MapViewer FAILED to start.

Cause: MapViewer start process failed.

Action: See log for additional details.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00063: Request type is not recognized. It must be one of map_request, info_request, non_map_request, or wms_feature_info_request.

Cause: Invalid request type sent to mapViewer server.

Action: Verify the request string sent to server.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00064: Error in writing xml response to output stream.

Cause: Unable to send response back to client.

Action: See log for additional details.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00065: Cannot stream image data with unknown format.

Cause: Invalid or undefined map request image format.

Action: Define a supported image format in map request.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00073: Spatial data provider must have a class attribute.

Cause: Missing attribute 'class' for spatial provider.

Action: Add 'class' attribute to spatial provider definition.
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 the 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: Style does not exist.

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 predefined themes from the basemap.

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 unknown situation.

Action: See log for additional details.
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 highlight 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 built-in 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: Verify the possibility of using a server side call to transform coordinate.
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: Verify FOI request bounding box values. See log for additional details.
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: Provide a valid FOI request.
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: Verify the possibility of using supported geometry types.
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 an 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 the 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: Unknown 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

MAPVIEWER-07000: Data server streaming request validation error.

Cause: Request with invalid parameters or invalid condition.

Action: See log for additional details about the validation error. Possible actions: Verify if data source is defined. Look 'mds_config' tag in configuration file to check if data source streaming is set to true. For dynamic theme request, verify if data source streaming of dynamic data is allowed. For predefined theme request, verify if streaming of theme data is not disabled.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-07001: MapViewer server does not allow streaming access. Contact server administrator to check MapViewer configuration file.

Cause: Map data server configuration is undefined.

Action: Add 'mds_config' tag to MapViewer's configuration file.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-07002: Data source does not allow streaming access. Contact server administrator to check MapViewer configuration file.

Cause: Data source is not defined in 'mds_config' tag.

Action: Add data source tag in 'mds_config' and allow themes to be streamed. To allow predefined themes streaming set 'allow_predefined_themes" tag to true. To allow dynamic themes streaming set 'allow_dynamic_themes' tag to true.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-07003: Data source does not allow dynamic client queries.

Cause: Stremaing of dynamic theme data is not allowed.

Action: To allow dynamic themes streaming set 'allow_dynamic_themes' tag to true.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-07004: Theme cannot be streamed.

Cause: Streaming of predefined theme data is not allowed.

Action: To allow themes streaming set 'allow_predefined_themes" tag to true.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-07007: Error reading json data file.

Cause: Cannot access JSON data file.

Action: Verify if path to JSON file is correct.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-09001: Map tile layer not found. Check map tile layer name and/or data source name.

Cause: The tile layer name defined is not found.

Action: Make sure the tile layer exists for data source. Look user_sdo_cached_maps view.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-09006: Error occurred when sending request to data server.

Cause: MapViewer server may be down.

Action: See client log for additional details.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-09007: Cannot get data from data server.

Cause: Streaming of theme data may not be allowed.

Action: Verify settings in 'mds_config' tag of configuration file.
Level: 1

Type: ERROR

Impact: Process

28 MDS-00001 to MDS-92010

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 pre-existing 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: Element with local name = {0}, namespace = {1} is not expected under Parent Element = {2} in document location = {3}

Cause: While parsing a document, a request was made to locate a type definition whose usage is either not defined or is not expected for the parent element within the schema definition.

Action: Check the xml source and any customizations to be applied and ensure that the element with the given namespace is defined and in the correct location as specified by the schema definition.
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 customization 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 customization 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 {3}.

Cause: An attempt was made to read or write an invalid attribute value.

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 returned as a non-multitenant MDSInstance was requested with the current persistence configuration.

Cause: The configuration at the time the MDSInstance was requested did not match with the configuration when it was originally created.

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 MDSInstance was requested did not match with the configuration when it was originally created.

Action: Request an MDSInstance appropriate to the original configuration.
Level: 1

Type: ERROR

Impact: Session

MDS-00180: Only a single tenant cache configuration is allowed.

Cause: The number of TenantCacheConfigs was not 1.

Action: Pass a single tenant cache configuration object. Although the constructor for the TenantCacheConfigs class takes an array this is reserved for future use.
Level: 1

Type: ERROR

Impact: Session

MDS-00181: Only a single tenant document cache configuration is allowed.

Cause: The number of TenantDocumentCacheConfigs was not 1.

Action: Pass a single tenant document cache configuration object. Although the constructor for the TenantDocumentCacheConfigs class takes an array this is reserved for future use.
Level: 1

Type: ERROR

Impact: Session

MDS-00182: Tenant cache configuration information cannot be requested for the global tenant.

Cause: Tenant cache configuration information was being requested for the global tenant.

Action: Do not request the tenant cache configuration for the global tenant - use getCacheConfig directly from MDSConfig
Level: 1

Type: ERROR

Impact: Session

MDS-00183: Tenant document cache configuration information cannot be requested for the global tenant.

Cause: Multitenant document cache information was being requested for the global tenant.

Action: Do not request the tenant document cache configuration for the global tenant - use getDocumentCacheConfig from NamespaceConfig
Level: 1

Type: ERROR

Impact: Session

MDS-00184: The relationship from {0} to {1} is invalid because the latter is configured as a global resource and cannot be referenced from a tenant resource because the corresponding relationship is defined with cascade delete enabled.

Cause: Relationships with cascade delete enabled were spanning tenant boundaries.

Action: Reconfigure the relationship with cascade delete disabled or ensure the parent reference is within the same tenant scope.
Level: 1

Type: ERROR

Impact: Session

MDS-00185: The relationship from {0} to {1} is invalid because the latter is configured as a global resource and cannot be referenced from a tenant resource because the corresponding relationship is defined with enforced integrity.

Cause: Relationships with defined referential integrity were spanning tenant boundaries.

Action: Reconfigure the relationship without referential integrity or ensure the parent reference is within the same tenant scope.
Level: 1

Type: ERROR

Impact: Session

MDS-00186: A {0} element is already present in the parent {1} element in document {2}, but with the QNameLUID identification mechanism only one is allowed.

Cause: An attempt was made to have two or more elements with same QName under same parent while QNameLUID identification mechanism is used.

Action: Remove duplicate instances of elements with same QName
Level: 1

Type: ERROR

Impact: Data

MDS-00187: The existing {0} element in the parent {1} element in document {2} is automatically removed, and new customized {0} element of "{3}"/"{4}" customization layer is inserted since with the QNameLUID identification mechanism, only one is allowed.

Cause: An attempt was made to have two or more elements with same QName under same parent while QNameLUID identification mechanism is used.

Action: Removed duplicate instances of elements with same QName
Level: 1

Type: ERROR

Impact: Data

MDS-00188: The relationship from {0} to {1} is invalid because the latter is configured as a tenant resource and cannot be referenced from a global resource.

Cause: An attempt was made to reference a tenant resource from a global resource.

Action: Ensure all references from global resources are also global.
Level: 1

Type: ERROR

Impact: Session

MDS-00189: The existing {0} element with unique id {1} in the parent {2} element in document {3} is automatically removed, and new customized {0} element with unique id {1} of "{4}"/"{5}" customization layer is inserted since {0} element is type-annotated to overwrite duplicates.

Cause: An attempt was made to have two or more elements with same QName under same parent having the same unique ID value while overwriteDuplicate mechanism is used.

Action: Removed duplicate instances of elements with same QName having the same unique ID value
Level: 1

Type: ERROR

Impact: Data

MDS-00190: A call to {0} on the current MDSSession does not specify the correct transaction key

Cause: The current MDS Session was created using a transaction key and the subsequent operation was either being attempted passing no key or a different one from that originally used.

Action: If the MDS Session is created using a transaction key, then use the MDSSession API's that take a transaction key and use the same key.
Level: 1

Type: ERROR

Impact: Session

MDS-00191: An exception occurred in PChangeListener {0}

Cause: The MetadataStoreCommunicator was attempting to notify the listener when an exception occurred.

Action: Check the HandlePChanges method of the listener.
Level: 1

Type: ERROR

Impact: Session

MDS-00192: Validation of {0} caused a NullPointerException: check there is an MDS bean object set on the MDS bean MO

Cause: This error most typically occurs when a Bean MO has been created but no bean object has been set on it.

Action: Check that an MDS bean is set on this MO. Failing that, examine the stack for clues for alternative causes.
Level: 1

Type: ERROR

Impact: Data

MDS-00193: Document with the MDSReference {0} contains an ID attribute with an invalid value: {1}

Cause: The value of the ID attribute is invalid according to the schema definition.

Action: Ensure that the ID conforms to the schema definition .
Level: 1

Type: WARNING

Impact: Data

MDS-00194: Auditing is disabled for component {0}.

Cause: There was an error registering the audit event definition(s) for the component.

Action: Ensure that the audit event definitions for the component are valid and that the audit service is functional.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-00195: The custom audit event of type "{0}" that was associated with "{1}" is not audited because the MDS object was unmodified since the last time the changes in the MDSSession were committed.

Cause: MDS object associated with the event was unmodified since the last time the changes in the MDSSession were committed. A custom audit event is discarded if the associated MDSObject is not modified.

Action: No action required.
Level: 1

Type: WARNING

Impact: Programmatic

MDS-00196: The MDSSession referenced by the audit component "{0}" is invalid.

Cause: The MDS audit support instance is being used even after the MDSSession that was used to created it is no longer referenced.

Action: Fetch the audit support instance from the MDSSession and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00197: An internal error occurred when processing MetadataObject {0} with document {1}.

Cause: An error occurred in the LayeredCache processing.

Action: Check for log messages. If the problem persists, clear the MDS cache and contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Session

MDS-00198: The requested object is deleted in the current PTransaction

Cause: The requested document was deleted in an earlier part of the PTransaction and not replaced.

Action: Review whether the document needed to be deleted or replace with a new version.
Level: 1

Type: ERROR

Impact: Data

MDS-00199: The requested object is deleted in the current MDSSession

Cause: The requested document was deleted in an earlier part of the MDSSession and not replaced.

Action: Review whether the document needed to be deleted or replace with a new version.
Level: 1

Type: ERROR

Impact: Data

MDS-00200: Reference not found in Document

Cause: Unable to locate the reference within the named Metadata Object.

Action: Check that the reference is correct.
Level: 1

Type: ERROR

Impact: Data

MDS-00201: PDocument not found in MetadataStore : {0}

Cause: The requested persistence document was not found in the given MetadataStore.

Action: Check that the requested name is correct and that the store is mapped to the namespace correctly .
Level: 1

Type: ERROR

Impact: Data

MDS-00202: The Document was not found on the classpath

Cause: The requested document was not found on the classpath.

Action: Check that the document is available on the classpath as a resource .
Level: 1

Type: ERROR

Impact: Data

MDS-00203: An error occurred while attempting to process Element "{0}" from customization document {1} because the change conflicts with information in the base document or changes made by a prior customization

Cause: An error occurred during parsing of a customization - see cause.

Action: Check for any conflicts between the customization and recent changes to the base document or other customizations being applied.
Level: 1

Type: ERROR

Impact: Data

MDS-00204: Remove customization fails on element with local reference "{0}" in document "{1}"

Cause: An attempt to remove a customization from an element has failed.

Action: Reproduce the customization document without the desired customization.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00205: Unexpected error in ChangeEventParseEngine

Cause: An error in the ChangeEventParseEngine.

Action: Check for log messages. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00206: Unexpected error while collecting ElementTipCustInfo for a customized element

Cause: An error occurred while gathering ElementTipCustInfo for a customized element.

Action: Check for log messages. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00207: Cached Object {0} was removed from the MDS cache by thread {1} while being read. Retrying the read.

Cause: An object being accessed by MDS was removed from the cache before it could be used to return the requested data.

Action: The notification can occur if there are concurrent updates to objects cached by MDS. If the notification persists review the MDS cache configuration.
Level: 1

Type: NOTIFICATION

Impact: Session

MDS-00208: Root node deleted but not replaced.

Cause: The root node of an XML document was deleted, but no replacement node was inserted.

Action: Insert a replacement root node after deleting the root node.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00209: Exception adding logging data: " {0}".

Cause: An exception was raised in the MDS diagnostic log processing.

Action: Examine logs for the full exception stack and underlying cause.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00210: The TenantId supplied {0} does not match the current tenant context: {1}.

Cause: A TenantId was supplied to MDS that does not match the TenantId provided by the context.

Action: Remove the TenantId from the deprecated API or correct the TenantId supplied.
Level: 1

Type: ERROR

Impact: Session

MDS-00211: Action is not allowed on a tenant-specific MetadataStoreCommunicator.

Cause: An attempt was made to invoke a method that is not allowed on a non-global tenant

Action: This change has to be made in a global tenant context.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00212: Unable to execute a task in the DOMAIN partition in application {0} because the application in the DOMAIN partition is not currently in RUNNING state, or this is a Java SE application that has not initialized MDS in the DOMAIN context.

Cause: A task runner was required but unable to be found.

Action: Ensure that the MDS application lifecycle listener is configured, or that MDS is initialized in the global tenant context before running in any other tenant context.
Level: 1

Type: ERROR

Impact: Session

MDS-00213: It was not possible to lock the cached RootNode with root key {0}.

Cause: An error occurred in the LayeredCache processing due to cache contention on a specific object.

Action: Check for log messages. If the problem persists, clear the MDS cache and contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Session

MDS-00214: Error encountered while processing root node replacement customization instruction in tip customization layer document.

Cause: The customization instructions in tip customization document might be corrupted.

Action: Check for log messages. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00215: TenantId is not supported. Please use equivalent ServiceId api.

Cause: An attempt was made to invoke MDS deprecated APIs with TenantId.

Action: Replace TenantId based API with ServiceId based API.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00216: Notification Manager for MDSInstance {0} was unable to get an application scoped executor for dispatching events in the application context - using a global executor instead.

Cause: An attempt was made to get an application scoped executor outside of an application.

Action: Check if the request should be running within the scope of an application.
Level: 1

Type: WARNING

Impact: Session

MDS-00217: Notification Manager for MDSInstance {0} was unable to get an application scoped contextual proxy for dispatching global events in the tenant context - using a global contextual proxy instead.

Cause: An attempt was made to get an application scoped contextual proxy outside of an application.

Action: Check if the request should be running within the scope of an application.
Level: 1

Type: WARNING

Impact: Session

MDS-00218: Cannot create ServiceId with null Service UUID.

Cause: An attempt was made to create an MDS ServiceId with a null value.

Action: Check lifecycle-config.xml and ensure that each 'service' element contains an 'id' attribute defined with a UUID value.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00219: Invalid resource passed to MDSFaceletsHelper: {0}.

Cause: An invalid resource was passed to MDSFaceletsHelper.

Action: Check exception message. Consider enabling oracle.mds.jrf logging for additional diagnostics.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00220: Document {0} to be loaded does not exist for label {1}.

Cause: An attempt was made to load a persistent document using a URL but the underlying document was not found in the DB MetadataStore.

Action: Check that the document name is correct and that the DB MetadataStore and Label are correctly configured.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00221: Specified label {0} does not exist in {1} store.

Cause: The specified label did not exist in the metadata store.

Action: Verify that the label name is correct and that the label exists in the metadata store, and then retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00222: Invalid value "{0}" for {1} attribute (type = "{2}").

Cause: An attempt was made to read or write an invalid attribute value.

Action: Double-check the value and attribute type.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00223: Unable to retrieve pinned Customization Class value from Unified Sandbox For CustomizationClass : {0} with Name {1}.

Cause: An attempt was made to read a customization value with AutoMergeOverrideValue.PINNED, but no value was retreived from the Unified Sandbox.

Action: Ensure Unified Sandbox is able to return a pinned value for this Customization Class.
Level: 1

Type: ERROR

Impact: Runtime

MDS-00224: Customization of {0} Location: {1} is not permitted due to a package level restriction in the cust-restriction-library-config element of the mds-library-config.xml at jar/zip level.

Cause: A jar level restriction on customization has been specified for objects in this package in the cust-restriction-library-config element of the mds-library-config.xml file.

Action: Check if customization of this object should be allowed and correct the entries in cust-restriction-library-config at the jar/zip level.
Level: 1

Type: ERROR

Impact: Runtime

MDS-00225: Updating immutable StreamedObject "{0}" is not allowed.

Cause: The StreamedObject being updated was immutable.

Action: Ensure that the StreamedObject to be updated is mutable.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00226: Unable to determine the MDSContext while processing cached MDS content : {0}

Cause: An attempt was made to access an MDSContext but an MDSContext is not presently available to this thread.

Action: Check for logged diagnostic messages, clear the MDS cache and if the problem persists contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Runtime

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} Sub-object {0} in document {2} has invalid value "{1}" for unique identifier; typed dependencies from this sub-object 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 configured metadata store.

Action: Retry the operation. If the problem persists, verify that the document exists in the configured metadata store.
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 restricted to be used with MDS Transfer operation only. Reading or writing files in ArchiveMetadataStore is not supported outside 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 input/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 occurred.

Action: Look at the cause exception for more details and take action accordingly.
Level: 1

Type: ERROR

Impact: Data

MDS-00599: Cannot obtain a connection to the Archive Metadata Store for archive file {0}.

Cause: There was a problem obtaining a connection to the Archive Metadata Store.

Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00601: The XLIFF document has invalid target language {0}.

Cause: The target language specified was either null or empty.

Action: Specify a valid target language and retry the operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00703: The name {0} is not a valid name under package {1} because {2} resource not considered child of the package.

Cause: A specified child resource was not a child of the package.

Action: Specify a valid child resource name, and then retry the operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00704: invalid value {0} for property {1} on component {2}

Cause: An invalid property value was provided.

Action: Provide a valid property value and retry.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00771: A component with {0} "{1}" already exists.

Cause: The specified component already existed.

Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Data

MDS-00907: unable to save document "{0}" because either a document or package of the same name already exists

Cause: A document or package with the same name already existed in the repository, perhaps because it was just created by another user.

Action: Retry the operation. If necessary, choose another name for the object being saved.
Level: 1

Type: ERROR

Impact: Data

MDS-00908: unable to create package "{0}" because a document or package of the same name already exists

Cause: A document or package with the same name already existed in the repository, perhaps because it was just created by another user.

Action: Retry the operation. If necessary choose another name for the object being saved.
Level: 1

Type: ERROR

Impact: Data

MDS-00910: unable to save the document because of corrupt MDS database sequences or other internal errors.

Cause: The database sequence used for generating the unique document ID was corrupt or some other internal errors caused violation of unique constraints.

Action: Retry the operation after deploying metadata to another MDS database repository partition. If that still fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

MDS-00911: Document with name "{0}" and version {1} [Low CN={2}, High CN={3}] does not exist in the repository.

Cause: The document was not found in the MDS repository.

Action: Specify a correct name for the document and retry the operation. Check if the document is deleted by another user.
Level: 1

Type: ERROR

Impact: Data

MDS-00912: MDS repository is incompatible with the middle tier. Repository version "{0}" is older than minimum repository version "{1}" required.

Cause: The MDS repository was older than minimum version required by the middle tier.

Action: Upgrade the MDS repository to the required version.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-00913: MDS repository is incompatible with the middle tier. MDS version "{0}" is older than minimum MDS version "{1}".

Cause: The MDS version was older than the minimum required version for using the MDS repository.

Action: Upgrade the MDS library to the required version.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-00914: unable to save document "{0}" because either an already deleted document or package with conflicting name or type already exists

Cause: A document or package with the same name or a parent package of incorrect type already existed in the repository as a deleted version.

Action: Delete the conflicting resource from repository or check if the new resource is invalid. If necessary, choose another name for the object being saved.
Level: 1

Type: ERROR

Impact: Data

MDS-00915: MDS repository is incompatible with the middle tier for dumping or restoring metadata.

Cause: The MDS repository was older than minimum version required by the middle tier to dump or restore metadata.

Action: Retry the operation after upgrading the MDS repository to newer version or use compatible middle tier to perform the operation.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-00916: MetadataStore configured for {0} does not support deployment management.

Cause: The metadata store configured for the resource did not support deployment management.

Action: Deployment management is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00918: Connection details for the MDS repository are incomplete. The values for "{0}" are invalid

Cause: The MDS repository connection details were invalid or missing.

Action: Specify correct values for the MDS repository details in the configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00919: Internal error: The database context for this repository appears to be corrupt.

Cause: The database context was invalid.

Action: Verify that the repository details are correct in the configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00922: The ConnectionManager "{0}" cannot be instantiated.

Cause: There was an error instantiating the ConnnectionManager class

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

MDS-00923: Unable to create sandbox "{0}"

Cause: An error occurred during creation of sandbox.

Action: Look in the error message log for the exact reason for the failure.
Level: 1

Type: ERROR

Impact: Data

MDS-00928: Invalid document reference, package "cust" should appear before package "trans" in the names of customization translation documents.

Cause: An internal MDS document (one in package mdssys) was found with an invalid name, or an attempt was made to create a name object with such an invalid name.

Action: Avoid using package or document names containing path element "mdssys" which is reserved for internal MDS use. If necessary, remove such invalid documents from the metadata store.
Level: 1

Type: ERROR

Impact: Data

MDS-00929: unable to look up name "{0}" in JNDI context

Cause: The implementation class to use for initial context was not found.

Action: Verify that environment properties are configured using system properties or application resources files.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00930: The JNDI location details for the registered datasource are incomplete.

Cause: JNDI location details were found to be incomplete.

Action: Provide complete JNDI location information in the configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00931: The database version is {0}.{1}, but MDS requires at least {2}.{3}.

Cause: The database version is older than the minimum database version required for hosting MDS repository.

Action: Upgrade the database to the minimum required version. Contact the database administrator for assistance.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-00932: unknown database vendor {0}

Cause: The database vendor could not be identified.

Action: Verify that the MDS repository is hosted on supported database vendors.
Level: 1

Type: ERROR

Impact: Installation

MDS-00933: cannot create data source using URL "{0}"

Cause: An error occurred while creating the data source using the specified URL.

Action: Verify that the URL specified is correct and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00934: XDB is not supported on database platform {0}.

Cause: An attempt was made to store XML metadata in a non-XDB database.

Action: Verify that the correct MDS repository is being used.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00935: Unable to complete operation even after maximum connection retries ({0}).

Cause: An error occurred while performing operation.

Action: Ensure that the database is running. Retry the operation later.
Level: 1

Type: ERROR

Impact: High Availability

MDS-00936: Fast Connection Failover is not supported on the underlying database connection ({0}).

Cause: The underlying database connection did not support fast connection failover, and retry-connection was set to true in either the config file, or programmatically.

Action: Either stop and then restart the database connection and configure it to allow fast connection failover, or do not attempt to set retry-connection to true.
Level: 1

Type: ERROR

Impact: High Availability

MDS-00937: A local transaction operation like commit or rollback cannot be used in a global transaction on connection "{0}".

Cause: The database connection was configured for global transactions, but MDS was not configured to support global transactions.

Action: Reconfigure the database connection to use local transactions. Change "tx-level" attribute on the MDS datasource to "local".
Level: 1

Type: ERROR

Impact: Configuration

MDS-00938: Unable to get an ADF library class loader

Cause: MDS expects to retrieve a resource from an ADF library, but is unable to obtain an ADF library classloader.

Action: Consider whether the resource should be repackaged in an ADF library rather than an ordinary jar.
Level: 1

Type: ERROR

Impact: Data

MDS-01059: document with the name {0} missing in the source metadata store

Cause: The document to be transferred did not exist in the source metadata store.

Action: Verify that the document name is correct, and that it exists in the source metadata store.
Level: 1

Type: ERROR

Impact: Data

MDS-01061: Listener {0} cannot be instantiated.

Cause: The listener class did not exist.

Action: Verify that the name of the listener class is correct. Ensure that the class is available on the class path.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01104: finding no documents for processing that match the pattern provided

Cause: No documents were found on the source metadata store that matched the pattern provided, or that matched the document name.

Action: Provide another pattern or document name, or provide another metadata store in which to look for the documents.
Level: 1

Type: ERROR

Impact: Data

MDS-01105: invalid label {0}

Cause: The label specified for the source metadata store did not exist.

Action: Verify that the label name is correct, or provide a label that exists in the source metadata store.
Level: 1

Type: ERROR

Impact: Data

MDS-01106: The TransferTypeRestriction {0} cannot be associated with given TransferType {1}.

Cause: The given TransferTypeRestriction cannot 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 at least 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 special document name.
Level: 1

Type: ERROR

Impact: Data

MDS-01123: The metadata path "{0}" specified in the mds-transfer-config.xml to preserve user updated documents in target repository is not a valid metadata path.

Cause: The metadata path specified in /meta-inf/mds-transfer-config.xml to preserve the user updated documents in target repository is not a valid metadata path.

Action: Make sure the metadata path specified in mds-transfer-config.xml is a valid metadata path.
Level: 1

Type: ERROR

Impact: Data

MDS-01150: Reference is null or empty.

Cause: A reference value was null or empty.

Action: Use a valid reference value that is not empty or null.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01151: Id/LocationPath reference is null or missing.

Cause: An Id/LocationPath reference value was null or empty.

Action: Use a valid Id/LocationPath reference value that is not empty or null.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01153: invalid LocationPath expression "{0}"

Cause: The LocationPath expression was invalid.

Action: Use a valid LocationPath format. The LocationPath expression should follow the format "/text()" or "/text()[x]", where 'x' is the index of "text block".
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01154: invalid LocationPath expression "{0}"

Cause: The node index in the LocationPath expression was invalid.

Action: Change the node index in the LocationPath expression to a number greater than or equal to 1.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01158: Expecting a base document. Reference "{0}" is a special document.

Cause: A base document was expected, but the reference was a special document.

Action: Use a valid base document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01159: Expecting absolute document reference. Reference "{0}" has local element reference portion.

Cause: The supplied reference was not the expected type.

Action: Ensure the reference is of the expected type.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01160: Expecting absolute document reference. Reference "{0}" is a relative reference to the document.

Cause: The supplied reference was not the expected type.

Action: Ensure the reference is of the expected type.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01161: Reference "{0}" has an invalid character "{1}".

Cause: The supplied reference did not follow the MDS naming standard.

Action: Use valid characters for the reference.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01162: Reference "{0}" has an invalid XML attribute character.

Cause: The supplied reference did not follow the MDS naming standard.

Action: Use valid characters for the reference.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01163: invalid reference "{0}"

Cause: The supplied reference did not follow the MDS naming standard.

Action: Ensure that the reference follows the MDS naming standard.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01164: invalid reference "{0}" for a translation document

Cause: The supplied reference did not have the expected document extension (.xlf).

Action: Use the correct extension, .xlf, for the translation document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01165: invalid reference "{0}" for a customization document

Cause: The supplied reference did not have the expected document extension (.xml).

Action: Use the correct extension, .xml, for the customization document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01166: invalid reference "{0}" for a metadata extension document

Cause: The supplied reference did not have the expected document extension (.rdf).

Action: Use the correct extension, .rdf, for the metadata extension document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01167: There is no namespace declaration for the prefix "{1}" used in LocationPath expression "{0}".

Cause: The LocationPath expression was incomplete.

Action: Use a valid LocationPath format.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01168: Partition name "{0}" starts or ends with character "{1}". Partition name cannot contain leading or trailing spaces, ".", "-"

Cause: The supplied partition name contained leading or trailing spaces, ".", "-".

Action: Ensure that the partition name follows the MDS naming standard for partitions.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01169: Partition name "{0}" has an invalid character "{1}".

Cause: The supplied partition name did not follow the MDS naming standard.

Action: Use valid characters for the partition name.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01170: Partition name is null or empty.

Cause: Partition name value was null or empty.

Action: Use a valid partition name that is not empty or null.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01171: The ID prefix generated by concatenating the layer name "{0}" and layer value "{1}" is not a valid MDS ID.

Cause: The ID prefix generated by concatenating the layer name with layer value did not follow the MDS ID naming standard.

Action: Ensure that the ID prefix generated by concatenating the layer name with layer value follows the MDS ID naming standard.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01200: This operation is not supported.

Cause: An MDS query operation was attempted, but this particular operation is not supported.

Action: Note the stack backtrace and context of the operation, and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01201: An invalid parameter cannot be used when constructing a query condition.

Cause: An invalid parameter was passed to the class ConditionFactory.

Action: Note the stack backtrace and context of the operation, and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01205: A SQL error is occurring when performing the query: "{0}" with binds {1}.

Cause: An MDS query on a database store led to a SQL error.

Action: Note the stack backtrace and context of the operation, including the reported SQL query and error, and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01206: The array size for the query must be greater than zero.

Cause: An MDS query specified a fetch unit size that was not positive.

Action: Note the stack backtrace and context of the operation and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01207: The namespace mapping for the prefix "{0}" specified in the location path, is missing.

Cause: During XPath evaluation, the namespace prefix was used, but the prefix was not mapped to a namespace.

Action: Note the stack backtrace and context of the operation and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

MDS-01208: MDS query condition produces more than {0} characters of SQL where clause.

Cause: An MDS query condition was so large that it would produce a very large SQL statement.

Action: Note the stack backtrace and context of the operation, and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01250: The file path "{0}" does not exist.

Cause: An invalid path was provided.

Action: Retry the operation with a valid file path.
Level: 1

Type: ERROR

Impact: Files

MDS-01251: The parameter file {0} has no namespace on the document element.

Cause: A namespace was missing from the parameter file provided.

Action: Provide a parameter file with valid namespace information.
Level: 1

Type: ERROR

Impact: Data

MDS-01252: The parameter file {0} must have either {1} or {2} definition.

Cause: No source stores or target stores information were provided in the parameter file.

Action: Check the parameter file to have source and target store information and retry.
Level: 1

Type: ERROR

Impact: Data

MDS-01253: The parameter file {0} must not have both {1} and {2} definitions.

Cause: An attempt was made to transfer from source directory to target directory. Both source and target as directories is not supported.

Action: Provide correct source and target definition. Either source or target should be a metadata store.
Level: 1

Type: ERROR

Impact: Data

MDS-01254: The parameter file {0} contains same store definition for sourceStore and targetStore.

Cause: An attempt was made to transfer from and to the same store. The definition for sourceStore cannot be the same as the definition for targetStore.

Action: Provide correct source and target information. Change either source or target store definition.
Level: 1

Type: ERROR

Impact: Data

MDS-01255: The property {0} has not been supplied.

Cause: The required property was missing from the parameter file.

Action: Check the parameter file and supply the required property. Refer to the MDS documentation for the correct syntax. A sample parameter file is also part of documentation.
Level: 1

Type: ERROR

Impact: Data

MDS-01258: The value {0} for property {1} is invalid.

Cause: An invalid property value was provided in the parameter file.

Action: Provide a valid property value. Refer to the MDS documentation for the correct syntax. A sample parameter file is also part of documentation.
Level: 1

Type: ERROR

Impact: Data

MDS-01259: The metadata store "{0}" cannot be instantiated.

Cause: An error occurred during the instantiation of the class for the metadata store.

Action: Verify that correct values are provided in the parameter file. Refer to the error messages in application logs that describe the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Data

MDS-01260: failure to process command-line arguments

Cause: Invalid command-line parameters were provided.

Action: Provide valid command-line parameters, and retry the operation. Refer to the MDS documentation for syntax of the tool parameters, or run the tool without parameters in order to get the Help message.
Level: 1

Type: ERROR

Impact: Data

MDS-01262: failure of transfer operation on a read-only target metadata store

Cause: The target metadata store used for transfer was read-only, for example a classpath store.

Action: Provide a writable target metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01263: operation failure on the resource {0} because source metadata store is read-only

Cause: An attempt was made to delete, create, update or get a mutable metadata object from a read-only source metadata store.

Action: Provide a writable source metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01264: The given element must contain either "customization" or "translation" configuration.

Cause: A customization or a translation configuration was missing for an element.

Action: Examine the transfer parameter file for valid MDS configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01265: Invalid parameter file {0}. Reason: <{1}:{2}> {3}

Cause: Parameter file provided was not valid.

Action: Provide a valid parameter file. Refer to the MDS documentation for the correct syntax. A sample parameter file is also part of documentation. Refer to sample parameter for correct syntax.
Level: 1

Type: ERROR

Impact: Files

MDS-01266: The associated customization document is missing for a given customization class {0} for the given document name {1}.

Cause: The associated customization document for the given customization class did not exist.

Action: If the associated customization document was to be transferred, verify that it exists. Otherwise, no action is required.
Level: 1

Type: ERROR

Impact: Data

MDS-01267: The associated translation document is not found for a given locale {0} for the given document name {1}.

Cause: Associated translation document did not exist for the given locale.

Action: If the associated translation document was expected to be transferred, verify if it exists, otherwise, no action required.
Level: 1

Type: ERROR

Impact: Data

MDS-01268: The associated extended metadata document for the given document name {0} is missing.

Cause: No associated extended metadata document for the given document name existed.

Action: If the document was to be transferred, verify that the document exists. Otherwise, no action is required.
Level: 1

Type: ERROR

Impact: Data

MDS-01270: Opening and closing parentheses do not match.

Cause: Either an opening or closing parentheses was missing.

Action: Check and correct the namespace mappings provided. Each opening parentheses should have an equivalent closing parentheses and vice versa.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01271: Cannot get the dependency registry

Cause: An error occurred while getting the dependency registry.

Action: Retry the operation. If the problem persists, look for messages that describe the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01272: unable to read mds-webapp-config.xml file

Cause: The mds-webapp-config.xml file was invalid.

Action: Confirm that the mds-webapp-config.xml file for the application is well formed, and valid.
Level: 1

Type: ERROR

Impact: Files

MDS-01273: The operation on the resource {0} failed because source metadata store mapped to the namespace {1} is read only.

Cause: An attempt was made to delete, create, update or get a mutable metadata object from a readonly source metadata store.

Action: Provide a writable source metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01301: Element "{1}", namespace "{0}" is not a valid child under parent "{3}", namespace "{2}".

Cause: An attempt was made to add, insert or replace a child element of the wrong type.

Action: Check the schema definition and ensure that the child element is the correct type.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01302: failure to load schema file "{0}"

Cause: An exception occurred in the XMLEF layer during processing of the schema definitions.

Action: Look for messages that describe the cause exception, and then take the appropriate action.
Level: 1

Type: ERROR

Impact: Data

MDS-01303: failure to register grammar from schema file "{0}"

Cause: An exception occurred in the XMLEF layer during addition of schema definitions.

Action: Look for messages that describe the cause exception, and then take the appropriate action.
Level: 1

Type: ERROR

Impact: Data

MDS-01305: failure to locate schema file "{0}".

Cause: The schema definition file was not found.

Action: Verify that the schema file name is correct, and that it is in the correct location.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01306: Grammar from a Web application can be added only once.

Cause: There were multiple method calls to add grammar from a web application.

Action: Verify that a grammar definition has already been added for the given MDSInstance and ServletContext. If it has then remove the calls to add it multiple times.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01307: no schema files for processing

Cause: No schema files were found against which beans can be generated.

Action: Pass an existing schema file to the bean generator.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01308: Event "{0}" is not supported.

Cause: An attempt was made to use event types that are not supported for the selected content model.

Action: Use only the event types that are allowed for the selected content model.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01309: ContentModelPipeline is empty.

Cause: The contentModelPipeline contained an empty or null builder list.

Action: A list of one or more valid builders must be available in the ContentModelPipeline.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01310: Invalid ContentModelPipeline. Missing {0}.

Cause: The expected builder was not available in builder list of the ContentModelPipeline.

Action: Valid builders must be supplied to the ContentModelPipeline.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01311: The DOM tree does not support the DOM event model.

Cause: This DOM Document did not implement EventTarget interface.

Action: Verify whether the Oracle XML Developer's Kit is used.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01312: Change-list transaction state is invalid.

Cause: The current change-list transaction state is invalid for the customization operation performed.

Action: Ensure Change-list to be in valid transaction state to perform the necessary customization operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01313: The argument for document cannot be null.

Cause: The argument for DocumentName was null.

Action: Provide a valid DocumentName.
Level: 1

Type: ERROR

Impact: Data

MDS-01314: TypeAnnotationProvider cannot be null.

Cause: The argument for TypeAnnotationProvider was null.

Action: Provide a valid TypeAnnotationProvider.
Level: 1

Type: ERROR

Impact: Data

MDS-01316: Support for XPath is not implemented yet.

Cause: Support for XPath has not been implemented yet.

Action: Provide a valid Configurable ID.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01319: JAXP support is not available. Falling back to using Oracle XML Developer's Kit for parsing the document {0}.

Cause: JAXP support was not available.

Action: None.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01320: Modifying the prefix declaration for {0} from "{1}" to "{2}" in document {3} through customizations is not supported.

Cause: An attempt was made to change an existing prefix declaration.

Action: Avoid attempts to change existing prefix declarations.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01321: Node type should be one of ImmutableModelNode.ELEMENT or ImmutableModelNode.TEXT or ImmutableModelNode.CDATA.

Cause: The node was not of the type ImmutableModelNode.ELEMENT or ImmutableModelNode.TEXT or ImmutableModelNode.CDATA.

Action: Ensure the node type is one of the following types: ImmutableModelNode.ELEMENT or ImmutableModelNode.TEXT or ImmutableModelNode.CDATA.
Level: 1

Type: ERROR

Impact: Data

MDS-01322: Value "{0}" does not satisfy "{1}" type.

Cause: The data type conversion failed.

Action: Verify that the expected XSD built-in simple data type and the passed-in string value are convertible.
Level: 1

Type: ERROR

Impact: Data

MDS-01323: Value "{0}" has an incorrect number of characters for a base64Binary.

Cause: The value did not represent a valid Base64Binary.

Action: Verify that the input value is valid.
Level: 1

Type: ERROR

Impact: Data

MDS-01324: Unknown XML schema built-in type "{0}"

Cause: An attempt was made to use an unknown XML schema built-in type.

Action: Use only valid XML schema built-in types.
Level: 1

Type: ERROR

Impact: Data

MDS-01325: unable to load type definition "{0}"

Cause: Could not load this type definition because the specified location did not exist.

Action: Ensure that the specified location for the type definition exists.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01326: Loading of type definition from element "{0}" is not supported.

Cause: An attempt was made to load a type definition from the specified element that is not supported in the MDS configuration.

Action: Examine the schema definition to ensure that the entry specified in type definition is correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01327: unable to load data from "{0}" into {1}

Cause: An error occurred while loading the content of this configuration element.

Action: Examine the schema definition to ensure that the content of this configuration element is correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01328: unable to load element "{0}" into {1}

Cause: An error occurred while loading this configuration element.

Action: Examine the schema definition to ensure this configuration element is correctly specified in the MDS configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01329: unable to load element "{0}"

Cause: An error occurred while loading this configuration element.

Action: Examine the schema definition to ensure this configuration element is correctly specified in the MDS configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01330: unable to load MDS configuration document

Cause: An I/O or parsing error occurred while loading the MDS configuration document.

Action: Verify that the URL is correct, and ensure that the document contains valid MDS configuration information.
Level: 1

Type: ERROR

Impact: Files

MDS-01331: unable to load MDS configuration document "{0}"

Cause: An error occurred in loading the content of MDS configuration document.

Action: Verify that the URL is correct, and ensure that the document contains valid MDS configuration information.
Level: 1

Type: ERROR

Impact: Files

MDS-01332: Class {0} is not a subclass or implementation of {1}.

Cause: The class specified in the configuration information did not extend the required class, or implement the required interface.

Action: Ensure that the class specified in the configuration information extends the correct class, or implements the correct interface.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01333: missing element "{0}"

Cause: This element was missing from the MDS configuration information.

Action: Ensure that the element is specified in the configuration information.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01334: missing element "{0}" in document "{1}"

Cause: This element was missing from the MDS configuration information.

Action: Ensure that this element is specified in the configuration document.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01335: namespace "{0}" mapped to metadata-store-usage "{1}" but its definition was not found in MDS configuration.

Cause: Metadata-store-usage element that was referenced by a namespace not found in MDS configuration.

Action: Ensure that this element is specified in MDS configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01336: No XML element is provided to create {0}.

Cause: A null XML element was passed to the constructor of this configuration object.

Action: Ensure that a valid XML element is provided to create a new instance of this configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01337: No URL is provided to create {0}.

Cause: A null URL was passed to the constructor of this configuration object.

Action: Ensure that a valid URL is provided to create a new instance of this configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01340: More than one metadata store can be resolved for the namespace "{0}".

Cause: There were multiple namespace to metadata store mappings in the persistence configuration that satisfied the request for the metadata store of a given namespace.

Action: Correct the namespace mapping in persistence configuration to ensure that the namespace is mapped to only one metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01341: Namespace mapping for "{0}" is overridden by namespace mapping for "{1}"; and they conflict.

Cause: A conflicting mapping to this namespace has already been defined in the persistence configuration.

Action: Correct 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 repository: "{0}".

Cause: MetadataStore was scheduled for auto-purge after the MDSInstance was released

Action: Try later and contact support if persists.
Level: 1

Type: WARNING

Impact: Other

MDS-01363: Failed to lookup datasource with JNDI name "{0}" configured for the DBMetadataStore, defaulting to use ClassPathMetadataStore.

Cause: Application was configured with DBMetadataStore using JNDI datasource and JNDI lookup failed when running outside application server.

Action: No action required if defaulting to ClasspathMetadataStore is acceptable. Otherwise, use appropriate configuration such as FileMetadataStore.
Level: 1

Type: WARNING

Impact: Configuration

MDS-01364: Namespace mapping for "{0}" is ovelapping with namespace mapping for "{1}"; the first mapping is redundant.

Cause: Redundant Namaspace mappings defined in the persistence configuration.

Action: Correct persistence configuration to ensure that there is no overlapping rundudant mappings.
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 environment 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 cannot be securely processed.

Cause: ADF security configuration was not found in the config file.

Action: Set the password using JDeveloper to ensure required configuration is generated.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01373: unable to retrieve password.

Cause: unable to retrieve the password due to exception in security layer.

Action: See message of the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01374: unable to save password.

Cause: unable to save the password due to exception in security layer.

Action: See message of the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01375: No password defined for DBMetadataStore in configuration file or in the wallet file.

Cause: DBMetadataStore uses JDBC based configuration but no password specified.

Action: Set the password for the DBMetadataStore using JDeveloper.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01376: Unable to get database connection from data source "{1}" configured with JNDI name "{0}".

Cause: Failed to retrieve a database connection from the data source either because the data source is not configured correctly or the database details are not correct.

Action: Test the data source to check if it is correctly configured and if the database can be accessed. See message of the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01377: Unable to get database connection from data source configured with JNDI name "{0}".

Cause: Failed to retrieve a database connection from the data source either because the data source is not configured correctly or the database details are not correct.

Action: Test the data source to check if it is correctly configured and if the database can be accessed. See message of the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01378: metadata-store-usage attribute should not be set on namespace "{0}" defined in mds-config.xml.

Cause: metadata-store-usage attribute was set on the specified namespace in mds-component-config, but this namespace is always assumed to map to deploy-target metadata store.

Action: Ensure that the metadata-store-usage attribute is removed on specified namespace in mds-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01379: Tenant scope "{0}" is not valid for namespace "{1}" with namespace restriction "{2}".

Cause: Tenant scope configured for the namespace is not supported with the configured namespace restriction.

Action: Resolve the conflict between tenant scope and namespace-restriction in the application configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01380: Tenant scoped base metadata in package "{0}" can not have global customization layer "{1}".

Cause: Tenant scope GLOBAL on the specified customization layer conflicts with tenant scope TENANT on the base namespace.

Action: Resolve the conflicts between the tenant scope on the base namespace and that on the customization layer.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01381: Customization layer "{0}" has been configured more than once with the same tenant scope.

Cause: Duplicate configuration for the same customization layer was found.

Action: Remove the duplicate customization layer configuration from adf-config.xml of the application or component config (mds-config.xml) on classpath.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01382: Customization layer "{0}" has been configured more than once with conflicting tenant scopes.

Cause: Conflicting tenant scope configurations was found for the same customization layer.

Action: Remove the incorrect customization layer configuration from adf-config.xml of the application or component config (mds-config.xml) on classpath.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01383: Sandbox name should be provided for registering a sandbox change listener.

Cause: No sandbox name was provided for registering the sandbox change listener.

Action: Provide a valid sandbox name when registering the sandbox change listener.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01384: Sandbox change listener is not found when registering the lifecycle listener for sandbox {0}.

Cause: The SendboxChangeListener being registered was null.

Action: Provide a valid sandbox change listener when registering the lifecycle listener for the sandbox.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01385: Tenant scope "{0}" as base tenant scope is not valid for namespace "{1}".

Cause: The specified tenant scope type could not be configured as base tenant scope for the namespace.

Action: Use the correct base tenant scope parameter to create the namespace.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01386: Multitenant application can not be configured with metadata store "{0}" that does not support multitenancy.

Cause: A metadata store that does not support multitenancy was configured for a multitenant enabled application.

Action: Configure a metadata store such as DBMetadataStore that supports multitenancy.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01387: Tenant with id "{0}" is not allowed to change the autopurge settings; only the global admin can change this configuration.

Cause: A tenant cannot change the autopurge configuration..

Action: Only a global admin can change the autopurge configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01388: Unable to set cache size to {0} KiloBytes.

Cause: The cache size requested was invalid either because it was negative or it was too large for the Java Object Cache.

Action: Check that the specified size is >0 and within the limit for the cache implementation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01389: ContentType can not be specified for Streamed documents.

Cause: Conflicting settings between ContentType and isStreamed were found in ContentConfig.

Action: Change ContentOptions to use either ContentType or isStreamed.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01390: An audit event name for component "{0}" is not specified.

Cause: An audit event was defined, but a name for the event was not specified.

Action: Give the audit event a valid name.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01391: "{0}" is not a valid audit event name.

Cause: An invalid audit event name was found. An audit event name should start with a letter and contain only letters and digits.

Action: Specify a valid name for the audit event.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01392: Conflicting definitions were found for the audit event with name "{0}" and audit-component "{1}".

Cause: Conflicting audit event definitions were found in audit-component element.

Action: Remove or modify one of the conflicting audit events.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01393: Multiple audit events named "{0}" are defined for component "{1}".

Cause: Duplicate audit events were found in audit-component element.

Action: Remove or modify one of the duplicate audit events.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01394: The repository-name property element is not specified for a metadata-store element that does not have the class-name property.

Cause: The repository-name property element was not specified for a metadata-store element. It is required when the class-name property is not specified on the metadata-store element to support look up of the repository details.

Action: Specify the repository name in a child property element of the metadata-store element or specify the class-name property for the metadata-store element in the configuration file.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01395: Unable to look up the details of the specified repository {0} for the metadata-store configuration.

Cause: The specified repository was not registered in the domain or the repository was not configured properly.

Action: Ensure that the specified repository for the metadata-store is configured and registered properly in the domain.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01396: metadata-store-usage attribute is not set on namespace "{0}" defined in mds-config.xml.

Cause: metadata-store-usage attribute was missing on the specified namespace in mds-component-config.

Action: Ensure that the metadata-store-usage attribute is set on the specified namespace in mds-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01397: Multiple audit events with display name "{0}" are defined for component "{1}".

Cause: More than one audit event was found with the same display name in audit-component element.

Action: Ensure that the display names are unique for all audit events of a component.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01398: Namespace "{0}" is mapped to both metadata store "{1}" and metadata store "{2}".

Cause: There were multiple metadata stores mapped to a given namespace in the persistence configuration.

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-01399: A DBMetadataStore store is being registered with a PManager with multitenant enabled set to {1} but an equal store is already registered with a PManager with multitenant enabled set to {0}.

Cause: The DBMetadataStore store being registered cannot be used for both multitenant and non multitenant operations at the same time.

Action: Ensure that the same physical store is not used for both multitenant and non multitenant operations.
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: Updating immutable MetadataObject "{0}" is not allowed.

Cause: The MetadataObject being updated was immutable.

Action: Ensure that the MetadataObject to be updated is mutable.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01403: Updating a mutable MElement in MetadataObject "{0}" using an immutable MElement: "{1}" 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 object {0} cannot be deleted because of relationship integrity constraints.

Cause: An attempt was made to delete an object that was still being referenced.

Action: Remove the child references to the metadataObject so that it can be deleted.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01614: Rename is not allowed because integrity checking is not turned on in the object {1} in MetadataObject {0}.

Cause: Integrity checking was switched off so it was not possible to check whether the rename would have broken any relationship integrity constraints.

Action: Ensure that integrity checking is turned on.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01615: failure to rename {0} because there is no reference attribute in MetadataObject {1}, element {2}

Cause: A child object could not reference the renamed object as its current reference was invalid.

Action: Confirm that all the references in the child object are valid.
Level: 1

Type: ERROR

Impact: Data

MDS-01620: The untyped dependency with the following registration details cannot be inserted: {0}, {1}, {2}, {3}.

Cause: The dependency could not be registered in the database repository due to a SQL exception.

Action: Correct the cause of the SQL exception and retry the untyped dependency registration.
Level: 1

Type: ERROR

Impact: Data

MDS-01621: The untyped dependency information for {0} could not be removed.

Cause: An attempt to remove untyped dependency information failed either because the document was invalid or there was a SQL exception.

Action: Verify that the document and its dependencies are valid, or correct the cause of any SQL exceptions.
Level: 1

Type: ERROR

Impact: Data

MDS-01622: There is no analyzer to unregister.

Cause: No analyzers were supplied to be unregistered.

Action: Supply the DependencyAnalyzer to be unregistered.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01630: invalid operation in a customized context on an element that could participate in a relationship: {0}

Cause: Within a customized context there was an attempt to insert an element without first deleting it as part of a composite move.

Action: Within the customized context, do not attempt inserts on elements without first deleting them as part of a composite move.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01631: In a customized context, an element that could participate in a relationship as a child cannot be modified. The reference is {0} on {1}.

Cause: Within a customized context, an attribute being customized could have been a parent reference within a relationship.

Action: Do not attempt to modify or remove an attribute that could be a parent reference within a relationship.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01633: In a customized context, an element that could participate in a relationship cannot be deleted: {0}.

Cause: Within a customized context an attempt was made to delete an element that could participate in a relationship.

Action: Do not attempt to delete an entity while in a customized context.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01634: In {0}, a {1} element that participates in a relationship lacks a configurable ID.

Cause: An operation was attempted on a participant in a relationship that lacked a configurable ID.

Action: Add a configurable ID to the element on which it is missing. If necessary, refer to the element's schema definition to identify the configurable ID attribute.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01635: Skipping the relationship validation for {0} in the metadata object {1} because the element contains an invalid MDS reference.

Cause: Validation of the object's relationships was not performed because the element contained an invalid MDS reference.

Action: Correct the MDS references in the MetadataObject specified.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01700: MElementBeanImpl._setSimpleChild cannot be called on a non-simpleType element: name={0}, namespace{1}

Cause: An attempt was made to set a bean element to a simple type, but the definition in the schema was not a simple type. The generated beans may not have matched the registered schema.

Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01701: Cannot set the value on an element that is not based on a simpleType: name={0}, namespace={1}

Cause: An attempt was made to set an element to a simple type, but the definition in the schema was not a simple type.

Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01702: The method getBean() is not valid for metadata object {0} - it is allowed on only bean metadata objects.

Cause: An attempt was made to access the metadata object using the bean API but the metadata object was not a bean metadata object. The schema for the root element may not have been registered with MDS, or the beans were not available on the classpath.

Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01703: error unmarshalling bean element: name={0}, namespace={1} in metadata object {2} - no object factory can be found or jaxb.properties cannot be found

Cause: An element was found in the metadata object that did not have a corresponding bean class. The schema for the element may not have been registered with MDS, or the beans were not available on the classpath.

Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01705: error unmarshalling bean element: name={0}, namespace={1} in metadata object {2} - object factory class {3} does not have the expected unmarshal() method

Cause: The bean object factory found for the element did not appear to have been generated by the MDS bean generation tool.

Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.
Level: 1

Type: ERROR

Impact: Data

MDS-01706: error unmarshalling bean element: name={0}, namespace={1} in metadata object {2} - object factory class {3} failure in unmarshal() method

Cause: An unexpected exception occurred while creating a bean object for the element.

Action: Contact the developers of the application, providing the cause exception.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01707: Error generating relationship method {0} for relationship defined on attribute {1}: incorrect parentType definition

Cause: There was an error in the relationship definition.

Action: Check the parentType definition on the relationship
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01708: No schema definition found in namespace "{0}" for element of type "{1}". {2} will not be retrievable as an MDS Bean MO.

Cause: The schema for the generated MDS bean is not found.

Action: Add the schema for this namespace and element type to the type definitions for the MDSInstance.
Level: 1

Type: WARNING

Impact: Configuration

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} cannot 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 published to mainline. The undo/finalize 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 either being refreshed or applied and is in intermediary state. No further updates except sandbox finalize/undo operation are allowed.

Cause: The sandbox is in intermediary state and no further updates can be done to the sandbox.

Action: The only allowed operations in the intermediary state are: finalize and undo.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01819: Lock on sandbox {0} cannot be taken. A concurrent management operation may be in progress.

Cause: A management operation on the sandbox is in progress and has locked the sandbox.

Action: Retry the operation after a while.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01820: Metadata for sandbox {0} is not available. The sandbox management operation cannot proceed without sandbox metadata.

Cause: Sandbox was created without metadata.

Action: Use the management APIs that are available for sandboxes without metadata.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01821: Lifecycle change notifications for the sandbox {0} cannot be sent out because the change type is not defined.

Cause: The sandbox lifecycle change does not have a valid change type.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

MDS-01900: None of the configured metadata stores support versioning.

Cause: The underlying metadata store did not support versioning.

Action: Configure a metadata store that supports versioning, and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01901: specifying multiple labels for a namespace not allowed

Cause: Multiple labels were provided for a namespace that pointed to a metadata store.

Action: Provide a single label to map to a namespace and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01902: Label or namespace is invalid.

Cause: Either the namespace or the label was invalid.

Action: Verify that the namespace and the label are correct, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01903: Specified label {0} does not exist for {1} namespace.

Cause: The specified label did not exist in the metadata store mapped to the namespace.

Action: Verify that the label name is correct and that the label exists, and then retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01906: A label with same name {0} already exists.

Cause: An attempt was made to create a label that already existed.

Action: Create a label with a different name, and then retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01907: The label {1} is already configured for the store "{0}", so the same store cannot be configured with another label "{2}".

Cause: An attempt was made to map a label for a store when a label-to-store mapping already existed for that store.

Action: De-associate the existing label mapped to the store first, and then retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01908: failure to delete versions of the document {0}

Cause: An error had occurred while versions were being deleted.

Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01909: No namespaces are specified for creating label {0}.

Cause: No namespace information was found for creating a label.

Action: Provide a namespace for creating a label, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01910: The namespace {0} is already registered with the label {1}, so the super/sub namespace {2} cannot be assigned with the label {3}.

Cause: An attempt was made to associate multiple labels with a namespace, or an attempt was made to associate multiple namespaces with a single label.

Action: Associate a single label with a single namespace, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01911: failure of the metadata purge operation for the requested repository partition

Cause: An error occurred during a purge operation.

Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01912: MetadataStore configured for {0} does not support versioning.

Cause: The metadata store configured for the resource did not support versioning.

Action: Configure a metadata store that supports versioning or verify that the resource name is correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01913: A deployment lineage with same application name "{0}" and deployment module name "{1}" already exists.

Cause: An attempt was made to create a lineage that already existed.

Action: Create a lineage with a different application or MAR name, and then retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01914: The application name and deployment module name cannot be null to create DeploymentInfo.

Cause: An attempt was made to create DeploymentInfo with null values.

Action: Make sure that the values for application name and deployment module name are non-null.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02001: Absolute path as metadata-path for the file metadata-store configuration is not supported for SaaS deployment.

Cause: Configuring an absolute directory in SaaS Multitenant application will violate metadata isolation across tenants.

Action: Ensure that relative path specified as metadata-path for the file metadata-store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02002: RelativeToLocation for the file metadata-store configuration is not supported for SaaS deployment.

Cause: Configuring an absolute directory in SaaS Multitenant application will violate metadata isolation across tenants.

Action: Ensure that relative path is specified as metadata-path for the Metadata Store and RelativeToLocation is null
Level: 1

Type: ERROR

Impact: Configuration

MDS-02003: Package name {0} in cust-restriction-config in {1} is invalid.

Cause: An invalid package name was encountered whilst loading the component configuration.

Action: Ensure that a valid package name is specified
Level: 1

Type: ERROR

Impact: Configuration

MDS-02024: Setting or modifying the unique (or locally unique) identifier "{0}" of an existing element with localRef "{1}" through customizations is not supported.

Cause: An attempt was made to customize unique (or locally unique) identifier.

Action: Remove any customization that is attempting to modify the unique (or locally 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}": {2}

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}": {2}

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 explicitly allowed by any type definition nor any extended metadata entry.

Cause: An attempt was made to customize a node that was not customizable.

Action: If the attempted customization is valid, the customization restrictions need to be modified to provide this ability. The customization restrictions can be defined in: the XML schema definition, standalone XML file or an extended metadata file. Also check the customization policy for the MDS session in use and the customization configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02407: Customization of {0} is not allowed because the local reference was not found in the document.

Cause: An enquiry about the customizability of a node supplied a local reference that wasn't found in the document.

Action: Ensure that the local reference applies to the document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02408: The operation {0} on the {1} node is not allowed because the metadata object reference was not found in the change event.

Cause: A document change is not allowed because the metadata object reference was null.

Action: Ensure that the change document exists.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02500: Cannot find a valid MDSSession object for accessing the MDS document using ORAMDS URL

Cause: A valid MDSSession object was not set before accessing the document using the "oramds:///" protocol.

Action: Use the MDSURLHelper.setMDSSession() method to set a valid MDSSession object before accessing MDS documents using the oramds protocol.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02501: cannot load the ORAMDS URL "{0}" because MDS session could not be created or resolved

Cause: An error occurred while creating or resolving an MDS session object.

Action: Look for messages describing the cause exception in the error message log for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02600: configuration migration failure because the configuration document contains more than one mds-config element

Cause: The given configuration document contained more than one mds-config element.

Action: Correct the configuration document to contain a single mds-config element.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02601: configuration migration failure because it contains more than one persistence-config element

Cause: The configuration document contained more than one persistence-config element.

Action: Correct the configuration document to contain a valid persistence-config element.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02602: configuration migration failure because it contains more than one metadata-stores element

Cause: The configuration document contained more than one metadata-stores element

Action: Correct the configuration document to be a valid 10.1.3 configuration document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02603: configuration migration failure because it contains an invalid metadata-store element

Cause: The configuration document contained an invalid metadata-store element.

Action: Correct the configuration document to be a valid 10.1.3 configuration document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02700: The resource "{0}" cannot be updated by tenant "{1}".

Cause: The given resource could not be updated by the current tenant because it was not available in current tenant's scope.

Action: Verify that the resource is being updated in the same scope of the tenant who updates the resource.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02702: Tenant scoped PManager instance cannot be created for tenant {0} because given PManager instance does not have multitenancy enabled.

Cause: The PManager instance used here did not have multitenancy enabled but an attempt was made to create tenant scoped PManager instance.

Action: Verify that the PManager instance being passed has multitenancy support enabled.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02703: Tenant scoped PManager cannot be created for tenant "null".

Cause: The PManager instance used here had multitenancy support enabled but an attempt was made to create tenant scoped PManager instance with "null" tenant.

Action: Create scoped PManager instance for valid tenant id.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02704: Cannot create tenant scoped PManager instance using another tenant scoped PManager instance.

Cause: An attempt was made to create tenant scoped PManager using another scoped PManager instance.

Action: Create a tenant scoped PManager using an unscoped PManager instance.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02705: Cannot create PContext using an unscoped PManager instance.

Cause: Creating PContext using an unscoped PManager instance was not allowed.

Action: Use PManager instance that is scoped for a tenant to create PContext.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02706: Cannot create PTransaction using an unscoped PManager instance.

Cause: Creating PTransaction using an unscoped PManager instance was not allowed.

Action: Use PManager instance that is scoped for a tenant to create PTransaction.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02707: PContext with tenant id {0} cannot be used in scoped PManager with tenant id {1}.

Cause: Tenant id attached to PContext and the tenant id of tenant scoped PManager to which it was passed did not match.

Action: Create PContext from the tenant scoped PManager to which it is passed.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02708: PManager instance is being used after it has been released.

Cause: PManager instance was being used after it had been released.

Action: Create a new PManager.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02709: Configuration change operation "{0}" on scoped PManager is not allowed for the tenant {1}. Only global tenant is allowed to change the configuration settings in PManager.

Cause: A non global tenant attempted to change configurations in scoped PManager.

Action: Use global tenant scoped PManager to change the configuration settings.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02710: Operation "{0}" is not allowed in unscoped PManager.

Cause: A tenant aware operation was invoked in an unscoped PManager instance.

Action: Use a global or tenant scoped PManager to do the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02711: No tenant operations are allowed on MetadataStoreConnection not associated with any tenant id.

Cause: A tenant aware operation was invoked in MetadataStoreConnection to database store which did not have any tenant id attached.

Action: Create a new MetadataStoreConnection with a valid tenant id.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02712: The operation {0} is not allowed in this MetadataStoreConnection to database store because the MetadataStoreConnection is not attached to any tenant id.

Cause: A tenant aware operation was invoked in MetadataStoreConnection to database store which did not have any tenant id attached.

Action: Create a new MetadataStoreConnection with a valid tenant id.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02713: PContext associated with tenant {0} cannot be used with MetadataStoreConnection associated with different tenant {1}. Operation {2} failure.

Cause: The tenant id attached to PContext and MetadataStoreConnection did not match.

Action: Use PContext with same tenant id as the one attached to metadata store connection.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02714: Creating metadata store connection for tenant {0} is not allowed in non multitenant application.

Cause: An attempt was made to create metadata store connection for non global tenant in non multitenant application.

Action: Use global tenant id to create metadata store connection.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02715: No tenant scoped PManager instances can be created on already released PManager instance.

Cause: An attempt was made to create a tenant scoped PManager instance on already released PManager instance.

Action: Create new PManager instance using a PConfig then try creating scoped PManager instance.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02720: Cannot rename the document {0} to {1} as the new tenant scope does not match the original tenant scope.

Cause: The new name for the document was configured to a different tenant scope to the old document name.

Action: Provide a new valid document name that maps to the same tenant scope as the original document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02721: PResource {0} for tenant {1} cannot be used with MetadataStoreConnection that is associated with different tenant {2}. Operation {3} failure.

Cause: The tenant ids of the PResource and the MetadataStoreConnection did not match.

Action: Use PResource with same tenant id of the one attached to metadata store connection.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02722: Mar Lineage can be created by global tenant only. Creating MAR lineage is not supported for tenant {0}.

Cause: A non-global tenant attempted to create MAR lineage which is not supported. MAR lineage creation is allowed only for global tenant currently.

Action: Create MAR lineage from global tenant context.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02723: Operation "{0}" is not supported in Sandbox currently.

Cause: Unsupported operation was invoked in Sandbox instance.

Action: This operation is not supported in Sandbox currently.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02724: The ResourceName that is attached to tenant scope {0} is not allowed in SandboxPTransaction that is attached to the different tenant scope {1}. Operation {2} failure.

Cause: Tenant scope for ResourceName and SandboxPTransaction did not match.

Action: Use ResourceName with same tenant scope of the one attached to SandboxPTransaction.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02725: The Label {0} that is attached to tenant {1} is not allowed in MetadataStoreConnection that is attached to different tenant {2}. Operation {3} failure.

Cause: Tenant id for Label and MetadataStoreConnection did not match.

Action: Use label with same tenant id of the one attached to MetadataStoreConnection.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02726: The tenant {0} that is attached to PDocument {1} is not allowed in SandboxPTransaction that is attached to different tenant {2}. Operation {3} failure.

Cause: Tenant id for PDocument and SandboxPTransaction did not match.

Action: Use PDocument with same tenant id of the one attached to SandboxTransaction.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02727: The tenant {0} that is attached to Label {1} is not allowed in SandboxPTransaction that is attached to different tenant {2}. Operation {3} failure.

Cause: Tenant id for Label and SandboxPTransaction did not match.

Action: Use label with same tenant id of the one attached to SandboxPTransaction.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02728: The tenant {0} that is attached to {1} {2} is not allowed in Sandbox that is attached to different tenant {3}. Operation {4} failure.

Cause: Tenant id attached and Sandbox did not match.

Action: Use tenant id same as the one attached to Sandbox.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02729: The tenant scope {0} that is attached to {1} is not allowed in Sandbox that is attached to the different tenant scope {2}. Operation {3} failure.

Cause: Tenant scope attached and Sandbox did not match.

Action: Use tenant scope same as the one attached to Sandbox.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02730: Error in deprovisioning the tenant {0}. Unable to delete the resources in {1}.

Cause: Tenant resources might be on read-only store.

Action: Verify that tenant resources exist on a writable store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02731: Tenant specific operations cannot be done in multitenant disabled environment for tenant {0}.

Cause: An attempt was made to do tenant specific operations in Multitenant disabled environment.

Action: Enable the multitenant feature.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02732: TenantId cannot be created for the value "{0}".

Cause: TenantId could not be created with negative values or a value with more than 18 digits.

Action: Use positive values with max of 18 digits in decimal format to create a valid TenantId object.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02733: Rename across multiple tenant stripes is not supported on this store.

Cause: The store does not support writing to multiple tenant stripes or multitenancy is not enabled.

Action: Enable the multitenant feature.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02734: Unable to get TenantInfo for TenantId "{0}" from tenant management system.

Cause: Tenant is not yet provisioned or was deprovisioned from the POD.

Action: Check tenant provisioning system to ensure tenant is provisioned.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02735: Label "{0}" cannot be deleted since it is attached to sandbox(es): "{1}".

Cause: An attempt was made to delete a label that is attached to active sandbox(es).

Action: Make sure that there are no sandboxes attached to label to be deleted. Refer to FMW Enterprise Manager MDS repository home page to check labels that are attached to a sandbox.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02736: Failed to update purge configuration value for tenant {0}.

Cause: An error occurred while updating purge configuration.

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-02737: Prevented potential duplicate tip version for document "{0}". Original request was to update document with PATH_DOC_ID={1}, PATH_VERSION={2} and PATH_LOW_CN={3}, updated latest tip version having PATH_DOC_ID={4}, PATH_VERSION={5} PATH_LOW_CN={6} to avoid duplicate tip version.

Cause: MDS detected code flow which could have lead to duplicate tip issue.

Action: Previous tip document is replaced forcefully with new content, validate content of the document.
Level: 1

Type: WARNING

Impact: Programmatic

MDS-02738: Database based metadata repository initialization failure because of invalid MDS database schema at "[{0}]".

Cause: Configured Database details refer to invalid or non-MDS schema.

Action: Configure a valid MDS database schema created using Repository Creation Utility
Level: 1

Type: ERROR

Impact: Configuration

MDS-02739: MDS Partition with ID {0} does not exist in the database repository

Cause: This could be caused by deleting the partition while still being used by application.

Action: Ensure partition is deleted only when not in use. To resolve the current issue, restart the application or server.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02740: MDS repository version for tenant "{0}" is not same as Global MDS repository version. Repository version for tenant is "{1}" whereas GLOBAL repository version is "{2}".

Cause: MDS Repository version for Tenant is not same as Global MDS repository version

Action: Upgrade the MDS repository to the required version so that Global and Tenant repository versions are same.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02741: The metadata changes cannot be written to 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-02742: Instance of {0} is being used after it has been released.

Cause: Instance of a MDS object was used after it was released.

Action: Create a new instance.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02743: Error deleting partition {0} in repository {1}.

Cause: The directory or partition doesn't exist.

Action: Verify that the metadata path or partition for the repository exists.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02744: Failed to delete directory {0}.

Cause: The specified directory was invalid, read only or was in use and could not be deleted.

Action: Check exception message in logs for the exception stack and underlying cause.
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-02805: Import Metadata With Exact Copy is allowed only from archive.

Cause: Source MetadataStore was not not archive.

Action: Use an archive as source store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02806: Source archive is invalid because it is missing the export criteria metadata file.

Cause: MetadataFile containing the export criteria was missing in the source archive

Action: Import from an archive which has metadata file.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02807: Import Metadata With Exact Copy is allowed only to Database repository

Cause: Target MetadataStore was not Database repository

Action: Use Database repository as target for import.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02808: Category with which Export Criteria is written in the archive file is different from the one which is used to get ExportCriteriaReader

Cause: Wrong category was used to get Export Criteria Reader.

Action: Use right category..
Level: 1

Type: ERROR

Impact: Configuration

MDS-02809: Import Metadata With Exact copy operation is not supported when export criteria used to generate source archive contains fromLabel or toLabel conditions.

Cause: Export parameters fromLabel or toLabel were specified to generate archive that was acting as source for Import Metadata With Exact Copy Operation.

Action: Use an archive MetadataStore that was exported without fromLabel or toLabel specified.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02810: Transfer operation with TransferType "{0}" has been aborted and rolled back because too many documents failed.

Cause: Operation failed for high number of documents.

Action: Check the server logs to identify root cause, rerun the operation after correcting the issue in the system environment.
Level: 1

Type: ERROR

Impact: Other

MDS-02811: Wrong TransferType {0} is passed in for Sandbox {1}

Cause: TransferType and TransferParams which is created for Sandbox transfer doesn't match.

Action: Supply the right TransferType.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02812: Parameter {0} has null values in it.

Cause: Parameter contains null values.

Action: Ensure that the indicated parameter does not contain null values when the method is called.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02813: Parameter TransferOptions must be set when transferBaseDocument is set to false.

Cause: Filtering out base documents is supported only when TransferOptions is set.

Action: Ensure that TransferOptions is set when transferBaseDocument is set to false.
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 occurred. Details are usually given in the accompanying messages.

Action: Look for messages describing the cause and take the appropriate action.
Level: 1

Type: ERROR

Impact: Data

MDS-10003: The specified {0} argument is null or empty.

Cause: A required program argument was null or empty.

Action: Record any accompanying exception messages and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-10009: The transfer of the document {0} is not successful.

Cause: Document transfer failed

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: WARNING

Impact: Data

MDS-10010: Deleting the document {0} is not successful.

Cause: Document deletion failed

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: WARNING

Impact: Data

MDS-10011: The operation on {0} has been rolled back. Total number of documents failed during the operation is {1}.

Cause: The transfer was rolled back

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: WARNING

Impact: Data

MDS-10012: The operation has failed.

Cause: The operation has failed.

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: WARNING

Impact: Data

MDS-10013: {0} operation started.

Cause: Transfer started.

Action: Transfer started, no action required.
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10014: {0} is completed. Total number of documents successfully processed : {1}, total number of documents failed : {2}.

Cause: Transfer complete.

Action: Check any accompanying messages to decide if any action is required.
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10015: Failure occurred while committing the {0} operation. The operation has been rolled back.

Cause: Failure occurred while committing the operation.

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: ERROR

Impact: Data

MDS-10016: The operation on {0} has been rolled back. The post transfer label {1} could not be created.

Cause: Failure occurred when creating the post transfer label.

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: ERROR

Impact: Data

MDS-10017: The target store does not support deployment management. Given application name "{0}" and deployment module name "{1}" could not be persisted as deployment information in store.

Cause: The target store does not support deployment management.

Action: No action required. The documents will be transferred without the deployment information attached. If you want to store deployment information as well, configure a metadata store that supports deployment management, typically a DB store.
Level: 1

Type: WARNING

Impact: Data

MDS-10018: The transfer restriction {0} is not supported in target store. All the documents will be transferred to target store.

Cause: Given transfer restriction is not supported in target store.

Action: No action required. The given restriction will not be applied to the transfer, all the documents will be transferred to target store.
Level: 1

Type: WARNING

Impact: Data

MDS-10019: The deployment information for application name "{0}" and module name "{1}" ignored since transfer operation is of type "{2}".

Cause: The deployment information will not be processed in transfer operation type other than "Deployment".

Action: No action required. Given deployment information will not be processed in the current transfer operation.
Level: 1

Type: WARNING

Impact: Data

MDS-10020: Querying checksum data from target repository to avoid transferring unchanged documents.

Cause: To apply transfer restriction CHANGED, transfer queries the target repository to check whether documents being transferred already exist with same content.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10022: Query to get the checksum of the documents from target repository completed successfully.

Cause: To apply transfer restriction CHANGED, transfer queries the target repository to check whether documents being transferred already exist with same content.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10023: No valid exclusion rules are specified in mds-transfer-config.xml to preserve documents in target store.

Cause: No valid namespaces or metadata object names specified in /meta-inf/mds-transfer-config.xml to preserve the documents in target store.

Action: No action required.
Level: 1

Type: WARNING

Impact: Data

MDS-10024: Preparing the list of documents to be excluded during transfer as per the configuration given in mds-transfer-config.xml.

Cause: To preserve the documents in target store as specified in the given /meta-inf/mds-transfer-config.xml, MDSTransfer prepares the list of documents to be excluded by looking at source and target stores.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10025: Following metadata paths are configured in mds-transfer-config.xml to preserve existing documents under this metadata path in target repository. Configured metadata paths are as follows {0}:

Cause: Some metadata paths are configured in mds-transfer-config.xml to preserve existing documents in target repository.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-10026: Following Metadata object names are configured in mds-transfer-config.xml to preserve existing metadata objects with same name in target repository. Configured metadata object names are {0}:

Cause: Some metadata object names are configured in mds-transfer-config.xml to preserve existing documents in target repository.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-10027: To preserve documents in target store, the following documents from source store are marked as excluded by transfer {0}.

Cause: To preserve documents in target store, some documents from source store are marked as excluded by transfer.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-10030: Sandbox {0} created as part of Import operation is not destroyed after import failed.

Cause: A Critical Write error on database side has occurred. Look for specific exception in the log file.

Action: Destroy unused sandbox from metadata repository. Contact application administrator for assistance.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-10031: Value provided in {0} in CustLayerUsage or CustLayerFilter is not properly encoded.Passed in value will considered as it is without interpreting intended encoded value

Cause: Passed in value is not proper hexadecimal encoded value

Action: No action required.
Level: 1

Type: WARNING

Impact: Data

MDS-10032: Transfer operation with transfer type {0} ignoring document {1} because MDSInstance {2} reported it as not existing.

Cause: MDSTransfer is configured to ignore such document.

Action: No action required.
Level: 1

Type: WARNING

Impact: Programmatic

MDS-10033: Transfer operation with transfer type {0} has been rolled back because {1} documents failed with exceptions.

Cause: Operation failed for large number of documents due to exceptions.

Action: Check the server logs to identify root cause, rerun the operation after correcting the issue in the system environment.
Level: 1

Type: ERROR

Impact: Other

MDS-10034: Polling for store {0} failed - {1}. Polling will retry when the polling interval has elapsed.

Cause: The polling query was unable to run. If this is a temporary condition, polling should recover automatically once the error condition is resolved.

Action: Polling will be retried. If problem persists enable tracing for oracle.mds.dbstore to get full stack trace and check datasources.
Level: 1

Type: WARNING

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, tenant-id, #versions purged]: [{0}, {1}, {2}, {3}, {4}].

Cause: An auto-purge occurred on a metadata-store.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-11016: MDS JSP Integration has been configured in Developer Mode to allow changes to files to be detected. Do not use this mode for production or performance testing.

Cause: Developer Mode is configured as a servlet initialization parameter either explicitly or because the application is being run within JDeveloper.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-11017: Started creating the final archive file at {0}.

Cause: ArchiveMetadataStore has started to create final archive file with all the changes done on the archive file so far.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-11018: The final archive file has been created successfully. The archive file is available at {0}.

Cause: ArchiveMetadataStore has created final archive file with all the changes done on the archive file so far.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-11019: The default CharSet {0} is not a unicode character set. File names with non-ASCII characters may not operate as expected. Check locale settings.

Cause: The Java default CharSet is used to convert file names to and from Java Strings. When this CharSet is a non-unicode character encoding, filenames that contain non-ASCII characters may not be correctly mapped to Java characters.

Action: Check the locale environment variable settings for the process that is running the JVM that MDS is running in to ensure that a UTF encoding is being used. For example, the LC_ALL and LANG settings may be relevant.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11020: Cannot delete the intermediary archive file {0}.

Cause: The intermediary archive file could not be deleted.

Action: Try deleting the file outside of MDS.
Level: 1

Type: WARNING

Impact: Other

MDS-11023: MDS Remote Notifications: Coherence is not configured to use unicast and no cluster name is specified so remote notification is not enabled.

Cause: MDS remote notification only works if the Coherence configuration specifies unicast or a cluster name.

Action: Unicast can be set by either specifying a unicast-listener in your Coherence cluster-config or by system property tangosol.coherence.wk. A cluster-name can be set either as part of a member-identity in your cluster-config or by system property tangosol.coherence.cluster.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11026: Ignoring the duplicate MDS component configuration file URL "{0}" found on the classpath.

Cause: A duplicate URL for an MDS component configuration file was found on the classpath.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-11027: Some metadata is configured to be stored as xml-stream. However it will be ignored because no metadata store configured for this application supports storing metadata in that form.

Cause: xml-stream content type was configured for some metadata content, but no metadataStore supports the feature.

Action: No action required if not using xml-stream content type is acceptable. Otherwise, to enhance MDS repository performance, ensure that the metadata store supports xml-stream feature.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11028: Some metadata is configured to be stored as xml-stream. However it will be ignored because the corresponding metadata store, with class name: {0}, repository name: {1}, partition name: {2}, does not support storing metadata in that form.

Cause: xml-stream content type was configured for some metadata content, but the metadata store did not support the feature.

Action: No action required if not using xml-stream content type is acceptable. Otherwise, to enhance MDS repository performance, ensure that the metadata store supports xml-stream feature.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11029: MetadataStore configuration for metadata-store-usage "{0}" is invalid. However the MetadataStore is ignored because it is not referenced by any namespace mapping.

Cause: MetadataStore class or some of its properties were not valid.

Action: Ensure that the MetadataStore class exists and all required properties are valid.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-11030: Failed to get schema version from registry for repository "{0}" because of exception: {1}

Cause: Either the DataSource definition for the repository is no longer valid or the MDS schema is not created using RCU.

Action: Ensure the DataSource connection is valid or the schema is created using RCU.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11032: Registered grammar using remote schema "{0}". In design time (JDev) environment, it is recommended to use local resources.

Cause: Remote schema was referred with http URI. In design time environment, recommendation is to use local resources.

Action: Replace it with local copy of schema.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11033: Duplicate mappings between namespace "{0}" and metadata store "{1}" are found in the persistence configuration.

Cause: There were more than one namespace to metadata store mappings for a given namespace in the persistence configuration.

Action: Correct the namespace mapping in persistence configuration to ensure that the namespace is mapped to only one metadata store.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11034: The name {0} derived from JNDI will be registered as an MDS repository instead of the DataSource with the same name.

Cause: A JDBC DataSource and a JNDI have conflict in naming a MDS repository in the domain. MDS repository names must be unique within a domain.

Action: Find out which application is referencing the repository and the JNDI name. Resolve the naming conflict by removing the DataSource with same name only if it is unused.
Level: 1

Type: ERROR

Impact: Configuration

MDS-11100: MetadataObject.getBaseMO() found a mismatched CacheAccess in the cache. [refNoGUID={0}, guidRef={1}, mdxLookupKey={2}, isLabelledRead={3}, baseDocLabel={4}, setSandboxName={5}, cacheAccess={6}, doc={7}, name={8}, GUID={9}].

Cause: CacheAcces does not match the the given MOReference/Guid combination. The metadata object will not be cached.

Action: Check the MOName and guid are correct and there are no duplicate Guids in the metadata store.
Level: 1

Type: WARNING

Impact: Other

MDS-11101: MetadataObject.getBaseMO() recursing too deep. [refNoGUID={0}, guidRef={1}, mdxLookupKey={2}, isLabelledRead={3}, baseDocLabel={4}, setSandboxName={5}, cacheAccess={6}, doc={7}].

Cause: CacheAcces does not match the the given MOReference/Guid combination. The metadata object will not be cached.

Action: Check the data in the metadata store to determine the cause.
Level: 1

Type: WARNING

Impact: Other

MDS-11102: The MDS session was created by the ADF framework with a transaction key for its "single flush" feature, and the call to {0} is restricted to that framework. This call does not use that transaction key and although working now, will fail with an exception in future. To find the originator of the call, set the log level for logger "oracle.mds.transkey" to FINEST. Note that the ADF framework manages the MDS session created for the request so an explicit call to {0} should be removed.

Cause: A call was made to a restricted method on the MDS session and that call should be removed as it is liable to fail in later releases.

Action: Identify the caller and ensure that the call to this method is removed.
Level: 1

Type: WARNING

Impact: Other

MDS-11103: Failed to register dump classes.

Cause: Failed to register dump classes with DFW.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

MDS-11104: Content config mapping with path {0} contains reserved keyword "mdssys/cust/", use restrictionType="CUSTOMIZATIONS" instead.

Cause: The path of the content config mapping contains reserved keyword "mdssys/cust/".

Action: Change the content config mapping to use restrictionType="CUSTOMIZATIONS"
Level: 1

Type: WARNING

Impact: Configuration

MDS-90013: The metadata partition with name "{0}" does not exist in the metadata repository "{1}".

Cause: The metadata partition with the specified name was not found in the metadata repository.

Action: Create a metadata partition with the specified name in the metadata repository before trying this operation.
Level: 1

Type: ERROR

Impact: Topology

MDS-90014: cannot update the metadata because the application is read-only

Cause: No metadata update was made because the ReadOnlyMode attribute was enabled.

Action: Disable the ReadOnlyMode attribute of the target application configuration.
Level: 1

Type: ERROR

Impact: Topology

MDS-90015: The metadata repository with name "{0}" does not exist.

Cause: The metadata repository with the specified name was not found.

Action: Verify that the repository name is spelled correctly. If the repository does not exist, create one with the specified name and try again.
Level: 1

Type: ERROR

Impact: Topology

MDS-90016: There are no applications deployed to partition "{0}".

Cause: An attempt was made to perform this operation on a partition that is not associated with a deployed application.

Action: Specify a partition that is associated with a deployed application.
Level: 1

Type: ERROR

Impact: Topology

MDS-90017: The application to be used for this operation is not specified.

Cause: Could not determine which application configuration to use for this operation since there is more than one application deployed to partition "{0}".

Action: Specify an application that is deployed to partition "{0}" to be used for this operation.
Level: 1

Type: ERROR

Impact: Topology

MDS-90018: Application "{1}" is not deployed to partition "{0}".

Cause: The specified application was not deployed to the specified partition.

Action: Specify an application that is deployed to the partition.
Level: 1

Type: ERROR

Impact: Topology

MDS-90019: cannot set the user property on the driver: {0}

Cause: A problem occurred while setting the user property on the driver.

Action: Ensure that the database server is running properly.
Level: 1

Type: ERROR

Impact: Topology

MDS-90020: Metadata store cannot be assigned to server "{0}".

Cause: A problem occurred while assigning resource to the server.

Action: Ensure that the server is running properly.
Level: 1

Type: ERROR

Impact: Topology

MDS-90021: Metadata path {0} is invalid.

Cause: The path used to create a FileMetadataStore was invalid. It must point to a directory.

Action: Correct the metadata path.
Level: 1

Type: ERROR

Impact: Topology

MDS-90022: The host name of the database repository cannot be empty.

Cause: The host name of the database repository was empty or null.

Action: Use a valid host name.
Level: 1

Type: ERROR

Impact: Topology

MDS-90023: The database name of the database repository cannot be empty.

Cause: The database name of the database repository was empty or null.

Action: Use a valid database name.
Level: 1

Type: ERROR

Impact: Topology

MDS-90024: The user name of the database repository cannot be empty.

Cause: The user name of the database repository was empty or null.

Action: Use a valid user name.
Level: 1

Type: ERROR

Impact: Topology

MDS-90025: The password of the database repository cannot be empty.

Cause: The password of the database repository was empty or null.

Action: Use a valid password.
Level: 1

Type: ERROR

Impact: Topology

MDS-90026: The server name cannot be empty.

Cause: The server name was empty or null.

Action: Use a valid server name.
Level: 1

Type: ERROR

Impact: Topology

MDS-90027: cannot find server "{1}" to register the metadata repository "{0}"

Cause: The server name was invalid.

Action: Use a valid server name.
Level: 1

Type: ERROR

Impact: Topology

MDS-90028: Metadata repository with name "{0}" already exists.

Cause: Metadata repository with the specified name already exists.

Action: Verify that the repository name is spelled correctly. If the repository already exists, create one with a different name and try again.
Level: 1

Type: ERROR

Impact: Topology

MDS-90029: The metadata db repository with name "{0}" does not exist.

Cause: The metadata db repository with the specified name was not found.

Action: Verify that the db repository name is spelled correctly.
Level: 1

Type: ERROR

Impact: Topology

MDS-90030: The metadata file repository with name "{0}" does not exist.

Cause: The metadata file repository with the specified name was not found.

Action: Verify that the file repository name is spelled correctly.
Level: 1

Type: ERROR

Impact: Topology

MDS-90031: The JDBC resource of metadata db repository "{0}" cannot be found.

Cause: The JDBC resource was not found.

Action: Verify that the metadata db repository is set up correctly.
Level: 1

Type: ERROR

Impact: Topology

MDS-90032: The metadata store of metadata file repository "{0}" cannot be found.

Cause: The metadata store was not found.

Action: Verify that the metadata file repository is set up correctly.
Level: 1

Type: ERROR

Impact: Topology

MDS-90033: unknown DB vendor code: "{0}"

Cause: The DB vendor code is invalid.

Action: Use a valid DB vendor code, such as 0 (ORACLE), 1 (MSSQL), or 2 (IBMDB2).
Level: 1

Type: ERROR

Impact: Topology

MDS-90034: The source directory or archive "{0}" for importing metadata is invalid.

Cause: The directory or archive location used to import metadata was invalid. It must point to a valid, existing directory or archive.

Action: Correct the source directory or archive location.
Level: 1

Type: ERROR

Impact: Topology

MDS-90035: The target directory or archive "{0}" for exporting metadata is invalid.

Cause: The directory or archive location used to export metadata was invalid. It must point to a valid location.

Action: Correct the target directory or archive file location.
Level: 1

Type: ERROR

Impact: Topology

MDS-90036: The application does not have a valid MAR file path.

Cause: The MAR path used to import MAR was invalid. It must point to a valid, existing MAR file.

Action: Make sure the MAR file exists and is located in the correct directory of the application.
Level: 1

Type: ERROR

Impact: Topology

MDS-90037: The archive "{0}" does not contain valid contents.

Cause: The archive used to import metadata was invalid. It must be to a valid, existing zip or jar file.

Action: Make sure the archive is valid.
Level: 1

Type: ERROR

Impact: Topology

MDS-90038: The database authentication alias "{0}" already exists. To reuse the same authentication alias, try the operation again without specifying user and password.

Cause: An attempt was made to configure a database authentication alias that already existed in Websphere server.

Action: Delete the existing authentication alias and try again, or specify a new authentication alias, or reuse the existing authentication alias by not specifying user and password.
Level: 1

Type: ERROR

Impact: Topology

MDS-90039: The database authentication alias "{0}" cannot be found. To create the authentication alias, try the operation again with user and password specified.

Cause: An attempt was made to use a database authentication alias that was not configured in Websphere server.

Action: Make sure the specified database authentication alias is properly configured in Websphere server, or automatically create the authentication alias by specifying user and password.
Level: 1

Type: ERROR

Impact: Topology

MDS-90040: failed to connect to database

Cause: An error occurred when trying to connect to database.

Action: Make sure the database connection details are correct. Look at the cause exception for more details.
Level: 1

Type: ERROR

Impact: Topology

MDS-90041: Customization layer values are not supported for "excludeCustFor" parameter.

Cause: One or more customization layer values was specified for "excludeCustFor" parameter.

Action: Make sure there are no customization layer values specified for "excludeCustFor" parameter.
Level: 1

Type: ERROR

Impact: Topology

MDS-90042: "{0}" is not a valid tenant name.

Cause: The specified tenant was not provisioned in the specified partition and repository.

Action: Specify a valid tenant name.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90043: This operation cannot be performed by the tenant named "{0}". It can only be invoked by the "{1}" tenant.

Cause: The specified tenant was not provisioned in the partition and repository provided.

Action: Execute this operation as GLOBAL tenant.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90044: This operation cannot be performed because the WebLogic edit session has been locked by a different user.

Cause: The WebLogic edit session has been locked by a different user.

Action: Retry the operation after the edit session lock is released.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90045: MDS dump operation "{0}" failed.

Cause: Exception occurred during the execution of the command.

Action: Provide the required parameters for the command.
Level: 1

Type: ERROR

Impact: Data

MDS-90046: MDS Application runtime MBean for application "{0}" running in server "{1}" is not available. "{2}" 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 application name is correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90047: The target archive name "{0}" is invalid. It must point to a local file name with a valid archive extension.

Cause: The archive location used for mds dump operation was invalid.

Action: Ensure target archive name is a valid local file name with valid archive extension.
Level: 1

Type: ERROR

Impact: Data

MDS-90048: The dump argument "{0}" is invalid. It cannot be an empty string.

Cause: A request to execute dump was made with an invalid argument.

Action: Ensure valid values are given for the dump arguments.
Level: 1

Type: ERROR

Impact: Data

MDS-90049: Exclusion of documents during exportMetadata is not supported for seeded documents.

Cause: It was invalid to specify excludeDocs while not setting excludeSeededDos to true.

Action: Either set excludeSeededDocs to true, or unspecify excludeDocs.
Level: 1

Type: ERROR

Impact: Data

MDS-90050: ExportParameters can not be null for {0} operation.

Cause: ExportParameters with null value was not allowed.

Action: Specify a valid ExportParameters argument.
Level: 1

Type: ERROR

Impact: Data

MDS-90051: ImportParameters can not be null for {0} operation.

Cause: ImportParameters with null value was not allowed.

Action: Specify a valid ImportParameters argument.
Level: 1

Type: ERROR

Impact: Data

MDS-90052: Cannot deregister metadata repository "{0}" because it is based on a JNDI name of a consolidated data source.

Cause: The deregistration of a metadata repository that is based on a JNDI name of a consolidated data source is not allowed.

Action: Perform deregistration operation on a metadata repository that is based on a non-consolidated data source only.
Level: 1

Type: ERROR

Impact: Data

MDS-90053: Import Metadata With Exact copy operation is not supported when export operation used to generate source archive uses programmatic TransferListener.

Cause: Export parameter transferListener was specified to generate archive that was acting as source for Import Metadata With Exact Copy Operation.

Action: Use an archive MetadataStore that was exported without programmatic TransferListener specified.
Level: 1

Type: ERROR

Impact: Data

MDS-90054: The resource group "{0}" cannot not be found in "{1}" partition.

Cause: The specified resource group was not found in the current domain partition.

Action: Verify that the specified resource group is defined in the current domain partition.
Level: 1

Type: ERROR

Impact: Data

MDS-90055: The resource group must be specified to register a metadata repository at "{0}" partition.

Cause: The resource group was not specified to register a metadata repository at partition scope.

Action: Specify a resource group for registering a metadata repository at the domain partition containing that resource group.
Level: 1

Type: ERROR

Impact: Data

MDS-90056: {0} can not be null for {1} operation.

Cause: Null value was not allowed.

Action: Specify a valid argument.
Level: 1

Type: ERROR

Impact: Data

MDS-90057: The document name used in exportDocVersions operation is invalid.

Cause: Document pattern or empty document name was used.

Action: Use the exact full document path.
Level: 1

Type: ERROR

Impact: Data

MDS-90058: {0} operation is not permitted in Weblogic domain configured with consolidate schema or datasource.

Cause: It was unneccesary to register or deregister a metadata DB repository in consolidate Weblogic domain.

Action: Use pre-configured metadata DB repository.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90143: "{0}" is not a valid component name.

Cause: The specified component name is invalid.

Action: Specify a valid audit component name that uses only letters.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90144: Error registering audit event definitions for component "{0}".

Cause: The audit event definitions could not be registered.

Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90145: Error occurred when raising audit event "{0}" for component "{1}".

Cause: The audit event was not registered or an unknown error occurred in the auditing system.

Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90146: Error occurred when checking if "{0}" is auditable.

Cause: An unknown error occurred when checking if auditing is enabled for the component "{0}".

Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90147: Error occurred when checking if the component "{0}" is auditable.

Cause: An unknown error occurred when checking if auditing is enabled for the event "{1}" defined for the component "{0}".

Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90243: Content auto merge failed for MO part "{0}" with change type "{1}" because its type is not registered for auto merge.

Cause: The specified MOType is not registered for auto merge functionality.

Action: Register the MOType for auto merge functionality.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90244: Content auto merge failed for MO part "{0}" with change type "{1}" because its base document is not accessible for read from any configured metadata stores.

Cause: Base document is not accessible for read.

Action: Make sure base document is available for read through any of configured metadata stores.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90245: Content auto merge failed for MO part "{0}" with change type "{1}" because both base and customization MOParts have conflicts and base MOPart is not a stub.

Cause: Base MOPart is not a stub document.

Action: This is unsupported case. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90246: Content auto merge failed for MO part "{0}" with change type "{1}" because mainline contains conflicting change type "{2}" for the same MOPart.

Cause: There were conflicting changes for MetadataObject between sandbox and mainline and cannot be resolved by content auto merge.

Action: Contact Application Administrator to resolve these conflicts manually or perform the changes again in a new sandbox.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90247: Content auto merge failed for MOPart "{0}" with change type "{1}", because conflicts identified for metadata object include changes for non tip or non configured customization layer "{2}".

Cause: Conflicts detected for given metadata object include changes for non tip or non configured customization layer.

Action: This is unsupported case. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90248: Content auto merge failed for MetadataObject "{0}".

Cause: Content auto merge failed for specified MO.

Action: Please check each MOPart exception for detailed reasons.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90249: Content auto merge failed for MetadataObject "{0}", because the MO constitutes more than one customization MOPart for the customization layer "{2}".

Cause: Customization layer yields multiple layer values.

Action: This is unsupported case. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90251: Conflict resolution hook annotation is missing for MOType {0}.

Cause: Conflict resolution policy was set to "callback" for the document type but associated Conflict resolution hook annotation configuration is missing.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90252: Conflict resolution policy is either found missing or it's value is not set to "callback" for MOType {0}

Cause: Conflict resolution hook annotation was found in document type but conflict resolution policy configuration was either not supplied or the value was not set to "callback".

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90253: AutoMergePluginContext is null for AutoMergePlugin class {0}

Cause: AutoMergePluginContext was found as null in AutoMergePlugin instance.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90254: Unable to get AutoMergePlugin for MOType "{0}", Parameter AutoMergePluginContext must have a value.

Cause: Parameter AutoMergePluginContext was null.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90255: Conflict resolution hook class "{0}" cannot be instantiated for MOType "{1}"

Cause: An exception occurred while instantiating conflict resolution hook class.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90256: Unable to get AutoMergePlugin instance from AutoMergePluginFactory for MOType "{0}".

Cause: AutoMergePluginFactory returned null for AutoMergePlugin.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90257: Unable to get AutoMergePluginFactory instance from ConflictResolutionHook for MOType "{0}".

Cause: ConflictResolutionHook returned null for AutoMergePluginFactory.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90258: Conflict resolution hook class "{0}" cannot be instantiated to get merge handler for MOType "{1}"

Cause: An exception occurred while instantiating conflict resolution hook class to get merge handler.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90259: Unable to get MergeHandler instance from MergeHandlerFactory for MOType "{0}".

Cause: MergeHandlerFactory returned null for MergeHandler.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90260: Unable to get MergeHandlerFactory instance from ConflictResolutionHook for MOType "{0}".

Cause: MergeHandlerFactory returned null for MergeHandlerFactory.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90343: Sandbox "{0}" Apply operation failed for MO part "{1}" since conflict were identified with mainline changes for MO Part "{2}" that violates the relationship and dependency constraints.

Cause: Sandbox changes violate some dependency constraints with mainline changes.

Action: Contact Application Administrator to resolve these conflicts manually or perform the changes again in a new sandbox.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90344: Sandbox "{0}" apply operation with content auto merge failed.

Cause: Sandbox apply operation with auto merge failed.

Action: Please check each MO exception for detailed reasons.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90345: Failure to get conflicts for sandbox

Cause: Target label is older than the sandbox mainline label.

Action: Specify a target label which is later than current label.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90346: Invalid SandboxUsage. The sandbox name "{0}" in sandboxUsage does not match with Sandbox instance being operated upon.

Cause: Wrong sandbox name used while retrieving MDSSession for conflict resolution.

Action: Use right SandboxUsage that was used earlier for making the sandbox changes.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90347: Retry refresh operation on Sandbox "{0}" failed as it detected some unexpected mainline changes on MDSSession which is intended for conflict resolution, for following documents : {1}

Cause: Unexpected mainline changes detected on MDSSession that was retrieved for conflict resolution during sandbox refresh operation.

Action: Cancel mainline document changes from the MDSSession and retry the refresh operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90348: This operation cannot continue as Refresh is in progress for Sandbox {0}.

Cause: Some other refresh operation might be in progress.

Action: Cancel or End the in-progress refresh before trying this operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90349: This operation cannot continue as Refresh operation is either not initiated OR already ended for Sandbox {0}.

Cause: Sandbox beginRefresh() hasn't been called.

Action: Invoke the beginRefresh() first before this operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90350: This operation cannot continue as in progress refresh transaction is not yet completed for Sandbox {0}.

Cause: Sandbox refresh operation hasn't ended using endRefresh() call.

Action: Invoke the endRefresh() before trying this operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90351: Tip customization layer name and value are not defined for refresh operations for Sandbox {0}.

Cause: Tip customization layer name and value are not defined.

Action: Define tip customization layer name and value to perform sandbox refresh.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90352: Refresh operation cannot be ended since there are pending conflicts to resolve for Sandbox {0}.

Cause: There are pending conflicts to resolve.

Action: Resolve the pending conflicts and try the operation again.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90500: Count of unresolved merge conflict(s) - {0}

Cause: One or more unresolved merge conflict(s) exists.

Action: For more details, use getUnresolvedMergeConflicts() method on MOPartChangeContentAutoMergeException instance.
Level: 1

Type: ERROR

Impact: Data

MDS-90501: Unexpected content auto-merge error

Cause: An unexpected content auto-merge error occurred.

Action: Please resolve the conflict before attempting auto-merge operation again.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-90502: Invalid input documents for content auto-merge operation.

Cause: Invalid documents are provided to perform content auto-merge operation.

Action: Provide valid documents.
Level: 1

Type: ERROR

Impact: Data

MDS-90503: Limited support available for XSD content auto-merge operation.

Cause: Unable to auto-merge changes being made by the request or by another user done to XSD metadata object.

Action: Please resolve the conflict before attempting auto-merge operation again.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-90504: No support to auto-merge updates done to elements with brittle local reference.

Cause: Updates done on elements with brittle local reference.

Action: Resolve the conflict before attempting auto-merge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90505: Auto-merge synchronous XML tree walk failure occurred while handling following merge conflict - * {0}

Cause: An error occurred in the MDSDocumentAutoMergePlugin.

Action: Check for log messages. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

MDS-90506: No support to auto-merge move operation

Cause: Encountered move operation while performing content auto-merge operation.

Action: Resolve the conflict before attempting auto-merge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90507: Type annotation "automerge" for child-list order preference on element with local reference "{0}" in metadata object "{1}" does not have valid value. Valid values are "childListOrderNotImportant" and "childListOrderImportant"

Cause: Child-list of the underlying element was modified as part of content auto-merge operation.

Action: Provide valid value for "automerge" type-annotation. Valid values are "childListOrderNotImportant" and "childListOrderImportant".
Level: 1

Type: ERROR

Impact: Data

MDS-90508: Type annotation automergeChildListOrderDefault set on element definition of root element in metadata object "{0}" does not have valid value. Valid values are "childListOrderNotImportant" and "childListOrderImportant".

Cause: Invalid value provided for automergeChildListOrderDefault type-annotation.

Action: Provide valid value for automergeChildListOrderDefault type-annotation. Valid values are "childListOrderNotImportant" and "childListOrderImportant".
Level: 1

Type: ERROR

Impact: Data

MDS-90540: Unable to automerge changes done to attribute on element "{0}" with local reference "{1}" since attribute "{2}" is inserted with different values "{3}" in the current transaction and "{4}" in another transaction.

Cause: Encountered element attribute automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90541: Unable to automerge changes done to attribute on element "{0}" with local reference "{1}" since attribute "{2}" is updated with different values "{3}" in the current transaction and "{4}" in another transaction.

Cause: Encountered element attribute automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90542: Unable to automerge changes done to attribute on element "{0}" with local reference "{1}" since attribute "{2}" is deleted in the current transaction but updated with value "{3}" in another transaction.

Cause: Encountered element attribute automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90543: Unable to automerge changes done to attribute on element "{0}" with local reference "{1}" since attribute "{2}" is updated with value "{3}" in the current transaction but deleted in another transaction.

Cause: Encountered element attribute automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90550: Unable to automerge changes done to text content of element "{0}" with local reference "{1}" since its text content is inserted with different values "{2}" in the current transaction and "{3}" in another transaction.

Cause: Encountered text content element automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90551: Unable to automerge changes done to text content of element "{0}" with local reference "{1}" since its text content is updated with different values "{2}" in the current transaction and "{3}" in another transaction.

Cause: Encountered text content element automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90552: Unable to automerge changes done to text content of element "{0}" with local reference "{1}" since its text content is deleted in the current transaction but updated with value "{2}" in another transaction.

Cause: Encountered text content element automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90553: Unable to automerge changes done to text content of element "{0}" with local reference "{1}" since its text content is updated with value "{2}" in the current transaction but deleted in another transaction.

Cause: Encountered text content element automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90560: Unable to automerge insertion of element "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since its fragment contents differ in the current transaction and in another transaction.

Cause: Encountered element insertion automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90561: Unable to automerge insertion of merge-unit "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since its fragment contents differ in the current transaction and in another transaction.

Cause: Encountered merge-unit insertion automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90562: Unable to automerge updates done to element "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since its fragment contents differ in the current transaction and in another transaction.

Cause: Encountered element update automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90563: Unable to automerge updates done to merge-unit "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since its fragment contents differ in the current transaction and in another transaction.

Cause: Encountered merge-unit update automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90564: Unable to automerge changes done to element "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since it is deleted in the current transaction but its fragment contents are updated in another transaction.

Cause: Encountered element automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90565: Unable to automerge changes done to merge-unit "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since it is deleted in the current transaction but its fragment contents are updated in another transaction.

Cause: Encountered merge-unit automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90566: Unable to automerge changes done to element "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since its fragment contents are updated in the current transaction but this element is deleted in another transaction.

Cause: Encountered element automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90567: Unable to automerge changes done to merge-unit "{0}" with local reference "{1}" under parent element "{2}" with local reference "{3}" since its fragment contents are updated in the current transaction but this merge-unit is deleted in another transaction.

Cause: Encountered merge-unit automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90568: Unable to automerge changes done to element "{0}" with local reference "{1}" since it is deleted in the current transaction but moved under a different parent in another transaction.

Cause: Encountered element automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90569: Unable to automerge insertion of element with local reference "{0}" in the current transaction since it is inserted under a different parent in another transaction.

Cause: Encountered element automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90570: Unable to automerge insertion of root element "{0}" with local reference "{1}" since its fragment contents differ in the current transaction and in another transaction.

Cause: Encountered element insertion automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90571: Unable to automerge insertion of root merge-unit "{0}" with local reference "{1}" since its fragment contents differ in the current transaction and in another transaction.

Cause: Encountered merge-unit insertion automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90572: Unable to automerge updates done to root element "{0}" with local reference "{1}" since its fragment contents differ in the current transaction and in another transaction.

Cause: Encountered element update automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90573: Unable to automerge updates done to root merge-unit "{0}" with local reference "{1}" since its fragment contents differ in the current transaction and in another transaction.

Cause: Encountered merge-unit update automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90574: Unable to automerge changes done to element "{0}" with local reference "{1}" since it is moved under a different parent in the current transaction but deleted in another transaction.

Cause: Encountered element automerge conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90590: Unable to automerge updates done to element "{0}" with local reference "{1}" since its child order differs between the current transaction and another transaction.

Cause: Encountered child order conflict while performing content automerge.

Action: Resolve the conflict before attempting automerge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-91001: MDS domain runtime MBean is not available. "{0}" operation failure.

Cause: MDS domain runtime MBean was not available in the server.

Action: Ensure the MDS domain runtime MBean is available in the server.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91002: MDS Application runtime MBean for "{0}" is not available. "{1}" operation failure.

Cause: MDS Application runtime MBean was not available in the server.

Action: Ensure the MDS Application runtime MBean for the application is available in the server.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91003: Multiple MDSAppRuntimeMBean exist for "{0}". To execute the command, parameter "applicationVersion" is required. "{1}" operation failure.

Cause: Multiple MDSAppRuntimeMBean for the application were found in the server.

Action: Provide the 'applicationVersion' parameter.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91004: MDS domain runtime MBean commands can be executed only from the Admin server. "{0}" operation failure.

Cause: WLST was not connected to the Admin server.

Action: Connect to an Admin server before executing the command.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91005: No connection to a "{0}" server exists. The operation "{1}" can be executed only in the online mode.

Cause: Command was executed in the offline mode.

Action: Ensure WLST is connected to the server.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91006: Expecting a "{0}" for parameter "{1}" but encountering "{2}". "{3}" operation failure.

Cause: Parameter type passed to the command was not correct.

Action: Ensure the correct type of parameters are passed to the command.
Level: 1

Type: ERROR

Impact: Data

MDS-91007: dbVendor should be one of ORACLE, MSSQL, IBMDB2, or MYSQL. "{0}" operation failure.

Cause: dbVendor value was not correct.

Action: Ensure the dbVendor value is one of ORACLE, MSSQL, IBMDB2, or MYSQL.
Level: 1

Type: ERROR

Impact: Data

MDS-91008: The "{0}" parameter is required. Provide a valid value and retry the operation.

Cause: Required parameter for the command was not given.

Action: Provide the required parameters for the command.
Level: 1

Type: ERROR

Impact: Data

MDS-91009: Operation "{0}" failure.

Cause: Exception occurred during the execution of the command.

Action: Provide the required parameters for the command.
Level: 1

Type: ERROR

Impact: Data

MDS-91010: The "adf-config" element is not available in the given archive file. "{0}" operation failure.

Cause: The "adf-config" element is not available in the given archive file.

Action: Ensure the "adf-config" element is available in the adf-config.xml of the given archive file.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91011: No "mds-config" element exists in the adf-config.xml of the given archive. "{0}" operation failure.

Cause: No mds-config element existed in the adf-config.xml file of the archive file.

Action: Ensure the "mds-config" element is available in the adf-config.xml file.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91012: Metadata repository connection type value should be either "File" or "DB". "{0}" operation failure.

Cause: Metadata repository connection type value is not correct.

Action: Ensure the metadata repository connection type value is either 'File' or 'DB'.
Level: 1

Type: ERROR

Impact: Data

MDS-91013: For the metadata repository''s DB connection type, JNDI location is a required parameter. "{0}" operation failure.

Cause: JNDI location not provided for DB connection type.

Action: Provide the JNDI location string while updating the repository connection to DB.
Level: 1

Type: ERROR

Impact: Data

MDS-91014: For the metadata repository''s File connection type, path location is a required parameter. "{0}" operation failure.

Cause: The path value was not provided for File connection type.

Action: Provide the path location string while updating the repository connection to File.
Level: 1

Type: ERROR

Impact: Data

MDS-91015: All parameters are required to update shared metadata repository configuration in adf-config.xml. At present, source archive has no connection details for the namespace "{0}". "{1}" operation failure.

Cause: Complete connection information was not provided to set the shared repository for the given namespace.

Action: Provide complete connection information in case the adf-config.xml file does not have any metadata repository connection information for the given namespace already.
Level: 1

Type: ERROR

Impact: Data

MDS-91016: All parameters are required to define new application metadata repository configuration in adf-config.xml. The source archive configuration does not contain any application metadata repository at present. "{0}" operation failure.

Cause: Complete connection information was not provided to set the application target repository.

Action: Provide complete connection information in case the adf-config.xml does not have any metadata repository connection information for the application target repository already.
Level: 1

Type: ERROR

Impact: Data

MDS-91017: The given namespace "{0}" to set the shared repository is not valid. Ensure that the namespace is available in the adf-config.xml file and it is not a sub-namespace of any other namespace. "{1}" operation failure.

Cause: The namespace provided to set the shared repository details is not valid.

Action: Ensure that the namespace is available in the adf-config.xml file and it is not a subnamespace of any other namespace in that file.
Level: 1

Type: ERROR

Impact: Data

MDS-91018: No namespaces are mapped to any shared repository in the source archive adf-config.xml configuration file. Shared repository details cannot be set. "{0}" operation failure.

Cause: No namespaces were mapped to any shared repository in the source archive adf-config.xml configuration file.

Action: To set the shared repository connections, ensure at least one namespace is mapped to shared repository in the source archive adf-config.xml file.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91019: Multiple MDSAppRuntimeMBean exist for application "{0}". Ensure that the "application" "node" and "server" parameters are correct. "{1}" operation failure.

Cause: Multiple MDSAppRuntimeMBean for the application were found in the server.

Action: Ensure that the "application" "node" and "server" parameters are correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91020: MDS Application runtime MBean for "{0}" is not available in server "{2}". Ensure server name and application name are correct. "{1}" operation failure.

Cause: MDS Application runtime MBean was not available in the server.

Action: Ensure the MDS Application runtime MBean for the application is available in the server. Ensure the server name and the application name are correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91021: Multiple MDSAppRuntimeMBean exist for "{0}" in server "{2}". To execute the command, parameter "applicationVersion" is required. "{1}" operation failure.

Cause: Multiple MDSAppRuntimeMBean for the application were found in the server.

Action: Provide the 'applicationVersion' parameter.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91022: Parameter "{0}" cannot be an empty string. "{1}" operation failure.

Cause: The parameter is not allowed to be an empty string.

Action: Ensure the parameter has a correct value.
Level: 1

Type: ERROR

Impact: Data

MDS-91023: Parameter "{0}" contains at least one empty element. "{1}" operation failure.

Cause: The parameter is not allowed to contain one or more empty elements.

Action: Ensure every element specified in the parameter is correct.
Level: 1

Type: ERROR

Impact: Data

MDS-91024: Parameters "{0}" and "{1}" cannot be specified at the same time.

Cause: The two parameters are not allowed to be specified at the same time.

Action: Remove one of the parameters.
Level: 1

Type: ERROR

Impact: Data

MDS-92000: Oracle Metadata Services schema upgrade is invalid.

Cause: Specified Metadata Services schema was updated but is invalid.

Action: Restore the Metadata Services schema from a backup and retry. Check the error messages in log file. Correct the problem before running the Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-92001: The upgrade is not supported from Oracle Metadata Services schema version of {0}.

Cause: An unsupported base schema version was being upgraded.

Action: Refer to the Oracle Metadata Services Upgrade Guide for supported versions to upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-92002: Error in upgrading Oracle Metadata Services schema.

Cause: An unexpected error occurred during Oracle Metadata Services schema upgrade.

Action: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

MDS-92003: Error occurred while verifying the character set in target Metadata Services schema

Cause: A SQL error occurred while verifying the character set in target Metadata Services schema.

Action: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

MDS-92004: Error occurred while closing the resources during Metadata Services schema upgrade

Cause: A SQL error occurred while closing the resources during Metadata Services schema upgrade.

Action: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

MDS-92005: Error occurred while closing Metadata Services schema upgrade log files.

Cause: An unexpected error occurred while closing Metadata Services schema upgrade log files.

Action: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

MDS-92006: Oracle Metadata Service schema status is invalid.

Cause: Specified Oracle Metadata Services database schema was invalid.

Action: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

MDS-92007: Error occurred while verifying the user privileges in target Metadata Services schema

Cause: A SQL error occurred while verifying the user privileges in target Metadata Services schema.

Action: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

MDS-92008: The logon DBA user does not have sufficient privileges to upgrade the target Metadata Services schema user

Cause: The logon DBA user needs to have grant execute privilege on specific DBMS packages to other users for upgrading the schema user privileges in target Metadata Services schema.

Action: Logon as SYSDBA or other DBA users with sufficient privileges to grant execute on DBMS packages to other users and run the Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-92009: Oracle Metadata Services schema is not enabled for EBR.

Cause: Specified Oracle Metadata Services database schema was not enabled for EBR.

Action: Specify an Oracle Metadata Service schema that is enabled for EBR or Specify an upgrade for Oracle database type.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-92010: 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: INCIDENT_ERROR

Impact: Upgrade

29 MFT-02001 to MFT-08500

MFT-02001: Not able to load the MDS repository.

Cause: MDS repository initialization failed.

Action: Check the metadata repository configuration and make sure that they are valid.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02002: No transfer found for the source(ID {0}).

Cause: No transfer found for the source.

Action: Ensure that the source is attached to a transfer.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02003: No purge schedule found with name [{0}].

Cause: No purge schedule found with provided name.

Action: Ensure that the purge oschedule has been created.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02004: [{0}] with label [{1}] is not found in MDS.

Cause: Artifact does not exist in MDS.

Action: Please check artifact name.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02006: Data not found in MDS repository.

Cause: Data not found in MDS repository.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error. Make sure the meta data exists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02007: Error while creating new label with value {0} in MDS repository.

Cause: An error while creating new MDS label. Check if the label already exists.

Action: Check the metadata repository configuration and make sure that they are valid. Check if the label already exists in the system.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02008: Not able to resolve the MDS reference for source with ID {0}.

Cause: Reference meta data not exists in repository.

Action: Restore the deleted data in the MDS repository.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02009: Not able to resolve the MDS reference for transfer with ID {0}.

Cause: Reference metadata does not exist in the repository.

Action: Restore the deleted data in the MDS repository.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02010: Not able to resolve the MDS reference for target with ID {0}.

Cause: Referenced metadata does not exist in the repository.

Action: Restore the deleted data in the MDS repository.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02011: Label {0} does not exist in the MDS repository.

Cause: Label no longer exists in the MDS repository.

Action: Problem not recoverable. Contact Oracle Support Services.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02101: Validation failed for the artifact [{0}].

Cause: Validation failed for the given artifact.

Action: Check the artifact configuration and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02102: Not able to retrieve {0} from the credential store for {1}.

Cause: Not able to retrieve the password from the credential store.

Action: Check the settings and data in the credential store or recreate the password. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02104: No target associated with the transfer.

Cause: No target is associated with the transfer.

Action: Associate at least one target with the transfer and redeploy.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02105: No source associated with the transfer.

Cause: No source is associated with the transfer.

Action: Associate a source with the transfer and redeploy.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02301: Error occurred while exporting the metadata.

Cause: Error during metadata export.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02302: Error generating the config plan XML.

Cause: Error generating the config plan XML.

Action: Review the diagnostic log for the exact error. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02351: Error occurred while importing the metadata.

Cause: Invalid import metadata.

Action: Make sure that import zip file is proper. Also, review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02401: The source [{0}] is currently associated with some transfers and so cannot be deleted.

Cause: The given source is currently referenced in some transfers and so cannot be deleted at this point.

Action: For each associated transfer that is associated with given source, detach the source, associate a new source, or delete the transfer. Then try deleting the source again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02402: The target [{0}] is currently associated with some transfers and so cannot be deleted.

Cause: The given target is currently referenced in some transfers and so cannot be deleted at this point.

Action: For each associated transfer that is associated with given target, detach the target, associate a new target, or delete the transfer. Then try deleting the target again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02403: Error occurred while resetting the metadata with preserved user changes {0}.

Cause: Exception while resetting the metadata.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02404: Error occurred while deleting the source [{0}] from metadata store.

Cause: Exception while deleting the given source from metadata store.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02405: Cannot delete the domain-info(name {0}) because it is referenced in some B2B source/target types.

Cause: Cannot delete the domain-info because it is referenced in some B2B source/target types.

Action: Detach the domain-info from the referring B2B sources or targets. Then try deleting the domain-info again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02406: Cannot delete the domain-info(name {0}) because it is referenced in some Healthcare source/target types.

Cause: Cannot delete the domain-info because it is referenced in some Healthcare source/target types.

Action: Detach the domain-info from the referring Healthcare sources or targets. Then try deleting the domain-info again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02407: Cannot delete the callout(name {0}) because it is referenced in some transfer preprocessing.

Cause: Cannot delete the callout because it is referenced in some transfer preprocessing.

Action: Detach the callout from the referring transfer preprocessing. Then try deleting the callout again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02408: Cannot delete the callout(name {0}) because it is referenced in some transfer postprocessing.

Cause: Cannot delete the callout because it is referenced in some transfer postprocessing.

Action: Detach the callout from the referring transfer postprocessing. Then try deleting the callout again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02409: Cannot delete the domain-info(name {0}) because it is referenced in some Web Service source/target types.

Cause: Cannot delete the domain-info because it is referenced in some Web Service source/target types.

Action: Detach the domain-info from the referring Web Service sources or targets. Then try deleting the domain-info again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02410: Error occurred while deleting the transfer [{0}] from metadata store.

Cause: Exception while deleting the given transfer from metadata store.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02411: Error occurred while deleting the target [{0}] from metadata store.

Cause: Exception while deleting the given target from metadata store.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02501: Error occurred while deploying the source artifact with id [{0}].

Cause: Error occurred while deploying the given source artifact.

Action: The configuration of the given source artifact may be incorrect or error occurred while deploying the artifact. Check the source configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02502: Error occurred while enabling the source artifact with id [{0}].

Cause: Error occurred while enabling the given source artifact.

Action: The configuration of the given source artifact may be incorrect or error occurred while enabling the artifact. Check the source configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02503: Error occurred while disabling the source artifact with id [{0}].

Cause: Error occurred while disabling the given source artifact.

Action: The configuration of the given source artifact may be incorrect or error occurred while disabling the artifact. Check the source configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02504: Error occurred while undeploying the source artifact with id [{0}].

Cause: Error occurred while undeploying the given source artifact.

Action: The configuration of the given source artifact may be incorrect or error occurred while undeploying the artifact. Check the source configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02505: Could not delete Deployment record for the currently deployed {0} [{1}] with label [{2}].

Cause: Artifact corresponding to given name and label is currently an Active deployment.

Action: Undeploy the artifact from the MFT console monitoring page and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02506: Deployment record does not exist for {0} [{1}] with label [{2}].

Cause: Artifact corresponding to given name and label is not found.

Action: Review the deployment history from the MFT console deployment page for the given artifact and check if artifact with the given label exists.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02507: Artifact {0} of type {1} is referenced in Transfer {2}.

Cause: Artifact corresponding to the given name is referenced in a transfer and cannot be deleted.

Action: Review deployment history for the given artifact and make sure it is not referenced in Transfer Deployments.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02508: Error deploying source {0}. Another source {1} was found deployed for URL {2}.

Cause: Another source that is already deployed is configured with the same URL.

Action: Configure the source with a different URL and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02509: Error deploying source {0}. Another source {1} was found deployed for folder {2}.

Cause: Another source that already deployed is configured with the same folder.

Action: Configure the source with a different folder and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02510: Error deploying SFTP source {0}. The configured private key is incorrect.

Cause: Error occurred while deploying the sFTP source. The configured private key is incorrect.

Action: Check if the key is imported to the key store. If not, import it and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02511: Error deploying SFTP target {0}. The configured private key is incorrect.

Cause: Error occurred while deploying the sFTP target. The configured private key is incorrect.

Action: Check if the key is imported to the key store. If not, import it and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02512: Error deploying source {0}. The configured PGP encryption alias is incorrect.

Cause: Error occurred while deploying the source. The configured PGP encryption alias is not valid.

Action: Check if the encryption key is imported to the key store. If not, import it and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02513: Error deploying source {0}. The configured PGP decryption alias is incorrect.

Cause: Error occurred while deploying the source. The configured PGP decryption alias is not valid.

Action: Check if the decryption key is imported to the key store. If not, import it and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02514: Error deploying transfer {0}. The configured PGP encryption alias for target {1} is incorrect.

Cause: Error occurred while deploying the target. The configured PGP encryption alias is not valid.

Action: Check if the encryption key is imported to the key store. If not, import it and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02515: Error deploying transfer {0}. The configured PGP decryption alias for target {1} is incorrect.

Cause: Error occurred while deploying the target. The configured PGP decryption alias is not valid.

Action: Check if the decryption key is imported to the key store. If not, import it and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02516: Error deploying transfer {0}. No Internal server address configured in server properties.

Cause: Error occurred while deploying the Web Service target. The internal server address is not configured.

Action: Go to the Server Properties page and check the internal server information under Advanced Delivery Properties. Enter correct values and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02517: Error deploying transfer {0}. No External server address configured in server properties.

Cause: Error occurred while deploying the Web Service target. The external server address is not configured.

Action: Go to the Server Properties page and check the external server information under Advanced Delivery Properties. Enter correct values and try deployment again
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02518: Error deploying transfer {0}. No internal FTP port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The Internal Server FTP port is not configured in server properties.

Action: Go to the Server Properties page and check the internal server information under Advanced Delivery Properties. Enter correct values and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02519: Error deploying transfer {0}. No external FTP port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The External FTP port is not configured in server properties.

Action: Go to the Server Properties page and check the external server information under Advanced Delivery Properties. Enter correct values and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02520: Error deploying transfer {0}. No internal FTPS port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The Internal Server FTPS port is not configured in server properties.

Action: Go to the Server Properties page and check the internal server information under Advanced Delivery Properties. Enter correct values and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02521: Error deploying transfer {0}. No external FTPS port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The External FTPS port is not configured in server properties.

Action: Go to the Server Properties page and check the external server information under Advanced Delivery Properties. Enter correct values and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02522: Error deploying transfer {0}. No internal sFTP port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The Internal Server sFTP port is not configured in server properties.

Action: Go to the Server Properties page and check the internal server information under Advanced Delivery Properties. Enter correct values and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02523: Error deploying transfer {0}. No external sFTP port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The External sFTP port is not configured in server properties.

Action: Go to the Server Properties page and check the external server information under Advanced Delivery Properties. Enter correct values and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02524: Deployment validation failed while deploying source {0}.

Cause: Deployment validation failed while deploying the source.

Action: Check the source configuration and try again. Deploy from the UI again to check what validations failed or deploy the source using WLST in interactive mode.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02525: Deployment validation failed while deploying transfer {1}.

Cause: Deployment validation failed while deploying the transfer.

Action: Check the transfer configuration and try again. Deploy from the UI again to check what validations failed or deploy the transfer using WLST in interactive mode.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02526: Deployment validation failed while deploying target {1}.

Cause: Deployment validation failed while deploying the target.

Action: Check the target configuration and try again. Deploy from the UI again to check what validations failed or deploy the target using WLST in interactive mode.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02527: Deployment of source {0} failed. The password configured is incorrect.

Cause: Deployment of source failed due to invalid password.

Action: Check the key store configuration and ensure the password configured for the source is available in the key store.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02528: Deployment of target {0} failed. The password configured is incorrect.

Cause: Deployment of target failed due to invalid password.

Action: Check the key store configuration and ensure the password configured for the target is available in the key store.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02529: Error deploying source {0}. Transport Endpoint validation failed.

Cause: Error occurred while deploying the source. Transport validation failed due to incorrect configuration of the source endpoint.

Action: Check the source configuration and try again. Deploy from the UI again to check what validations failed or deploy the source using WLST in interactive mode.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02530: Error deploying Target {0}. Transport endpoint validation failed.

Cause: Error occurred while deploying the target. Transport validation failed due to incorrect configuration of the target endpoint.

Action: Check the target configuration and try again. Deploy from the UI again to check what validations failed or deploy the target using WLST in interactive mode.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02531: Invalid configuration found in the associated source {0}.

Cause: Error occurred while deploying the transfer because source configuration is invalid.

Action: Go to the source page, fix the invalid configuration, and try redeploying the transfer.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02532: Invalid configuration found in the associated target {0}.

Cause: Error occurred while deploying the transfer because the target configuration is invalid.

Action: Go to the target page, fix the invalid configuration, and try redeploying the transfer.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02533: Error. Could not find a deployment record for source [{0}].

Cause: A deployment record for the given source artifact could not be found in database.

Action: Deploy the source and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02534: Error. Could not find a deployment record for target [{0}].

Cause: A deployment record for the given target artifact could not be found in database.

Action: Deploy the target and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02535: Error. Could not find a deployment record for transfer [{0}].

Cause: A deployment record for the given transfer artifact could not be found in database.

Action: Deploy the transfer and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02536: The transfer [{0}] is already enabled.

Cause: The deployment record for the given transfer artifact is already enabled.

Action: No action required.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02537: The source [{0}] is already enabled.

Cause: The deployment record for the given source artifact is already enabled.

Action: No action required.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02538: The target [{0}] is already enabled.

Cause: The deployment record for the given target artifact is already enabled.

Action: No action required.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02539: The transfer [{0}] is already disabled.

Cause: The deployment record for the given transfer artifact is already disabled.

Action: No action required.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02540: The source [{0}] is already disabled.

Cause: The deployment record for the given source artifact is already disabled.

Action: No action required.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02541: The target [{0}] is already disabled.

Cause: The deployment record for the given target artifact is already disabled.

Action: No action required.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02542: Error occurred while deploying the transfer artifact with id [{0}].

Cause: Error occurred while deploying the given transfer artifact.

Action: The configuration of the given transfer artifact may be incorrect or error occurred while deploying the artifact. Check the transfer configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02543: Error occurred while deploying the target artifact with id [{0}].

Cause: Error occurred while deploying the given target artifact.

Action: The configuration of the given target artifact may be incorrect or error occurred while deploying the artifact. Check the target configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02544: Error occurred while enabling the transfer artifact with id [{0}].

Cause: Error occurred while enabling the given transfer artifact.

Action: The configuration of the given transfer artifact may be incorrect or error occurred while enabling the artifact. Check the transfer configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02545: Error occurred while enabling the target artifact with id [{0}].

Cause: Error occurred while enabling the given target artifact.

Action: The configuration of the given target artifact may be incorrect or error occurred while enabling the artifact. Check the target configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02546: Error occurred while disabling the transfer artifact with id [{0}].

Cause: Error occurred while disabling the given transfer artifact.

Action: The configuration of the given transfer artifact may be incorrect or error occurred while disabling the artifact. Check the transfer configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02547: Error occurred while disabling the target artifact with id [{0}].

Cause: Error occurred while disabling the given target artifact.

Action: The configuration of the given target artifact may be incorrect or error occurred while disabling the artifact. Check the target configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02548: Error occurred while undeploying the transfer artifact with id [{0}].

Cause: Error occurred while undeploying the given transfer artifact.

Action: The configuration of the given transfer artifact may be incorrect or error occurred while undeploying the artifact. Check the transfer configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02549: Error occurred while undeploying the target artifact with id [{0}].

Cause: Error occurred while undeploying the given target artifact.

Action: The configuration of the given target artifact may be incorrect or error occurred while undeploying the artifact. Check the target configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02550: Error creating source [{0}]. Another source was found with this name.

Cause: Another source found with the same name as the given name.

Action: Configure the source with a different name and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02551: Error creating target [{0}]. Another target was found with this name.

Cause: Another target found with the same name as the given name.

Action: Configure the target with a different name and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02552: Error creating transfer [{0}]. Another transfer was found with this name.

Cause: Another transfer found with the same name as the given name.

Action: Configure the transfer with a different name and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02553: Incorrect additional http header value. Use key value pair and # as separator.Example pro1=value1#pro2=value2.

Cause: Incorrect additional http header value.

Action: Correct the value and try deploying again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02554: Payload access is referring to invalid user/groups/roles.

Cause: Payload access is referring to invalid resource.

Action: Associate valid users/groups/roles and try redeploying the transfer.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02555: Not valid integer value [{0}] for attribute [{1}].

Cause: Not valid integer value.

Action: Correct the value and reperform the action.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02556: Not valid boolean value [{0}] for attribute [{1}]. Only true/false is allowed.

Cause: Not valid boolean value.Only true/false is allowed.

Action: Correct the value and reperform the action.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02557: Not valid value [{0}] for attribute [{1}]. Only allowed values are {2}.

Cause: Possible values for the field are restricted to predefined. Specified value is not allowed for this field.

Action: Correct the value and reperform the action.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02558: Invalid patten [{0}].

Cause: Invalid pattern.

Action: Correct the pattern and reperform the action.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02559: Error creating source [{0}]. Another deployed source was found with this name.

Cause: Another deployed source found with the same name as the given name.

Action: Configure the source with a different name or undeploy the other source with same name and try again
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02560: Error creating target [{0}]. Another deployed target was found with this name.

Cause: Another deployed target found with the same name as the given name.

Action: Configure the target with a different name undeploy the other target with same name and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02561: Error creating transfer [{0}]. Another deployed transfer was found with this name.

Cause: Another deployed transfer found with the same name as the given name.

Action: Configure the transfer with a different name or undeploy the other transfer with same name and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02562: Another source [{0}] was found with similar settings. Undeploy one of the source if they are identical.

Cause: Another source with similar settings is already deployed.

Action: Undeploy one of the source is its duplicate.
Level: LOW

Type: WARNING

Impact: SYSTEM

MFT-02563: Error deploying source {0}. The configured signing key alias is incorrect.

Cause: Error occurred while deploying the source. The configured PGP signing key alias is not valid.

Action: Check if the signing key is imported to the key store. If not, import it and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02564: Error deploying transfer {0}. The configured PGP signing key alias for target {1} is incorrect.

Cause: Error occurred while deploying the target. The configured PGP signing key alias is not valid.

Action: Check if the PGP signing key is imported to the key store. If not, import it and try deployment again.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02565: Invalid processing funcation order.

Cause: Invalid order specified for processing actions.

Action: Correct the processing order and retry.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02566: Callout param {0} doesn''t matches with the callout[{1}] definition.

Cause: Invalid paramerter specified in the request.

Action: Refer to the callout definition. Correct the callout parameters and rety.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02567: No need to deploy as latest version of the artifact is already deployed.

Cause: Latest version of the artifact is already deployed.

Action: No need to deploy the artifact again.
Level: LOW

Type: WARNING

Impact: MESSAGE

MFT-02568: startDate is not specified for the schedule.

Cause: startDate is required for the schedule.

Action: Provide the startDate and retry.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02569: Illegal Arguments Exception while fetching list of schedule occurrences from ESS

Cause: Problem with arguments passed to function

Action: Provide a valid time zone and retry
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02570: Unable to fetch schedule by schedule name

Cause: The Schedule name is invalid

Action: Provide a valid schedule name and retry
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02571: Schedule has expired

Cause: The Schedule has expired

Action: Change the schedule to a valid range and retry
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02572: Unable to submit schedule purge job

Cause: Submitting the purge job to ESS threw an exception

Action: Change the schedule and retry
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-02600: Error in creating target {0} . Error Message: {1}

Cause: An Error occurred while either reading or parsing the metadata xml file.

Action: Refer to the plugin logs for more details.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-03001: Error while starting the MFT server.

Cause: Unable to initialize the MFT Server dependent components.

Action: Ensure the infrastructure components like Identity Store, Security Store, Database, JCA are configured properly.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03002: Error while registering the Web Service source {0} with the provider.

Cause: Unable to register the Web Service source with the provider.

Action: Verify the Web Service source configuration and provider availability.Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03003: Error while Initializing Web Service source {0}.

Cause: An error occurred while registering the Web Service sources.

Action: Check the configuration of the deployed Web Service sources.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03004: Error while initializing Security components for Stripe {0}.

Cause: An Error occurred while creating the application policy data in the domain-wide policy store or while obtaining the connection to the default realm identity store.

Action: Ensure that the required permissions are granted to the MFT source and check the config parameters of the Identity Store.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03005: Error while initializing the WebLogic Work Manager {0}.

Cause: Unable to look up the Work Manager from the underlying environment.

Action: Check the Work Manager configuration in the WebLogic console.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03006: Error while registering the EM Discovery Mbean with Object name {0}.

Cause: An error occurred while registering the Config MBean with the Platform MBean Server.

Action: Review the diagnostic log for the exact error. Check whether management infrastructure is up and MFT MBean details are correct.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03007: Error while shutting down MFT server.

Cause: Unable to stop one or more dependent components of the MFT server.

Action: Review the diagnostic log for the exact error. Failure might be due to configuration of infrastructure components or connection problem.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03008: Error occurred while unsubscribing the Web Service source.

Cause: Unable to unsubscribe the Web Service source.

Action: Failure could be due to unavailability of Web Service registration service or improper Web Service configuration. Review the diagnostic log for the exact error.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03009: Error while getting the Application Properties metadata.

Cause: Unable to get the Application Properties details.

Action: Check the Application Properties configuration in the system.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03010: Error occurred while updating the port {2} for service {1} of server {0} by user {3}

Cause: Exception while updating the port details of databases.

Action: Check the service, server instance and port. If these are correct it could be due to database issue. Review the diagnostic log for the exact error.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03011: Error while loading the MFT Configuration MBean Properties from underlying infrastructure.

Cause: Unable to load the MBean Properties.

Action: Unable to load the MBean config properties from the underlying metadata store. Review the diagnostic log for the exact error.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03012: Error while initializing the MFT persistence context.

Cause: Unable to initialize the persistence units context.

Action: Check the database availability and connection configuration. Review the diagnostic log for the exact error.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03013: Error while initializing the MFT System event manager.

Cause: Unable to initialize the System event manager with required Queue and Topic receiver(s).

Action: Check the JMS system event Queue and Topic configurations in the WebLogic console.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03014: Error while initializing the MFT Purge event manager.

Cause: Unable to initialize the Purge event manager with required Queue receiver(s).

Action: Check the JMS purge event Queue and Topic configurations in the WebLogic console.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03015: Error while initializing the source listener {0}

Cause: Unable to start the JCA adapter to poll the files on the source.

Action: Check the source configuration parameters. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03016: Error updating port for server instance [{0}] and service [{1}]. The given server instance or service is incorrect.

Cause: Error occurred while updating port assignment for the given server instance and service in database.

Action: Check the port configuration for the server instance. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03017: File [{0}] doesn''t exists.

Cause: File doesn't exist.

Action: Check if the file exists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03018: Not able to create file [{0}].

Cause: Invalid location.

Action: Check if the parent directory exists. Also, check the file permission for the parent directory.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03019: Invalid XML format or scheam validation failed for [{0}].

Cause: Invalid XML or schema validation failed.

Action: Validate the XML against the schema and rerun.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03250: Invalid argument(s) {0} provided to MFT utility for method {1}.

Cause: Arguments of the MFT command line utility are either missing or invalid.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03251: MFT utility - Operation {0} failed for parameters {1}.

Cause: EJBException thrown by the MFT utility due to failure in operation.

Action: Refer to MFT utilities documentation to determine the arguments and their types for the given command.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03252: Exception occurred while executing runtime purge for batch id [{0}].

Cause: Exception occurred while executing runtime purge for batch id [{0}].

Action: Try again with the recovery option by passing same batch id. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03253: Error while processing the purge event {0}.

Cause: An error occurred during processing of the purge event by the JCA JMS Adapter.

Action: Check the Purge Event Queue configuration in the server. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03254: Exception occurred while executing runtime archive for batch id [{0}].

Cause: Exception occurred while executing runtime archive for batch id [{0}].

Action: Try again by passing same batch id. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03255: Exception occurred while executing runtime restore from archive file [{0}].

Cause: Exception occurred while executing runtime restore from archive file [{0}].

Action: Try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03302: Failed to initialize the engine. The engine message queue receivers for queue {0} were not initialized properly.

Cause: Problem with JMS queue settings.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Correct the queue settings and restart the MFT server.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03303: Error while stopping queue receivers for queue {0}.

Cause: An error has occurred while stopping the queue receivers.

Action: Review the diagnostic log for the exact error. Check the MFT specific JMS Queue settings in the WebLogic console.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-03304: Failed to initialize the engine. The engine queue message producer for queue {0} was not initialized properly.

Cause: Problem with JMS queue settings.

Action: Check the MFT specific JMS Queue settings in the WebLogic console.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-03305: Error while stopping the message producer for queue {0}.

Cause: An error has occurred while stopping queue message producer.

Action: Review the diagnostic log for the exact error. Check the MFT specific JMS Queue settings in the WebLogic console.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-03306: Error while initializing the source listeners

Cause: Unable to start the JCA adapter to poll the files on the sources.

Action: Check the source configuration parameters. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03307: Error initializing the MFT message processing engine.

Cause: An error has occurred while starting the message processing engine for MFT.

Action: Check the MFT specific JMS Queue settings in the WebLogic console.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03308: Error during shutdown of source listener {0}.

Cause: Unable to stop the JCA Adapter that is polling the source.

Action: Review the diagnostic log for the exact error. Check the MFT specific JMS Queue settings in the WebLogic console.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03309: Error stopping the MFT message processing engine.

Cause: An error has occurred while stopping the message processing engine for MFT.

Action: Review the diagnostic log for the exact error. Check the MFT specific JMS Queue settings in the WebLogic console.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03310: Error initializing the task queue receivers.

Cause: An error has occurred while starting the task queue receivers for MFT.

Action: Check the MFT task queue JMS Queue settings in the WebLogic console.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03601: Error while starting the hosted server {0} with root dir {1} and port {2}.

Cause: An error occurred while starting the hosted server at a specified port and root directory.

Action: Check the root directory and Port assigned to the hosted server. For FTP over SSL and sFTP Servers, verify that all the required keys are configured.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03602: Error while shutting down the Hosted Server {0} running at port {1}.

Cause: An error occurred while stopping the hosted server running at the specified port.

Action: Review the diagnostic log for the exact error.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03604: Error while allocating the HA ports for the server instance {0}.

Cause: An error occurred while persisting the ports of the hosted servers for a given server instance.

Action: Check the ports definitions in MDS and the database config parameters. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'.Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03605: Error while fetching the Key store configuration from MDS.

Cause: An Error occurred while getting the default key store MO from MDS.

Action: Unable to get the key store information from the underlying metadata store during initialization. Review the diagnostic log for the exact error.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03606: Error while fetching the ES root directories from path {0} with option {1} for {2} server

Cause: An Error occurred while getting the directories under the ES root directory

Action: Check the Embedded Server root directory configuration and access permissions. Review the diagnostic log for the exact error.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-04001: No associated active source found for the incoming file {0} from the endpoint {1}.

Cause: No matching MFT source found for the incoming message.

Action: Create and deploy the matching source. Redeliver the message to MFT.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04002: Multiple matching active sources found for the file {0} from endpoint {1}. Matching sources : {3}.

Cause: Invalid configuration: multiple active deployed sources for the same endpoint.

Action: Activate only one source for a given endpoint configuration.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04003: Not able to find the metadata reference for source with id {0}.

Cause: Reference metadata for the given source id does not exist in repository.

Action: Restore the deleted data in the metadata repository and redeploy the source.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04004: Invalid source message received for source message processing. Source message ID {0}.

Cause: Internal processing error.

Action: Contact Oracle Support Services.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04005: Invalid source configuration.

Cause: Invalid source configuration.

Action: The listening or Web Service source could not be registered due to error while creating the endpoint. Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04007: Associated source {2} for the file {0} from endpoint {1} was disabled.

Cause: Associated source was disabled.

Action: Enable the source and redeliver the message to MFT.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04008: No matching active transfer found for the message.

Cause: There is no associated transfer with a matching content type for the incoming message.

Action: Associate and deploy the matching transfer for the incoming message and resubmit the source message.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04009: Error during source message processing.

Cause: Unexpected error.

Action: Unexpected error encountered during source processing. Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04010: Source {0} is disabled.

Cause: Source is disabled.

Action: Enable the source and retry.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04011: Duplicate source message. Original message id {0}.

Cause: Duplicate message submitted.

Action: Check the status of original message.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04012: Directory reference as payload is not allowed for the source if compression processing action is not associated with the source.

Cause: Directory reference as payload is not allowed if compression processing action is not associated with the source.

Action: Associate compression as processing action for the source and redeploy the source. Resubmit the message after that.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04013: Invalid Payload information.

Cause: Bad request or specified payload doesn't exists.

Action: Send valid request, make sure payload information is correct.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04014: No source metadata record found with name [{0}].

Cause: No source metadata record found with given name.

Action: Check if the source metadata was deleted. Try again by specifying correct source name.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04015: Source plugin error while creating the endpoint from source metadata.

Cause: Plugin error while creating the endpoint from source metadata..

Action: Check the logs for more details. In case of custom plugin implementation, check the plugin implementation otherwise contact Oracle Support Services if the problem persists
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04202: File {0} does not exist in the file system.

Cause: File does not exist in the file system.

Action: If the file has been purged, restore the file and resubmit the appropriate message.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04204: IO exception encountered during message processing.

Cause: IO exception.

Action: IO exception encountered. Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04205: Error while encrypting the payload using PGP.

Cause: PGP encryption setting error.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04206: Error while decrypting payload using PGP.

Cause: Invalid PGP-encrypted payload.

Action: Check the incoming payload.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04207: Error while compressing the payload.

Cause: Compression setting error.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04208: Error while decompressing the payload.

Cause: Invalid compressed payload.

Action: Check the incoming payload.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04209: Error while executing source preprocessing

Cause: Unexpected source preprocessing error.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04210: Error while executing source postprocessing

Cause: Unexpected source postprocessing error.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04211: Error while executing target preprocessing

Cause: Unexpected target preprocessing error.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04212: Error while executing target postprocessing.

Cause: Unexpected target postprocessing error.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04213: Error during instance message processing.

Cause: Unexpected error.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04214: Unsupported compressed payload content.

Cause: The compression format of the payload is not supported in MFT.

Action: None: compressed format is not supported in MFT.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04215: Multiple file decompression is only supported for web service targets: SOAP, SOA, Service Bus, and ODI

Cause: Compressed payload contains multiple files.Multiple file decompression is only supported for web service targets: SOAP, SOA, Service Bus, and ODI.

Action: Decompress and submit a message for each decompressed file.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04216: No file found after decompression.

Cause: There were no files found after decompression.

Action: None: Invalid input message.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04217: PGP private key not found for key alias {0}

Cause: Key for the alias is not present in the key store.

Action: Import the key and resubmit the message.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04218: PGP public key not found for key alias {0}

Cause: Key for the alias is not present in the key store.

Action: Import the key and resubmit the message.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04219: Message cannot be processed as the associated schedule has expired.

Cause: Message cannot be processed as the associated schedule has expired.

Action: Associate valid schedule and redeploy.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04220: PGP private key is invalid or key password is incorrect.

Cause: PGP private key is invalid or key password is incorrect.

Action: Correct the key password if key password is incorrect otherwise import valid PGP private key.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04221: Incoming data is encrypted with different public key.

Cause: PGP public key used for encryption is not corresponding key pair for private key specified.

Action: Associate correct private key alias for the decryption action.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04222: Incoming data is not a valid PGP encrypted data.

Cause: Incoming data is not a valid PGP encrypted data.

Action: Check the incoming data.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04223: Encryption algorithm or key length is restricted under the java policy.

Cause: Encryption algorithm or key length is restricted.

Action: Make sure algorithms and key used is not restricted under java security policy.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04224: PGP Encryption key is not a valid encryption key.

Cause: PGP Encryption key is not a valid encryption key.

Action: Make sure key alias is a correct PGP encryption public key.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04225: Error while decryption.Signature is not valid.

Cause: Signature is not valid.

Action: Check if the encrypted payload is valid or not.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04226: Cannot find the matching signee key.

Cause: Unknown signee.

Action: Add signee's pgp key to the key store.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04227: Script({0}) execution failed with error: ({1})

Cause: Error in script execution.

Action: Review the diagnostic log for the exact error and resubmit the message after fixing script.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04228: Script({0}) execution failed with unknown error

Cause: Unexpected error in script execution.

Action: Review the diagnostic log for the exact error and resubmit the message after fixing script.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04229: Script({0}) execution timed out

Cause: Script execution timed out.

Action: Script execution is taking longer time then given timeout. Fix the script and resubmit the message.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04230: Script({0}) execution interrupted

Cause: Script execution interrupted.

Action: Please validate the script.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04401: Exception encountered during execution of callout {0}.

Cause: Error while executing custom callout.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04501: Payload {0} not found in the MFT data storage.

Cause: Payload does not exist in the MFT data storage.

Action: If the data exists, try to restore the data.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04502: Invalid digest algorithm {0}.

Cause: Invalid algorithm.

Action: Correct the setting for the digest algorithm.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04503: Unexpected Error.

Cause: Unexpected exception occurred.

Action: Review the diagnostic log for the exact error.
Level: MEDIUM

Type: ERROR

Impact: MESSAGE

MFT-04504: JTA Transaction Error

Cause: JTA Transaction Error

Action: Review the diagnostic log for the exact error.
Level: MEDIUM

Type: ERROR

Impact: MESSAGE

MFT-04506: The archive {0} does not exist.

Cause: The given archive file could not be found. The file path is incorrect or the archive is empty.

Action: Check the archive file path. If path is correct, then ensure that the archive file is proper and try again.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04507: IP address or name of the host machine could not be determined.

Cause: IP address or name of the host machine could not be determined.

Action: Check if the system and network configuration is correct. Contact Oracle Administrator if problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-04508: Invalid argument.

Cause: Invalid argument.

Action: Check the input arguments provided and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04509: External ports in the application properties cannot be null.

Cause: External ports in the application properties are null.

Action: Set the external ports in the application properties.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04510: External ports in the application properties cannot be null.

Cause: External ports in the application properties are null.

Action: Set the external ports in the application properties.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04511: External ports in the application properties cannot be null.

Cause: External ports in the application properties are null.

Action: Set the external ports in the application properties.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04512: Error creating the directory {0}.

Cause: IO exception.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04513: Invalid in-progress transfer count {0} for source.

Cause: Unexpected error.

Action: Internal error while calculating the progress in transfer count. No action needed.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04514: Invalid in-progress target count {0} for the transfer.

Cause: Unexpected error.

Action: Internal error while calculating the progress in transfer count. No action needed.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04515: Transfer {0} is disabled.

Cause: Transfer is disabled.

Action: Enable the transfer and retry.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04516: Target {0} is disabled.

Cause: Target is disabled.

Action: Enable the target and retry.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04517: No target record found for the instance ID {0}.

Cause: No target record found for the instance.

Action: Try resubmitting the transfer or source instead.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04518: Target {0} is no longer associated with transfer {1}.

Cause: Target is no longer associated with transfer {1}.

Action: Associate the target with the transfer and retry.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04519: Unexpected error occurred while processing message with id [{0}].

Cause: An unexpected error occurred during processing of the message with the given message id.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04520: Internal ports in the application properties cannot be null.

Cause: Internal ports in the application properties are null.

Action: Set the internal ports in the application properties.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04521: Internal ports in the application properties cannot be null.

Cause: Internal ports in the application properties are null.

Action: Set the internal ports in the application properties.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04522: Internal ports in the application properties cannot be null.

Cause: Internal ports in the application properties are null.

Action: Set the internal ports in the application properties.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04523: Error while moving the file [{0}] to location [{1}].

Cause: Issue while moving the file from one location to another.

Action: Check user permissions in the destination location.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04524: Unexpected error occurred during instance message processing for transfer [{0}].

Cause: An unexpected error occurred during instance message processing for the given transfer.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04525: Unexpected error occurred during message processing for target [{0}].

Cause: An unexpected error occurred during message processing for the given target.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04526: Unexpected error occurred during message processing for source [{0}].

Cause: An unexpected error occurred during message processing for the given source.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04801: Error while processing the system event {0}.

Cause: An error occurred during processing of the system event by the JCA JMS Adapter.

Action: Check the System Event Queue and Topic configuration in the server. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-04802: Error while submitting the system event {0} for service {1}.

Cause: An error occurred during processing of the system event by the JCA JMS Adapter.

Action: Check the System Event Queue and Topic configuration in the server. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-04803: Error while submitting the system event {0} with resubmit type as {1} for instances {2} by user {3}.

Cause: An error occurred during submission of the system event by the JCA JMS Adapter.

Action: Check the System Event Queue and Topic configuration in the server. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-04804: Error while submitting the system event {0} with instance ID {1} by user {2}.

Cause: An error occurred during submission of the system event by the JCA JMS Adapter.

Action: Check the System Event Queue and Topic configuration in the server. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-04805: Error while submitting pause transfer request. Target Message with Id [{0}] does not exist.

Cause: The given target message does not exist in database.

Action: Check the target message Id is correct and try again. Use the UI Monitoring Dashboard to verify target message details.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-04806: Error while submitting resume transfer request. Target Message with Id [{0}] does not exist.

Cause: The given target message does not exist in database.

Action: Check the target message Id is correct and try again. Use the UI Monitoring Dashboard to verify target message details.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05001: Unsupported endpoint {0} passed to adapter.

Cause: Unsupported endpoint has been passed to the adapter. Adapter only supports File / FTP / sFTP / JMS.

Action: Check the endpoint that was passed.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05002: Error occurred while creating JCABindingFactoryImpl. Type: {0}, endpoint: {1}.

Cause: An error occurred while initializing the adapter.

Action: Check the adapter properties and try again. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05003: No payload found while delivering to endpoint {0}.

Cause: No payload found while delivering a message.

Action: Try resubmitting the message.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05004: Error occurred while delivering message [{0}] to endpoint [{1}].

Cause: Error occurred while delivering message.

Action: Check the adapter properties and try again. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05005: Error occurred while closing connection after sending file to end point [{0}].

Cause: Error occurred while closing adapter connection.

Action: Check adapter properties and try again. If the problem persists,contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05006: Error occurred while trying to open connection for endpoint [{0}], Type [{1}] and interface [{2}].

Cause: Error occurred while trying to open connection.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05007: Exception occurred while sending file [{0}] to endpoint [{1}].

Cause: File [{0}] does not exist.

Action: Ensure that the file [{0}] exists and resubmit.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05008: Exception occurred while creating connection with [{0}] for operation [{1}].

Cause: Error occurred while creating connection.

Action: Check the adapter properties and try again. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05010: Exception occurred while validating adapter binding reference property for end point [{0}].

Cause: Could not validate Binding reference properties.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05011: Value for property 'Physical Directory' is missing.

Cause: No value specified for property 'Physical Directory' in the input connection properties.

Action: Specify a value for 'Physical Directory' in the connection properties for the endpoint and try again.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05012: Exception occurred while creating connection for polling to end point [{0}] for operation [{1}]

Cause: Error occurred while creating connection.

Action: Check the adapter properties and try again. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05013: Exception occurred while creating poller service for endpoint [{0}].

Cause: Error occurred while creating poller service.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05014: Exception occurred while starting poller service for endpoint [{0}].

Cause: Error occurred while starting poller service.

Action: Check the adapter properties and try again. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05015: Exception occurred while validating poller service for endpoint [{0}].

Cause: Could not validate adapter properties for poller service.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05016: NOT_IN_USE

Cause: NOT_IN_USE

Action: NOT_IN_USE
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05017: Error occurred while stopping the adapter polling.

Cause: Exception occurred while trying to close the adapter to stop polling the messages.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05018: NOT_IN_USE

Cause: NOT_IN_USE

Action: NOT_IN_USE
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05019: Exception occurred while creating file [{0}] received from end point [{1}]

Cause: Could not create the file [{0}], which was received from endpoint [{1}].

Action: Check if the file exists but is a directory rather than a regular file, does not exist but cannot be created, or cannot be opened for any other reason.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05020: IO Exception occurred while writing to file [{0}] received from endpoint [{1}].

Cause: File created, but could not write to the file [{0}], which was received from endpoint [{1}].

Action: Check if write permissions are provided for file [{0}].
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05021: IO Exception occurred while closing file [{0}] after writing. This file was received from endpoint [{1}].

Cause: File [{0}] written, but IO exception occurred while closing the file, which was received from endpoint [{1}].

Action: Check if write permissions are provided for the file [{0}].
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05022: Source Message was found null while transferring to endpoint [{0}].

Cause: Source message found null.

Action: Resubmit the message. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05023: The JNDI queue name specified is null.

Cause: Adapter initialization failed because of invalid queue name.

Action: Try again. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05024: Exception occurred in postprocessing while moving or renaming the file after sending to [{5}]. Source File Name [{1}], Source Folder [{0}], Target Folder [{2}], Target File Name [{3}], Target File Naming Convention [{4}].

Cause: Error occurred while moving or renaming a file after sending.

Action: Check the adapter properties and resubmit the message. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05025: Exception occurred while creating directory [{0}] for storing file [{1}] received from endpoint [{2}].

Cause: Could not create directory [{0}].

Action: Ensure that permissions (for creating directory and files) are assigned to this folder.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05026: NOT_IN_USE

Cause: NOT_IN_USE

Action: NOT_IN_USE
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05027: Exception occurred while looking for directory for storing file [{0}] received from endpoint [{1}].

Cause: Error occurred while looking for directory for storing file.

Action: Check server properties. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05028: Exception occurred while deactivating poller service for end point [{0}].

Cause: Error occurred while deactivating poller service.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05029: Exception occurred while closing poller service for endpoint [{0}].

Cause: Error occurred while closing poller service.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05030: Configuration mismatch found while polling to endpoint [{0}]. Alert code [{1}].

Cause: Configuration mismatch found while polling to endpoint [{0}].

Action: Ensure that the host name, port, username and password configured are correct and that the server is running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05031: Error occurred while reading metadata of file [{0}] from endpoint [{1}].

Cause: Error occurred while reading metadata of file.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05032: Unexpected error during target delivery.

Cause: Unexpected error during target delivery.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05033: Error while creating the B2B/Healthcare endpoint {0} during target delivery.

Cause: Unexpected error while creating a b2b/healthcare endpoint.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05034: Error while delivering the payload to B2B/Healthcare target.

Cause: Unexpected error while delivering the payload.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05035: Error occurred while closing connection after getting size for file [{0}] for end point [{1}].

Cause: Error occurred while closing adapter connection.

Action: Check adapter properties and try again. If the problem persists,contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05036: Error occurred while closing connection after pausing transfer for end point [{0}].

Cause: Error occurred while closing adapter connection.

Action: Check adapter properties and try again. If the problem persists,contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05037: Value for property 'Host Name' is missing.

Cause: No value specified for property 'Host Name' in the input connection properties.

Action: Specify a value for 'Host Name' in the connection properties for the endpoint and try again.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05038: Value for property 'Port' is missing.

Cause: No value specified for property 'Port' in the input connection properties.

Action: Specify a value for 'Port' in the connection properties for the endpoint and try again.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05039: Value for property 'User Name' is missing.

Cause: No value specified for property 'User Name' in the input connection properties.

Action: Specify a value for 'User Name' in the connection properties for the endpoint and try again.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05040: Error occurred during shutting down while clearing JCA resources.

Cause: Unexpected error occurred while clearing JCA resources.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05041: Error occurred while polling the listening source {0}.

Cause: Unexpected error occurred while polling the JCA source.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05201: Access denied.

Cause: Access denied for the resource/action.

Action: Check if you have the permission for given resource/action.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05202: Unable to authenticate the user.

Cause: An error occurred while authenticating the user.

Action: Correct the username/password and retry.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05203: The Content-MD5 you specified did not match what is received.

Cause: Content-MD5 mismatch.

Action: .
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05204: A container with same name already exists.

Cause: A container with same name already exists.

Action: Provide a different container name and retry.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05205: Container isn't empty.

Cause: There are some objects stored in the container.

Action: Delete all the objects in the container and retry.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05206: No container found for given container name.

Cause: No container found.

Action: Provide a valid container name or create new container with the given name.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05207: Invalid key name.

Cause: Invalid key name.

Action: Provide a valid key name and retry.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05208: The requested range cannot be satisfied.

Cause: Invalid range.

Action: Provide a valid range.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05209: Invalid request.

Cause: Some required parameter is missing in the request.

Action: Provide all the parameters in the request and retry.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05210: Unexpected server error.

Cause: Unexpected server error, response code 500.

Action: Check the service setting and retry. For more details, review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05211: Malformed URL used.

Cause: A malformed URL has occurred. Either no legal protocol could be found in a specification string or the string could not be parsed.

Action: Correct the provided url and retry.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05212: Unexpected error occurred.

Cause: Unexpected error.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05213: Unexpected source error occurred.

Cause: Unexpected error.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05214: Error encountered while connection/authentication.

Cause: Error while connection/authentication.

Action: Make sure the connection url and user information is correct. Also, make sure to import the certificate in the server.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05215: Client error encountered for the request.

Cause: Client error encountered for the request.

Action: Check the server connection/user details. Also, review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05216: Server error encountered for the request.

Cause: Server error encountered for the request.

Action: Check the storgae service setting.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05217: Malformed URI used.

Cause: A malformed URI has been used. Unable to locate the required file

Action: Correct the provided uri and retry.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05218: File Not Found.

Cause: File you are trying to refer to is not found

Action: Correct the provided file path.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05219: IO Exception

Cause: An I/O Exception occurred

Action: An I/O exception occurred.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05220: URI Exception

Cause: URI Exception has occurred

Action: Please provide a valid URI location
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05250: Error while reading or writing the serialized configuration information for [{0}].

Cause: Endpoint configuration issue.

Action: Check the configuration and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05251: Error in the idc filters.

Cause: Error in the idc filters.

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05252: Errors while processing service request [{0}] from content server [{1}].

Cause: Errors thrown from the Content Server.

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05253: Error in the connection for endpoint [{0}].

Cause: Error in the protocol layer.

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05255: Folder [{0}] ''t accessible.

Cause: Folder not accessible.

Action: Check if the remote folder exists and user has permission to access the folder.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05256: Error while processing the service due to SSL configuration and setup for endpoint [{0}].

Cause: Exception due to SSL configuration and setup.

Action: Make sure certificate is imported properly.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05257: Error occured during the post download operation[{0}].

Cause: Error occured during the post download operation.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05400: Invalid SOAP request received by MFTService on endpoint {0}.

Cause: SOAP message contains invalid XML.

Action: Review the SOAP request and check if the SOAP message contains invalid XML. This can be done by copying the request to a temporary XML file and opening the file in a web browser.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05401: MFT Service could not deliver message to Web Service endpoint {0}.

Cause: Web Service endpoint configured in MFT Target definition is either invalid or down.

Action: Check the Target configuration in the MFT console and verify the Web Service configuration parameters such as url , Port and Service. Try connecting to the configured endpoint by typing URL in a web browser.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-05402: Invalid SOAP request received by MFT Discovery Service from URL {0}.

Cause: SOAP Message contains invalid XML.

Action: Review the SOAP request and check if the SOAP message contains invalid XML. This can be done by copying the request to a temporary XML file and opening the file in a web browser.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05403: Discovery service is unable to query MFT Sources for the given application {0} and search Filter {1}.

Cause: MFT Source Message Table cannot be queried due to a Persistence Error.

Action: Verify whether the MFT Server is initialized successfully in the MFT Diagnostic Log. If there are issues in loading MFT persistence, try restarting MFT.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05404: Discovery service is unable to create a SOAP response for the given application {0} and search Filter {1}.

Cause: SOAP exception in creating SOAP response.

Action: Contact your Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05405: SOAP Request received on endpoint url {0} contains multiple attachments, which is not supported in MFT.

Cause: SOAP message contains an AttachmentPart that has multiple attachments. MFT does not support multiple attachments inline. Only one attachment is allowed.

Action: Review the SOAP request and make sure that the AttachmentPart has only one attachment.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05406: MFT Service is unable to process the AttachmentPart in the SOAP request received from endpoint url {0}.

Cause: IO error in reading the attachment stream.

Action: Review the SOAP request and make sure the attachment is configured according to SOAP standards.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05407: MFT Service is unable to process inline payload received from endpoint url {0}.

Cause: IO exception in reading inline Payload embedded in the SOAP body.

Action: Review the SOAP request and make sure the inline payload embedded in the SOAP body conforms to the schema defined in the MFT Service wsdl.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05408: MFT Service is unable to process reference payload coming from the endpoint url {0}.

Cause: IO exception in reading Reference payload embedded in the SOAP body.

Action: Review the SOAP request and make sure the FileReference or FTPReference element in the SOAP body conforms to the schema defined in the MFT Service wsdl.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05409: MFT Service is unable to process SOAP Headers coming from the endpoint url {0}

Cause: IO exception in reading SOAP Headers embedded in the SOAP message.

Action: Review the SOAP request and make sure the headers conform to the MFTHeader element schema defined in the MFT Service wsdl.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05410: Invalid url in Reference Payload element received on endpoint url {0} for reference type {1}.

Cause: For an incoming SOAP request containing a Reference Payload element, the URL defined in the message is invalid.

Action: Review the SOAP request and verify that the URL element in the Reference Payload contains a valid URL.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05411: Unable to create SOAP message from MessageFactory.

Cause: Unknown error due to the SOAP MessageFactory being unable to create the SOAP message.

Action: Contact the Oracle Administrator.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-05412: MFT Web Service transport is unable to create a SOAP Message with InlinePayload for Web Service endpoint {0}.

Cause: SOAP exception while adding InlinePayload element in the SOAP message. This could be due to invalid inline payload data passed to Transport layer

Action: Review the SOAP target configured in the MFT console to verify the Payload type and message type configuration. Also verify that the InlinePayload being passed to transport layer.
Level: CRITICAL

Type: ERROR

Impact: MESSAGE

MFT-05413: MFT Web Service transport is unable to create a SOAP Message with Reference Payload for Web Service endpoint {0}.

Cause: SOAP exception while adding Reference Payload element in the SOAP message. This could be due to invalid Reference payload data passed to Transport layer

Action: Review the SOAP target configured in the MFT console to verify the type of reference defined.
Level: CRITICAL

Type: ERROR

Impact: MESSAGE

MFT-05414: MFT Web Service transport is unable to create SOAP Message with Reference of type {0} for Web Service endpoint {1}

Cause: SOAP exception while adding FTP reference Payload element in the SOAP message. This could be due to invalid Reference payload data passed to the transport layer

Action: Review the SOAP target configured in the MFT console to verify the type of reference defined.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05415: MFT Web Service transport is unable to create SOAP Message with Base64 Encoded format for Web Service endpoint {0}

Cause: Error in encoding the SOAP message in Base64 format.

Action: Review the SOAP target configured in the MFT console to verify the payload type and MessageType.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05416: MFT Web Service transport is unable to create SOAP Message with SOAP Header {0} for Web Service endpoint {1}.

Cause: SOAP Exception while adding the SOAP headers to SOAP Message.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05417: MFT Web Service transport is unable to create SOAP Message with additional transport headers for Web Service endpoint {0}.

Cause: SOAP Exception while adding the HTTP headers to SOAP Message.

Action: Review Target configuration in MFT console to verify Additional headers field. Headers format is [header1]=[value1]#[header2]=[value2].
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05418: MFT Service is unable process SOAP Message containing Base64 content for Web Service endpoint {0}.

Cause: Error in Decoding the SOAP message containing Inline payload in Base64 format. This could be because the message does not contain a valid Base64 format.

Action: Review the SOAP target configured in the MFT console to verify the payload type and MessageType. Also check the SOAP request to validate the Base64 format.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05419: URL {0} configured for Web Service endpoint is invalid.

Cause: Web Service endpoint configured in MFT Target definition is either invalid or down.

Action: Check the target configuration in the MFT console and verify the Web Service URL. Try connecting to the configured endpoint by typing the URL in a web browser.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05420: MFT webservice Transport has encountered error parsing Inline XML payload for webservice endpoint {0}.

Cause: Error in parsing Inline XML payload. This could be because the Inline payload does not contain a valid XML format.

Action: Review the SOAP target configured in the MFT console to verify the payload type and MessageType. Also check the inline payload to validate the XML format.
Level: High

Type: ERROR

Impact: Message

MFT-05421: MFT webservice Transport has encountered error processing the payload stream.

Cause: Error in reading the inlne payload stream. This could be because the the payload stream may is Null or contains invalid data

Action: Review the SOAP target configured in the MFT console to verify the payload type and MessageType. Also check the payload received from MFT Source contains valid data.
Level: High

Type: ERROR

Impact: Message

MFT-05422: Error in processing EventService request. SourceName input parameter {0} is invalid.

Cause: Error in processing the EventService request. The provided Source name is invalid or does not exists.

Action: Submit the Event Request with valid Source Name.
Level: High

Type: ERROR

Impact: Message

MFT-05423: Error in processing EventService request. The Source {0} either doesn''t exists or not deployed.

Cause: Error in processing the EventService request. The provided Source does not exists or is not deployed.

Action: Submit the Event Request with valid Source Name or after deploying the intended Source.
Level: High

Type: ERROR

Impact: Message

MFT-05424: Error in processing EventService request. The Source {0} is not active.

Cause: Error in processing the EventService request. The provided Source is disabled.

Action: Submit the Event Request after enabling the intended Source.
Level: High

Type: ERROR

Impact: Message

MFT-05425: Error in processing EventService request. Unable to fetch the metadata for Source {0}.

Cause: Error in processing the EventService request. Error while fetching the metadata for the Source.

Action: Contact your Oracle Administrator.
Level: High

Type: ERROR

Impact: Message

MFT-05426: Error in processing EventService request. Event is not supported for Source {0}, which is of type {1}.

Cause: Error in processing the EventService request. The Source does not accept the event request, Event mechanism is not supported for these types of Sources.

Action: Submit the Event Request with Sources for which events are supported, ex. File, FTP, SFTP.
Level: High

Type: ERROR

Impact: Message

MFT-05427: Error in processing EventService request. Event is not enabled for Source {0}.

Cause: Error in processing the EventService request. The Event option is not enabled at the Source.

Action: Submit the Event Request after enabling the event option in the Source.
Level: High

Type: ERROR

Impact: Message

MFT-05428: Error in processing EventService request. User {0} is not authorized to invoke the Event on Source {1}.

Cause: Error in processing the EventService request. The User does not have the requisite permission to invoke the event on Source.

Action: Submit the request with user having the necessary permissions.
Level: High

Type: ERROR

Impact: Message

MFT-05429: Error in processing EventService request. There is an Event with session id {0} already active on Source {1}.

Cause: Error in processing the EventService request. Previous Event submitted for the source is still in progress.

Action: Submit the request once the previous event request is completed.
Level: High

Type: ERROR

Impact: Message

MFT-05430: Error in processing EventService request. Polling is active on Source {0}.

Cause: Error in processing the EventService request. Source is already started in polling mode.

Action: Submit the request once the polling is stopped.
Level: High

Type: ERROR

Impact: Message

MFT-05431: Error in processing EventService request. Error in validating the Event Request.

Cause: Error in processing the EventService request. Exception while validating the request.

Action: Submit the request again. Contact your Oracle Administrator if the problem persists.
Level: High

Type: ERROR

Impact: Message

MFT-05432: Error in processing EventService request. Required input parameter {0} is missing.

Cause: Error in processing the EventService request. The parameter required for processing the event request for source is missing.

Action: Submit the request with required parameter.
Level: High

Type: ERROR

Impact: Message

MFT-05433: Error in processing EventService request.

Cause: Exception in processing the EventService request.

Action: Contact your Oracle Administrator.
Level: High

Type: ERROR

Impact: Message

MFT-05434: Error in processing EventService request. Invalid User, unable to get the user details from request.

Cause: Exception in processing the EventService request. User Subject is null in the request.

Action: Contact your Oracle Administrator.
Level: High

Type: ERROR

Impact: Message

MFT-05435: Error in processing EventService request. Invalid Event Session Id {0}.

Cause: Exception in processing the EventService request. Provided Event Session Id is invalid.

Action: Resubmit the request with valid Event Session Id.
Level: High

Type: ERROR

Impact: Message

MFT-05436: Error in processing EventService request. No Event found with provided Event Session Id {0}.

Cause: Exception in processing the EventService request. No Event found with provided Event Session Id.

Action: Resubmit the request with valid Event Session Id.
Level: High

Type: ERROR

Impact: Message

MFT-05437: Error in processing EventService request. Persistence error while getting the Event/Instance details.

Cause: Exception in processing the EventService request. Error in Persistence layer.

Action: Contact your Oracle Administrator.
Level: High

Type: ERROR

Impact: Message

MFT-05438: Error in processing EventService request. SOAP error while creating the response.

Cause: Exception in processing the EventService request. Error in creating the response.

Action: Contact your Oracle Administrator.
Level: High

Type: ERROR

Impact: Message

MFT-05439: Parameter {0} configured with value {1} at ODIInvoke processing action is invalid.

Cause: The Parameter(s) configured at the ODIInvoke processing function is not valid.

Action: Correct the parameter configured as per the standard expected for Webservices.
Level: High

Type: ERROR

Impact: Message

MFT-05440: Error while getting the {1} type of Operation {0}.

Cause: An error occurred while parsing the request/response/fault types of an Operation.

Action: Verify whether the valid Operation is configured. Contact Oracle Support if the problem persists.
Level: High

Type: ERROR

Impact: Message

MFT-05441: Exception while processing the ODIInvoke Processing function. {0}

Cause: An error occurred while processing the ODIInvoke processing function.

Action: Verify whether the valid parameters are configured at the ODIInvoke processing function. Contact Oracle Support if the problem persists.
Level: High

Type: ERROR

Impact: Message

MFT-05442: Invalid Export type {0}.

Cause: Export type is not the supported one.

Action: Send the request again after changing the export type.
Level: High

Type: ERROR

Impact: Message

MFT-05443: Invalid {0} file.

Cause: The archive file uploaded is invalid.

Action: Send the request again after selecting the valid archive file.
Level: High

Type: ERROR

Impact: Message

MFT-05444: Invalid RESTful resource {0}.

Cause: The resource name provided in the url is invalid.

Action: Send the request again after changing resource name path parameter.
Level: High

Type: ERROR

Impact: Message

MFT-05445: Unable to list the resources catalog of MFT RESTful services.

Cause: An exception occured while listing the resources.

Action: Review diagnostic log for detailed error message.
Level: High

Type: ERROR

Impact: Message

MFT-05501: The {0} record {1} is already persisted.

Cause: The new record you are trying to persist is already available in the database.

Action: Check the details of the record you are trying to insert and try again.
Level: CRITICAL

Type: ERROR

Impact: MESSAGE

MFT-05502: No instance record found for message ID {0}.

Cause: There was no instance record found in the database.

Action: Check the ID of the entity.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05503: Error occurred while performing persistence operation.

Cause: Exception occurred while performing the persistence operation.

Action: Review diagnostic log for detailed error message.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05504: Could not perform the persistence lock operation {0} for entity {1}.

Cause: Exception occurred while performing the persistence operation.

Action: The exception may have occurred while performing the corresponding database lock operation. Check the logs for the exception trace.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05505: Error while deleting Data Storage {0}.

Cause: Error occurred while deleting the Data Storage entity in the database.

Action: Make sure the Data Storage is not associated with any entity. Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05506: Error deleting Source Message for source {0}.

Cause: Error occurred while deleting the Source Message entity in the database.

Action: Make sure the source is not associated with any transfer. Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05507: Error deleting transfer instance for transfer {0}.

Cause: Error occurred while deleting the transfer instance entity in the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05508: Error deleting Target Message {0}.

Cause: Error occurred while deleting the Target Message entity in the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05509: No retry info record exists in database.

Cause: Retry information not found for target.

Action: Resubmit the message again.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05510: No source lifecycle record exists for source name {0} and label {1} in database.

Cause: No record found.

Action: Redeploy the source and resubmit the message.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05511: No source record found for message ID {0}.

Cause: There was no source record found in the database.

Action: Check the ID of the entity.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05512: No transfer instance record found for message ID {0}.

Cause: There was no transfer instance record found in the database.

Action: Check the ID of the entity.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05513: No target message record found for ID {0}.

Cause: There was no transfer message record found in the database.

Action: Check the ID of the entity.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05514: Source {0} is not deployed.

Cause: Source is not deployed.

Action: Deploy the source and retry.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05515: Transfer {0} is not deployed.

Cause: Transfer is not deployed.

Action: Deploy the transfer and retry.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05516: Target {0} is not deployed.

Cause: Target is not deployed.

Action: Deploy the target and retry.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05517: Error deleting source {0}.

Cause: Error occurred while deleting the source in the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05518: Error deleting transfer {0}.

Cause: Error occurred while deleting the transfer in the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05519: Error deleting target {0}.

Cause: Error occurred while deleting the target in the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05520: Error fetching sources with label {0}.

Cause: Error occurred while fetching sources with this label from the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05521: Error fetching transfers with label {0}.

Cause: Error occurred while fetching transfers with this label from the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05522: Error fetching targets with label {0}.

Cause: Error occurred while fetching targets with this label from the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05523: Batch id [{0}] provided by user for purge recovery does not exist.

Cause: Batch id [{0}] provided by user for purge recovery does not exist.

Action: Check the passed batch id and try again. You can start a new purge also by passing the batch id as blank. Contact Oracle Support if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05524: Batch id [{0}] provided by user, for filesystem purge, does not exist.

Cause: Batch id [{0}] provided by user, for filesystem purge, does not exist.

Action: Check the passed batch id and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05525: Filesystem purge is already run successfully for the provided batch id [{0}].

Cause: Filesystem purge is already run successfully for the provided batch id [{0}].

Action: Check the passed batch id and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05526: Filesystem purge can not be run without a valid Root Directory configured.

Cause: No Root directory configured in the Application Settings.

Action: Check the Root Directory under Hosted Server properties. Contact Oracle Support if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05527: Runtime Purge is not yet executed for the batch id [{0}]. FS Purge can not be run without first running the Runtime Purge.

Cause: Runtime Purge is not yet executed for the batch id. FS Purge can not be run without first running the Runtime Purge.

Action: Check the Root Directory under Hosted Server properties. Contact Oracle Support if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05528: Filesystem archive is already run successfully for the provided batch id [{0}].

Cause: Filesystem archive is already run successfully for the provided batch id [{0}].

Action: Check the passed batch id and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05529: Batch id [{0}] provided by user, for filesystem archive, does not exist.

Cause: Batch id [{0}] provided by user, for filesystem archive, does not exist.

Action: Check the passed batch id and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05530: Filesystem archive can not be run without a valid Root Directory configured.

Cause: No Root directory configured in the Application Settings.

Action: Check the Root Directory under Hosted Server properties. Contact Oracle Support if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05531: Error while creating the archive file {0}. Error Message: {1}

Cause: Error while creating the archive file.

Action: Check the Root Directory under Hosted Server properties. Contact Oracle Support if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05532: Filesystem Archive operation started for the provided batch id [{0}] but not complete. Filesystem purge can not continue.

Cause: Filesystem Archive operation started for the provided batch id but not complete. Filesystem purge can not continue.

Action: Check the passed batch id and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05533: Error while adding payload {0} to the archive file. Error Message: {1}

Cause: Filesystem error while adding payload file to the archive.

Action: Check the payload file path, permissions and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05534: Error while working with archive file {0}. Error Message: {1}

Cause: Filesystem error while working with archive file.

Action: Check the archive file path, permissions and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05535: Error while working with archive file {0} for restore. Error Message: {1}

Cause: Filesystem error while working with archive file.

Action: Check the archive file path, permissions and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05536: No Schedule Purge record found for schedule name [{0}].

Cause: There was no Schedule Purge record found in the database.

Action: Check the Name of the Schedule Purge. Please review the diagnostic logs for specified schedule purge
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05537: Error occurred while performing persistence operation.

Cause: Exception occurred while performing the persistence operation.

Action: Review diagnostic log for detailed error message.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05802: Exception occurred while querying for ESS job definition [{0}].

Cause: Unexpected exception occurred while querying for the ESS job definition [{0}].

Action: Ensure that the MFT Custom Hosting App is properly deployed. For further details, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05803: NOT_IN_USE

Cause: NOT_IN_USE

Action: NOT_IN_USE
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05804: NOT_IN_USE

Cause: NOT_IN_USE

Action: NOT_IN_USE
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05805: NOT_IN_USE

Cause: NOT_IN_USE

Action: NOT_IN_USE
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05806: Exception occurred while looking up JNDI context.

Cause: Unexpected exception occurred while looking up the JNDI context.

Action: Check the JNDI configuration for ESS on your application server.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05807: Exception occurred while looking up EJB [{0}].

Cause: Could not look up ESS EJB [{0}].

Action: Ensure that the MFT custom hosting app (MFTCustomHostingApp) is installed properly.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05808: Unexpected error occurred while submitting an ESS job with details: job type [{0}], schedule name [{1}], job description [{2}], schedule time [{3}].

Cause: Unexpected error occurred while submitting an ESS job.

Action: Check the schedule details and deploy again. Also verify that ESS environment is up and running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05809: {0}

Cause: Validation failed for schedule.

Action: Check your schedule details. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05810: Exception occurred while looking for schedule with name [{0}].

Cause: Unexpected exception occurred while looking for schedule with name [{0}].

Action: Ensure that the schedule is attached to the artifact and try deploy again. For further details, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05811: Could not find schedule with name [{0}].

Cause: Could not find a schedule with name [{0}].

Action: Ensure that the schedule is attached with artifact and try deploy again. For further details, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05812: Exception occurred while opening ESS runtime service. Event: [{0}].

Cause: Could not open ESS runtime service.

Action: Check that ESS environment is up and running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05813: Exception occurred while opening ESS metadata service. Event: [{0}].

Cause: Could not open ESS metadata service

Action: Check that ESS environment is up and running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05814: Exception occurred while closing ESS runtime service. Event: [{0}].

Cause: Could not close ESS runtime service.

Action: Check that ESS environment is up and running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05815: Exception occurred while closing ESS runtime service. Event: [{0}].

Cause: Could not close ESS metadata service.

Action: Check that ESS environment is up and running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05816: Could not find ESS job with id [{0}] while cancelling.

Cause: Could not find the ESS job while cancelling.

Action: Ignore this exception. A new job has been submitted as part of a new deployment.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05817: Exception occurred while cancelling the ESS job with ID [{0}].

Cause: Illegal Job State Found. Cannot be cancelled.

Action: Try again or contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05818: Could not find ESS job request with ID [{0}]. Event [{0}].

Cause: Could not find ESS job request with id [{0}].

Action: Check that the artifact is deployed and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05819: Unexpected error occurred for job request ID [{0}]. Event [{1}].

Cause: Unexpected error occurred for job request ID [{0}].

Action: Check that the artifact is deployed and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05820: NOT_IN_USE

Cause: NOT_IN_USE

Action: NOT_IN_USE
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05821: Exception occurred while looking up EJB [{0}].

Cause: Could not look up ESS EJB [{0}].

Action: Ensure that the MFT custom hosting app (MFTCustomHostingApp) is installed properly. For further details, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05822: Error occurred for schedule name [{1}]. Event: [{0}].

Cause: Error occurred for schedule name [{1}]. Event: [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05823: Validation failed for schedule name [{1}]. Event [{0}].

Cause: Validation failed for schedule name [{1}]. Event: [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05824: Schedule already exists with name [{1}]. Event: [{0}].

Cause: Schedule already exists with name [{1}]. Event: [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05825: Null schedule passed for event [{0}].

Cause: Null schedule passed for event [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05826: ID in schedule found null for event [{0}].

Cause: ID in schedule found null for event [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05827: Exception occurred for schedule [{1}]. Event: [{0}].

Cause: Unexpected exception occurred for schedule.

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05828: Validation failed for schedule [{1}]. Event: [{0}].

Cause: Validation failed for schedule [{1}]. Event: [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05829: Schedule object found null for event [{0}].

Cause: Schedule object found null.

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05830: Passed schedule name is null for event [{0}].

Cause: Passed schedule name is null.

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05831: No schedule found with given name [{0}].

Cause: No schedule found with given name.

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05832: Unexpected error occurred while querying for schedule with name [{0}].

Cause: Unexpected error occurred while querying for schedule.

Action: Check the schedule details and try again. Also verify that ESS environment is up and running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05833: Schedule name passed as NULL while deleting schedule.

Cause: Schedule name passed as NULL while deleting schedule.

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05834: Unexpected error occurred while deleting schedule with name [{0}].

Cause: Unexpected error occurred while deleting schedule.

Action: Check the schedule details and try again. Also verify that ESS environment is up and running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05835: Trying to deactivate a non-active Schedule Purge [{0}].

Cause: Trying to access a non-active schedule purge.

Action: Scheduled purge is not active, Please active it first.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05836: Error occurred while deleting an active schedule purge [{0}] with ESS Job ID[{1}]..

Cause: Trying to delete an active schedule purge.

Action: An active schedule purge can't be deleted. Deactivate it and then try to delete it.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05837: Trying to activate an active Schedule Purge [{0}].

Cause: Trying to activate an active Schedule Purge [{0}].

Action: Scheduled purge is active, Please deactive it first.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05838: Trying to modify an active Schedule Purge [{0}].

Cause: Trying to modify an active Schedule Purge [{0}].

Action: An active schedule purge can't be modified. Deactivate it and then try to modify it.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05839: Error occurred while creating ESS schedule for purge schedule [{0}].

Cause: Error occurred while creating ESS schedule for purge schedule [{0}].

Action: Check the purge schedule details and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05840: Error occurred while updating ESS schedule[{1}] for purge schedule [{0}].

Cause: Error occurred while updating ESS schedule[{1}] for purge schedule [{0}].

Action: Check the purge schedule details and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05841: Could not find job definition with name [{0}].

Cause: Could not find job definition with name [{0}].

Action: Ensure that the MFT Custom Hosting App is deployed. For further details, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05842: Exception occurred while checking if schedule with name [{0}] is in use.

Cause: Unexpected exception occurred while checking if schedule with name [{0}] is in use.

Action: Check the database connection.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05843: Could not find ESS job with id [{0}] while doing operation {1}.

Cause: Could not find the ESS job while doing a specified operation.

Action: Ignore this exception. Job has been cancelled already as part of deployment cleanup.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05844: Exception occurred while doing the operation {1} with ESS job ID [{0}].

Cause: Illegal Job State Found. Cannot do the specified operation.

Action: Try again or contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05845: Operation {1} with ESS job ID [{0}] is not allowed.

Cause: Specified operation is not allowed on the given job.

Action: Try again or contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05846: {0}

Cause: Exception occurred while interacting with ESS

Action: Check your ESS environment and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05847: {0}

Cause: Exception occurred while invoking the ESS through security interceptor.

Action: Check your ESS environment and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06001: Error while initializing security for stripe {0}.

Cause: An error occurred while defining the required policy for the application stripe.

Action: Check whether the application has all the required permissions in the EM and policy store connection properties. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06002: An error occurred while performing the security operation.

Cause: An error occurred while executing the security operation on the specified application stripe.

Action: Check the security store configuration in the WebLogic console or jps-config.xml and default permissions of MFT in the policy store. Review the diagnostic log for the exact error.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06003: Error while initializing the identity store for default realm.

Cause: An error occurred while initializing identity store with default security realm.

Action: Check the security store configuration in the WebLogic console or jps-config.xml and default permissions of MFT in the policy store. Review the diagnostic log for the exact error.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06005: Illegal MFTESPermission resource name {0}.

Cause: The resource name is not in the expected MFT ES Permission format.

Action: Correct the resource name parameter using the format 'resourceName={ResourceName},includeSubfolders=true|false,,serverType=FTP|SFTP'.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-06006: Error while performing the SSH Key store operations on key type:{0} and alias {1}.

Cause: An error occurred while getting the SSH key store keys or aliases from the specified location.

Action: Check the key store location in the metadata repository and ensure that the required keys are present in the specified location. Review the diagnostic log for the exact error, and Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-06007: Secured Method {0} is not annotated with required parameters.

Cause: An error occurred while checking the access provisioning before executing the method.

Action: Annotate the method with the required parameters.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-06008: Error while performing the credential operation {0} for alias {1}.

Cause: An error occurred while performing the credential operation.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-06009: Error while performing the key store operation {0}.

Cause: An error occurred while performing the key store operation.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-06010: An error occurred while performing the security operation on stripe {0}, store {1} and alias {2}.

Cause: An error occurred while executing the security operation on the specified application stripe.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06011: Invalid key file location [{0}]. The given path does not exist.

Cause: The given key file location does not exist or the key file is an empty file.

Action: Provide the correct path for export and while importing make sure that valid non empty key file exists at the given path.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06012: The imported key file {0} has multiple key rings. Importing multiple key rings is not supported.

Cause: The key file being imported has more than one PGP key.

Action: Import a valid key file that has only one key ring.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06013: Unable to get the resource type {0} while granting the permission for resource {1}.

Cause: Internal resource type definition might have failed, there is no associated resource type defined in the policy store.

Action: Resource type should be predefined before granting the permission by the security layer. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06014: Unable to get the Principal of user/group {0} with type {1}.

Cause: The principal type specified for permission grant is invalid.

Action: Grant the permission with the valid principal type which can be a User or Group or Application Role.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06015: Error while granting the permission {2} to resource {0} for principal(s){1}.

Cause: An exception occurred while granting the permission for a resource.

Action: Check the parameters used for granting the permission. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06016: Error while getting principals and actions of resource {0} with type {1}.

Cause: An exception occurred while getting the principals and actions of a resource.

Action: Check the resource name for validity. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06017: Error while revoking the permission {2} of a resource{0} for principal(s){1}.

Cause: An exception occurred while deleting the permissions of a resource.

Action: Check the revoke parameters. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06018: Authorization failure for principal(s) {0} to resource {1} for action {2}.

Cause: Access control exception occurred for a user while doing an operation.

Action: If this error encountered even if the operation was allowed for the user, then check the permissions of the user. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06019: Unable to create the MFT OPSS resource type {0}.

Cause: An error occurred while defining the resource type.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06020: Unable to create the Principal object for principal name {0} and type {1}.

Cause: An error occurred while creating the principal object.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06021: Unable to get the members of the role {0}.

Cause: An error occurred while fetching the members of a role.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06022: Error while fetching all the application roles of application stripe {0}.

Cause: An error occurred while fetching the all the application roles.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06023: Error while fetching all the application roles of principal {0} with type {1}.

Cause: An error occurred while fetching the all the application roles of a principal.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06024: Error while fetching the granted resources of a principal {0}.

Cause: An error occurred while fetching the resources of a principal.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06025: Error while deleting all the grants of a resource {0} with type {1}.

Cause: An error occurred while deleting all the grants of a resource.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06026: Error while creating an application role with name {0}.

Cause: An error occurred while creating an application role.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06027: Error while deleting the application role with name {0}.

Cause: An error occurred while deleting an application role.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06028: Error while adding the member(s) {0} to application role {1}.

Cause: An error occurred while adding members to an application role.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06029: Error while removing the member(s) {0} from application role {1}.

Cause: An error occurred while removing members of an application role.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06030: Unable to authenticate the user {0}.

Cause: An error occurred while authenticating the user.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06031: Unable to get the enterprise groups of the user {0}.

Cause: An error occurred while getting the enterprise groups of the user.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06032: Error while retrieving the list of users/groups from identity store with criteria {0}.

Cause: An error occurred while fetching the users from identity store with search criteria.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06033: Invalid value [{0}] for parameter [{1}].

Cause: Parameter value supplied is incorrect.

Action: Provide the expected parameter value.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06034: The imported key file is not having valid encryption/decryption key.

Cause: The key file being imported has no valid PGP key.

Action: Import a key file that has a valid PGP key.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06035: A key already exists for the given key alias {0} in credential store.

Cause: A key is already created for the given key alias in the credential store.

Action: Import the key file again with a different key alias.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06036: Key not found for the given key alias {0} in credential store.

Cause: No key was found for the given key alias in the credential store.

Action: Check if a key for the given key alias has been generated or not in the credential store.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06037: Invalid key file [{0}]. The given key file is an empty file.

Cause: The given key file location to export CSF Key does not exist.

Action: Provide the correct path for export and while importing make sure that valid non empty key file exists at the given path.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06038: Path {0} specified on MFT embedded server for the resource is invalid.

Cause: No directory exists on MFT Embedded server specified by given path.

Action: Check if path specified is a valid directory on MFT Embedded server. If directory does not exist correct the Path input to point to existing directory OR create a new directory with the given Path.
Level: MEDIUM

Type: ERROR

Impact: MESSAGE

MFT-06039: Error in configuring home directory {0} for user {1}.

Cause: Error in configuring user home directory due to error accessing metadata for User/Group.

Action: Review Metadata repository configuration for MFT Embedded Server users. Try running MFT metadata export command to see if metadata repository configured properly.
Level: MEDIUM

Type: ERROR

Impact: MESSAGE

MFT-06040: Invalid Embedded Server types specified in the input.

Cause: Server Types specified in the input does not belong to one/more of the types FTP,SFTP.

Action: Provide server types which contains one ore more values FTP,SFTP.
Level: MEDIUM

Type: ERROR

Impact: MESSAGE

MFT-06041: Invalid permissions set {0} provided.

Cause: The permissions set provided contains one or more values that are not from the supported set 'READ,WRITE,DELETE,LIST'.

Action: Provide permissions that contains one or more values from supported set 'READ,WRITE,DELETE,LIST'.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-06042: Error while registering the WSM Security Policies to endpoint {0}.

Cause: An exception occurred while registering the WSM policies with WSM Policy Manager.

Action: Check the endpoint policies and WSM Manager configuration.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-06043: Error while unregistering the WSM Security Policies of endpoint {0}.

Cause: An exception occurred while unregistering the WSM policies from WSM Policy Manager.

Action: Check the endpoint policies and WSM Manager configuration.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-06044: Error while deleting the WSM assembly file of endpoint {0}.

Cause: An exception occurred while deleting the WSM assembly file from the MDS repository.

Action: Check the MDS configuration and endpoint availability.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-06045: No user found by name [{0}].

Cause: No user found.

Action: Specify the valid user name and retry the action.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-06046: No user group found by name [{0}].

Cause: No user group found.

Action: Specify the valid user group name and retry the action.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-07001: Error while creating audit record for the event {0}.

Cause: Error while creating audit record for the event .

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07002: Error while initializing audit framework.

Cause: Error initializing audit framework.

Action: Check Audit configuration in EM console. Contact Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07003: Audit enabled method {0} is not annotated with the required parameters.

Cause: An error occurred during auditing after executing a method.

Action: Annotate the method with the required parameters.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-07201: Error while sending notification.

Cause: Error while sending notification.

Action: Check the notification settings. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07202: Error while sending email notification.

Cause: Error while sending email notification.

Action: Check the notification settings. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07203: Error while sending sms notification.

Cause: Error while sending sms notification.

Action: Check the notification settings. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07204: Email settings are not configured for user [{0}].

Cause: Email settings are not configured for user.

Action: Configure the email settings for user in the user store and retry the action.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-07205: SMS settings are not configured for user [{0}].

Cause: SMS settings are not configured for user.

Action: Configure the SMS settings for user in the user store and retry the action.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-07206: Delivery channel [{0}] is not supported for notification. Only SMS/Email delivery channel is only supported.

Cause: Delivery channel is not supported.

Action: Change the delivery channel to Email/SMS and retry the action.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-07207: Delivery channel information is required.

Cause: Delivery channel cannot be null.

Action: Specify delivery channel and retry the action.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-07208: Notification template file[{0}] doesn''t exists.

Cause: Template file not exists.

Action: Specify the correct template file location and retry the action.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07209: Invalid notification template [{0}], no notification message subject found.

Cause: No notification message subject found.

Action: Correct the template file to add the message subject and retry the action.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07210: Invalid notification template [{0}], no notification message body found.

Cause: No notification message body found.

Action: Correct the template file to add the message body and retry the action.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07401: Callout with name: {0} exists in the Metadata Store. Not creating a new one.

Cause: An existing callout with same name was found in the Metadata Store.

Action: Change the callout name and try again. Refer to the MFT utilities documentation to determine the arguments and their types for the given command.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07402: Exception while creating Callout.

Cause: EJBException thrown by utility while creating callout.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07403: Callout definition XML input file [{0}] not found.

Cause: Callout definition XML input file not found. The given file name or file path is incorrect.

Action: Provide provide a valid file path and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07404: Callout definition XML File validation failed. Correct the errors and rerun the utility.

Cause: Callout definition XML File validation failed. Correct the errors and rerun the utility.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07405: Invalid Notification event type: {0}.

Cause: Invalid notification event type.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07406: Contact Information not found. Type: {0} Value: {1}.

Cause: Contact not found. Add the contact to the system and rerun the utility.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07407: An Exception occurred while running MFT utility. {0}

Cause: An Exception occurred while running the MFT utility.

Action: Refer to the MFT utilities documentation to determine arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07408: Contact already exists. Type: {0} # Value: {1}.

Cause: A contact of the given type and value already exists in the system.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07409: Error while creating contact of type: {0} and value: {1}.

Cause: An error occurred while creating a new contact of the given type and value.

Action: Refer to the MFT utilities help to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07410: Error while deleting callout: {0}.

Cause: An error occurred while deleting the given callout.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07411: Error occurred while listing all the callouts in the system.

Cause: An error occurred while listing all the callouts in the system.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07412: Error while adding a contact to notification event. Event: {0} # Contact type: {1} # Value: {2}.

Cause: An error occurred while adding a contact to the notification event.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07413: Error while removing a contact from a notification event. Error Message: {0}.

Cause: An Error while removing a contact from a notification event.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07414: Error while deleting a contact from the system. Error Message: {0}.

Cause: An error occurred while deleting a contact from the system.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07415: Unsupported artifact type found. Artifact type: {0}.

Cause: Unsupported artifact type found. Supported values are SOURCE, TARGET and TRANSFER.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07416: Exception while getting the id for source artifact [{0}].

Cause: Exception occurred while getting the source id from metadata store for the given name.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07417: Cannot delete the contact. Given contact is associated with a notification event. Contact type: {0} :: Value: {1}.

Cause: Given contact is associated with a notification event. First remove the contact from the event and then try deleting the contact again.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07418: Error while listing contacts from the system. Contact type: {0}.

Cause: Error while listing the contacts of the given type. Try again.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07419: Callout with name: {0} not found in MDS. No changes done.

Cause: An existing callout with the given name was not found in the Metadata Store.

Action: Provide a different and correct callout name and try again. Refer to the MFT utilities documentation to determine the arguments and their types for the given command.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07420: Invalid value supplied for group name. Callout definition for {0} not changed.

Cause: Incorrect value provided for group name.

Action: Valid values for group name can contain any combination of comma-separated values of following: Source-pre,Source-post,Target-pre,Target-post. Refer to the MFT utilities documentation to determine the arguments and their types for the given command.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07421: Error while modifying callout {0}. Error Message: {1}.

Cause: An Error occurred while modifying the callout definition.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07422: Error while creating {0} keys. Error Message: {1}.

Cause: An Error occurred while creating sample keys.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07423: Exception while getting the id for target artifact [{0}].

Cause: Exception occurred while getting the target id from metadata store for the given name.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07424: Exception while getting the id for transfer artifact [{0}].

Cause: Exception occurred while getting the transfer id from metadata store for the given name.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07425: Exception while getting the name for transfer artifact id [{0}].

Cause: Exception occurred while getting the transfer id from metadata store for the given name.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07426: Exception while getting the name for target artifact id [{0}].

Cause: Exception occurred while getting the target id from metadata store for the given name.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07427: Exception while getting the name for source artifact id [{0}].

Cause: Exception occurred while getting the source id from metadata store for the given name.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07428: Error while retrieving deployment history for transfer [{0}].

Cause: Exception occurred while retrieving deployment history information for the given transfer.

Action: Check the transfer deployment details in UI. Deploy the transfer from UI or WLST and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07429: Error while retrieving deployment history for target [{0}].

Cause: Exception occurred while retrieving deployment history information for the given target.

Action: Check the target deployment details in UI. Deploy the target from UI or WLST and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07430: Error while retrieving deployment history for source [{0}].

Cause: Exception occurred while retrieving deployment history information for the given source.

Action: Check the source deployment details in UI. Deploy the source from UI or WLST and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07431: Error while retrieving deployment history for transfer [{0}].

Cause: Exception occurred while retrieving deployment history information for the transfer source.

Action: Check the transfer deployment details in UI. Deploy the transfer from UI or WLST and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07432: Exception occurred while checking if transfer [{0}] exists in metadata store.

Cause: Exception occurred while checking if the given transfer exists in metadata store.

Action: Restore the deleted transfer artifact in metadata store and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07433: Exception occurred while checking if target [{0}] exists in metadata store.

Cause: Exception occurred while checking if the given target exists in metadata store.

Action: Restore the deleted target artifact in metadata store and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07434: Exception occurred while checking if source [{0}] exists in metadata store.

Cause: Exception occurred while checking if the given source exists in metadata store.

Action: Restore the deleted source artifact in metadata store and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07435: Could not parse xml [{0}]

Cause: Exception occurred while parsing xml

Action: Check / Validate the xml against given xsd and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07436: File [{0}] doesn''t exist or is a directory.

Cause: File doesn't exist or is a directory

Action: Ensure that file exists and try again. File should exist on machine where server is running.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07437: Exception while creating mds session.

Cause: Could not create mds session

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07438: Exception while creating mds artifact.

Cause: Could not create mds artifact.

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07439: Exception while querying mds artifact id using artifact name [{0}]

Cause: Could not query mds artifact id.

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07440: Exception while fetching mds artifact using artifact id [{0}].

Cause: Could not fetch mds artifact by id.

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07441: Exception while saving mds artifact.

Cause: Could not save mds artifact.

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07442: Exception while fetching processing functions.

Cause: Could not fetch processing functions from mds

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07443: Parameter not found with name [{0}] for function [{1}].

Cause: Could not find parameter with name [{0}] for function [{1}]

Action: Check the parameter name and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07444: Function not found with name [{0}].

Cause: Could not find function with name [{0}]

Action: Check the function name and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07445: Domain not found with name [{0}].

Cause: Could not find domain with name [{0}]

Action: Check the domain name and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07446: Exception while fetching domain MO from domain name {0}.

Cause: Could not fetch domain info from mds

Action: Check the logs for the exception trace and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07447: Artifact with name [{0}] already exists.

Cause: Artifact with given name already exists.

Action: Try with a new name or pass updateIfExists as true.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07448: Could not parse date {0}.

Cause: Could not parse date.

Action: Correct the date format and try again. It should be 'MM/dd/yyyy H:m:s'
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07449: Could not parse given month of year {0} for schedule {1}.

Cause: Could not parse month of year given with schedule definition.

Action: Check the passed month of year and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07450: Could not parse given day of month {0} for schedule {1}.

Cause: Could not parse day of month given with schedule definition.

Action: Check the passed day of month and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07451: Could not parse given week of month {0} for schedule {1}.

Cause: Could not parse week of month given with schedule definition.

Action: Check the passed week of month and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07452: Could not parse given day of week {0} for schedule {1}.

Cause: Could not parse day of week given with schedule definition.

Action: Check the passed day of week and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07453: Could not initiate mds storage provider while attaching policy with artifact {0}.

Cause: Could not initiate mds storage provider.

Action: Check the mds settings and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07454: Error occurred while attaching OWSM policies for artifact {0}.

Cause: Error occurred while attaching OWSM policies.

Action: Check the policy details, ensure policy name is valid and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07455: Could not create empty assembly.

Cause: Could not create empty assembly.

Action: Review the diagnostic log for the exact error. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07456: Could not fetch domain from MDS store.

Cause: Could not fetch domain from MDS store.

Action: Check the mds settings and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07457: User is not authorize to create domain.

Cause: User is not authorize to create domain.

Action: Only Administrator can create the domain. Check the user permissions and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07458: Domain with name {0} not found.

Cause: Could not find domain with given name.

Action: Check the domain name and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07459: Error while deleting domain with name {0}.

Cause: Could not delete domain with given name.

Action: Review the diagnostic log for the exact error. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07460: Could not lookup EJB with name {0}.

Cause: Could not lookup EJB.

Action: Review the diagnostic log for the exact error. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07461: PGP encryption and decryption functions are not allowed in post processing.

Cause: PGP encryption and decryption functions are not allowed in post processing.

Action: Remove the PGP functions from post processing and try again. If required, these functions can be used as pre processing functions.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07462: Unsupported value {0} found for {1}.

Cause: Could not find given value.

Action: Check the documentation for supported values for [{1}] and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07463: Artifact not found for given name [{0}].

Cause: Could not find artifcat for given name.

Action: Check the artifact name and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07464: Callout [{0}] exists but not allowed for given artifact type.

Cause: Callout not allowed for given artifact.

Action: Check the artifact definition and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07465: Invalid processing function [{0}] found for post processing.

Cause: Processing function [{0}] is not allowed in post processing.

Action: Remove the function from post processing and try again. If required, these functions can be used as pre processing functions.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07466: Invalid action type found for source. Allowed action types are ''{1}'', ''{2}'' and ''{3}''. Value found: [{0}].

Cause: Invalid action type found for source.

Action: Check the action type and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07467: Invalid action type found for target. Allowed action types are ''{1}'', ''{2}'' and ''{3}''. Value found: [{0}].

Cause: Invalid action type found for target.

Action: Check the action type and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07468: One of property ['Physical Target Directory' / 'Moved To Folder' / 'File Naming Convention'] found null.

Cause: Required property found null.

Action: Check the properties and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07469: Creating external contacts isn't allowed.

Cause: Creating external contacts is disabled.

Action: Creating external contacts is disabled so create internal user/group contact instead otherwise contact your administrator.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07470: Contact[{1}] is already associated with event[{0}].

Cause: Contact is already associated with the notification event.

Action: Check the contact details.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07471: Polling/Event options are not enabled for the source {0}.

Cause: Either One of Polling/Event options should be enabled.

Action: Enable one of the option and try again.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07472: Schedule definition is missing for source {0}.

Cause: Polling along with Event can be enabled only when schedule(s) are defined.

Action: Add schedule and try again.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-07473: Unsupported action[{0}].

Cause: Unsupported action for schedule purge found. Supported values are ACTIVATE and DEACTIVATE.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07474: Could not parse given date[{0}] in format[{1}].

Cause: Provided date in not in valid format.

Action: Check the input date and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07475: Could not parse given time[{0}] in format[{1}].

Cause: Provided time is not in valid format.

Action: Check the input time and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07476: Invalid Target artifact {0}. Only one among Append/Overwrite/CreateOnly attributes can be true.

Cause: Provided target artifact is not in valid format.

Action: Correct the target attributes and try again. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-08001: Error while reading metadata archive {0}. Error Message: {1}

Cause: An Error occurred while reading the metadata archive file.

Action: Refer to the plugin logs for more details.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-08002: Error while closing metadata archive {0}. Error Message: {1}

Cause: An Error occurred while closing the metadata archive file.

Action: Refer to the plugin logs for more details.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-08003: Error while processing metadata file {0}. Error Message: {1}

Cause: An Error occurred while either reading or parsing the metadata xml file.

Action: Refer to the plugin logs for more details.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-08500: Unsupported REST operation.

Cause: This REST operation is not supported.

Action: Check the input and try again. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

30 ODI-01100 to ODI-999999

ODI-01100: Agent {0} successfully cleaned up {1} stale sessions from work repository {2}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01101: Agent {0} successfully completed session {1} ({2}) (for scenario {3}) on {4} using context {5} with statistics: Rows {6} Inserts {7} Updates {8} Deletes {9} Errors {10}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01102: Agent {0} successfully completed session {1} ({2}) on {3} using context {4} with statistics: Rows {5} Inserts {6} Updates {7} Deletes {8} Errors {9}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01103: Agent {0} successfully completed step {1} in session {2}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01104: Agent {0} successfully connected to master repository using {1}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01105: Agent {0} successfully connected to work repository {1} using {2}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01106: Agent {0} created load plan {1}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01107: Agent {0} created session {1} ({2}) in work repository {3}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01108: Agent {0} created session {1} ({2}) from scenario {3} in work repository {4} using context {5}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01109: Agent {0} is delegating session {1} on work repository {2} to agent {3}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01110: Agent {0} successfully retrieved {1} schedules from work repository {2} using {3}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01111: Agent {0} started. Agent version: {1}. Port: {2}. JMX Port: {3}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01112: Agent {0} received a request to recalculate its schedule on work repository {1}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01113: Agent {0} received a data server test request for {1}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01114: Agent {0} received a request to stop load plan instance {1} on work repository {2}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01115: Agent {0} received a ping request.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01116: Agent {0} received a request to retrieve its schedule on work repository {1}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01117: Agent {0} received a request to restart load plan instance ({1}) in work repository {2}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01118: Agent {0} received a request to start load plan {1} on work repository {2} using context {3}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01119: Agent {0} received a request to start scenario {1}.{2} on work repository {3} using context {4}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01120: Agent {0} received a request to restart session {1} on work repository {2} using context {3}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01121: Agent {0} received a request to stop session {1} on work repository {2}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01122: Agent {0} successfully restarted {1} queued sessions from work repository {2} using {3}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01123: Agent {0} sent a request to agent {1}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01124: Agent {0} started load plan {1}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01125: Agent {0} started session {1} ({2}) from scenario {3} in work repository {4} using context {5}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01126: Agent {0} started session {1} ({2}) in work repository {3} using context {4}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01127: Agent {0} started step {1} in session {2}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01128: Agent {0} is starting. Container: {1}. Agent Version: {2}. Port: {3}. JMX Port: {4}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01129: Agent {0} stopped.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01130: Agent {0} is stopping.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01131: Agent {0} encountered an error: {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01132: Agent {0} encountered a warning: {1}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01133: Agent {0} detected that the work repository {1} went down.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01134: Agent {0} encountered an error: {1}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01135: Agent {0} detected that the master repository went down.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01136: Starting Schedulers on Agent {0}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01137: Scheduler started for work repository {0} on Agent {1}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01138: Migrating Schedulers for Agent {0}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01139: The current task of the session ({0}) does not support stop immediate. This session will be stopped normally by the Agent ({1}) before next task begins.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01140: Unable to stop session ({0}) immediately. This session will be stopped by the agent ({1}) before next task begins.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01141: Agent {0} started load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01142: Agent {0} successfully completed load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01143: Agent {0} started computing next steps from step {5} of load plan instance {1} ({2}), run {3} in work repository {4}. Triggering session={6}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01144: Agent {0} completed computing next steps from step {5} of load plan instance {1} ({2}), run {3} in work repository {4}. Triggering session={6}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01145: Agent {0} not found when trying to stop session with id {1} in work repository {2}.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01146: Agent {0} invocation error when trying to stop session with id {1} in work repository {2}: {3}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01147: Agent {0} stopped load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01148: Agent {0} executing load plan log purge for work repository {1} at {2}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01151: Agent {0} cannot continue load plan instance {1} ({2}), run {3} in work repository {4}, because the instance has been deleted.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01152: Agent {0} continuing processing for load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01153: An exception occurred while processing scheduled job for scenario {0} and version {1}. The exception message is : {2}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01154: An exception occurred while processing scheduled job for loadplan {0}. The exception message is : {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01155: Invalid repetition interval {0} specified in scheduled job for scenario {1} {2}. The schedule would not be repeated.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01156: Invalid repetition interval {0} specified in scheduled job for loadplan {1}. The schedule would not be repeated.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01157: Coherence cluster property {0} is not found in the system properties for Agent {1}. Agent may connect to an unintended coherence cluster.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01158: Agent {0} started invoking load plan exception handler {5} for failed step {6} of load plan instance {1} ({2}), run {3} in work repository {4}. Caused by: step {6}: {7}

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01159: Agent {0} completed load plan exception handler {5} for failed step {6} of load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01160: Agent {0} started processing load plan step {5} of load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01161: Agent {0} completed load plan step {5} (status={6}) of load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01162: Scheduled task failed with id {0} of work repository {1} on Agent {2}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01163: The load plan logs purge operation failed on Agent {0}: {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01165: Client requires a repository with version {0} but the repository version found is {1}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01166: Connection to Enterprise Scheduler {0} succeeded with url={1}, factory={2}, JNDI Name={3}, user={4}

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01167: Connection to Enterprise Scheduler {0} failed with url={1}, factory={2}, JNDI Name={3}, user={4}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01200: Session start failure: the request is incorrectly formed.

Cause: A malformed request was sent to the agent.

Action: Verify the request format and parameters sent to the agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01201: Session start failure on agent {0}: JDBC connection error occurs while connecting to the master repository.

Cause: An incorrect connection was used for the master repository database, or repository database was down.

Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01202: Session start failure on agent {0}: data source for master repository does not contain a master repository.

Cause: The master repository connection information pointed to a database schema that did not contain a master repository.

Action: Verify the master repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01203: Session start failure on agent {0}: the master repository is in an invalid state.

Cause: The master repository was in a state that did not allow connections. This is the case if an upgrade was being performed.

Action: Verify the state of the master repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01204: Session start failure on agent {0}: the master repository version {1} is not compatible with the agent version {2}.

Cause: The master repository was upgraded but not this agent, or the agent was upgraded but not the master repository.

Action: Upgrade the master repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01205: Session start failure on agent {0}: an authentication error occurred while connecting to the master repository.

Cause: An incorrect ODI user or password was specified for this master repository.

Action: Verify the ODI user and password used for connecting.
Level: 1

Type: ERROR

Impact: Other

ODI-01206: Session start failure on agent {0}: the agent is not defined in the topology for master repository.

Cause: The session was not found in the master repository.

Action: Verify that a session with this ID exists in the repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01207: Session start failure on agent {0}: JDBC connection error occurs while connecting to the work repository {1}.

Cause: An incorrect connection was used for the work repository database, or repository database was down.

Action: Verify the work repository connection information and the status of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01208: Session start failure on agent {0}: database schema {1} does not contain a work repository.

Cause: The work repository connection information pointed to a database schema that did not contain a work repository.

Action: Verify the work repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01209: Session start failure on agent {0}: work repository {1} is in an invalid state.

Cause: The work repository was in a state that did not allow connections. This is the case if an upgrade was being performed.

Action: Verify the state of the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01210: Session start failure on agent {0}: work repository {1} version {2} is not compatible with the agent version {3}.

Cause: The work repository was upgraded but not this agent, or the agent was upgraded but not the work repository.

Action: Upgrade the work repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01211: Session start failure on agent {0}: work repository {1} is not bound to the master repository.

Cause: The work repository specified in the request was not found in the list of work repositories attached to this master.

Action: Verify that work repository name matches an existing one.
Level: 1

Type: ERROR

Impact: Other

ODI-01212: Session preparation failure: scenario {0} does not exist in work repository {1}.

Cause: The session request was received, but the agent was unable to find the named scenario in the work repository.

Action: Verify that the scenario name matches an existing scenario name in the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01213: Session preparation failure: scenario {0} version {1} does not exist in work repository {2}.

Cause: The session request was received, and the scenario existed in the work repository, but not with the specified version.

Action: Ensure that the scenario version matches an existing scenario version in the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01214: Session preparation failure: context {0} does not exist in the master repository.

Cause: The session request was received, but the agent was unable to find the context in the master repository.

Action: Ensure that the context matches an existing context code in the Topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01215: Session preparation failure: privileges are insufficient to run scenario {0}.{1} in repository {2}.

Cause: User privileges were not sufficient for running this scenario in this repository.

Action: Ensure that the user has sufficient privileges for this task.
Level: 1

Type: ERROR

Impact: Other

ODI-01216: Session preparation failure: insufficient privileges to use Context {0} ({1}).

Cause: User privileges were not sufficient for using this context.

Action: Ensure that the user has sufficient privileges for this task.
Level: 1

Type: ERROR

Impact: Other

ODI-01217: Session {0} ({1}) fails with return code {2}.

Cause: The session finished in an error state.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01218: Session preparation failure: database error occurs while connecting to the master repository.

Cause: The agent received a database error from the master repository while creating the session.

Action: Verify the state of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01219: Session preparation failure: database error while connecting to work repository {0}.

Cause: The agent received a database error from the work repository while creating the session.

Action: Verify the state of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01220: Session preparation failure: an unexpected exception occurred.

Cause: The remote agent faced an unexpected error while attempting to create the session.

Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Other

ODI-01221: Unable to restart session {0}: session is not found in work repository {1}.

Cause: The session to restart did not exist in the repository. This session may have been deleted, or an incorrect session ID or work repository was supplied.

Action: Verify that a session with this ID exists in the repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01222: Session start failure on agent {0}: logical schema {1} cannot be found in the master repository.

Cause: The object to be executed referred to a logical schema not present in the master repository.

Action: Ensure that the logical schema configuration exists in your master repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01223: Database error while connecting to the master repository.

Cause: The connection for the master repository database was incorrect, or the repository database was down.

Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01224: Database error while connecting to work repository {0}

Cause: The connection for the work repository database was incorrect, or the repository database was down.

Action: Verify the work repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01225: An unexpected exception occurred.

Cause: The agent faced an unexpected exception.

Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Other

ODI-01226: Step {0} fails after {1} attempt(s).

Cause: This is an execution warning. The session step failed to execute after the maximum number of retries. If step failure was not handled in the package design, the session finished in an error state.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01227: Task {0} fails on the source connection {1}.

Cause: This is an execution warning. The command on the source for this task finished with an error.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01228: Task {0} fails on the target connection {1}.

Cause: This is an execution warning. The command on the target for this task finished with an error.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01229: An error occurred while performing a {0} operation on model code {1}.

Cause: This is an execution warning. The operation specified failed on the model.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01231: An error occurred while performing a {0} operation on datastore {1}.

Cause: This is an execution warning. The operation specified failed on the datastore.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01232: Procedure {0} execution fails.

Cause: This is an execution warning. The procedure execution failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01233: Error while evaluating variable the following expression: {0} {1} {2}

Cause: This is an execution warning. The variable evaluation failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01235: Error while incrementing variable {0} to value {1}

Cause: This is an execution warning. The variable increment failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01236: Error while refreshing variable {0}.

Cause: This is an execution warning. The variable refresh failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01237: Error while setting variable {0} to value {1}.

Cause: This is an execution warning. The set variable operation failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01238: Flow {0} fails because the maximum number of allowed errors ({1} rows) is exceeded during the flow check. This flow loads target table {2}.

Cause: This is an execution warning. The interface failed because the number of errors detected in the flow exceeded the value defined in the interface.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Review the erroneous records for this interface in the error table.
Level: 1

Type: WARNING

Impact: Other

ODI-01239: Flow {0} fails because the maximum percentage of allowed errors ({1} %) is exceeded during the flow check. This flow loads target table {2}.

Cause: This is an execution warning. The interface failed because the percentage of errors detected in the flow exceeded the value defined in the interface.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Review the erroneous records for this interface in the error table.
Level: 1

Type: WARNING

Impact: Other

ODI-01240: Flow {0} fails while performing a {1} operation. This flow loads target table {2}.

Cause: This is an execution warning. The interface failed because one of the statements returned an error return code.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01241: Oracle Data Integrator tool execution fails.

Cause: This is an execution warning. The tool execution failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01242: Operating system command execution fails.

Cause: This is an execution warning. Execution of the operating system command failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01243: Session {0} ({1}) fails because work repository {2} went down.

Cause: Work repository database went down while session was being executed.

Action: Verify the state of the work repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01244: Session {0} {1} was prepared successfully but fails because work repository {2} went down before execution could begin.

Cause: Work repository database went down while session was starting its execution.

Action: Verify the state of the work repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01245: Session preparation failure: work repository {0} went down during session preparation.

Cause: Work repository went down while session was being prepared.

Action: Verify the state of the work repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01246: The Logical Schema has not been set for {0}.

Cause: Because the logical schema had not been set, the object could not be executed.

Action: Verify the object that you are trying to execute, and set the logical schema for this object.
Level: 1

Type: ERROR

Impact: Other

ODI-01247: Session {0} {1} was prepared successfully but fails because master repository went down before execution could begin.

Cause: Master repository database went down while session was starting its execution.

Action: Verify the state of the master repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01248: Session preparation failure by Agent {0}: master repository went down during session preparation.

Cause: Master repository went down while session was being prepared.

Action: Verify the state of the master repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01249: Session {0} ({1}) fails because master repository went down.

Cause: Master repository database went down while session was being executed.

Action: Verify the state of the master repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01250: Session {0} ({1}) could not be stopped by Agent {2} because session {0} {1} already completed execution.

Cause: The session has already completed and cannot be stopped.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01251: Session ({0}) could not be stopped by Agent {1} because session ({0}) was not found in work repository {2}.

Cause: The session was not found in the work repository.

Action: Verify that a session with this ID exists in the repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01252: Session ({0}) could not be stopped by Agent {1}: insufficient privileges to access session.

Cause: User privileges were not sufficient for accessing this session in this agent.

Action: Ensure that the user has sufficient privileges for this task.
Level: 1

Type: ERROR

Impact: Other

ODI-01253: Session {0} ({1}) could not be stopped by Agent {2}: an unknown error occurred.

Cause: An unexpected Exception occurred.

Action: Verify your Agent configuration and make sure other operations on Agent are working correctly.
Level: 1

Type: ERROR

Impact: Other

ODI-01254: Session {0} ({1}) could not be stopped by Agent {2}: a JDBC error occurred on work repository {3}.

Cause: The agent had incorrect connection for the work repository database, or repository database was down.

Action: Verify the work repository connection information and the status of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01255: Session {0} ({1}) could not be stopped by Agent {2}: insufficient privileges to stop the session.

Cause: User privileges were not sufficient for stopping this session in this agent.

Action: Ensure that the user has sufficient privileges for this task.
Level: 1

Type: ERROR

Impact: Other

ODI-01256: Session {0} ({1}) stopped (Normal) by user {2}.

Cause: Session was stopped by the user.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01257: Session {0} ({1}) stopped (Immediate) by user {2}.

Cause: Session was stopped by the user.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01258: Session {0} ({1}) stopped (Abort) by user {2}.

Cause: Session was aborted by the user.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01259: Session Task {0} stopped (Normal) by user {1}.

Cause: Task was stopped by the user.

Action: Review the task execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01260: Session Task {0} stopped (Immediate) by user {1}.

Cause: Task was stopped by the user.

Action: Review the task execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01261: Session Task {0} stopped (Abort) by user {1}.

Cause: Task was aborted by the user.

Action: Review the task execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01262: Session {0} ({1}) could not be stopped by Agent {2}: a JDBC error occurred on master repository.

Cause: The agent had incorrect connection for the master repository database, or repository database was down.

Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01263: Step {0} stopped (Normal) by user {1}.

Cause: Step was stopped by the user.

Action: Review the step execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01264: Step {0} stopped (Immediate) by user {1}.

Cause: Step was stopped by the user.

Action: Review the step execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01265: Step {0} stopped (Abort) by user {1}.

Cause: Step was aborted by the user.

Action: Review the step execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01266: Agent {0} detected Session as stale session and set to error status.

Cause: The agent detected a stale session and the session status was set to error status.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01267: Session ({0}) could not be stopped by Agent {1} because stop type {2} provided in the request is an invalid stop type.

Cause: The agent attempted to stop a session with an invalid stop type.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01268: Agent {0} does not support stopping asynchronous child sessions.

Cause: The agent attempted to stop an asynchronous child session and this is not supported.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01269: Session {0} ({1}) could not be stopped by Agent {2}: session is being run by another Agent with the same name.

Cause: The agent attempted to stop a session that is being run by a different agent.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01270: Session {0} ({1}) could not be stopped by Agent {2}: session {0} ({1}) is being run by {3} Agent which is not a listener Agent.

Cause: The agent attempted to stop a session that is being run by the internal agent and this is not supported.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01271: The asynchronous jndi name cannot be null for asynchronous jobs. The ESS job status cannot be updated.

Cause: The agent attempted to set the status of the asynchronous ESS job and its jndi name was not set.

Action: Review the jndi name supplied to the Enterprise Scheduler job.
Level: 1

Type: WARNING

Impact: Other

ODI-01272: The Logical Schema has not been set on {0} for {1}.

Cause: The logical schema for this object has not been set.

Action: Verify that the logical schema has been set in the Topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01273: The selected technology {0} is not supported on source for {1}.

Cause: The selected technology is not supported for this object.

Action: Verify that the object has a valid technology.
Level: 1

Type: ERROR

Impact: Other

ODI-01274: Agent Exception

Cause: An error was detected by the agent when performing an operation.

Action: Review the underlying exception for more details.
Level: 1

Type: ERROR

Impact: Other

ODI-01275: An error occurred while performing a {0} operation on submodel step {1} of the model code {2}.

Cause: This is an execution warning. The operation specified failed on the submodel operation.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01276: An error occurred while executing the OnConnect command on JDBC connection created for data server {0} with transaction label {1}.

Cause: An error was occurred while executing the OnConnect command on the JDBC connection created to the data server.

Action: Review the underlying exception and update the OnConnect command definition configured for the data server.
Level: 1

Type: ERROR

Impact: Other

ODI-01277: An error occurred while executing the OnDisconnect command on JDBC connection created for data server {0} with transaction label {1}.

Cause: An error was occurred while executing the OnDisconnect command on the JDBC connection created to the data server.

Action: Review the underlying exception and update the OnDisconnect command definition configured for the data server.
Level: 1

Type: ERROR

Impact: Other

ODI-01278: Load plan instance {0}, run {1} does not exist in work repository {2}.

Cause: The Load Plan Instance run does not exist in the repository. This Load Plan Instance run may have been deleted, or an incorrect instance ID/run number or work repository was supplied.

Action: Verify that a load plan instance run with this instance ID and run number exists in the repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01279: The Source Logical Schema {0} and Context {1} of the task {2} are not mapped to any Physical Schema.

Cause: The Logical Schema to Physical Schema Mapping is not defined for the Context used.

Action: For the Context used define the Logical Schema to Physical Schema Mapping in the Topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01280: The Target Logical Schema {0} and Context {1} of the task {2} are not mapped to any Physical Schema.

Cause: The Logical Schema to Physical Schema Mapping is not defined for the Context used.

Action: For the Context used define the Logical Schema to Physical Schema Mapping in the Topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01281: Source Technology {0} of task {1} is not of JDBC Type. When both Source and Target commands are specified, the Source Technology should be of JDBC type.

Cause: When Source and Target commands are specified, the Source Technology should always be of JDBC type.

Action: Make Sure that you modify your Procedure or KM to either use a JDBC Source Technology or edit your step to use only the Target command.
Level: 1

Type: ERROR

Impact: Other

ODI-01282: Invalid log level {0} is specified. A valid log level value is between {1} and {2}.

Cause: Invalid log level specified for scenario/session invocation or for session restart.

Action: Please specify a valid log level.
Level: 1

Type: ERROR

Impact: Other

ODI-01283: Owb preparation failure: Owb object {0} of type {1} in location {2} does not exist in Owb repository {3}.

Cause: The session request was received, but the agent was unable to find the named Owb object in the Owb repository.

Action: Verify that the Owb object name matches an existing Owb object in the location in the Owb repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01284: Session {0} ({1}) with Owb audit Id {2} fails.

Cause: The session finished in an error state.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01285: Session {0} ({1}) Retreival of audit for auditId {2} failed in the {3} phase {4}. Please use OWB Design Client or Browser for further information.

Cause: An error was raised during the retreival of the Owb audit data.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1

Type: ERROR

Impact: Other

ODI-01286: Session {0} ({1}) could not find Owb job for this session.

Cause: The session being aborted is not an Owb Job.

Action: Review the session being aborted in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01287: Session {0} ({1}) with Owb audit Id {2} is in an invalid state to be aborted.

Cause: The session being aborted is not in a state that can be aborted.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1

Type: ERROR

Impact: Other

ODI-01288: Session {0} ({1}) with Owb audit Id {2} abort fails.

Cause: The session abort finished in an error state.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1

Type: ERROR

Impact: Other

ODI-01289: Agent {0} detected Session as stale session and set to error status. Please use OWB Design Client or Browser for further information.

Cause: The agent detected a stale OWB session and the session status was set to error status.

Action: Review the session execution details in the OWB Design Client or Browser.
Level: 1

Type: ERROR

Impact: Other

ODI-01290: Session {0} ({1}) Loading of audit for auditId {2} failed in the {3} phase {4}.

Cause: An error was raised during the loading of the Owb audit data.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1

Type: ERROR

Impact: Other

ODI-01291: Workspace {0} cannot be resolved to a physical workspace using context {1}.

Cause: The context does not contain a mapping for the logical workspace.

Action: Review the mappings defined in the context.
Level: 1

Type: ERROR

Impact: Other

ODI-01292: An execution context cannot be determined for this job.

Cause: An execution context cannot be determined for this job.

Action: Use the Context to provide an explicit context for this execution.
Level: 1

Type: ERROR

Impact: Other

ODI-01293: Exception occurred during spawning of ECID to child session.

Cause: Spawning of ECID from parent session to child session failed.

Action: Review the exception raised to get more detail.
Level: 1

Type: WARNING

Impact: Other

ODI-01294: Unwrapping of a wrapped ECID [{0}] failed.

Cause: Unwrapping of ECID failed.

Action: Review the exception raised and the format of wrapped ECID to get more detail on unwrap failure
Level: 1

Type: WARNING

Impact: Other

ODI-01295: Cleanup of Session {0} ({1}) raised the following {2} messages: {3}

Cause: Messages were raised during the Cleanup phase.

Action: Review the messages raised during the Cleanup and you may need to perform some manual cleanup.
Level: 1

Type: WARNING

Impact: Other

ODI-01296: The Cleanup Tool encountered the following {0} nested errors when executing the Cleanup tasks: {1}

Cause: Messages were raised during the Cleanup tool execution.

Action: Review the messages raised during the Cleanup and you may need to perform some manual cleanup.
Level: 1

Type: ERROR

Impact: Other

ODI-01297: Parallel task "{0}" failed; {1} child task(s) in error; Failed child tasks: {2}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01298: Serial task "{0}" failed because child task "{1}" is in error.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01299: A task "{0}" from one of the parallel branches has failed. Hence aborting the current branch

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01300: ASYNC_JNDI_NAME cannot be null for async job.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01301: Unable to submit Job Definition: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01302: Logical Agent {0} must be mapped to a Physical Agent in the ContextCode {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01303: RuntimeSessionfactory must not be null.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01304: Unable to find request for ID {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01305: jobDefinitionId must not be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01306: scheduleDefinitionId must not be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01307: ContextCode is null, cannot lookup physical agent

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01308: SchedulingService object was created without an EntityManager, cannot lookup physical agent

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01309: Unable to find logical agent : {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01310: Unable to find context : {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01311: JobDefinition with name {0} already exists.

Cause: JobDefinition already exists.

Action: Check JobDefinition name.
Level: 32

Type: ERROR

Impact: Other

ODI-01312: Schedule with name {0} already exists.

Cause: Schedule already exists.

Action: Check Schedule name.
Level: 32

Type: ERROR

Impact: Other

ODI-01313: Unable to find job definition for ID {0}.

Cause: Wrong ID.

Action: Check ID.
Level: 32

Type: ERROR

Impact: Other

ODI-01314: Unable to find job definition with name {0}.

Cause: Wrong name.

Action: Check name.
Level: 32

Type: ERROR

Impact: Other

ODI-01315: Unable to update job definition.

Cause: Exception during updating.

Action: Check cause exception details.
Level: 32

Type: ERROR

Impact: Other

ODI-01316: Unable to remove job request.

Cause: Exception was thrown.

Action: Check cause exception details.
Level: 32

Type: ERROR

Impact: Other

ODI-01317: Unable to find scheduler definition with name {0}.

Cause: Wrong name.

Action: Check name.
Level: 32

Type: ERROR

Impact: Other

ODI-01318: jobDefnition is required to have a not null ID.

Cause: Metadata Object ID is null.

Action: Check job definition.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-01319: Error while refreshing variable {0}. Null/Empty refresh query is provided.

Cause: This is an execution warning. The variable refresh failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01350: Credential map key ''{0}'' not found in credential map ''{1}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01351: An unexpected error was thrown during execution of the scenario ''{0} - {1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01352: An unexpected error was thrown during job execution

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01353: RequestId={0} Scenario={1} : Agent URL must be specified. The Job Definition must include the LocalAgent or the job submission must include a physical agent url ({2}) parameter.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01354: Load plan must be asynchronous

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01355: username ''{0}'' from credential map ''{1}'' does not match currentSubjectName ''{2}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01356: Credential map key parameter ''{0}'' not found.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01357: Error resolving ADF connection for connectionId=''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01400: Agent {0} start failure: JDBC connection error occurs while connecting to the master repository.

Cause: The master repository information was incorrect, or the repository database was down.

Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01401: Agent {0} start failure: data source for master repository did not contain a master repository.

Cause: The master repository connection information pointed to a database schema that did not contain a master repository.

Action: Verify the master repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01402: Agent {0} start failure: the master repository is in an invalid state.

Cause: The master repository was in a state that did not allow connections. This is the case when an upgrade is being performed.

Action: Verify the state of the master repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01403: Agent {0} start failure: the master repository version {1} is not compatible with the agent version {2}.

Cause: The master repository was upgraded but not this agent, or the agent was upgraded but not the master repository.

Action: Upgrade the master repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01404: Agent {0} start failure: an authentication error occurred while connecting to the master repository.

Cause: An incorrect ODI user or password was specified for this master repository.

Action: Verify the ODI user and password used for connecting.
Level: 1

Type: ERROR

Impact: Other

ODI-01405: Agent {0} start failure: the agent is not defined in the topology for master repository.

Cause: This agent was not declared in the topology.

Action: Add this physical agent in the list of agents in the ODI topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01406: Agent {0} started with warning: JDBC connection error occurs while connecting to the work repository {1}.

Cause: The work repository information was incorrect, or the repository database was down.

Action: Verify the work repository connection information and the status of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01407: Agent {0} started with warning: connection details of {1} do not contain a work repository.

Cause: The work repository connection information pointed to a database schema that did not contain a work repository.

Action: Review the work repository connection information and revise it as necessary.
Level: 1

Type: ERROR

Impact: Other

ODI-01408: Agent {0} started with warning: work repository {1} is in an invalid state.

Cause: The work repository was in a state that did not allow connections. This is the case when an upgrade is being performed.

Action: Verify the state of the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01409: Agent {0} started with warning: work repository {1} version {2} is not compatible with the agent version {3}.

Cause: The work repository was upgraded but not this agent, or the agent was upgraded but not the work repository.

Action: Upgrade the work repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01410: Agent {0} started with warning: work repository {1} is not bound to the master repository.

Cause: The work repository specified in the request was not found in the list of work repositories attached to this master.

Action: Ensure that work repository name matches an existing one.
Level: 1

Type: ERROR

Impact: Other

ODI-01411: Agent {0} started with warning: a database error occurs while cleansing stale sessions.

Cause: The agent encountered a database error while attempting to close stale sessions.

Action: Review the status of the sessions for this agent, and manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01412: Agent {0} started with warning: an unexpected error occurs while cleaning stale sessions.

Cause: The agent encountered an unexpected error while attempting to close stale sessions.

Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode). Verify the status of the sessions for this agent, and manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01413: Request is incorrectly formed.

Cause: A malformed request was sent to the agent.

Action: Review the request format and parameters sent to the agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01414: Error connecting to agent {0}: a JDBC error occurs while connecting to the master repository.

Cause: The remote agent had incorrect connection for the master repository database, or repository database was down.

Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01415: Error connecting to agent {0}: data source for master repository did not contain a master repository.

Cause: The master repository connection information for the remote agent pointed to a database schema that did not contain a master repository.

Action: Review the master repository connection information and revise it as necessary.
Level: 1

Type: ERROR

Impact: Other

ODI-01416: Error connecting to agent {0}: the master repository is in an invalid state.

Cause: The master repository was in a state that did not allow connections from the remote agent. This is the case when an upgrade is being performed.

Action: Verify the state of the master repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01417: Error connecting to agent {0}: the master repository version {1} is not compatible with the agent version {2}.

Cause: The master repository was upgraded but not the remote agent, or the remote agent was upgraded but not the master repository.

Action: Upgrade the master repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01418: Error connecting to agent {0}: an authentication error occurs while connecting to the master repository.

Cause: An incorrect ODI user or password was specified for this master repository.

Action: Verify the ODI user and password used for connecting.
Level: 1

Type: ERROR

Impact: Other

ODI-01419: Warning connecting to Agent {0}: JDBC connection error occurs while connecting to the work repository {1}.

Cause: The remote agent had incorrect connection for the work repository database, or the repository database was down.

Action: Verify the work repository connection information and the status of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01420: Warning connecting to Agent {0}: connection details of {1} do not contain a work repository.

Cause: The work repository connection information for the remote agent pointed to a database schema that did not contain a work repository.

Action: Verify the work repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01421: Warning connecting to Agent {0}: work repository {1} is in an invalid state.

Cause: The work repository was in a state that did not allow connections from the remote agent. This is the case when an upgrade is being performed.

Action: Verify the state of the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01422: Warning connecting to Agent {0}: work repository {1} version {2} is not compatible with the agent version {3}.

Cause: The work repository was upgraded but not the remote agent, or the remote agent was upgraded but not the work repository.

Action: Upgrade the work repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01423: Warning connecting to Agent {0}: work repository {1} is not bound to the master repository.

Cause: The work repository specified in the request was not found in the list of work repositories attached to the master.

Action: Verify that work repository name matches an existing one.
Level: 1

Type: ERROR

Impact: Other

ODI-01424: Agent host or port cannot be reached using {0}.

Cause: Incorrect host or port information was provided, or the agent was not started on the remote host.

Action: Correct the host or port information or start the agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01425: Agent application cannot be reached using {0}.

Cause: An incorrect application name was provided for this agent, or the agent application was not started on the host.

Action: Correct the application name used in the URL or verify the agent status.
Level: 1

Type: ERROR

Impact: Other

ODI-01426: Agent {0} is not defined in the topology for the master repository.

Cause: This agent was not declared in the topology.

Action: Add this physical agent to the list of agents in the ODI topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01427: invalid parameters

Cause: Invalid parameters were supplied in the request.

Action: Check the parameters that were supplied as part of the request. Ensure that parameter names and cases are correct.
Level: 1

Type: WARNING

Impact: Other

ODI-01428: internal error

Cause: An agent internal error occurred.

Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: FATAL

Impact: Other

ODI-01429: The user {0} is not authorized to perform request {1} on Agent {2}.

Cause: The user had insufficient privileges for performing this request against the remote agent.

Action: Amend the user privileges.
Level: 1

Type: ERROR

Impact: Other

ODI-01430: Agent {0} cannot clean the stale sessions in work repository {1} due to a database error.

Cause: The remote agent faced a database error while attempting to close stale sessions.

Action: Examine the status of the sessions for this agent, and manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01431: Agent {0} cannot clean the stale sessions in work repository {1} because the work repository {1} is still down.

Cause: The remote agent was not able to connect to the work repository while attempting to close stale sessions.

Action: Determine the status of the repository. Once this repository is running, manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01432: Agent {0} cannot clean the stale sessions in work repository {1} due to an unexpected error.

Cause: The remote agent faced an unexpected error while attempting to close stale sessions.

Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode). Determine the status of the sessions for this agent, and manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01433: The Internal agent does not support cleaning stale sessions from multiple work repositories.

Cause: Empty string value was passed for the work repository name in the Clean Stale Sessions request sent to the Internal Agent.

Action: Specify a non-empty valid work repository name in the Clean Stale Sessions request sent to the Internal Agent. If you want to clean the stale sessions across the work repositories, perform this operation on a Remote physical Agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01434: Agent {0} start failure: error while trying to use JMX Port {1}.

Cause: JMX Registry was unable to use the given port.

Action: Specify a different port by using the command-line parameter JMXPORT.
Level: 1

Type: ERROR

Impact: Other

ODI-01435: Storage space for the IDs of some object types is low in Repository {0}. When no storage space is available, it will not be possible to create obects of these types. Consider creating a new repository for the following object types (Object Type: Number Remaining) {1}.

Cause: Storage space was low for some IDs in this repository.

Action: Consider creating a new repository.
Level: 1

Type: WARNING

Impact: Other

ODI-01436: Error retrieving ID statistics for repository {0}.

Cause: The ID statistics for this repository could not be verified.

Action: Verify the statistics for this repository manually.
Level: 1

Type: WARNING

Impact: Other

ODI-01437: Error retrieving information from the credential store map.

Cause: Could not retrieve information from the credential store map.

Action: Verify that the credentials have been entered correctly into the credential store map.
Level: 1

Type: ERROR

Impact: Other

ODI-01438: Agent {0} cannot be stopped by user {1}: a JDBC error occurred on master repository {2}.

Cause: Some SQL Exception occurred on the Master Repository.

Action: Verify that other operations on the Agent are working correctly.
Level: 1

Type: ERROR

Impact: Other

ODI-01439: Agent {0} cannot be stopped by user {1}: a JDBC error occurred on work repository {2}.

Cause: Some SQL Exception occurred on the Work Repository.

Action: Verify that other operations on the Agent are working correctly.
Level: 1

Type: ERROR

Impact: Other

ODI-01440: Agent {0} cannot be stopped by user {1}: an unknown error occurred.

Cause: An unexpected Exception occurred.

Action: Verify your Agent configuration and make sure other operations on Agent are working correctly.
Level: 1

Type: ERROR

Impact: Other

ODI-01441: Unable to connect to the master repository at JBDC URL={0} with USER={1}.

Cause: An SQLException occurred while creating connection to the master repository with the given parameters.

Action: Verify your Agent configuration and make sure the master repository connection parameters are correct.
Level: 1

Type: ERROR

Impact: Other

ODI-01442: Unable to load JBDC Driver {0} configured for master repository connection.

Cause: ClassNotFoundException occurred while loading the driver class.

Action: Verify your Agent configuration and make sure the driver specified for master repository connection is correct and the corresponding jar is present under driver folder.
Level: 1

Type: ERROR

Impact: Other

ODI-01443: Error while starting agent : {0}

Cause: Error occurred while starting the embedded web container.

Action: Verify your Agent configuration and make sure that the specified ports are available.
Level: 1

Type: ERROR

Impact: Other

ODI-01444: The master repository signature specified by the client {0} does not match the master repository signature of the agent {1}.

Cause: The client and the agent are not using the same master repository

Action: Verify the client and the agent are using the same master repository. Verify that the client is calling the correct agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01445: Invalid HTTP/S URL retrieved from the JRF utility : {0}

Cause: JRF utility has returned an invalid HTTP/S URL for the agent.

Action: Verify if ODI agent's dependent modules are successfully deployed on the container.
Level: 1

Type: ERROR

Impact: Other

ODI-01446: Agent {0} is already running on port {1}.

Cause: This agent is already running.

Action: Stop the agent before attempting to start it.
Level: 1

Type: ERROR

Impact: Other

ODI-01447: Agent {0} failed to start. {1}.

Cause: The agent failed to start.

Action: See the nodemanager and agent log for further information.
Level: 1

Type: ERROR

Impact: Other

ODI-01448: Failed to execute command {1} for agent {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

ODI-01449: Injection risk detected for command {0}. Command not executed.

Cause: The command was not executed because it contained characters that pose an injection risk.

Action: Adjust the command to eliminate characters that pose an injection risk.
Level: 1

Type: ERROR

Impact: Other

ODI-01450: ODI does not support soft restart.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

ODI-01451: Using localhost for hostname because of {0} when trying to get hostname.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

ODI-01452: Agent {0} cannot be started, {1} is already in use by another agent.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

ODI-01453: Agent {0} cannot be started, {1} is already in use by another process.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

ODI-01454: Agent {0} cannot be started at {1}. Unexpected http response = {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

ODI-01455: System componenent creation failed: instanceName={0}, cause={1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

ODI-01456: getServerConfiguration() failed. domainDir={0}, dirPath={1}, instanceName={2}, cause={3}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

ODI-01457: getDBConfiguration() failed. domainDir={0}, dirPath={1}, datasourceName={2}, cause={3}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

ODI-01458: ODI configuration files found, but a corresponding instance is not configured. dirPath={0}. Cause={1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODI-01459: Failed to retrieve master repository name and timestamp for agent {0}. Using the values from instance.properties. Cause={1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODI-01460: Unable to insert into table {0} for concurrent execution control. Exceptions due to competing insertions can happen and are handled to continue execution. Other exceptions likely indicate a runtime problem. Error message: {1}

Cause: An exception was raised when inserting a record into the concurrent execution control table.

Action: Exceptions due to competing insertions can happen and are handled to continue execution. Other exceptions likely indicate a runtime problem.
Level: 1

Type: WARNING

Impact: Other

ODI-01461: {0} job status has changed unexpectedly from {1} to {2} while waiting for its turn to run under concurrent execution control.

Cause: The status of a job was likely changed outside of the control of the runtime agent while the job was waiting for its turn to run under concurrent execution control by the agent.

Action: The job may have been changed outside of the agent, and the agent skipped the job execution. Start the job again if it was not executed.
Level: 1

Type: WARNING

Impact: Other

ODI-01462: {0} job [{1}] should be the last one in the following waiting {0} list: {2}

Cause: The job may have been changed or deleted outside of the runtime agent while the job was waiting for its turn to run under concurrent execution control by the agent.

Action: The job may have been changed or deleted outside of the agent, and the agent skipped the job execution. Start the job again if it was not executed.
Level: 1

Type: WARNING

Impact: Other

ODI-01463: {0} job [{1}] blocked by the following {0} job(s) due to potential concurrent execution condition: {2}{3}

Cause: The job was under concurrent execution control with Raise Error violation behavior, and there were existing runnable and/or waiting jobs submitted ahead of the job.

Action: Start the job when other concurrently running and waiting jobs are completed, or change the job's violation behavior to Wait To Execute before starting the job.
Level: 1

Type: WARNING

Impact: Other

ODI-01464: There is no Hadoop Dataserver selected for PigDataServer- {0} from topology.

Cause: Repository Error.

Action: Verify the dataservers in topology and associate a Hadoop dataserver to Pig dataserver when in Mapreduce mode .
Level: 1

Type: ERROR

Impact: Other

ODI-01465: Error while trying to read values of Hadoop DataServer- {0} from topology.

Cause: Repository Error.

Action: Verify the dataservers in topology and associate a Hadoop dataserver to Pig dataserver when in Mapreduce mode .
Level: 1

Type: ERROR

Impact: Other

ODI-01466: Error occurred previewing file on agent {0}

Cause: Error previewing file on the agent

Action: Verify that file configuration is valid. Verify that file is available
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-01590: The execution of the script failed. {0}

Cause: The execution of the script failed in the BSF Engine.

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01591: The ODI agent name {0} specified in the client request does not match with the ODI agent {1} serving the request.

Cause: The client and the agent are not using the same physical agent name.

Action: Verify the client and the agent are using the same agent name. Verify that the client is calling the correct agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01592: Error occurred testing connection to dataserver with agent {0}

Cause: Dataserver connection test failed on the agent

Action: Verify that dataserver connection configuration is valid. Verify that dataserver is available
Level: 1

Type: ERROR

Impact: Other

ODI-01593: The following bind parameters ({0}) in the task command {1} are not bound to any value. All the bind parameters should be bound for the command to be successful.

Cause: Either the source command is not providing values for some of the bind parameters in target command or the Odi Variables and/or Odi Sequence meta-data is not generated for the Scenario.

Action: Verify that either the source command is correct or the Odi Variables and/or Odi Sequences meta-data is generated in the Scenario.
Level: 1

Type: ERROR

Impact: Other

ODI-01594: The connection to the data server {0} failed.

Cause: The data server might be down or the data server connectivity settings are not correct.

Action: Verify that you are able to test the data server using the Studio successfully.
Level: 1

Type: ERROR

Impact: Other

ODI-01595: The command script failed with trace {0}.

Cause: There was a failure in the Ftp or Sftp command script.

Action: Verify the trace and resolve the error in the command script passed to the tool.
Level: 1

Type: ERROR

Impact: Other

ODI-01596: Failed to execute the pig script.

Cause: There was a failure in executing Pig script.

Action: Verify the trace and resolve the error in the command script passed.
Level: 1

Type: ERROR

Impact: Other

ODI-01597: The submitted pig script is empty.

Cause: The command did not contain or generate any pig script.

Action: Verify the trace and resolve the error in the code generation.
Level: 1

Type: ERROR

Impact: Other

ODI-01598: Failed to call method {0}.

Cause: Invocation Error.

Action: Verify the trace and resolve the error in the runtime pig engine.
Level: 1

Type: ERROR

Impact: Other

ODI-01599: The associated Hadoop Dataserver with ID- {0} is missing for PigDataServer- {1} from topology.

Cause: Repository Error.

Action: Verify the dataservers in topology and associate a Hadoop dataserver to Pig dataserver when in Mapreduce mode .
Level: 1

Type: ERROR

Impact: Other

ODI-01600: Unable to update Opmn Xml file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01601: Unable to parse Opmn xml file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01602: Please provide all arguments

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01603: Syntax: java DeleteAgentFromOpmn <Instance Home> <OracleOpmnHome> <Agent Name>

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01604: Unable to parse Opmns Snippet Xml

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01605: Component already exists in the file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01606: Please provide the value for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01607: Error reading file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01608: No of values provided for component name and port number are not equal. Please provide the same no of values for both.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01609: No of values provided for component name and JMXport number are not equal. Please provide the same no of values for both.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01610: ODI environment variable {0} is not set and ODI Tool startcmd not launched from interactive console.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01611: Must provide username for {0} before obtaining password.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01612: Unknown parameter ignored: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01613: Unknown parameter value pair ignored: {0}={1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01614: {0} is a mandatory parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01615: DESCRIPTION Resumes an execution session. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX restartsession.(cmd|sh) "-INSTANCE=<instance_name>" <session_number> [<log_level>] ["-AGENT_URL=<agent_url>" | "-AGENT_NAME=<physical_agent_name>"]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01616: DESCRIPTION Starts an agent. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX agent.(cmd|sh) -NAME=<agent name> [-PORT=<port>] [-PROTOCOL=<protocol>] [-JMXPORT=<jmxport>] [-ODI_CONNECTION_RETRY_COUNT=<nn>] [-ODI_CONNECTION_RETRY_DELAY=<nn>] PORT represents the listening port. It should match the port value specified against the physical agent defined in Topology. PROTOCOL represents the listening protocol, HTTP or HTTPS. Its default value is HTTP. NAME represents the name of this physical agent. It should match the name of a physical agent defined in Topology. User must have created an agent with this name using configuration wizard. JMXPORT represents the JMX port used for JMX notifications etc. Its default value is calculated as PORT + 1000, or 20810 if the calculated value is greater than 65535 ODI_CONNECTION_RETRY_COUNT represents the number of times a connection to the ODI Repository will be retried. Its default value is 10 ODI_CONNECTION_RETRY_DELAY represents the number of milliseconds between connection retries to the ODI Repository. Its default value is 7000

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01617: DESCRIPTION Stops an agent. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX agentstop.(cmd|sh) "-NAME=<agent name>" ["-AGENT_URL=<agent_url>"] ["-IMMEDIATE=<true(default)|false>" ["-MAX_WAIT=<stop timeout in millis>"]]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01618: DESCRIPTION Restarts execution of a load plan instance. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX restartloadplan.(cmd|sh) "-INSTANCE=<instance_name>" <load_plan_instance_id> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01619: DESCRIPTION Starts a Oracle Data Integrator command. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX startcmd.(cmd|sh) "-INSTANCE=<instance_name>" <Command Name> ["<command parameter>"]*

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01620: DESCRIPTION Starts a load plan. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX startloadplan.sh "-INSTANCE=<instance_name>" <load_plan_name> <context_code> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"] ["-KEYWORDS=<keywords>"] ["<variable>=<value>"]*

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01621: DESCRIPTION Starts a scenario. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX startscen.(cmd|sh) "-INSTANCE=<instance_name>" <scenario_name> <scenario_version> <context_code> [<log_level>] ["-SESSION_NAME=<session_name>"] ["-KEYWORDS=<keywords>"] ["-AGENT_URL=<agent_url>"] ["-ASYNC=(no|yes)"] ["-DEBUGGABLE=(no|yes)"] ["-SUSPEND_FIRST_STEP=(no|yes)"] ["-DESCENDANTS_DEBUGGABLE=(no|yes)"] ["-BREAK_ON_ERROR=(no|yes)"] ["<variable>=<value>"]* -ASYNC=no is default; -ASYNC=yes is valid only if -AGENT_URL is specified.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01622: DESCRIPTION Stops a load plan instance execution. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX stoploadplan.(cmd|sh) "-INSTANCE=<instance_name>" <load_plan_instance_id> [<load_plan_run_count>] "-AGENT_URL=<agent_url>" ["-STOP_LEVEL=<normal(default)|immediate>"]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01623: DESCRIPTION Stops the execution of a running session. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX stopsession.(cmd|sh) "-INSTANCE=<instance_name>" <session_number> ("-AGENT_URL=<agent_url>" | "-AGENT_NAME=<physical_agent_name>") ["-STOP_LEVEL=<normal(default)|immediate>"]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01624: DESCRIPTION Encode a password. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX encode.(cmd|sh) "-INSTANCE=<instance_name>" <password>

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01625: This must be executed from a domain. System property domain.home cannot be null"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01626: "Neither parameter {0} nor {1} is specified"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01627: "Error getting instance properties"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01628: {0} (arg[{1}]) "{2}" should not be blank.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01629: {0} (arg[{1}]) "{2}" should specify a valid integer.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01630: {0} (arg[{1}]) "{2}" should specify a valid long number.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01631: -STOP_LEVEL parameter value must be one of: {0}, {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01632: Session "{0}" is being stopped ({1})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01633: OracleDI: Starting scenario {0} {1} in context {2} ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01634: "Either parameter {0} or {1} should be specified, and they cannot be specified together."

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01635: "Debug parameters are ignored when -AGENT_NAME parameter is specified."

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01650: -AGENT_URL=<agent_url> is a mandatory parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01651: Agent {0} error while executing: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01652: Unknown parameter ignored: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01653: Unknown parameter value pair ignored: {0}={1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01654: load_plan_instance_id is a mandatory parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01655: Usage: RestartLoadPlan -INSTANCE=<instance_name> <load_plan_instance_id> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01656: Load plan instance "{0}", run {1} has restarted

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01657: load_plan_name and context_code are mandatory parameters

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01658: Usage: StartLoadPlan -INSTANCE=<instance_name> <load_plan_name> <context_code> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"] ["-KEYWORDS=<keywords>"] ["<variable>=<value>"]*

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01659: Load plan "{0}", instance "{1}", run {2} has started

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01660: load_plan_instance_id is a mandatory parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01661: Usage: StopLoadPlan -INSTANCE=<instance_name> <load_plan_instance_id> [<load_plan_run_count>] "-AGENT_URL=<agent_url>" [-STOP_LEVEL=<normal (default) | immediate>]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01662: Load plan instance "{0}", run {1} has stopped ({2})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01663: -STOP_LEVEL parameter value must be one of: {0}, {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01664: Waiting for completion of load plan execution.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01665: Load plan execution completed in {0} status.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01700: SessionId is not valid

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01701: The session was not found in the repository: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01702: This operation is not supported on this platform

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01800: Exception {0} has occurred as ESS-EM linking is disabled.

Cause: Unable to connect to master repository.

Action: Check if the master repository is accessible and up. This is not mandatory since master repositories can be down.
Level: 1

Type: ERROR

Impact: Configuration

ODI-01801: Agent target discovery mbean registration has failed due to {0}.

Cause: A runtime error has occurred.

Action: Check the log for details on the error and take corrective action.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01802: Agent target discovery mbean unregistration has failed due to {0}.

Cause: A runtime error has occurred.

Action: Check the log for details on the error and take corrective action.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01803: Error {0} has occurred during mbean registration.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01804: Error {0} has occurred during mbean deregistration.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01805: Error {0} has occurred during notification listener registration.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01806: Error {0} has occurred during notification listener deregistration.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01807: Error {0} has occurred during deregistration of ODI Service Mbean {1}.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01808: Error {0} has occurred during registration of Agent Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the server and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01809: Error {0} has occurred during registration of Master Repository Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the error and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01810: Error {0} has occurred during registration of Work Repository Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the error and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01811: Error {0} has occurred during registration of Session Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the error and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01812: Error {0} has occurred during registration of Event Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the error and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01813: Error {0} has occurred during registration of Session Search Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the error and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01814: No repository definition found for work repository {0} in repositories.xml. Search will be disabled for this repository.

Cause: A configuration error has occurred.

Action: Add the jndi entries for all the work repositories for each of the master repositories in repositories.xml.
Level: 1

Type: ERROR

Impact: Configuration

ODI-01815: Exception {0} has occurred during Session Search by id.

Cause: A runtime error has occurred.

Action: No action is required. The session id mentioned for search is not available.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01816: Session status passed {0} is invalid.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01817: Error {0} has occurred while fetching statistics for agents. Statistics shown might not be complete.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01818: Agent Service Mbean is not initialized. Re-initialization of agents in tree is disabled.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the same and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01819: Event Service Mbean is not initialized. Re-initialization of event notification listeners is disabled.

Cause: A runtime error has occurred.

Action: Check log for details on the error, fix the same and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01820: Agent {0} is not up at {1} for reason {2}.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03000: error in creating repository connection {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03001: error in updating repository connection {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03002: error in deleting repository connection {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03003: Failed to connect to the error table {0}. Check the connection details and retry.

Cause: The table might no longer exist or the structure of the table might not be correct.

Action: Check the connection details and retry.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03016: Creation of Work Repository failed because a previous Work repository was found, and the user had asked not to overwrite any existing repository.

Cause: Work repository already exists and overwriting of the repository was not chosen

Action: Select overwriting of Work Repository
Level: 1

Type: ERROR

Impact: Data

ODI-03017: Exception occurred while creating Work Repository at {0} failed. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03018: Test connection failed due to {0}.

Cause: Connection to DB failed

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03019: Exception occurred while exporting Master Repository. Failure reason {0}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03020: Only zip files can be uploaded , the {0} upload was unsuccessful.

Cause: A file with extension other than zip was uploaded.

Action: Make sure file uploaded has zip as extension
Level: 1

Type: ERROR

Impact: Data

ODI-03021: Exception occurred while importing Work Repository. Failure reason {0}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03022: Attaching of Work Repository failed due to error: {2}

Cause: Errored out due to {2} and overwriting of the repository was not chosen

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03023: Attaching of Work Repository failed

Cause: An unexpected error occured and overwriting of the repository was not chosen

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03024: Exception occurred while attaching Work Repository at {0} failed. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03031: Creation of Master Repository failed at {0}.

Cause: Creation of Master Repository Failed

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03032: Exception occurred while creating Master Repository at {0} failed. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03033: Supervisor Password and Confirm Supervisor Password fields should match.

Cause: Supervisor Password and Confirm Supervisor Password fields must match

Action: Input same passwords
Level: 1

Type: ERROR

Impact: Data

ODI-03034: Test connection failed due to {0}.

Cause: Testing of DB connection failed

Action: Check the logs
Level: 1

Type: ERROR

Impact: Data

ODI-03035: Supervisor Password and Confirm Supervisor Password fields should match and only zip files can be uploaded , the {0} upload was unsuccessful.

Cause: Both the password match and zip files to be uploaded conditions failed

Action: Make sure both the passwords are same and file uploaded is zip file
Level: 1

Type: ERROR

Impact: Data

ODI-03036: Only zip files can be uploaded , the {0} upload was unsuccessful.

Cause: zip files to be uploaded condition failed

Action: Make sure file uploaded is zip file
Level: 1

Type: ERROR

Impact: Data

ODI-03037: Exception occurred while exporting Master Repository. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03038: Exception occurred while exporting Physical Topology. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03039: Exception occurred while Importing Master Repository. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03040: Unable to connect to the Repository User. {0}

Cause: Testing of DB connection failed

Action: Check the logs
Level: 1

Type: ERROR

Impact: Data

ODI-03041: Unable to connect to the DBA User. {0}

Cause: Testing of DB connection failed

Action: Check the logs
Level: 1

Type: ERROR

Impact: Data

ODI-03046: unable to find the agent for given logical agent and context code

Cause: Physical Agent mapping was not defined for selected logical agent and context.

Action: A different set of credentials is required or the mapping needs to be defined.
Level: 1

Type: ERROR

Impact: Data

ODI-03047: exception while executing {0}. Failure reason {1}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03048: Only XML files can be uploaded: the {0} upload fails

Cause: File selected for import was not a XML file.

Action: Provide the XML file.
Level: 1

Type: ERROR

Impact: Data

ODI-03049: exception while importing {0}. Failure reason {1}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03050: failed to start scenario : {0} ? {1} in debug mode.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03075: Error in purging Load Plans Executions/Sessions {0}

Cause: An exception has occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03076: exception while killing {0}. Failure reason {1}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03077: Selected Session {0} is in {1} State, and therefore cannot be killed.

Cause: The selected session was in Done, Error, or Warning state.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Data

ODI-03078: Selected Session {0} is in {1} State, and therefore cannot be restarted.

Cause: The selected session was not in Error state.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Data

ODI-03079: exception while restarting {0}. Failure reason {1}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03080: exception while clearing stalesessions. Failure reason {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03081: Error fetching records from error table {0}. The table might no more exist or the format of the table is not correct

Cause: The table might no longer exist or the structure of the table might not be correct

Action: Upgrade the CKM
Level: 1

Type: ERROR

Impact: DATA

ODI-03082: CKM SQL does not contain ODI_PK primary key column. Hence unable to delete the error records.

Cause: CKM SQL does not contain ODI_PK primary key column. Hence unable to delete the error records.

Action: Future release will have the ODI_PK primary key column incorporated in CKM SQL.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03083: Scenario "{0}" parent not found.

Cause: Trying to get the Odi Object which does not exist or has been deleted.

Action: Check the logs
Level: 1

Type: ERROR

Impact: Data

ODI-03090: failed to restart session : {0} in debug mode.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03101: import of {1} from {0) failed

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03102: export of {1} to {0) failed

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03103: failed to stop a loadplan instance id : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03104: failed to start a loadplan : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03105: failed to start a scenario : {0} ? {1}

Cause: An unexpected error occured

Action: Check the logs1
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03106: failed to restart session : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03107: failed to clean stale sessions for repository : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03108: failed to stop session : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03109: Creation of work runtime repository at {0} failed. Failure reason {1}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03110: Update of work runtime repository at {0} failed. Failure reason {1}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03111: failed to read config.properties

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03112: shared config dir path is not valid : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03114: {0} not set

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03115: {0} is not correct

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03116: failed to read

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03117: datasource not located at {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03118: Could not get the service locator. JpsServiceLocator service is not configured.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03119: JPS Exception {0} was thrown. Credential Store might not be configured.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03120: Credential store could not be found.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03121: Not populating any values in credential store

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03122: Exception in purging Session/Load Plan Executions

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03123: Exception occured while inserting usedInContext in Physical Schema

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03124: Exception occured while deleting usedInContext in Physical Schema

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03125: Exception occured while inserting usedInContext in Edit Physical Schema

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03126: Exception in adding an entity

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03127: Odi object not found

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03128: Exception in update

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03129: Unable to find odi object {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03130: Loading of entity failed

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03131: Unauthorized to delete entity of type

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03132: error occurred while executing method

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03133: no repository definition found for alias {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03134: login failed for user {0}=

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03135: version mismatch

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03136: unable to connect to repository with alias {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03137: Error occurred in EMIntegrationServlet.doOperation() - {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03138: failed to init jview diagrammer

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03139: repositories.xml path not set

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03140: {0} file does not exist at {1}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03141: failed to create RepositoryDefinitionRegistry

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03142: error logging out a user after session expired

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03143: Creation of work dev repository at {0} failed. Failure reason {1}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03144: Creation of Master Repository failed at {0}. Failure reason {1}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03145: Check the logsPrivilegedActionException {0} was thrown. system-jazn-data.xml might not have the privileges specified.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03146: ???

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03147: Delete operation failed

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03148: Maximum number of sessions should be in between 1 and 99999.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03149: Port Number should not be non negative.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03150: Invalid Context code. Context code cannot have lower case characters and white spaces. Though, it can contain '$' and '_' special characters.

Cause: A validation error occured

Action: Context code cannot have lower case characters and white spaces
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03184: Maximum Cache Entries cannot be less than zero.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03185: Unused Blueprint Lifetime cannot be less than zero.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03186: Maximum Threads Number cannot be less than Max Threads Per Session.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03187: Max Threads Per Session cannot be less than zero.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03188: Maximum Threads Number should be greater than zero.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03189: Maximum Threads Number cannot be less than Maximum Session Number.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03190: Exception fetching connector points. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03191: Exception fetching model. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03192: Exception fetching physical schema. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03193: Exception fetching Data Server. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03194: Exception fetching Catalog. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03195: Exception fetching Constraints. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03196: Exception fetching connector point properties. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03197: Exception during Hadoop Initialization. Reason: {0}

Cause: Error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03198: Exception during Oozie Initialization. Reason: {0}

Cause: Error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03199: Failed to initiate Log retriever. Reason: {0}

Cause: Error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03200: Invalid Deployment Archive. Reason: {0}

Cause: Error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03201: Exception viewing Deployment Archive. Reason: {0}

Cause: Error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03202: IO Exception in Deployment Archive. Reason: {0}

Cause: Error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03203: Exception. Reason: {0}

Cause: Error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03226: Parameter File could not be Loaded.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03260: Failed to apply settings for agent: {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03261: Exception while applying settings for agent: {0}. Failure reason: {1}

Cause: An unexpected error occurred

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03265: Exception occurred while creating Datasource. Failure reason {0}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03266: Data Source already exists for {0}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03267: No valid repository alias is found. Click on management link on top right corner to create one.

Cause: Either there were no repository connection aliases, or those that were created did not have a valid JNDI name

Action: Create a new repository connection alias.
Level: 1

Type: ERROR

Impact: Data

ODI-03276: Tab limit reached.Please close at least one tab.

Cause: Max limit on the number of tabs that can be open has been met.

Action: Close at least one tab
Level: 1

Type: ERROR

Impact: Data

ODI-03277: Object cannot be found.

Cause: The object might have been deleted.

Action: Refresh your view.
Level: 1

Type: ERROR

Impact: Data

ODI-03278: View operation fails with the following exception {0}. See the server log for details.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03279: Add operation failed with the following exception {0}. Please see the server log for details.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03280: Edit operation failed with the following exception {0}. Please see the server log for details.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03281: Delete operation failed with the following exception {0}. Please see the server log for details.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03290: You are not authorized to add a new entity of this type.

Cause: User doesn't have required privileges to add an new entity of a particular type

Action: No action
Level: 1

Type: ERROR

Impact: Data

ODI-03326: Please specify a valid search text

Cause: Invalid search text was specified

Action: Provide a valid search text
Level: 1

Type: ERROR

Impact: Data

ODI-03327: Please choose at least one model or project type.

Cause: No model or project type was selected

Action: Select at least one model or project type so that search criteria is valid
Level: 1

Type: ERROR

Impact: Data

ODI-03328: Please choose at least one topology type.

Cause: No topology type was selected

Action: Select at least one topology type so that search criteria is valid
Level: 1

Type: ERROR

Impact: Data

ODI-03329: Please choose at least one runtime type.

Cause: No runtime type was selected

Action: Select at least one runtime type so that search criteria is valid
Level: 1

Type: ERROR

Impact: Data

ODI-03330: Exception while importing attrbutes. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03331: Exception while importing properties. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03332: Exception while fetching attributes. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03333: Exception while fetching properties. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03334: Exception while importing propeties and expressions of attributes. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03335: Exception while loading components. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03336: Error in persisting user preferences {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03337: UserPref.xml path is not set

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03338: Failed to get User Preferences

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03339: Error in getting policies. Reason: {0}

Cause: Error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03501: Exception while applying deployment archive. Failure reason {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-05000: Task {0} ({1}) on logical schema {2} with Context Id {3} fails since scripting technology name could not be discovered.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-05001: Session {0} ({1}) could not be stopped by Agent {2}: Session run on an 'Internal' agent cannot be stopped from another process.

Cause: Stopping a session being run by an internal agent from another process is not possible.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-05002: Pig Script Execution failure: The following {0} Job(s) - [{1}] reported failed. Please check the resource manager logs for these jobs for the failure reason.

Cause: There was a failure in executing Pig script in MapReduce Mode. Some Jobs have been reported failed.

Action: Verify the Resource Manager trace and resolve the error in the command script passed.
Level: 1

Type: ERROR

Impact: Other

ODI-10000: Method setObject class DwgObjectRepresentor does not support object class: {0}.

Cause: Java method was not found.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-10001: Action unauthorized for this license: {0}

Cause: Action was unauthorized for this license.

Action: Choose another license.
Level: 32

Type: ERROR

Impact: Security

ODI-10002: Only one local repository can be defined; {0} were found.

Cause: More than one local repository was found.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-10003: No connection set.

Cause: No connection was set.

Action: Set connection.
Level: 32

Type: ERROR

Impact: Other

ODI-10004: File already exists.

Cause: File already existed.

Action: Choose another file.
Level: 32

Type: ERROR

Impact: File

ODI-10005: Repository is expected to be a master repository.

Cause: Repository was expected to be a master repository.

Action: Choose master repository.
Level: 32

Type: ERROR

Impact: Other

ODI-10006: Repository is expected to be enterprise repository.

Cause: Repository was expected to be an enterprise repository.

Action: Choose enterprise repository.
Level: 32

Type: ERROR

Impact: Other

ODI-10007: Object must be in editable state before using set methods.

Cause: The object was not in editable state.

Action: Edit this object.
Level: 32

Type: ERROR

Impact: Other

ODI-10008: Object must be in consult mode before using methods get.

Cause: The object was not in consult mode.

Action: Consult the object.
Level: 32

Type: ERROR

Impact: Other

ODI-10009: Object does not exist in the repository.

Cause: The repository did not contains this object.

Action: Choose another object or create first this one.
Level: 32

Type: ERROR

Impact: Other

ODI-10010: This type of object cannot be updated.

Cause: Object could not be updated.

Action: Do not update this object.
Level: 32

Type: ERROR

Impact: Other

ODI-10011: Invalid object; it has been updated by another user.

Cause: Object was updated by another user.

Action: Refresh the object.
Level: 32

Type: ERROR

Impact: Other

ODI-10012: Object cannot be inserted

Cause: Object could not be inserted.

Action: Check object.
Level: 32

Type: ERROR

Impact: Other

ODI-10013: This import action has been cancelled because it could damage your repository. This is due to an {0} object that has object identifier {1} that is greater than that for the current {0} id sequence. Importing this object would lead to primary key violations in the future.

Cause: Import could damage your repository.

Action: Check identifier sequences.
Level: 32

Type: ERROR

Impact: Other

ODI-10014: Method must be redefined in derived classes. It cannot be called for DwgObject

Cause: Method must be redefined in derived classes.

Action: Call redefined method.
Level: 32

Type: ERROR

Impact: Other

ODI-10015: The work repository {0} is not declared in this master repository, the import process has been cancelled.

Cause: Work repository was not declared in this master repository.

Action: Declare work repository and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10016: Import aborted.

Cause: Import was aborted.

Action: Check objects and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10017: This import is forbidden: the text {0} has a different origin in the repository and in the import file.

Cause: The text has a different origin in the repository and in the import file.

Action: Check import file and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10018: The repository {0} is not coherent between the current repository and the import file.

Cause: The repository was not coherent between the current repository and the import file.

Action: Check import file.
Level: 32

Type: ERROR

Impact: Other

ODI-10019: Impossible to create the directory {0}.

Cause: I was not possible to create the directory.

Action: Check your system rights for creating directory; directory's path and name.
Level: 32

Type: ERROR

Impact: File

ODI-10020: Impossible to replace the file

Cause: It was not possible to replace the file.

Action: Check, if you have enough rights for this operation.
Level: 32

Type: ERROR

Impact: File

ODI-10021: Unspecified save directory.

Cause: Directory to save environment information was unspecified.

Action: Specify the directory for saving the environment information file.
Level: 32

Type: ERROR

Impact: Other

ODI-10022: You must specify all options.

Cause: Missed one or more options.

Action: Specify missed options.
Level: 32

Type: ERROR

Impact: Other

ODI-10023: Invalid license. This license is suitable for {0}.

Cause: Invalid license.

Action: Check license.
Level: 32

Type: ERROR

Impact: Security

ODI-10024: Your installation of Oracle Data Integrator is corrupted.

Cause: The technology description file contains errors.

Action: Reinstall Oracle Data Integrator.
Level: 32

Type: ERROR

Impact: Other

ODI-10025: Your installation of Oracle Data Integrator is corrupted.

Cause: The technology description file is missing.

Action: Reinstall Oracle Data Integrator.
Level: 32

Type: ERROR

Impact: Other

ODI-10026: Error while testing the Master Repository technology.

Cause: Error occurred while testing the Master Repository technology.

Action: Check parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-10027: The import is canceled because at least one object is locked by another user.

Cause: At least one object was locked by another user.

Action: Check objects' locks.
Level: 32

Type: ERROR

Impact: Other

ODI-10028: It is forbidden to import a log into a repository having the same ID.

Cause: The log had the same ID as repository.

Action: Check log and/or repository id.
Level: 32

Type: ERROR

Impact: Other

ODI-10029: Version {0} for object {1} already exists.

Cause: Version already existed.

Action: Choose another version.
Level: 32

Type: ERROR

Impact: Other

ODI-10030: DwgBeanWrapper can only wrap DwgObjects

Cause: DwgBeanWrapper can only wrap DwgObjects

Action: Choose correct type of objects.
Level: 32

Type: ERROR

Impact: Other

ODI-10031: Object {0}: {1} is locked by user {2}

Cause: Object was locked by another user.

Action: Wait until object is unlocked.
Level: 32

Type: ERROR

Impact: Other

ODI-10032: You cannot import this object ({0}). A referenced object ({1}) does not exist in the repository.

Cause: A referenced object does not exist in the repository.

Action: Check import file.
Level: 32

Type: ERROR

Impact: Other

ODI-10033: You cannot delete this object because it is locked by another user ({0}).

Cause: This object was locked by another user.

Action: Wait until object is unlocked.
Level: 32

Type: ERROR

Impact: Other

ODI-10034: The technology hosting your master repository does not support Versioning.

Cause: The technology did not support versioning.

Action: Choose another repository or technology.
Level: 32

Type: ERROR

Impact: Other

ODI-10035: {0} : ''{1}'' (with global id: {5} and internal id: {6}) violates alternate key constraint {2} {3} for values {4}

Cause: Object violated alternate key constraint.

Action: Check object properties and constraint's values.
Level: 32

Type: ERROR

Impact: Other

ODI-10036: Importing object {0} : {1} (with global id: {2} and internal id: {3}) failed.

Cause: Import failed.

Action: Check import file and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10037: Import-replace for this node is supported for action groups only. The import file is invalid.

Cause: Import-replace for this node was supported for action groups only.

Action: Check import file.
Level: 32

Type: ERROR

Impact: Other

ODI-10038: The interface you are trying to use ({0}) is related to a logical schema ({1}) that no longer exists.

Cause: Logical schema was not found.

Action: Check interface.
Level: 32

Type: ERROR

Impact: Other

ODI-10039: Bad ID for an object representer

Cause: Bad ID for an object representer

Action: Check object`s ID.
Level: 32

Type: ERROR

Impact: Other

ODI-10040: Cannot create directory

Cause: Directory could not be created.

Action: Check directory path/name.
Level: 32

Type: ERROR

Impact: File

ODI-10041: Oracle Data Integrator Remote Object (SnpRemoteObject) must inherit from SnpsFunction.

Cause: Oracle Data Integrator Remote Object (SnpRemoteObject) did not inherit from SnpsFunction.

Action: Use SnpsFunction as parent.
Level: 32

Type: ERROR

Impact: Other

ODI-10042: SnpsQuery must be connected prior to execution

Cause: SnpsQuery was not connected.

Action: Set a connection.
Level: 32

Type: ERROR

Impact: Other

ODI-10043: Security token is a mandatory parameter

Cause: Security token was not specified.

Action: Check security parameters.
Level: 32

Type: ERROR

Impact: Security

ODI-10044: Unable to save the interface. Maximum number of source datastores exceeded.

Cause: Maximum number of source datastores was exceeded.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-10045: a2.getCargo() not instance of SAPSegment

Cause: a2.getCargo() not instance of SAPSegment

Action: Check SAP Tree.
Level: 32

Type: ERROR

Impact: Other

ODI-10046: No IDoc.

Cause: Missed IDoc.

Action: Check IDoc.
Level: 32

Type: ERROR

Impact: Other

ODI-10047: Repository is not a development work repository

Cause: Repository was not a development work repository.

Action: Choose development work repository.
Level: 32

Type: ERROR

Impact: Other

ODI-10048: No work repository found.

Cause: No work repository was found.

Action: Check your connection settings or database.
Level: 32

Type: ERROR

Impact: Other

ODI-10049: Missing parameter

Cause: Parameter was missing.

Action: Check all parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-10050: Missing parameter at: {0} SQL: {1}

Cause: Parameter was missing.

Action: Check all parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-10051: Some objects cannot be exported because they do not exist in the repository: {0} {1}

Cause: Objects did not exist in the repository.

Action: Check objects state.
Level: 32

Type: ERROR

Impact: Other

ODI-10052: A problem occurred in your repository.

Cause: A problem occurred in your repository.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-10053: Problem retrieving JCOFunction object. {0}

Cause: Problem occurred retrieving JCOFunction object.

Action: Check JCO Function object.
Level: 32

Type: ERROR

Impact: Other

ODI-10054: Unable to find the XML file corresponding to your technology.

Cause: XML file corresponding to your technology was not found.

Action: Check technology and/or XML file for the technology.
Level: 32

Type: ERROR

Impact: Other

ODI-10055: This ID is already in use in the repository

Cause: This ID was already in use in the repository.

Action: Change ID.
Level: 32

Type: ERROR

Impact: Other

ODI-10056: This repository ID already exists. This repository cannot be created.

Cause: Repository ID already existed.

Action: Change repository ID.
Level: 32

Type: ERROR

Impact: Other

ODI-10057: Unrecognized export type.

Cause: Export type was unrecognized.

Action: Check export type.
Level: 32

Type: ERROR

Impact: Other

ODI-10058: You are trying to import objects from a master repository of an older version into {0} version. This action is forbidden. Master repositories must be upgraded using the upgrade assistant, not using the export/import facility.

Cause: You tried to import objects from a master repository of an older version.

Action: Master repositories must be upgraded using the upgrade assistant, not using the export/import facility.
Level: 32

Type: ERROR

Impact: Other

ODI-10059: Repository is null

Cause: Repository was null.

Action: Check repository.
Level: 32

Type: ERROR

Impact: Other

ODI-10060: Saputil is mandatory.

Cause: Saputil was mandatory.

Action: Check Saputil
Level: 32

Type: ERROR

Impact: Other

ODI-10061: Empty XML Character Set

Cause: XML Character Set was empty.

Action: Fill XML Character Set.
Level: 32

Type: ERROR

Impact: Other

ODI-10062: Unable to find license key {0}. An exception {1} occurred with message: {2}

Cause: An exception occurred.

Action: Check license key.
Level: 32

Type: ERROR

Impact: Other

ODI-10063: Unable to check the license key. An exception {0} occurred with message: {1}

Cause: An exception occurred.

Action: Check license key.
Level: 32

Type: ERROR

Impact: Other

ODI-10064: The interface must have a JMS datastore as a source or target. Another license is required otherwise.

Cause: The interface must have a JMS datastore as a source or target.

Action: Check datastore type and/or license.
Level: 32

Type: ERROR

Impact: Other

ODI-10065: You license does not include these features. Please contact your reseller.

Cause: You license does not include these features.

Action: Please contact your reseller.
Level: 32

Type: ERROR

Impact: Other

ODI-10066: The interface is using a Datastore defined in Model "{0}" which is linked to a logical schema "{1}" that no longer exists.

Cause: Logical schema was not found.

Action: Correct interface.
Level: 32

Type: ERROR

Impact: Other

ODI-10067: Target file already exists.

Cause: Target file already existed.

Action: Choose another target file name.
Level: 32

Type: ERROR

Impact: File

ODI-10068: SnpsConnection: Current Isolation level: {0}. The new Isolation level: {1}, not supported

Cause: Isolation level not supported.

Action: Check isolation level.
Level: 32

Type: ERROR

Impact: Other

ODI-10069: Unsupported XML Character Set: {0}

Cause: Unsupported XML Character Set.

Action: Check XML charset.
Level: 32

Type: ERROR

Impact: Other

ODI-10070: Cannot delete this object. It is being edited or viewed

Cause: Object was being edited or viewed.

Action: Stop edit or view object and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10071: Cannot delete this object

Cause: Could not delete this object.

Action: Check object state.
Level: 32

Type: ERROR

Impact: Other

ODI-10073: A repository already exists on this data server

Cause: A repository already existed on this data server.

Action: Choose another data server.
Level: 32

Type: ERROR

Impact: Other

ODI-10074: An object with the wrong type was given to an object representative

Cause: An object with the wrong type was given to an object representative

Action: Check object type.
Level: 32

Type: ERROR

Impact: Other

ODI-10075: An object is in an unidentified state {0}

Cause: An object is in an unidentified state.

Action: Check object state.
Level: 32

Type: ERROR

Impact: Other

ODI-10076: A collection object is the wrong class

Cause: A collection object is the wrong class.

Action: Check collection object's class
Level: 32

Type: ERROR

Impact: Other

ODI-10077: Undefined action performed on an object: {0}

Cause: An undefined action was performed on an object.

Action: Check action and object.
Level: 32

Type: ERROR

Impact: Other

ODI-10078: An object will be in an unidentified state (it is in the state "{0}" and "{1}" is currently being performed on it)

Cause: An object would have been in an unidentified state.

Action: Check object state.
Level: 32

Type: ERROR

Impact: Other

ODI-10080: Incorrect License ....

Cause: Incorrect License.

Action: Contact your seller.
Level: 32

Type: ERROR

Impact: Other

ODI-10081: You are not authorized to Insert the Object: {0}: {1} / {2}

Cause: You were not authorized to Insert the Object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10082: You are not authorized to View the Object: {0}: {1}

Cause: You were not authorized to View the Object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10083: You are not authorized to Delete the Object: {0}: {1} / {2}

Cause: You were not authorized to Delete the Object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10084: You are not authorized to Edit the Object: {0}: {1} / {2}

Cause: You were not authorized to Edit the Object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10085: You cannot consult this object

Cause: You could not consult this object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10086: You cannot edit this object

Cause: You could not edit this object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10087: You can only give Supervisor Access Privileges if you are a Supervisor.

Cause: You could only give Supervisor Access Privileges if you are a Supervisor.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10088: Empty Java Character Set.

Cause: Java Character Set was empty.

Action: Fill Java charset.
Level: 32

Type: ERROR

Impact: Other

ODI-10089: You cannot modify another user''s password

Cause: You cannot modify another user''s password

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10090: Object {0} {1} is referenced by: {2}. Cannot remove.

Cause: Object was referenced by another one.

Action: Check object''s references.
Level: 32

Type: ERROR

Impact: Other

ODI-10091: not connected

Cause: not connected

Action: Check connection.
Level: 32

Type: ERROR

Impact: Other

ODI-10092: Some objects cannot be exported. They do not exist in the repository.

Cause: Objects did not exist in the repository.

Action: Check objects'' state.
Level: 32

Type: ERROR

Impact: Other

ODI-10093: You are importing an object from another repository with the same identifier. It is forbidden.

Cause: You tried to import an object from another repository with the same identifier.

Action: Change repository ID.
Level: 32

Type: ERROR

Impact: Other

ODI-10094: Problem while computing new name.

Cause: A problem occurred while computing new name.

Action: Try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10095: Exception while getting the children list

Cause: Exception while getting the children list.

Action: Try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10096: Error while parsing fields

Cause: Error occurred while parsing fields.

Action: Check fields value.
Level: 32

Type: ERROR

Impact: Other

ODI-10097: Impossible to find text with ID {0} in text list.

Cause: Text was not found.

Action: Check text ID
Level: 32

Type: ERROR

Impact: Other

ODI-10098: No connection available. Check connection parameters.

Cause: No connection was available.

Action: Check connection parameters.
Level: 32

Type: ERROR

Impact: Network

ODI-10099: Object cannot be exported because the file with name {0} could not be created.

Cause: Object could not be exported because the file could not be created.

Action: Check your system rights to write files and file name.
Level: 32

Type: ERROR

Impact: Other

ODI-10100: Empty XML Version

Cause: XML version was empty.

Action: Fill XML Version.
Level: 32

Type: ERROR

Impact: Other

ODI-10101: Invalid XML Version: {0}

Cause: XML Version was invalid.

Action: Check XML version.
Level: 32

Type: ERROR

Impact: Other

ODI-10102: Alias with the name {0} already exists.

Cause: Alias already exists.

Action: Change alias.
Level: 32

Type: ERROR

Impact: Other

ODI-10103: Alias with the name {0} does not exist.

Cause: Alias doesn't exit.

Action: Check alias name ant try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10104: File {0} is not a Smart Export file and cannot be imported by Smart Import.

Cause: Smart Export file not specified for Smart Import.

Action: Specify a Smart Export file for importing via Smart Import.
Level: 32

Type: ERROR

Impact: Other

ODI-10105: Smart Import file name cannot be null.

Cause: Smart Export file name not specified for Smart Import.

Action: Specify a Smart Export file for importing via Smart Import.
Level: 32

Type: ERROR

Impact: Other

ODI-10106: Smart Import response file name cannot be null.

Cause: Smart import response file name not specified for Smart Import.

Action: Specify a Smart Import response file.
Level: 32

Type: ERROR

Impact: Other

ODI-10107: Smart Import file {0} not found.

Cause: File does not exist.

Action: Specify an existing Smart Export file for importing via Smart Import.
Level: 32

Type: ERROR

Impact: Other

ODI-10108: Smart Import response file {0} not found.

Cause: Response file does not exist.

Action: Specify an existing Smart Import response file.
Level: 32

Type: ERROR

Impact: Other

ODI-10109: File {0} is not a valid Smart Import Response file.

Cause: File is not a valid Smart Import response.

Action: Specify an existing Smart Import response file.
Level: 32

Type: ERROR

Impact: Other

ODI-10110: {0} with the same {1} exists.

Cause: An object with the same alternative key value(s) exists.

Action: Change the alternative key value to be unique.
Level: 32

Type: ERROR

Impact: Other

ODI-10111: {0} <{1}> referenced by {2} <{3}> is missing.

Cause: A referenced object does not exist.

Action: Either import the missing object or change to reference a different object.
Level: 32

Type: WARNING

Impact: Other

ODI-10112: Project code will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing project code.

Action: Determine whether the change to project code is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10113: {0} with {1} <{2}> does not exist.

Cause: A referenced object does not exist.

Action: Either import the missing object or change to reference a different object.
Level: 32

Type: WARNING

Impact: Other

ODI-10114: {0} with {1} id <{2}> does not exist.

Cause: A referenced object does not exist.

Action: Either import the missing object or change to reference a different object.
Level: 32

Type: WARNING

Impact: Other

ODI-10115: {0} with the same name <{1}> already exists.

Cause: A different object with the same name already exists.

Action: Either change the name of the object being imported or use match by name to match to the already existing object with the same name.
Level: 32

Type: WARNING

Impact: Other

ODI-10116: Model code will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing model code.

Action: Determine whether the change to model code is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10117: Sub-model code will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing sub-model code.

Action: Determine whether the change to sub-model code is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10118: A different Physical Schema is already set as the default physical schema for the same data server.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-10119: A different Context is already set as the default Context.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-10120: Context code will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing context code.

Action: Determine whether the change to context code is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10121: Logical schema name will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing logical schema name.

Action: Determine whether the change to logical schema name is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10122: Logical agent name will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing logical agent name.

Action: Determine whether the change to logical agent name is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10123: {0} with {1} <{2}> and {3} <{4}> does not exist.

Cause: A referenced object does not exist.

Action: Either import the missing object or change to reference a different object.
Level: 32

Type: WARNING

Impact: Other

ODI-10124: Smart import of file {0} cannot be run due to unfixed critical issues.

Cause: Critical issues exist for objects in the Smart Import.

Action: A fix must be provided for all critical issues before the Smart Import can be run.
Level: 32

Type: ERROR

Impact: Other

ODI-10125: Smart Export file name cannot be null.

Cause: Smart Export file name not specified for Smart Export.

Action: Specify a Smart Export file via Smart Export.
Level: 32

Type: ERROR

Impact: Other

ODI-10126: File {0} already exists.

Cause: The file already exists.

Action: Specify another file name.
Level: 32

Type: ERROR

Impact: Other

ODI-10127: Column position {0} is being used by another object <{1}>.

Cause: The position value is already in use.

Action: Specify a unique position value.
Level: 32

Type: ERROR

Impact: Other

ODI-10128: Multiple primary keys found. Only one primary key can be defined per datastore.

Cause: Multiple primary keys defined.

Action: Delete or match primary keys so that only one is defined.
Level: 32

Type: ERROR

Impact: Other

ODI-10129: Object with id {0} and type {1} is not a smart exportable object.

Cause: Smart Export does not support the type of object specified.

Action: Do not export this object.
Level: 32

Type: ERROR

Impact: Other

ODI-10130: Smart Import Response file {0} is not valid for Smart Export file {1}.

Cause: Smart Import Response file was not generated for the Smart Export file being imported.

Action: Specify a Smart Import response file that belongs to the Smart Export file being imported.
Level: 32

Type: ERROR

Impact: Other

ODI-10131: Entity of type {0} cannot be merged.

Cause: Wrong entity type.

Action: Check entity type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10132: Entity of type {0} cannot be removed.

Cause: Wrong entity type.

Action: Check entity type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10133: Cannot create a transaction against the extended persistent context [{0}].

Cause: Another persistence context is already bound to the current thread.

Action: Unbound persistence context from current thread.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10134: You don't have READ permission on at least one object from the collection/list.

Cause: Insufficient level of permissions.

Action: Check your permissions
Level: 32

Type: ERROR

Impact: Security

ODI-10135: Max value ({1}) reached for sequence {0} and reset is not allowed.

Cause: Reset is not allowed.

Action: Check configuration of sequence behaviour.
Level: 32

Type: ERROR

Impact: Other

ODI-10136: Illegal transaction state: transaction synchronization is active but entity manager is not synchronized within the transaction.

Cause: Entity manager is not synchronized within the transaction.

Action: Synchronize entity manager and try again.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10137: Your program needs to set authentication first.

Cause: There is no authentication set.

Action: Set authentication via odiInstance.getSecurityManager().setGlobalAuthentication(.) or odiInstance.getSecurityManager().setCurrentThreadAuthentication(.), see the SecurityManager API for more detail.
Level: 32

Type: ERROR

Impact: Security

ODI-10138: Unable to create DwgConnectConnection to {0} repository.

Cause: Exception during connection.

Action: Check repository configuration.
Level: 32

Type: ERROR

Impact: Other

ODI-10139: {0} must not be null or empty.

Cause: Parameter is null or empty.

Action: Check parameter name.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10140: {0} must be greater or equal 0.

Cause: Parameter is negative.

Action: Check parameter value.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10141: Unable to create datasource provider from class [{0}].

Cause: Exception during creation.

Action: Check configuration.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10142: Active transaction is required to use the method {0} on the TransactionalOdiEntityManager.

Cause: Transaction isn't active.

Action: Check transaction state.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10143: Error while accessing the {0} repository.

Cause: Network problems.

Action: Check the network connection and the database status.
Level: 32

Type: ERROR

Impact: Network

ODI-10144: OdiInstance is closed.

Cause: OdiInstance is closed.

Action: Check OdiInstance status.
Level: 32

Type: ERROR

Impact: Other

ODI-10145: Limited persistence support.

Cause: Limited persistence support.

Action: Check OdiInstance configuration.
Level: 32

Type: ERROR

Impact: Other

ODI-10146: Cannot create JDBC DataSource for this type of DataServer.

Cause: Invalid connection provider.

Action: Check connection provider.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10147: Repository type mismatches.

Cause: Wrong repository type.

Action: Check repository type.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10148: Repository is in error install/upgrade state and needs to be repaired. Connection has been disabled.

Cause: Repository install/upgrade did not complete successfully.

Action: Check install/upgrade log files and/or ODI user documentation for information on reparation process.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10149: Local Repository table is empty.

Cause: Local Repository table is empty.

Action: Check repository configuration.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10150: Work repository with ID {0} is not bound to master: Definition in master ID:{0}, Name:{1}, Timestamp:{2} Definition in work ID:{3}, Name:{4}, Timestamp:{5}.

Cause: Work repository with ID is not bound to master repository.

Action: Check work and master repositories configuration.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10151: Unable to get ID for entity {0}.

Cause: Wrong entity ID.

Action: Check entity properties.
Level: 32

Type: ERROR

Impact: Security

ODI-10152: I_OBJECTS for entity class {0} is not found.

Cause: Entity type is not mapped to I_OBJECTS.

Action: Check entity class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10153: {0} is denied.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10154: {0} is denied for {1}.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10155: You don't have {0} permission on at least one object from the collection/list.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10156: Impossible to connect to JPS MBean Server.

Cause: Exception during connection.

Action: Check configuration.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10157: {0}: must call preWebLogic() before postWebLogic().

Cause: Wrong API usage.

Action: Call preWebLogic() before postWebLogic().
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10158: The credential with map name {0} and key {1} already exists.

Cause: Wrong credential.

Action: Check credential configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10159: The user {0} hasn't required CONNECT profile.

Cause: The user hasn't required profile.

Action: Grant the user CONNECT profile first.
Level: 32

Type: ERROR

Impact: Security

ODI-10160: Unable to load user.

Cause: Exception during user loading.

Action: Check repository connection.
Level: 32

Type: ERROR

Impact: Other

ODI-10161: Trying to create authentication with Subject parameter which should be applicable when OPSS authentication is used, but ODI shows it is using ODI internal authentication.

Cause: ODI internal authentication is used instead of OPSS authentication.

Action: Check authentication type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10162: This OPSS user ''{0}'' is not registered to Oracle Data Integrator.

Cause: The user is not registered to ODI.

Action: Check user name.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10163: This OPSS user ''{0}'' has different GUID than the one found in Oracle Data Integrator repository.

Cause: OPSS user differs from ODI user in GUID.

Action: Check user GUID.
Level: 32

Type: ERROR

Impact: Security

ODI-10164: Only supervisor user can invoke this API.

Cause: Insufficient level of permissions.

Action: Check user role.
Level: 32

Type: ERROR

Impact: Security

ODI-10165: The RunAsUser {0} is not a valid user from external user identity store.

Cause: User isn't valid.

Action: Check user.
Level: 32

Type: ERROR

Impact: Security

ODI-10166: The RunAsUser: {0} has different GUID in ODI repository and external user identity store.

Cause: User from external user identity store differs from ODI user in GUID.

Action: Check user.
Level: 32

Type: ERROR

Impact: Security

ODI-10167: Authentication is missing.

Cause: Authentication is missing.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Security

ODI-10168: There is already an Authentication bound to this thread.

Cause: There is already an Authentication bound to this thread.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10169: Trying to set authentication object which is not created by this security manager.

Cause: Authentication object isn't created by this security manager.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10170: There is currently no Authentication bound to this thread.

Cause: There is currently no Authentication bound to this thread.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Security

ODI-10171: There is already an Authentication bound as global Authentication.

Cause: There is already an Authentication bound as global Authentication.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10172: There is currently no global Authentication bound to this SecurityManager.

Cause: There is currently no global Authentication bound to this SecurityManager.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Security

ODI-10173: You are not authorized to change the password for external user ''{0}''.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10174: You are not authorized to change the password for user ''{0}''.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10175: You are not authorized to change the password for external user.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10176: Authentication is needed to change password.

Cause: Authentication is missed.

Action: Authenticate first.
Level: 32

Type: ERROR

Impact: Security

ODI-10177: ODI was not able to load the jdbc driver class "{0}" provided on {1}.

Cause: Wrong jdbc driver class.

Action: Check that the driver class name is correct and that this driver is available to ODI classloader.
Level: 32

Type: ERROR

Impact: Other

ODI-10178: The jdbc URL "{1}" was not accepted by the jdbc driver class "{0}" provided on {2}.

Cause: Insufficient jdbc URL.

Action: Check that the jdbc URL and the driver class name are matching.
Level: 32

Type: ERROR

Impact: Other

ODI-10179: Client requires a repository with version {0} but the repository version found is {1}.

Cause: Insufficient repository version.

Action: Check repository configuration.
Level: 32

Type: ERROR

Impact: Other

ODI-10180: ODI was not able to load the jdbc driver class {0} specified in ODI topology for work repository {1}.

Cause: Wrong jdbc driver class.

Action: Check that the driver class name is correct and that this driver is available to ODI classloader. If the driver class name is incorrect please connect to ODI topology to fix it.
Level: 32

Type: ERROR

Impact: Other

ODI-10181: Uncategorized configuration exception.

Cause: An unexpected error occurred.

Action: Check exception cause for details.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10182: Uncategorized exception during repository access.

Cause: An unexpected error occurred.

Action: Check exception cause for details.
Level: 32

Type: ERROR

Impact: Other

ODI-10183: {0} is an invalid finder class.

Cause: Wrong finder class.

Action: Check finder class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10184: Could not get ESS {0}.

Cause: Exception during session retrieving.

Action: Check configuration and try again.
Level: 32

Type: ERROR

Impact: Session

ODI-10185: Operation is not granted.

Cause: Current level of permission is not sufficient.

Action: Check your permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10186: User {0} is inactive.

Cause: There is no GUID defined for this User in ODI repository

Action: Check user GUID.
Level: 32

Type: ERROR

Impact: Security

ODI-10187: The authentication API is used in wrong way.

Cause: The authentication API is used in wrong way.

Action: Check usage of API.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10188: Error while login from OPSS.

Cause: Exception was thrown during login process.

Action: Make sure OPSS is configured correctly for this installation.
Level: 32

Type: ERROR

Impact: Other

ODI-10189: The password violates the following rule: "Password policy {0}". Select another password.

Cause: Weak password

Action: Check password policy and correct password.
Level: 32

Type: ERROR

Impact: Security

ODI-10190: The user {0} has its account expired.

Cause: Account expired

Action: Request supervisor for account unlocking.
Level: 32

Type: ERROR

Impact: Security

ODI-10191: Unable to create datasource provider.

Cause: Exception during creation.

Action: Check configuration.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10192: Unable to retrieve user GUID.

Cause: Exception during GUID retrieving.

Action: Check repository connection.
Level: 32

Type: ERROR

Impact: Other

ODI-10193: Unexpected null value in port.

Cause: JPS port value is null.

Action: Check JPS configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10194: Uncategorized security exception.

Cause: An unexpected error occurred.

Action: Check exception cause for details.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10195: CsfAccessor is only available for CsfPasswordStorageConfiguration

Cause: Password storage configuration is internal.

Action: Check storage configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10196: Error while accessing the repository.

Cause: Network problems.

Action: Check the network connection and the database status.
Level: 32

Type: ERROR

Impact: Network

ODI-10197: Instance is not connected to a work repository

Cause: Work datasource is null.

Action: Check work datasource.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10198: Context with code '{0}' wasn''t found.

Cause: Context wasn't found.

Action: Check context code.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10199: Incorrect ODI username or password.

Cause: Incorrect ODI username or password.

Action: Check username and password.
Level: 32

Type: ERROR

Impact: Security

ODI-10200: Work repository {0} wasn''t found.

Cause: Wrong repository name or repository isn't defined.

Action: Check repository name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10201: The user {0} has its password expired.

Cause: Account expired

Action: Request supervisor for changing password.
Level: 32

Type: ERROR

Impact: Security

ODI-10202: Supervisor privilege is required to setup repository.

Cause: Insufficient level of permissions.

Action: User supervisor account for this operation.
Level: 32

Type: ERROR

Impact: Security

ODI-10203: Transaction state is illegal.

Cause: Transaction state is illegal.

Action: Check transaction state.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10204: Inappropriate usage of a ODI transaction API.

Cause: Inappropriate usage of a ODI transaction API.

Action: Check ODI transaction API.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10205: Unexpected rollback.

Cause: Attempt to commit a transaction resulted in an unexpected rollback.

Action: Check transaction.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10206: Transaction can't be created.

Cause: Exception was thrown during transaction creation.

Action: Check transaction.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10207: Uncategorized exception during transaction system usage.

Cause: An unexpected error occurred.

Action: Check exception cause for details.
Level: 32

Type: ERROR

Impact: Other

ODI-10208: Error when changing password for user {0}.

Cause: An unexpected error occurred.

Action: Check exception cause for details.
Level: 32

Type: ERROR

Impact: Other

ODI-10209: Cannot access a closed IOdiEntityManager.

Cause: IOdiEntityManager has been closed.

Action: Check IOdiEntityManager state.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10210: File {0} does not contain any objects to be imported by Smart Import.

Cause: Smart Export file specified for Smart Import is empty.

Action: Specify a Smart Export file with objects for importing via Smart Import.
Level: 32

Type: ERROR

Impact: Other

ODI-10211: Unsupported Java Character Set: {0}

Cause: Unsupported Java Character Set.

Action: Check Java charset.
Level: 32

Type: ERROR

Impact: Other

ODI-10212: Parent object {0}: ''{1}'' already has child {2}: ''{3}''. Technical details: {2} : ''{3}'' (with global id: {7} and internal id: {8}) violates alternate key constraint {4} {5} for values {6}

Cause: Object violated alternate key constraint.

Action: Check object properties and constraint's values.
Level: 32

Type: ERROR

Impact: Other

ODI-10213: Fixed format file field {0} (starts at {1} ends at {2}) has a file position that overlaps with the file position of field {3} (starts at {4} ends at {5}).

Cause: Two fields from a fixed format file have overlapping file positions.

Action: Modify the file positions or remove a field if the overlapping file positions are not correct.
Level: 32

Type: ERROR

Impact: Other

ODI-10214: Fixed format file fields {0} (starts at {1} ends at {2}) and {3} (starts at {4} ends at {5}) have unused file positions between them.

Cause: Two fields from a fixed format file have unused file positions between them.

Action: Modify the file positions if having unused file positions is not correct.
Level: 32

Type: ERROR

Impact: Other

ODI-10215: It is forbidden to import a log into a repository using any other import mode except "Synonym Mode Insert".

Cause: Import mode is not "Synonym Mode Insert".

Action: Correct import mode.
Level: 32

Type: ERROR

Impact: Other

ODI-10216: Upgrade key cannot be null when importing objects from before ODI 12C.

Cause: Upgrade key is not set for import that must upgrade objects to have global ids.

Action: Specify the upgrade key to be used.
Level: 32

Type: ERROR

Impact: Other

ODI-10217: Permission check failed for instance object {0}.

Cause: Permission check failed for instance object.

Action: Need to grant initial permission for creator on object.
Level: 32

Type: NOTIFICATION

Impact: Other

ODI-10218: Invalid WAS_HOME ("{0}") set or WebSphere library jar ({1}) not found under WAS_HOME/plugins.

Cause: Wrong WAS_HOME set (or) WebSphere libraries (com.ibm.ws.admin.core.jar, com.ibm.ws.admin.services.jar, com.ibm.ws.runtime.jar) are moved

Action: Check that the environment-variable WAS_HOME is set properly to point to WebSphere Application Server root. Also, ensure the libraries exist under WAS_HOME/plugins.
Level: 32

Type: ERROR

Impact: Other

ODI-10219: ODI Library for WebSphere access ({0}) not found.

Cause: Library could be moved / deleted

Action: Check that the specified library present
Level: 32

Type: ERROR

Impact: Other

ODI-10220: ODI was unable to find the technology "{0}".

Cause: Missing technology.

Action: Check that this technology is defined in the repository. .
Level: 32

Type: ERROR

Impact: Other

ODI-10221: It's taken {0} second to synchronize Snp_Ent_Principal table content.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-10222: The compatible Mapping/ReusableMapping {0} can only be modified by 11g SDK.

Cause: An attempt was made to modify compatible Mapping using 12c SDK.

Action: Modify compatible Mapping using 11g Interface SDK.
Level: 32

Type: ERROR

Impact: Other

ODI-10223: A non-legacy compatible import source cannot be imported into a legacy compatible repository.

Cause: An attempt was made to import a non-legacy compatible import source into a legacy compatible repository.

Action: Import a legacy compatible import source or make repository not legacy compatible.
Level: 32

Type: ERROR

Impact: Other

ODI-10224: You are not authorized to create new user.

Cause: Only SUPERVISOR could create users.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10225: Invalid wallet password: A valid password must have a minimum length of eight characters and contain alphabetic characters combined with numbers or special characters.

Cause: Invalid wallet password.

Action: Please choose a valid wallet password accordingly.
Level: 32

Type: ERROR

Impact: Security

ODI-10226: Wallet already exists.

Cause: Try to create a wallet which already exists.

Action: Please stop creating a wallet. Instead use the existing one.
Level: 32

Type: ERROR

Impact: Security

ODI-10227: Wallet new password is same as old password.

Cause: You provide a new wallet password which is the same as the old one.

Action: Please choose different wallet password than the old one.
Level: 32

Type: ERROR

Impact: Security

ODI-10228: Repository with id ''{0}'' or with name ''{1}'' has been already used in your master repository.

Cause: Master repository has already work repository with the same name or id.

Action: Check your master repository and work repository.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10229: Repository with id ''{0}'' has been already used in your master repository.

Cause: Master repository has already work repository with the same id.

Action: Check your master repository and work repository.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10230: Repository with name ''{0}'' has been already used in your master repository.

Cause: Master repository has already work repository with the same name.

Action: Check your master repository and work repository.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10231: Interface {0} cannot be imported because source temporary interface / mapping {1} is not found.

Cause: An attempt was made to import an interface with a source temporary interface / mapping that cannot be found in the import source or target repository.

Action: Import the missing source temporary interface / mapping.
Level: 32

Type: ERROR

Impact: Other

ODI-10232: The password violates the following rule: "New password must be different from old one". Select another password.

Cause: Weak password

Action: Check password policy and correct password.
Level: 32

Type: ERROR

Impact: Security

ODI-10234: Object cannot be imported since it contains non XML files

Cause: ZipFolder to be imported should not contain non XML files

Action: Check ZipFolder to be imported
Level: 32

Type: ERROR

Impact: Other

ODI-10235: No Importable files found

Cause: None of XML files imported from ZipFolder

Action: Check XML files to be imported from Zip Folder
Level: 32

Type: ERROR

Impact: Other

ODI-10236: Object must be replaced with an object of same KM type

Cause: KM of different type to the existing KM was selected for import replace.

Action: Import Replace KM with existing KM type
Level: 32

Type: ERROR

Impact: Other

ODI-10237: Object not replaced

Cause: A KM was selected for the Import Replace with a different type to the current KM.

Action: Select a KM of the same type for import replace.
Level: 32

Type: WARNING

Impact: Other

ODI-10238: Object must be replaced with an object of same type

Cause: Different ODI object is used to Import Replace KM

Action: Import Replace KM with Same type
Level: 32

Type: ERROR

Impact: Other

ODI-10239: Importing file "{0}"...

Cause:

Action:
Level: 32

Type: NOTIFICATION

Impact: Files

ODI-10240: Updating dataservers...

Cause:

Action:
Level: 32

Type: NOTIFICATION

Impact: Topology

ODI-10241: Removing Error Tables for Physical Schema with id '{0}'

Cause:

Action:
Level: 32

Type: NOTIFICATION

Impact: Topology

ODI-10242: Removing Error Table "{0}"

Cause:

Action:
Level: 32

Type: NOTIFICATION

Impact: Topology

ODI-10243: Cannot import an export file with parents using regular import and INSERT_UPATE mode. Use smart import instead.

Cause: An attempt was made to import an export file created with parent objects using regular import and INSERT_UPATE mode. This would cause all other objects under the parent objects and not in the import file to be deleted.

Action: Use smart import to import an export file created with parent objects when INSERT_UPDATE functionality is needed.
Level: 32

Type: ERROR

Impact: Other

ODI-10244: Cannot import {0} {1} (with global id: {2} and internal id: {3}) because referenced {4} with global id {5} does not exist.

Cause: The referenced object for a foreign key cannot be found in order to set the reference and a missing reference cannot be created.

Action: Import the missing referenced object before importing the referencing object.
Level: 32

Type: ERROR

Impact: Other

ODI-10245: Cannot import {0} {1} (with global id: {2} and internal id: {3}) belonging to {4} {5} (with global id: {6} and internal id: {7}) because its referenced object is not found in the target repository.

Cause: The object was imported in a SYNONYM UPDATE mode and the referenced object was not found in the repository.

Action: Change the import mode to INSERT_UPDATE or import the file twice first in INSERT MODE and then in UPDATE mode.
Level: 32

Type: ERROR

Impact: Other

ODI-10246: No Exportable objects found in the repository.

Cause: No objects are present in the repository for export

Action: Create repository objects
Level: 32

Type: ERROR

Impact: Other

ODI-10247: Specified project {0} does not exist in the repository.

Cause: The repository did not contain the specified project.

Action: Choose another project or create the project with the specified name.
Level: 32

Type: ERROR

Impact: Other

ODI-10248: {0} : Not an ODI special driver.

Cause: Invalid Special driver.

Action: Check that this technology is part of the special driver list.
Level: 32

Type: ERROR

Impact: Other

ODI-13000: Invalid Directory Path specified - {0}

Cause: Invalid directory path. Either the path does not exist or is not a directory

Action: Provide valid directory path
Level: 32

Type: ERROR

Impact: Other

ODI-13001: Error Fetching Objects From File

Cause: Error Fetching Objects From File

Action: Check The File
Level: 32

Type: ERROR

Impact: Other

ODI-13002: Error Fetching Objects From Subversion

Cause: Error Fetching Objects From Subversion

Action: Check The Repository
Level: 32

Type: ERROR

Impact: Other

ODI-13003: Error Fetching Objects From Folder

Cause: Error Fetching Objects From Folder

Action: Check Either the path does not exist or is not a directory
Level: 32

Type: ERROR

Impact: Other

ODI-13005: Error Listing Branches From VCS

Cause: Error Listing Branches From VCS

Action: Check The Repository
Level: 32

Type: ERROR

Impact: Other

ODI-13006: Error Exporting Objects To Memory

Cause: Error Exporting Objects To Memory

Action: Check The Object List
Level: 32

Type: ERROR

Impact: Other

ODI-13007: Error Creating Temp Dir

Cause: Error Creating Temp Dir

Action: Check The Path / Permission
Level: 32

Type: ERROR

Impact: Other

ODI-13008: Error Listing NonEmpty Branches From Version Control System

Cause: Error Listing NonEmpty Branches From Version Control System

Action: Check The Repository
Level: 32

Type: ERROR

Impact: Other

ODI-13009: Error Listing NonEmpty Tags From Version Control System

Cause: Error Listing NonEmpty Tags From Version Control System

Action: Check The Repository
Level: 32

Type: ERROR

Impact: Other

ODI-13010: Error querying merge objects

Cause: Error Fetching SnpObjects

Action: Check The Repository
Level: 32

Type: ERROR

Impact: Other

ODI-13011: An in progress merge already exists. Only one in progress merge is allowed at a time.

Cause: A different in progress merge already exists

Action: Complete the merge that is in progress before attempting to start another merge.
Level: 32

Type: ERROR

Impact: Other

ODI-13012: In progress merge objects still exist for the merge. All merge objects must be complete before merge status can be set to complete.

Cause: In progress merge objects still exist for the merge

Action: Complete the merge for all in progress merge objects in order to complete the merge.
Level: 32

Type: ERROR

Impact: Other

ODI-13700: Unable to set the role OWB_USER for this user.

Cause: An attempt was made to set the role OWB_USER for the connected user.

Action: Check that the role exists and the connected user is an OWB user.
Level: 1

Type: ERROR

Impact: Other

ODI-13701: Unable to set the workspace {0} for this user.

Cause: An attempt was made to select the OWB workspace for the connected user.

Action: Check that the workspace exists and the connected user has got privilege to access it.
Level: 1

Type: ERROR

Impact: Other

ODI-13702: Unexpected error when connecting to OWB workspace {0}.

Cause: An unexpected error occurred when connecting to workspace.

Action: Verify that the Owb repository is up and running.
Level: 1

Type: ERROR

Impact: Other

ODI-13703: Unexpected error when locating object {0} in OWB workspace {1}.

Cause: An unexpected error occurred when locating an object in a workspace

Action: Verify that the Owb repository is up and running and the object exists.
Level: 1

Type: ERROR

Impact: Other

ODI-13704: Could not locate the physical schema associated with OWB workspace {0} in context {1}.

Cause: An error occurred when finding the schema related to an OWB workspace in a context.

Action: Verify that the OWB workspace is related to a physical schema in the context.
Level: 1

Type: ERROR

Impact: Other

ODI-13800: Cannot locate the monitor configuration file: {0} using JVM argument: {1}={2} or the environment variable: {3}={4}.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Configuration

ODI-13801: Cannot locate the monitor configuration file at: {0}.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Configuration

ODI-13802: Cannot access the monitor configuration file: {0}.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Configuration

ODI-13803: The contents of the monitor configuration file: {0} are invalid.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Configuration

ODI-13804: The runtime performance monitoring has been turned off due to invalid monitor configuration.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Configuration

ODI-13805: An error occured while updating the monitor status for the Agent:{0}, Master repository external id:{1}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13806: An error occurred while starting the pre execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13807: An error occurred while stopping the pre execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13808: An error occurred while starting the request processing monitor for Agent={0}, Master repository external id={1}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13809: An error occurred while stopping the request processing monitor for Agent={0}, Master repository external id={1}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13810: An error occurred while starting the execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13811: An error occurred while stopping the execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13812: An error occurred while starting the post execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13813: An error occurred while stopping the post execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13814: An error occurred while starting the Scenario execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13815: An error occurred while stopping the Scenario execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13816: An error occurred while starting the Step execution monitor for Agent={0}, Scenario={1}, Step={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13817: An error occurred while stopping the Step execution monitor for Agent={0}, Scenario={1}, Step={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13818: An unexpected error occurred while starting the entity monitor for entity={0}, agent={1}, master repository external id={2}, session id={3}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13819: An unexpected error occurred while updating the entity monitor for entity={0}, agent={1}, master repository external id={2}, session id={3}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13820: An unexpected error occurred while starting the entity monitor for entity={0}, agent={1}, master repository external id={2}, session id={3}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13821: An error occurred while registering the Agent Discovery Mbean, mbeanName={0}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13822: An error occurred while de-registering the Agent Discovery Mbean, mbeanName={0}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13823: Could not find the Server MBean for server {0} on platform {1}.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-14000: Importing Object

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14001: Importing Profile

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14002: Importing User

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14003: Importing InstObj

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14004: Importing Local Repository

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14005: Importing Techno

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14006: Importing Data Types

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14007: Importing Data Types Conversions

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14008: Importing Language

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14009: Importing Open Tools

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14010: Importing Pwd Policies

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14011: Importing Pwd Rule

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14012: Importing Connection

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14013: Importing Agent

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14014: Importing LBAgent

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14015: Importing Logical Agent

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14016: Importing Context

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14017: Importing Pschema

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14018: Importing Lschema

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14019: Importing Entity

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14020: Importing Link

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14021: Importing Field

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14022: Importing FieldLook Up

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14023: Importing Look Up

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14024: Importing Look Up Value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14025: Importing Action

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14026: Importing Action Group

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14027: Importing Version

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14028: Importing Solutions

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14029: Cleaning connections

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14030: Importing:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other{0}

ODI-14031: Importing Session

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14032: Importing Global Sequences

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14033: Importing Global Variables

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14034: Importing Global User Functions

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14035: Importing Global Group of States

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14036: Importing Model Folders

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14037: Importing Models

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14038: Importing Scenario folders

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14039: Importing Projects

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14040: Importing Scenario

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14041: Importing Folders

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14042: Importing Packages

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14043: Importing Interfaces

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14044: Importing Procedures

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14045: Importing Knowledge Modules

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14046: ODI Master Repository Upgrade: Upgrading Repository Structure...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14047: ODI Master Repository Upgrade: Upgrading Repository Data...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14048: ODI Master Repository Upgrade: Done.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14049: Master repository creation is successful.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14050: ODI Work Repository Attach: Attaching Repository...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14051: ODI Work Repository Attach: Done.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14052: ODI Work Repository Upgrade: Upgrading Repository Structure...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14053: ODI Work Repository Upgrade: Upgrading Repository Data...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14054: ODI Work Repository Upgrade: Done.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14055: Work repository creation is successful.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14056: Importing SubModels

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14057: Importing Tables

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14058: End importing {1}. Import time (milliseconds): {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14059: End importing {1}. Import time (hh:mm:ss): {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14060: End importing {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14061: Master repository already up to date nothing to do.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14062: Upgrading master repository from {0} to {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14063: Applying DDL from file {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14064: Error while applying DDL from file {0}

Cause: Exception during execution of session.

Action: Check session.
Level: 32

Type: ERROR

Impact: Other

ODI-14065: Work repository already up to date. Nothing to do.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14066: upgrade error while executing {0} params = {1}

Cause: Wrong parameters at Sql query.

Action: Check parameters.
Level: 32

Type: ERROR

Impact: Upgrade

ODI-14067: Exporting {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14068: End exporting {1}. Export time (milliseconds): {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14069: End exporting {1}. Export time (hh:mm:ss): {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14070: Import failed. The parent object was not found in the repository.

Cause: The object was imported in a SYNONYM mode and the parent object was not found in the repository.

Action: Change the import mode or restore the parent object in the repository
Level: 32

Type: ERROR

Impact: Other

ODI-14071: Getting Dependencies

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14072: End getting dependencies. Time (milliseconds): {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14073: End getting dependencies. Time (hh:mm:ss): {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14074: Parent folder already has the release tag set.

Cause: Setting the release tag when the parent already has the release tag set.

Action: Set the release tag in parent.
Level: 32

Type: ERROR

Impact: Other

ODI-14075: Seed data for property missing.

Cause: Seed data for property {0} is missing.

Action: Contact Oracle Support Services
Level: 32

Type: ERROR

Impact: Other

ODI-14077: Importing Mappings/Reusable Mappings

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14078: Importing Mapping Component Types

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14079: Importing Enterprise Scheduler

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14080: Importing Enterprise Principals

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14081: User Function syntax is not unique.

Cause: Work repository already has User Function with the same syntax.

Action: Check your user function syntax.
Level: 32

Type: ERROR

Impact: Other

ODI-14082: Folder or sub-folder name is not unique.

Cause: Duplicate folder name. Folder with the same name already exists in this project/folder.

Action: Choose another folder name.
Level: 32

Type: ERROR

Impact: Other

ODI-14083: Profile name is not unique.

Cause: Profile with the same name already exists.

Action: Check your profile name.
Level: 32

Type: ERROR

Impact: Other

ODI-14084: Diagram name is not unique.

Cause: Diagram with the same name already exists.

Action: Check your diagram name.
Level: 32

Type: ERROR

Impact: Other

ODI-14085: Object cannot be Imported since it contains non XML file

Cause: Folder to be imported should not contain non XML files

Action: Check Folder to be imported
Level: 32

Type: ERROR

Impact: Other

ODI-14086: Begin importing: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14087: Total Time For Import (before Upgrade of Interfaces) : {0} (milliseconds)

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14088: Total Time For Import (before Upgrade of Interfaces) : {0} (hh:mm:ss)

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14089: Total Time for Import:{0} (milliseconds)

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14090: Total Time for Import: {0} (hh:mm:ss)

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14091: Work repository is already attached to another master repository.

Cause: Attempt to attach already attached work repository was made while work repository can be attached to only one master repository at the moment.

Action: Work repository should be first detached from the master repository it is attached to at the moment.
Level: 32

Type: ERROR

Impact: Other

ODI-14092: Loading Master Repository Info

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14093: Cannot Connect To Master Repository

Cause: Cannot Connect To Master Repository

Action: Check your connection settings or database
Level: 32

Type: ERROR

Impact: Other

ODI-14094: Master Repository Is In Invalid State.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14095: Master Repository Already Up To Date.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14096: Error While Upgrading Master Repository {0}

Cause: Exception caught while upgrading Master Repository

Action: Please check the Logs.
Level: 32

Type: ERROR

Impact: Other

ODI-14097: Importing Technology Seed Data

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14098: Error While Importing Technology Seed Data {0}

Cause: Exception caught while importing technology Seed Data

Action: Please check the logs
Level: 32

Type: ERROR

Impact: Other

ODI-14099: Scanning Export Files

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14100: Loading Technology

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14101: Checking for Pre 4.3.3.2 Version

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14102: Upgrading To Master Repository Till 4.3.3.2 Version

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14103: Upgrading Master Repository Post 4.3.3.2 Version

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14104: Reimporting Metadata

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14105: Reimporting Security Seed Data

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14106: Getting Work Repositories

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14107: Found {0} Work Repositories to Upgrade

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14108: Upgrading {0} Work Repository

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14109: Cannot Connect To Work Repository

Cause: Cannot Connect To Work Repository {0}

Action: Check your connection settings or database
Level: 32

Type: ERROR

Impact: Other

ODI-14110: Work Repository {0} Is In Invalid State.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14111: Work Repository Already Up To Date.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14112: Converting All Interface to Mapping

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14113: Work repository is already attached to the master repository.

Cause: Attempt to attach already attached work repository was made.

Action: Please do not attach the work repository again to the master repository.
Level: 32

Type: ERROR

Impact: Other

ODI-14114: Incorrect wallet password.

Cause: Provided wallet password is incorrect.

Action: Please enter correct wallet password.
Level: 32

Type: ERROR

Impact: Security

ODI-14115: Wallet file is not found at specified location : {0}

Cause: Wallet file is not present in $HOME/.odi/oracledi/ewallet directory.

Action: Please check wallet file is present at specified location.
Level: 32

Type: ERROR

Impact: Security

ODI-14116: No registry database provided

Cause: Registry database not provided.

Action: Please provide registry database.
Level: 32

Type: ERROR

Impact: Other

ODI-14117: No repository database in URL: {0}

Cause: Repository database missing from the jdbc url.

Action: Please provide repository database in the jdbc url.
Level: 32

Type: ERROR

Impact: Other

ODI-14118: Not a valid jdbc mysql url: {0}

Cause: Invalid JDBC mysql url

Action: Please provide a valid jdbc url.
Level: 32

Type: ERROR

Impact: Other

ODI-14119: The selected database was released after this version of Oracle Fusion Middleware. For the most recent list of certified databases, refer to the Supported System Configurations information on the Oracle Technology Network.

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14120: The database you are connecting is not a supported version. refer to the certification matrix for supported DB versions.

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14121: The selected Oracle Database 11g Release 2 instance is not certified with this version of Oracle Fusion Middleware. Oracle Fusion Middleware 12c requires Oracle Database 11g Release 2 (11.2.0.3) or higher. For the latest list of certified databases, refer to the Supported System Configurations information on the Oracle Technology Network.

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14122: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 10.5.3.0. Refer to the certification matrix for supported DB versions

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14123: DB Init Param Prerequisite failure for innodb_file_format. Its value should be 'Barracuda'.

Cause: INNODB_FILE_FORMAT value is not 'Barracuda'.

Action: Refer to the certification matrix for supported DB init parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-14124: The selected MySQL instance is not certified with this version of Oracle Fusion Middleware. Oracle Fusion Middleware 12c requires MySQL 5.5.14 or higher. For a list of certified databases, refer to the Supported System Configurations information on the Oracle Technology Network.

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14125: DB Init Param Prerequisite failure for innodb_file_per_table. Its value should be 'ON'

Cause: INNODB_FILE_PER_TABLE value is not 'ON'

Action: Refer to the certification matrix for supported DB init parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-14126: DB Init Param Prerequisite failure for innodb_large_prefix. Its value should be 'ON'.

Cause: INNODB_LARGE_PREFIX value is not 'ON'

Action: Refer to the certification matrix for supported DB init parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-14127: DB Init Param Prerequisite failure for log_bin_trust_function_creators. Its value should be 'ON'.

Cause: log_bin_trust_function_creators value is not 'ON'

Action: Refer to the certification matrix for supported DB init parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-14128: The selected Oracle database is a multitenant container database (CDB). Connecting to a multitenant container database (CDB) is not supported. Instead, connect to a valid pluggble database (PDB).

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14129: The selected Oracle Database 12c instance is not certified with this version of Oracle Fusion Middleware. Oracle Fusion Middleware 12c requires Oracle Database 12c (12.1.0.1) or higher. For a list of certified databases, refer to the Supported System Configurations information on the Oracle Technology Network

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14130: The selected Oracle Database 11g Release 1 or Oracle Database 10g instance is not certified with this version of Oracle Fusion Middleware. Oracle Fusion Middleware 12c requires Oracle Database 10g (10.2.0.4) or higher or Oracle Database 11g Release 1 (11.1.0.7) or higher. For the latest list of certified databases, refer to the Supported System Configurations information on the Oracle Technology Network.

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14131: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 2008 R2. Refer to the certification matrix for supported DB versions.

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14132: The selected IBM DB2 instance is not certified with this version of Oracle Fusion Middleware. Oracle Fusion Middleware 12c requires IBM DB2 9.7 or higher in 9 series and IBM DB2 10.1 FP2 or higher in 10 series. For a list of certified databases, refer to the Supported System Configurations information on the Oracle Technology Network.

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14133: User should have sysdba or dba privilages.

Cause: User does not have sysdba or dba privilages

Action: Grant user sysdba or dba privilages.
Level: 32

Type: ERROR

Impact: Other

ODI-14134: The selected Oracle database is not configured to use the AL32UTF8 character set. Oracle strongly recommends using the AL32UTF8 character set for databases that support Oracle Fusion Middleware.

Cause: The database you are connecting is with non-AL32UTF8 character set

Action: Use AL32UTF8 as the database character set.
Level: 32

Type: ERROR

Impact: Other

ODI-14136: Database does not match the requirement.

Cause: Database validation failed

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14137: Error occurred while validating database {0}.

Cause: Database validation failed

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14138: Could not perform validation of the database.Please check the database user privileges.

Cause: Database validation failed

Action: Check if database user has sufficient privileges or required table/view/file exist .
Level: 32

Type: NOTIFICATION

Impact: Other

ODI-14139: Encryption Standard is not set in Master Repository.

Cause: Master Repository configured with invalid or no Encryption Standard.

Action: Set the Encryption Standard to be used in the Master Repository, with valid value for algorithm ('AES') and key-length ('128' / '256').
Level: 32

Type: ERROR

Impact: Security

ODI-14140: Master key data is not set in Master Repository

Cause: Master Repository does not have the master key data.

Action: Set the Master key data to be used in the Master Repository.
Level: 32

Type: ERROR

Impact: Security

ODI-14141: The provided key is not matching the key-specification. Key must : be of length 8-100, contain at least one alphabet (lower/uppercase), contain at least one numeric-digit (or) a special-character from: [@ # $ % + / =].

Cause: The provided key is not matching the key-specification.

Action: Provide key that matches the key-specification
Level: 32

Type: ERROR

Impact: Security

ODI-14142: The Security Policy currently in force, does not allow the use of AES-256.

Cause: The Security Policy in force does not allow using AES-256 Encryption Standard.

Action: To use AES-256, please replace the security policy files in JRE_HOME/lib/security, with Unlimited Strength Policy Files available at Java SE downloads at http://www.oracle.com/technetwork/java. Refer Java SE documentation for more information.
Level: 32

Type: ERROR

Impact: Security

ODI-14143: Encryption Standard persisted in master repository is not AES-128 or AES-256.

Cause: The Encryption Standard configured in the repository is not supported.

Action: Edit the master repository configuration to set the Encryption Standard as AES-128 or AES-256.
Level: 32

Type: ERROR

Impact: Security

ODI-14144: An Error occurred while parsing the ODI Tool Command

Cause: An error occurred while parsing the ODI Tool Command text.

Action: Refer to stack trace for more details.
Level: 32

Type: ERROR

Impact: Security

ODI-14145: An Error occurred while setting parameter {0} in ODI Tool Command.

Cause: Unable to set parameter in ODI Tool Command.

Action: Refer to stack trace for more details.
Level: 32

Type: ERROR

Impact: Security

ODI-14146: Incorrect Export Key

Cause: The Export Key provided is incorrect for the import source

Action: Provide a valid Export Key that was used during Export of object
Level: 32

Type: ERROR

Impact: Security

ODI-14147: An error occurred while migrating cipher text in object {0} - ''{1}'' (with Internal ID: {2} and Global ID: {3})

Cause: Invalid Cipher content or Invalid Export Key

Action: If exporting, check if the cipher data present in the object is correct. If importing, check if Export Key is correct.
Level: 32

Type: ERROR

Impact: Security

ODI-14148: An Error occurred while creating Cipher for migration.

Cause: An error occurred while creating ODI Cipher.

Action: Refer to stack trace for more details
Level: 32

Type: ERROR

Impact: Security

ODI-14149: Invalid Encoder/Decoder for Cipher Text Migration.

Cause: The ODI Encoder/Decoder is invalid.

Action: Create valid Encoder/Decoder for Cipher Text Migration.
Level: 32

Type: ERROR

Impact: Security

ODI-14150: An Error occurred while migrating password cipher text

Cause: An error occurred while migrating the password cipher text

Action: Refer to stack trace for more details
Level: 32

Type: ERROR

Impact: Security

ODI-14151: An error occurred while retrieving parameters from ODI Tool Command.

Cause: Invalid ODI Tool Command.

Action: Check ODI Tool Command text.
Level: 32

Type: ERROR

Impact: Security

ODI-14152: Package name is not unique.

Cause: Duplicate package name. Package with the same name already exists in this folder.

Action: Choose another package name.
Level: 32

Type: ERROR

Impact: Other

ODI-14153: Procedure name is not unique.

Cause: Duplicate procedure name. Procedure with the same name already exists in this folder.

Action: Choose another procedure name.
Level: 32

Type: ERROR

Impact: Other

ODI-14154: Context name is not unique.

Cause: Context with the same name already exists.

Action: Check your context name.
Level: 32

Type: ERROR

Impact: Other

ODI-14155: Context code is not unique.

Cause: Context with the same code already exists.

Action: Check your context code.
Level: 32

Type: ERROR

Impact: Other

ODI-14156: KM name is not unique.

Cause: Duplicate KM name. KM with the same name already exists.

Action: Choose another KM name.
Level: 32

Type: ERROR

Impact: Other

ODI-14157: Procedure option name is not unique.

Cause: Duplicate procedure option name. Procedure option with the same name already exists.

Action: Choose another procedure option name.
Level: 32

Type: ERROR

Impact: Other

ODI-14158: A Supervisor user can be updated only by another Supervisor user.

Cause: The logged-in user is not a Supervisor user, but trying to update another Supervisor user.

Action: Login as a user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-14159: An error occurred while validating the Export Key.

Cause: An error occurred while validating the export key

Action: Please check the Logs
Level: 32

Type: ERROR

Impact: Security

ODI-14160: Skipping Data migration on IP Text {0} . Failed with Exception : {1} . Please fix manually.

Cause: An error occurred while migrating the password cipher text

Action: Refer to Error Message for more details
Level: 32

Type: ERROR

Impact: Security

ODI-14161: Duplicate name objects are found in the repository. Please check the upgrade log file.

Cause: Some objects with same names are under same parents

Action: Check the log file for the duplicate name objects. Remove them before upgrade
Level: 32

Type: ERROR

Impact: Other

ODI-14162: User cannot login ODI with blank password. Please contact SUPERVISOR to reset the password.

Cause: User cannot login ODI with blank password. Please contact SUPERVISOR to reset the password.

Action: Please contact SUPERVISOR to reset the password.
Level: 32

Type: ERROR

Impact: Security

ODI-14163: User cannot create master repository through import with blank supervisor password.

Cause: User cannot create master repository through import with blank supervisor password.

Action: Please provide valid supervisor password to the API while create master repository thorugh import.
Level: 32

Type: ERROR

Impact: Security

ODI-14164: Work repository name must not be null or empty

Cause: Work repository name is null or empty.

Action: Check Work repository name.
Level: 32

Type: ERROR

Impact: Other

ODI-14165: The repository is currently locked for sync operation and cannot be modified

Cause: User cannot make any changes as repository is locked for sync.

Action: Please try after some time.
Level: 32

Type: ERROR

Impact: Repository

ODI-14166: Importing Project Marker Groups

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14167: Importing Project Sequences

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14168: Importing Project Variables

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14169: Importing Project User Functions

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14170: Importing Project Knowledge Modules

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14171: Importing Project Reusable Mappings

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14172: Importing Project Mappings

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14173: The repository is for {0} so you cannot connect to this repository from {1}.

Cause: Repository is not valid for the invoking application.

Action: Connect to this repository use the proper application.
Level: 32

Type: ERROR

Impact: Security

ODI-14174: You are using Oracle Golden Gate Studio which only supports internal authentication mode. But the repositgory is in external authentication mode which cannot be used for Oracle Golden Gate Studio.

Cause: The repository is in external authentication mode and it is not valid for Oracle Golden Gate Studio since Oracel Golden Gate Studio only supports internal authentication mode. One possibility could be that this repository is for Oracle Data Integrator.

Action: Connect to a different repository.
Level: 32

Type: ERROR

Impact: Security

ODI-14175: Cannot delete this user since it is the last supervisor user.

Cause: You are trying to delete the last supervisor user which cannot deleted.

Action: Create another user and make it supervisor user and then you can delete this supervisor user.
Level: 32

Type: ERROR

Impact: Security

ODI-14176: Password cannot be empty for accessing the MBean Server, which is used for External Password Storage.

Cause: Password is empty for the accessing the MBean Server.

Action: Provide MBean server password.
Level: 32

Type: ERROR

Impact: Security

ODI-14177: The external user: {0} does not exist in ODI repository and also has no ODI role granted. The GUID of the user : {1}

Cause: The specified external user does not exists in ODI repository and has no ODI role granted.

Action: Add the external user in ODI repository or grant required ODI roles to the user.
Level: 32

Type: ERROR

Impact: Security

ODI-14178: Schema name and Catalog name is not unique for the dataserver {0}

Cause: Duplicate physical schema. Physical Schema with the same schema name and catalog name already exists for this dataserver.

Action: Choose another schema name and/or catalog name.
Level: 32

Type: ERROR

Impact: Other

ODI-14179: For security reasons, you cannot use odiRef.getJDBCConnection("WORKREP"), since your Work Repository and Master Repository use the same database schema. Please contact your Oracle Data Integrator Administrator to grant you <Create JDBC Connection> permission on Master Repository object from Oracle Data Integrator Studio Security Explorer and try again. Please note that the <Create JDBC Connection> permission is located under Master Repository object in the Objects section from Security Explorer. You can give the permission to a user, say User1, by 1) drag and drop it to the user User1 2) then mark the newly granted permission as Generic Privilege: the newly granted permission <Create JDBC Connection> will be under the tree node User1/Objects/Master Repository, open the editor of the granted permission and select the check box named <Generic Privilege>.

Cause: The Work Repository and Master Repository use same database schema and you do not have the required permission granted.

Action: Please contact your Oracle Data Integrator Administrator to grant you <Create JDBC Connection> permission on Master Repository object from Oracle Data Integrator Studio Security Explorer and try again. Or you also can re-create your Master and Work repositories in different database schema. Please note that the <Create JDBC Connection> permission is located under Master Repository object in the Objects section from Security Explorer. You can give the permission to a user, say User1, by 1) drag and drop it to the user User1 2) then mark the newly granted permission as Generic Privilege: the newly granted permission <Create JDBC Connection> will be under the tree node User1/Objects/Master Repository, open the editor of the permission and select the check box named <Generic Privilege>.
Level: 32

Type: ERROR

Impact: Other

ODI-14180: {0}. Data migration is skipped for URL : {1}

Cause: The format of the URL is incorrect or the URL contains invalid properties.

Action:
Level: 32

Type: WARNING

Impact: Upgrade

ODI-14181: Upgrading Converson Datatype Global Ids

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14182: Error While Upgrading Conversion Datatype Global Ids {0}

Cause: Exception caught while upgrading conversion datatype (SnpConvDt) Global Ids

Action: Please check the logs
Level: 32

Type: ERROR

Impact: Other

ODI-15000: BSF Not Present

Cause: Bean Scripting Framework manager cannot be found.

Action: Ensure that class org.apache.bsf.BSFManager is available in the classpath.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15001: No End Separator for the following text:

Cause: No end delimiter found for a delimited text in the expression.

Action: Add an end delimiter to the delimited text.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15002: The string to be transformed cannot be null.

Cause: Parsing failed for an expression reference tag.

Action: Fix the expression.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15003: Error during Code Interpretor creation

Cause: Code generator internal error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15005: The datatype "{0}" does not exist in technology: {1}.

Cause: The datatype for a column is not supported by the technology.

Action: Change the datatype or the technology of the execution location.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15006: The source datatype is null for the column: {0}, and the technology: {1}

Cause: The datatype for a column is null for the technology.

Action: Change the datatype or the technology of the execution location.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15007: Syntax not set for 'Create Table' for the datatype: {0} for the technology: {1}.

Cause: The execution location technology does not have any "Create Table" syntax set up.

Action: Edit the technology definition and add "Create Table" syntax.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15009: No text for the 'Writable Datatype Syntax' for the datatype: {0} in technology: {1}

Cause: The datatype does not have a "Writable Datatype Syntax" property value set up for the execution location technology.

Action: Edit the datatype in the technology to add a "Writable Datatype Syntax".
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15010: No conversion for the datatype {0}, for the source technology {1} and for the target technology {2}

Cause: No conversion is defined for the source technology datatype to the target technology datatype.

Action: Edit the source or target technology datatype to add a conversion from the source to the target datatype.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15011: The variable does not exist in the database.

Cause: A variable is being referenced but it does not exist in the repository.

Action: Create the variable in the repository.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15012: Sequence does not exist in database

Cause: A sequence is referenced but does not exist in the repository.

Action: Create the sequence in the repository.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15013: The table {0} has fatal errors.

Cause: The table cannot be processed.

Action: Check the table for inconsistencies.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15014: The referenced text does not exist in the database.

Cause: The text reference in the expression does not exist in the repository.

Action: Repository corruption has occurred, contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15015: Too much recursion in this text resolution.

Cause: The expression text references other text recursively too many times.

Action: Review the expression and try to simplify.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15016: Commands Undefined.

Cause: KM is missing a block of lines.

Action: Check the KM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15017: Table not selected (null).

Cause: Target table not found.

Action: Check interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15018: CKM not selected.

Cause: The CKM is not selected for the object.

Action: Select a CKM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15019: Missing context

Cause: The context object cannot be found.

Action: Check the context selection.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15020: No JKM available

Cause: JKM has not been set or is not found.

Action: Set a valid JKM for the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15021: Journalizing requires a Primary Key on the Table:

Cause: Journalizing is enabled, but the target table has no primary key.

Action: Add a primary key to the target table.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15022: No RKM Set.

Cause: RKM has not been set or is not found.

Action: Set a valid RKM for the object.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15023: Cannot perform standard reverse. Choose customized reverse and set RKM.

Cause: Standard reverse engineering is not supported for this object.

Action: Select customized reverse engineering for the object and select an RKM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15025: The interface clause text does not exist.

Cause: The interface clause refers to text that does not exist.

Action: Check interface clauses for (join, filter, etc.) for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15026: Interface clauses are missing.

Cause: The code generator cannot find the clause collection for the interface.

Action: Check the interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15027: Interface source tables are missing.

Cause: The code generator cannot find the source table collection for the interface.

Action: Check the interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15028: Interface result collection is null.

Cause: Internal error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15029: Interface error clause collection is missing.

Cause: Internal error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15030: Interface is missing the integration work table collection.

Cause: Internal error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15031: Technology not selected.

Cause: No technology is selected for the interface target execution location.

Action: Check the technology selection for the interface target.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15032: Unknown object in interface source table collection

Cause: Internal Error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15033: The expression: {0} does not have an associated column.

Cause: The expression should represent a column, but no column is found for the name.

Action: Fix the expression.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15034: A scenario with the same name and the same number already exists. Please select other values.

Cause: Cannot create a duplicate scenario with the same name and version number as an existing scenario.

Action: Give the scenario a different name or version.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15036: Scenario''s name and/or number are missing.

Cause: A scenario must have a name and version, but the name or version is missing.

Action: Set values for name and version for the scenario.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15037: The interface {0} has fatal errors.

Cause: The interface has fatal errors.

Action: Check and fix interface issues.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15038: The scenario name substitution pattern {0} is not supported. Please check the user parameter for the scenario naming convention.

Cause: Invalid substitution pattern used for scenario name.

Action: Change the substitution pattern.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15039: The interface {0} use native sequence. Native sequence are not allowed for Derived Table (sub select statement)

Cause: Native sequence was used in a sub-select or derived interface.

Action: Remove the native sequence usage.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15040: Errors detected when building SQL clauses.

Cause: An error occurred when generating code for the SQL clauses.

Action: Fix the interface clauses.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15041: An aggregation function may not be used in a join condition. Please use a separate interface for the aggregation and join the result in this interface.

Cause: An aggregation function was used inside a join condition expression.

Action: Change the join condition to remove the aggregation function.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15042: Unable to regenerate this scenario. It references an package that does not exist.

Cause: The scenario must reference a package, but it doesn't.

Action: Delete the scenario and create a new one.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15043: Unable to regenerate this scenario from a Runtime repository.

Cause: The scenario must cannot be regenerated from the runtime repository.

Action: Delete the scenario and create a new one.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15044: Invalid pScenSource type when calling SnpGeneratorSQLCIT.mainGenScenSourceScenario

Cause: Internal error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15045: Invalid value for KM type.

Cause: An invalid value was specified for the KM type.

Action: Specify a valid value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15046: The column cache is null during code generation.

Cause: Internal Error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15047: The cached column is null in the column cache during code generation.

Cause: Internal Error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15050: Flow Control not possible if no key is declared in your target datastore

Cause: Flow control is enabled for the interface, but the target datastore has no primary key defined.

Action: Define a primary key for the target datastore object, and re-add the target datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15051: Missing mapping instance for interface.

Cause: The target column does not have any mapping.

Action: Add a mapping expression for the target column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15052: The interface is missing a dataset.

Cause: There is no dataset for the interface source.

Action: Check the interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15054: Scenario generation error: Cannot regenerate the scenario. The physical mapping design used to generated the scenario is not found.

Cause: The physical mapping design used to generated the scenario is not found.

Action: Choose to create or replace the scenario.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15055: Character '']'' missing in: {0}.

Cause: A bracketed tag inside a KM line is missing a closing bracket ("]") character.

Action: Fix the KM line.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15057: Non-ordered outer join not supported for technology.

Cause: Non-ordered outer join syntax disabled for technology.

Action: Correct join.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15058: Variable scenario generation error: Logical schema is required.

Cause: Variable scenario cannot be generated if logical schema is not set.

Action: Set the logical schema.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15059: I_TXT is mandatory.

Cause: A call was made to SnpTxtCachedHashMap.getInstance, but the pITxt parameter was null.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15060: The JKM line {0} uses an unsupported execution channel: {1}

Cause: A line in the JKM uses an execution channel that is not supported.

Action: Change the line in the JKM to use a supported channel.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15061: The JKM line {0} uses an unsupported commit type: {1}

Cause: A line in the JKM uses a commit type that is not supported.

Action: Change the line in the JKM to use a supported commit type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15062: Invalid commit type: {0}

Cause: An invalid commit type was passed to SnpServiceGenerator.convertCommitType

Action: Contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15063: The alternate key {0} is not unique.

Cause: An alternate key defined by the repository is found to be non-unique.

Action: Check the data or the alternate key definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15064: The primary key {0} is not unique.

Cause: A primary key defined by the repository is found to be non-unique.

Action: Check the data or primary key definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15065: Join error ({0}) between the table {1} and the table {2}.

Cause: A foreign key relationship is not found.

Action: A foreign key relationship between 2 tables defined in the repository is not valid.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15066: The column {0} cannot be null.

Cause: The column is marked in the repository as not nullable.

Action: Check the data, or change the not null value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15067: The datatype value ''{0}'' is incorrect.

Cause: An invalid datatype has been found.

Action: The repository table contains an invalid datatype.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15068: Unknown flexfield code {0}.

Cause: An undefined flex field code is being referenced

Action: Check the flex field references in the KM, and the flex field definitions
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15069: {0} Is not valid without session context.

Cause: A current session context does not exist.

Action: Check session definition.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15070: Unable to find method object: PythonInterpreter.initialize(Properties, Properties, String[]) method

Cause: The python method used by the script is not found.

Action: Check the KM step.
Level: 32

Type: ERROR

Impact: Other

ODI-15071: Error occurred

Cause: An exception was thrown while executing a python script in the KM step.

Action: Check the cause.
Level: 32

Type: ERROR

Impact: Other

ODI-15072: There is no PK constraint

Cause: There is a call to "getPK" in the KM, but no PK is found.

Action: Check the KM and the PK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15073: There is no index

Cause: There is a call to "getIndex" in the KM, but no index is found.

Action: Check the KM and the index definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15076: no dataset

Cause: A KM line is calling "getDataSet", but no data set is found.

Action: Check the KM or the DataSet definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15077: No Current Model Set

Cause: There is a call to "getModel" in the KM, but no model is found.

Action: Check the KM and the model definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15078: There is no Not Null column

Cause: There is a call to "getNotNullCol" in the KM, but no not null column is found.

Action: Check the KM and the not null column definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15079: There is no current Pop.

Cause: There is a call to "getPop" in the KM, but no interface is found.

Action: Check the KM and the interface definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15080: There is no Step

Cause: There is a call to "getStep" in the KM, but no step is found.

Action: Check the KM and the step definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15081: There is no Target Table

Cause: There is a call to "getTargetTable" in the KM, but no target table is found.

Action: Check the KM and the interface target table definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15083: Multiple Primary Keys have been detected for {0} .

Cause: A repository table can only have one primary key defined, but multiple primary keys are defined.

Action: Edit the table's primary key definitions and remove all but one.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15084: There is no session

Cause: There is a call to "getSession" in the KM, but no session is found.

Action: Check the KM and the session definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15085: The value : ''({0})'' is unknown.

Cause: A KM line has a templated call which contains an unknown bracketed property.

Action: Fix the KM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15086: There is no Temporary Index

Cause: There is a call to "getTemporaryIndex" in the KM, but no temporary index is found.

Action: Check the KM and the temporary index definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15087: There is no current execution context defined.

Cause: There is a call to "getContext" in the KM, but no context is found.

Action: Check the KM and the context definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15088: Not in designer mode

Cause: A KM line has a call to access design information, but the interpretation location is not set to designer.

Action: Make sure that the interpretation location is set to designer when this line is executed.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15089: asked '({0})' and available value are between 0 and ({1}).

Cause: A KM line is calling "getDataSet", but the specified index is out of range.

Action: Fix the KM or the DataSet definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15090: Table "{0}" not found on model "{1}", schema "{2}"

Cause: Attempt to initialize data services from a table that cannot be found

Action: Change data services reference or make sure that table exists
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15091: Impossible to connect to JPS MBean Server

Cause: Cannot connect to JPS MBean server.

Action: Internal Error.
Level: 32

Type: ERROR

Impact: Other

ODI-15092: Unable to generate data service - the column {0} does not exist in the database.

Cause: A data service references a column that does not exist

Action: Fix the data service reference or make sure that the column exists
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15093: Unable to regenerate this scenario. It references a null package.

Cause: The scenario must reference a package, but the package is null.

Action: Delete the scenario and create a new one.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15094: You must give a name for the published entity for each datastore.

Cause: A web services data store does not have a name.

Action: Give the data store a name.
Level: 32

Type: ERROR

Impact: Other

ODI-15095: Invalid entity for datastore: {0}

Cause: A web services data store has an invalid entity.

Action: Associate the data store with a valid entity.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15096: Property name must not be null.

Cause: The KM line is calling "isColAttrChanged", but the property value is null.

Action: Internal error, contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15097: Unknown value {0} for property

Cause: The KM line is making a templated call, but the property value is unknown.

Action: Fix the KM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15098: You must define a data source for the model.

Cause: The model used by a web service does not have any data source.

Action: Define a data source for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15099: You must specify a JKM for the model.

Cause: The model used by a web service does not have an associated JKM.

Action: Define a JKM for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15100: You must define a Java package for the model.

Cause: The model used by a web service does not have an associated Java package.

Action: Define a Java package for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15101: Invalid Java package format: {0}

Cause: The Java package associated with a model has an invalid package format.

Action: Correct the package format for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15102: You must specify an XML namespace for the model.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15103: Invalid namespace: {0}

Cause: A model namespace used by a web service is invalid.

Action: Correct the namespace for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15104: You must specify an SKM for the model.

Cause: A model used by a web service does not have an associated SKM.

Action: Add an SKM to the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15105: You must specify which schema the model will be deployed to.

Cause: No web service deployment schema is specified for the model.

Action: Specify a schema to which the model will be deployed.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15106: You must specify a name for the Data Service for the model.

Cause: The data service for the model does not have a name.

Action: Set a valid name for the data service.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15107: Invalid model code: {0}. It should follow the Java identifiers naming conventions.

Cause: The web service model name does not follow the standard Java identifier naming convention.

Action: Set a valid name for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15108: Invalid model Data Service name: {0}. It should follow the Java identifiers naming conventions.

Cause: The web service model Data Service name does not follow the standard Java identifier naming convention.

Action: Set a valid name for the model Data Service.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15109: Invalid web service name for datastore: {0}

Cause: The web service model data store has an invalid name.

Action: Set a valid name for the model data store.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15110: SKM is empty

Cause: The web service SKM has no valid lines.

Action: Add some lines to the SKM.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15111: Problem during deployment

Cause: Internal error.

Action: Contact Oracle support.
Level: 32

Type: SET_AT_RUNTIME

Impact: Deployment

ODI-15113: Reverse table {0} for model {1} already exists.

Cause: An attempt was made to reverse engineer a table, but it already exists in the model.

Action: Move or rename the data store in the model, or skip reverse engineering for the table.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15116: There is not enough data in the target file to proceed with the reverse-engineering. Please make sure the file has at least one non-empty line and number of rows to skip is correct.

Cause: An attempt was made to reverse engineer a target file that is empty, or the number of skipped rows is larger than the number of rows in the file.

Action: Set the number of skipped lines to a lower value, or add some data to the file.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15117: Not allowed (OLD and NEW are involved)

Cause: The KM line is calling "getColumn", but the ADH action origin is not ''NEW'' or ''OLD''.

Action: Change the ADH action origin.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15118: Invalid FTP URL

Cause: The URL given for a web services FTP connection is not correct.

Action: Check the URL for the FTP connection.
Level: 32

Type: SET_AT_RUNTIME

Impact: Network

ODI-15119: Column {0} has no Java datatype.

Cause: The column being processed has no java datatype.

Action: Internal Error: contact Oracle support.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-15120: Column {0} has no String datatype.

Cause: The column being processed has no string datatype.

Action: Internal Error: contact Oracle support.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-15121: Selector must be not null

Cause: The ADH selector value must not be null when "getColumn" is called from the KM line.

Action: Change the ADH selector value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15122: Exception getPKColList

Cause: An exception was found when calling "getPKColList" during KM execution.

Action: Fix the KM or the PK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15123: There is no AK constraint

Cause: There is a call to "getAK" in the KM, but no AK is found.

Action: Check the KM and the AK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15124: Unable to regenerate the following scenario:

Cause: Cannot regenerate the scenario.

Action: Delete the scenario and create a new one.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15125: Missing DataSet.

Cause: The interface is missing a dataset.

Action: Check interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15126: The sub-model must be set.

Cause: The sub-model is not set for the source or target.

Action: Check the interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15127: There is no CK constraint

Cause: There is a call to "getCK" in the KM, but no CK is found.

Action: Check the KM and the CK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15128: There is no FK constraint

Cause: There is a call to "getFK" in the KM, but no FK is found.

Action: Check the KM and the FK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15129: Selector value must be 'OLD' or 'NEW'

Cause: The ADH selector value must be 'OLD' or 'NEW' when "getColumn" is called from the KM line.

Action: Change the ADH selector value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15130: Unknown object in interface source table list

Cause: Internal Error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15131: You must define the name of each web service to be generated for each datastore.

Cause: A web service associated with a data store has no name.

Action: Give a name to the web service.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15132: Exception getPK

Cause: An exception was found when calling "getPK" during KM execution.

Action: Fix the KM or the PK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15135: There is no current index.

Cause: The current index can not be found for the property name.

Action: Check the reference.
Level: 32

Type: ERROR

Impact: Other

ODI-15141: Repository is not a development work repository

Cause: When getting a connection used to execute the KM, it was determined that the provided connection information does not point to a development work repository

Action: Fix the connection information
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15142: [PROPERTY: {0} not found.]

Cause: The bracketed property in the KM line (e.g. "[COL_NAME]") is not found.

Action: Fix the KM line to specify a correct property name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15143: Invalid isolation level : {0}

Cause: An invalid isolation level value was passed to SnpServiceGenerator.convertIsolationLevel

Action: Contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15144: KM not encrypted since it is empty.

Cause: KM was not encrypted since it is empty.

Action: Skip encryption.
Level: 32

Type: ERROR

Impact: Other

ODI-15146: Data Type can't be null

Cause: null DataType passed.

Action: Pass non null DataType.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15147: The changes on this target column will be lost since it is not saved (it has no mapping text)

Cause: Target column will not be saved.

Action: Enter mapping text if the column requires to be saved.
Level: 32

Type: WARNING

Impact: Interface Issue

ODI-15148: The target datastore is not on the Oracle Technology: this interface cannot be used with the platform compiler

Cause: Target datastore is not on Oracle.

Action: Move target datastore to an Oracle schema.
Level: 32

Type: WARNING

Impact: Interface Issue

ODI-15149: The staging area is not on the Oracle Technology: this interface cannot be used with the platform compiler

Cause: Staging Area is not on Oracle.

Action: Move Staging Area to an Oracle schema.
Level: 32

Type: WARNING

Impact: Interface Issue

ODI-15150: The source datastore is not on the Oracle Technology: this interface cannot be used with the platform compiler

Cause: Source DataStore not on Oracle.

Action: Use only DataStores located on an Oracle technology.
Level: 32

Type: WARNING

Impact: Interface Issue

ODI-15151: Non ordered outer joins cannot be used with the platform compiler

Cause: An outer join is not ordered.

Action: Make the join ordered.
Level: 32

Type: WARNING

Impact: Interface Issue

ODI-15152: Unhandled Action {0}

Cause: This shouldn't happen. Programmer added an action in the enum and forgot to add it in switch.

Action: Add action in switch.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15153: The column is already the first column and cannot be moved up

Cause: Column already first and cannot be moved up.

Action: Do not try to move first column up.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15154: The column is already the last column and cannot be moved down

Cause: Column already last and cannot be moved down.

Action: Do not try to move last column down.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15155: Cannot move a target column to a position that is 0 or negative: {0}

Cause: Trying to move a column beyond the boundaries of column positions.

Action: Use a value between 1 and the number of columns.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15156: Cannot move a target column to a position beyond the size of the column list: {0} is greater than {1}

Cause: Trying to move a column beyond the boundaries of column positions.

Action: Use a value between 1 and the number of columns.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15157: Cannot remove the only dataset of interface {0}

Cause: Trying to remove the last dataset of an interface is not permitted.

Action: Make sure there are more than one dataset in the interface before deleting it.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15159: Cannot move target columns on a non temporary DataStore.

Cause: Trying to move columns on a non temporary DataStore.

Action: Make sure that the target DataStore is temporary before attempting to move target columns.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15160: Native Sequences may not be supported by the target technology after transforming with the Platform Compiler

Cause: Using Native Sequence and Platform Compiler Enabled User Param Set

Action: Make sure that all target technologies will support native sequences
Level: 32

Type: WARNING

Impact: Programmatic

ODI-15162: The interface {0} use native sequence. Native sequence are not allowed for Derived Table (sub select statement)

Cause: Using native sequence in derived sub interface

Action: Make sure that none sub interface using native sequence
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15200: Tried to retrieve an int with an {0} object

Cause: Attempted to read the column from RDB as an integer, but the column type is not integer

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15201: Tried to retrieve a short with an {0} object

Cause: Attempted to read the column from RDB as a short type, but the column type is not short

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15202: This resultset accepts only FETCHFORWARD requests

Cause: Attempted to set the fetch direction to something other than FETCH_FORWARD for a RDB result set read

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15203: This function is unsupported: the software you are using might not be compatible with this driver.

Cause: A jdbc call was made that is not supported by the currently loaded jdbc driver for RDB

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15204: The {0} call is not implemented in this result set class.

Cause: A result set call was made that is not implemented by the ODI RDB result set class

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15205: The call is not supported in this result set class.

Cause: A result set call was made that is not supported by the ODI RDB result set class

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15206: Unmanaged numeric type {0}

Cause: The RDB inserter class was passed a data value of a numeric type that is not handled

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15207: Strange: a PK has multiple lines

Cause: When selecting a parent row based on a primary key, multiple rows were returned

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15208: The PK column of the root table has an unknown type: {0}

Cause: When unloading data from the RDB, the PK column of the parent table has an unknown type

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15209: Unsupported technology (Driver: {0}, Url: {1})

Cause: The jdbc driver is not supported by the ODI RDB

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15210: Unsupported technology: HSQL cannot create FKs after the tables have been created

Cause: The Hypersonic SQL engine cannot create FK after the table is already created

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15211: Unsupported technology: HSQL cannot create PKs after the tables have been created

Cause: The Hypersonic SQL engine cannot create PK after the table is already created

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15212: Datatype NULL (0) unsupported

Cause: The Hypersonic SQL engine does not support the null datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15213: JDBC Datatype '{0}' unsupported

Cause: The Hypersonic SQL engine does not support the datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15214: JDBC Datatype '{0}' with length parameter unsupported

Cause: The Hypersonic SQL engine does not support the datatype with length

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15215: JDBC Datatype '{0}' with length and scale parameters unsupported

Cause: The Hypersonic SQL engine does not support the datatype with scale

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15216: JDBC Datatype '{0}' unsupported

Cause: The internal MS Sql Server database does not support the datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15217: JDBC Datatype '{0}' with length parameter unsupported

Cause: The internal MS SQL Server database does not support the datatype with length

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15218: JDBC Datatype '{0}' with length and scale parameters unsupported

Cause: The internal MS SQL Server database engine does not support the datatype with length and scale

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15219: Please transform your URL into: {0};SelectMethod=cursor

Cause: The internal MS SQL Server database engine does not recognize the supplied URL

Action: Change the format of the connection URL
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15220: need length param

Cause: The internal Oracle database does not support the selected type without a length param

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15221: Datatype NULL (0) unsupported

Cause: The internal Oracle SQL engine does not support the null datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15222: JDBC Datatype '{0}' unsupported

Cause: The internal Oracle database does not support the datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15223: JDBC Datatype '{0}' with length parameter unsupported

Cause: The internal Oracle database does not support the datatype with length

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15224: JDBC Datatype '{0}' with length and scale parameters unsupported

Cause: The internal Oracle database engine does not support the datatype with length and scale

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15225: No key found on table {0}

Cause: The internal database table does not have a key

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15226: The root table {0} has no data

Cause: The internal database table does not have any data

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15227: Multiple keys found on table {0}

Cause: The internal database table has multiple keys

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15228: *** FATAL *** Table {0} could not be validated

Cause: The internal database cannot validate the table

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15229: *** FATAL *** Table {0} could not be found

Cause: The internal database cannot find the table

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15230: Could not convert object {0} to a {1}

Cause: The internal database cannot convert the datatype of the selected column

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15231: No '=' sign found on line {0} of bundle {1}

Cause: The internal database engine encountered a syntax error when reading the property file

Action: Fix the property file
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15232: The alias {0} for table {1} is already used by another table, when reading bundle {2}

Cause: The internal database found a duplicate table alias in a property file

Action: Fix the property file
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15233: Table {0} is used twice. Make sure that the table names and aliases do not conflict.

Cause: The internal database found a duplicate table name in the property bundle

Action: Fix the property file
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15234: Internal RDB database table {0} not found

Cause: The requested table cannot be found in the internal database

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15235: Internal RDB database key {0} not found

Cause: The requested key cannot be found in the internal database

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15236: Unknown table {0}

Cause: The requested table cannot be found in the internal database

Action: Correct the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15237: Duplicate table

Cause: The internal database table is a duplicate table

Action: Correct the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15238: Could not find table although we should have created it!

Cause: The newly created table cannot be found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15239: Only SnpsRDBDiffActionImportDifference are supported for now.

Cause: When processing diff actions in a diff operation, an unsupported diff action class was found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15240: Unknown key {0}

Cause: When processing diff actions in a diff operation, a nonexistent key was specified by the diff action

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15241: This type of difference is not managed for now: {0}

Cause: When processing diff actions in a diff operation, an unsupported diff action class was found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15242: Unknown difference type: {0}

Cause: When processing diff actions in a diff operation, an unknown diff class was found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15243: Bad model number: {0}

Cause: When processing diff actions in a diff operation, the 2 models that are being compared are internally numbered as model 1 and 2. A model number other than 1 or 2 was used internally in a call to getModel.

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15244: Could not add a key because {0} is not an ID key.

Cause: When building a model, the specified key class instance was not an id key

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15245: Unknown key type: {0}

Cause: When building a model, an unknown key class was found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15246: Key {0}.{1} is of unknown type: {2}

Cause: When building a model, an unknown key class was found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15247: The table {0} cannot be found. It is referenced by key: {1}.

Cause: When building a model, an table name is referenced by a key, but the table cannot be found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15248: The column {0} in table {1} cannot be found. It is referenced by key: {2}.

Cause: When building a model, an column name is referenced by a key, but the column cannot be found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15249: An {0} was caught while adding a key which is not an FK. Very strange.

Cause: When building a model, an column name is referenced by a key, but the column cannot be found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15250: The key {0} referenced by table {1} cannot be found.

Cause: When building a model, a key name is referenced by a table, but the key cannot be found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15251: A duplicate key was found: {0}

Cause: When dropping a model, a duplicate key was found in the model

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15252: Key already exists: {0}

Cause: When updating a model, a duplicate key was found in the model

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15253: Key not found: {0}

Cause: When updating a model, the key was not found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15254: Could not find a constructor with a key name for class {0}

Cause: When creating a key class instance, the constructor could not be found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15255: Could not instantiate an object of class {0}

Cause: Could not instantiate the key class

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15256: Could not create an object for class {0} for security reasons

Cause: Could not instantiate the key class, due to a security failure

Action: Check security settings
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15257: Could create an object for class {0} because a {1} occurred saying {2}

Cause: Could not instantiate the key class, due to an invocation target exception

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15258: Column {0} not found

Cause: The column could not be found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15259: The key class {0} is not an ID key class.

Cause: The specified key class instance was not a SnpsRDBIdKey instance

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15260: Could not add column {0}: Unsupported datatype: {1}

Cause: Cannot add the column to the model because the datatype is not supported by the technology

Action: Correct the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15261: Unsupported action: {0}

Cause: The action class is not supported by the ODI RDB

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15262: Cannot drop column {0}. It is used in a foreign key!

Cause: An attempt was made to drop a column that participates in a foreign key

Action: Drop the key first, then the column
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15263: Cannot drop column {0}. It is used in a primary key!

Cause: An attempt was made to drop a column that participates in a primary key

Action: Drop the key first, then the column
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15264: Cannot modify this column. It is used in a foreign key!

Cause: An attempt was made to modify a column that participates in a foreign key

Action: Drop the key first, then modify the column
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15265: Cannot modify this column. It is used in a primary key!

Cause: An attempt was made to modify a column that participates in a primary key

Action: Drop the key first, then modify the column
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15268: Table not found: {0}

Cause: When attempting to drop a table during an update, the table name is not found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15270: Key type {0} is not supported here.

Cause: The key type is not supported

Action: Correct the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15272: An error occurred while executing a RDB command: {0}

Cause: When executing a command action, an exception was thrown

Action: Check root cause
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15273: {0}: action is not accepted: {1}

Cause: Attempt to execute a command action, but it is not accepted

Action: Check root cause
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15274: Multiple PKs are not allowed on a table

Cause: When reverse engineering a primary key, multiple primary keys were found for the table

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15275: An exception ocurred while retrieving a table primary key: {0}

Cause: When reverse engineering a table, a primary key could not be retrieved

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15276: An exception occurred while retrieving the indexes of a table: {0}

Cause: When reverse engineering a table, the indexes could not be retrieved

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15277: An exception ocurred while retrieving a table foreign keys: {0}

Cause: When reverse engineering a table, the foreign keys could not be retrieved

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15278: An exception occurred while retrieving the check constraints of a table: {0}

Cause: When reverse engineering a table, the check constraints could not be retrieved

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15279: An exception occurred while retrieving the alternate keys of a table: {0}

Cause: When reverse engineering a table, the alternate keys could not be retrieved

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15280: *** FATAL *** Table {0} is duplicate as root

Cause: The table is duplicated as the root when determining the root tables of the model

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15281: *** FATAL ** Table {0} is unknown

Cause: The root table is unknown

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15282: Table {0} is unknown though it was reversed

Cause: The table cannot be found in the ODI model, although it was reversed

Action: Retry the reverse engineering
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15283: Duplicate declaration for table {0}

Cause: The model XML contains a duplicate table declaration

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15285: FK {0} references a table with no PK.

Cause: The model XML contains a foreign key that references a table with no defined primary key

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15286: Unknown PK table for foreign key {0}: please check the name and order of the tables and FK.

Cause: The model XML contains a foreign key that references an unknown primary key table

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15287: Unknown element: {0}

Cause: The model XML contains an unknown element

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15288: An {0} error occurred with the following message: {1}

Cause: An error occurred when writing the model to a file

Action: See root cause
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15290: Column {0} was not found in table {1}

Cause: The column was not found when building the columns from column names

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15291: *** FATAL *** Could not rename table {0} to {1}

Cause: Could not rename table

Action: Check permissions and security settings
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15292: *** FATAL *** Could not rename table {0} because it was not found in the model!

Cause: Could not rename table, because the table to be renamed does not exist

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15293: Unknown FK table for foreign key {0}: please check the name and order of the tables and FK.

Cause: The model XML contains a foreign key that references an unknown table

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15294: unknown element: {0}

Cause: The model XML contains an unknown XML element

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15295: Unsupported datatype: {0}

Cause: The datatype is unsupported when creating the column from attributes

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15300: A {0} occurred while creating the helper of class {1}. Error message: {2}

Cause: INTERNAL ERROR: A helper cannot be created.

Action: Internal error: contact Oracle support.
Level: 32

Type: ERROR

Impact: Other

ODI-15301: Choose: {0}

Cause: Choose one of the displayed options.

Action: Choose one of the displayed options.
Level: 32

Type: ERROR

Impact: Other

ODI-15302: FK is null: {0}

Cause: The FK is null, may indicate repository corruption.

Action: Internal error: contact Oracle support.
Level: 32

Type: ERROR

Impact: Other

ODI-15303: JDBC Datatype '{0}' with length '{1}' parameter unsupported

Cause: MySQL database does not support the datatype with length

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15304: JDBC Datatype '{0}' with length '{1}' and scale '{2}' parameter unsupported

Cause: MySQL database does not support the datatype with scale

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15305: JDBC Datatype '{0}' unsupported

Cause: MySQL database does not support the datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15306: Column data type "{0}" not supported. Refer documentation for supported types.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15307: Metadata format of element with identifier "{0}" is incorrect. Found value "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15308: Error unloading CLOB for column "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15309: Error unloading BLOB for column "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15400: Error in generating data service

Cause: Exception thrown when creating the data service used for DDL generation and reverse engineering.

Action: Check the root cause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15401: Unknown key {0}

Cause: Unknown key encountered when processing diff class instances during DDL generation.

Action: Check the model.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15402: Exception thrown in the DDL generation service: {0}

Cause: An exception was thrown while generating DDL.

Action: Check the root cause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15403: The method is not supposed to sort something else than the expected actors. Attempting to sort class instances: {0}, {1}

Cause: While sorting action commands, the DDL generator service encountered an unknown class instance type.

Action: Internal Error: contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15404: Scenario generation has not been implemented for this container.

Cause: During DDL generation, an attempt was made to generate a scenario for an object that does not support it.

Action: Internal Error: contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15405: Scenario generation exception: {0}

Cause: An exception was thrown during scenario generation.

Action: Check root cause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15406: Oozie workflow generation exception: {0}

Cause: An exception was thrown during Oozie workflow generation.

Action: Check root cause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15407: Oozie workflow generation exception for Task: {0} - Transactions not supported on Oozie engine with commit mode not set. {1} command Transaction Channel: {2}.

Cause: Transactions are not supported on Oozie Engine.

Action: Please refer to documentation on Oozie Engine Execution.
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: The LKM is not compatible with the source set technology or multi-connection setting.

Action: Select an LKM which matches the source set technology and multi-connection setting.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15524: LKM {0} not accepted for staging area to target

Cause: The LKM is not compatible with the staging area technology or multi-connection setting.

Action: Select an LKM which matches the staging technology and multi-connection setting.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15525: CKM {0} not accepted for target technology

Cause: The CKM is not compatible with the target technology.

Action: Select a CKM which matches the target technology.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15526: IKM {0} not accepted for staging and target technology

Cause: The IKM is not compatible with the staging or target technologies or multi-connection setting.

Action: Select an IKM which matches the staging and target technologies and multi-connection setting.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15527: IKM {0} not accepted for target technology

Cause: The IKM is not compatible with the target technology or multi-connection setting.

Action: Select an IKM which matches the target technology and multi-connection setting.
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: Recheck target expressions for proper source references.
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-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-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: Review the error details for further information.v
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: This is an internal error with no recommended user 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: This is an internal error with no recommended user 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: Remove jounalizing from one or more datastores.
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: Remove jounalizing from one or more datastores.
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: The target datastore is a temporary target.

Action: Use a non-temporary target.
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: Multiple source datastores were found.

Action: Use only a single source datastore.
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: Use only a single source datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15584: Elements are from different interfaces.

Cause: The components passed to prepareSQLStatement are from different interfaces.

Action: Only pass components from the same interface when preparing an SQL statement.
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: Only pass components from the same data set when preparing an SQL statement.
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: Ensure that the interface uses only one dataset.
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 datastore was found.

Action: Ensure that multiple tables are contained in a sourceset.
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: Ensure that joins are contained in a sourceset.
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: Ensure that only a single, real table is used in the sourceset.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15617: Invalid type for a TextHolder: {0}

Cause: The method getExecutableTextHolderFor was called with an invalid TextHolder component type.

Action: Valid types are TargetMapping, TargetColumn, Filter, and Join.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15618: Cannot set a source set on a target column.

Cause: SetSourceSet was called for a target column, which is not a valid usage. This method is specified for the interface, but is not valid for this class.

Action: SetSourceSet should never be invoked for this class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15619: Inconsistent filter with a clauseType of {0}

Cause: The Filter.getFilterType method was called, but the clause type was not a filter type.

Action: Ensure that the filter has a type of SnpPopClause.CLAUSE_TYPE_FILTER or SnpPopClause.CLAUSE_TYPE_JRN_FILTER.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15620: Execution location is null. Target technology cannot be determined

Cause: The execution filter for the location was not set.

Action: The execution location should be set in the Filter constructor or by invoking setExecutionLocation.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15621: Attached dataStore is null. Target technology cannot be determined

Cause: The attached datastore for the execution location was not set.

Action: The datastore should be set in the Filter constructor or by invoking setAttachedDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15622: Staging area does not have a logical schema. Target technology cannot be determined

Cause: The attached datastore for the execution location was not set.

Action: The datastore should be set in the Filter constructor or by invoking setAttachedDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15623: Invalid technology for the given index type

Cause: The technology of the clause and index type do not match.

Action: Ensure that the index type technology matches the clause technology.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15624: Inconsistent join with clauseType = {0} and joinType = {1}

Cause: The join clause type is invalid.

Action: This exception is thrown from a deprecated method. Use isCross or isOrdered methods instead.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15625: Cannot set OdiDataType on a journalized source column

Cause: The setDataType method has been invoked for a journalized source column, but the datatype cannot be set for journalized columns.

Action: Do not invoke this method for a journalized column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15626: Cannot set the length on a journalized source column

Cause: The setLength method has been invoked for a journalized source column, but the length cannot be set for journalized columns.

Action: Do not invoke this method for a journalized column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15627: Cannot set the scale on a journalized source column

Cause: The setScale method has been invoked for a journalized source column, but the scale cannot be set for journalized columns.

Action: Do not invoke this method for a journalized column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15628: Cannot set the data type on a source column

Cause: The setDataType method has been invoked for a source column, but the datatype cannot be set for source columns.

Action: Do not invoke this method for a source column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15629: Cannot set the length on a source column

Cause: The setLength method has been invoked for a source column, but the length cannot be set for source columns.

Action: Do not invoke this method for a source column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15630: Cannot set the scale on a source column

Cause: The setScale method has been invoked for a source column, but the scale cannot be set for source columns.

Action: Do not invoke this method for a source column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15631: Connection information is not available.

Cause: The physical schema has not been set.

Action: Define physical and logical schemas.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15632: Column {0} may not be removed because it is mapped in interface {1}.

Cause: The specified target column is mapped in another interface. This dependency prevents removal of the column.

Action: Only remove a column after mapping dependencies have been removed.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15633: Data Type must be set first.

Cause: Data Type is null.

Action: Set Data Type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15634: Length is not allowed for the current Data Type

Cause: Data Type doesn't support length.

Action: Check Data Type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15635: Scale is not allowed for the current Data Type.

Cause: Data Type doesn't support scale.

Action: Check Data Type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15636: Cannot change the column because it's not a temporary column.

Cause: Column isn't temporary.

Action: Check column state.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15637: Execution location must be either null or target.

Cause: Wrong Execution location state.

Action: Check Execution location.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15638: Scenario {0} contains invalid characters. Try {1}.

Cause: String contains invalid characters.

Action: Check scenario name.
Level: 32

Type: ERROR

Impact: Other

ODI-15639: Scenario version is not set.

Cause: Scenario version is not set.

Action: Set scenation version.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15640: No Scenario was found through the Tag : {0}.

Cause: No Scenario was found.

Action: Check tag.
Level: 32

Type: ERROR

Impact: Other

ODI-15641: The refresh SQL statement of a variable cannot contain sequence references when the variable is added to a load plan.

Cause: SQL statement contains sequence references.

Action: Check refresh SQL statement.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15642: Scenario name must be {0} characters long max.

Cause: Scenario name is too long.

Action: Check name length.
Level: 32

Type: ERROR

Impact: Other

ODI-15643: No Physical Mapping Design from Mapping: {0}.

Cause: Cannot find any Physical Mapping Design from Mapping.

Action: Check there is valid Physical Mapping Design.
Level: 32

Type: ERROR

Impact: Other

ODI-15644: The physical data server for the source code and for sequqnce(s) {0} is not the same, this may result in the same sequence value being used for each row.

Cause: The sequence may be remote so a single nextval is calculated and reused per row.

Action: Make sure the sequence and task have the same data server if you want the sequences to use distinct values per row.
Level: 1

Type: NOTIFICATION

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: 1

Type: NOTIFICATION

Impact: Other

ODI-15700: Exception thrown in the Odi shortcut service: {0}

Cause: An exception was thrown while materializing a shortcut object.

Action: Check the root cause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-16000: Dataset has no sources: {0}

Cause: The Dataset has no source or the source is not available.

Action: Check sources.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16001: Dataset {0} contains only one source.

Cause: The Dataset has only one source.

Action: Check sources.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16002: Dataset has added default join condition with cartesian product: {0}

Cause: Dataset has added default join condition with cartesian product.

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16003: Multiple joins in the same dataset have the same order number: {0}

Cause: Multiple joins in the same dataset have the same order number.

Action: Check the order numbers of join components in the dataset.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16004: ANSI join: {0} has no user-defined order. The default order -1 (meaning "random order") is assigned.

Cause: An ANSI join component does not have a join order assigned to it.

Action: Assign an order number that is not -1.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16005: Join component inside dataset has no valid source references in the join condition. Join: {0} , condition = {1}.

Cause: Join component inside dataset has no valid source references in the join condition.

Action: Check source references in the join condition.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16006: Join component inside dataset has only one source references in the join condition, must have at least 2 references. Join: {0}, condition = {1}

Cause: Join component inside dataset has only one source references in the join condition, must have at least 2 references.

Action: Check join condition.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16008: There is no possible pairwise join order that satisfies both the join condition references and the user order numbers.

Cause: There is no possible pairwise join order that satisfies both the join condition references and the user order numbers.

Action: Check both the join condition references and the user order numbers.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16009: Lookup component creation is not complete: it misses either driving and/or lookup source information.

Cause: Lookup component: {0} in dataset: {1} is incomplete. (Driving source: {2}, lookup source: {3})

Action: Set the missing driving and/or lookup source on the lookup component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16010: Dataset has sources that are not referenced by any join condition. Dataset: {0} , unconnected sources: {1}.

Cause: Dataset has sources that are not referenced by any join condition.

Action: Check sources.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16011: INTERNAL ERROR: Dataset error when connecting joins in order. Cannot find source for join: {0}, referenced source name: {1}.

Cause: Dataset error when connecting joins in order. Cannot find source for join.

Action: Check sources.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16012: Cannot find ordered join connection in dataset for: {0}

Cause: Cannot find ordered join connection in dataset.

Action: Check ordered join connection.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16013: Cannot find a valid pairwise tree of join connections for dataset: {0} unconnected join: {1} ({2})

Cause: Cannot find a valid pairwise tree of join connections for dataset.

Action: Check join connections.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16014: Cannot find a valid pairwise tree of join connections for dataset: {0}

Cause: Cannot find a valid pairwise tree of join connections for dataset.

Action: Check join connections.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16015: Missing expression for aggregate component {0}, attribute: {1}

Cause: Missing expression for aggregator attribute.

Action: Check aggregator attribute.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16016: Could not find an output signature for point: {0}

Cause: Could not find an output signature for point.

Action: Check output signature for the connection point.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16017: The join component: {0} has more than 2 input connector points. This is not recommended. ANSI SQL join syntax may not be supported.

Cause: The join component has more than 2 input connector points. This is not recommended. ANSI SQL join syntax may not be supported.

Action: Check the join component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16018: The join condition for component: {0} only references {1} sources, but there are {2} input connector points. Expression text: {3}

Cause: The number of references sources is less than the number of input connector points.

Action: Check the join condition and input connector points.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16019: Set component output attribute {0} contains {1} expressions, but there are only {2} input connector points.

Cause: The number of input expressions is greater than the number of input connector points.

Action: Check expressions and input connector points.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16020: Set component output attribute expression for attribute: {0} does not have a scoping input connector point specified. Set component input expressions must have an associated scoping input connector point.

Cause: A scoping input connector point need to be specified.

Action: Check If set component input expressions have an associated scoping input connector point.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16021: The immediate downstream node {0} of the AP node {1}, which uses a push style LKM, is not a target.

Cause: A push style LKM is assigned to an AP node but its immediate downstream node is not a target.

Action: Either change the LKM to a pull style LKM or move some physical nodes to source execution unit(s).
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16022: Set component output attribute: {0} does not have an expression that references through input: {1}.

Cause: Not all input connector points have been referenced by one expression.

Action: Check input connector points and expressions.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16023: Expression cross reference object is null: {0}.

Cause: Expression cross reference object is null.

Action: Check expression cross reference object.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16024: The expression contains unresolved attribute references. {0} Expression: {1} Unresolved identifiers: {2}.

Cause: The expression contains identifiers that were not resolved as attribute references.

Action: Check all identifiers in the expression for accessibility through a valid input connector point.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16025: An access point (AP) node has been created in the physical graph, but it does not have any columns: {0}.

Cause: ERROR: An access point (AP) node has been created in the physical graph, but it does not have any columns.

Action: Check access points.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16026: Cannot move an existing physical node to a different physical design! Node: {0}.

Cause: Cannot move an existing physical node to a different physical design! .

Action: The action attempted is not supported.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16027: No path exists from physical node: {0} to: {1}.

Cause: No path exists between physical nodes.

Action: Check paths between physical nodes.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16028: Expression push is not allowed because it would push the expression through projector node: {0}.

Cause: Expression push is not allowed because it would push the expression through projector node.

Action: The action attempted is not supported.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16029: Expression {0} ({1}) owned by: {2} has blank value, but a non-blank value is required.

Cause: Expression has blank value, but a non-blank value is required.

Action: Check the expression text.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16030: An attribute expression must reference only one projector or joiner source. Attribute: {0}.

Cause: An attribute expression must reference only one projector or joiner source.

Action: Check attribute expressions.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16031: The lookup component must have a driver and a lookup source input connection.

Cause: The lookup component is not properly connected, it must have 2 input connections.

Action: Connect the lookup component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16032: Unsupported component type: {0}: component: {1} in dataset: {2}.

Cause: The dataset does not support the component type.

Action: Remove the component from the dataset.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16033: Aggregate filter: {0} is not supported in dataset: {1}.

Cause: The dataset does not support aggregate filters.

Action: Remove the aggregate filter.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16034: A transparent target LKM was picked for: {0}, but the AP node has more than one downstream target component.

Cause: An AP node with a transparent target LKM can only have one downstream target.

Action: Pick a different LKM.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16035: Target node {0} has assigned IKM {1}. The IKM will be ignored.

Cause: A target node that is loaded by an upstream AP node with a transparent target LKM assigned does not need an IKM assigned, since the loading functionality will be handled by the LKM transparent push.

Action: Set IKM to null.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16036: No target connected to AP node: {0} with SQL multi-connect LKM assigned.

Cause: An AP node with SQL multi-connect LKM assigned has no target.

Action: Add a target component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16037: Only one target allowed for AP node: {0} with SQL multi-connect LKM assigned.

Cause: An AP node with multi-connect LKM assigned cannot have multiple targets.

Action: Pick different LKM, or remove all but one of the targets in the mapping.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16038: No extra logical components are allowed downstream from AP node: {0} with SQL multi-connect LKM assigned. The AP node must have a direct connection to target.

Cause: An AP node with multi-connect LKM assigned must be connected directly to the target, with no intervening nodes.

Action: Pick a different LKM, or reconfigure the physical graph such that the AP nodes connects directly to the target.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16039: The AP node: {0} has a transparent target LKM assigned, but it is not connected directly to the target.

Cause: An AP node with transparent target LKM assigned must be connected directly to the target, with no intervening nodes.

Action: Pick a different LKM, or reconfigure the physical graph such that the AP nodes connects directly to the target.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16040: Non-ANSI full outer join for component: {0} is not supported.

Cause: Full outer join is set to generate non-ANSI syntax.

Action: Check the box for "Generate ANSI Syntax" under Join properties.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16041: The manual group by clause is missing a required attribute: {0}

Cause: The maual group-by expression is missing one or more attributes required for the SQL group-by clause.

Action: Edit the manual group-by expression to included the missing attribute.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16042: The expression for attribute: {0} does not contain an aggregate function, but the group by column setting is NO. Non aggregate attributes should be part of the group-by clause.

Cause: The group-by column setting for an attribute is NO, but it should be part of the group-by clause because the expression does not contain an aggregate function.

Action: If the attribute expression does not contain an aggregate, set the group by column setting to YES.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16043: The expression for attribute: {0} contains an aggregate function, but the group by column setting is YES. Only non aggregate attributes should be included in the group-by clause.

Cause: The group by column setting for an attribute is YES, but it should not be part of the group-by clause because the expression contains an aggregate function.

Action: If the attribute expression contains an aggregate, set the group by column setting to NO.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16044: The having clause references aggregate attribute: {0}, but an aggregate function is not specified.

Cause: An aggregated attribute is used in a having clause without an aggregate function.

Action: If the having clause references an aggregated attribute, include the aggregate function used with that attribute.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16045: Input connector point {0} is not referenced by any attribute expression. That input to the set component is unused.

Cause: An input connector point for a set component is unused because no attribute expressions reference attributes scoped through that connector.

Action: At least one attribute expression should reference an attribute through the input connector in order to use that input to the set.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16046: Set components must have a minimum of two input connector points.

Cause: The set component has less than two input connector points.

Action: Add an input connector point. Set components must have at least two sources.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16047: Set component output attribute: {0} must have a non empty expression for input connector point {1}.

Cause: The number of input expressions is less than the number of input connector points.

Action: Specify a non empty expression for each input. Specify null if no attribute reference is used.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16048: Reusable mapping component: {0} must have a connection for input connector point {1}.

Cause: An input connector point is not connected to another map component.

Action: Connect the input connector point to a source component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16049: Reusable mapping component {0} has one or more output connector points, but none are connected or contain target components. DML cannot be generated without a target component connected downstream or within the reusable mapping.

Cause: None of the output connector points for the reusable mapping component are connected or contain target components.

Action: Add a connection for at least one output connector point.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16050: Native sequence and ORDER BY operation are performed on the same flow. This might not be allowed in some technologies such as Oracle.

Cause: Sequence is used before order by, this is now allowed in Oracle.

Action: Remove sorter component or place sorter in an execution unit different from the sequence expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16051: The Sub select option may not be set for reusable mappings having an input signature.

Cause: The reusable mapping component setSubSelect method was called with a value of true, but sub select is not allowed if an input signature is present.

Action: Avoid calling the setSubSelect method or specify false for the value parameter.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16052: The Sub select option may not be set for reusable mappings having more than one output signature.

Cause: The reusable mapping component setSubSelect method was called with a value of true, but sub select is not allowed if more than one output signature is present.

Action: Avoid calling the setSubSelect method or specify false for the value parameter.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16053: Mixed non-ordered (outer) join and ordered join is not supported.

Cause: Outer join is set to non-ordered.

Action: Change the join to ordered join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16054: An unparsed identifier, {0}, was found in the aggregate HAVING clause. This identifier was not found in any other aggregate or group by expressions.

Cause: An identifier was found in the HAVING clause, but is invalid because it is not present in any aggregation or group by expression.

Action: Remove this expression from the HAVING clause or use it in one of the aggregate output attribute expressions.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16055: Reusable mapping {0} for reusable mapping component {1} contains errors or warnings.

Cause: A reusable mapping used by this mapping has errors or warnings.

Action: See following error or warning messages regarding the reusable mapping.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16056: The driver connection for lookup component {0} is not connected to any source.

Cause: A connection has not been made between the source and driving connection of the lookup component.

Action: Connect a source to the lookup component driver connection.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16057: The lookup connection for lookup component {0} is not connected to any source.

Cause: A connection has not been made between the source and lookup connection of the lookup component.

Action: Connect a source to the lookup component lookup connection.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16058: Output signature {0} of reusable mapping {1} is not connected to any input source.

Cause: An output signature is not connected to any upstream component.

Action: Connect the output signature to an upstream component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16059: Error adding lines to task container for KM {0}: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16060: Error finding helper component KM for AST processing of a node with 11g KM assigned: node={0}, helper KM={1}, error={2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16061: Error when calling generation delegate for component KM {0}: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16062: Cannot create node variable binding map for component KM {0}: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16063: No target multi-connect IKM found when processing an AP node with a SQL multi-connect LKM assigned.

Cause: A multi-connect IKM could not be found for a target.

Action: Check the target IKM assignment.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16064: When processing an AP node with SQL multi-connect LKM assigned, the downstream target node does not have a multi-connect IKM assigned.

Cause: The IKM assigned to the target is not a multi-connect IKM. If an AP node uses a multi-connect LKM, a multi-connect IKM is required on the target.

Action: Assign a multi-connect IKM to the target.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16065: Cannot get an entity manager for the mapping object. The entity manager must be set for the owning mapping or reusable mapping by calling IOdiEntityManager.persist() or Mapping.setEntityManager(), before this operation can be done. Mapping object= {0}

Cause: An mapping operation is being performed that requires the mapping to resolve a reference, but the mapping entity manager has not been set.

Action: Set the entity manager for the mapping, by calling IOdiEntityManager.persist() or Mapping.setEntityManager().
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16066: Target datastore column {0} is a mandatory column and should be mapped.

Cause: Missing expression for mandatory target datastore column.

Action: Check target datastore mandatory column expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16067: The Sub select option may not be set for reusable mappings having no output signature.

Cause: The reusable mapping component setSubSelect method was called with a value of true, but sub select is not allowed if no output signature is present.

Action: Avoid calling the setSubSelect method or specify false for the value parameter.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16068: A parse error was encountered when parsing the expression: {0}. The default parser supports ANSI SQL delimiters. If a non-standard syntax is desired, use the free-form expression delimiters /%% and %%/ around the expression.

Cause: Expression is syntactically incorrect.

Action: Make sure the expression is well-formed.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16069: Technology {0} does not support the WHERE clause and cannot process the join.

Cause: Technology "Where" indicator is set to false.

Action: Check the technology setting or remove the join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16070: Ordered joins are not supported in technology {0}.

Cause: Technology Join Support Ordered indicator is set to false.

Action: Set join to non-ordered (Generate ANSI syntax = false).
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16071: Cross joins are not supported in technology {0}.

Cause: Technology Cross Join indicator is set to false.

Action: Set join type to non-cross join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16072: Natural joins are not supported in technology {0}.

Cause: Technology Natural Join indicator is set to false.

Action: Set join type to non-natural join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16073: Non-ordered natural joins are not supported.

Cause: Natural Join is set to non-ordered (generate ANSI syntax = false).

Action: Set 'Generate ANSI syntax' to true.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16074: Non-ordered joins are not supported in technology {0}.

Cause: Join is set to non-ordered (generate ANSI syntax = false).

Action: Set join to ordered (Generate ANSI syntax = true).
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16075: Non-ordered outer joins are not supported in technology {0}.

Cause: Outer Join is set to non-ordered (generate ANSI syntax = false).

Action: Set 'Generate ANSI syntax' to true.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16076: Outer joins are not supported in technology {0}.

Cause: Join is set to outer join.

Action: Set join to non-outer join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16077: Full outer joins are not supported in technology {0}.

Cause: Join is set to full outer join.

Action: Set join to non-full outer join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16078: Inner joins are not supported in technology {0}.

Cause: Join is set to inner join.

Action: Set join to non-inner join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16079: Reusable mapping {0} is not compatible with dataset {1}. A reusable mapping within a dataset must have no input signatures and exactly one output signature.

Cause: An incompatible reusable mapping is being added to the dataset. The reusable mapping must have no input signatures and exactly one output signature.

Action: Choose a different compatible reusable mapping or modify the resuable mapping to contain just a single output signature and no input signatures.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16080: Mapping component type {0} is not supported within a {1}.

Cause: An unsupported component is being added to a mapping or composite component.

Action: Use a supported component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16081: Physical Mapping Design {0} cannot be calculated with no optimization context.

Cause: The optimization context of the physical design is not set, or it becomes invalid because the referenced context is deleted.

Action: Check the optimization context of the physical design and specify an appropriate context.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16082: The physical node {0} cannot be supported by technology {1} on execution unit {2} of mapping {3}.

Cause: The physical node cannot be moved to the execution unit because its technology does not support the node.

Action: Do not move the physical node to this execution unit.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16083: Input Attribute {0} of reusable mapping component {1} does not have an expression to connect it to any source, but is referenced in the reusable mapping.

Cause: An input signature attribute in a reusable mapping is referenced by another component, but the input is not connected in the parent mapping.

Action: Assign an expression to the reusable mapping component input attribute.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16084: The proposed connection would create a circular graph.

Cause: The proposed connection would create a logical graph which contains a circular path, which connects a source component through some other components and back to itself.

Action: Fix the connections to get rid of the circular path.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16085: Cannot set an expression for attribute {0} because the attribute was not found. Available attributes: {1}.

Cause: SetAttributeExpressionText was called with an invalid attribute name.

Action: Specify a valid attribute name.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16086: Set component {0} input connector point {1}: set operator {2} is not valid for {3} technology.

Cause: The set operation chosen for the connector point is not valid for the technology.

Action: Choose a set operation valid for the technology.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16087: Generation of set component {0} failed because of an incompatibility with the technology.

Cause: The set operation chosen for the connector point is not valid for the technology.

Action: Choose a set operation valid for the technology.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16088: Map component {0}, attribute {1} contains an aggregate function. Aggregate functions are only supported by the aggregate component.

Cause: An aggregate function is used in the expression of a datastore attribute. The Datastore component does not support aggregate functions and will not generate the required GROUP BY clause.

Action: Create an aggregate component to contain the aggregate function.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16089: "Cannot connect to component {0}, no input connector points are available.

Cause: An attempt was made to connect to the component, but no input connector points are available.

Action: Fix the connection graph.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16090: "Attempt connect a component to itself. from={0}, to= {1}

Cause: An attempt was made to connect an output of the component back into an input of the same component.

Action: Do not connect a component to itself.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16091: Expression component {0} has no attributes.

Cause: An expression has no attributes. Expression components are projectors and must have attributes in order to be referenced by downstream components.

Action: Add one or more attributes to the expression component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16092: Datastore component {0}, attribute {1} is mandatory but not active.

Cause: A datastore attribute is mandatory, but has been tagged as non active.

Action: Set the mandatory attribute to active.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16093: The subselect option is not valid for reusable mapping component {0} because the reusable mapping contains an expression referencing a native sequence.

Cause: The reusable mapping has an expression referencing a native sequence, and the subselect option has been chosen for the reusable mapping component.

Action: Avoid using the subselect option for reusable mappings having expressions which reference native sequences.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16094: Physical node {0} is associated with logical schema {1}, but it is not mapped to a physical server in context {2}.

Cause: The physical schema of the physical node cannot be resolved, as its logical schema is not mapped in the execution context.

Action: Associate the logical schema with a physical schema in the context specified.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16095: "Scenario Generation failed for mapping {0} because no physical design was found.

Cause: No physical design was found during scenario generation for a mapping.

Action: Correct any errors preventing physical design generation.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16096: A mapping with name {0} already exists in folder {1}.

Cause: A mapping with the same name already exist in the same folder.

Action: Use a different name for the mapping.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16097: A reusable mapping with name {0} already exists in folder {1}.

Cause: A reusable mapping with the same name already exist in the same folder.

Action: Use a different name for the reusable mapping.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16098: A reusable mapping with name {0} already exists in global project.

Cause: A reusable mapping with the same name already exist in the global project.

Action: Use a different name for the reusable mapping.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16099: Name {0} already exists in {1} {2}.

Cause: The given name is already used. Object name needs to be unique with the parent object.

Action: Provide a different name for the object.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16100: Name cannot be an empty string.

Cause: Name of an object cannot be empty.

Action: Provide a name for the object.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16101: Name {0} contains invalid characters. Only letters, digits or underscore characters are allowed.

Cause: Proposed name contains invalid characters, such as space. Only letters, digits or underscore characters are allowed.

Action: Provide a different name for the object.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16102: Name {0} contains invalid characters. Only uppercase letters, digits or underscore characters are allowed, and the first character needs to be a letter.

Cause: Proposed name contains invalid characters, such as space. Only uppercase letters, digits or underscore characters are allowed, and the first character needs to be a letter.

Action: Provide a different name for the object.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16103: Name {0} is longer than {1} characters.

Cause: Proposed name is too long.

Action: Shorten the proposed name.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16104: The expression for attribute {0} cannot be resolved because it references an input signature which could not be redirected to an upstream expression. Input connector connections may be incorrect.

Cause: An expression references an input signature, but it could not be redirected to an expression upstream of the input signature. Invalid input connector point connections are the most common cause.

Action: Check all input connector points for correct upstream connections.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16105: Expression of attribute {0} does not refer to any upstream attribute. If {0} is an attribute of an input signature component, the corresponding attribute of the reusable mapping component does not have an expression text, or the input connector point of the reusable mapping component is not properly connected.

Cause: The expression is not set or the input connector point is not properly connected.

Action: Verify the expression or the connection to the input connector point.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16106: No columns are set to update column in Target datastore {0}.

Cause: The update indicator is not set in target datastore.

Action: Verify the targetDatastore attribute and set the update indicator.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16107: The data type for datastore component {0}, attribute {1} is not defined.

Cause: The data type of the column to which the datastore attribute is bound is null. This may occur when reverse engineering an unknown data type.

Action: Add the data type to the technology and set the data type of the column.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16108: Preset Staging Location explicitly set to target location. This may result in the addition of another execution unit and decreased performance. Consider using the default Preset Staging Location, which is already set to use the target location.

Cause: The preset staging location has been explicitly set, instead of using the default value. When an explicit value is set, and execution unit will be created, even if the location is the same as the target location.

Action: Consider using the default value for the preset staging location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16109: Encountered {0} at line {1} column {2}. Was expecting one of: {3}. The default parser supports ANSI SQL delimiters. If a non-standard syntax is desired, use the free-form expression delimiters /%% and %%/ around the expression.

Cause: A parser error was encountered when parsing the expression.

Action: Fix the syntax of the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16110: Non-ANSI natural join for component: {0} is not supported.

Cause: Natural join is set to generate non-ANSI syntax.

Action: Check the box for "Generate ANSI Syntax" under Join properties.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16111: Cannot remove {0} connector point for component {1} due to minimum connector point count violation.

Cause: Removal of connector point will result in connector point count less than minimum count.

Action: Do not remove connector point.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16112: Reusable mapping component {0}, output connector point {1} is not connected.

Cause: An output connector point of a reusable mapping component is not connected.

Action: Check that connections from all output connector points are optional.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16113: Mapping component {0} has no input or output connections.

Cause: An mapping component has not been connected.

Action: Connect the component to a source and/or target component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16114: Error when ordering the components for physical design:{0}, component re-ordering is not valid. A skipped component was not able to be placed in an execution unit because of dependency errors.

Cause: When attempting to reorder the component nodes in the physical graph, an eror was found.

Action: Do not reorder the component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16115: Cannot reorder an outer join node around another kind of node.

Cause: Cannot reorder an outer join node around another kind of node.

Action: Cannot reorder an outer join node around another kind of node.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16116: Cannot reorder a join around another join if one of the joins does not have at least 2 references in its join condition.

Cause: Illegal reordering.

Action: Do not reorder the component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16117: Cannot reorder a join around another join if one is generating ANSI and the other is not.

Cause: Illegal reordering.

Action: Do not reorder the component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16118: Cannot reorder a join around another join if one is a left or right outer join and the other is not the same type, for non-ANSI joins.

Cause: Illegal reordering.

Action: Do not reorder the component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16119: Cannot reorder a join around another join if either one is a left outer or right outer join, for ANSI joins.

Cause: Illegal reordering.

Action: Do not reorder the component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16120: Warning: Target Load Order -- Child component is ordered before parent component.

Cause: A datastore component with foreign key relationships is ordered before its parent datastore component.

Action: Change the load order to put parent component before child component or keep the load order knowing that it may result in error in loading due to missing primary record.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16121: Error: Target Load Order -- Load order is not consistent with processing graph from source to target. Please modify the graph or change the load order.

Cause: A target component is ordered before its source component.

Action: Change the load order to put source component before target component or change the mapping design.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16122: Cannot create physical design due to mapping validation errors: {0}.

Cause: Validation errors.

Action: Fix the mapping.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16123: Node pushed upstream causes conflicts due to multiple upstream connections from different execution units. Pushed node={0}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16124: Not allowed to reorder node {0}: {1}

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16125: Not allowed to push node {0} past node {1}: {2}

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16126: Physical graph re-ordering is causing a referencing problem for component: {0}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16127: Cannot reorder component that is not a selector:{0}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16128: Cannot reorder component that does not have at least one input and output connector point: {0}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16129: Cannot reorder a component that has multiple downstream targets: {0}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16130: Cannot reorder an outer join component: {0}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16131: The node will not be moved.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16132: Cannot reorder node {0} downstream of {1}, since {1} has expression references to {0}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16133: Cannot reorder node {0} upstream of {1}, since {0} has expression references to {1}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16134: Cannot set journalizing for datastore component {0}, since its bound datastore is not journalized.

Cause: Cannot set journalizing since the bound datastore is not journalized.

Action: Make sure the bound datastore is CDC enabled.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16135: File technology has limited capability to serve as a staging area. Consider switching the staging area to another technology, such as in-memory engine.

Cause: File technology unit set as staging area.

Action: Set staging area to non-file technology.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16136: Join {0} has type {1}, so its non-blank {2} will be ignored.

Cause: With Join Type CROSS or NATURAL, the Join Condition will be ignored.

Action: Check the Join Type. If correct, set the Join Condition to blank.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16137: IKM {0} is selected for physical node {1}, but the corresponding logical component {2} of reusable mapping {3} is not marked as derived sub-select.

Cause: An IKM is used for extraction of a physical node, but derived sub-select is not enabled.

Action: Change the KM selected for the physical node, or mark the logical component as derived sub-select.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16138: Internal error occurred during mapping metadata conversion. Please check the original 11g interface to see if it is complete and valid. Only interfaces that pass validation are supported during the upgrade process. If the 11g interface validates properly (in 11g) and then fails to upgrade cleanly, you should contact Oracle Support. The detailed exceptions information can be found in log file.

Cause: Internal error occurred or unexpected exception received during mapping metadata conversion.

Action: Make sure the original 11g interface is valid. If the 11g interface validates properly (in 11g) and then fails to upgrade cleanly, you should contact Oracle Support. The detailed exceptions information can be found in log file.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16139: Execution unit {0} does not have a location.

Cause: The execution unit does not have a logical schema selected for its location.

Action: Select a logical schema as the location of the execution unit.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16140: Mapping component {0} must have a connection for input connector point {1}.

Cause: An input connector point is not connected to another map component.

Action: Connect the input connector point to a source component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16141: Mapping component {0} must have a connection for output connector point {1}.

Cause: An output connector point is not connected to another map component.

Action: Connect the output connector point to a downstream component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16142: Cannot bind a datastore component to file model datastore {0}, use a file component instead.

Cause: Attempt to bind a datastore component to a datastore with file technology.

Action: Use a file component instead, and bind the file object to it.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16143: Cannot bind a file component to non-file model datastore {0}, use a datastore component instead.

Cause: Attempt to bind a file component to a datastore with non-file technology.

Action: Use a datastore component instead, and bind the file object to it.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16144: The expression cannot be pushed to execution unit {0} because its references would be out of scope.

Cause: Illegal push-to target execution unit for expression.

Action: Do not push the expression to this execution unit.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16145: The lookup match nth rows for lookup component {0} should be positive number.

Cause: The match nth row property has not been correctly configured for lookup component.

Action: Correct the match nth row property for lookup component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16146: The join condition for component {0} contains a filter expression that does not reference a different schema on each side of the equality operator: {1}. Filter expressions may not behave as expected in joins.

Cause: The join condition contains a filter expression. Filter expressions may not be effective in joins, and are inherently problematic in outer joins.

Action: Move the extra filter condition to a separate filter component to eliminate interaction with the join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16147: The join condition for component {0} does not contain an identifiable equality operator to join the input sources: {1}.

Cause: The join condition may be missing an equality operator needed to match rows when joining the input sources.

Action: Check the join expression for a valid equality operator.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16148: The size of map attribute {0} ({1}) is greater than the size of attribute {2} ({3}), to which it is mapped. Truncation or runtime errors are possible, depending on the technology.

Cause: A map attribute is mapped to an attribute of smaller size. This may result in data truncation or DML errors.

Action: Verify the size of both attributes and make any adjustments necessary to avoid truncation. Add an expression to explicitely truncate the data if necessary.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16149: For lookup component {0}, the option {1} for non matching rows may only be selected if option {2} is selected for multiple matching rows.

Cause: The no match rows property has not been correctly configured for lookup component. It may only be used if the multiple matching rows option specifies all rows.

Action: Correct the no match rows property for lookup component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16150: Multiple non-ANSI outer joins exist within a dataset for the same datastore {0}.

Cause: A datastore is outer joined to more than one datastore. This may result in execution errors.

Action: Create joins outside of datasets.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16151: The context value {0} for map component {1} does not map to a physical location.

Cause: The forced context value of a data storage component, combined with the model and logical schema, does not map to a physical schema. A map physical design cannot be created.

Action: Use the logical schema editor or SDK to set a physcial schema for the chosen component context.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16152: Error processing KM target expression for mapping: {0}, KM line: {1}, KM error: {2}

Cause: An exception was thrown during KM processing of the target expression for a particular line.

Action: Review the KM line and error to determine the cause.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16153: Error processing KM source expression for mapping: {0}, KM line: {1}, KM error: {2}

Cause: An exception was thrown during KM processing of the source expression for a particular line.

Action: Review the KM line and error to determine the cause.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16154: No expressions have been defined on the attributes for map component {0}.

Cause: A target datastore is connected, but none of its attributes have expressions defined.

Action: Create expressions to map one or more attributes to a source.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16155: Join or Lookup component {0} is inactive. Components joining sources must be active.

Cause: A join or lookup component has been set to inactive. Components which join sources must be active because all sources will not be in scope without the join.

Action: Set the component to active.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16156: Join type {0} in {1} cannot be supported due to circular relationships in Dataset {2}.

Cause: If a circle of relationships exist in a Dataset, one of the joinis must be reduced to a filter. The join type defined on it could be lost.

Action: Examine the logic in the Dataset and try to reduce the number of outer joins if possible as the currently specified logic in Dataset cannot be translated to a SQL query.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16157: Ambiguous expression reference due to split path. {0} Expression: {1}, Available paths: {2}

Cause: The connection path to the referenced attribute is split and the reference does not include a path specifier with a sufficient number of connector names to specify an unambiguous path..

Action: Add a path specifier qualifier to the expression reference.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16158: Component in path specifier has multiple output connector points. {0} Expression: {1}, Component={2}

Cause: A map component specified in the expression path specifier has multiple output connector points.

Action: A specific connector point must be specified in the path specifier.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16159: Path specifier contains nonexistent identifier. {0} Expression: {1}, Identifier={2}

Cause: An identifier specified in the expression path specifier is not found in the set of upstream components or connector points.

Action: Fix the path specifier in the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16160: Path specifier contains out-of-scope identifier. {0} Expression: {1}, Identifier={2}

Cause: An identifier specified in the expression path specifier is not found in the set of upstream components or connector points.

Action: Fix the path specifier in the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16161: No matching path can be found. {0} Expression: {1}

Cause: A path specifier is included in the expression, but it does not match any actual path in the map.

Action: Fix the path specifier in the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16162: Final parsing of {0} command {0} failed with exception {1}.

Cause: A final parsing of the command was performed and hit an error.

Action: Report as an ODI bug.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16163: Cannot parse identifier "{0}" because there are multiple instances of "{1}" in the mapping.

Cause: An identifier in the expression can not be parsed because it refers to multiple components.

Action: Fix the identifier in the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16164: Internal Error: Cannot find input query select item for expression cross reference: {0}

Cause: The code generator cannot generate code for the map expression cross reference because the upstream query does not include the referenced object.

Action: Fix the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16165: An attribute input expression for a set component must reference upstream attributes through only one input connector point. Attribute: {0}.

Cause: An attribute input expression for a set component must reference upstream attributes through only one input connector point.

Action: Check input expressions for the set component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16166: Cannot parse the syntax of user defined function or language element {0}: {1}.

Cause: The syntax text of the user defined function or language element cannot be parsed by the code generator.

Action: Check the syntax text of the user defined function or language element.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16167: The function call {0} does not match the number of parameters defined for user defined function or language element {1}.

Cause: The function call in the expression text does not match the number of parameters of the user defined function or language element.

Action: Check the function call in the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16168: Invalid parameter syntax in the syntax text of user defined function or language element {0}: {1}.

Cause: One of the parameters in the syntax text contains invalid parameter syntax.

Action: Check the syntax text of the user defined function or language element.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16169: Invalid parameter syntax in the implementation text of user defined function or language element {0}: {1}.

Cause: One of the parameters in the implementation text contains invalid parameter syntax.

Action: Check the implementation text of the user defined function or language element.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16170: Cannot locate calling parameter {0} in implementation text from the syntax text of user defined function or language element {1}.

Cause: The calling parameter in the implementation text does not match any parameters that are defined in the syntax of the user defined function or language element.

Action: Check the implementation text of the user defined function or language element.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16171: KM {0} is not valid for physical node {1}. The default KM is {2}.

Cause: The KM being set is not valid for the physical node.

Action: Set the KM using the default KM or another compatible KM.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16172: An expression in map component {0} cannot be resolved because it references an input signature which could not be redirected to an upstream expression. Input connector connections may be incorrect.

Cause: An expression references an input signature, but it could not be redirected to an expression upstream of the input signature. Invalid input connector point connections are the most common cause.

Action: Check all input connector points for correct upstream connections.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16173: Map component {0}, attribute {1} contains an expression which references a window function. Window functions are not valid for technology {2}.

Cause: An attribute expression references a window or analytical function, but the technology does not support window functions.

Action: Check the technology editor for window function support, and change the setting if the technology supports window functions. If not, the window function may not be used in the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16174: Map component {0}, property {1} contains an expression which references a window function. Window functions are not valid for technology {2}.

Cause: A property expression references a window or analytical function, but the technology does not support window functions.

Action: Check the technology editor for window function support, and change the setting if the technology supports window functions. If not, the window function may not be used in the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16175: Aggregate component {0}, attribute {1} contains an expression which references a window function. Window functions used within an aggregate component may result in errors or unexpected results.

Cause: An attribute expression in an aggregate component references a window or analytical function. Due to rowset cardinality differences between window functions and aggregate functions, window functions may be problematic in the context of an aggregation.

Action: Use window functions within a separate expression component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16176: The filter condition for component {0} references a window function. Window function calls are not valid in filter conditions.

Cause: A filter condition references a window or analytical function. Window functions are not valid in filter conditions.

Action: Use window functions within a separate expression component upstream of the filter component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16177: The join condition for component {0} references a window function. Window function calls are not valid in join conditions.

Cause: A join condition references a window or analytical function. Window functions are not valid in join conditions.

Action: Use window functions within a separate expression component upstream of the join component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16178: The lookup condition for component {0} references a window function. Window function calls are not valid in lookup conditions.

Cause: A lookup condition references a window or analytical function. Window functions are not valid in lookup conditions.

Action: Use window functions within a separate expression component upstream of the lookup component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16179: The subquery filter condition for component {0} references a window function. Window function calls are not valid in subquery filter conditions.

Cause: A subquery filter condition references a window or analytical function. Window functions are not valid in subquery filter conditions.

Action: Use window functions within a separate expression component upstream of the subquery filter component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16180: The split condition for component {0}, output connector point {1} references a window function. Window function calls are not valid in split conditions.

Cause: A split condition references a window or analytical function. Window functions are not valid in split conditions.

Action: Use window functions within a separate expression component upstream of the split component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16181: The expression for attribute {0}, connector point {1}, references a window function. Window functions may not be referenced in the subquery part of a subquery filter.

Cause: An expression for an attribute that participates in the subquery part of a subquery filter references a window or analytical function. Window functions are not valid in expressions which are part of the filter in a subquery filter.

Action: Use window functions within a separate expression component upstream of the subquery filter component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16182: The expression for {0} references a native sequence, which is not supported for technology {1}.

Cause: An expression for an attribute or property references a native sequence, but the execution technology does not support native sequences.

Action: Remove the native sequence reference from the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16183: Lookup component {0} specifies first, last, or nth row matching, but no order-by modifiers have been set on the attributes.

Cause: No order by modifiers have been set for the lookup attributes.

Action: Set an ASC or DESC order by modifier on one of the lookup attributes.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16184: Unable to fetch data from datastore {0}. The model {1} does not have a reverse-engineering context set.

Cause: Context associated with the logical schema does not exist.

Action: Check the context associated with the logical schema.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16185: {0} does not support single row selection from multiple matching rows.

Cause: The database technology does not support the analytical functions used to select a particular matching row.

Action: Select a lookup type which does not select a specified single row.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-17500: Invalid old password.

Cause: Old password did not match current password.

Action: Provide the correct password.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17501: Temporary table has no column.

Cause: No column have been defined for the temporary table.

Action: Define a column mapping to the temporary table.
Level: 32

Type: ERROR

Impact: Other

ODI-17502: No next value returned.

Cause: No sequence next value was found for given context code.

Action: Verify sequence definition or context code.
Level: 32

Type: ERROR

Impact: Other

ODI-17503: Internal error: object ConnectConnection

Cause: Missed connection.

Action: Try reconnect.
Level: 32

Type: ERROR

Impact: Other

ODI-17504: An ordered join references the same table twice (directly or indirectly).

Cause: A same table was referenced twice by a join.

Action: Check interface definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17505: An ordered join references the same table twice through another join.

Cause: A join was referencing the same table twice through another join.

Action: Check interface definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17506: Variable has no value

Cause: Variable had no value.

Action: Provide value for variable.
Level: 32

Type: ERROR

Impact: Other

ODI-17507: Key does not exist

Cause: Key was unknown.

Action: Provide a known key.
Level: 32

Type: ERROR

Impact: Other

ODI-17508: No conversion for data type "{0}" from source technology "{1}" to destination technology "{2}"

Cause: No data type conversion between technology was found.

Action: Define corresponding data type conversion.
Level: 32

Type: ERROR

Impact: Other

ODI-17509: Query to access value for specific sequence {0} has failed. Query="{1}"

Cause: Query for sequence has failed.

Action: Check sequence definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17510: Driver does not exist.

Cause: Driver was not found.

Action: Check repository.
Level: 32

Type: ERROR

Impact: Other

ODI-17511: No value to be set to variable ''{0}''.

Cause: No value was returned to be set to the variable.

Action: Check variable value.
Level: 32

Type: ERROR

Impact: Other

ODI-17512: Sequence is already locked

Cause: The sequence was already locked.

Action: Unlock the sequence.
Level: 32

Type: ERROR

Impact: Other

ODI-17513: Variable ''{0}'' does not exist.

Cause: Variable was not found.

Action: Check variable.
Level: 32

Type: ERROR

Impact: Other

ODI-17514: Unrecognized Oracle Data Integrator built-in function: {0}

Cause: Oracle Data Integrator built-in function was not recognized.

Action: Check function syntax.
Level: 32

Type: ERROR

Impact: Other

ODI-17515: Invalid loading command (INSERT,UPDATE...).

Cause: Loading command was invalid.

Action: Check loading command.
Level: 32

Type: ERROR

Impact: Other

ODI-17516: Internal error within the connection list

Cause: Internal error within the connection list.

Action: Try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17517: Error during task interpretation. Task: {0} {1} Text: {2}.

Cause: A task interpretation error has occured.

Action: Check tasks and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17518: Error while interpreting the user name.

Cause: User name interpretation has failed.

Action: Check user name.
Level: 32

Type: ERROR

Impact: Other

ODI-17519: Error while interpreting the URL

Cause: URL interpretation has failed

Action: Check URL.
Level: 32

Type: ERROR

Impact: Other

ODI-17520: Error while interpreting the password

Cause: Password interpretation has failed.

Action: Check password.
Level: 32

Type: ERROR

Impact: Other

ODI-17521: Error while interpreting the driver

Cause: Driver interpretation has failed.

Action: Check driver.
Level: 32

Type: ERROR

Impact: Other

ODI-17522: Empty column name are not allowed

Cause: A empty column name was found.

Action: Fill column name.
Level: 32

Type: ERROR

Impact: Other

ODI-17523: There is no connection for this logical schema / context pair: {0} / {1}.

Cause: No connection was found for this logical schema / context pair.

Action: Check schema and context assignment.
Level: 32

Type: ERROR

Impact: Other

ODI-17524: Cannot set an empty alias for a source table.

Cause: Source table''s alias was empty.

Action: Fill alias of source table.
Level: 32

Type: ERROR

Impact: Other

ODI-17525: Cannot set an empty source set name.

Cause: Source set name was empty.

Action: Fill alias of a source table.
Level: 32

Type: ERROR

Impact: Other

ODI-17526: Cannot set Longc value in a PopCol having a column

Cause: Cannot set Longc value in a PopCol having a column.

Action: Check interface`s columns.
Level: 32

Type: ERROR

Impact: Other

ODI-17527: Cannot set SourceDt value in a PopCol having a column

Cause: Cannot set SourceDt value in a PopCol having a column.

Action: Check interface`s columns.
Level: 32

Type: ERROR

Impact: Other

ODI-17528: Cannot set Scalec value in a PopCol having a column

Cause: Cannot set Scalec value in a PopCol having a column.

Action: Check interface`s columns.
Level: 32

Type: ERROR

Impact: Other

ODI-17529: Reference check failure

Cause: Reference check has failed.

Action: Check control conditions.
Level: 32

Type: ERROR

Impact: Other

ODI-17530: Incomplete join may result in partial cross join

Cause: An incomplete join was found.

Action: Check joins.
Level: 32

Type: ERROR

Impact: Other

ODI-17531: KM already encrypted.

Cause: KM has been already encrypted.

Action: Skip encryption.
Level: 32

Type: ERROR

Impact: Other

ODI-17532: KM not encrypted.

Cause: KM was not encrypted.

Action: Check KM.
Level: 32

Type: ERROR

Impact: Other

ODI-17533: Clause set to cross join on a technology that does not support cross joins.

Cause: Technology did not support cross joins.

Action: Correct joins.
Level: 32

Type: ERROR

Impact: Other

ODI-17534: Clause set to full join on a technology that does not support full joins.

Cause: Technology did not support full joins.

Action: Correct joins.
Level: 32

Type: ERROR

Impact: Other

ODI-17535: Clause set to outer join on a technology that does not support left outer joins or right outer joins.

Cause: Technology did not support left outer joins.

Action: Correct joins.
Level: 32

Type: ERROR

Impact: Other

ODI-17536: Incomplete clause (Missing order number).

Cause: Order number was missing.

Action: Correct clause.
Level: 32

Type: ERROR

Impact: Other

ODI-17537: Incomplete clause (table1 and/or table2 must be set).

Cause: Table1 and/or table2 were undefined.

Action: Set clause''s table1 and/or table2 tables.
Level: 32

Type: ERROR

Impact: Other

ODI-17538: Filter is not properly set (The table must be defined)

Cause: The table must have been set.

Action: Set filter''s table.
Level: 32

Type: ERROR

Impact: Other

ODI-17539: Clause is ordered on a technology that does not support it

Cause: Technology did not support ordering.

Action: Remove ordering.
Level: 32

Type: ERROR

Impact: Other

ODI-17540: Connection is not set for this source set {0}.

Cause: Source set''s connection was not set.

Action: Set connection.
Level: 32

Type: ERROR

Impact: Other

ODI-17541: Method SnpTrt::getAllTrtOfTypeForTechnosAndProject requires not null parameters for technologies

Cause: Method requires not null parameters

Action: Specify correct parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-17542: Sequence must be locked before using this function

Cause: Sequence was not locked.

Action: Lock sequence and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17543: Technology does not support joins

Cause: Technology did not support joins.

Action: Check technology and/or joins.
Level: 32

Type: ERROR

Impact: Other

ODI-17544: This Technology does not support the WHERE clause

Cause: Technology did not support the WHERE clause

Action: Check technology and/or clause.
Level: 32

Type: ERROR

Impact: Other

ODI-17545: Technology not set for this source set {0}

Cause: Source set''s technology was undefined.

Action: Set technology.
Level: 32

Type: ERROR

Impact: Other

ODI-17546: Specified variable not found in the Repository

Cause: Variable was not found in the Repository.

Action: Define variable and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17547: Data type "{0}" for the technology "{1}" does not exist.

Cause: Data type for the technology did not exist.

Action: Check data type and/or technology.
Level: 32

Type: ERROR

Impact: Other

ODI-17548: The file reverse-engineering is only possible for delimited files.

Cause: The file reverse-engineering was performed against a not delimited file.

Action: Use delimited files.
Level: 32

Type: ERROR

Impact: Other

ODI-17549: Source data type "{0}" for the technology "{1}" does not exist.

Cause: Source data type was not found.

Action: Check data type and/or technology.
Level: 32

Type: ERROR

Impact: Other

ODI-17550: Missing default Physical Schema for Data Server "{0}"

Cause: Default Physical Schema was undefined.

Action: Specify default Physical Schema.
Level: 32

Type: ERROR

Impact: Other

ODI-17551: Duplicate clause order numbers

Cause: Duplicated order numbers were found.

Action: Check clause definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17552: Duplicate join order numbers

Cause: Duplicated join order numbers were found.

Action: Check join.
Level: 32

Type: ERROR

Impact: Other

ODI-17553: Exceeded the maximum number of errors allowed.

Cause: The maximum number of errors allowed were exceeded.

Action: Check maximum error numbers.
Level: 32

Type: ERROR

Impact: Other

ODI-17554: Agent "{0}" does not exist.

Cause: Agent was not found.

Action: Check agent definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17555: You cannot unlock this object. Only the lock owners and Supervisors can unlock objects.

Cause: An attempt was made to unlock objects that were locked by another user.

Action: Login as Supervisor or as the lock owners and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17556: Error during decryption of text.

Cause: Text decryption has failed.

Action: Try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17557: No condition defined for this rule.

Cause: No condition have been defined for this rule.

Action: Define conditions.
Level: 32

Type: ERROR

Impact: Other

ODI-17558: The field for this rule is not specified.

Cause: The field was unspecified.

Action: Specify field for this rule.
Level: 32

Type: ERROR

Impact: Other

ODI-17559: The operator for this rule is not specified.

Cause: The operator was unspecified.

Action: Specify operator for this rule.
Level: 32

Type: ERROR

Impact: Other

ODI-17560: The value to test is not defined.

Cause: The value to test was not defined.

Action: Specify value.
Level: 32

Type: ERROR

Impact: Other

ODI-17561: This operator is not supported.

Cause: This operator was not supported.

Action: Correct operator.
Level: 32

Type: ERROR

Impact: Other

ODI-17562: This operator cannot be used with this field.

Cause: The operator could not be used with the given field.

Action: Correct operator.
Level: 32

Type: ERROR

Impact: Other

ODI-17563: There is no work repository matching the name "{0}".

Cause: Work repository was not found.

Action: Check work repository with the given name exists.
Level: 32

Type: ERROR

Impact: Other

ODI-17564: More than one work repository found with the name "{0}" for this master repository.

Cause: More than one work repository with the specified name was found for this master repository.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-17565: Scenario has been already encrypted. No encryption was performed.

Cause: Scenario has been already encrypted.

Action: Decrypt and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17566: Scenario is not encrypted. No decryption was performed.

Cause: Scenario was not encrypted.

Action: Check Scenario.
Level: 32

Type: ERROR

Impact: Other

ODI-17567: A Scenario generated from a Variable cannot be encrypted or decrypted.

Cause: An attempt was made to encrypte or decrypte a Scenario generated from a Variable.

Action: Change Scenario'' source component.
Level: 32

Type: ERROR

Impact: Other

ODI-17568: Could not connect to the database referenced by the context and the logical schema

Cause: Connection to the database failed.

Action: Check context and logical schema.
Level: 32

Type: ERROR

Impact: Network

ODI-17569: Unable to update sequence''s next value.

Cause: Updating sequence was not possible.

Action: Check sequence definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17570: Your text is too long. Please shorten it or choose the ''LONG TEXT'' datatype.

Cause: Text was too long.

Action: Shorten the text or choose the LONG TEXT data type.
Level: 32

Type: ERROR

Impact: Other

ODI-17571: Password does not respect the following rule: "{0}".

Cause: The password did not respect the rule.

Action: Choose another password.
Level: 32

Type: ERROR

Impact: Security

ODI-17572: This SnpFfValuee does not exist.

Cause: Value was not found.

Action: Check FlexField value.
Level: 32

Type: ERROR

Impact: Other

ODI-17573: This SnpFfValuem does not exist.

Cause: Value was not found.

Action: Check FlexField value.
Level: 32

Type: ERROR

Impact: Other

ODI-17574: This SnpFfValuew does not exist.

Cause: Value was not found.

Action: Check FlexField value.
Level: 32

Type: ERROR

Impact: Other

ODI-17575: SnpLicense does not exist.

Cause: SnpLicense was not found.

Action: Check License.
Level: 32

Type: ERROR

Impact: Other

ODI-17576: Unknown actual constraint type for an interface constraint.

Cause: Interface constraint type was unknown.

Action: Check constraint type.
Level: 32

Type: ERROR

Impact: Other

ODI-17577: Unknown variable data type.

Cause: Variable data type was unknown.

Action: Check variable data type.
Level: 32

Type: ERROR

Impact: Other

ODI-17578: Name "{0}" is already used.

Cause: Name was already used.

Action: Use another name or change mode of import.
Level: 32

Type: ERROR

Impact: Other

ODI-17579: Type of clause is not set.

Cause: Type of clause was not set.

Action: Set type of clause.
Level: 32

Type: ERROR

Impact: Other

ODI-17580: Type of join is not set.

Cause: Type of join was not set.

Action: Set type of join.
Level: 32

Type: ERROR

Impact: Other

ODI-17581: A non ordered clause is passed to the construction of ordered joins trees method.

Cause: A non ordered clause was passed to the construction of ordered joins trees method.

Action: Check clauses.
Level: 32

Type: ERROR

Impact: Other

ODI-17582: Missing order number for an ordered clause.

Cause: Clause order was not set.

Action: Set the clause order.
Level: 32

Type: ERROR

Impact: Other

ODI-17583: More than one unique constraint associated to an interface constraint.

Cause: More than one unique constraint associated to an interface constraint was found.

Action: Check constraints.
Level: 32

Type: ERROR

Impact: Other

ODI-17584: URL does not exist.

Cause: URL was not found.

Action: Check URL.
Level: 32

Type: ERROR

Impact: Other

ODI-17585: Key cannot be checked.

Cause: Key could not be checked.

Action: Check key definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17586: Field separator is mandatory for a delimited file.

Cause: Field separator was missing.

Action: Check separator and/or file type.
Level: 32

Type: ERROR

Impact: Other

ODI-17587: Object name "{0}" is too long for the technology "{1}" (Logical schema : "{2}" ; Context Code : "{3}")

Cause: Object name was too long.

Action: Correct object name.
Level: 32

Type: ERROR

Impact: Other

ODI-17588: Unable to load work repository info.

Cause: Work repository was not found.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-17589: Logical schema has not been specified for sequence "{0}"

Cause: Logical schema was not specified.

Action: Specify logical schema.
Level: 32

Type: ERROR

Impact: Other

ODI-17590: Code {0} for model "{1}" is already used by another model.

Cause: An already used code was assigned.

Action: Change code for model.
Level: 32

Type: ERROR

Impact: Other

ODI-17591: Name "{0}" is already used.

Cause: A name already used was assigned.

Action: Change name.
Level: 32

Type: ERROR

Impact: Other

ODI-17592: Object is not in execution work repository.

Cause: Object was not in execution work repository.

Action: Check object and/or repository.
Level: 32

Type: ERROR

Impact: Other

ODI-17593: Maximum number or source/target technologies exceeded. Current limit is {0}.

Cause: Maximum number or source/target technologies was exceeded.

Action: Check limit and number of technologies.
Level: 32

Type: ERROR

Impact: Other

ODI-17594: Cannot encrypte already encrypted action.

Cause: This action has been already encrypted.

Action: Skip encryption.
Level: 32

Type: ERROR

Impact: Other

ODI-17595: This action is not encrypted.

Cause: This action was not encrypted.

Action: Check parameters and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17596: Query to retrieve value for native sequence "{0}" has failed Query="{1}"

Cause: Query has failed.

Action: Check query.
Level: 32

Type: ERROR

Impact: Other

ODI-17597: Cannot mix ordered and non-ordered join syntax within a dataset for technology.

Cause: Mixed join not allowed within a dataset.

Action: Change all joins in dataset to same join syntax (either ordered or non-ordered).
Level: 32

Type: ERROR

Impact: Other

ODI-17598: Non-ordered natural join is not supported.

Cause: Non-ordered natural join is not supported.

Action: Change natural join to use ordered syntax.
Level: 32

Type: ERROR

Impact: Other

ODI-17599: Ordered inner join is not supported.

Cause: Ordered inner join is disabled for technology.

Action: Change join type.
Level: 32

Type: ERROR

Impact: Other

ODI-17600: Ordered left outer join is not supported.

Cause: Ordered left outer join is disabled for technology.

Action: Change join type.
Level: 32

Type: ERROR

Impact: Other

ODI-17601: Ordered right outer join is not supported.

Cause: Ordered right outer join is disabled for technology.

Action: Change join type.
Level: 32

Type: ERROR

Impact: Other

ODI-17602: Non-ordered full outer join is not supported.

Cause: Non-ordered full outer join is not supported.

Action: Change full outer join to use ordered syntax.
Level: 32

Type: ERROR

Impact: Other

ODI-17603: Sql error checking a condition. {0}

Cause: Sql error checking a condition.

Action: Correct the Sql in the condition.
Level: 32

Type: ERROR

Impact: Other

ODI-17604: Reference column isn't associated with this instance of reference.

Cause: Reference column isn't associated with this instance of reference.

Action: Check reference column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17605: Column is not associated to this datastore.

Cause: Datastore doesn't have this column.

Action: Check datastore and column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17606: {0} already belongs to another OdiDataStore.

Cause: Object belongs to another datastore.

Action: Check object and datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17607: Parameter pReference is not an outbound reference for this OdiDataStore.

Cause: Parameter is not an outbound reference for OdiDataStore.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17608: Invalid technology for the given data type.

Cause: Invalid technology for the given data type.

Action: Check technology.
Level: 32

Type: ERROR

Impact: Other

ODI-17609: Invalid data type code.

Cause: Invalid data type code.

Action: Check data type code.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17610: Found NULL in STEP_TYPE.

Cause: Step type is null.

Action: Check step type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17611: STEP_TYPE is not valid.

Cause: Step type isn't valid.

Action: Check step type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17612: MultiConnectionSupported is not settable for {0}.

Cause: MultiConnectionSupported is not settable.

Action: Check knowledge module.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17613: Cannot handle {0} of type {1}.

Cause: Cannot handle object.

Action: Check object's type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17614: Unknown key type: {0}.

Cause: Unknown key type.

Action: Check key.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17615: The command is not an ODI Tool command.

Cause: Wrong command.

Action: Check command.
Level: 32

Type: ERROR

Impact: Other

ODI-17616: No WorkTextOrig was found for ID: {0}.

Cause: Invalid ID.

Action: Check ID.
Level: 32

Type: ERROR

Impact: Other

ODI-17617: Class descriptor for WorkTextOrig [ {0} ] is null.

Cause: Descriptor is null.

Action: Check class descriptors.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17618: Unable to deal with an AliasedColumnCrossRef with type {0}.

Cause: Incorrect column type.

Action: Check column type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17619: Unexpected CrossRef {0} type.

Cause: Incorrect CrossRef type.

Action: Check CrossRef.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17620: Object type is not valid.

Cause: Object type is not valid.

Action: Check object type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17621: Unable to manage crossRef for object from class [ {0} ].

Cause: Illegal object type.

Action: Check object type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17622: pSqlIndGroup is not a valid group type.

Cause: Invalid group type.

Action: Check type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17623: Too many parameters for function {0}, Object {1}, Language {2}.

Cause: Too many parameters.

Action: Check parameters count.
Level: 32

Type: ERROR

Impact: Other

ODI-17624: Missing parameter for function {0}, Object {1}, Language {2}.

Cause: Missing parameter.

Action: Check parameters count.
Level: 32

Type: ERROR

Impact: Other

ODI-17625: Only OdiColumns are currently supported for SnpsExpressionTag.

Cause: Wrong column type.

Action: Check column type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17626: Cannot reassign a DataType.

Cause: Technology has been assigned yet.

Action: Check DataType
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17627: Inconsistent connection settings.

Cause: Inconsistent connection settings.

Action: Check connection settings type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17628: Unknown IConnectionSettings implementation.

Cause: Unknown IConnectionSettings implementation.

Action: Check settings type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17629: Connection Settings for repository server must be instanceof JdbcSettings.

Cause: Wrong settings type.

Action: Check settings type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17630: Unknown OptionType.

Cause: Unknown OptionType.

Action: Check option type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17631: The given class has no matching OverridenOptionOrig.

Cause: The given class has no matching OverridenOptionOrig.

Action: Check class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17632: Unexpected variable type.

Cause: Unexpected variable type.

Action: Check variable type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17633: {0} datatype is expected.

Cause: Wrong value datatype.

Action: Check value datatype.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17634: Parameter must have text; it must not be null or empty.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17635: Parameter must have text; it must not be null, empty, or blank.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17636: Parameter {0} must be false.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17637: Parameter must not be null.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17638: Parameter {0} must be null.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17639: Parameter must be null.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17640: Parameter {0} must have text; it must not be null or empty.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17641: No {0} matches this IObject: {1}.

Cause: IObject is not matched.

Action: Check class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17642: No Entity Class matches this Snp Class: {0}.

Cause: No Entity Class matches Snp Class.

Action: Check Entity Class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17643: No Snp Class matches this Entity Class: {0}.

Cause: No Snp Class matches Entity Class.

Action: Check Snp Class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17644: Unknown FlexFieldType.

Cause: Unknown FlexFieldType.

Action: Check FlexFieldType type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17645: Parameter must be instance of {0}.

Cause: Wrong parameter type.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17646: It is forbidden to use a variable of one project in a package of another project.

Cause: Variable and package have different parents.

Action: Check variable and package.
Level: 32

Type: ERROR

Impact: Other

ODI-17647: Unable to create the expression element, Object {0}, Language {1}.

Cause: Unable to create the expression element.

Action: Check expression parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-17648: A mapping cannot be on the target.

Cause: A mapping cannot be on the target.

Action: Check execution location.
Level: 32

Type: ERROR

Impact: Other

ODI-17649: Can't create join between 2 source datastore from different DataSet.

Cause: Source datastores are from different DataSet.

Action: Correct join.
Level: 32

Type: ERROR

Impact: Other

ODI-17650: A {0} was expected as value since {1} is {2}.

Cause: Wrong type.

Action: Check type.
Level: 32

Type: ERROR

Impact: Other

ODI-17651: Parameter {0} must be instance of [{1}].

Cause: Wrong parameter class.

Action: Check parameter class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17652: Class {0} is not assignable to {1}.

Cause: Inconsistent classes.

Action: Check classes.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17653: {0} line isn't found.

Cause: Missed line.

Action: Check line count.
Level: 32

Type: ERROR

Impact: Other

ODI-17654: Parameter {0} must not be null.

Cause: Parameter must be not null.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17655: Parameter {0} must be {1} characters long max.

Cause: Parameter length is too long.

Action: Check parameter length.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17656: Can't define variable override for steps in exception tree.

Cause: Step is in exception tree.

Action: Check step and variable for consistency.
Level: 32

Type: ERROR

Impact: Other

ODI-17657: Cannot add a reference column to an OdiReference with type [{0}].

Cause: Reference type isn't ReferenceType.COMPLEX_REFERENCE.

Action: Check reference type.
Level: 32

Type: ERROR

Impact: Other

ODI-17658: Cannot change the target table because it's not a temporary datastore.

Cause: Datastore isn't temporary.

Action: Check target table and datastore.
Level: 32

Type: ERROR

Impact: Other

ODI-17659: Cannot get the journalized columns of a non-journalized datastore.

Cause: Datastore isn't journalized.

Action: Check datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17660: Cannot set a clause on the target.

Cause: Wrong execution location.

Action: Check execution location.
Level: 32

Type: ERROR

Impact: Other

ODI-17661: {0} is not supported for this Technology.

Cause: Object is not supported for this Technology.

Action: Check topology.
Level: 32

Type: ERROR

Impact: Other

ODI-17662: Parameter {0} must have text; it must not be null, empty, or blank.

Cause: Incorrect parameter.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17663: Parameter {0} must be uppercase.

Cause: Parameter is lower case.

Action: Check parameter case.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17664: Parameter {0} must not contain whitespaces.

Cause: Parameter contains whitespaces.

Action: Consider to replace whitespace with another symbold (e.g. underscore)
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17665: Column is not associated with this instance of OdiKey.

Cause: Column is not associated with instance of OdiKey.

Action: Check column and OdiKey.
Level: 32

Type: ERROR

Impact: Other

ODI-17666: Column is not present in the key.

Cause: Column is not present in the key.

Action: Check column and key.
Level: 32

Type: ERROR

Impact: Other

ODI-17667: Data type should be set before accessing value.

Cause: Illegal method usage.

Action: Set Data type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17668: Datastore already has a Primary Key.

Cause: Datastore already has a Primary Key.

Action: Remove the current primary key before adding a new one.
Level: 32

Type: ERROR

Impact: Other

ODI-17669: {0} must be set before calling method {1}.

Cause: Illegal method usage.

Action: Set actual value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17670: Default implementation already exists.

Cause: Default implementation already exists.

Action: Check function implementation.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17671: {0} must not be negative.

Cause: Wrong parameter value.

Action: Set value to 0 or greater.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17672: FlexFields isn''t initialized.

Cause: FlexFields isn''t initialized.

Action: Call initFlexFields method first.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17673: Foreign key column''s datastore must be equals to this reference''s foreign datastore.

Cause: Inconsistent datastores.

Action: Check datastore.
Level: 32

Type: ERROR

Impact: Other

ODI-17674: IncrementValue is not set.

Cause: IncrementValue is not set.

Action: Set IncrementValue with setVariable method.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17675: Invalid step log's status.

Cause: Step status is not RUNNING.

Action: Check step status.
Level: 32

Type: ERROR

Impact: Other

ODI-17676: Invalid value type.

Cause: Invalid value type.

Action: Check value type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17677: Cycle could be defined in {0} hierarchy.

Cause: It is forbidden to define cycle in {0} hierarchy.

Action: Check hierarchy.
Level: 32

Type: ERROR

Impact: Other

ODI-17678: It is forbidden to fill a key with columns from another datastore.

Cause: It is forbidden to fill a key with columns from another datastore.

Action: Check datastore.
Level: 32

Type: ERROR

Impact: Other

ODI-17679: It is forbidden to link two steps from different packages.

Cause: Steps are from different packages.

Action: Check steps and packages.
Level: 32

Type: ERROR

Impact: Other

ODI-17680: Line wasn't found.

Cause: Line wasn't found.

Action: Check procedure lines.
Level: 32

Type: ERROR

Impact: Other

ODI-17681: Maximum number of sessions must be positive.

Cause: Wrong value.

Action: Check maximum number.
Level: 32

Type: ERROR

Impact: Other

ODI-17682: Method is not valid unless MultiConnectionSupported.

Cause: MultiConnectionSupported is true.

Action: Check procedure.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17683: Model must be in Customized mode.

Cause: Wrong model mode.

Action: Call setReverseType(ReverseType.CUSTOMIZED).
Level: 32

Type: ERROR

Impact: Other

ODI-17684: Name can't be set.

Cause: Name is computed.

Action: Check name.
Level: 32

Type: ERROR

Impact: Other

ODI-17685: No {0} is defined for this model.

Cause: Missed definition.

Action: Define CKM for model.
Level: 32

Type: ERROR

Impact: Other

ODI-17686: No valid {0} name was found from this qualified name.

Cause: Valid name wasn't found.

Action: Check qualified name.
Level: 32

Type: ERROR

Impact: Other

ODI-17687: No valid qualified name was provided.

Cause: Name is invalid.

Action: Check qualified name.
Level: 32

Type: ERROR

Impact: Other

ODI-17688: OdiScenario is undefined.

Cause: OdiScenario is undefined.

Action: Check OdiScenario definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17689: Option must be in the same procedure as line.

Cause: Option procedure is inconsistent.

Action: Check option procedure.
Level: 32

Type: ERROR

Impact: Other

ODI-17690: Package and procedure must be owned by the same project.

Cause: Procedure parent is inconsistent.

Action: Check procedure parent.
Level: 32

Type: ERROR

Impact: Other

ODI-17691: Primary key column's datastore must be equals to this reference's primary datastore.

Cause: Column datastore is inconsistent.

Action: Check datastores.
Level: 32

Type: ERROR

Impact: Other

ODI-17692: Reference column doesn't belong to this reference.

Cause: Column is inconsistent.

Action: Check column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17693: Reference's foreign datastore is not equal to this datastore.

Cause: Datastores are inconsistent.

Action: Check datastores.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17694: Steps can't be moved from one package to another.

Cause: Steps can't be moved from one package to another.

Action: Conside not to move steps.
Level: 32

Type: ERROR

Impact: Other

ODI-17695: The new position is not valid.

Cause: The new position is not valid.

Action: Check new position.
Level: 32

Type: ERROR

Impact: Other

ODI-17696: The option already exists.

Cause: The option already exists.

Action: Check option.
Level: 32

Type: ERROR

Impact: Other

ODI-17697: The option owner has already been set.

Cause: The option owner has already been set.

Action: Check option owner.
Level: 32

Type: ERROR

Impact: Other

ODI-17698: The reference type must be [ {0} ] in order to define a complex SQL expression.

Cause: Wrong reference type.

Action: Check reference type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17699: The reference type must be [ {0} ] in order to obtain the complex SQL expression.

Cause: Wrong reference type.

Action: Check reference type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17700: The string value length should not exceed MAX_SHORT_TEXT_LENGTH since FlexFieldType is SHORT_TEXT.

Cause: FlexFieldType is SHORT_TEXT.

Action: Check FlexFieldType and string value length.
Level: 32

Type: ERROR

Impact: Other

ODI-17701: This OdiLoadPlanInstanceRun is not ESS Job related.

Cause: OdiLoadPlanInstanceRun is not ESS Job related.

Action: Check OdiLoadPlanInstanceRun.
Level: 32

Type: ERROR

Impact: Other

ODI-17702: This session is not ESS Job related.

Cause: Session is not ESS Job related.

Action: Check session.
Level: 32

Type: ERROR

Impact: Other

ODI-17703: This OdiReference must be from type [{0}] in order to access the primary DataStore alias.

Cause: Wrong OdiReference type.

Action: Check OdiReference type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17704: This OdiReference must be from type [{0}] in order to set the primary DataStore alias.

Cause: Wrong OdiReference type.

Action: Check OdiReference type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17705: This file descriptor is not consistent with the parent model's technology.

Cause: File descriptor is not consistent.

Action: Check file descriptor and parent technology.
Level: 32

Type: ERROR

Impact: Other

ODI-17706: This setVariable is used for increment.

Cause: Increment value is set.

Action: Use method getIncrementValue().
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17707: Unable to add an alien main partition.

Cause: Main partition datastore is inconsistent.

Action: Check main partition.
Level: 32

Type: ERROR

Impact: Other

ODI-17708: Unable to compute name.

Cause: Name has been set on this physical schema.

Action: Do not compute name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17709: Parameter must be false.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17710: Parameter {0} must be true.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17711: Undefined ODI work repository name.

Cause: Undefined repository name.

Action: Check repository name.
Level: 32

Type: ERROR

Impact: Other

ODI-17712: Variable and Step should be defined in the same Load Plan.

Cause: Variable and Step have different parent Load Plans.

Action: Define variable and step in the same Load Plan.
Level: 32

Type: ERROR

Impact: Other

ODI-17713: VariableDataType should be set before accessing DefaultValue.

Cause: VariableDataType is undefined.

Action: Set VariableDataType.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17714: You can only set KMs contained in the OdiProject containing of the OdiInterface.

Cause: KM has different parent project than OdiInterface.

Action: Check KM.
Level: 32

Type: ERROR

Impact: Other

ODI-17715: Can't add a null variable to load plan.

Cause: Variable is null.

Action: Check variable value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17716: DataTypes must be consistent.

Cause: DataTypes is inconsistent.

Action: Check DataTypes.
Level: 32

Type: ERROR

Impact: Other

ODI-17717: Constraint is not a condition.

Cause: Inconsistent constraint type.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17718: Constraint is not a key.

Cause: Inconsistent constraint type.

Action: Check constraint.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17719: Option is not associated to this procedure.

Cause: Option is not associated to this procedure.

Action: Check option and procedure.
Level: 32

Type: ERROR

Impact: Other

ODI-17720: Constraint is not a reference.

Cause: Inconsistent constraint type.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17721: Parameter {0} already belongs to {1}.

Cause: Parameter has parent.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17722: Parameter {0} does not belong to this instance of {1}.

Cause: Parameter has different parent.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17723: Parameter {0} must belong to this {1}.

Cause: Parameter parent is inconsistent.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17724: Parameter {0} can't be moved to an other {1}.

Cause: Parameter can't be moved.

Action: Do not move parameter.
Level: 32

Type: ERROR

Impact: Other

ODI-17725: Parameter {0} must start with {1} prefix.

Cause: Parameter has wrong prefix.

Action: Check parameter prefix.
Level: 32

Type: ERROR

Impact: Other

ODI-17726: Logical Agent {0} must be mapped to a Physical Agent in the ContextCode {1}.

Cause: Agent is null.

Action: Check agents.
Level: 32

Type: ERROR

Impact: Other

ODI-17727: pDataServiceContainer is not a data service.

Cause: pDataServiceContainer is not a data service.

Action: Check pDataServiceContainer.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17728: Package and interface must be owned by the same project.

Cause: Package and interface have different parents.

Action: Check package and interface.
Level: 32

Type: ERROR

Impact: Other

ODI-17729: Parameter must be true.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17730: Not legal for shortcut.

Cause: Object is shortcut.

Action: Use getShortcutBaseObject() to access the real object.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17731: Not legal to construct a shortcut from a datastore in a model with a different technology.

Cause: Inconsistent technologies.

Action: Check model and datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17732: Odi object Must be shortcut after materialize.

Cause: Object isn't shortcut.

Action: Check object.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17733: Reference's primary datastore must be not null in order to define a ReferenceColumn.

Cause: Primary DataStore is null.

Action: Check DataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17734: pDataServiceContainer {0} has no technology defined.

Cause: Data Service Container has no technology defined.

Action: Define technology.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17735: Reference's foreign datastore is not equals to this datastore.

Cause: Reference's foreign datastore is not equals to this datastore.

Action: Check DataStores.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17736: You can only set global KMs or KMs contained in the OdiProject containing the OdiInterface.

Cause: Wrong KM.

Action: Check KM and project.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17737: StepLog and Variable don't belong to the same session.

Cause: Inconsistent session.

Action: Check Session value for StepLog and Variable.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17738: Unable to find '{0}' as variable used by the scenario '{1}' in version '{2}'.

Cause: Variable is null.

Action: Check variable name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17739: Unable to override '{0}' variable for execution. It is marked as read-only for scenario '{1}' in version '{2}'.

Cause: Variable is read-only.

Action: Check variable.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17740: Error while connecting to the Application Server at URL {0}.

Cause: Exception was thrown during connection.

Action: Ensure that the Application Server is running and accepting requests.
Level: 32

Type: ERROR

Impact: Network

ODI-17741: Datastore isn't used as a lookup source.

Cause: Datastore isn't used as a lookup source.

Action: Check Datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17742: Parameter {0} must be greater or equal than {1} and less or equal than {2}.

Cause: Wrong parameter value

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17743: Variable should be related to the same {0}.

Cause: Wrong parent for variable.

Action: Check variable.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17744: The status can only be switched from ERROR to DONE or from DONE to ERROR.

Cause: Wrong status

Action: Check status.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17745: Parameter {0} must be greater or equal than {1}.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17746: Parameter {0} must be greater than {1}.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17747: Array {0} must not be empty.

Cause: Array length is 0.

Action: Check array.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17748: Parameter {0} is not relevant to this schedule.

Cause: Wrong parameter.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17749: Invalid value was specified. Cannot create {0} with the value {1}.

Cause: Invalid value was specified.

Action: Check value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17750: Parent folder already has the release tag set.

Cause: Setting the release tag when the parent already has the release tag set.

Action: Set the release tag in parent.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17751: Shortcut and the base object are under same folder.

Cause: Cannot create shortcut {0} with the base object under same folder {1}.

Action: Create shortcut in different folder.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17752: Shortcut and the base object are in different projects.

Cause: Cannot create shortcut {0} in project {1} which is different from the project of the base object.

Action: Create shortcut in same project as the base object.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17753: Shortcut with same reference object in same folder.

Cause: There is other shortcut object with same reference object as {0} in the same folder.

Action: Create shortcut in different folder.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17754: Shortcut and the base object are under same model.

Cause: Cannot create shortcut {0} with the base object under same model {1}.

Action: Create shortcut in different model.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17755: Shortcut with same reference object in same model.

Cause: There is other shortcut object with same reference object as {0} in the same model.

Action: Create shortcut in different model.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17756: Scenario "{0}", which is referenced by RunScenario step "{1}", has variable "{2}" but LoadPlan does not have variable with the same name.

Cause: Missed variable in Load Plan

Action: Check Load Plan''s variables.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17757: Scenario "{0}", which is referenced by RunScenario step "{1}", has a newer version "{2}" in the repository

Cause: Scenario has newer version.

Action: Consider to use latest version.
Level: 32

Type: NOTIFICATION

Impact: Programmatic

ODI-17758: LoadPlan Variable "{0}" SQL is different than the design repository Variable "{1}" SQL.

Cause: Variable's SQL was redefined.

Action: Check LoadPlan's variable.
Level: 32

Type: NOTIFICATION

Impact: Programmatic

ODI-17759: LoadPlan Variable "{0}" LogicalSchema "{1}" is different than the design repository Variable "{2}" LogicalSchema "{3}".

Cause: Variable's Logical Schema was redefined.

Action: Check LoadPlan's variable.
Level: 32

Type: NOTIFICATION

Impact: Programmatic

ODI-17760: Exception "{0}" is not used in the Load Plan.

Cause: Exception is not used.

Action: Consider to delete or disable unused exception.
Level: 32

Type: NOTIFICATION

Impact: Programmatic

ODI-17761: LoadPlan Variable "{0}" is refreshed at step "{1}", but it has no SQL.

Cause: LoadPlan Variable doesn't have refresh SQL.

Action: Check variable''s SQL or disable variable refreshing.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17762: Context is specified on a step "{0}", but it''s no longer present in the topology.

Cause: Context was removed.

Action: Check step's context.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17763: Logical Agent is specified on a step "{0}", but it is no longer present in the topology

Cause: Logical Agent was removed.

Action: Check step's Logical Agent.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17764: Context "{0}" and Logical agent "{1}" on a step "{2}" does not map to any physical agent.

Cause: Physical Agent doesn''t exist.

Action: Check agents'' mapping.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17765: Scenario variable "{0}" type and LoadPlan variable "{1}" type mismatch.

Cause: Variables have different datatype.

Action: Check variables.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17766: Scenario "{0}" wasn''t found.

Cause: Scenario doesn''t exist

Action: Check scenario and Load Plan step.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17767: LoadPlan has variable "{0}", but repository doesn't have variable with the same name.

Cause: Variable was deleted.

Action: Check variables.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17768: LoadPlan Variable "{0}" has SQL, which could not be validated.

Cause: OdiVariableTextGeneratorException during validation.

Action: Check variable and variable text generator.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17769: OdiRef: Internal ID {0} of IObjects {1} should not be used when the repository is 12c mode.

Cause: Internal ID is used in 12c mode.

Action: Use Global Id instead of internal id.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17770: Profile {0} is not assigned to role {1}.

Cause: Profile is not assigned to role.

Action: Check role's profiles.
Level: 32

Type: ERROR

Impact: Security

ODI-17771: Enterprise principal with unique ID/name {0} is not mapped to role {1}.

Cause: Enterprise principal is not mapped to role.

Action: Check role's mapped enterprise principals.
Level: 32

Type: ERROR

Impact: Security

ODI-17772: Parameter {0} should be {1} or {2}.

Cause: Wrong parameter value.

Action: Check parameter value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17773: Enterprise User or Role {0} does not exist.

Cause: Enterprise principla with such name could be found at LDAP server.

Action: Check principal name and LDAP server.
Level: 32

Type: ERROR

Impact: Security

ODI-17774: Maximum number of concurrent threads must be positive.

Cause: Wrong value.

Action: Check maximum number provided.
Level: 32

Type: ERROR

Impact: Other

ODI-17775: Maximum number of threads per session can not be negative.

Cause: Wrong value.

Action: Check maximum number provided.
Level: 32

Type: ERROR

Impact: Other

ODI-17776: Maximum number of concurrent threads must not be less than maximum session count.

Cause: Wrong value.

Action: Check maximum numbers provided.
Level: 32

Type: ERROR

Impact: Other

ODI-17777: Maximum number of threads per session must be not greater than maximum number of threads.

Cause: Wrong value.

Action: Check maximum numbers provided.
Level: 32

Type: ERROR

Impact: Other

ODI-17778: Maximum number of cache entries in Session Blueprint queue cannot be negative.

Cause: Wrong value.

Action: Check value.
Level: 32

Type: ERROR

Impact: Other

ODI-17779: Maximum idle time for Session Blueprint in cache cannot be negative.

Cause: Wrong value.

Action: Check value.
Level: 32

Type: ERROR

Impact: Other

ODI-17780: Package and mapping must be owned by the same project.

Cause: Package and mapping have different parents.

Action: Check package and mapping.
Level: 32

Type: ERROR

Impact: Other

ODI-17781: Physical Mapping Design must be owned by the mapping.

Cause: Physical Mapping Design is not owned by mapping.

Action: Check mapping and physical design.
Level: 32

Type: ERROR

Impact: Other

ODI-17782: OdiRef: Internal ID is retrieved in method {0}.{1} for 12c repository.

Cause: Internal ID is retrieved in 12c mode.

Action: Retrieve Global Id instead of internal id.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17783: Mapping metadata version mismatch. Expected {0}, but was {1}.

Cause: Mapping metadata version mismatch.

Action: Check the expected and actual Mapping metadata version.
Level: 32

Type: ERROR

Impact: Other

ODI-17784: Reusable Mapping metadata version mismatch. Expected {0}, but was {1}.

Cause: Reusable Mapping metadata version mismatch.

Action: Check the expected and actual Reusable Mapping metadata version.
Level: 32

Type: ERROR

Impact: Other

ODI-17785: Option positions in knowledge module must be unique.

Cause: Option position undefined or multiple option in knowledge module has same position.

Action: Modify the position of options to be unique and not null.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17786: JKM is not Oracle Golden Gate JKM.

Cause: Model doesn't have JKM set or JKM is not Oracle Golden Gate JKM.

Action: Set Oracle Golden Gate JKM for the model.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17787: Extract and initial extract processes cannot be the same.

Cause: Extract and inital extract processes are the same.

Action: Choose another extract or initial expract process.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17788: Replicat and initial replicat processes cannot be the same.

Cause: Replicat and initial replicat processes are the same.

Action: Choose another replicat or initial replicat process.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17789: Positions must be set positive.

Cause: Position is not a positive integer.

Action: Set the position to be a positive integer.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17790: {0} should be {1}

Cause: Type is not correct

Action: Set the correct type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17791: The option group already exists.

Cause: The option group already exists.

Action: Check option group.
Level: 32

Type: ERROR

Impact: Other

ODI-17792: Option group is not associated to the same procedure

Cause: Group is not associated to the same procedure

Action: Check option group.
Level: 32

Type: ERROR

Impact: Other

ODI-17794: Count is larger than permissible value of Integer. Use method : {0}

Cause: Return value is larger than permissible value of Integer

Action: Use method : {0}
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17795: {0} parameter is not valid

Cause: Parameter is not correct

Action: Set the correct parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17796: {0} is not a valid technology.

Cause: Technology is not correct.

Action: Set the correct technology.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17797: Logical Agent "{0}" type and Physical Agent "{1}" type mismatch.

Cause: Logical Agent and Physical Agent are of different type.

Action: Check the type of Logical and Physical Agents.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17798: {0} parameter format is not valid.

Cause: Parameter format is not correct.

Action: Set the parameter with correct format.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17799: Level attribute {0} bound column: {1} is owned by table {2}, but the level is bound to table {3}

Cause: The bound column parent table does not match the bound table for the level or dimension

Action: Reset the column binding to a column of the bound level table.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17800: Level attribute {0} bound error column: {1} is owned by table {2}, but the level is bound to error table {3}

Cause: The bound error column parent table does not match the bound error table for the level or dimension

Action: Reset the error column binding to a column of the bound level error table.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17801: Level attribute {0} bound staging column: {1} is owned by table {2}, but the level is bound to staging table {3}

Cause: The bound staging column parent table does not match the bound staging table for the level or dimension

Action: Reset the staging column binding to a column of the bound level staging table.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17803: The dimension has an invalid cyclical parent/child level relationship involving {0}.

Cause: One of the parent/child relationships reverses the order of another parent/child relationship, this is not allowed.

Action: Fix the parent/child relationships for the dimension.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17804: The dimension hierarchy member uses parent ref {0}, which points to a level that is not included in the hierarchy.

Cause: A dimension hierarchy must use parent references that allow navigation of the levels that are included in the hierarchy.

Action: Fix the hierarchy member to use a different parent ref, or add a level to the hierarchy.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17805: An invalid dimension key for this key reference.

Cause: The key reference must point to a dimension key which is belonged to the referenced dimension.

Action: Use the dimension key belonged to the referenced dimension.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17806: The dimension key is already used by another key reference.

Cause: Each dimension key can only be used by one key reference.

Action: Set another dimension key that has not been used by any key reference.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17807: A non-transparent LKM must have a processing type of BOTH.

Cause: The setProcessingType method was called for a LKM, and specified and incorrect type. A non-transparent LKM must have processing type of BOTH.

Action: Change the call to set the correct type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17808: Sql join parameter combination is not correct for technology {0}.

Cause: Sql Join parameters combination is not correct.

Action: Set the correct sql join parameter combination.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17809: When data server contains multiple schemas with same table and column names, physical schema must specify a schema name.

Cause: Schema name is not specified while creating the physical schema.

Action: Please specify the schema name in corresponding physical schema.
Level: 32

Type: ERROR

Impact: Other

ODI-17810: Error during BeanShell evaluation: {0}, Pre-execution code: {1}

Cause: Error occurs during BeanShell evaluation of procedure or KM task code.

Action: Please check the procedure or KM task code in the error message.
Level: 32

Type: ERROR

Impact: Other

ODI-17811: {0} argument is not a valid format.

Cause: Argument is not a valid format

Action: Please provide the correct format.
Level: 32

Type: ERROR

Impact: Other

ODI-17900: Cube {0} does not reference any dimensions.

Cause: A cube must reference at least one dimension to be viable.

Action: Add dimension references to the cube.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17901: Cube {0} does not have any measures.

Cause: A cube must have at least one measure to be viable.

Action: Define measures for this cube.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17902: A dimension reference of cube {0} is not associated with a level.

Cause: A cube reference to a dimension must be associated with a level to be viable.

Action: Ensure each dimension reference of the cube is associated with a level.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17903: Cube {0} reference to dimension {1} is invalid.

Cause: The cube references an invalid dimension.

Action: Validate the dimensions which are referenced by this cube.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17904: Cube {0} has multiple references to dimension {1} with no unique role qualifiers.

Cause: Role qualifiers are missing or not unique when a cube has multiple references to a dimension.

Action: Set role qualifiers on the dimension references of the cube and ensure role qualifiers are unique.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17905: Cube {0} is not bound to a datastore.

Cause: A cube must be bound to a datastore to be viable.

Action: Bind the cube to a datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17906: Cube {0} with orphan management enabled is not bound to an error datastore.

Cause: A cube must be bound to an error datastore to be viable when orphan management is enabled.

Action: Bind the cube to an error datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17907: In cube {0}, measure {1} is not bound to a column of the cube bound datastore.

Cause: The measure must be bound to a column of the cube bound datastore.

Action: Bind each measure to a column of the cube bound datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17908: In cube {0}, measure {1} is not bound to an error column of the cube bound error datastore when orphan management is enabled.

Cause: The measure must be bound to an error column of the cube bound error datastore when orphan management is enabled.

Action: Bind each measure to an error column of the cube bound error datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17909: Cube {0} is bound to datastore {1}, but measure {2} is bound to column {3} which is owned by datastore {4}.

Cause: The measure is bound to a column which is owned by a different datastore to the one bound to the cube.

Action: Bind each measure to a column which is owned by the cube bound datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17910: Cube {0} is bound to error datastore {1}, but measure {2} is bound to error column {3} which is owned by datastore {4}.

Cause: The measure is bound to an error column which is owned by a different error datastore to the one bound to the cube.

Action: Bind each measure to an error column which is owned by the cube bound error datastore.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-17911: Cube {0} reference to dimension {1} does not have a key reference.

Cause: The cube is missing a key reference for one of the dimensions.

Action: Ensure the cube references the key for each dimension.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17912: Cube {0} reference to dimension {1}, level {2} has a surrogate key, but the key reference does not point to this surrogate key.

Cause: The cube has a key reference that does not point to the surrogate key of the dimension level.

Action: Ensure the cube references the surrogate key if the dimension level has a surrogate key.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17913: In cube {0}, the key reference for dimension {1} is not bound to a column of the cube bound datastore.

Cause: The key reference for a dimension must be bound to a column of the cube bound datastore.

Action: Bind each key reference to a column of the cube bound datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17914: In cube {0}, the key reference for dimension {1} is not bound to an error column of the cube bound error datastore when orphan management is enabled.

Cause: The key reference for a dimension must be bound to an error column of the cube bound error datastore when orphan management is enabled.

Action: Bind each key reference to an error column of the cube bound error datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17915: Cube {0} is bound to datastore {1}, but key reference for dimension {2} is bound to column {3} which is owned by datastore {4}.

Cause: The key reference for a dimension is bound to a column which is owned by a different datastore to the one bound to the cube.

Action: Ensure each key reference is bound to a column of the cube bound datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17916: Cube {0} is bound to an error datastore {1}, but key reference for dimension {2} is bound to an error column {3} which is owned by datastore {4}.

Cause: The key reference for a dimension is bound to an error column which is owned by a different datastore to the one bound to the cube.

Action: Ensure each key reference is bound to an error column of the cube error bound datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17917: In cube {0}, multiple dimension key references or measures are bound to the same column {1} of the cube bound datastore.

Cause: Multiple dimension key references or measures of the cube are bound to a same column of the cube bound datastore.

Action: Ensure each dimension key reference and each measure is bound to a separate column of the cube bound datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17918: In cube {0}, multiple dimension key references or measures are bound to the same error column {1} of the cube bound error datastore.

Cause: Multiple dimension key references or measures of the cube are bound to a same error column of the cube bound error datastore.

Action: Ensure each dimension key reference and each measure is bound to a separate error column of the cube bound error datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17919: There is no primary key to foreign key constraint defined in ODI between the cube table {0} and the dimension table {1}.

Cause: ODI looks for primary key and foreign key references between dimension tables and cube tables. For cube table there is no foreign key to the dimension table.

Action: Define a foreign key on the cube table that references the primary key on the dimension table.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17920: Dimension {0} does not have any levels.

Cause: The dimension does not have any levels.

Action: Create one or more levels for this dimension.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17921: In Dimension {0}, level {1} does not have any level attributes.

Cause: The level does not have level attributes.

Action: Create one or more level attributes for this level.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17922: In dimension {0} level {1}, level attribute {2} is defined as surrogate key, but its type is not NUMERIC.

Cause: The level attribute is defined as surrogate key,but its datatype is not NUMERIC.

Action: If the level attribute is defined as surrogate key, its datatype should be NUMERIC.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17923: In Dimension {0}, hierarchy {1} contains either only one level or no levels.

Cause: The hierarchy contains only one level or no levels.

Action: The hierarchy should contain two or more levels.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17924: Dimension {0} has more than one level but no hierarchy defined.

Cause: The dimension has more than one level but no hierarchy defined.

Action: The dimension can have a single level with no hierarchies or all levels must be contained in at least one hierarchy.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17925: In dimension {0}, level {1} does not have any natural key.

Cause: The level does not have any natural key.

Action: Create a natural key for this level.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17926: Dimension {0} has some levels that use surrogate key but some that do not.

Cause: The dimension has some levels that use surrogate key but some that do not.

Action: Surrogate key usage must be consistent within a dimension. Modify the dimension to ensure all levels have a surrogate key or no levels have a surrogate key.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17927: In dimension {0}, level {1} does not have any updatable attributes. An updatable attribute is defined as level attribute that is not surrogate key or natural key.

Cause: The level does not have any updatable attributes.

Action: Define one or more updatable attributes for this level.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17928: In dimension {0}, level {1} does not use surrogate key and the natural key has more attribute defined.This is not supported by the dimension loading pattern.

Cause: The level does not use surrogate key and the natural key has more than one attribute defined. This is currently not supported by the dimension loading pattern.

Action: If no surrogate key is defined, the natural key should have only one attribute defined. Update the level accordingly.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17929: Dimension {0} flagged as a star implementation is not bound to a datastore.

Cause: The dimension flagged as a star implementation must be bound to a datastore.

Action: Bind the dimension to a datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17930: Dimension {0} is flagged as a snowflake implementation, but level {1} is not bound to a datastore.

Cause: The dimension is flagged as a snowflake implementation, but the level is not bound to a datastore.

Action: Bind the level to a datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17931: In dimension {0}, level {1} is not bound to a staging datastore.

Cause: The dimension level is not bound to a staging datastore.

Action: Bind the level to a staging datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17932: Dimension {0} is flagged as a star implementation and the orphan management is enabled, but the dimension is not bound to an error datastore.

Cause: The dimension is flagged as a star implementation and the orphan management is enabled, but the dimension is not bound to an error datastore.

Action: Bind the dimension to an error datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17933: Dimension {0} is flagged as a snowflake implementation and the orphan management is enabled, but level {1} is not bound to an error datastore.

Cause: The dimension is flagged as a snowflake implementation and the orphan management is enabled, but the level is not bound to an error datastore.

Action: Bind the level to an error datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17934: In dimension {0} level {1}, level attribute {2} is not bound to a column of the bound datastore.

Cause: The level attribute is not bound to a column of the bound datastore.

Action: Bind the level attribute to a column of the bound datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17935: In dimension {0} level {1}, level attribute {2} is not bound to a staging column of the bound staging datastore.

Cause: The level attribute is not bound to a staging column of the bound stating datastore.

Action: Bind the level attribute to a staging column of the bound staging datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17936: In dimension {0} level {1}, level attribute {2} is not bound to an error column of the bound error datastore.

Cause: The level attribute is not bound to an error column of the bound error datastore.

Action: Bind the level attribute to an error column of the bound error datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17937: In dimension {0}, level {1} is bound to datastore {2}, but level attribute {3} is bound to column {4} which is owned by datastore {5}.

Cause: The level is bound to a datastore, but a level attribute is bound to a column which is owned by another datastore.

Action: Bind the level attribute to a column which is owned by the datastore that is bound to the level.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17938: In dimension {0}, level {1} is bound to staging datastore {2}, but level attribute {3} is bound to staging column {4} which is owned by datastore {5}.

Cause: The level is bound to a staging datastore, but a level attribute is bound to a staging column which is owned by another datastore.

Action: Bind the level attribute to a staging column which is owned by the staging datastore that is bound to the level.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17939: In dimension {0}, level {1} is bound to error datastore {2}, but level attribute {3} is bound to error column {4} which is owned by datastore {5}.

Cause: The level is bound to an error datastore, but a level attribute is bound to an error column which is owned by another datastore.

Action: Bind the level attribute to an error column which is owned by the error datastore that is bound to the level.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17940: Dimension {0} uses surrogate key but is not associated with a sequence.

Cause: The dimension uses a surrogate key but is not associated with a sequence.

Action: Associate the dimension with a sequence or do not use a surrogate key.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17941: Dimension {0} uses surrogate key but bound datastore {1} does not have primary key constraint.

Cause: The dimension uses a surrogate key, but the datastore that is bound to the dimension does not have a primary key constraint.

Action: Define a primary key constraint for the datastore that is bound to the dimension.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17942: Dimension {0} uses surrogate key but bound datastore {1} of level {2} does not have primary key constraint.

Cause: The dimension uses a surrogate key, but the datastore that is bound to the level does not have a primary key constraint.

Action: Define a primary key constraint for the datastore that is bound to the level.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17943: In dimension {0} level {1}, parent reference member {2} is not bound to a column.

Cause: In the dimension, the parent ref member is not bound to a column.

Action: Bind the parent reference member to a column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17944: In dimension {0} level {1}, parent reference member {2} is not bound to a staging column.

Cause: In dimension, the parent ref member is not bound to a staging column.

Action: Bind the parent reference member to a staging column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17945: In dimension {0} level {1}, parent reference member {2} is not bound to an error column.

Cause: In dimension, the parent ref member is not bound to an error column.

Action: Bind the parent reference member to an error column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17946: In dimension {0} level {1} is bound to datastore {2}, but parent reference member {3} is bound to staging column {4} which is owned by datastore {5}.

Cause: The level is bound to a datastore, but a parent reference member is bound to a column which is owned by another datastore.

Action: Bind the parent reference member to a column which is owned by the datastore that is bound to the level.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17947: In dimension {0} level {1} is bound to staging datastore {2}, but parent reference member {3} is bound to column {4} which is owned by datastore {5}.

Cause: The level is bound to a staging datastore, but a parent reference member is bound to a staging column which is owned by another datastore.

Action: Bind the parent reference member to a staging column which is owned by the staging datastore that is bound to the level.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17948: In dimension {0} level {1} is bound to error datastore {2}, but parent reference member {3} is bound to error column {4} which is owned by datastore {5}.

Cause: The level is bound to an error datastore, but a parent reference member is bound to an error column which is owned by another datastore.

Action: Bind the parent reference member to an error column which is owned by the error datastore that is bound to the level.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17949: Dimension {0} is flagged as a snowflake implementation, in level {1}, the bound column of parent reference member {2} does not have foreign key constraint.

Cause: The dimension is flagged as a snowflake implementation, in the level, the bound column of a parent reference member {2} does not have a foreign key constraint.

Action: Define foreign key constraints for the columns that are bound to the parent reference members.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17950: In dimension {0} parent reference member {1}, the datatype of {3} of referenced level attribute {2} does not match with the datatype {5} of bound column {4}.

Cause: For the parent reference member, the datatype of the referenced level attribute does not match with that of the bound column.

Action: The datatype of the referenced level attribute should match with that of the bound datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17951: In dimension {0} parent reference member {1}, the size {3} of referenced level attribute {2} is not equal to the size {5} of bound column {4}.

Cause: For the parent reference member, the size of the referenced level attribute is not equal to that of the bound column.

Action: The size of the referenced level attribute should be equal to that of the bound datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17952: In dimension {0} parent reference member {1}, the scale {3} of referenced level attribute {2} is not equal to the scale {5} of bound column {4}.

Cause: For the parent reference member, the scale of the referenced level attribute is not equal to that of the bound column.

Action: The scale of the referenced level attribute should be equal to that of the bound datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17953: In dimension {0} parent reference member {1}, the datatype {3} of referenced level attribute {2} does not match with the datatype {5} of bound staging column {4}.

Cause: For the parent reference member, the datatype of the referenced level attribute does not match with that of the bound staging column.

Action: The datatype of the referenced level attribute should match with that of the bound staging datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17954: In dimension {0} parent reference member {1}, the size {3} of referenced level attribute {2} is not equal to the size {5} of bound staging column {4}.

Cause: For the parent reference member, the size of the referenced level attribute is not equal to that of the bound staging column.

Action: The size of the referenced level attribute should be equal to that of the bound staging datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17955: In dimension {0} parent reference member {1}, the scale {3} of referenced level attribute {2} is not equal to the scale {5} of bound staging column {4}.

Cause: For the parent reference member, the scale of the referenced level attribute is not equal to that of the bound staging column.

Action: The scale of the referenced level attribute should be equal to that of the bound staging datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17956: In dimension {0} parent reference member {1}, the datatype {3} of referenced level attribute {2} does not match with the datatype {5} of bound error column {4}.

Cause: For the parent reference member, the datatype of the referenced level attribute does not match with that of the bound error column.

Action: The datatype of the referenced level attribute should match with that of the bound error datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17957: In dimension {0} parent reference member {1}, the size {3} of referenced level attribute {2} is not equal to the size {5} of bound error column {4}.

Cause: For the parent reference member, the size of the referenced level attribute is not equal to that of the bound error column.

Action: The size of the referenced level attribute should be equal to that of the bound error datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17958: In dimension {0} parent reference member {1}, the scale {3} of referenced level attribute {2} is not equal to the scale {5} of bound error column {4}.

Cause: For the parent reference member, the scale of the referenced level attribute is not equal to that of the bound error column.

Action: The scale of the referenced level attribute should be equal to that of the bound error datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17959: Dimension {0} has an invalid cyclical parent/child level relationship involving parent reference {1}.

Cause: One of the parent/child relationships reverses the order of another parent/child relationship, this is not allowed.

Action: Fix the parent/child relationships for the dimension.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17960: In dimension {0} hierarchy {1}, the hierarchy member for level {2} uses parent reference {3}, which points to level {4} that is not included in this hierarchy.

Cause: The hierarchy member uses the parent reference which points to the level that is not included in hierarchy.

Action: Fix the hierarchy member to use a different parent reference or add a level to the hierarchy.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17961: In dimension {0} level {1}, the datatype {3} of level attribute {2} is does not match with the datatype {5} of bound column {4}.

Cause: The datatype of the level attribute does not match with that of the bound column.

Action: The datatype of the level attribute should match with that of the bound datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17962: In dimension {0} level {1}, the size {3} of level attribute {2} is not equal to the size {5} of bound column {4}.

Cause: The size of the level attribute is not equal to that of the bound column.

Action: The size of the level attribute should be equal to that of the bound datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17963: In dimension {0} level {1}, the scale {3} of level attribute {2} is not equal to the scale {5} of bound column {4}.

Cause: The scale of the level attribute is not equal to that of the bound column.

Action: The scale of the level attribute should be equal to that of the bound datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17964: In dimension {0} level {1}, the datatype {3} of level attribute {2} does not match with the datatype {5} of bound staging column {4}.

Cause: The datatype of the level attribute does not match with that of the bound staging column.

Action: The datatype of the level attribute should match with that of the bound staging datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17965: In dimension {0} level {1}, the size {3} of level attribute {2} is not equal to the size {5} of bound staging column {4}.

Cause: The size of the level attribute is not equal to that of the bound staging column.

Action: The size of the level attribute should be equal to that of the bound staging datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17966: In dimension {0} level {1}, the scale {3} of level attribute {2} is not equal to the scale {5} of bound staging column {4}.

Cause: The scale of the level attribute is not equal to that of the bound staging column.

Action: The scale of the level attribute should be equal to that of the bound staging datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17967: In dimension {0} level {1}, the datatype {3} of level attribute {2} does not match with the datatype {5} of bound error column {4}.

Cause: The datatype of the level attribute does not match with that of the bound error column.

Action: The datatype of the level attribute should match with that of the bound error datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17968: In dimension {0} level {1}, the size {3} of level attribute {2} is not equal to the size {5} of bound error column {4}.

Cause: The size of the level attribute is not equal to that of the bound error column.

Action: The size of the level attribute should be equal to that of the bound error datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17969: In dimension {0} level {1}, the scale {3} of level attribute {2} is not equal to the scale {5} of bound error column {4}.

Cause: The scale of the level attribute is not equal to that of the bound error column.

Action: The scale of the level attribute should be equal to that of the bound error datastore column.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17970: Dimension {0} is flagged as a star implementation, but parent reference {1} member {2} is not bound to the same column {3} as the matching parent level key attribute {4}.

Cause: The dimension is star implementation, but one or more parent reference members is not bound to the same column as the matching parent level key attribute.

Action: Bind the parent reference member to the column which is also bound to the matching parent level key attribute.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17971: In dimension {0} level {1}, a key attribute {2} is flagged as role playing(date or trigger, etc.). This is not allowed.

Cause: In SCD type 2, a key attribute cannot be flagged as a date or trigger attribute.

Action: Do not define a key attribute as an SCD2 flag(e.g. date or trigger).
Level: 32

Type: ERROR]

Impact: Programmatic

ODI-17972: In dimension {0}, if any of SCD2 trigger history, SCD2 effective time or SCD2 expiration time is set for a level, then all of them must be set.

Cause: In the dimension, if any of SCD2 trigger history, SCD2 effective time or SCD2 expiration time is set for a level, then all of them must be set.

Action: Set SCD2 trigger history, SCD2 effective time and SCD2 expiration time for the level.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17973: In dimension {0}, SCD2 is enabled, but surrogate key is not used.

Cause: In the dimension, SCD2 is enabled, but surrogate key is not used.

Action: The dimension should use surrogate key if SCD2 is enabled.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17974: In dimension {0}, SCD2 is enabled for non-leaf level {1}, but hierarchy versioning is not enabled between level {1} and {2}. The versioning of non-leaf level {1} will not result in the versioning of its corresponding child records in level {2}.

Cause: In the dimension, SCD2 is enabled for non-leaf level, but hierarchy versioning is not enabled.

Action: Enable hierarchy versioning, otherwise the versioning of non-leaf level will not result in the versioning of its corresponding child records.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17975: In dimension {0} level {1}, a key attribute {2} is flagged as role playing(date or trigger, etc.). This is not allowed.

Cause: In SCD type 3, a key attribute cannot be flagged as a date or trigger attribute.

Action: Do not define a key attribute as an SCD3 flag(e.g. date or trigger).
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17976: In dimension {0} level {1}, the datatype {3} of level attribute {2} does not match with the datatype {5} of SCD3 previous attribute {4}.

Cause: In the dimension, the datatype of the level attribute does not match with that of the SCD3 previous attribute.

Action: The datatype of the level attribute should match with that of the SCD3 previous attribute.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17977: In dimension {0} level {1}, the size {3} of level attribute {2} does not match with the size {5} of SCD3 previous attribute {4}.

Cause: In the dimension, the size of the level attribute does not match with that of the SCD3 previous attribute.

Action: The size of the level attribute should match with that of the SCD3 previous attribute.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17978: In dimension {0} level {1}, the scale {3} of level attribute {2} does not match with the scale {5} of SCD3 previous attribute {4}.

Cause: In the dimension, the scale of level attribute does not match with that of the SCD3 previous attribute.

Action: The scale of the level attribute should match with that of the SCD3 previous attribute.
Level: 32

Type: WARNING

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: General Exception invoking editor.

Action: This is an internal error with no recommended user action.
Level: 32

Type: ERROR

Impact: Other

ODI-20004: ODI-20004: Cannot edit the reference

Cause: General Exception invoking editor.

Action: This is an internal error with no recommended user action.
Level: 32

Type: ERROR

Impact: Other

ODI-20005: ODI-20005: Cannot edit the variable

Cause: General Exception invoking editor.

Action: This is an internal error with no recommended user action.
Level: 32

Type: ERROR

Impact: Other

ODI-20006: ODI-20006: Cannot display table's data. Data is probably already displayed.

Cause: General Exception invoking editor.

Action: This is an internal error with no recommended user action.
Level: 32

Type: ERROR

Impact: Other

ODI-20007: ODI-20007: Cannot display table's data.

Cause: General Exception invoking editor.

Action: This is an internal error with no recommended user action.
Level: 32

Type: ERROR

Impact: Other

ODI-20008: ODI-20008: You cannot Display this Attribute Data. Data is probably already displayed

Cause: General Exception invoking editor.

Action: This is an internal error with no recommended user action.
Level: 32

Type: ERROR

Impact: Other

ODI-20009: ODI-20009: Cannot display data. The datastore resource name is {0} characters long which is longer than allowed by the technology ({1}). Please review the technology settings in Topology.

Cause: The datastore resource name exceeded the limit allowed by its technology.

Action: Ensure the maximum table name length setting in the corresponding technology is correct. Consider changing the datastore resource name to comply.
Level: 32

Type: ERROR

Impact: Other

ODI-20010: ODI-20010: Cannot display this Attribute Data

Cause: General Exception invoking editor.

Action: This is an internal error with no recommended user 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: Another user may be editing this datastore.

Action: Wait for the other editing session to be committed.
Level: 32

Type: ERROR

Impact: Other

ODI-20012: ODI-20012: Cannot perform this action: the Datastore containing this Column is currently being modified

Cause: Another user may be editing this datastore.

Action: Wait for the other editing session to be committed.
Level: 32

Type: ERROR

Impact: Other

ODI-20013: ODI-20013: Unable to perform the action because the package is currently being modified

Cause: Another user may be editing this package.

Action: Wait for the other editing session to be committed.
Level: 32

Type: ERROR

Impact: Other

ODI-20014: ODI-20014: Cannot encrypt the Procedure: it is currently being modified

Cause: Another user may be editing this procedure.

Action: Wait for the other editing session to be committed.
Level: 32

Type: ERROR

Impact: Other

ODI-20015: ODI-20015: Cannot initialize the Flexfields values

Cause: Another user may be editing the flexfield values.

Action: Wait for the other editing session to be committed.
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 label.
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 label.
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 label.
Level: 32

Type: ERROR

Impact: Other

ODI-20019: ODI-20019: Unable to get GBO object

Cause: Internal error.

Action: No action required.
Level: 32

Type: ERROR

Impact: Other

ODI-20020: ODI-20020: Cannot change CKM

Cause: Only one CKM is available.

Action: Import additional CKMs.
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: Insufficient privileges to edit the object.

Action: Assign additional privileges to edit the object.
Level: 32

Type: ERROR

Impact: Other

ODI-20022: ODI-20022: Could not change the KM

Cause: Additional KMs may not be available or installed for the current technology.

Action: Import additional KMs.
Level: 32

Type: ERROR

Impact: Other

ODI-20024: ODI-20024: Cannot create the cross reference for the condition

Cause: Internal error creating cross references for a condition.

Action: No action required.
Level: 32

Type: ERROR

Impact: Other

ODI-20025: ODI-20025: Cannot create the cross references for the reference

Cause: Internal error.

Action: No action required.
Level: 32

Type: ERROR

Impact: Other

ODI-20026: ODI-20026: Cannot view this Datastore: one of its Columns is currently being edited

Cause: The data store is being edited in another session.

Action: Wait for the other editing session to end.
Level: 32

Type: ERROR

Impact: Other

ODI-20027: ODI-20027: Cannot view this Column: its Datastore is currently being edited

Cause: A package step is being edited in another session.

Action: Wait for the other session to end.
Level: 32

Type: ERROR

Impact: Other

ODI-20028: ODI-20028: Cannot start execution.

Cause: Execution cannot be started due to an internal error.

Action: No required action.
Level: 32

Type: ERROR

Impact: Other

ODI-20029: ODI-20029: Cannot move a line

Cause: Internal error.

Action: No action required.
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: An attempt was made to delete a command being edited.

Action: Save the edit before deleting.
Level: 32

Type: ERROR

Impact: Other

ODI-20032: ODI-20032: Cannot Delete a Command

Cause: Internal error.

Action: No required action
Level: 32

Type: ERROR

Impact: Other

ODI-20033: ODI-20033: Cannot find the KM description

Cause: Internal error.

Action: No action required.
Level: 32

Type: ERROR

Impact: Other

ODI-20034: ODI-20034: Cannot find the Options list for a Command

Cause: Internal error.

Action: No action required.
Level: 32

Type: ERROR

Impact: Other

ODI-20035: ODI-20035: Could not find a description for the KM

Cause: Internal error.

Action: No action required.
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: Internal error.

Action: No action required.
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: A context was not chosen for execution.

Action: Select an execution context.
Level: 32

Type: ERROR

Impact: Other

ODI-20040: ODI-20040: Problem encountered when determining the context

Cause: Internal error.

Action: No action required.
Level: 32

Type: ERROR

Impact: Other

ODI-20041: ODI-20041: No candidate datastore was found. Please create a mapping which loads data into this datastore.

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: An object is already open in another editor and cannot be modified.

Action: Close any other editors which may be locking the object.
Level: 32

Type: ERROR

Impact: Other

ODI-20047: ODI-20047: Unable to change Value

Cause: Internal error.

Action: Review the error details for further information.
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: An object is being edited, preventing other operations.

Action: Save or cancel editing of the object.
Level: 32

Type: ERROR

Impact: Other

ODI-20084: ODI-20084: Only variables from the same project can be placed in a package.

Cause: An unsupported operation was attempted.

Action: Variables from another projects cannot be placed in packages.
Level: 32

Type: ERROR

Impact: Other

ODI-20085: ODI-20085: Only mappings from the same project can be placed in a package.

Cause: An unsupported operation was attempted.

Action: Mappings from another project cannot be placed in packages.
Level: 32

Type: ERROR

Impact: Other

ODI-20086: ODI-20086: Only procedures from the same project can be placed in a package.

Cause: An unsupported operation was attempted.

Action: Procedures from another projects cannot be placed in packages.
Level: 32

Type: ERROR

Impact: Other

ODI-20087: ODI-20087: Error while duplicating

Cause: Internal error.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20088: ODI-20088: Error while generating the scenario

Cause: Internal error.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20089: ODI-20089: Error during parameter initialization

Cause: Internal error.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20090: ODI-20090: Error while duplicating

Cause: Internal error.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20091: ODI-20091: An unexpected error occurred.

Cause: Internal error.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20092: ODI-20092: An error occurred while replacing the version.

Cause: Internal error.

Action: Review the error details for further information.
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: Internal error.

Action: No action required.
Level: 32

Type: ERROR

Impact: Other

ODI-20097: ODI-20097: The line Name is mandatory

Cause: A value for the Action Line Name field was not specified.

Action: Enter a non-empty value for the Action Line Name field.
Level: 32

Type: ERROR

Impact: Other

ODI-20098: ODI-20098: Some Datatype Conversions between current and new Technologies are absent

Cause: Changing the selected Model's Technology failed because the Physical Architecture did not provide datatype conversion rules for datatypes used by attributes of datastores belonging to the selected model.

Action: Ensure datatype conversion rules exist for all datatypes used by attributes of datastores belonging to the selected model or do not use datatypes that cannot be converted.
Level: 32

Type: ERROR

Impact: Other

ODI-20099: ODI-20099: Unable to create execution window

Cause: Internal error.

Action: No action required.
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: Internal error.

Action: No action required.
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: An unexpected error occurred while trying to subscribe a datastore for CDC.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20115: ODI-20115: Error while stopping journalizing

Cause: An unexpected error occurred while trying to stop journalizing.

Action: Review the error details for further information.
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: An unexpected error occurred while building a menu.

Action: Review the error details for further information.
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: An unexpected error occurred during journalizing.

Action: Review the error details for further information.
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: An unexpected error occurred during query execution.

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: An unexpected error occurred.

Action: Review the error details for further information.
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: An unexpected error occurred during a drag operation.

Action: Review the error details for further information.
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: An unexpected error occurred opening a frame.

Action: Review the error details for further information.
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: The requested object has already been encrypted.

Action: No action required.
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: User function syntax has not been specified.

Action: Specify the function syntax.
Level: 32

Type: ERROR

Impact: Other

ODI-20155: ODI-20155: Changing the Logical Schema may require a re-generation of your Mappings. It may be better to modify the Topology information instead.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-20158: ODI-20158: Datastores distribution failed.

Cause: An error occured during the datastore distribution process.

Action: Review the message details and message log for more information. If problem persists contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20159: ODI-20159: The Attribute {0} is used as a Reference

Cause: An attempt was made to delete an attribute referenced by another object.

Action: Delete the object which references this attribute then retry deleting this attribute.
Level: 32

Type: ERROR

Impact: Other

ODI-20160: ODI-20160: The table {0} does not exist.

Cause: An error occured while executing the SQL request

Action: Review the message details for more information. If problem persists contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20161: ODI-20161: Standard reverse-engineering failed.

Cause: An error occured during the standard reverse-engineering process.

Action: Ensure the technology or driver supports standard reverse-engineering. Otherwise choose Customized Reverse and select an appropriate RKM for the technology.
Level: 32

Type: ERROR

Impact: Other

ODI-20162: ODI-20162: The context is not valid.

Cause: A Context was not specified.

Action: Specify a Context.
Level: 32

Type: ERROR

Impact: Other

ODI-20163: ODI-20163: Unable to add object

Cause: An error occurred while dragging and dropping an object.

Action: Review the message details and message log for more information.
Level: 32

Type: ERROR

Impact: Other

ODI-20164: ODI-20164: The line Name is mandatory

Cause: A name was not specified.

Action: Specify a Line name.
Level: 32

Type: ERROR

Impact: Other

ODI-20165: ODI-20165: The project name {0} is a reserved word.

Cause: A reserved word was used as the name of a project.

Action: Enter a different project name.
Level: 32

Type: ERROR

Impact: Other

ODI-20166: ODI-20166: The project code {0} is a reserved word.

Cause: A reserved word was used as the project code.

Action: Enter a different project code.
Level: 32

Type: ERROR

Impact: Other

ODI-20167: ODI-20167: Logical schema is not set for the current context

Cause: A Logical schema was not set for the current context.

Action: Ensure the Logical Schema is not set to "Undefined" in the Context editor.
Level: 32

Type: ERROR

Impact: Other

ODI-20168: ODI-20168: Logical schema is not set for the current context

Cause: A Logical schema was not set for the current context.

Action: Ensure the Logical Schema is not set to "Undefined" in the Context editor.
Level: 32

Type: ERROR

Impact: Other

ODI-20169: ODI-20169: The field {0} is mandatory.

Cause: A mandatory field was not specified.

Action: Enter a value for this field.
Level: 32

Type: ERROR

Impact: Other

ODI-20170: ODI-20170: You are trying to insert this versioned object but the version was deleted. Please re-create a version for this object.

Cause: The requested version of the object did not exist in the repository.

Action: Recreate the required version of this object.
Level: 32

Type: ERROR

Impact: Other

ODI-20171: ODI-20171: The label already contains a child of {0}. To add {1} to the label, you should delete {2} {3}. It is advised to use the button "synchronize" later to check the label's coherence.

Cause: The label already contained the specified object as a child.

Action: Delete the child object from the label before retrying the addition. Consider using the synchronize option to verify the label's coherence.
Level: 32

Type: ERROR

Impact: Other

ODI-20172: ODI-20172: The label already contains a parent of {0}. To add {1} to the label, you should delete {2} {3}. It is advised to use the button "synchronize" later to check the label's coherence.

Cause: The label has already contained the specified object as a parent of {0}.

Action: Delete the parent object from the label before retrying the addition. Consider using the synchronize option to verify the label's coherence.
Level: 32

Type: ERROR

Impact: Other

ODI-20173: ODI-20173: An error occurred while generating the procedure

Cause: An unexpected error occurred while generating a procedure.

Action: Review the error details for further information.
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: An unexpected error occurred while opening a window.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20183: ODI-20183: Error while refreshing Label

Cause: An unexpected error occurred while refreshing a label.

Action: Review the error details for further information.
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: The query for retrieving sequences has not been defined for the technology.

Action: Update the technology with the sequence query syntax.
Level: 32

Type: ERROR

Impact: Other

ODI-20185: ODI-20185: Error while opening window

Cause: An unexpected error occurred while opening a window.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20186: ODI-20186: Error while saving

Cause: An unexpected error occurred while saving an object.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20187: ODI-20187: Error while adding the marker

Cause: An unexpected error occurred while adding a marker.

Action: Review the error details for further information.
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: An unexpected error occurred while replacing a versioned object.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20193: ODI-20193: An error occurred during the versioning operation.

Cause: An unexpected error occurred during versioning.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20194: ODI-20194: Your license does not allow Versioning operations.

Cause: The license does not include versioning.

Action: Upgrade the license.
Level: 32

Type: ERROR

Impact: Other

ODI-20195: ODI-20195: Unable to unlock this object

Cause: An unexpected error occurred while unlocking an object.

Action: Review the error details for further information.
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: The current license does not inlude versioning.

Action: Upgrade the license to include versioning.
Level: 32

Type: ERROR

Impact: Other

ODI-20198: ODI-20198: Error while creating the version.

Cause: An unexpected error occurred while creating a version.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20199: ODI-20199: Your license does not allow Versioning operations.

Cause: The license does not include versioning.

Action: Upgrade your license.
Level: 32

Type: ERROR

Impact: Other

ODI-20200: ODI-20200: An error happened while comparing the versions

Cause: An unexpected error occurred while comparing versions.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20201: ODI-20201: Error while refreshing.

Cause: An unexpected error occurred while refreshing.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20202: ODI-20202: Synchronisation was stopped by the user.

Cause: Synchronization was stopped by the user.

Action: No action is required.
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: An unexpected error occurred.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20210: ODI-20210: Error When Printing...

Cause: An unexpected error occurred while printing.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20211: ODI-20211: Error When Displaying Node...

Cause: An unexpected error occurred while displaying a node.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20212: ODI-20212: An error occurred while checking errors

Cause: An unexpected error occurred while checking errors.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20213: ODI-20213: An error occurred while recovering an object in a node

Cause: An unexpected error occurred while recovering an object in a node.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20214: ODI-20214: An error occurred while deleting

Cause: An unexpected error occurred while deleting an object.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20216: ODI-20216: Error while deleting

Cause: An unexpected error occurred while deleting an object.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20217: ODI-20217: Error while executing the reverse-engineering

Cause: An unexpected error occurred while reverse engineering.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20218: ODI-20218: Error during duplication ...

Cause: An unexpected error occurred during duplication.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20219: ODI-20219: Error while opening

Cause: An unexpected error occurred while opening an object.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20220: ODI-20220: Error during data loading ....

Cause: An unexpected error occurred while loading data.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20221: ODI-20221: Error during execution ...

Cause: An unexpected error occurred during execution.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20222: ODI-20222: Error during scenario creation ...

Cause: An unexpected error occurred during scenario generation.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20223: ODI-20223: Error When Purging Log

Cause: An unexpected error occurred while purging the log.

Action: Review the error details for further information.
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: An unexpected error occurred while creating a popup menu.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20226: ODI-20226: Error while applying the changes

Cause: An unexpected error occurred while saving changes.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20227: ODI-20227: You cannot copy this attribute. Attribute name already in use.

Cause: Attribute copy failed because the Datastore already contained an attribute with the same name.

Action: Select another attribute to drop to datastore.
Level: 32

Type: ERROR

Impact: Other

ODI-20228: ODI-20228: Error while creating the popup menu

Cause: Retrieval of the Available Methods for the column failed.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20229: ODI-20229: Unable to create condition.

Cause: The editor for the Condition could not be opened.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20230: ODI-20230: Error while creating the popup menu

Cause: Retrieval of the Available Methods for the Condition failed.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20231: ODI-20231: Unable to create a synonym for this table.

Cause: An unexpected error occurred while creating a synonym.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20232: ODI-20232: Error while deleting attributes

Cause: An unexpected error occurred while deleting attributes.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20233: ODI-20233: Error during the drag-and-drop operation

Cause: An unexpected error occurred during a drag and drop operation.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20234: ODI-20234: You do not have the sufficient privileges to add this object.

Cause: The operation failed due to insufficient ODI security on Attribute.

Action: Ensure the ODI user security permissions are correct specifically the Attribute Duplication setting.
Level: 32

Type: ERROR

Impact: Other

ODI-20235: ODI-20235: Error during the drag-and-drop operation

Cause: An unexpected error occurred during a drag and drop operation

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20236: ODI-20236: You do not have the sufficient privileges to add this object.

Cause: The operation failed due to insufficient ODI security on Datastore.

Action: Ensure the ODI user security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20237: ODI-20237: Unable to duplicate the attribute.

Cause: An unexpected error occurred while duplicating an attribute.

Action: Review the error details for further information. Ensure that the repository connection is still valid.
Level: 32

Type: ERROR

Impact: Other

ODI-20238: ODI-20238: Unable to duplicate the table.

Cause: An unexpected error occurred while duplicating a table.

Action: Review the error details for further information. Ensure that the repository connection is still valid.
Level: 32

Type: ERROR

Impact: Other

ODI-20239: Error during the action

Cause: An unexpected error occurred during a user action.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20240: ODI-20240: Error while deleting

Cause: An unexpected error occurred during a delete operation.

Action: Review the error details for further information. Ensure that the repository connection is valid.
Level: 32

Type: ERROR

Impact: Other

ODI-20241: ODI-20241: Unable to apply changes.

Cause: The changes to the filter could not be applied.

Action: Save the object before retrying to apply the filter.
Level: 32

Type: ERROR

Impact: Other

ODI-20242: ODI-20242: Error while creating the popup menu

Cause: Retrieval of the Available Methods for the filter failed.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20243: ODI-20243: Unable to add an attribute.

Cause: An unexpected error occurred while adding an attribute.

Action: Review the error details for further information. Ensure that the repository connection is open.
Level: 32

Type: ERROR

Impact: Other

ODI-20244: ODI-20244: Unable to add reference

Cause: An unexpected error occurred while adding a reference.

Action: Review the error details for further information. Ensure that the repository connection is open.
Level: 32

Type: ERROR

Impact: Other

ODI-20245: ODI-20245: Unable to add table

Cause: An unexpected error occurred while adding a table.

Action: Review the error details for further information. Ensure that the repository connection is open.
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: An unexpected error occurred while adding a key.

Action: Review the error details for further information.
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: An unexpected error occurred while creating a popup menu.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20250: ODI-20250: Error while

Cause: Internal error.

Action: Review the error details for further information.
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-20263: ODI-20263: Please enter the duration in a format such as 5s (seconds), 10m (minutes), 1d (days), 1y (years).

Cause: Duration is specified in an invalid format

Action: Please change duration such that it comprises an integer followed by a time indicator, for example 10s, 30d, 1y
Level: 32

Type: ERROR

Impact: Other

ODI-20300: ODI-20300: Error while printing the diagram

Cause: An unexpected condition has occurred in the print system.

Action: Check the printer settings and physical printer.
Level: 32

Type: ERROR

Impact: Other

ODI-20301: ODI-20301: Error while saving the diagram

Cause: The save file could not be created.

Action: Check the destination folder is writable and that their is sufficient disk space.
Level: 32

Type: ERROR

Impact: Other

ODI-20310: Unsupported Flavor

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20311: ODI-20311: An unexpected exception occurred while reading or writing a text in a business object. Please contact Oracle technical support.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20312: ODI-20312: An error occurred while printing.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20313: ODI-20313: Could not double click

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20315: ODI-20315: Invalid Password

Cause: The Password is incorrect.

Action: Correct the password and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-20316: ODI-20316: A timeout occurred while trying to establish a connection.

Cause: A timeout error occurred while connecting to the database.

Action: Verify that the Database Connection details are correct and the database is available.
Level: 32

Type: ERROR

Impact: Other

ODI-20317: ODI-20317: The field "{0}" is mandatory.

Cause: A value has not been provided for a required field.

Action: Enter a value for the named field.
Level: 32

Type: ERROR

Impact: Other

ODI-20318: ODI-20318: The icon {0} cannot be found.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20319: ODI-20319: {0} is not a valid date for field {1}. The format is: {2}

Cause: The format of the date does not match the required format.

Action: Enter a valid date using the correct date format.
Level: 32

Type: ERROR

Impact: Other

ODI-20320: ODI-20320: Error when applying changes.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20321: ODI-20321: Error when initializing the panel.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20322: ODI-20322: Unable to add a Step.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20323: ODI-20323: Unable to execute the step

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20324: ODI-20324: Cannot execute the Package

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20325: ODI-20325: Unable to open the linked object.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20326: ODI-20326: Unable to edit the text

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20327: ODI-20327: Unable to modify the value.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20328: ODI-20328: Unable to define the next Step.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20329: ODI-20329: Unable to delete Steps(s). You do not have Edit privileges.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20330: ODI-20330: Unable to delete Link(s). You do not have Edit privileges.

Cause: You must have Edit privilege on each steps of the link.

Action: Review the Security settings for the steps and ensure that you have the correct permissions.
Level: 32

Type: ERROR

Impact: Other

ODI-20331: ODI-20331: The Step diagram is not be accessible.

Cause: You do not have permission to access this step.

Action: Check the diagram security settings and verify that you have permission to access the diagram.
Level: 32

Type: ERROR

Impact: Other

ODI-20332: ODI-20332: Cannot change the position of this object

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20333: ODI-20333: Cannot view this Step because the Package is being edited

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20335: ODI-20335: Printing Options not accessible.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20336: ODI-20336: Unknown event sent to the Package event manager.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20337: ODI-20337: A Knowledge Module cannot be added as a Step.

Cause: Only a DataStore,Model,Sub Model,Interface,Procedure or Variable can be added as a Step.

Action: Use a valid object type for your step creation.
Level: 32

Type: ERROR

Impact: Other

ODI-20338: ODI-20338: A starting Step must be defined.

Cause: A Starting step has been defined.

Action: Select the first step in the package and mark is the starting step.
Level: 32

Type: ERROR

Impact: Other

ODI-20339: ODI-20339: One or more Steps are not linked.

Cause: All steps must be linked.

Action: Ensure that all steps are linked .
Level: 32

Type: ERROR

Impact: Other

ODI-20340: ODI-20340: Only one starting Step can be defined.

Cause: A package must have one and only one starting steps.

Action: Ensure that you have only one starting step defined .
Level: 32

Type: ERROR

Impact: Other

ODI-20341: ODI-20341: You don't have the appropriate privileges.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20342: ODI-20342: Cannot open the Expression Editor

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20343: ODI-20343: There are errors in your diagram

Cause: The diagram may contain objects that are not connected, or objects that are not completely defined.

Action: Check the diagram and ensure that all objects are connected and fully defined.
Level: 32

Type: ERROR

Impact: Other

ODI-20344: ODI-20344: Cannot launch the editor for this expression

Cause: An error occured while retrieving the language for the expression. This may be due to an unexpected exception, or the language may not be available for the schema's technology.

Action: Review the message log for additional errors. Ensure that the schema has a valid technology for which the language is set.
Level: 32

Type: ERROR

Impact: Other

ODI-20345: ODI-20345: Cannot change the clause position

Cause: An unexpected internal exception has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20346: ODI-20346: Cannot get the boolean value of an option

Cause: The boolean value of the option could not be retrieved due to a security error.

Action: Review the message log and contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-20347: ODI-20347: Error during data transfer for drag and drop

Cause: An internal error occured while dropping the object into the diagram.

Action: Review the message log for additional information and contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-20348: ODI-20348: An interface with the same name already exists in this folder. Please change the name of the new interface.

Cause: An interface with the specified name exists in the folder. The interface name must be unique within a folder.

Action: Enter a new interface name that is unique within the folder.
Level: 32

Type: ERROR

Impact: Other

ODI-20349: ODI-20349: Unknown event detected by the event manager. Please contact Oracle Support Services.

Cause: The Package Event Manager was called to action an unknown event.

Action: Contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-20350: ODI-20350: Your diagram contains one or more FATAL/CRITICAL errors preventing display of the Flow Editor

Cause: The diagram is incomplete or contains errors that prevent the Flow Editor being displayed.

Action: Return to the diagram tab and review the error messages using the errors and warnings button in the toolbar. Fix the errors in order to access the Flow Editor.
Level: 32

Type: ERROR

Impact: Other

ODI-20351: ODI-20351: Error adding source to Quick Edit source table.

Cause: An internal error occured which prevented the source being added.

Action: Contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-20352: ODI-20352: Error adding target datastore to Quick Edit mapping table.

Cause: An internal error occured which prevented the target being added.

Action: Contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-20353: ODI-20353: Only a single column may be pasted into a Quick Edit table.

Cause: The clipboard contains multiple columns. Quick Edit only supports pasting a single cell into a table.

Action: Select the cells to be copied and paste them one at a time.
Level: 32

Type: ERROR

Impact: Other

ODI-20354: ODI-20354: Paste targets must be in the same column as the previous copy. This does not apply to Expression columns (Lookup Expression, Join Expression, Filter Expression, and Mapping Expression).

Cause: You have selected a value from one column, and tried to paste it into a different column. This is only supported for Expression Columns.

Action: Please enter the values into the cell manually.
Level: 32

Type: ERROR

Impact: Other

ODI-20355: ODI-20355: Duplicate value is not supported on this column.

Cause: The paste operation is not permitted in the Alias and Target Column Name fields as these fields must contain a unique value.

Action: Please enter the Alias or Name field manually.
Level: 32

Type: ERROR

Impact: Other

ODI-20356: ODI-20356: Can not perform paste into a read-only column.

Cause: The Paste operation is not permitted on read-only columns.

Action: You may not update this value in the table.
Level: 32

Type: ERROR

Impact: Other

ODI-20357: ODI-20357: Can not perform deletion because the target datastore is not temporary.

Cause: An attempt was made to delete a row in the target, but the target datastore is not a temporary table. Only rows in a temporary target table may be deleted.

Action: You cannot delete the row.
Level: 32

Type: ERROR

Impact: Other

ODI-20358: ODI-20358: Interface cannot be saved because it has a fatal error: {0}.

Cause: The Interface could not be saved because it contains a fatal error which must be resolved.

Action: Review the errors in the Diagram tab and resolve the fatal errors.
Level: 32

Type: ERROR

Impact: Other

ODI-20359: ODI-20359: Only one cell can be copied one at a time.

Cause: More than one cell was selected. Quick Edit only supports copying a single cell.

Action: Select and copy a single cell.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-20360: ODI-20360: Only Expression columns support Copy and Paste from other applications. For all other columns, please perform a copy first on that column before pasting.

Cause: Only values from other applications may be copied into Expression columns.

Action: For all other columns, perform a copy first on that column before pasting.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-20361: ODI-20361: Can not perform Copy and Paste across tables, except for Expression columns (Lookup Expression, Join Expression, Filter Expression, and Mapping Expression).

Cause: Values may not be copied between tables in Quick Edit, apart from between Expression columns.

Action: Please enter the values manually.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-20362: ODI-20362: Couldn't connect to Web Service

Cause: An error occured while creating a connection to the Web Service.

Action: Ensure that the Web Service is accessible and WSDL URL is correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20363: ODI-20363: Error while exporting request

Cause: The request could not be exported

Action: Check that there is sufficient disk space and that the target directory is accessible.
Level: 32

Type: ERROR

Impact: Other

ODI-20364: ODI-20364: Error while parsing the XML file

Cause: An error occured while parsing the XML file

Action: Ensure that the correct XML file is specified and that it is correctly structured
Level: 32

Type: ERROR

Impact: Other

ODI-20365: ODI-20365: There is no port with SOAP binding defined on this service

Cause: The referenced service does not support the specified port

Action: Specify a valid port for the service
Level: 32

Type: ERROR

Impact: Other

ODI-20366: ODI-20366: The timeout must be an integer value.

Cause: The value entered for the timeout is not a valid integer

Action: Enter a valid integer value
Level: 32

Type: ERROR

Impact: Other

ODI-20367: ODI-20367: Export directory {0} does not exist.

Cause: The specified directory does not exist

Action: Create the directory and repeat the operation
Level: 32

Type: ERROR

Impact: Other

ODI-20368: ODI-20368: WSDL URL is null or empty, ODI can not initialize the current request.

Cause: WSDL URL is null

Action: Set the WSDL URL or remove the soap request.
Level: 32

Type: ERROR

Impact: Other

ODI-20370: ODI-20370 : Shortcuts within a project can only refer to objects that belong to that same project

Cause: Shortcuts within a project can only refer to objects that belong to that same project

Action: =Try another folder destination
Level: 32

Type: ERROR

Impact: Other

ODI-20371: ODI-20371 : No two shortcut objects within a folder may refer to the same base object

Cause: No two shortcut objects within a folder may refer to the same base object

Action: Try another folder destination or fix folder contents
Level: 32

Type: ERROR

Impact: Other

ODI-20372: ODI-20372 : The source and destination models must be defined with the same Technology

Cause: The source and destination models must be defined with the same Technology

Action: Try another model destination or fix model properties.
Level: 32

Type: ERROR

Impact: Other

ODI-20373: ODI-20373 : No two shortcuts within a model may contain the same base object

Cause: No two shortcuts within a model may contain the same base object

Action: Try another folder destination or fix model contents.
Level: 32

Type: ERROR

Impact: Other

ODI-20374: ODI-20374 : A model cannot contain a datastore and a datastore shortcut to another datastore with the same datastore name

Cause: A model cannot contain a datastore and a shortcut to another datastore with the same datastore name

Action: Try another folder destination or fix model contents.
Level: 32

Type: ERROR

Impact: Other

ODI-20701: ODI-20701: The Name field is mandatory.

Cause: The Name field was not entered.

Action: Enter a name for the Load Plan.
Level: 32

Type: ERROR

Impact: Other

ODI-20702: ODI-20702: The name given for the Load Plan is already used by another load plan. Please provide another name.

Cause: The name provided for the Load Plan was not unique.

Action: Enter a unique name for the Load Plan.
Level: 32

Type: ERROR

Impact: Other

ODI-20703: ODI-20703: Variable "{0}" is not found.

Cause: The variable could not be found.

Action: Provide another name for the variable.
Level: 32

Type: ERROR

Impact: Other

ODI-20704: ODI-20704: Datatype of variable "{0}" has been changed.

Cause: The datatype of the original variable is different to the datatype of the load plan variable.

Action: Verify the datatype of the variable and ensure that the types of the original and load plan variables match.
Level: 32

Type: ERROR

Impact: Other

ODI-20705: ODI-20705: This variable is used in one or more case steps. Removing it will trigger deletion of those case steps, and all of their child steps. Do you want to continue?

Cause: An attempt was made to remove a variable which is used in one or more case steps.

Action: To remove the variable and its associated case steps, click Yes. Otherwise, click No, and nothing will be removed.
Level: 32

Type: WARNING

Impact: Other

ODI-20706: ODI-20706: The Step Name is mandatory.

Cause: The Step Name field was not entered.

Action: Enter a name for the Step.
Level: 32

Type: ERROR

Impact: Other

ODI-20707: ODI-20707: The Variable is mandatory.

Cause: A Variable was not selected.

Action: Select a variable.
Level: 32

Type: ERROR

Impact: Other

ODI-20708: ODI-20708: The Scenario is mandatory.

Cause: A Scenario was not selected.

Action: Select a Scenario.
Level: 32

Type: ERROR

Impact: Other

ODI-20709: ODI-20709: The Value is mandatory.

Cause: A Value was not provided.

Action: Enter a Value.
Level: 32

Type: ERROR

Impact: Other

ODI-20710: ODI-20710: The Value format is not valid.

Cause: An incorrect format was given for the Value.

Action: Check the format of the Value and correct it.
Level: 32

Type: ERROR

Impact: Other

ODI-20711: ODI-20711: The Step Name is mandatory.

Cause: The Step Name field was not entered.

Action: Provide the name of the Step.
Level: 32

Type: ERROR

Impact: Other

ODI-20712: ODI-20712: The Variable is mandatory.

Cause: A Variable was not selected.

Action: Select a Variable.
Level: 32

Type: ERROR

Impact: Other

ODI-20713: ODI-20713: The Scenario is mandatory.

Cause: A Scenario was not selected.

Action: Select a Scenario.
Level: 32

Type: ERROR

Impact: Other

ODI-20714: ODI-20714: The Context is mandatory.

Cause: A Context was not selected for execution.

Action: Select an execution Context.
Level: 32

Type: ERROR

Impact: Other

ODI-20715: ODI-20715: The Logical Agent is mandatory.

Cause: A Logical Agent was not selected for execution.

Action: Select a Logical Agent.
Level: 32

Type: ERROR

Impact: Other

ODI-20716: ODI-20716: No Physical Agent is defined for the selected Logical Agent and Context. Edit Logical Agent "{0}", and define a Physical Agent for Context "{1}".

Cause: There was no Physical Agent associated with this Logical Agent in the specified context.

Action: Associate a Physical Agent with the Logical Agent in the selected context.
Level: 32

Type: ERROR

Impact: Other

ODI-20717: ODI-20717: No Physical Agents are running. A Physical Agent must be running in order to Restart a Load Plan.

Cause: There were no Physical Agents running.

Action: Start a Physical Agent before restarting the Load Plan.
Level: 32

Type: ERROR

Impact: Other

ODI-20718: ODI-20718: No Physical Agents are running. A Physical Agent must be running in order to Stop a Load Plan.

Cause: There were no Physical Agents running.

Action: Start the Agent before executing the Load Plan.
Level: 32

Type: ERROR

Impact: Other

ODI-20719: ODI-20719: Scenario "{0}" is not found.

Cause: The scenario was not found.

Action: Specify an existing scenario.
Level: 32

Type: ERROR

Impact: Other

ODI-20720: ODI-20720: Physical Agent "{0}" - which is defined in Logical Agent "{1}" to be used for Context "{2}" - is not responding. Verify that Physical Agent "{0}" has been started.

Cause: The Physical Agent was not reachable.

Action: Check the Physical Agent and start it.
Level: 32

Type: ERROR

Impact: Other

ODI-20721: ODI-20721: Interface contains one or more errors. You should correct the errors before attempting to execute it

Cause: The interface contains errors which prevent it from being executed.

Action: Review the errors shown in the interface editor and update the interface to fix the problems.
Level: 32

Type: ERROR

Impact: Other

ODI-20722: ODI-20722: Cannot display data. Source alias is {0} characters long which is longer than allowed by the technology ({1}). Please review the technology settings in Topology.

Cause: Source alias exceeded the limit allowed by its technology.

Action: Ensure the maximum table name length setting in the corresponding technology is correct. Consider changing source alias to comply.
Level: 32

Type: ERROR

Impact: Other

ODI-20723: ODI-20723: There is no any version of scenario {0} found. A scenario of the step {1} cannot be refreshed.

Cause: The scenario of step was not found.

Action: Check if specified scenario for this step is correct.
Level: 32

Type: WARNING

Impact: Other

ODI-20724: ODI-20724: Journalized data not found. Journal data view: {0}

Cause: Journal is not started or is stopped.

Action: Ensure the journal is started: select Changed Data Capture > Journal Data.
Level: 32

Type: ERROR

Impact: Other

ODI-20726: ODI-20726: The Step Name is mandatory.

Cause: The Step Name field was not entered.

Action: Enter a name for the Step.
Level: 32

Type: WARNING

Impact: Other

ODI-20727: ODI-20727: Scenario "{0}" parent is not found.

Cause: The Scenario source object does not exist.

Action: Check if the source object, from which the Scenario was generated, does exist.
Level: 32

Type: ERROR

Impact: Other

ODI-20728: ODI-20728: The attribute name is mandatory

Cause: The datastore attribute could not be saved because the mandatory Name field was not entered.

Action: Enter a value in the attribute name field.
Level: 32

Type: ERROR

Impact: Other

ODI-20729: ODI-20729: {0} is a dependant object of the following object(s) {1} and cannot be removed

Cause: Selected object for removal is a dependent object.

Action: Remove the dependent object first.
Level: 32

Type: ERROR

Impact: Other

ODI-20731: ODI-20731: The parent from which this scenario is generated does not exist anymore so the editor couldn't show the parent related information.

Cause: The editor couldn't show the parent related information because the scenario parent does not exist anymore. This could happen, for example, if you imported the scenario, but didn't import it's parent object.

Action: Try to figure out, why the scenario parent object does not exist. Try to restore the parent.
Level: 32

Type: ERROR

Impact: Other

ODI-20732: ODI-20732: You cannot move a submodel into another model.

Cause: An unsupported operation was attempted.

Action: Submodels cannot be moved into hierarchy of another models.
Level: 32

Type: ERROR

Impact: Other

ODI-20733: ODI-20733: You cannot copy a submodel into another model.

Cause: An unsupported operation was attempted.

Action: Submodels cannot be copied into hierarchy of another models.
Level: 32

Type: ERROR

Impact: Other

ODI-20734: ODI-20734: Changing the name of a user function only impacts the user function itself; Users need to manually change object(s) which reference the old user function name.

Cause: The user function name has been updated

Action: It is the user's responsibility to determine where the user function is referenced and to manually change the name of the user function in those places
Level: 32

Type: WARNING

Impact: Other

ODI-20735: ODI-20735: The name given for the Physical Agent is already used by another agent. Please provide another name

Cause: The name provided for the Physical Agent was not unique.

Action: Enter a unique name for the Physical Agent.
Level: 32

Type: ERROR

Impact: Other

ODI-20736: ODI-20736: The Name field is mandatory.

Cause: The value for the Name field was not specified.

Action: Enter a name for the Object.
Level: 32

Type: ERROR

Impact: Other

ODI-20737: Could not build WSDL Model.

Cause: An unexpected error occurred while building a WSDL model.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20741: ODI-20741: This is not a valid Cobol Copybook.

Cause: The file chosen in the Reverse Engineering Cobol Copybook process is not a valid Cobol Copybook.

Action: Ensure the file is a valid Cobol Copybook.
Level: 32

Type: ERROR

Impact: Other

ODI-20742: ODI-20742: You cannot copy a mapping into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Mappings cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20743: ODI-20743: You cannot copy a reusable mapping into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Reusable mappings cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20744: ODI-20744: You cannot move a mapping into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Mappings cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20745: ODI-20745: You cannot move a reusable mapping into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Reusable mappings cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20746: ODI-20746: You cannot move a global reusable mapping into a folder.

Cause: An unsupported operation was attempted.

Action: Global Reusable mappings cannot be moved into a folder.
Level: 32

Type: ERROR

Impact: Other

ODI-20747: ODI-20747: You cannot copy a global reusable mapping into a folder.

Cause: An unsupported operation was attempted.

Action: Global Reusable mappings cannot be copied into a folder.
Level: 32

Type: ERROR

Impact: Other

ODI-20748: ODI-20748: Open is not valid for this node.

Cause: The editor is not applicable for this node.

Action: Editor cannot be opened for this node.
Level: 32

Type: ERROR

Impact: Other

ODI-20749: ODI-20749: Selected Capture/Initial Load Capture process is associated with another model. This may cause conflicts during 'Start Journal' action, if the logical process instance selected uses the same physical process instance.

Cause: Selected Goldengate Capture/Initial Load Capture process is used in a different model.

Action: Select a different set of process instances for this model.
Level: 32

Type: ERROR

Impact: Other

ODI-20750: ODI-20750: Selected Delivery/Initial Load Delivery process is associated with another model. This may cause conflicts during 'Start Journal' action, if the logical process instance selected uses the same physical process instance.

Cause: Selected Goldengate Delivery/Initial Load Delivery process is used in a different model.

Action: Select a different set of process instances for this model.
Level: 32

Type: ERROR

Impact: Other

ODI-20751: ODI-20751: Load Plan Debugging is not supported: {0}.

Cause: An unsupported operation was attempted.

Action: Load Plan can't be debug.
Level: 32

Type: ERROR

Impact: Other

ODI-20752: ODI-20752: Format can not be empty for File datastore's Date type column

Cause: Column added for the File datastore has Date as type but Format is not given

Action: Ensure the Format is entered for File datatsore's column of type Date.
Level: 32

Type: ERROR

Impact: Other

ODI-20753: ODI-20753 : Shortcuts in a Model can not be moved

Cause: Shortcuts in a Model can not be moved to another Model

Action: Please get the base object of the shortcut first and then try to move
Level: 32

Type: ERROR

Impact: Other

ODI-20754: ODI-20754 : Driver name cannot be empty

Cause: Driver is not assigned for the Data Server

Action: Please choose the appropriate driver for the datastore.
Level: 32

Type: ERROR

Impact: Other

ODI-20755: ODI-20755: A Data Server with the name {0} already exists. Please provide another name.

Cause: The name provided for the Data Server is not unique.

Action: Enter a unique name for the Data Server.
Level: 32

Type: ERROR

Impact: Other

ODI-20756: ODI-20756: A Logical Schema with the name {0} already exists. Please provide another name.

Cause: The name provided for the Logical Schema is not unique.

Action: Enter a unique name for the Data Server.
Level: 32

Type: ERROR

Impact: Other

ODI-20757: ODI-20757: If logical schema is specified, WSDL URL can not differ from physical schema's WSDL URL.

Cause: You have specified different WSDL URL compared to physical schema WSDL URL.

Action: WSDL URL and physical schema WSDL URL should be same when logical schema is specified.
Level: 32

Type: ERROR

Impact: Other

ODI-20758: ODI-20758: If logical schema is specified, HTTP User can not differ from physical schema's/data server's HTTP User.

Cause: You have specified different user compared to physical schema/data server HTTP user.

Action: User and physical schema/data server HTTP user should be same when logical schema is specified.
Level: 32

Type: ERROR

Impact: Other

ODI-20759: ODI-20759: If logical schema is specified, Port Type can not differ from physical schema's port type.

Cause: You have specified different port type compared to physical schema port type.

Action: Port type and physical schema port type should be same when logical schema is specified.
Level: 32

Type: ERROR

Impact: Other

ODI-20760: ODI-20760: Choice names should be unique.

Cause: You have added duplicate choice names.

Action: Ensure only unique choice names are used.
Level: 32

Type: ERROR

Impact: Other

ODI-20761: ODI-20761: An Option Group with the name {0} already exists. Please provide another name.

Cause: The name provided for the Option Group is not unique.

Action: Enter a unique name for the Option Group.
Level: 32

Type: ERROR

Impact: Other

ODI-20763: ODI-20763: Maximum number of login attempts reached. ODI User will be locked.

Cause: You have exceeded the maximum number of login attempts.

Action: A Supervisor user must unlock this user.
Level: 32

Type: ERROR

Impact: Other

ODI-20764: ODI-20764: Error occurred while creating version for regenerated Scenario.

Cause: Auto versioning failed for the regenerated Scenario

Action: Please check log for more information
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: An unexpected error occurred while generating data services.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-23023: ODI-23023: The Schema path ({0}) is not supported

Cause: The Model's Physical Schema attempted to define the Schema path using an unsupported protocol (ftp, http or file).

Action: Change the Physical Schema to not use ftp, http or file protocol to reference the file.
Level: 32

Type: ERROR

Impact: Other

ODI-23024: ODI-23024: The URL is mandatory.

Cause: The URL field has not been entered and is a mandatory parameter.

Action: Enter the URL parameter. A template chosen from the drop down list may help to ensure the syntax is correct.
Level: 32

Type: ERROR

Impact: Other

ODI-23025: ODI-23025: The ID is mandatory.

Cause: The Repository ID parameter has not been entered and is a mandatory parameter.

Action: Enter an integer value for the Repository ID parameter.
Level: 32

Type: ERROR

Impact: Other

ODI-23026: ODI-23026: The ID must be an integer value.

Cause: The value entered for the Repository ID is not a valid integer.

Action: Enter an integer value for the Repository ID parameter.
Level: 32

Type: ERROR

Impact: Other

ODI-23027: ODI-23027: The driver is mandatory.

Cause: A JDBC Driver was not specified and is a mandatory parameter.

Action: Select a JDBC Driver from the list of values.
Level: 32

Type: ERROR

Impact: Other

ODI-23028: ODI-23028: The password is mandatory.

Cause: The Supervisor user's Password parameter was not specified.

Action: Enter the Supervisor password.
Level: 32

Type: ERROR

Impact: Other

ODI-23029: ODI-23029: The confirm password is mandatory.

Cause: The Supervisor user's Confirm Password parameter was not specified.

Action: Enter the Supervisor user's password in the Confirm Password parameter.
Level: 32

Type: ERROR

Impact: Other

ODI-23030: ODI-23030: Password and Confirm Password are different

Cause: The Password and Confirm Password parameters are not the same.

Action: Ensure the same value is entered for both the Password and Confirm Password parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-23031: ODI-23031: The Supervisor username is mandatory.

Cause: The Supervisor User parameter was not entered.

Action: Enter a value for the Supervisor User parameter ensuring it matches a user in the external enterprise identify store, or switch to ODI Authentication.
Level: 32

Type: ERROR

Impact: Other

ODI-23032: ODI-23032: Maximum number of sessions cannot be less or equal to 0.

Cause: The Maximum Number of Sessions parameter value was specified as 0.

Action: Change the Maximum Number of Sessions parameter in the Agent Definition tab to a value greater than 0.
Level: 32

Type: ERROR

Impact: Other

ODI-23033: ODI-23033: The file reverse-engineering is only possible for delimited files.

Cause: The file format for the specified file was not delimited.

Action: Select a delimited format file and retry the reverse-engineering action.
Level: 32

Type: ERROR

Impact: Other

ODI-23035: ODI-23035: Can not update the scheduling - This agent may not be running

Cause: The Update Scheduling action could not be performed because the ODI Client could not connect to the Agent.

Action: Check that the Agent connection details are correct and that the agent is running. Use the Agent Test button to check the connection details.
Level: 32

Type: ERROR

Impact: Other

ODI-23036: ODI-23036: Logical Schema not set for this Context

Cause: A Logical Schema entry in the Physical Schema's Context was specified as <Undefined>.

Action: Ensure none of the Logical Schemas on the Physical Schema's Context tab are set to <Undefined>.
Level: 32

Type: ERROR

Impact: Other

ODI-23037: ODI-23037: To use scheduling please associate a Logical Agent to a Physical Agent via the Logical Architecture Accordion in the Topology Navigator

Cause: There are no logical agents available to use for scheduling.

Action: Associate a logical agent with a physical agent using the Topology Navigator and then resubmit your schedule request.
Level: 32

Type: ERROR

Impact: Other

ODI-23038: ODI-23038: Cannot resolve the table name. Check the masks defined for this physical schema.

Cause: The table and schema format could not be calculated. This is because the object mask has not been set for the Physical Schema that contains this table.

Action: From the Topology Navigator edit the Physical Schema containing this table and ensure the Masks parameter value is valid for the schema based on its technology (for example "%SCHEMA.%OBJECT").
Level: 32

Type: ERROR

Impact: Other

ODI-23039: ODI-23039: You cannot carry out this type of export.

Cause: The export type specified is not supported.

Action: Retry the export. If the problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23040: ODI-23040: Import file "{0}" error

Cause: An error occured during the import file process.

Action: Correct any errors identified in the error log and retry the import process. If the problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23042: ODI-23042: An error occurred while changing the repository number.

Cause: An error occured while changing the repository number.

Action: Correct any errors identified in the message log and retry the action. If the problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23043: ODI-23043: The Repository ID must be numeric.

Cause: The value specified for the Repository ID parameter was not a valid numeric value.

Action: Enter a valid numeric value for the Repository ID parameter.
Level: 32

Type: ERROR

Impact: Other

ODI-23044: ODI-23044: The new ID you have chosen is already in use as a table "{0}" primary key. The renumbering has been aborted. No changes have been made.

Cause: The Repository ID specified is already used by an existing object.

Action: Enter a different value for the Repository ID parameter ensuring it is unique within the repository.
Level: 32

Type: ERROR

Impact: Other

ODI-23045: ODI-23045: You may not renumber a repository before version 11. Please upgrade your repository first.

Cause: The renumber functionality is not supported for ODI Repository versions prior to version 11.

Action: Upgrade the repository to version 11 (or higher) and then renumber it.
Level: 32

Type: ERROR

Impact: Other

ODI-23046: ODI-23046: An error was encountered during the test.

Cause: An attempt to connect a Work Repository failed.

Action: Correct any errors identified in the message log. Ensure the Work Repositories are available and the connection information is correctly specified in the Master Repository. Retry the test.
Level: 32

Type: ERROR

Impact: Other

ODI-23047: ODI-23047: Could not connect to the work repository. The renumbering process has been aborted. No changes have been made.

Cause: An attempt to connect a Work Repository failed.

Action: Correct any errors identified in the message log. Ensure the Work Repositories are available and the connection information is correctly specified in the Master Repository. Retry the test.
Level: 32

Type: ERROR

Impact: Other

ODI-23048: ODI-23048: Import report generation error

Cause: The import was performed, but there was an unexpected error while opening the Import Report.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23049: ODI-23049: Error Detected during Repository Installation

Cause: An error occured during the creation or import of the Master Repository.

Action: Correct any errors described in the message log and retry the installation process. If the problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23050: ODI-23050: The password you entered doesn't match the actual password

Cause: The password you entered doesn't match the actual password

Action: Ensure that the password entered matches the actual password
Level: 32

Type: ERROR

Impact: Other

ODI-23051: ODI-23051: Maximum number of threads must be greater than zero.

Cause: Values for maximum number of threads is not valid

Action: Enter valid value for maximum number of threads
Level: 32

Type: ERROR

Impact: Other

ODI-23052: ODI-23052: Maximum number of thread per session cannot be less than 0.

Cause: Values for maximum number of thread per session is not valid

Action: Enter valid value for maximum number of threads per session
Level: 32

Type: ERROR

Impact: Other

ODI-23053: ODI-23053: Maximum number of threads cannot be less than maximum number of threads per session.

Cause: Maximum number of threads less than maximum number of threads per session

Action: Enter valid values for maximum number of threads and maximum number of threads per session
Level: 32

Type: ERROR

Impact: Other

ODI-23054: ODI-23054: Maximum number of cache entries cannot be less than zero.

Cause: Values for maximum number of cache entries is not valid

Action: Enter valid values for maximum number of cache entries
Level: 32

Type: ERROR

Impact: Other

ODI-23055: ODI-23055: Session Blueprint Lifetime cannot be less than zero.

Cause: Value for session blueprint lifetime is not valid

Action: Enter valid values forsession blueprint lifetime
Level: 32

Type: ERROR

Impact: Other

ODI-23056: ODI-23056: Syntax of condition "{0}" is not valid.

Cause: The entered condition has invalid syntax.

Action: Specify the valid condition expression.
Level: 32

Type: ERROR

Impact: Other

ODI-23057: ODI-23057: The Registry Database is mandatory for MySQL Technology.

Cause: The Registry Database was not specified for MySQL Technology.

Action: Enter the Registry Database for MySQL Technology.
Level: 32

Type: ERROR

Impact: Other

ODI-23058: ODI-23058: This Technology does not support multiple schemas.

Cause: Attempt to create multiple Physical Schemas for Technologies that support only one Schema.

Action: The solution for Technologies that do not support multiple Physical Schemas is to create separate Data Dervers from the Physical Schemas.
Level: 32

Type: ERROR

Impact: Other

ODI-23059: ODI-23059: No Agent selected

Cause: No Agent has been selected for the selected DataSource.

Action: Make sure an Agent is selected for the DataSource.
Level: 32

Type: ERROR

Impact: Other

ODI-23060: ODI-23060: Update Import Modes are not valid for Interfaces

Cause: An invalid import mode of Update is selected for an Interface export file.

Action: Use an import mode other than Update or alternatively only import Mapping export files
Level: 32

Type: ERROR

Impact: Other

ODI-23061: ODI-23061: Syntax of expression "{0}" is not valid.

Cause: The entered expression has invalid syntax.

Action: Specify the valid expression.
Level: 32

Type: ERROR

Impact: Other

ODI-23062: ODI-23062: Maximum number of threads cannot be less then the maximum number of sessions.

Cause: Value for maximum number of threads is less than the maximum number of sessions

Action: Ensure that maximum number of threads is equal to or greater than the maximum number of sessions
Level: 32

Type: ERROR

Impact: Other

ODI-23064: ODI-23064 Language Name must be specified

Cause: Language name is not specified.

Action: Enter Language name on the Languages table.
Level: 32

Type: ERROR

Impact: Other

ODI-23065: ODI-23065 Invalid Parameter values. Key names not unique

Cause: Invalid values.

Action: Parameter values need to be valid including uniquenames for keys.
Level: 32

Type: ERROR

Impact: Other

ODI-23066: ODI-23066: Letter used in the icon input "{0}" is not valid. No Special Characters are allowed to be entered.

Cause: The entered input is invalid.

Action: Enter the valid value.
Level: 32

Type: ERROR

Impact: Other

ODI-23068: ODI-23068 : Degree Of Parallelism For Target has to be in the range of 1 to 99.

Cause: Value entered for Degree Of Parallelism is not in the range 1-99.

Action: Please choose the appropriate Degree Of Parallelism For Target.
Level: 32

Type: ERROR

Impact: Other

ODI-23069: ODI-23069 : Web Application Context must be provided

Cause: No value entered for the Web Application Context.

Action: Please enter value for the Web Application Context.
Level: 32

Type: ERROR

Impact: Other

ODI-23070: ODI-23070: Port number must be an integer between 0 and 65535.

Cause: The value for the Port Number was not valid.

Action: Enter a valid integer value between 0 and 65535 for the Port Number.
Level: 32

Type: ERROR

Impact: Other

ODI-23071: ODI-23071: Invalid Override Endpoint URL.

Cause: Override Endpoint URL enterred is invalid.

Action: Please enter a valid Override Endpoint URL.
Level: 32

Type: ERROR

Impact: Other

ODI-23072: ODI-23072: Invalid WSDL URL.

Cause: WSDL URL enterred is invalid.

Action: Please enter a valid WSDL URL.
Level: 32

Type: ERROR

Impact: Other

ODI-24004: ODI-24004: There are no supervisor accounts in the ODI repository with matching entries in the identity store. Please provide a suitable supervisor account. Or you may also want to double check your JPS configuration file e.g. jps-config-jse.xml regarding the identity store configuration on properties such as {0}.

Cause: The ODI repository does not have any supervisor account that matches the entries in the identity store based on the identity store configuration from JPS configuration file.

Action: Create a supervisor account in the ODI repository that matches an entry in the identify store. Or you may also want to double check your JPS configuration file e.g. jps-config-jse.xml file regarding the identity store configuration on properties such as username.attr, groupname.attr, user.search.bases, group.search.bases.
Level: 32

Type: ERROR

Impact: Other

ODI-24005: ODI-24005: An error occurred while checking the status of the master repository.

Cause: An unexpected error occurred.

Action: Check the exception to see if it gives details about the error and contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-24006: ODI-24006: An error occurred while switching the authentication mode for the master repository.

Cause: An unexpected error occurred.

Action: Check the exception to see if it gives details about the error and contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-24007: ODI-24007: Rules should not have empty conditions.

Cause: Rules associated with policy have empty conditions.

Action: Create rules with conditions associated with them.
Level: 32

Type: ERROR

Impact: Other

ODI-25001: ODI-25001: Unable to input a larger element

Cause: The total length of all keywords exceeds the maximum length.

Action: Remove one or more of the keywords, or decrease their lengths.
Level: 32

Type: ERROR

Impact: Other

ODI-25002: ODI-25002: The end date cannot be before the start date.

Cause: The end date is before the start date.

Action: Set the end date to be after the start date.
Level: 32

Type: ERROR

Impact: Other

ODI-25003: ODI-25003: Error while starting session

Cause: An unexpected error occured while starting the session.

Action: Check the error details for further information and contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-25004: ODI-25004: Date Format Not Valid

Cause: One of the Date fields is invalid. This may be the From or To Date.

Action: Click the button to the right of the field to invoke a dialog for entering a valid Time and Date.
Level: 32

Type: ERROR

Impact: Other

ODI-25005: ODI-25005: Incorrect date format . The format is {0}.

Cause: The date format is incorrect.

Action: Use the format that is presented in the error message.
Level: 32

Type: ERROR

Impact: Other

ODI-25006: ODI-25006: At least one agent must be selected.

Cause: Agent selection is mandatory.

Action: Select at least one agent to clean stale sessions.
Level: 32

Type: ERROR

Impact: Other

ODI-25007: ODI-25007: At least one work repository must be selected.

Cause: Work repository selection is mandatory.

Action: Select at least one work repository to clean stale sessions.
Level: 32

Type: ERROR

Impact: Other

ODI-25008: ODI-25008: You are not allowed to delete session variable.

Cause: User attempt to delete session variable.

Action: Cancel deleting session variable.
Level: 32

Type: ERROR

Impact: Other

ODI-25009: ODI-25009: You are not allowed to delete scenario variable.

Cause: User attempt to delete scenario variable.

Action: Cancel deleting scenario variable.
Level: 32

Type: ERROR

Impact: Other

ODI-26001: ODI-26001: Boolean does not correspond to the Field Update Object Layer.

Cause: The repository contained an invalid value of the Field Update property for a checkbox or radio group.

Action: Ensure the repository value is a boolean for checkbox or a valid action command for a radio group.
Level: 32

Type: ERROR

Impact: Other

ODI-26002: ODI-26002: This object is referenced by another object. View the details for more information. You may also see where this object is used in the hierarchy.

Cause: The specified object could not be used because it is referenced by another object.

Action: Remove references to this object. The "Uses" hierarchy may be useful in finding objects references.
Level: 32

Type: ERROR

Impact: Other

ODI-26003: ODI-26003: This object cannot be removed: it is referenced by another object.

Cause: The specified object could not be deleted because it is referenced by another object.

Action: Remove references to this object before deleting it. The "Uses" hierarchy may be useful in finding objects references.
Level: 32

Type: ERROR

Impact: Other

ODI-26004: ODI-26004: Action denied:

Cause: The current license may not allow use of the designer.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-26005: ODI-26005: You are importing an object from another repository with the same identifier. It is forbidden.

Cause: An object in the import file has an identifier which already exists in the repository.

Action: Consider manually changing the "com.sunopsis.dwg.dwgobj.SnpImportRep" object section of the import XML file to use a unique identifier.
Level: 32

Type: ERROR

Impact: Other

ODI-26006: ODI-26006: The specified encryption key is invalid.

Cause: The encryption key specified was found to be invalid during the decrypting phase.

Action: Ensure a valid encryption key is utilized.
Level: 32

Type: ERROR

Impact: Other

ODI-26007: ODI-26007: KM or Procedure not encrypted. No decryption was performed.

Cause: Decryption was requested for a non-encypted KM or Procedure.

Action: Do not attempt to decrypt a non-encrypted KM or Procedure.
Level: 32

Type: ERROR

Impact: Other

ODI-26008: ODI-26008: Scenario not encrypted. No decryption was performed.

Cause: Decryption was requested for a non-encypted Scenario.

Action: Do not attempt to decrypt a non-encrypted Scenario.
Level: 32

Type: ERROR

Impact: Other

ODI-26009: ODI-26009: Action not encrypted. No decryption was performed.

Cause: Decryption was requested for a non-encypted Action.

Action: Do not attempt to decrypt a non-encrypted Action.
Level: 32

Type: ERROR

Impact: Other

ODI-26010: ODI-26010: Decryption failed due to incompatible key.

Cause: The key provided to decrypt was an invalid key.

Action: Ensure the decryption key is correctly specified.
Level: 32

Type: ERROR

Impact: Other

ODI-26011: ODI-26011: unable to find specified encryption API

Cause: The specified cryptographic algorithm requested was not available in the environment.

Action: Ensure the environment can access the DES/ECB/PKCS5Padding algorithms and padding.
Level: 32

Type: ERROR

Impact: Other

ODI-26012: ODI-26012: invalid encrypted data.

Cause: The BASE64 content may be invalid or the zip file contents may be corrupted.

Action: Ensure the encrypted data is correct and the decryption key is correctly specified.
Level: 32

Type: ERROR

Impact: Other

ODI-26013: ODI-26013: Your security parameters are insufficient to perform this action.

Cause: The ODI user security parameters do not specifically permit the user to perform this particular action.

Action: Ensure this ODI user is granted the security access to perform this action.
Level: 32

Type: ERROR

Impact: Other

ODI-26014: ODI-26014: The code of your {0} is already used by another {1}. Please give another code to save this {2}.

Cause: The value entered for code must be unique for the entire work repository.

Action: Ensure the a unique value is entered.
Level: 32

Type: ERROR

Impact: Other

ODI-26015: ODI-26015: You do not have sufficient privileges to perform this operation.

Cause: The ODI user security parameters do not specifically permit the user to perform this particular operation.

Action: Ensure this ODI user is granted the security access to perform this operation.
Level: 32

Type: ERROR

Impact: Security

ODI-26016: ODI-26016: The requested operation cannot succeed. The object no longer exists.

Cause: The specified ODI object cannot be accessed because it no longer exists in the repository (it may have been deleted by another ODI user).

Action: Recreate the specified ODI object. Consider importing the object from a backup.
Level: 32

Type: ERROR

Impact: Other

ODI-26017: ODI-26017: Error.

Cause: Internal error.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-26018: ODI-26018: Key Error.

Cause: An unexpected error occurred.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-26019: ODI-26019: Action Denied.

Cause: An unexpected error occurred.

Action: Review the error details for further information.
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: Internal error.

Action: No action required.
Level: 32

Type: ERROR

Impact: Other

ODI-26029: ODI-26029: Could not deploy the datasource automatically.

Cause: Weblogic Administration server is not up and running, the server connection parameters are wrong.

Action: Please check Weblogic Administration server connection parameters and the server state.
Level: 32

Type: ERROR

Impact: Other

ODI-26030: ODI-26030: The new password does not meet the password policy. Your change could not be saved.

Cause: The new password does not meet the password policy.

Action: Please verify that the new password meets the password policy (go to the "Security Navigator -> Password policies...").
Level: 32

Type: ERROR

Impact: Other

ODI-26031: ODI-26031: You may not delete work repository {0} because you are connected to it. To delete this repository, reconnect to a different work repository or use a master repository only connection.

Cause: Deletion of a work repository which is currently connected is not supported.

Action: Disconnect from the repository and then connect utilizing a Master Repository Only connection or a different work repository before attempting to delete the specified work repository.
Level: 32

Type: ERROR

Impact: Other

ODI-26032: ODI-26032: This object was modified by {0} on {1} at {2}. Your changes cannot be saved.

Cause: The object was changed in the repository after the editor was opened for this object.

Action: Close the editor without saving changes. Open the editor again and reapply the edits and save. Note: consider using the lock object facility to disallow current modifications to an object.
Level: 32

Type: ERROR

Impact: Other

ODI-26033: ODI-26033: You cannot edit this object because it is locked by another user ({0}). You can only view it.

Cause: The ODI object opened for editing is locked by another user. Other ODI users can only view such objects.

Action: Try to edit the object later.
Level: 32

Type: ERROR

Impact: Other

ODI-26034: ODI-26034: An error occurred while deleting executions.

Cause: The specified executions could not be deleted. This is possibly caused by the repository database connection problems.

Action: Retry to delete the executions. If problem persists, contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26035: ODI-26035: Error.

Cause: Internal error.

Action: Review the error details for further information.
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: An unexpected error occurred searching for a host variable.

Action: Review the error details for further information.
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: An unexpected error occurred while importing an XML document.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-26053: ODI-26053: An error occurred during initialization.

Cause: Initialization failed possibly due a repository access failure or insufficient ODI security permissions.

Action: Ensure the repository database is available, and the ODI user security permissions permit connection.
Level: 32

Type: ERROR

Impact: Other

ODI-26054: ODI-26054: Page not available.

Cause: The selected page number was invalid.

Action: Ensure the page number entered is greater than 0 and less than the total number of pages.
Level: 32

Type: ERROR

Impact: Other

ODI-26056: ODI-26056: Error while disconnecting.

Cause: This error is occured while closing the repository database connection after "Test query" action completed.

Action: This error may be ignored.
Level: 32

Type: ERROR

Impact: Other

ODI-26057: ODI-26057: Unable to connect the agent. The agent is probably not started.

Cause: The connection request to the agent failed.

Action: Ensure the agent is started and available. Ensure the connection information is valid.
Level: 32

Type: ERROR

Impact: Other

ODI-26058: ODI-26058: Unable to connect the agent. The agent URL cannot be found.

Cause: The connection request to the agent failed using the given URL.

Action: Ensure the agent is started and available. Ensure the connection URL information is valid.
Level: 32

Type: ERROR

Impact: Other

ODI-26059: ODI-26059: Object on method setObjectDisplay(Object pObjectDisplay) is not a List.

Cause: An unexpected error occured setting ObjectData.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26060: ODI-26060: The Password and Confirmation Password do not match.

Cause: The values entered for Password and Confirmation Password did not match.

Action: Enter the same value for Password and Confirmation Password.
Level: 32

Type: ERROR

Impact: Other

ODI-26061: ODI-26061: The minimum password length is {0} characters.

Cause: The length of the Password entered is less than specified in password policy rule.

Action: Enter a Password whose length is greater than or equal to the specified minimum length.
Level: 32

Type: ERROR

Impact: Other

ODI-26062: ODI-26062: The password violates the following rule: "{0}". Select another password.

Cause: The password supplied was invalid.

Action: Enter a valid password.
Level: 32

Type: ERROR

Impact: Other

ODI-26063: ODI-26063: Invalid password.

Cause: The password supplied was invalid.

Action: Enter a valid password.
Level: 32

Type: ERROR

Impact: Other

ODI-26064: ODI-26064: Error while exporting.

Cause: An error occured during the creation of the Export file.

Action: Ensure the repository is accessible and the export file and its directory are writable.
Level: 32

Type: ERROR

Impact: Other

ODI-26065: ODI-26065: You must specify all the options.

Cause: This is caused by programmatic error.

Action: ODI users should normally never see this message.
Level: 32

Type: ERROR

Impact: Other

ODI-26066: ODI-26066: An unexpected error has occurred.

Cause: An unexpected error occured this process.

Action: Retry action. If problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26067: ODI-26067: mandatory field "Java charset" not entered

Cause: A value for the "Java character set" field was not entered.

Action: Enter a value for the "Java character set" field.
Level: 32

Type: ERROR

Impact: Other

ODI-26068: ODI-26068: unable to load export list in the module: {0}

Cause: The contents of the export file list was not formatted correctly.

Action: Correct the format of the export list file specified.
Level: 32

Type: ERROR

Impact: Other

ODI-26069: ODI-26069: The specified export directory does not exist.

Cause: The specified export directory is invalid.

Action: Ensure the specified export directory exists and is writable.
Level: 32

Type: ERROR

Impact: Other

ODI-26070: ODI-26070: The Open Tool class name must not begin with "Snp" or "Odi".

Cause: The Open Tool class name begins with "Snp" or "Odi".

Action: Ensure the Open Tool class name does not begin with "Snp" or "Odi".
Level: 32

Type: ERROR

Impact: Other

ODI-26071: ODI-26071: Open Tool not activated. Your Open Tool references a class which not found.

Cause: The class name specified in this Open Tool was not found.

Action: Ensure the Open Tool class name specified is valid and available in the class path.
Level: 32

Type: ERROR

Impact: Other

ODI-26072: ODI-26072: Your Open Tool has been installed. You can now use it in a procedure or package.

Cause: Installation of the Open Tool has been completed.

Action: No action is required.
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: An unexpected error occurred while versioning an object.

Action: Review the error details for further information.
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 label {3}

Cause: Deletion of a version of an object referenced by a Solution was attempted.

Action: Delete the label 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 label {4}

Cause: An object version cannot be deleted because it is referenced.

Action: If an object version must be deleted, remove all references first.
Level: 32

Type: ERROR

Impact: Other

ODI-26082: ODI-26082: No difference found

Cause: No difference was found between two object versions.

Action: No action is required.
Level: 32

Type: ERROR

Impact: Other

ODI-26083: ODI-26083: No difference found.

Cause: No difference was found between object versions.

Action: No action is required.
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: Internal error.

Action: Review the error details for further information.
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: An unexpected error occurred while opening a window.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-26094: ODI-26094: Your license does not allow Changed Data Capture operations.

Cause: The current license does not include change data capture.

Action: Upgrade the license to include change data capture.
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: The current license does not include usage of the specified KM.

Action: Select another compatible KM or upgrade the license.
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: A query parameter is missing for retrieving a level.

Action: Supply the missing parameter.
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: An unexpected error occurred while searching for an icon.

Action: Review the error details for further information.
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: An unexpected error occurred during a save operation.

Action: Review the error details for further information. Ensure that the repository connection is open.
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: An unexpected error occurred while searching for an object.

Action: Review the error details for additional information.
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: An unexpected error occurred while comparing tables.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-26120: ODI-26120: Fields compared are not the same

Cause: An unexpected error occurred while comparing fields.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-26121: ODI-26121: Error while exploring version

Cause: An unexpected error occurred while checking the version.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-26122: ODI-26122: Exception when getting the children list

Cause: An unexpected error occurred while getting a list of child elements.

Action: Review the error details for further information.
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: An unexpected error occurred while opening an editor.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-26129: ODI-26129: Unable to open Editor: Technology could not be opened twice

Cause: Technology editor is already open.

Action: Close the other editor before opening a new technology editor.
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-26138: ODI-26138: Server initialization failed.

Cause: The attempt to initialize the server failed. This may be due to one or more of the following: invalid connection parameters specified, database problems, network problems.

Action: Ensure the server is available and acceccesible and the connection parameters are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26139: ODI-26139: Oozie Engine initialization failed.

Cause: The attempt to initialize the Oozie engine failed. This may be due to one or more of the following: invalid connection parameters specified, database problems, network problems.

Action: Ensure the Oozie engine is available and acceccesible and the connection parameters are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26140: ODI-26140: Oozie Engine test failed.

Cause: The attempt to initialize the Oozie engine failed. This may be due to one or more of the following: invalid connection parameters specified, database problems, network problems.

Action: Ensure the Oozie engine is available and acceccesible and the connection parameters are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26150: ODI-26150: Incorrect Context.

Cause: A valid Context was not specified.

Action: Select a Context from the list. If none are available then create one from the Topology Navigator.
Level: 32

Type: ERROR

Impact: Other

ODI-26153: ODI-26153: Connection failed; JDBC Error

Cause: An unexpected JDBC error was encountered during the connection process.

Action: Ensure the resource referenced is available and the connection information is correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26155: ODI-26155: No Master Repository on this connection

Cause: A connection to the Master Repository could not be established.

Action: Ensure the Master Repository is available and valid connection details are provided.
Level: 32

Type: ERROR

Impact: Other

ODI-26156: ODI-26156: Designer cannot connect to an Execution repository. The operation will be canceled.

Cause: Unable to establish a connection to the Execution repository.

Action: Ensure the Execution repository is available and the connection details are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26157: ODI-26157: Connection Error

Cause: A connection to the Master Repository could not be established.

Action: Ensure the Master Repository is available and valid connection details are provided.
Level: 32

Type: ERROR

Impact: Other

ODI-26158: ODI-26158: Work Repository Attachment Error

Cause: A connection to the Work Repository could not be established.

Action: Ensure the Work Repository is available and valid connection details are provided.
Level: 32

Type: ERROR

Impact: Other

ODI-26159: ODI-26159: Error while creating Work Repository

Cause: An unexpected error occurred while creating the Work Repository.

Action: Correct any issues described in the error details.
Level: 32

Type: ERROR

Impact: Other

ODI-26160: ODI-26160: URL not referenced in the list.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26161: ODI-26161: File Not Found

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26162: ODI-26162: Connection failure

Cause: A connection to the repository could not be established.

Action: Ensure the repository is available and valid connection details are provided.
Level: 32

Type: ERROR

Impact: Other

ODI-26163: ODI-26163: Access Denied

Cause: A connection to the repository could not be established because of insufficient user privilege.

Action: Ensure the ODI user has sufficient privilege to connect to the specified repository.
Level: 32

Type: ERROR

Impact: Other

ODI-26164: ODI-26164: The reverse cannot be executed. Your Model will be created.

Cause: The specified technology or driver did not support standard reverse-engineering.

Action: Ensure the technology or driver supports standard reverse-engineering. Otherwise choose Customized Reverse and select an appropriate RKM for the technology.
Level: 32

Type: ERROR

Impact: Other

ODI-26165: ODI-26165: This driver has no match in the URL list

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26166: ODI-26166: The template was not generated: {0}

Cause: The WLS Template could not be generated.

Action: Correct any errors identified in the error log and retry the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-26167: ODI-26167: File System Error: {0}

Cause: Creation of the Server Template file failed due to an error detected by the file system.

Action: Correct any errors identified in the error log. Ensure the file system location is accessible and retry the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-26168: ODI-26168: Client requires a repository with version {0} but the repository version found is {1}

Cause: Could not connect to the repository due to the old repository version.

Action: Update repository to the latest version.
Level: 32

Type: ERROR

Impact: Other

ODI-26169: ODI-26169: JDBC driver is mandatory.

Cause: JDBC driver was not entered.

Action: Provide JDBC driver for database connection.
Level: 32

Type: ERROR

Impact: Other

ODI-26170: ODI-26170: JDBC URL is mandatory.

Cause: JDBC URL was not entered.

Action: Provide JDBC URL for database connection.
Level: 32

Type: ERROR

Impact: Other

ODI-26171: ODI-26171: User is mandatory.

Cause: User was not entered.

Action: Provide user for database connection.
Level: 32

Type: ERROR

Impact: Other

ODI-26172: ODI-26172: Id is mandatory.

Cause: Id was not entered.

Action: Provide work repository ID.
Level: 32

Type: ERROR

Impact: Other

ODI-26173: ODI-26173: Name is mandatory.

Cause: Name was not entered.

Action: Provide work repository name.
Level: 32

Type: ERROR

Impact: Other

ODI-26174: ODI-26174: Database connection is not available.

Cause: Connection error occurred while connecting to the database.

Action: Verify that the Database Connection details are correct and the database is available.
Level: 32

Type: ERROR

Impact: Other

ODI-26175: ODI-26175: Import folder does not exist or not a valid folder.

Cause: Non-existing or invalid folder was specified.

Action: Ensure the specified folder path is correct and refers to an existing folder.
Level: 32

Type: ERROR

Impact: Other

ODI-26176: ODI-26176: Import file does not exist or not a valid file.

Cause: Non-existing or invalid file was specified.

Action: Ensure the specified file path is correct and refers to an existing file.
Level: 32

Type: ERROR

Impact: Other

ODI-26177: ODI-26177: Unable to connect to the DBA user.

Cause: Unable to connect to the DBA account.

Action: Check that the DBA username and password are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26178: ODI-26178: Unable to connect to the Repository user.

Cause: Unable to connect to the Repository account.

Action: Check that the Repository connection details are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26179: ODI-26179: Invalid Date Format

Cause: An Invalid Date format was entered in the date filter.

Action: Ensure the date entered is of the required format.
Level: 32

Type: ERROR

Impact: Other

ODI-26180: ODI-26180: Changing the name of a sequence only impacts the sequence itself; Users need to manually change object(s) which reference the old sequence name.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-26181: ODI-26181: Unable to add a Project knowledge module

Cause: An unsupported action was attempted.

Action: No action required as Project knowledge modules are not a valid selection to be added to a solution.
Level: 32

Type: ERROR

Impact: Other

ODI-26182: ODI-26182: Object was modified by another user and cannot be saved.

Cause: The object could not be saved. It's possible that the object was modified by another user.

Action: Try to save changed data, then refresh edited object and apply changed data again.
Level: 32

Type: ERROR

Impact: Other

ODI-26183: ODI-26183: The maximum password length is {0} characters.

Cause: The entered work repository password length is greater than allowed.

Action: Provide a shorter password.
Level: 32

Type: ERROR

Impact: Other

ODI-26184: ODI-26184: SQL error occurred. See error details for more information.

Cause: SQL error occurred while performing UI action.

Action: If this error is not expected, contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26185: ODI-26185: File does not exist or cannot be created. See error details for more information.

Cause: UI action tried to open a file which did not exist, or create a file which could not be created due to some reasons.

Action: Make sure the file path is typed correctly. Make sure application has enough file system permissions in order to create a file at the specified path.
Level: 32

Type: ERROR

Impact: Other

ODI-26186: ODI-26186: Character set is not supported. See error details for more information.

Cause: UI action tried to use character encoding which is not supported.

Action: Make sure character set is typed correctly.
Level: 32

Type: ERROR

Impact: Other

ODI-26187: ODI-26187: Unexpected I/O error occurred. See error details for more information.

Cause: UI action caused unexpected I/O error.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26188: ODI-26188: There is no enough memory to perform this UI action. Increase the maximum Java heap size value (-Xmx).

Cause: UI action requires more memory than available at the current moment.

Action: Increase the maximum Java heap size value by using the "-Xmx" JVM option.
Level: 32

Type: ERROR

Impact: Other

ODI-26189: ODI-26189: Unexpected report generation error occurred. See error details for more information.

Cause: UI action caused unexpected report generation error.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26190: ODI-26190: A user with same name {0} already exists in ODI. Note: LDAP user name is case insensitive. You have to first drop that user prior to registering or changing this one.

Cause: Due to LDAP user name is case insensitive so ODI will follow same rule in external authenticaiton mode.

Action: Please drop the existing user with same name(ingoring case) first prior to registering this one.
Level: 32

Type: ERROR

Impact: Other

ODI-26191: ODI-26191: You cannot move this object because it is locked by another user ({0}).

Cause: This object was locked by another user.

Action: Wait until object is unlocked.
Level: 32

Type: ERROR

Impact: Other

ODI-26192: ODI-26192: You cannot drag & drop this object because it is locked by another user ({0}).

Cause: This object was locked by another user.

Action: Wait until object is unlocked .
Level: 32

Type: ERROR

Impact: Other

ODI-26193: ODI-26193: You are not allowed to delete master repository.

Cause: User attempt to delete master repository.

Action: Cancel deleting master repository.
Level: 32

Type: ERROR

Impact: Other

ODI-26194: ODI-26194: Database Connection User is mandatory.

Cause: Database Connection User was not entered.

Action: Provide Database Connection User.
Level: 32

Type: ERROR

Impact: Other

ODI-26195: ODI-26195: Database Connection Password is mandatory.

Cause: Database Connection Password was not entered.

Action: Provide Database Connection Password.
Level: 32

Type: ERROR

Impact: Other

ODI-26196: ODI-26196: Failed to migrate login information to new format.

Cause: ODI was not able to migrate login information from old format into the new format.

Action: Make sure that directory %ODI_HOME%/oracledi has write permissions. Try manually copying %ODI_HOME%/oracledi/snps_login_work.xml into %ODI_HOME%/oracledi/snps_login_work_12.xml file.
Level: 32

Type: ERROR

Impact: Other

ODI-26197: ODI-26197: Failed to delete old login information.

Cause: ODI was not able to delete old login information after migration from old format into the new format.

Action: Make sure that directory %ODI_HOME%/oracledi and file %ODI_HOME%/oracledi/snps_login_work.xml have write permissions. Try manually removing %ODI_HOME%/oracledi/snps_login_work.xml file.
Level: 32

Type: ERROR

Impact: Other

ODI-26198: ODI-26198: Passwords do not match.

Cause: Password confirmation doesn't match the entered password.

Action: Make sure that password and password confirmation are the same.
Level: 32

Type: ERROR

Impact: Other

ODI-26199: ODI-26199: User {0} is not authorized to grant object {1}.

Cause: Current user is not authorized to grant generic object privileges

Action: Assign generic object privileges to user.
Level: 32

Type: ERROR

Impact: Security

ODI-26200: ODI-26200: User {0} is not authorized to grant method {1}.

Cause: Current user is not authorized to grant generic method privileges

Action: Assign generic method privileges to user.
Level: 32

Type: ERROR

Impact: Security

ODI-26201: ODI-26201: Invalid Export Key. Export Key must have a minimum length of eight characters and maximum length of 100 characters, contain at least one alphabetic (lower/upper case) character, at least one numeric-digit or a special characters (@ # $ % + / =).

Cause: Export Key must have a minimum length of eight characters and maximum length of 100 characters, contain at least one alphabetic (lower/upper case) character, at least one numeric-digit or a special characters (@ # $ % + / =).

Action: Provide a valid Export Key
Level: 32

Type: ERROR

Impact: Other

ODI-26202: ODI-26202: The Export Key and the confirmed Export Key are not the same.

Cause: Export Key confirmation doesn't match the entered Export Key.

Action: Make sure that the Export Key and confirmed Export Key are the same.
Level: 32

Type: ERROR

Impact: Other

ODI-26203: ODI-26203: The provided Export Key is not correct for the selected file.

Cause: The provided Export Key is not the same as the Export Key of this selected file.

Action: Provide a correct Export Key
Level: 32

Type: ERROR

Impact: Other

ODI-26204: ODI-26204: The incorrect Export Key is entered three times. The Export Key field will be disabled now. You can Import this file without an Export Key (the cipher data will not be imported) or Cancel import.

Cause: The incorrect Export Key entered 3 times.

Action: Continue import this file without importing cipher data or Cancel import.
Level: 32

Type: ERROR

Impact: Other

ODI-26205: ODI-26205: The incorrect Export Key is entered three times. The Export Key field will be disabled now. Please consider other options or Cancel import.

Cause: The incorrect Export Key entered 3 times.

Action: Continue import this file or all files without importing cipher data, or Skip the file, or Cancel import.
Level: 32

Type: ERROR

Impact: Other

ODI-26206: ODI-26206: Unable to connect Registry Database to the DBA user.

Cause: Unable to connect Registry Database by DBA Account.

Action: Check Registry Database and the DBA username and password are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26207: ODI-26207: An Option with the name {0} already exists. Please provide another name.

Cause: The name provided for the Option is not unique.

Action: Enter a unique name for the Option.
Level: 32

Type: ERROR

Impact: Other

ODI-26208: ODI-26208: Unable to perform move because {0} already exists in folder {1}.

Cause: A folder already consists a such type of object with the same name as a moving object.

Action: Rename an object, which you want to move, or rename, or delete an existing object from a folder.
Level: 32

Type: ERROR

Impact: Other

ODI-26209: ODI-26209: The repository contains map component definitions that are newer than the ones supported by the current client version. Certain operations involving mappings may not function correctly. It is recommended to update your client to a newer version. Do you want to continue?

Cause: A client of an older version is used to connect to a repository containing newer map component definitions.

Action: Update the current client by downloading and installing the latest patch. Insure other clients that connect to the same repository are also at the same patch version.
Level: 32

Type: WARNING

Impact: Other

ODI-26210: ODI-26210: The repository contains map component definitions that are older than the ones supported by the current client version. Clicking Yes will continue the login and the map component definitions will be updated. Clicking No will disconnect from the repository without updating. Do you want to continue?

Cause: The current client contains map component definitions that are newer than the ones recorded in the repository.

Action: Continuing the connection will update the repository with map component definitions at the same version as the client. Check and update other clients that connect to the same repository to the same patch version as the current client.
Level: 32

Type: WARNING

Impact: Other

ODI-26211: Mapping name is not unique.

Cause: Duplicate mapping name. Mapping with the same name already exists in this folder.

Action: Choose another mapping name.
Level: 32

Type: ERROR

Impact: Other

ODI-26212: Reusable mapping name is not unique.

Cause: Duplicate reusable mapping name. Reusable mapping with the same name already exists in this folder, or there is another global reusable mapping with the same name.

Action: Choose another reusable mapping name.
Level: 32

Type: ERROR

Impact: Other

ODI-26213: Cannot create connection from {0} to {1}. Connections can only be made within the same component owner.

Cause: Cannot make a connection between two components that are contained in different component owners, for example a connection from a component that is inside a dataset to another component outside the dataset.

Action: Connect to a component that is contained by the same component owner.
Level: 32

Type: ERROR

Impact: Other

ODI-26214: Cannot find appropriate Knowledge Module for node:{0}

Cause: Cannot find a KM to assign to this node.

Action: Set appropriate KM for physical nodes.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-26215: Error when attempting to set the Loading Knowledge Module to AP node:{0}

Cause: Cannot find a LKM to assign to this node.

Action: Set appropriate LKM for AP nodes.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-26216: Error when attempting to set the Extract Knowledge Module to physical node:{0}

Cause: Cannot find a XKM to assign to this node.

Action: Set appropriate XKM for physical nodes.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-26300: ODI-26300: Following Flexfields are found missing, which are required to persist this object properly: {0} You can use Security Navigator to define Flexfields for this object type.

Cause: There are some required flexfields missing in the editor opened. Without the mentioned flexfields the given object will not persist properly.

Action: User can use Security Navigator to define Flexfields for this object type.
Level: 32

Type: WARNING

Impact: Other

ODI-26301: ODI-26301: The incorrect Export Key is entered three times. The Export Key field will be disabled now. Please consider other options or cancel the Compare.

Cause: The incorrect Export Key entered 3 times.

Action: Continue comparing this file without cipher data or cancel the Compare.
Level: 32

Type: ERROR

Impact: Other

ODI-26310: ODI-26310: Could not delete the Open Tool {0}. It is used within steps in the following packages: {1}

Cause: The Open Tool is used within package steps and cannot be deleted.

Action: Delete the corresponding steps from the referencing package before deleting the Open Tool.
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}. Error details are [{1}].

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30039: Parameter -RESUME_KEY_VAR is mandatory when -RESUME_KEY_COL is used

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30040: The -TABLE_NAME parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30041: LSCHEMA parameter is mandatory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30042: SUBSCRIBER_NAME parameter is mandatory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30043: You cannot use the OPTIMIZED_WAIT option with the current journalizing method.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30044: Invalid parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30045: Impossible to find a valid name on this machine for the "{0}" file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30046: Session stopped

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30047: You cannot select more than one source.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30048: Unable to find the object with type {0} and identifier {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30049: Version is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30050: The same file cannot be used as the source and the target.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30051: File does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30052: No file found.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30053: File name is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30054: It is not possible to delete sessions in the queue.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30055: Context is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30056: Sequence name is mandatory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30057: The position is a mandatory parameter.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30058: -SCEN_NAME parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30059: The number of child sessions in error state is greater or equal to the MAX_CHILD_ERROR parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30060: The parent session "{0}" does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30061: "{0}" is not a correct value for -OBJECT_TYPE

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30062: There's no table matching the pattern in the database

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30063: -TABLE_NAME and -CDC_SET_NAME cannot be used simultaneously.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30064: You must specify -TABLE_NAME or -CDC_SET_NAME

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30065: Incorrect length at position :{0} for value : {1} expected max size of {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30066: All child sessions have failed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30067: -UNIT_ROW_COUNT and -CDC_SET_NAME cannot be used simultaneously.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30068: Unable to find the table(s): {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30069: You must specify a Project

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30070: You have not specified the export scenarios location.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30071: You have not specified the export location.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30072: Unable to delete a running session

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30073: Unable to delete a waiting session

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30074: {0}: Illegal value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30075: Cannot be specified at the same time: {0} and {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30076: Unable to save the line number sum

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30077: The variable in use is null.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30078: No message.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30079: Mandatory Parameter "{0}" is missing

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30080: Cannot copy a directory "{0}" to a regular file "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30081: The source directory file "{0}" does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30082: The source directory file "{0}" is not a directory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30083: Invalid value "{0}" passed for parameter "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30084: File "{0}" does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30085: Cannot copy file with a regular expression to a regular file "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30086: The FROMDATE {0} should be earlier than the TODATE {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30087: Import failed. No work repository name was defined and the import failed in the master repository.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30088: Timed out. No result.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30089: Source file "{0}" does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30090: Scenario name is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30091: Invalid internal object transition

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30092: Cannot create directory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30093: PORT and NAME parameters can''t be used together.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30094: Log files can only be imported in synonym mode INSERT.

Cause: The value of parameter -IMPORT_MODE is invalid for this type of object.

Action: Modify the value of parameter -IMPORT_MODE to SYNONYM_INSERT
Level: 32

Type: ERROR

Impact: Other

ODI-30095: PROMPT option can only be used when ReverseManageShortcut tool is run from ODI UI and on a Local Agent.

Cause: The value of parameter -SHORTCUT_HANDLING_MODE is invalid for this mode of execution.

Action: Modify the value of parameter -SHORTCUT_HANDLING_MODE to ALWAYS_MATERIALIZE or ALWAYS_SKIP
Level: 32

Type: ERROR

Impact: Other

ODI-30096: Invalid shortcut handling mode.

Cause: The value of parameter -SHORTCUT_HANDLING_MODE is invalid.

Action: Modify the value of parameter -SHORTCUT_HANDLING_MODE to ALWAYS_MATERIALIZE or ALWAYS_SKIP or PROMPT.
Level: 32

Type: ERROR

Impact: Other

ODI-30097: -LOCATION parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30098: -OBJECT_NAME parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30099: -OBJECT_TYPE parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30100: -WORKSPACE parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30101: Enterprise Data Quality project {0} not found.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30102: Enterprise Data Quality Job {0} not found in Enterprise Data Quality project {1}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30103: Enterprise Data Quality matching query returned with empty or ambiguous result for {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30104: Model Internal ID is not supported when Legacy ID Compatible Mode is switched off.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30105: Internal ID is not supported for "{0}" when Legacy ID Compatible Mode is switched off. Only Global ID is supported.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30106: JAX-WS Dispatch proxy object could not be created. Check ODI Agent log for error messages.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30107: Upgrade key is required for pre-12.x object import.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30108: Target directory "{0}" does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30109: Error while polling run status of load plan {0} (instance id {1}, run {2}) for execution completion. Last polled status value: {3}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30110: Execution of load plan {0} (instance id {1}, run {2}) ended in status "{3}" instead of "{4}". {5}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30111: Value for mandatory parameter {0} is missing.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30112: Invalid logical schema "{0}" selected for PROCESS_LSCHEMA parameter. Oracle Golden Gate process logical schema is expected.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30113: Values for mandatory parameters PROCESS_LSCHEMA and OPERATION are missing.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30114: Oracle GoldenGate process logical schema with the name {0} does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30115: All selected load plan runs ({0}) have completed, with {1} in Error status.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30116: The number of load plan runs in error status ({0} in error out of {1} completed runs), is at or above the MAX_LP_ERROR limit of {2}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30117: The parent session "{0}" does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30118: The value "{0}" specified for the -NB_PROCESS parameter is invalid. A valid value must be a positive integer.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30119: Error while splitting XML file. Target file {0} already exists.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30120: Authentication mechanisms (parameter: AUTHMECHANISMS) is required when Use Authentication (parameter: AUTH) is set to Yes.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30121: This operation {0} is not to be invoked

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30122: Error while writing output XML file - {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30124: Error while parsing input XML file - {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30125: Error while creating SystemID using the XML file input - {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30126: Error on parsing header.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30127: Error on parsing footer.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30128: Error while joining XML files.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30129: The user {0} does not have privileges to export Scenario {1} ({2})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30130: The user {0} does not have privileges to import a Scenario.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30131: The user {0} does not have privileges to generate a Scenario.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30132: The user {0} does not have privileges to export Scenarios.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30133: Specified folder with ID {0} does not exist in repository.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30134: Specified scenario {0} of version {1} does not exist in repository.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30135: Invalid arguments for OdiExportObject tool. EXPORT_DIR="{0}",FILE_NAME="{1}". When EXPORT_DIR value is not specified, FILE_NAME value must contain absolute path.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30136: Incorrect EDQ server domain name {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30137: Invalid arguments for OdiExportAllScen when connected to Runtime Repository. Design repository parameters cannot be used on runtime repository.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30138: Invalid Source type provided. Valid Source types for OdiCreateDeploymentArchive are ODI or VCS.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30139: Invalid Archive type provided. Valid Archive type for Source type ODI is INITIAL.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30140: VCS Label not provided for Source VCS.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30141: Invalid VCS type provided. Valid VCS type is SVN.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30142: Invalid VCS Authentication type provided. Valid values are SVNBASIC|BASIC|PROXY|SSH|SSL|FILE.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30143: VCS URL not provided.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30144: VCS User name is mandatory for authentication type {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30145: VCS Password is mandatory for authentication type {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30146: Proxy Host as well as Proxy port are mandatory for authentication type {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30147: Invalid Archive type provided. Valid Archive types for OdiApplyDeploymentArchive are INITIAL or PATCH.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30148: Invalid Archive type provided. Valid Archive type for OdiRollbackDeploymentArchive is ROLLBACK.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30149: The timeout was reached before all of the sessions could be retrieved.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30150: Current user is not VCS ADMIN to perform unlock operation

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30151: Error while setting parameters on tool: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30152: Archive Name needs to be provided.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30153: Export Key is required when Create without cipher data option is selected as No.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30154: Parameter {0} cannot be null, when -LSCHEMA is null. Either -LSCHEMA or (all of -HOST,-PORT,-USER,-PASSWORD,-DOMAIN) are mandatory and cannot be null.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30155: SSH Port is mandatory for authentication type {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30156: Neither VCS Password nor Private Key file details provided for SSH.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40001: Cannot join two journalized sets of data: {0} and {1}.

Cause: The generated query object has detected multiple journalized data sources, only one is allowed.

Action: Switch off journalizing for one of the sources, in the logical or physical graph.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-40100: Invalid JDBC URL {0} . No XSD or DTD was provided.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Configuration

ODI-40101: Not Supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40102: The parameter {0} has already been specified for {1}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40103: No value provided for JMS_DESTINATION

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40104: The URL {0} does not start with {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40105: Connecting to JMS using URL {0} failed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40106: JNDI protocol not specified after the JMS XML protocol prefix : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40107: Path separator ":" after JNDI protocol not found {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40108: "//" after colon not found : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40109: Need more information than JNDI hostname. eg: port, provider : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40110: Could not find JNDI host, port, provider info : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40200: Cannot create the initial JNDI context. Check that the JNDI server is running, and that the following URL is correct ({0}).

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40201: Cannot create the initial JNDI context

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40202: Cannot find the target in JNDI ({0})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40203: Cannot find the Connection Factory ({0}) in JNDI

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40204: The URL cannot be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Network

ODI-40205: No connection.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Network

ODI-40206: Problem with getInternalSession

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40207: You must specify the URL parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Configuration

ODI-40208: This function has no effect for this connection

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40209: Unable to create the table

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40210: Unable to drop the table

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40212: Missing file structure in the request

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40213: Error performing update

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40214: Error creating prepared statement

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40215: Error performing commit

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40216: Error performing update

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40217: Error closing resultset

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40218: Error getting next element in resultset

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40219: Error opening file for insert

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40220: Error creating prepared statement

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40221: Error writing

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40222: Error initializing

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40223: Error performing commit

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40224: Error obtaining connection

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40225: Error performing rollback

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40226: Error initializing

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40227: Error performing commit

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40228: Error obtaining connection

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40229: Error performing rollback

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40300: File is read-only.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40301: Invalid COL ALIAS "{0}" for column "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40302: Invalid format description

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40303: XML/LDAP driver encountered exception during decryption of password for DB connection

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40304: The URL can not be null.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40305: Invalid property "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40306: Property {0} has invalid value {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40307: Parameter "{0}" has been declared twice. Old value : "{1}" New value : "{2}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40400: Invalid format description

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40401: Mis-matched start/end delimiters

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40402: File metadata could not be obtained for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40403: Unable to obtain row structure for file {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40404: Array must not be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40405: End must be greater than begin: {0} > {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40406: Bytes are too big for array

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40407: Begin interval must be >= 0: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40408: End interval must not go beyond the size of the pointed array: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40409: Array must not be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40410: End must be greater than begin: {0} > {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40411: Begin interval must be >= 0: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40412: End interval must not go beyond the size of the pointed array: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40413: Bytes are too long for array

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40414: Reader has been closed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40415: File {0} already exists

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40416: Could not create file {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40417: An IOException was caught while creating the file saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40418: File not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40419: Could not delete file: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40420: Bad String size, hex Strings should have an even size

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40421: Cannot code String {0} into {1} bytes using the encoding {2}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40422: The array of bytes is not a valid number:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40423: A bad number was found in a COMP3 format: {0} at position {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40424: Cannot code value {0} on {1} bytes.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40425: Bad number in a ZONED format: {0} at position {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40426: URL must start with {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40427: Unknown property: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40428: Could not write header rows to file: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40429: An IOException occured while writing a row saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40430: Unknown property

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40431: Could not close output file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40432: File {0} is read-only

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40433: File {0} was not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40434: Could not clone a row of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40435: Could not transform data for column {0} value {1} because: {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40436: JVM 1.4 at least is required

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Compliance

ODI-40437: Number of bad rows actually detected: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40438: File not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40439: Could not read heading rows from file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40440: Could not close file: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40441: Error reading file: {0} said {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40442: Could not translate value for column {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40443: Could not convert value of type {0} to BigDecimal

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40444: Column not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40445: Column {0} > {1}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40446: Column {0} negative or zero.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40447: This type is not valid datatype

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40448: File is read-only.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40449: File not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40450: An IOException occured saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40451: Column Not Found:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40452: Missing file structure in the request

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40453: Missing JMS properties in the request

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40454: Missing host variable at index

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40455: Not a numeric value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40456: A Number datatype was expected instead of :

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40457: Parsing error

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40458: Unknown column datatype

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40459: An IOException occurred saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40460: Could not transform the data: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40461: A Date datatype was expected instead of :

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40462: File already exists

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40463: Invalid cursor state

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40464: Invalid descriptor index

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40465: Data array must not be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40466: String is too long: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40467: Too many columns on this row

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40468: Row rejected because column {0} contains a bad value.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40469: Value was incorrect for column {0}: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40470: EOF reached but not expected

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40471: Tried to retrieve an int with an {0} object.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40472: Tried to retrieve a short with an {0} object.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40473: This resultset accepts only FETCHFORWARD requests

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40474: This function is unsupported: the software you are using might not be compatible with this driver.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40475: Invalid column name

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40476: Expected a comma.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40477: Cannot have a parameter inside a bare statement: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40478: Could not transform data.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40479: Unrecognized command.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40480: Malformed INSERT statement.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40481: Invalid COL ALIAS "{0}" for column "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40482: Two selected columns have the same alias: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40483: Could not read value {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40484: Could not read null value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40485: Not a ?

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40486: Could not read value {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40487: Unknown file format

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40488: Invalid COL ALIAS "{0}" for column "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40489: Not Supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40490: Datatype {0} is not implemented for now

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40491: ResultSet already closed. Cannot call next() on it.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40492: Property "{0}" is having invalid value "{1}".

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40493: Parameter "{0}" has been declared twice. Old value : "{1}" New value : "{2}".

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40500: Unknown parameter : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40501: Syntax: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40502: Can''t begin loading while loading another context

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40503: Creating a new element {0} from the object {1} in DN {2} which contains attributes {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40504: Found the key {0} for the element {1} in DN {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40505: Entry {0} in {1} has a key {2} which is different from the original key found: {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40506: Adding new attribute {0} for object {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40507: Model Builder

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40508: Not finished loading!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40509: Can''t begin loading while loading another context

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40510: Not finished loading!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40511: Bad element {0} while in level

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40512: Because an element {0} is not supposed to appear here. Please check your data model.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40513: Entry {0} in {1} has a key {2} which is different from the original key found: {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40514: Not implemented

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40515: Not implemented

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40516: Could not add table {0} because the model told us it''s a duplicate. Please try changing the grouping factor.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40517: Could not add table {0} because the model told us it''s a duplicate. Please try changing the grouping factor.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40518: The table {0} already exists in the model and could not be added

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40519: The table {0} is a duplicate root

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40520: The table {0} doesn''t exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40521: A NamingException occurred saying {0} because of {1} with the remaining name {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40522: Exception {0} occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40523: Property {0} is invalid

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40524: Property {0} from the URL is invalid

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40525: Internal connection is null. This shouldn''t happen that way.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40526: A NamingException occured saying: {0} with this explanation: {1} and this remaining name: {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40527: Could not read alias bundle because an IOException occurred saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40528: A {0} occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40529: Could not write alias bundle because an IOException occurred saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40530: The schema is now in a read only mode because the technology is not HSQL

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40531: Exception {0} occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40532: Could not find the element for row of table {0}: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40533: Element {0} has no identifier so this row could not be updated.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40534: Exception getting original attributes of baseDN={0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40535: Key column {0} has a null value though it''s required

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40536: Deleting attribute {0} from Object {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40537: Deleting object {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40538: Creating attribute value {0} in attribute {1} from Object {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40539: Adding object {0} to the database from row {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40540: Modifying attribute value {0} to {1} in attribute {2} from Object {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40541: Adding attribute value {0} in attribute {1} from Object {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40542: This update is not permitted because it would move the element to another location in the hierarchy.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40543: This update is not permitted because it would move this attribute to another element.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40544: The attribute {0} cannot exist in an element of class {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40545: Modifying attribute value {0} to {1} in attribute {2} from Object {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40546: A user has not been provided

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40547: Not Supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40548: Parameter {0} has already been specified. Old value : {1} New value : {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40549: Invalid value specified for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40550: Unable to create IntialLdapContext for {0}. Pagination is not possible. Is LDAP server LDAPv3?

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40551: LdapContext needed for pagination. Found {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40552: Invalid page size : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40553: Unable to get cipher without instance

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40554: Unable to encrypt LDAP2 password

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40555: Unable to encrypt LDAP2 password

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40556: URL must start with {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40557: objectClass attribute not found for {0} from parent {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40558: objectClass attribute not found for element with attributes {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40559: LDAP server URL is mandatory.

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}" of XML file doesn''t match the DTD/XSD element with name "{1}" from namespace "{2}" set as root element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40800: No root found!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40801: Ambiguous name: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40802: Namespace not found for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40803: Malformed qualified name {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40804: Empty table for multiple links in attribute {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40805: Unknown link type: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40806: Multiple roots found: {0} and {1}. Use the parameter 'root_elt' in the URL to choose the root element.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40807: No root found in the DTD file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40808: Should not occur {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40809: Creating a RDB model from an XML model is currently not supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40810: Creating an XML model from a RDB model is currently not supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40811: No root on model

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40812: The table {0} which is linked to attribute {1} was not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40813: Unknown attribute: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40814: Unknown link type: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40815: Ambiguous name: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40816: Bad attribute: {0} in element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40817: Namespace not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40818: Internal error: expected to find PCData in element {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40819: Malformed QName: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40820: *** FATAL *** A duplicate root has been found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40821: *** FATAL *** The potential root is not in the model: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40822: Duplicate attribute: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40823: Type unsupported for PCDATA attribute of element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40824: Two namespaces are in conflict and we cannot build aliases: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40825: *** FATAL *** Could not create a table because it already exists in the model.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40826: A Qualified name cannot begin with a colon

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40827: A Qualified name cannot end with a colon

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40828: SnpsXmlNamespaceNotFoundException occured: Should not occur while setting prefixes

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40829: This is a fixed namespace and elements cannot be added to it

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40830: The request type is different

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40831: The request command is different

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40832: A parameter is missing

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40833: A parameter has a bad value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40834: This token was not expected anymore: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40835: Function not implemented yet: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40836: Cannot drop the default schema

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40837: An error occurred during the creation of the schema: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40838: An error occurred in the cleanup of the schema: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40839: InvalidTableException said: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40840: The table {0} already exists in the schema {1}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40841: Could not create schema with URL "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40842: As no XML and no DTD were provided, the XML schema cannot be created

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40843: No DTD found and no XML file provided: the XML schema cannot be created

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40844: Could not generate the DTD because the file could not be created. Verify that you have write permission in the directory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40845: While generating the DTD from the XML file, a "{0}" exception occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40846: Could not close the file because an IOException occurred saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40847: An UnupportedDatatypeException occurred saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40848: Could not find the file called {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40849: IOException reading file called {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40850: Unsupported DB property "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40851: Table {0} not found in schema {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40852: The default schema cannot be read/write

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40853: The schema {0} cannot be set read/write because it has no associated file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40854: No file provided for synchronization. Use CREATE FILE <file> FROM <schema> command

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40855: Table {0} already exists but it doesn''t have the correct number of columns

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40856: Column {0} doesn''t exist in table {1}, it is required for this DTD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40857: Expected one of auto, xml or xsd for parameter ns_prefix_generation

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40858: Found that the file references the DTD or XSD: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40859: Could not read the file to get its associated schema because an IOException occurred saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40860: Could not read the file to get its associated schema because a SAXException occurred saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40861: Could not read the file to get its associated schema because a ParserConfigurationException occurred saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40862: No DTD was provided and the property "generate_dtd" is set to no

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40863: The parameter generate_dtd has a bad value: {0} . One of 'AUTO', 'YES', 'NO' was expected

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40864: XSD {0} was found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40865: No DTD named {0} was found so the XML schema could not be created

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40866: This schema is in a {0} state and cannot be opened in another state.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40867: Could not connect on schema because it is {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40868: The path {0} doesn''t exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40869: The path {0} is not a directory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40870: You already have a schema opened on this file with another name: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40871: Duplicate attribute where no attribute should have been set yet.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40872: Unsupported exception saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40873: There are several root tables and the unload is not supported in this case

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40874: Expected to find attribute {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40875: Something unexpected occured. Expected to find datatype {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40876: Extension found in an object of type {0} is not permitted.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40877: Cannot merge types for element {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40878: Restriction violated : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40879: An IOException occured while including another schema saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40880: A ParserConfigurationException occured while including another schema saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40881: Unexpected element of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40882: Cannot add a restriction!: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40883: Cannot add a restriction on a non simple type or attribute

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40884: Extension found outside an element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40885: Type {0} was not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40886: Cannot merge types for element "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40887: Unexpected element of type {0} in hierarchy before simple type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40888: Unexpected element of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40889: Could not affect complex type to object of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40890: Unexpected element of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40891: An element has no name and doesn''t refer to another element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40892: Cannot add an element to an attributeGroup (wanting to add {0} to group {1} )

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40893: Cannot add an element to an object of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40894: Could not find namespace: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40895: Conflicting Namespace Error: Should not occur: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40896: Unknown prefix: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40897: Cannot handle type [{0}] as a simple type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40898: Element {0} referenced in group {1} was not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40899: Attributes' group {0} not found in the file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40900: Duplicate attribute: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40901: Unsupported exception: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40902: Element group {0} not found in the file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40903: Duplicate reference while adding an element of a group: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40904: Unsupported exception while adding an element of a group: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40905: Namespace {0} for element {1} referenced in group {2} was not found.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40906: Element {0} referenced in group {1} has an ambiguous name

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40907: An object of one of these types was expected in the hierarchy: element, type, attribute, attribute group

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40908: No more pending objects left in hierarchy

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40909: An object of one of these types was expected in the hierarchy: element, type, attribute, attribute group

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40910: Cannot add element {0} to type {1} because it doesn''t handle references.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40911: One pending element was not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40912: Simple type {0} has a restriction on a type {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40913: The object of type {0} is missing type {1} but don't know how to deal with it.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40914: Element {0} is missing but is referenced

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40915: Type {0} is missing but is needed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40916: Element {0} has no type.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40917: One pending element's namespace was not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40918: One pending element has an ambiguous name: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40919: Cannot add element {0} to type {1} because it doesn''t handle references.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40920: An attribute must have a simple type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40921: Could not find the root element that we've just set.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40922: This qualified name is malformed: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40923: Inner type of element {0} is not defined or is not a complex type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40924: Renamed column {0} to {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40925: Should not occur

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40926: Internal error

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40927: Not Supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40928: Not supported for XML driver commands

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40929: Property {0} has invalid value {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40930: Root element {0} specified by user not a global element in the NXSD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40931: Unrecognised request type for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40932: Unable to find root element in DTD.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40933: Unable to build XSD from DTD.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40934: The schema {0} is not created using the appropriate compatibility mode.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40935: The schema {0} was created with correct compatibility mode, but has incorrect XML model type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40936: Namespace URI for the prefix {0} was not found in the XSD/DTD or XML

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40937: Encountered one more close tag while no more open tags were found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40938: Error splitting prefixed string {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40939: The XML construct "{0}" in element "{1}" from type "{2}" is not supported by XML JDBC driver

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40940: No global elements were found in the XSD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40941: Requested root element {0} was not found in the XSD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40942: Ending on "{0}" but needed to find "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40945: XSD parser ecnountered error parsing XSD/DTD. Check validity.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40946: Error processing XSD/DTD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40947: Unable to write xpath mapping information

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40948: Could not find namespace URI {0} in XML model for {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40949: Old object type found for namespace {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40951: Unable to find namespace URI : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40952: Element {0} of type {1} at xpath {2} appears to be same as element {3} of type {4} at xpath {5}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40953: Prefix "{0}" is already mapped to "{1}" in current XML scope. New uri : "{2}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40956: Root element {0} is substitutionGroup head. This is not allowed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40957: Unable to resolve path of XSD "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40958: Illegal state. Currently coalescing for "{0}".

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40959: Illegal state. Not coalescing yet.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40960: Unknown object "{0}" found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40961: You cannot use v1 compatibility flag along with v3 mode

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40962: Error occurred checking if table "{0}" exists

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40963: XSD does not define "anyAttribute" for {0}, but found it in DB.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40964: Element "{0}" is defined in XSD to have "any" element child, but could not find it in model.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40965: Illegal metadata on element "{0}". Element results in column, but has table metadata.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40966: Column metadata set on element with xpath "{0}" while it has child : "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40967: Illegal metadata on attribute "{0}" with xpath "{1}". Attribute may only have column metadata.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40968: Property only supported for complex file driver when inxb/is_nxsd_based=true.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40969: Trying to use "{0}" data type with Statement not supported. {1} xPath "{2}". Either user has requested not to use PreparedStatement or your DB/driver does not support PreparedStatement

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40970: Trying to use table "{0}" used by "{1}" for "{2}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40971: When user specifies DB type, length and scale must also be specified. Not done for "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40972: More than one "any" associated with element "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40973: URL must start with {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40974: Element with xpath {0} already set with recursion head as {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40975: Element with xpath {0} already set with recursion on {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40976: xpath {0} already seen with {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40977: URL syntax error {0}. Consult driver documentation

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-41000: Groovy code in stage {0} could not be compiled

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-41001: Groovy code in stage {0} could not be converted to GroovySource

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-41002: GroovySource for stage {0} is null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-41003: Groovy code for stage {0} pointed by {1} could not be located as file or classpath resource

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-41004: Groovy script for stage {0} could not be read

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-41005: Groovy script for stage {0} could not be compiled

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-41006: Java class {0} for stage {1} could not be found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-41007: Stage definition {0} is invalid. Need at least one of "code", "groovyScript" or "javaClass"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-41008: Unable to find constructor with right signature for stage {0}. Expected constructor with params {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-41009: Error instantiating stage {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-41010: Stage {0} incorrectly attempts to create an InputDecorator. This class is not meant for instantiation.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-41011: Stage {0} incorrectly attempts to create an OutputDecorator. This class is not meant for instantiation.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-41012: LinkageError trying to instantiate Java class {0} for stage {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-41013: InitializationError trying to instantiate Java class {0} for stage {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-50000: Java exception thrown: {0}.

Cause: A java exception was thrown during processing.

Action: Internal Error: contact Oracle support.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-999999: Expression reference not found: {0}.

Cause: The expression being parsed has a column reference that cannot be found.

Action: Check the expression
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

31 ODL-52001 to ODL-52816

ODL-52001: deleting log file: {0}, size: {1} bytes

Cause: A log file was deleted because of the rules defined in the current configuration.

Action: This is an information message, no action is needed.
Level: 16

Type: NOTIFICATION

Impact: Logging

ODL-52002: invalid value for parameter {0}: {1}. Value must be greater than zero.

Cause: An invalid value was assigned to a numeric parameter that require a positive value.

Action: Use a value that is greater than zero value for the parameter.
Level: 1

Type: ERROR

Impact: Logging

ODL-52003: invalid value for parameter maxLogSize: {0}. Value must be greater than the value of maxFileSize ({1}).

Cause: The value used for the maxLogSize parameter is smaller than the value used for the maxFileSize parameter, which is not valid.

Action: Enter a value for the maxLogSize parameter that is greater than the value of the maxFileSize parameter.
Level: 1

Type: ERROR

Impact: Logging

ODL-52004: invalid encoding: {0}

Cause: The value used for encoding parameter is not valid.

Action: Enter a valid encoding value.
Level: 1

Type: ERROR

Impact: Logging

ODL-52005: invalid path: {0}. This path is already being used by another log writer instance of a different type.

Cause: There was an attempt to create a log using a path that is already being used by another log, but the two logs are of different types.

Action: Contact Oracle support services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52006: Path cannot be null.

Cause: A null value was used for the log file path.

Action: Enter a non-null value for the path.
Level: 1

Type: ERROR

Impact: Logging

ODL-52007: The log path is not a directory: {0}.

Cause: The value used for the log path is not a directory. Some log types require that the log path be a directory, not a file, because the log file name is fixed.

Action: Enter a directory path instead of a file path.
Level: 1

Type: ERROR

Impact: Logging

ODL-52008: unable to create log directory: {0}

Cause: One or more directories that were used in the log path could not be created.

Action: Make sure that the process has permission to create the directories, or enter a different path. It may also be possible to create the directories manually.
Level: 1

Type: ERROR

Impact: Logging

ODL-52009: The log directory is not writable: {0}.

Cause: The process could not write to the log directory.

Action: Make sure that the process has permission to write to the log directory, or enter a different path.
Level: 1

Type: ERROR

Impact: Logging

ODL-52010: no permission to access log directory: {0}

Cause: The process could not access the log directory.

Action: Make sure that the process has permission to access the log directory, or enter a different path.
Level: 1

Type: ERROR

Impact: Logging

ODL-52011: attempting to operate on a closed LogWriter

Cause: There was an attempt to perform an operation on a log writer that is already closed.

Action: This is possible a programming error. Contact Oracle Support Services. If the problem occurs during process shut down, it is possible that some component is attempting to log a message after the logging system has already shut down.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52012: attempting to write to a closed LogWriter

Cause: There was an attempt to writea a message to a log writer that is already closed.

Action: This is possible a programming error. Contact Oracle Support Services. If the problem occurs during process shut down, it is possible that some component is attempting to log a message after the logging system has already shut down.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52013: attempting to flush a closed LogWriter.

Cause: There was an attempt to flush a log writer that is already closed.

Action: This is possible a programming error. Contact Oracle Support Services. If the problem occurs during process shut down, it is possible that some component is attempting to log a message after the logging system has already shut down.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52014: Maximum log size is reached.

Cause: The maximum size for the log defined in the configuration was reached and the current configuration does not enable automated removal of older log messages.

Action: Review the logging configuration. It may be necessary to increase the maxLogSize parameter, or enable a policy for the automatic removal of older messages.
Level: 1

Type: ERROR

Impact: Logging

ODL-52015: unable to delete old archived file

Cause: There was an attempt to delete an old log file, but the file could not be deleted.

Action: Check that the process has permission to delete the log file.
Level: 1

Type: ERROR

Impact: Logging

ODL-52016: failure to rotate log file: {0}

Cause: There was an attempt to rename a log file, but the operation failed.

Action: Check that the process has permission to rename files.
Level: 1

Type: ERROR

Impact: Logging

ODL-52017: out of log file names

Cause: There was an attempt to rename a log file, but there are no more names that can be used.

Action: Remove some or all of the archived files.
Level: 1

Type: ERROR

Impact: Logging

ODL-52018: unable to write to log ''{0}'': {1}

Cause: There was an error when writing messages to a log file.

Action: See the error message for the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52019: unable to close log ''{0}'': {1}

Cause: There was an error when closing a log file.

Action: See the error message for the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52020: failed to get a lock on file ''{0}'' after {1} milliseconds

Cause: A log file lock could not be acquired within the specified time period, and the log write operation has time-out.

Action: Check that other processes are not holding a lock to the log file.
Level: 1

Type: ERROR

Impact: Logging

ODL-52021: thread interrupted while waiting to lock file ''{0}''

Cause: The thread was interrupted while waiting to acquire a lock on a lock file.

Action: Check that other processes are not holding a lock to the log file.
Level: 1

Type: ERROR

Impact: Logging

ODL-52029: recursive logging detected that exceeds the recursion depth limit of {0}. The handler will not log the message.

Cause: The handler detect recursive logging calls that exceed that maximum configured recursion depth limit.

Action: Review the source code to eliminate logging calls within code that may be called while formatting a log message.
Level: 1

Type: ERROR

Impact: Logging

ODL-52030: invalid property name: {0}

Cause: An invalid property name was used in the logging configuration.

Action: Review the configuration and enter a valid property name.
Level: 1

Type: ERROR

Impact: Logging

ODL-52031: required property ''{0}'' is not found

Cause: A required property was not present in the configuration of a log handler.

Action: Review the configuration and add the required property.
Level: 1

Type: ERROR

Impact: Logging

ODL-52032: invalid format: {0}. Valid formats are: {1}.

Cause: An invalid value for the 'format' property was used in the configuration of an ODLHandler.

Action: Review the configuration and add a valid value for the format property.
Level: 1

Type: ERROR

Impact: Logging

ODL-52033: invalid value for property {0}: {1}.

Cause: An invalid value for used for an ODLHandler property.

Action: Review the configuration and add a valid value for the property.
Level: 1

Type: ERROR

Impact: Logging

ODL-52034: Configuration is invalid: {0} cannot be less than {1}.

Cause: An invalid value for used for a size property in an ODLHandler configuration.

Action: Review the configuration and make sure that the value of the 'maxFileSize' property is not greater than the value of the 'maxLogSize' property.
Level: 1

Type: ERROR

Impact: Logging

ODL-52035: failure to create ODLHandler: {0}

Cause: An ODLHandler instance could not be created.

Action: Check the error message for the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52036: invalid level: {0}. Check spelling and verify that the value is a valid ODL or Java level.

Cause: An invalid level was used in the configuration of a logger or handler.

Action: Review the configuration and enter a valid level.
Level: 1

Type: ERROR

Impact: Logging

ODL-52040: failure to initialize class {0}: property {1} must be defined.

Cause: A required system property was not defined.

Action: Review the process configuration and make sure that the required system property is defined.
Level: 1

Type: ERROR

Impact: Logging

ODL-52041: Use of {0} in logging configuration is deprecated; replacing it with {1}. (File: {2}).

Cause: A deprecated property was used in the logging configuration.

Action: Review the logging configuration and consider replacing the deprecated property. While the configuration may be valid, use of deprecated properties should be avoided.
Level: 1

Type: WARNING

Impact: Logging

ODL-52042: undefined property: {0}.

Cause: An undefined property was used in the logging configuration.

Action: Review the logging and process configuration and either replace the invalid property in the logging configuration, or define a value for the property.
Level: 1

Type: ERROR

Impact: Logging

ODL-52043: expecting one element of type ''{0}''

Cause: The logging configuration contained more than one XML element of a given type, when only one was expected.

Action: Review the logging configuration and remove the extra XML elements.
Level: 1

Type: ERROR

Impact: Logging

ODL-52044: cannot find handler: {0}

Cause: The logging configuration assigned a handler to one or more loggers, but the handler was not defined.

Action: Review the logging configuration and either add the missing handler, or remove any references to the handler.
Level: 1

Type: ERROR

Impact: Logging

ODL-52045: invalid class: {0}

Cause: The logging configuration defined an invalid class for a handler.

Action: Review the logging configuration and make sure that the handler class is valid. The handler class must be either a subclass of java.util.logging.Handler, or implement the oracle.core.ojdl.logging.HandlerFactory interface.
Level: 1

Type: ERROR

Impact: Logging

ODL-52046: cannot find class: {0}

Cause: The logging configuration defined a handler, filter, or error manager class, but that class could not be found.

Action: Review the logging and process configuration and make sure that the class is available in the system classpath, or that the class is visible to the classloader that loads the ODL configuration classes.
Level: 1

Type: ERROR

Impact: Logging

ODL-52047: cannot load or link class ''{0}'': {1}

Cause: The logging configuration defined a handler, filter, or error manager class, but that class could not be loaded due to a linkage error.

Action: Review the logging and process configuration and make sure that the class is available in the system classpath, or that the class is visible to the classloader that loads the ODL configuration classes, or that the correct version of the class is being used..
Level: 1

Type: ERROR

Impact: Logging

ODL-52048: Class ''{0}'' is not of expected type ''{1}''.

Cause: The logging configuration defined a handler, filter, or error manager class, but that class is not a handler, filter or error manager instance.

Action: Review the logging and process configuration and make sure that the class is of the correct type.
Level: 1

Type: ERROR

Impact: Logging

ODL-52049: cannot create instance of class ''{0}'': {1}

Cause: The logging configuration defined a handler, filter, or error manager class, but an instance of that class could not be created.

Action: Review the error message for the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52050: unable to process file ''{0}'', XML parse exception (line: {1}, column: {2}): {3}

Cause: The logging configuration could not be processed due to an XML error in the configuration file.

Action: Review the error message for a description of the XML error, and correct the problem in the configuration file.
Level: 1

Type: ERROR

Impact: Logging

ODL-52051: unable to process file ''{0}''; exception: {1}

Cause: The logging configuration could not be processed due to a unexpected XML parser error.

Action: Review the error message for a description of the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52052: unable to find resource: {0}

Cause: The logging configuration could not be processed due to a missing XML schema or DTD.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52053: unable to create handler instance using class ''{0}''; exception: {1}

Cause: The creation of a handler instance failed because the handler factory threw an exception.

Action: Review the error message for the root cause.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52054: The logger ''{0}'' is already defined.

Cause: There was an attempt to add a new logger to the configuration file, but the logger is already defined.

Action: Verify that the logger name is correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52055: The handler ''{0}'' is already defined.

Cause: There was an attempt to add a new handler to the configuration file, but a handler is already defined.

Action: Verify that the handler name is correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52056: The logger ''{0}'' is not defined.

Cause: There was an attempt to access a logger in the logging configuration but the logger is not defined.

Action: Verify if the logger name is correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52057: The handler ''{0}'' is not defined.

Cause: There was an attempt to access a handler in the logging configuration but the handler is not defined.

Action: Verify if the handler name is correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52058: The handler ''{0}'' cannot be removed because it is being used by logger ''{1}''.

Cause: There was an attempt to remove a handler from the logging configuration, but the handler could not be removed because it is being used by a logger.

Action: Verify that the handler name is correct, or remove the handler from all the loggers first before attempting to remove the handler.
Level: 1

Type: ERROR

Impact: Logging

ODL-52059: The logger ''{0}'' already has handler ''{1}''.

Cause: There was an attempt to add a handler to a logger but the logger already has the given handler.

Action: Verify if the logger and handler names are correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52060: The logger ''{0}'' does not have handler ''{1}''.

Cause: There was an attempt to remove a handler from a logger, but the logger does not contain the given handler.

Action: Verify if the logger and handler names are correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52061: The handler ''{0}'' does not have property ''{1}''.

Cause: There was an attempt to remove a property from a handler, but the handler does not have a property with the given name.

Action: Verify if the handler and property are correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52062: Illegal value for ''{0}'': {1}

Cause: There was an attempt to set a property for a handler or logger, but the value of the property is not valid.

Action: Verify if the handler or loggers properties are valid.
Level: 1

Type: ERROR

Impact: Logging

ODL-52063: Unable to load logging configuration from ''{0}''; exception: {1}

Cause: There was an error while loading the logging configuration file.

Action: Review the error message for the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52064: The handler ''{0}'' is already defined in the target logging configuration document.

Cause: There was an attempt to add a handler to a logging configuration file, but a handler with the given name already exists in the target file.

Action: Review the definition of the new handler.
Level: 1

Type: ERROR

Impact: Logging

ODL-52065: The logger ''{0}'' or a descendant is already defined in the target logging configuration document.

Cause: There was an attempt to add a logger to a logging configuration file, but the logger or one of its descendants is already defined in target logging configuration.

Action: Review the definition of the new logger.
Level: 1

Type: ERROR

Impact: Logging

ODL-52080: Reading logging configuration from ''{0}''.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

ODL-52081: unable to read logging configuration from file ''{0}''; exception: {1}

Cause: There was an error reading the logging configuration from the given file.

Action: Review the error message for the root cause.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52082: unable to register logging runtime MBean; exception: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Logging

ODL-52083: unable to register log dump; exception: {0}

Cause: There was an error registering the log dump with the FMW Diagnostics Framework.

Action: Review the error message for the root cause. The system may still work, but the log dump will not be available.
Level: 1

Type: WARNING

Impact: Logging

ODL-52084: unable to initialize ODL; exception: {0}

Cause: There was an error initializing Oracle Diagnostic Logging (ODL).

Action: Review the error message for the root cause. Oracle Diagnostic Logging is not properly configured in this system.
Level: 1

Type: ERROR

Impact: Logging

ODL-52085: Reloading logging configuration from ''{0}''.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

ODL-52086: unable to reload logging configuration from file ''{0}''; exception: {1}

Cause: There was an error reloading the logging configuration from the given file.

Action: Review the error message for the root cause.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52087: suspicious logging configuration reload. The original configuration was read from file ''{0}'', but the new configuration is being read from ''{1}''.

Cause: The logging configuration is being reloaded, but the configuration file is different from the configuration file used for the initial configuration.

Action: This is probably an error, there should only be one configuration file.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52088: The java.util.logging configuration was reloaded.

Cause: The java.util.logging configuration was reloaded, probably via the invocation of LogManager.readConfiguration.

Action: The java.util.logging configuration should not be reloaded programmatically, as this can override the ODL configuration.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52501: Unable to get OPMN connection for instance ''{0}''; check that the instance name is valid and that OPMN is running.

Cause: There was an attempt to invoke an operation on a OPMN managed target, but a connection to that target could not be created.

Action: Check the target argument and make sure that the instance and component names are valid, and that OPMN is running.
Level: 1

Type: ERROR

Impact: Logging

ODL-52502: Invalid target. The server name ''{0}'' is not a valid server name, the server is not running, or JRF is not enabled on the server.

Cause: There was an attempt to invoke an operation on a Java EE server target, but the target does not exist or is not valid for the operation.

Action: Check the target argument and make sure that the server name is correct, the server is running, and that JRF is enabled on the server.
Level: 1

Type: ERROR

Impact: Logging

ODL-52801: There is already an active trace with ID ''{0}''. Use a different trace ID or stop the active trace first before starting a new trace with the same ID.

Cause: There was an attempt to start a trace using an ID value that is already being used by another active trace.

Action: Use a different trace ID or disable the existing active trace first before starting a new one with the same ID.
Level: 1

Type: ERROR

Impact: Logging

ODL-52802: There is already an active trace for attribute ''{0}'' with value ''{1}''. The existing active trace must be disabled first before a new one can be started for the same attribute value.

Cause: There was an attempt to start a trace using an attribute value that is already used by an active trace.

Action: Use a different attribute value or disable the existing active trace first before starting a new one with the same attribute value.
Level: 1

Type: ERROR

Impact: Logging

ODL-52803: Unable to complete the start tracing operation. The operation failed on target ''{0}''; cause: {1}

Cause: The start tracing operation cannot be completed because one or more servres are unable to complete the operation.

Action: See the error message for more information on the cause of the server failure.
Level: 1

Type: ERROR

Impact: Logging

ODL-52804: The start tracing operation failed for provider ''{0}''; cause: {1}

Cause: The start tracing operation cannot be completed because a trace provider is unable to complete the operation. See the error message for more information on the cause for the provider failure.

Action: See the error message for more information on the cause of the provider failure. You may try to disable the failing provider to obtain trace data from the other trace providers.
Level: 1

Type: ERROR

Impact: Logging

ODL-52805: Unable to complete the start tracing operation. The operation failed for one or more providers and could not be rolled back. The tracing configuration may be in an inconsistent state. Disable all active traces or restart the servers to reset the selective tracing configuration.

Cause: The start tracing operation failed for one or more providers or servers but could not be rolled back on all servers or providers.

Action: The tracing system may be on an inconsistent state. Disable all active traces or restart the servers to reset the selective tracing configuration.
Level: 1

Type: ERROR

Impact: Logging

ODL-52806: The stop tracing operation failed for provider ''{0}''; cause: {1}

Cause: The stop tracing operation cannot be completed because a trace provider is unable to complete the operation. See the error message for more information on the reason for the provider failure.

Action: See the error message for more information on the cause of the provider failure.
Level: 1

Type: ERROR

Impact: Logging

ODL-52807: Unable to create incident for trace with ID ''{0}''; cause: {1}

Cause: A trace was stopped but an incident could not be created for the trace data.

Action: See the error message for more information on the root causeof the incident creation failure.
Level: 1

Type: ERROR

Impact: Logging

ODL-52808: Invalid expression: {0}

Cause: An invalid expression was passed as a parameter to the startTracing operation.

Action: Review the list of active traces and disable some of the duplicate traces.
Level: 1

Type: ERROR

Impact: Logging

ODL-52809: Multiple active traces match the current request. The request is already being traced with ID ''{0}'' and it will not be traced with ID ''{1}''.

Cause: There are multiple active traces that can be started for the current request, but the request can only be associated with one trace. One or more traces will not be started.

Action: Review the expression and check for incorrect spelling or syntax. See the documentation for details on the expression syntax.
Level: 1

Type: WARNING

Impact: Logging

ODL-52810: A new trace cannot be started because there are too many traces currently active in the system.

Cause: A new trace cannot be started because there are too many traces currently active in the system.There are multiple active traces that can be started for the current request.

Action: Wait until some of the other traces are stopped before trying to start a new one. Contact your system administrator for more information.
Level: 1

Type: ERROR

Impact: Logging

ODL-52811: A new trace cannot be started or stopped for the current HTTP session because there is no current HTTP session.

Cause: A request to start or stop tracing the current HTTP session cannot be executed because there is no HTTP session associated with the current request.

Action: The HTTP session must be already active before tracing operations can be executed for the session.
Level: 1

Type: ERROR

Impact: Logging

ODL-52812: A new trace cannot be started for the current HTTP session because the session is already being traced.

Cause: A request to start tracing the current HTTP session cannot be executed because the session is already being traced.

Action: Stop the active trace before starting a new trace for the same session.
Level: 1

Type: ERROR

Impact: Logging

ODL-52813: A request to stop tracing an HTTP request cannot be executed because the request is not being traced.

Cause: A request to stop tracing an HTTP request cannot be executed because the request is not being traced.

Action: Check if the HTTP request is being traced before trying to stop tracing.
Level: 1

Type: ERROR

Impact: Logging

ODL-52814: Unable to send notification for start tracing event. Tracing will continue on the local server, but may not be enabled on other servers. Cause: {0}

Cause: A JMX notification for a start tracing event could not be sent due to an unexpected exception.

Action: See the error message for more information on the root cause.
Level: 1

Type: WARNING

Impact: Logging

ODL-52815: Unable to send notification for stop tracing event. Tracing is stopped on the local server, but may not be stopped on other servers. Cause: {0}

Cause: A JMX notification for a stop tracing event could not be sent due to an unexpected exception.

Action: See the error message for more information on the root cause.
Level: 1

Type: WARNING

Impact: Logging

ODL-52816: Unable to propagate a {0} event; cause: {0}

Cause: A selective tracing event originating from one server could not be propagated to other servers.

Action: See the error message for more information on the root cause.
Level: 1

Type: WARNING

Impact: Logging

32 OTD-68176 to OTD-68408

OTD-68176: Failover cannot be started until the instance ''{0}'' has been started.

Cause: While starting failover will make the VIP accessible, the requests to the instance will fail if it is not running.

Action: Start failover only after starting the corresponding instance.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-63113: Error copying the configuration ''{0}''. For details, see the administration server log.

Cause: The admin server process may not have write permissions for <domain name>/config/fmwconfig/components/OTD or the disk may be full.

Action: Fix any permission or disk space related issues. Look at otd_admin.log for more details.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-63114: Could not create a new configuration directory: {0}

Cause: The admin server process may not have write permissions for <domain name>/config/fmwconfig/components/OTD or the disk may be full.

Action: Fix any permission or disk space related issues. Look at otd_admin.log for more details.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68213: Could not create the configuration directories.

Cause: The admin server process may not have write permissions for <domain name>/config/fmwconfig/components/OTD or the disk may be full.

Action: Fix any permission or disk space related issues. Look at otd_admin.log for more details.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68666: Cannot delete certificate because it is being referred by OTD configuration ''{0}''.

Cause: There is likely to be a listener, virtual server or an origin server pool that has been configured to use this certificate for SSL communication.

Action: Ensure that no entity is using this certificate before attempting to delete it. You can either delete the reference or change it to use some other certificate.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68153: The virtual IP ''{0}'' either has an invalid format or is an unknown hostname.

Cause: This could either be due to an invalid format for the IP address or the domain name resolution failed for the specified hostname. Failover will not work if the specified VIP cannot be resolved to a valid IP address.

Action: Specify a valid IP address or ensure that the hostname can be resolved to a valid IP address.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-63147: An error occurred while reading configuration file ''{0}''. For details, see the administration server log.

Cause: The file may not exist or the admin server process may not have permissions to read the file.

Action: Look at otd_admin.log for more details.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-67762: Cannot stop instance ''{0}'' as failover is still running. Stop failover by running the WLST command 'otd_stopFailover' as a privileged user before stopping the instance.

Cause: If the instance is stopped while failover is still running, the VIP will not failover to the backup and any subsequent requests to the instance will fail.

Action: Stop failover before stopping the instance.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-63145: Configuration file ''{0}'' could not be saved. For details, see the administration server log.

Cause: The admin server process may not have write permissions for the file or the disk may be full.

Action: Fix any permission or disk space related issues. Look at otd_admin.log for more details.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68411: Cannot delete the origin-server pool since it is being used by the TCP proxies: {0}

Cause: The origin server pool cannot be deleted as long as there are TCP proxies that are referring to it.

Action: Before deleting the origin server pool, either modify the referring TCP proxies to use a different origin server pool or delete them.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68154: The router ID is already in use for the failover group with virtual IP ''{0}'' in the configuration ''{1}''

Cause: The specified router ID is already in use. Router ID must be unique across all the failover groups.

Action: Choose a different router ID (should be between 1 and 255).
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68663: The certificate alias ''{0}'' either does not exist or is not of type ''Certificate''.

Cause: The certificate identified by the specified alias must be present in the keystore and should not be of type 'TrustedCertificate'.

Action: If the alias does exist in the keystore, it is likely that the entire certificate chain has not been added correctly into the keystore. This can be verified by checking if the specified alias is listed to be of type 'Certificate'.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68301: HTTP listener ''{0}'' is being referred by virtual server(s): {1}

Cause: The HTTP listener cannot be deleted as long as there are virtual servers that are referring to it.

Action: Before deleting the HTTP listener, either modify the referring virtual server(s) to use a different HTTP listener or delete them. To force delete the HTTP listener, execute the WLST command 'otd_deleteHttpListener' with 'force' option.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-67753: An error occurred while restarting the instance. For details, see the server log.

Cause: Common causes are errors in server configuration and bind errors (Address already in use) on listener ports.

Action: Check if any other process is listening on any of the listener ports. Look at the instance's server log for more details.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-63030: Cannot create instance of configuration ''{0}'' as an instance ''{1}'' of the same configuration already exists on host ''{2}''.

Cause: Multiple instances of a configuration are not supported on the same host.

Action: Create instance of the configuration on a different host after creating the OTD managed domain on the same.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-67751: An error occurred while starting the instance. For details, see the server log.

Cause: Common causes are errors in server configuration and bind errors (Address already in use) on listener ports.

Action: Check if any other process is listening on any of the listener ports. Look at the instance's server log for more details.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68108: Failover is not supported on the system due to missing prerequisites: ''{0}''

Cause: The failover feature depends on keepalived on Linux and vrrpd on Solaris.

Action: Install keepalived RPM on Linux or vrrp package on Solaris.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-63026: Cannot delete the configuration ''{0}''. It has been deployed to ''{1}'' node(s).

Cause: Cannot delete a configuration which has instances.

Action: Delete all the instances of the configuration before deleting the configuration.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68881: CRL management is not supported since crl-path ''{0}'' is external to the configuration.

Cause: CRL management is not supported since the configured crl-path is external to the configuration.

Action: To enable CRL management, reset crl-path to the default path or to any directory within the configuration.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

OTD-68408: Cannot delete the origin-server pool. It is referred by virtual server(s): {0}

Cause: The origin server pool cannot be deleted as long as there are routes that are referring to it.

Action: Before deleting the origin server pool, either modify the referring routes to use a different origin server pool or delete them.
Level: 1

Type: NOTIFICATION

Impact: ADMIN

33 OGGV-00001 to OGGV-600013

OGGV-00001: Compare Pair Mappings are valid

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00002: Compare Pair Key Mapping are invalid

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00003: Compare Pair Comparison Column Mappings are invalid

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00004: Compare Pair Mappings are invalid

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00005: Compare Pair Mappings are no longer valid (possible changes in the datasources)

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00006: The operation was completed successfully.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00007: The operation failed due to validation error(s).

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00008: This job is already added.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00009: A Favorite Job/Shortcut with this name already exists. Please choose another name.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00010: Application Error

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00011: An unexpected error occurred. Please contact the system administrator. Original error message was: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00012: An error occurred when trying to update the connection. The operation was not completed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00013: The operation was not completed. Please select a connection to proceed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00014: An error occurred when trying to update the group. The operation was not completed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00015: The operation was not completed. Please select a group to proceed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00016: The operation was not completed. Please select a profile to proceed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00017: The operation was not completed. Please select a shortcut to proceed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00018: Please specify or verify the datasource type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00019: Please enter a valid host name.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00020: White spaces are not allowed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00021: Invalid character found: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00022: White spaces are not allowed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00023: Invalid character found: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00024: Value is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00025: Conversion error

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00026: Specified attribute is not between the expected values of {0} and {1}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00027: Maximum length is {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00028: Specified value is not a valid number.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00029: Specified value is not a valid number.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00030: Type specified does not match correct type. Correct type is {1}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00031: The connection {0} could not be found. Please verify that the name is correct.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00032: A job named {0} already exists. Job name is case insensitive and must be unique.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00033: The profile {0} could not be found. Please verify that the name is correct.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00034: The group {0} could not be found. Please verify that the name is correct.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00035: An error occurred when trying to load metadata information (Indexes) for [{0}]. Connection used was [{1}].

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00036: An error occurred when trying to load metadata information (Columns) for [{0}]. Connection used was [{1}].

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00037: A connection named {0} already exists. Connection name is case insensitive and must be unique.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00038: A group named {0} already exists. Group name is case insensitive and must be unique.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00039: Finished details will only be available when the entire job finishes.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00040: This compare pair did not complete successfully, therefore the charts will only display the results obtained before the failure.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00041: You need to select a Connection to continue.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00042: You need to select a Group to continue.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00043: You need to select a Job to continue.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00044: You need to select a Profile to continue.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00045: The job {0} could not be found. Please verify that the name is correct.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00046: You cannot change the DBMS type of the manager.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00047: The Compare Pair referenced no longer exists.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00048: You cannot set Compare Pairs status filter to ''{0}'' when run options is ''Review Previous Out-Of-Sync Results''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00049: General datasource error: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00050: The requested object was not found in the database.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00051: It was not possible to delete the object: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00052: Could not find the password file: [{0}]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00053: Could not read the password from file: [{0}]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00054: Unable to locate the server.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00055: There was a communication issue with Veridata Server.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00056: GoldenGate Veridata Server could not be reached. Please verify if it is currently running and that your configuration is correct.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00057: Your session is invalid. Please log on again.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00058: Connection to Veridata Server timed out. Please try again.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00059: Could not load comparison report {0}: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00060: Command file name was not provided

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00061: Path to chunks was not provided

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00062: Cannot parse control file: [{0}]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00063: Cannot create metadata

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00064: Cannot create operation summary

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00065: Cannot create differences by column

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00066: Cannot get chunks info

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00067: Cannot get operation details because: [{0}]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00068: Cannot initialize Velocity Engine: [{0}]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00069: Cannot apply Velocity Template: [{0}]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00070: The Source Schema is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00071: The Target Schema is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00072: The Source Schema is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00073: The Target Schema is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00074: The Source Schema is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00075: The Target Schema is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00076: The Source Schema is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00077: The Target Schema is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00078: The Source Schema is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00079: The Target Schema is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00080: The Source Schema is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00081: The Target Schema is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00082: The Source Catalog is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00083: The Target Catalog is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00084: The Source File Pattern is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00085: The Target File Pattern is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00086: The Source Table is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00087: The Target Table is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00088: The Source Table is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00089: The Target Table is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00090: The Source Table is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00091: The Target Table is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00092: The Source File/Table is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00093: The Target File/Table is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00094: Connection ''{0}'' still referenced, you cannot delete it.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00095: Connection ''{0}'' does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00096: Connection ''{0}'' already exists

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00097: {0} handle is not valid.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00100: Bad password

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00102: Bad authorization handle

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00103: Cannot connect to ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00104: Cannot start meta lookup

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00105: Group must be created empty

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00106: Compare pair id must be 0 to create

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00107: Element <{0}> cannot be Null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00108: Cannot start RHS agent, mgr={0}, port={1}, error={2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00109: Catalog lookup failed, mgr={0}, port={1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00110: Schema lookup failed, mgr={0}, port={1}, catalog={2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00111: Tables lookup failed, mgr={0}, port={1}, catalog={2}, schema={3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00112: Column lookup failed, mgr={0}, port={1}, catalog={2}, schema={3}, table={4}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00113: Index lookup failed, mgr={0}, port={1}, catalog={2}, schema={3}, table={4}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00114: Communication error ({0}, {1})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00118: Agent message ({0}): {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00119: Agent remote message ({0}): {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00120: Could not log into database, check username and password

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00121: Test fault with parameters. int64: 0x{0}, uint64: {1}, int32: {2}, uint32: {3}, int16: {4}, uint16: {5}, int8 {6}, uint8 {7}, char * {8}, char * {9}, char * {10}, char * {11}, char * {12}, void * 0x{13}, double {14}, long double {15}, ptrdiff_t {16}, size_t {17}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00123: Internal error.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00124: {0} ''{1}'' has changed since it was selected, please try again.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00126: Bad meta-session handle

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00127: Column validation failed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00128: Index validation failed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00129: {0} index ''{1}'' does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00130: {0} table schema has changed. Please check that the table still exists and column positions and datatypes have not changed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00131: Column mapping is invalid, please check the datatypes and comparison formats.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00132: Client error. (''{0}'').

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00133: RunId ({0}, {1}, {2}) does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00134: Job ''{0}'' is already running as ({1}, {2}, {3}).

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00135: Job ''{0}'' is still running, cannot delete a running job.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00136: Job cannot be run. Check server config parameters server.max_concurrent_jobs and server.max_concurrent_comparision_threads.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00137: {0} ''{1}'' contains invalid character(s).

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00138: Could not create report file ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00139: Field ''{0}'' cannot be more than {1} characters ''{2}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00140: ''{0}'' reading the file ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00142: Out of Sync details were not saved for this comparison run

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00143: Job cannot be run because it contains no compare pairs.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00144: Source column ''{0}'' not found in source table ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00145: Source column ''{0}'' has datatype ''{1}'', the datatype does not match the source table datatype of ''{2}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00146: Target column ''{0}'' not found in target table ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00147: Target column ''{0}'' has datatype ''{1}'', the datatype does not match the target table datatype of ''{2}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00148: The number of source columns doesn''t match the number of target columns

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00149: The datatype of source column ''{0}'' ({1}) does not match the datatype of target column ''{2}'' ({3})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00150: Source table ''{0}'' does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00151: Target table ''{0}'' does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00152: Source index ''{0}'' does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00153: Target index ''{0}'' does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00154: The number of source key columns ({0}) does not match the actual number of columns ({1}) of index ''{2}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00155: The number of target key columns ({0}) does not match the actual number of columns ({1}) of index ''{2}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00156: Source key column ''{0}'' is not part of index ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00157: Target key column ''{0}'' is not part of index ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00158: The datatype of source key column ''{0}'' ({1}) does not match the datatype of the same column in index ''{2}'' ({3})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00159: The datatype of target key column ''{0}'' ({1}) does not match the datatype of the same column in index ''{2}'' ({3})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00160: The number of source keys columns is different than the number of target key columns

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00161: The datatype of source key column ''{0}'' ({1}) does not match the datatype of target key column ''{2}'' ({3})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00162: Index validation failed because there were no mappable columns.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00163: Enscribe compare pair ''{0}'' cannot be executed because it has user defined keys and sorting is not done in the server.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00164: Enscribe compare pair ''{0}'' cannot be executed because the Confirm Out Of Sync step is on.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00165: NSK compare pair ''{0}'' cannot be executed because it has delta processing enabled and sorting is not done in the server.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00166: NSK Enscribe compare pair ''{0}'' cannot be executed because it has starting/ending key range(s) when sorting is done in the server.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00167: NSK SQL/MP compare pair ''{0}'' cannot be executed because it has SQL predicate(s) when sorting is done in the server.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00168: The comparison format of source column ''{0}'' ({1}) cannot convert to the comparison of target column ''{2}'' ({3}).

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00169: Source column ''{0}'': Agent does not support a comparison format ''{1}'' for datatype ''{2}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00170: Source column ''{0}'': {1} of {2} is greater than the max of {3}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00171: Source column ''{0}'': Agent format ''{1}'' does not support ''{2}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00172: Source column ''{0}'' and target column ''{1}'': ''{2}'' is mismatched ({3} and {4}).

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00173: The comparison format of source key column ''{0}'' ({1}) cannot convert to the comparison format of target key column ''{2}'' ({3}).

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00174: The {0} table info is missing the ''{1}'' attribute.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00176: Compare pair ''{0}'' has empty user defined key columns.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00177: Column was not validated.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00178: Column mapping is valid.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00179: The connection type of ''{0}'' cannot be changed to ''{1}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00180: The {0} connection type of group ''{1}'' cannot be changed to ''{2}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00181: The {0} connection type of job ''{1}'' must match the {2} connection types of all included groups.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00182: Manager at {0}:{1} is not supported because: {2}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00183: Internal Error: RunJobModify failed with: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00184: Error message: {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00185: SAX Exception: {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00186: Sorting failed with an IO error: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00187: Sorting failed for an unknown reason: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00188: Requested sort memory size, {0}m, too large; sort memory set to {1}m

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00189: Total sort memory is {0}m

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00190: Requested Maximum comparison memory, {0}m, cannot exceed total memory size; maximum comparison memory is set to {1}m

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00191: Maximum comparison memory is {0}m

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00192: The requested comparison memory {0}m exceeds the configured maximum {1}m

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00193: The memory request waiting threshold, {0}, has been exceeded

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00194: The maximum number of concurrent writes is {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00195: The maximum number of concurrent reads is {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00196: Agent DBMS type changed: was {0} but is now {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00197: Partition ''{0}'' was not found.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00198: {0} Repair Agent failure ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00199: Repair is not supported by connection ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00200: Nothing selected for repair

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00201: Delta partition name mismatch for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00203: Delta partition physical name mismatch for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00204: Delta processing partition count mismatch for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00205: Source Reader should have completed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00206: Comparison threads did not stop

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00207: Repair cannot be executed with Check Update Values set to 'true' when initial comparison skipped the COOS step.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00208: Repair cannot be executed because the Out-Of-Sync file cannot be opened.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00209: Use Secure Socket Layer (SSL) for agent-server communication

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00210: Error in communicating with the Agent.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00211: Could not find component {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00212: Exception Stack Trace

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00213: Missing Item Type: {0}, Missing Item Name: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00214: MethodNotFoundException, coding error

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00215: {0} is Null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00216: Unknown Item Type: {0}, Unknown Item Name:{1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00217: Unable to proceed because {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00218: Duplicate {0}: {1}: {2}: {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00219: {0} does not support {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00220: {0} has unexpected status {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00221: The job run did not finish yet

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00222: Could not execute {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00223: Error when dropping tables: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00224: Unable to make a datasource connection using {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00225: Executing {0} requires {1} role

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00226: Profile/run option {0}(value : {1}) is incompatible with option {2}(value : {3})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00227: Error occurs when running repair job automatically after compare job, error code: {0} error message: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00228: Compare pair ''{0}'' already exists

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00229: Group ''{0}'' already exists

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00230: Job ''{0}'' already exists

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00231: Profile ''{0}'' already exists

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00232: Error reading file header in ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00233: Invalid port number: {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00234: Group ''{0}'' still referenced, you cannot delete it.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00235: Profile ''{0}'' still referenced, you cannot delete it.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00236: Compare pair ''{0}'' does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00237: Group ''{0}'' does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00238: Job ''{0}'' does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00239: Profile ''{0}'' does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00240: Target column ''{0}'': Agent does not support a comparison format ''{1}'' for datatype ''{2}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00241: Target column ''{0}'': {1} of {2} is greater than the max of {3}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00242: Target column ''{0}'': Agent format ''{1}'' does not support ''{2}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00243: Target Reader should have completed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00244: The Group referenced no longer exists.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00245: The Job referenced no longer exists.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00301: The Source Table is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00302: The Target Table is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00303: The Source Schema is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00304: The Target Schema is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00501: Connection IO exception: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00502: Unable to perform mapping validation. Please select at least one compare pair.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00503: Source row null for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00504: Un-Registered Veridata MBean : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00505: There is already a compare pair named ''{0}'' in group ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00506: Compare pair with id {0} does not exist in group ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00507: ''{0}'' creating directory ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00508: Delta partition key mismatch for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00509: Delta Processing can not be enabled for the Compare Pair - {0}, Go to Edit Column Mapping -> Delta Processing Tab for performing configuration.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00510: Unable to enable Delta Processing, Please select at least one compare pair.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00511: Unable to disable Delta Processing, Please select at least one compare pair.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00512: Delta Processing is already enabled for this Compare Pair - {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00513: Delta Processing is already disabled for this Compare Pair - {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00600: Source row not null for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00601: Error {0} returned from Start ({1})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00602: Empty reply from {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00603: IO Exception in exchange state={0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00604: oosxml file error: Out-Of-Sync counts of any column should not be less than Out-Of-Sync count of key column

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00605: Error in parsing chunk: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00606: No veridata.cfg file found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00607: veridata.cfg failed to load: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00608: VeridataConfig was not initialized.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00609: Read of ''{0}'' failed: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00610: Could not create sort file on ''{0}'': {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00611: Sort cancelled

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00612: Sort cancelled with error: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00613: Error parsing agent response: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00614: XML writer error: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00615: Could not queue cancel request

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00616: Could not create Out-Of-Sync file: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00617: OOSXML generation failed: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00618: Could not create directory: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00619: Could not open report file ''{0}'': {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00620: Report write failed: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00621: RowHash agent failed: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00622: Unexpected COOS agent exception: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00623: Exception during COOS cancel agents: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00624: Error trying to save job/group reports: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00625: {0} completed with error: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00626: {0} completed {1} comparisons with {2} Out-Of-Sync

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00627: Job ''{0}'' failed: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00628: Failure during cleanup

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00629: In group: ''{0}'' , repair pair ''{1}'' completed with error: {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00630: Repair job ''{0}'' failed: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00631: Ignored exception during cancel: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00632: Repair job ''{0}'' starting

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00633: Repair pair ''{0}'' starting

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00635: Cancel complete for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00636: Processing cancel request for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00637: Still waiting for create lock for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00638: Concurrent comparison limit reached

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00639: Starting comparison: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00640: Comparison ''{0}'' is complete

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00641: First row read

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00642: Registered Veridata MBean : [{0}] object Name: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00643: Comparison job ''{0}'' starting

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00644: Comparison job ''{0}'' Complete

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00645: Available sort memory is {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00646: Available processors are: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00647: Repair pair ''{0}'' is complete

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00648: Number of sort threads: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00649: Attempt to send invalid input

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00650: CSRF Token is missing or not matching with authorized Session

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00651: Config parameter ''truncate_spaces_len'' accepts values of 0 or 1, ignoring ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00652: Not running {0} because {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00653: No ComparePairs of selection have out-of-sync in previous run or No previous stats available to generate oosxml for Job: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00654: Encryption bits ''server.encryption.bits'' is limited to {0} by the JRE.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00655: Encryption of report failed ''{0}'' with: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00657: Report manager failed to start with: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00658: Encryption bits ''server.encryption.bits'' is required and must be a decimal number

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00659: Rolling report encryption key.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00660: Could not allocate mapped memory for sorting. Using heap memory: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00662: Target row not null for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00663: Target row null for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00664: File vdtdomain.cfg was not found : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00665: Current changes in the column mapping affects Source Delta Column configuration, Please disable delta processing , complete and save column mapping , then select delta columns from the delta processing tab.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00666: Current changes in the column mapping affects Target Delta Column configuration, Please disable delta processing , complete and save column mapping , then select delta columns from the delta processing tab.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00667: Delta Column Validation Error.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00668: The Veridata Server version {0} is lower than the minimum repository version {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00669: The Veridata repository version {0} is lower than the minimum version required by the Veridata Server {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00670: Veridata repository connection started with repository version {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00671: Veridata repository connection started. The expected repository version is {0} and the actual version is {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-00673: Repair after compare is not supported for this Job. Please revisit the Profile settings for this Job or uncheck the repair after compare checkbox from Override run options.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-05002: Invalid connection name ''{0}'' is assigned to Group

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20001: Command line flag ''{0}'' is obsolete.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20002: {0} requires a {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20003: Error reading number ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20004: {0} not allowed with {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20005: {0} already specified.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20006: Unrecognized command line flag ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20007: You must specify -job.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20008: {0} has been deprecated and will be ignored

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20009: Run job command line flags require -job or -j

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20010: -g requires -c.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20011: -c requires -g.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20012: -rd0 and -rdN require -c.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20013: You cannot specify ascii/hex keys for SQL tables

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20014: -rN requires a number greater than 0

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20016: The finished stats for record ''{0}'' could not be found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20017: Could not start the vericom asynchronously

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20018: Job ''{0}'' not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20019: Group ''{0}'' not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20020: Compare pair ''{0}'' not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20021: Profile ''{0}'' not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20022: The job {0} is already running with runId {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20023: Job {0} started

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20024: Run ID: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20025: No Job Stats found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20026: Number of Compare Pairs: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20027: Number of Compare Pairs With Errors: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20028: Number of Compare Pairs With No Out-Of-Sync: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20029: Number of Compare Pairs Cancelled: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20030: Job Report Filename: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20031: Compare Pair Report Filename: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20032: Run ID: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20033: Number of Rows Compared: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20034: Number of Rows In Sync: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20035: Number of Rows With Errors: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20036: Number of Rows Out Of Sync: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20037: Compare Pair OOSXML Directory: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20038: Compare Pair OOSXML Filename: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20039: Job Completion Status: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20043: Could not update new repository password.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20044: Error: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20045: Could not validate new repository password.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20046: Could not get Console.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20047: Enter password on the command line instead.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20048: Enter new repository password:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20049: Updated new repository password.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20050: Please visit the [Services->Data Sources->VeridataDataSource] Section in WebLogic Administration console to reset the Veridata Repository Database password. or Please contact System administrator for more information.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20051: Weblogic User Name required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20052: Weblogic password input failed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20053: Authorization failed to run commandline tools.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20054: Authentication failed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20055: Waiting for the Job completion with Polling interval {0} sec

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20056: User Interrupted

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20057: Number of Repair Pairs: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20058: Number of Repair Pairs With Errors: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20059: Number of Repair Pairs Successfully repaired: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20060: Number of Repair Pairs With Warnings: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20061: Number of Repair Pairs Cancelled: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20062: Repair Job Report Filename: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20063: Repair Job Completion Status: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20064: Repair Run ID: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20065: No out-of-sync comparisons for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20066: You cannot specify SQL partitions for Enscribe

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20067: Provided Job does not support Repair operation , Can use ''{0}'' option to override.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-20068: Number of Compare Pairs With Out-Of-Sync: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30000: Expected token: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30002: Replicat filename : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30003: Extract filename : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30004: Uncaught exception

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30005: Both host and port must be defined if either is defined for Source

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30006: Expression syntax error

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30007: Expected assignment source term

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30008: Expression evaluation exception : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30009: Missing arguments to function : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30010: Missing or extra arguments to function : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30011: Invalid expression, found : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30012: Trail ''{0}'' not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30013: Usage: gg2v [[-noscripting|-create|-replace|-update] -wluser <user> [-wlport <port>]] [-p <propfile>] [-o <out file>] [<extract param file>] <replicat param file> or -help or -version

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30015: Operation ''{0}'' already specified

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30016: Unrecognized flag: ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30017: Replicat parameter file required

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30018: -create, -replace, and -update require -wluser

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30019: Operation failed: ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30020: Macro name and parameter name must start with ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30021: Unknown parameter ''{0}'', file: {1}, line: {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30022: Syntax error ''{0}'', file: {1}, line: {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30023: COLMATCH: unrecognized parameter: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30024: Enter WebLogic user password :

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30025: Scripting invocation failed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30026: Scripting successful

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30027: The specified extract file ''{0}'' does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30028: The specified replicat file ''{0}'' does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30029: The option '-wluser' is required when '-noscripting' option not specified

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30030: The option ''{0}'' requires a value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-30031: Both host and port must be defined if either is defined for Target

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-40000: Authorization to allow execution of commandline tools failed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-40001: Authentication failed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-40002: Weblogic User Name required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-40003: Weblogic password input failed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-40004: {0} requires an argument.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-40005: {0} cannot be specified with {1}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-40006: Operation failed with exception: {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-40007: Operation completed successfully

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-40008: OOS files require redirection to a file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-40009: Cannot open {0} for reading.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-40010: Cannot open {0} for writing.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-40011: {0} does not appear to be an encrypted Veridata report file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-40012: Could not generate a new encryption key, check Veridata Server log for errors.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50001: XML configuration is successful

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50002: Enter valid XML file name.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50003: No operation specified. Operation should be [-create|-update|-replace|-delete |-export]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50004: Veridata server is not running. Please start veridata server and rerun the command

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50005: Unable to parse xml file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50006: Unable to read config xml file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50007: Enter WebLogic user password :

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50008: Error in authenticating with WebLogic, please check the supplied arguments or credentials.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50009: Error in executing the scripting request, please contact system administrator for more information.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50010: Error in reading the supplied xml file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50011: Unknown error during scripting execution, please contact system administrator for more information.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50012: The supplied WebLogic user does not have required authorization to access command line tools.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50013: Requested Operation : ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50014: Scripting file name : ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50015: WebLogic Username : ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50016: WebLogic Port number: ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50017: Can not connect to database using connection details ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50018: Connection with the name ''{0}'' already exists.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50019: ComparePair validation failed for Group ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50020: Group with the name ''{0}'' already exists.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50021: Job with the name ''{0}'' already exists.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50023: Invalid group ''{0}'' is assigned to Job

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50024: Invalid profile ''{0}'' is assigned to job

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50025: Invalid profile ''{0}'' is assigned to Compare Pair

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50026: Invalid connection name ''{0}'' is assigned to Job

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50027: Source pattern ''{0}'' is not well formatted

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50028: Connection with the name ''{0}'' does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50029: Group with the name ''{0}'' does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50030: Job with the name ''{0}'' does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50031: White spaces are not allowed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50032: The name ''{0}'' contains the invalid character ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50033: Please enter a valid host name

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50034: The catalog ''{0}'' does not exist on the source system

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50035: The catalog ''{0}'' does not exist on the target system

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50036: The schema ''{0}'' does not exist on the source system

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50037: The schema ''{0}'' does not exist on the target system

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50038: The source primary key, ''{0}'', and the target primary key, ''{1}'', must have the same number of columns

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50039: The target primary key, ''{0}'', requires an index name or a key column list

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50040: The source system requires a catalog name for compare pairs

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50041: The target system requires a catalog name for compare pairs

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50042: The specified index, ''{0}'', does not exist for table ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50043: The specified index, ''{0}'', does not exist for table ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50044: Unable to create Job ''{0}'' due to: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50045: Unable to create Group ''{0}'' due to: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50046: Unable to create Connection ''{0}'' due to: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50047: Unable to create Compare Pair ''{0}'' due to: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50048: Unable to update Job ''{0}'' due to: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50049: Unable to update Group ''{0}'' due to: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50050: Unable to update Connection ''{0}'' due to: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50051: Unable to update Compare Pair ''{0}'' due to: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50052: Unable to delete Group ''{0}'' due to: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50053: Unable to delete Connection ''{0}'' due to: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50054: Unable to delete Compare Pair ''{0}'' due to: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50055: Connection''{0}'' is used by job ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50056: Connection''{0}'' is used by group ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50057: Group ''{0}'' is used by job ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50058: Could not list the existing jobs due to: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50059: Could not list the existing groups due to: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50060: Parsing failed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50061: Error while parsing the XML {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50062: Fatal error while parsing the XML {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50063: Missing required value for ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50064: Missing required boolean value for ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50065: Missing required integer value for ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50066: Invalid integer value for ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50067: Deleting jobs

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50068: Job ''{0}'' deleted

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50069: Deleting groups

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50070: Compare Pair ''{0}'' deleted

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50080: Group ''{0}'' deleted

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50081: Deleting connections

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50082: Connection ''{0}'' deleted

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50083: Updating jobs

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50084: Job ''{0}'' updated

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50085: Updating groups

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50086: Group ''{0}'' updated

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50087: Updating compare pairs for group ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50088: Compare Pair ''{0}'' updated

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50089: Updating connections

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50090: Connection ''{0}'' updated

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50091: Creating jobs

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50092: Job ''{0}'' created

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50093: Creating groups

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50094: Group ''{0}'' created

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50095: Creating compare pairs for group ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50096: Compare Pair ''{0}'' created

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50097: Creating connections

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50098: Connection ''{0}'' created

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50099: Compare Pair validation failed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50100: Skipping Compare Pair ''{0}'' due to {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50101: Compare Pair ''{0}'' validation failed due to {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50102: Compare Pair ''{0}'' validation successful

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50103: Compare Pair ''{0}'' has multiple partition on ''{1}'' side

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50105: Exception caught while processing: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50106: Usage: veridata_scripting [-create|-update|-replace|-delete] configxml_fullpath [-wlPort portno] -wlUser commandline_username

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50107: Connection with the name ''{0}'' has a repairUser but does not have repairPassword or it has a repairPassword but does not have repairUser

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50108: Waiting for the Scripting task completion with Polling interval {0} sec

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50109: User Interrupted

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50110: Profile with the name ''{0}'' already exists.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50111: Profile with the name ''{0}'' does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50112: Unable to update profile ''{0}'' due to: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50113: Unable to delete profile ''{0}'' due to: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50114: Could not list the existing profiles due to: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50115: profile''{0}'' is used by job ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50116: profile''{0}'' is used by Compare Pair ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50117: Deleting profiles

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50118: Profile ''{0}'' deleted

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50119: Updating profiles

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50120: Profile ''{0}'' updated

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50121: Creating profiles

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50122: Profile ''{0}'' created

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50123: Invalid boolean value for ''{0}''. Valid values are true or false.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50124: Invalid boolean value ''{0}'' for ''{1}''. Valid values are true or false.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50125: Invalid integer value ''{0}'' for ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50126: Invalid value ''{0}'' for ''{1}''. See documentation for correct set of values.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50127: Input value ''{0}'' for ''{1}'' is less than minimum supported value of ''{2}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50128: Input value ''{0}'' for ''{1}'' is more than maximum supported value of ''{2}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50129: The parameter ''{0}'' is not supported. Please check documentation for correct parameters.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50130: Precision is not supported for ''{0}'' format.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50131: Scale is not supported for ''{0}'' format.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50132: Timezone is not supported for ''{0}'' format.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50133: Timezone ''{0}'' is invalid or not supported for ''{1}'' format.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50134: Format ''{0}'' is invalid or not supported for ''{1}'' datatype.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50135: Datatype ''{0}'' is invalid or not supported for ''{1}'' connection

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50137: The Query for the specified source delta column : ''{0}'' is empty.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50138: Unable to validate delta configuration, There are no valid delta source columns for this compare-pair : ''{0}'', Group Name : ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50139: The supplied source delta column : ''{0}'', is not a suitable delta column. Compare-Pair Name : ''{1}'' , Group Name : ''{2}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50140: Unable to validate delta configuration, There are no valid delta target columns for this compare-pair : ''{0}'', Group Name : ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50141: The supplied target delta column : ''{0}'', is not a suitable delta column. Compare-Pair Name : ''{1}'' , Group Name : ''{2}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50142: The supplied target delta column : ''{0}'', is not a suitable delta column.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50143: Expecting, source delta configuration for this compare-pair : ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50144: Not expecting, source delta configuration for this compare-pair : ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50145: Expecting, target delta configuration for this compare-pair : ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50146: Not expecting, target delta configuration for this compare-pair : ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50150: {0} requires a {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50151: Error reading number ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50152: {0} not allowed with {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50153: {0} already specified.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50154: Unrecognized command line flag ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50159: Weblogic User Name required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50160: Remote repository DB schema and User Name required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50161: File already exist. Overwrite the file? y/[n].

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50162: Please re-run the export operation with new valid file or provide permission to overwrite the file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50163: File does not have write permission. Please provide valid file name.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50164: Enscribe type ''{0}'' is not valid.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50165: Validating input provided for export.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50166: Boolean value is null. Returning null.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50168: System mapped primary key

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50169: System mapped primary key

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50170: Failed to connect to repository. Please check the connection details provided.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50171: Test connection to repository is successful.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50172: The connection details provided does not contain veridata tables. Please provide valid veridata repository details and try again.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50173: Could not get datasource from spring context.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50174: Error in getting connection from datasource.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50175: Repository version of exported veridata repository : ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50176: Processing Jobs

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50177: Processing Groups

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50178: Processing Connections

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50179: Processing Profiles

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50180: Generating xml scripting file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50181: Writing repository configuration to output file: ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50182: Error while writing configuration to XML file ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50183: Error while reading configuration XML file ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50184: Getting repository connection from url provided ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50185: Getting repository connection from datasource.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50186: Connection list was empty or exporting all connections. No connection name to validate.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50187: Group list was empty or exporting all groups. No group name to validate.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50188: Job list was empty or exporting all jobs. No job name to validate.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50189: Profile list was empty or exporting all profiles. No profile name to validate.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50190: Connection name ''{0}'' is present in the repository

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50191: Connection name ''{0}'' is not present in the repository

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50192: Group name ''{0}'' is present in the repository

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50193: Group name ''{0}'' is not present in the repository

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50194: Job name ''{0}'' is present in the repository

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50195: Job name ''{0}'' is not present in the repository

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50196: Profile name ''{0}'' is present in the repository

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50197: Profile name ''{0}'' is not present in the repository

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50198: Connection option not provided for exporting. Not exporting any independent connection objects.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50199: Group option not provided for exporting. Not exporting any independent group objects.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50200: Job option not provided for exporting. Not exporting any independent job objects.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50201: Profile option not provided for exporting. Not exporting any independent profile objects.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50202: Exporting all connections.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50203: Exporting all groups.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50204: Exporting all jobs.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50205: Exporting all profiles.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50206: Exporting connections present in list.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50207: Exporting groups present in list.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50208: Exporting jobs present in list.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50209: Exporting profiles present in list.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50210: Not exporting any connections.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50211: Not exporting any groups.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50212: Not exporting any profiles.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50213: Exporting connection ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50214: Exporting group ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50215: Exporting job ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50216: Exporting profile ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50217: Failed to export connections.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50218: Failed to export groups.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50219: Failed to export jobs.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50220: Failed to export profiles.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50221: Jdbc connection URL is null.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50222: The connection url ''{0}'' is unrecognized. URLs need to start with one of ''{1}}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50223: Jdbc driver class ''{0}'' not found in the classpath.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50225: NSK file-pattern is not supported with schema wildcard. Please use exact names with file-pattern options.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50226: Connection names.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50227: Group names.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50228: Job names.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50229: Profile names.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50230: Connection names provided by user.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50231: Group names provided by user.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50232: Job names provided by user.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50233: Profile names provided by user.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50234: Argument 'vdtPath' is only for export operation when using external veridata db and using 'exportPassword' argument.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50235: Exporting connections for external veridata db.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50236: Temporary file for connections : ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50237: External veridata installation path is null. Path is required for exporting password for external veridata installation.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50238: External veridata installation path ''{0}'' does not exist or is incorrect. Please enter correct path for external veridata installation.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50239: Checking if veridata path is 12c path : ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50240: Checking if veridata path is 11g path : ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50241: Path ''{0}'' does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50242: Jps file was not found in the path ''{0}''. Please enter the correct veridata installtion path. It will be domain path for 12c and Installation location for 11g.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50243: Path of jps file is ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50244: Could not find java.home from system property.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50245: Java home ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50246: Java home ''{0}'' does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50247: Jar file location ''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50248: Failed to export connection password to file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50249: Using temporary jps config file ''{0}'' for veridata 11g.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50250: Failed to read passwords from wallet.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50251: Wrong number of arguments passed for wallet export operation.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50252: Wrong argumnet passed ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50253: The source system requires a schema name for compare pairs

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50254: The target system requires a schema name for compare pairs

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50255: Veridata path provided ''{0}'' does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50256: Veridata path ''{0}'' should be a directory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50257: "vdtPath" argument is missing. Exporting password for external Veridata setup requires 'vdtPath' argument as well.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50258: Unable to validate delta configuration, Both Source and Target Delta Queries can not be Null for this compare-pair : ''{0}'', Group Name : ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50259: Unable to validate delta configuration, Source Delta Query required for this compare-pair : ''{0}'', Group Name : ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50260: Unable to validate delta configuration, Target Delta Query required for this compare-pair : ''{0}'', Group Name : ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50261: No operation specified. Operation should be [-export]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50262: No operation specified. Operation should be [-create | -update | -delete | -replace]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50263: Operation ''{0}'' not allowed for profile ''{1}''. Only update operation is allowed for default profile.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50264: Target pattern ''{0}'' is not well formatted

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50265: Unable to delete Job ''{0}'' due to: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-50266: Not exporting any jobs.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60001: Veridata Agent Version {0} built on {1} {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60002: Veridata Agent running on {1} port {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60003: Veridata Agent shutting down on port {0} due to error: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60004: Veridata Agent stopped on port {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60005: Could not find the agent properties file ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60006: Error reading file ''{0}'': {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60007: Character set conversion error: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60008: The database.url property is required.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60009: The database.url ''{0}'' is unrecognized. URLs need to start with one of ''{{1}}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60010: Starting session {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60011: Session {0} stopped

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60012: IO Error encountered: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60014: Session: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60015: Missing value for: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60016: Parsing exception: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60017: Parsing warning: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60018: Unexpected type: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60019: Corrupted row encountered: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60020: Record length exceeds bytes remaining in message

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60021: Row length exceeds bytes remaining in message

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60022: {0} rows updated

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60023: user ''{0}'' connected to ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60024: Failed to open data source for user {0} (from {1} host)

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60025: User ''{0}'' could not connect to database: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60026: Could not get schemas: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60027: Could not get tables: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60028: Could not get database version: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60029: Could not get metadata for ''{0}'': {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60030: Could not get index metadata for ''{0}'': {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60031: Could not list catalogs: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60032: Could not execute statement <{0}>: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60033: Table ''{0}'' not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60034: Could not convert value to a String: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60035: Could not convert value to a number: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60036: Could not get type info: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60038: Database query failed: ''{1}'' SQL<{0}>

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60039: COOS lookup query failed: ''{1}'' SQL<{0}>

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60040: The specified transaction isolation level, ''{0}'', is not recognized

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60041: The specified transaction isolation level, ''{0}'', is not support for {1} databases

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60042: The length of column ''{0}'', {1}, exceeds the supported maximum length, {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60043: The display value of hash column ''{0}'' was truncated to {1} bytes

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60044: An unexpected exception has occurred: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60046: A catalog is required

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60047: Starting source initial compare for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60048: Database metadata request failed: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60049: Could not load database driver ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60050: The connection cache property ''{0}'' has been set to ''{1}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60051: You must login before getting ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60052: Comparison format ''{0}'' is not supported on ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60053: Repair fetch query failed: ''{1}'' SQL<{0}>

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60054: Lookup failed during apply: ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60055: Fetch of long varchar/varbinary returned 0 rows.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60056: Repair apply failed: ''{0}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60058: Unexpected tag: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60059: Could not configure XML output: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60060: The side, ''{0}'', specified in the request does not match the side specified in the login request

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60063: Ignoring conversion exception: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60064: Duplicate key found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60065: Caught unexpected SQL exception: {0} retry= {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60066: CLOB I/O error: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60067: Error freeing temporary CLOB: {}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60068: Could not set the Session Time Zone to {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60069: Ignoring invalid database hint: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60070: Character encoding exception: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60071: SQLException was ignored: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60072: Processed {0} rows and waited on full queue: {1} times

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60073: JDBC Driver version: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60074: Request was unexpectedly interrupted

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60075: OGGV-60152

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60076: Cannot parse the database exception error code "{0}", expecting integer

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60077: Type name ''{0}'' java.sql.Types value ''{1}'' defaulting to BLOB type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60078: Repair apply failed: code: {0}, msg: ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60079: Disable triggers requires replication role

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60080: Could not get position for column ''{0}'' in table ''{1}'' for index ''{2}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60150: Configuring logging.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60151: Config file for logger is {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60153: Expected {0} type to be {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60154: SQL exception occurred during UDT lookup of {0}, msg: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60155: Field {0} not found in UDT {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60156: Field {0} expected type {1}, got {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60157: Field {0} was missing value.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60158: Unable to serialize: {0}, msg: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60159: Unable to deserialize: {0}, msg: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60160: Connection changed in UDT description

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60161: Shutdown request complete: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60162: Reset log request complete: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60163: Agent communications error: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60164: Query to get the delta-base value, failed: ''{1}'' SQL<{0}>

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60165: Invalid delta-base value-query, result set.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60166: No valid rows on delta base value-query, result set.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60167: More than one rows in delta base value-query, result set.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60168: More than one column in delta base value-query, result set.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60169: More than one result-set in delta base value-query, result.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60170: Unable to get the delta base value from the query.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60171: Unable to convert Oracle number {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60172: {0} rows deleted

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-60173: {0} rows inserted

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70001: **** Creation of Veridata User Started ****

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70002: Database type : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70003: Database connect url : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70004: Database jdbc driver : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70005: Database dba user : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70006: Database schema user : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70007: RCU home path : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70008: Log path location : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70009: Changed MySQL URL : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70010: RCU Connection url : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70011: RCU Connection user : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70012: RCU Connection passed is null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70013: **** Successfully created Veridata User and Database ****

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70014: *** Insertion of data into Veridata repository started ****

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70015: **** Successfully Inserted data into Veridata Repository ****

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70016: *** Deletion of Veridata repository started ****

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70017: **** Successfully deleted Veridata Repository ****

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70018: Using rcu log level : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70019: Using default log level {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70020: Error in creating Veridata user {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70021: Error in creating Veridata database {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70022: Unsupported database type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70023: Error in Veridata schema user creation

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70024: Error in inserting data into repository

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70025: Error in dropping Veridata repository

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70026: RCU_LOG_LEVEL invalid level: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70027: File {0} not found on classpath

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70028: Error in closing open input stream

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70201: Saving file : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70202: Loading file : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70203: Key : {0} not updated

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70204: Updating key : "{0}" , value : "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70205: Found null key

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70206: String ''{0}'' should match pattern ''{1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70207: Loaded Veridata configuration file : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70208: Error processing Veridata configuration file : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70209: Unknown argument : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70210: Arguments can not be empty.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70211: configureVeridata.(sh/cmd) [-pU<veridata.config.property>=<New Value>] [-redeploy -wluser=<weblogic domain admin username>] [-refreshConfig]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70212: When -redeploy option is specified , Weblogic Domain Administrator user name must be specified in -wluser argument.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70213: Enter the password for WebLogic Domain Administrator user {0} :

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70214: Property VERIDATA_ORACLE_HOME not set.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70215: Added key : "{0}", value : "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70216: Failed to refresh the veridata.cfg file. File was not updated.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70301: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70302: Could not create user {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70303: Could not create database {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70304: Could not install database {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70305: Could not drop database {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70306: Could not remove Veridata from database {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70307: Could not drop user {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70308: Upgrade cannot be done on {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70309: Could not upgrade database {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70310: Failed to retrieve current schema version {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70311: Failed to alter schema for tables {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70312: Failed to grant permission for user {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70401: Length of arguments that are sent to repository are {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70402: WLS domain home argument passed to the patching script is {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70403: Veridata config file location: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70404: Database name is either null or not specified in Veridata config file and patching cannot be continued

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70405: Database name key from Veridata config file: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70406: Failed to apply repository patch

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70407: User terminated the patching operation

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70408: Password is missing for database user

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70409: You are about to patch the repository and database details are - Database URL :: {0} Database User :: {1} Make sure database backup have taken up before proceeding next steps.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70410: Enter Veridata database repository password:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70411: Veridata repository patching is successful.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70412: JdbcUrl used in datasource xml: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70413: Jdbc driver class used in datasource xml: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70414: DB user used in datasource xml: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70415: Veridata repository patching is failed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-70416: Expected argument is missing, Failed to apply repository patch

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80001: Get credential for {0}.{1} failed: {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80002: Put credential for {0}.{1} failed: {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80003: Create credential for WEB.{0} failed: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80004: Remove credential for {0}.{1} failed: {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80005: Update credential for WEB.{0} failed: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80006: Authenticate credential for WEB.{0} failed: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80007: Digest credential failed: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80008: Could not get JpsContextFactory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80009: Could not get JPS Config location

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80010: Could not get CredentialStore instance

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80011: Could not check if credential exists in wallet

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80012: Could not remove all credentials in map: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80013: Could not get repository password.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80014: Could not dump credentials

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80015: Could not remove all credentials starting with: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80016: Could not open input stream: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80017: Could not process xml stream.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80018: Wallet messages are installed correctly.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80019: The property {0} has not been set.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80020: Wallet ''{0}'' does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80022: Enter Agent Identity Store unlock password:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80023: Enter Agent Identity Store entry password:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80024: Enter Agent Trust Store unlock password:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80025: Agent Wallet not initialized.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80026: Password can not be empty for key : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80027: Invalid Agent KeyStores path configuration.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80028: Copyright (c) 2013, 2015, Oracle and/or its affiliates. All rights reserved.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80029: Veridata Agent SSL Configuration Utility

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80030: Notes:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80031: 1.This utility reads the configuration from agent configuration properties file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80032: The agent configuration properties file needs to be updated before executing this script.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80033: 2.Enter the Entry and Unlock passwords of the configured key-stores below.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80034: Server Identity Store is empty or no alias names found.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80035: Unable to find any valid alias names in Server Identity Store.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80036: Unable to find agent configuration file : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80037: SSL Configuration of Veridata Agent with agent id : {0} is successful.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80038: Error during SSL configuration, please contact System Administrator for more information.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80039: Log redirected to the file : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80040: Exception stack trace

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80041: Cannot get SecureRandom instance: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80042: Unrecognized password encoding.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80043: Error in creating OPSS keystore service.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80044: Could not get VeridataWebIdentityStore

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80045: Could not get VeridataWebTrustStore

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80046: Could not get VeridataWebSymKeyStore

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80047: Cannot find MBservers for domain: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80048: Could not change password

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80049: ''{0}'' removed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80050: Error during wallet export information, please contact System Administrator for more information.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80051: Error during wallet import information, please contact System Administrator for more information.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80052: Exporting Wallet : MapName = {0}, Wallet Key = {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80053: Importing Wallet : {0} key : {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80054: Wallet {0} complete

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80055: {0} Wallet - mapName = {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80056: Could not encrypt property

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80057: Could not decrypt property

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80058: Invalid JPS configuration file location : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80059: Invalid Veridata Wallet Map Name

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80060: Invalid Veridata Wallet Store Location Name : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80061: Invalid Veridata Wallet Store Location : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80062: Error during initializing Veridata Wallet Store.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80063: Wallet Store file does not exist : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80064: Error during checking if key exists in wallet.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80065: Error during getPassword in wallet.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80066: Error during Wallet Store Save Operation.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-80067: Connection list is empty or null. No password will be exported.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-500167: Side ''{0}'' not recognised

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

OGGV-600013: Unhandled exception ''{0}'': {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

34 OHS-03506 to OHS-04533

OHS-03506: OHS audit configuration load failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03507: OHS audit configuration save failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03508: Unable to set Custom Log configuration

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03509: CustomLog configuration is wrong

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03526: Failed to read file {0}, because of {1} exception.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03570: ThreadLimit may not exceed MaxThreadLimitValue.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03571: ServerLimit may not exceed MaxServerLimitValue.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03572: MaxRequestWorkers exceeds range, raise ServerLimit.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03573: MaxRequestWorkers exceeds range, raise ServerLimit or ThreadPerChild.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03575: The value of ThreadLimit cannot be less than the value of ThreadsPerChild.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03576: The value of ThreadsPerChild cannot be greater than the value of ThreadLimit.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03577: The value of ServerLimit cannot be less than the value of MaxRequestWorkers.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03578: The value of ServerLimit * ThreadsPerChild cannot be less than the value of MaxRequestWorkers.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03579: Virtual Host Already Exists

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03580: Not a proper Virtual Host Name

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03581: Error enabling module "{0}" : {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03582: The specified module "{0}" is not installed. Module has to be installed before configuring it.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03583: Register child MBean api failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03584: Proxy Port MBean registration failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03585: Audit MBean registration failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03586: Parsing error while loading MBeans

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03587: Exception occurred while loading MBeans

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03588: Virtual Host creation failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03589: Duplicate virtual host found

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03590: Base Virtual host creation failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03594: Unregister of configuration MBeans failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03595: Unable to get VH objects from root OHS MBean

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03596: Load wallets failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03597: Removal of Virtual Host failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03598: Removal of Listen failed while removing VH

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03601: Load failed with IOException

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03602: Module name can not be null

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03604: Unable to find Server Name, Setting it to default AdminServer

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03605: Virtual host MBean registration failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03606: The current MPM does not support directive {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03607: Port {0} for {1} is already in use on machine "{2}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03608: No ports for {0} were available for auto-assignment on machine "{1}" in the range {2}-{3}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03609: Port {0} for {1} is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03610: Error disabling module "{0}" : {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03611: Instance "{0}" is in state "{1}" and cannot be deleted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03612: The port value, {0}, has already been used and cannot be configured for {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03613: The mpm "{0}" is not supported for this platform

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03614: The umask "{0}" is not valid, please provide an octal number less than or equal to 0777.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03701: Error log configuration not valid

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03702: Saving wallet is null

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03703: P12 Wallet is null; Possibly because the wallet is absent/not configured.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03704: CWallet is null, not able to load cwallet

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03705: Directive does not exist

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03707: WLHost not configured; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03708: WLCluster not configured; Not allowed to call listWLCluster

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03709: DynamicServerList is not configured ; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03710: SSLCARevocationPath is not configured

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03711: SSLCRLCheck or SSLCARevocationFile is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03712: SSLWallet is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03713: SSLVerifyClient is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03714: SSLCipherSuite is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03715: SSLProtocol is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03716: SSLEngine is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03717: Value cannot start with '#'.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03718: The file requested, "{0}", is not part of the current OHS configuration. Please enable the file first.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03719: Cannot register virtual host :

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03720: No virtual host name specified. Invalid virtual host name.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03721: Default Virtual Host name must be a port number or * or an empty string.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03722: Virtual Host-Server Name "{0}"-"{1}" already exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03723: Syntax Error in Log configuration: operation failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03724: Could not parse configuration file template value "{0}" on createInstance() invocation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03725: Key "{0}" is not a valid configuration file template value on createInstance() invocation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03726: Configuration file template value "{0}" does not contain a valid port number on createInstance() invocation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03728: Instance name invalid. "{0}" is longer than 30 characters.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03729: Instance name invalid. "{0}" does not start with a letter.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03730: Instance name invalid. "{0}" contains an invalid character.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03731: Instance name invalid :"{0}". The following reserved names (ignoring letter case) are not allowed as instance names : "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03732: OHS instance already exists ("{0}").

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03733: OHS instance does not exist ("{0}").

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03734: Invalid port number "{0}" is specified. Port number must be between 1 and 65535 inclusive.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03735: Invalid log level :"{0}". Valid log levels are : "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03736: File {0} could not be read

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03737: Property file {0} could not be loaded; using defaults

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03738: NodeManager is unreachable for the instance "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03739: NodeManager is unreachable for the machine "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03740: KeepAliveTimeout "{0}" is not valid. Use KeepAliveTimeout num[ms|s|mi|h].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03741: Specify severity for module "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03742: Invalid module "{0}". Only module identifiers specified in LoadModule directives with the trailing _module omitted and statically compiled modules are supported

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03743: OraLogLevel cannot be empty

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03744: Log level "{0}" is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03745: LogLevel syntax is not valid. Use LogLevel [module:]level [module:level] ...

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03746: LogLevel cannot be empty

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03747: Log severity "{0}" is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03748: OraLogLevel syntax is not valid. Use OraLogLevel [module_name] <msg_type>[:msg_level] ...

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03749: The cipher "{0}" is not valid

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03750: The protocol "{0}" is not valid

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03751: The authentication type "{0}" is not valid

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03752: The crl "{0}" is not valid

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03753: The validation path is not specified

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03754: The wallet is not specified

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03755: VirtualHost copntainer with value "{0}" was not found in the file "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03756: There was no "{0}" directive with value "{1}" in the file "{2}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03801: Load Operation failed in VH SSLResource

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03802: Load Operation finished in VH SSLResource for instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03804: Load operation success for instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03805: The specified module "{0}" is already enabled.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03806: Unregistered all configuration MBeans for instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03807: Wildcard char, allow processing

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03808: Error log configuration mode is not apache

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03809: Error log Mode is apache

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03810: Listen Directive not configured

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03811: Listen Directive already exist for specified port

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03814: An error occured while setting the file contents for the config file "{0}". Make sure that the specified configuration file content is of valid format.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03815: It is not permitted to edit "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03816: The specified configuration file "{0}" is not part of the configuration.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03817: An error occurred setting the contents of config file "{0}": {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03818: An error occurred updating the instance "{0}": {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03819: The specified module "{0}" is already disabled.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03820: Directory "{0}" is missing from the Oracle HTTP Server installation. The instance cannot be created.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03821: The ohs.product.home property is not set. The instance cannot be created.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03822: The fully qualified domain name for host "{0}" could not be resolved. ServerName will be set to "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03823: No parameter found on include

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03828: Can not find directive in new DirectiveLine

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03829: Failed to find < in Container directive

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03830: Failed to find space in Container directive

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03831: Failed to find > in Container directive

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03832: IOException reading file

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03833: Never found container terminator for

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03834: Element to add after not found

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03835: Element to add before not found

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03836: Can't find element to remove

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03837: Can't clear the container

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03838: Comment must be empty string or start with #.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03840: Listen directive corresponding to the address({0}) exists in configuartion file of another instance

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03841: Error while creating the keyStore "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03842: Error while deleting the keyStore "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03843: Listing KeyStores failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03844: Error while exporting the keyStore "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03845: Exporting an empty KeyStore is not allowed, please add certificate(s) before exporting.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03846: The keystore "{0}" already exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03847: Keystore not associated with any OHS instance.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03848: The value "{0}" is not valid for the directive "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03849: MinSpareThreads cannot be greater than MaxSpareThreads.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03850: MaxSpareThreads cannot be less than MinSpareThreads.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03851: Error while creating demo CA-signed certificate.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03852: Error while importing the contents of a wallet for the instance "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03853: The certificates in the wallet "{0}" are not being imported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04001: Error while starting the server {0}: server start/stop is already in progress

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04002: Error while stopping the server {0}: server start/stop is already in progress

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04003: Graceful stop of server {0} failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04004: Error while restarting the server {0}: server start/stop is already in progress

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04005: Check the instance log file for more information: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04006: Error while restarting the server {0}: server is not currently running

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04007: Failed to start the server {0} successfully: attempting to cleanup the process

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04008: Failed to stop the server {0} gracefully: attempting to kill

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04009: Failed to re-start the server {0} completely: attempting to cleanup the process

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04010: Server {0} is in an inconsistent state -- the process could not be stopped or killed. This issue must be manually resolved

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04011: Property file {0} could not be loaded; using defaults

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04012: Invalid property {0} was configured in file {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04013: Property {0} has value {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04014: Property {0} was configured with invalid value {1} in file {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04015: Invalid instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04016: Failed to start the server {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04017: Failed to restart the server {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04018: Starting server {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04019: Restarting server {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04020: Stopping server {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04021: Corrupted value {0} for property

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04022: File {0} could not be read

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04023: Invalid property specified: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04024: Valid properties are {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04025: Invalid value {0} for property {1} specified:

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04026: Valid values are {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04027: Valid values are between {0} and {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04028: Unexpected validator type

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04029: {0}: command timed out; the process has been terminated

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04030: {0}: command stdout/stderr IO error

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04031: Check log file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04032: Invalid property environment variable name {0} configured in {1}: {2}. Property environment name syntax is {3}, where {4} is the optional append flag, {5} is the optional numeric order value, and {6} is the name of the environment variable

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04101: Instance {0} already exists

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04102: InstanceDirectory {0} does not contain a valid OHS instance

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04103: Unable to delete the directory: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04104: Failed to create instance directory: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04106: Unable to delete the file: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04107: No instance root: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04108: Instance {0} is alive; cannot delete

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04109: Errors occured while commiting changes for the following instances: {0}. Check {1} for details

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04110: ohs.product.home system property is not set

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04111: Unable to find a valid OHS installation at {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04112: Creating instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04113: Deleting instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04114: Updating instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04115: Synchronization copy of {0} to {1} failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04116: Failed to make directory {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04117: Failed to create file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04118: Failed to delete {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04251: Failed to reach the OHS instance: {0} Make sure that instance is up and running

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04252: OHS instance failed to respond to the requested URL: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04401: Unable to find template directory {0} within OHS installation at {1}. Make sure that {1} contains a valid OHS installation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04402: Unable to copy template directory {0} to directory {1} within new instance

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04501: Connect to a WebLogic server before using this command.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04502: Unexpected error: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04503: ohs_createInstance() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04504: ohs_deleteInstance() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04505: Machine "{0}" does not exist.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04506: Instance "{0}" already exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04507: Instance "{0}" is in state "{1}" and cannot be deleted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04508: Instance "{0}" does not exist.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04511: Port {0} is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04512: The following arguments are not valid :{0} .

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04513: The following required arguments are missing :{0} .

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04514: Port {0} was specified more than once for the new instance.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04515: The new instance uses a privileged port. Refer to the privileged port configuration information in the product documentation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04516: Instance name "{0}" is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04517: Instance names are limited to thirty characters, must begin with a letter, may contain letters, numbers, -, or _, and must not be one of the following reserved names(ignoring letter case): {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04519: OHS instance "{0}" was successfully created.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04520: OHS instance "{0}" was successfully deleted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04521: ohs_addAdminProperties() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04522: ohs_addNMProperties() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04523: ohs_createTestDomain() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04524: Domain "{0}" already exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04525: Privileged ports are not supported with this command.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04526: NodeManager is unreachable. "{0}" might be in undeletable state because the NodeManager is unreachable.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04527: ohs_exportKeyStore() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04528: Disconnect from WebLogic server before using this command.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04529: Update of OHS instances failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04530: OHS instances have been updated successfully.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04532: This method is deprecated, please refer to product documentation for more details.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04533: Keystore "{0}" successfully exported to OHS instance "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

35 OJRF-00001 to OJRF-00008

OJRF-00001: NOT on WLS - could not calculate application name for Jersey Client. Using default

Cause:

Action:
Level: 1

Type: WARNING

Impact: JAXRS_CLIENT

OJRF-00001: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: JAXRS_SERVER

OJRF-00002: Could not retrieve ServerPlatformSupport: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: JAXRS_CLIENT

OJRF-00002: State sensor for {0} couldn't be created. StateFactory didn't return valid sensor.

Cause:

Action:
Level: 1

Type: WARNING

Impact: JAXRS_SERVER

OJRF-00003: State sensor for {0} couldn't be created. Couldn't retrieve StateFactory.

Cause:

Action:
Level: 1

Type: WARNING

Impact: JAXRS_SERVER

OJRF-00004: Event sensor for {0} couldn't be created. EventFactory didn't return valid sensor.

Cause:

Action:
Level: 1

Type: WARNING

Impact: JAXRS_SERVER

OJRF-00005: Event sensor for {0} couldn't be created. Couldn't retrieve EventFactory.

Cause:

Action:
Level: 1

Type: WARNING

Impact: JAXRS_SERVER

OJRF-00006: Phase event sensor for {0} couldn't be created. PhaseEventFactory didn't return valid sensor.

Cause:

Action:
Level: 1

Type: WARNING

Impact: JAXRS_SERVER

OJRF-00007: Phase event sensor for {0} couldn't be created. Couldn't retrieve PhaseEventFactory.

Cause:

Action:
Level: 1

Type: WARNING

Impact: JAXRS_SERVER

OJRF-00008: OWSM ResourcePattern not available for application {0} and module {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: JAXRS_SERVER

36 ORABPEL-00006 to ORABPEL-22005

ORABPEL-00006: failure to load the JCE cipher "{0}"

Cause: The environment may not have been set correctly.

Action: JCE library files must be installed in the JRE installation as an extension. Copy the jar files from "{1}\install\java\jce1.2.2" directory to "(jdk_path)\jre\lib\ext" directory (where jdk_path is JDK installation directory).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00007: failure to decrypt cipher text with transformation "{0}"; exception reported is: {1}

Cause: This was an internal error. It may have been caused by an incorrect cipher state or an invalid padding size being specified.

Action: Contact Oracle Support Services. Provide the error message and the process that appeared to cause the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00008: failure to encrypt plain text with transformation "{0}"; exception reported is: {1}

Cause: This was an internal error. It may have been caused by an incorrect cipher state or an invalid padding size being specified.

Action: Contact Oracle Support Services. Provide the error message and the process that appeared to cause the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00015: failure to create jar file {0}

Cause: The Sun tools.jar may not have been installed on the local machine or included in the class path.

Action: Verify that tools.jar is installed on this machine and is included in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00016: failure to execute javac compiler on file(s) "{0}"; exception reported is: {1}

Cause: The Sun tools.jar may not have been installed on the local machine or included in the class path.

Action: Verify that tools.jar is installed on this machine and is included in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00017: failure to compile file(s) "{0}"; exception reported is: {1}

Cause: The generated Java class(es) had errors and/or all the required libraries to compile the class(es) were not available.

Action: Verify that the file named in the error message is valid Java file and that all required libraries are included in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00018: cannot find the Java source directory "{0}"

Cause: The specified Java source directory did not exist or it could not be written to.

Action: Create the source directory named in the error message and set the write permission accordingly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00019: cannot create the Java destination directory "{0}"

Cause: The parent directory permissions prevented the creation of this directory.

Action: Verify that the parent directory for the directory named in the error message is writable.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00020: failure to write the Javadoc argument file "{0}"; exception reported is: "{2}"

Cause: The Javadoc file named in the error message was not written to the directory "{1}".

Action: Verify that the directory "{1}" can be written to.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00021: failure to execute Javadoc with the argument file "{0}"

Cause: The Javadoc executable was not found in the system path or was not executed.

Action: Verify that Javadoc is installed on this machine in the <JDK>\bin directory and that this directory is included in the machine system path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00024: failure to schedule the "{0}" agent with the scheduler; exception reported is: {1}

Cause: The Quartz scheduler did not schedule the job named in the error message. This is typically an internal scheduler error.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00025: failure to unschedule the "{0}" agent with the scheduler; exception reported is: {1}

Cause: The Quartz scheduler did not unschedule the job named in the error message. This is typically an internal scheduler error.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00026: error while attempting to execute the job "{0}" for agent "{1}"; exception reported is: {2}

Cause: This error was a wrapper for an internal exception thrown by the underlying scheduler job.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00201: cannot return system authentication token for caller "{0}"

Cause: This was an internal error. The agent "{0}" was not added to the allowed callers list for the system token.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00209: The domain identifier "{0}" is not registered with the server.

Cause: All domain identifiers were kept in the domain table; this table may have been modified incorrectly.

Action: Restart the application server; if the domain directory is present, the identifier will be automatically registered again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00210: domain ref "{0}" is not registered with the server.

Cause: All domain identifiers were kept in the domain table; this table may have been modified incorrectly.

Action: Restart the application server; if the domain directory is present, the identifier will be automatically registered again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00214: The OraBPEL server has not finished initializing yet; the initialization process may be complete in a few moments.

Cause: A request was sent to the server before it finished initializing.

Action: Resubmit the request. If this does not solve the problem, check the logs (with logging level set to debug mode) for error messages.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00215: error while attempting to instantiate the JDK adapter class "{0}" for run-time version "{1}"; exception reported is: {2}

Cause: The JDK adapter class named in the error message was not in the system class path or there was an incompatibility with the JDK used to the compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00216: JDK adapter class "{0}" for run-time version "{1}" does not implement the IJDKAdapter interface

Cause: This was an internal error. All JDK adapters registered with the system must conform to the IJDKAdapter interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00217: JDK version "{0}" is not supported by the OraBPEL run-time; currently only JDK versions 1.4 and 1.5 are supported

Cause: A JDK adapter was not specified for the JVM version with which the container was started.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00219: cannot instantiate an instance for the class "{0}"

Cause: The class "{1}" was not granted sufficient permissions by the JVM to instantiate the class "{0}".

Action: Verify that the OraBPEL run-time class "{1}" has the necessary security permissions to access the class specified in the error message.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00220: class "{0}" (for the platform adapter for platform "{1}") does not implement the IPlatformAdaptor interface

Cause: This was an internal error. All platform adapters registered with the system must conform to the IPlatformAdaptor interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00221: error while attempting to instantiate the class "{0}" as the adapter for platform "{1}"; exception reported is: {2}

Cause: The platform adapter class "{0}" was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00222: class for platform adapter "{0}" (platform "{1}") cannot be found

Cause: The platform adapter class "{0}" was not in the system class path.

Action: Ensure that Oracle BPEL libraries are set correctly in the system class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00227: class "{0}" (for the database adapter for "{1}") does not implement the IDatabaseAdaptor interface

Cause: This was an internal error. All database adapters registered with the system must conform to the IDatabaseAdaptor interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00228: error while attempting to instantiate the class "{0}" as the database adapter, data source "{1}"; exception reported is: {3}

Cause: The database adapter class "{0}" was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00229: database adapter class name for data source "{0}" has not been specified

Cause: The database adapter class "{0}" was not in the system class path.

Action: Ensure that the Oracle BPEL libraries are set correctly in the system class path. If the libraries are configured correctly, the adapter configuration files may have been modified incorrectly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00230: adapter resource file "{0}" cannot be found in the current class path

Cause: The resource file named in the error message contained all the JNDI mappings required for the BPEL process domain to initialize.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00231: error while attempting to instantiate the class "{0}" as the adapter manifest for "{1}", data source "{2}"; exception reported is: {3}

Cause: The adapter manifest class "{0}" was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00232: class "{0}" (for the adapter manifest for "{1}", data source "{2}") does not implement the IServerAdaptorManifest interface; all adapter manifests used by the OraBPEL server must implement this interface

Cause: This was an internal error. All adapter manifests registered with the system must conform to the IServerAdaptorManifest interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00233: adapter manifest class name for "{0}", data source "{1}" is not specified.

Cause: The adapter manifest class "{0}" was not in the system class path.

Action: Ensure that the Oracle BPEL libraries are set correctly in the system class path. If the libraries are configured correctly, the adapter configuration files may have been modified incorrectly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00235: The component identifier "{0}" has not been registered with the server.

Cause: All component identifiers were kept in the "component" table; this table may have been modified incorrectly.

Action: Restart the application server; when the component is loaded, the identifier will be automatically registered again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00236: The component reference "{0}" is not registered with the server.

Cause: All component references were kept in the "component" table; this table may have been modified incorrectly.

Action: Restart the application server; when the component is loaded, the reference will be automatically registered again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00237: failure to create the component reference for "{0}"

Cause: The maximum number of components ({1}) were reached.

Action: Contact Oracle Support Services. At the current time, the maximum number of components has been set to 32767.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00238: exception while reading the component index from the data source; the exception reported is: {0}

Cause: There was a problem with connecting to the data source where the component index is stored.

Action: There are three things to verify. Verify that the machine hosting the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for the OraBPEL server has been installed in the data source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00239: exception while writing the component index (application_name "{0}", composite_name"{1}", revision "{2}", label "{3}", component_name "{4}") to the data source; the exception reported is: {5}

Cause: There was a problem with connecting to the data source where the component index is stored.

Action: There are three things to verify. Verify that the machine hosting the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for the OraBPEL server has been installed in the data source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00240: exception occurs while removing the component index (dn "{0}", ref "{1}") from the data source; the exception reported is: {2}

Cause: There was a problem with connecting to the data source where the component index is stored.

Action: There are three things to verify. Verify that the machine hosting the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for the OraBPEL server has been installed in the data source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01005: failure to compile the generated BPEL classes for BPEL process "{0}" of composite "{1}"

Cause: The class path setting is incorrect.

Action: Ensure that the class path is set correctly. If this happens on the server side, verify that the custom classes or jars which this BPEL process is depending on are deployed correctly. Also verify that the run time is using the same release/version.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01007: build directory "{0}" for the BPEL process "{1}" of composite "{2}" cannot be found or accessed

Cause: The compiler could not find or create the directory "{0}".

Action: Ensure that the parent directory of "{0}" is a valid directory and that it is not read-only.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01010: failure to generate the BPEL process file "{0}".

Cause: Could not generate named BPEL process file. The exception reported was "{1}".

Action: Ensure that the file "{0}" is a valid file to be generated.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-01027: trying to manipulate the nonexistent part "{1}" in a message of type "{0}"

Cause: An invalid request was made to manipulate the invalid part "{1}".

Action: Ensure that the client request is correct.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01028: cannot find propertyAlias definition that associates the BPEL correlation "{0}" of correlationSet "{1}" to messageType "{2}"

Cause: A propertyAlias must be defined to associate the BPEL correlation to a correlationSet. The run time could not find it.

Action: Ensure that the mentioned propertyAlias is in one of the WSDL files that are referenced by the composite. Redeploy the composite.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01029: cannot find property definition for "{0}" in any of the WSDL files

Cause: The BPEL correlation property needs to be defined. But the run time could not find it.

Action: Define the mentioned BPEL property in one of the WSDL files referenced by the composite.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01030: cannot generate debug model file "{0}"

Cause: The named BPEL debug model file was not generated. The exception reported was: "{1}".

Action: Correct the error reported by the error message.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01032: specified process ID "{0}" is invalid

Cause: The specified process identifier did not follow the naming constraints.

Action: Valid process identifiers might start with a letter, a '$' or '_' character; process characters (other than the first character) include a letter, a digit, a '$', a '_' or '-' character. The max length permitted is 100. Ensure that the component name specified in the composite descriptor conforms to the above mentioned constraints.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02000: The class "{0}" for the block element "{1}" does not implement the ICubeBlock interface.

Cause: This was an internal error. All block elements contained within the process domain must implement this interface.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02001: error while attempting to instantiate the class "{1}" for the block element "{0}"; exception reported is: {2}

Cause: This was an internal error. The block class "{0}" was not in the composite class path, or there was an incompatibility with the JDK used to the compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02002: block element "{0}" missing its class name; this element cannot be created without its class name

Cause: This was an internal error. The block element class "{0}" was not in the composite class path.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02003: A Cube element is missing its "ID" property. Every Cube element in the process domain is uniquely identified by its "ID" property.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02005: The parent block element "{0}" specified by node or block element "{1}" is not defined in the service class map. All nodes or blocks contained in the map must be bound to a valid parent block element.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02006: The node or block element "{0}" is missing a parent block identifier. All nodes or blocks contained in the service class map must be bound to a parent block element.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02007: Multiple method block elements are specified in the service class map. A valid map can only contain one method block element.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02008: No block elements are specified in the service class map. All valid maps must contain at least one block element (the root block).

Cause: This was an internal error. The block map was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02009: No node elements are specified in the service class map. All valid maps must contain at least one node element.

Cause: This was an internal error. The block map was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02010: No method block element is specified for the service class map. All valid maps must contain one method block element.

Cause: This was an internal error. The block map was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02011: The class "{0}" for the node element "{1}" does not implement the ICubeNode interface.

Cause: This was an internal error. All node elements contained within the process domain must implement this interface.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02012: error while attempting to instantiate the class "{1}" for the node element "{0}"; the exception reported is: {2}

Cause: This was an internal error. The node class "{0}" was not in the composite class path or there was an incompatibility with the JDK used to the compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02013: The class "{0}" cannot be found in the current class path.

Cause: This was an internal error. The node element class "{0}" was not in the composite class path.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02014: The node element "{0}" is missing its class name; this element cannot be created without its class name.

Cause: This was an internal error. The node class name should be generated by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02015: The BPEL process "{0}" (revision "{1}") has been compiled with an older version of SCAC; current BPEL process domain cannot execute this process.

Cause: An attempt to deploy a process that was compiled with an older version of SCAC failed.

Action: Recompile the BPEL process using the SCAC tool bundled with the current process domain.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02016: The process "{0}" is not initializing because of the error: "{1}".

Cause: This error contained the exceptions thrown by the underlying process loading module.

Action: Check for possible cause in the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02017: cannot compress the data stream with GZIP algorithm; exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying compression layer.

Action: Check for possible cause in the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02018: cannot uncompress the data stream with GZIP algorithm; exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying compression layer.

Action: Please enable DEBUG log level for logger oracle.soa.bpel.engine.data. Please check for message "Byte value passed is:" and exception stack trace in soa server diagnostic log and provide this information to Oracle Support
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02019: cannot compute the md5 checksum; exception reported is: {0}

Cause: This error contained exceptions thrown by the underlying digest layer.

Action: Check for possible cause in the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02020: failure to serialize the audit trail for instance "{0}" to its binary representation; exception reported is: {1}

Cause: This was an internal error. This error contained the exceptions thrown by the underlying XML marshalling module.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02022: The value "{0}" for the tag "{1}" in the XML serialized text for the audit trail for instance "{2}" is not a numeric value.

Cause: The tag "{1}" did not contain a numeric value.

Action: Ensure that the value for tag "{1}" conforms to the expected numeric format.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02023: failure to activate the block "{0}" for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02024: failure to invoke the method "until" on the block "{0}" for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02025: failure of the block "{0}" to handle a business exception for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02026: failure to invoke the canActivate method on the block "{0}" for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02027: failure to deserialize the instance "{0}" from binary format; exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02028: failure to serialize the instance "{0}" to binary format; exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02029: The process domain cannot create the bean "{0}"; this bean is responsible for generating a unique key for a new instance. The exception reported is: "{1}".

Cause: The SOA application or class path was not configured correctly.

Action: Verify that the instance key generator bean has been properly deployed to the server and can be properly mounted from a java class.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02030: failure to marshall the instance "{0}" to XML format; exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02031: The instance "{0}" is created from the domain "{1}"; the current domain is "{2}". A process can be loaded only from the domain from which it was created.

Cause: The instance was not accessed because it was created in a different domain.

Action: If this instance is being accessed from the API, try looking up the instance "{0}" from the "{1}" domain (change the domain ID parameter to the Locator initializer).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02032: The instance "{0}" is created with process guid "{1}"; the current guid for the process "{2}" (revision "{3}") is "{4}".

Cause: Whenever a process is deployed on top of an existing process with the same process ID and revision tag, all instances created from the previous process are marked as stale.

Action: If this instance is being accessed from the console, the browser may be referring to an out-of-date page; click the Instances tab to get the current list of active instances.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02033: failure to construct a valid instance key from the string "{0}"; exception reported is: {2}

Cause: The instance did not consist of a single integer value.

Action: If the instance key has not been constructed by the process domain, ensure that the key format is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02037: exception while trying to create a context object; the exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying JNDI environment.

Action: Verify that the directory service on the application server has been configured correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02038: The process domain is unable to look up the context object using the bind name "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying JNDI environment.

Action: Verify that the JNDI identifier is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02040: exception while trying to destroy a context object; the exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying JNDI environment.

Action: Verify that the directory service on the application server has been configured correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02041: The action "{0}" cannot be performed on the instance "{1}" because of its current state ("{2}").

Cause: The current instance state did not allow the requested action to be performed.

Action: Consult the product documentation for a list of all the permissible actions that can be performed on an instance when it is in the "{2}" state.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02042: The action "{0}" cannot be performed on the work item "{1}" because of its current state ("{2}").

Cause: The current work item state did not allow the requested action to be performed.

Action: Consult the product documentation for a list of all the permissible actions that can be performed on a work item when it is in the "{2}" state.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02043: The action "{0}" cannot be performed on the scope "{1}" because of its current state ("{2}").

Cause: The current scope state did not allow the requested action to be performed.

Action: Consult the product documentation for a list of all the permissible actions that can be performed on a scope when it is in the "{2}" state.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02044: The process domain is failing to write the audit trail for instance "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying persistence framework.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02046: The process domain is failing to write the debug trace for instance "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization layer.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02047: The process domain is failing to write the instance trace for instance "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization layer.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02048: The process domain is unable to handle the work item "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying process execution layer.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02050: The invocation for method "{0}" on the instance "{1}", process "{2}" (revision "{3}") is cancelled. The return value for this method cannot be determined in this case.

Cause: The instance "{1}" was cancelled or aborted.

Action: Check the audit trail for instance "{1}" for more information.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02051: The invocation for method "{0}" on the instance "{1}", process "{2}" (revision "{3}") is not complete. The return value for this method cannot be fetched until the method has completed.

Cause: The instance "{1}" was not complete yet.

Action: Resubmit this request after several minutes. Note that the method may contain some asynchronous interactions that could take an indeterminate amount of time to complete.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02052: The BPEL domain "{0}" is missing.

Cause: The BPEL domain "{0}" may not have initialized properly.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02053: The BPEL domain "{0}" is not finished initializing yet.

Cause: The domain initialization procedure was not finished yet.

Action: Resubmit the request in few minutes. The initialization progress can be monitored in the server log; set the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02054: The BPEL domain "{0}" is currently uninitializing; the domain may not be accessed.

Cause: The domain was uninitializing.

Action: Restart the application server. If the domain uninitialized due to an exception, check the server log for the underlying exception trace (be sure to set the logging level to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02055: failure to handle a fault thrown from a scope, by any blocks in the scope chain

Cause: This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope.

Action: A top-level fault handler should be added to the flow to handle faults not caught from within the flow.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02057: The block element "{0}" is not defined in the service class map.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02058: The node element "{0}" is not defined in the service class map.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02059: The process domain is unable to fetch the work item "{0}" from the memory repository.

Cause: This was an internal error. The work item was not correctly registered from the previous transaction.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02060: failure to activate the node "{0}" for the instance "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying routing subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02061: failure to finalize the node "{0}" for the work item "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying routing subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02062: failure to invoke the canActivate method on the node "{0}" for the instance "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying routing subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02063: failure to deserialize the delivery callback messages for conversation "{0}", message "{1}" from the binary format; the exception reported is: {2}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02064: failure to serialize the delivery callback messages for conversation "{0}", message "{1}" to the binary format; the exception reported is: {2}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02065: failure to serialize the delivery properties for conversation "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02066: failure to deserialize the delivery properties for conversation "{0}" from the binary format; the exception reported is: {1}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02067: failure to marshall the delivery callback messages for conversation "{0}", message "{1}" to XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02068: Failure to call method "{0}" of the delivery persistence service with parameter "{1}". This operation is not supported.

Cause: This was an internal error. Delivery persistence service does not support advanced persistence features such as lazy loading. The persistence manager should not have used those related operations.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02069: The delivery service fails to load the message content from the data store; the exception reported is: {0}

Cause: This was an internal error. Either the load() method was not working properly if the object type was imported into the process, or the delivery message content might have been edited manually in the data store.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02070: The delivery service fails to store the object "{0}" of type "{1}" to the data source. The exception reported is: {2}

Cause: This was an internal error. The save() method was not working properly if the object type was imported into the process.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02071: failure to copy the object "{0}" of type "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02072: failure to release the moniker "{0}"; the exception reported is: {1}

Cause: An attempt was made to remove the last reference to a moniker before the object referred to by the moniker had been loaded.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02073: failure to delete the object "{0}" of type "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02074: The target element with ID "{0}" cannot be located in the current XML document. The node "{1}" has a reference link to this element.

Cause: The document was corrupt; it might have been edited manually.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02075: The element "{0}" does not have an "xsi:type" attribute specifying the schema type of the underlying Java object. An XML fragment cannot be properly unmarshalled to its Java representation without this information.

Cause: The document was corrupt; it might have been edited manually.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02076: failure to deserialize an object from its moniker format; the exception reported is: {0}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the deserialization failure.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02077: Assertion failure: object "{0}" has negative reference count "{1}".

Cause: This was an internal error. An object had a reference count less than zero because it fell out of scope and had its reference count decremented.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02078: failure to marshall the object "{0}" of type "{1}" to XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02079: failure to prepare the object "{0}" of type "{1}" for marshalling; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02080: failure to prepare the object "{0}" of type "{1}" for saving; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02081: failure to read an object''s moniker from the deserializer stream; the exception reported is: {0}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02082: failure to save the object "{0}" of type "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02083: failure to unmarshall the object "{0}" of type "{1}" from XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02084: failure to write an object''s moniker into the serializer stream; the exception reported is: {0}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02085: The metadata for object "{0}" is not registered with the persistence service.

Cause: This was an internal error. Every Java object type in the scope must be registered.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02086: The metadata for object "{0}" does not contain an embedded moniker.

Cause: This was an internal error. One or more of the linked variants in the scope did not contain an embedded moniker that contained the actual bytes defining the object.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02087: The node "{0}" is missing its reference identifier.

Cause: This was an internal error. Any element with an "href" attribute did not contain a non-empty reference ID that could be resolved to another element in the document.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02088: An instance's root scope cannot be routed.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02089: failure to construct a valid scope activation key from the string "{0}".

Cause: The expected format was: "param1-param2", where the two parameters were: instance ID (integer) and scope ID (string) respectively.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02090: failure to unmarshall the metadata for the scope tree of instance "{0}"; the exception reported is: {1}

Cause: This was an internal error. A variant's metadata did not contain "guid", "class name" and "ref-count" attributes; or the "ref-count" attribute was not an integral value while it should be.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02091: failure to release an instance's root scope from the scope tree.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02092: failure to unmarshall a scope for the instance "{0}" from an XML document; the exception reported is: {1}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02093: The tag "{0}" is missing from the serialized XML text for the scope data for the instance "{1}".

Cause: This was an internal error. The XML document for this instance did not contain a value for the tag named in the error message.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02094: The scope "{0}" is not defined for cikey {1}.

Cause: This was an internal error. The scope was either closed or released, and it was not reachable.

Action: Please enable debug log level for logger oracle.soa.bpel.engine.delivery and provide soa diagnostics logs
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02095: The scope associated with the block element "{0}" is not defined in the current instance.

Cause: This was an internal error. The scope metadata was corrupt.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02096: The value "{0}" for the tag "{1}" in the serialized XML text for instance "{2}" is not a parseable integral value.

Cause: This was an internal error. The value for tag named in the error message did not conform to the expected format.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02097: cannot read the XML model file for process "{0}" (revision "{1}"); the exception reported is: {2}

Cause: An exception was thrown by the underlying operating system.

Action: Verify that the BPEL archive for the process named in the error message (for the cited revision) has been deployed correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02100: cannot find the content file "{0}" for process "{1}" (revision "{2}").

Cause: The content file named in the error message might not have been deployed with the process named in the error message.

Action: Verify that the path named in the error message is correct, and that it refers to a file that has been included as a part of the deployment archive.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02101: cannot read the content file "{0}" for process "{1}" (revision "{2}"); the exception reported is: {3}

Cause: The content file named in the error message might not have been deployed with the process named in the erorr message.

Action: Verify that the path named in the error message is correct, and that it refers to a file that has been included as a part of the deployment archive.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02102: Method "{0}" is missing.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02103: The map for node element "{0}" is not defined in the process class.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02104: New instances cannot be created when the process "{0}" is not active; existing instances are permitted to complete as usual.

Cause: The process named in the error message was not active and therefore could not create new instances.

Action: The process life cycle can be changed to active through the EM console.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02106: The process "{0}" has not been turned on. No operations can be performed on the process or any instance belonging to the process if the process is turned off.

Cause: The process named in the error message was not turned on; therefore it did not process any requests.

Action: Consult the administrator if this process has not been turned on.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02107: The process domain is unable to fetch the scope activation message with key "{0}" from the data source.

Cause: The scope activation message with the key named in the error message was not found in the data source.

Action: This row may have been manually removed from the data source; in which case the instance should be aborted.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02108: cannot create a copy of the scope "{0}"

Cause: This was an internal error. Scopes are not cloneable.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02109: The process domain is unable to deserialize the scope data for instance "{0}" from its binary representation; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02110: failure to marshall the scope data for instance "{0}" into XML; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02111: failure to serialize the scope data for instance "{0}" into a binary byte stream; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02112: The absolute scope ID "{0}" does not conform to the expected format for a scope identifier.

Cause: This was an internal error. The expected scope ID format is (block id + relative scope id).

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02113: failure to fetch the return or header value from the root scope.

Cause: This was an internal error. Only top-level scopes can contain return or header values.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02114: The requested variant "{0}" is not a primitive variant type. Reference variants cannot be cast to a primitive type.

Cause: This was an internal error. The code accessing the variant named in the error message was assuming that that variant was a reference variant.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02115: The requested variant "{0}" is not a reference variant type. Primitive variants cannot be cast to a reference type.

Cause: This was an internal error. The code accessing the variant named in the error message was assuming that that variant was a primitive variant.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02116: The variant object associated with key "{0}" in the scope tree is neither a primitive nor a reference variant.

Cause: This was an internal error. The type of the declared variant "{0}" in the scope tree is not contained in the list of supported types (serializable and deserializable), including primitive (all Java primitive types) and reference (java.lang.String, java.util.Date, BPEL documents, EJB entity beans and one-dimensional arrays of any primitive or reference type).

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02117: A variable with key "{0}" is already declared in the current scope.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02118: The variable "{0}" is not declared in the current scope. All variables must be declared in the scope before being accessed. Component DN is "{1}" and corresponding Instance Id is {2}

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Please provide component definition of "{1}" and audit trail of instance id {2} using enterprise manager console.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02121: failure to marshall the object "{0}" of class "{1}" to XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the marshalling failure.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02122: The type class "{0}" is missing a "{1}" tag.

Cause: The XML fragment for this type was missing a required tag; the XML document might have been edited manually.

Action: Set the logging level to debug mode. Check the log for the any exception related to the type class.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02123: The value "{0}" of the tag "{1}" in the serialized XML text for the type class "{2}" is not a parseable integral value.

Cause: The value for the tag named in the error message did not conform to the expected format.

Action: Set the logging level to debug mode. Check the log for the any exception related to the type class.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02124: failure to deserialize the work item "{0}" from the binary format; the exception reported is: {1}

Cause: This error contained the exceptions thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02125: failure to serialize the work item "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02126: failure to deserialize the work items for instance "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02127: failure to serialize the work items for instance "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02128: failure to marshall the work item "{0}" to the XML format; the exception reported is: {1}

Cause: An exception was thrown from the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02129: cannot construct a valid work item key from the string "{0}"

Cause: The string was of wrong format to construct a valid work item key. The expected key format is: "param1-param2-param3-param4", where the parameters are: instance ID (integer), node ID (string), scope ID (string) and count ID (integer) respectively.

Action: If the work item key string has not been constructed by the process domain, ensure that the key format is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02130: The tag "{0}" is missing from the serialized XML text for work item "{1}".

Cause: The XML document for this instance was missing a value for the tag named in the error message.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02131: The activity "{0}" is throwing a null exception.

Cause: This was an internal error. Exceptions thrown from the activity cannot be null.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02132: The value "{0}" for the tag "{1}" in the serialized XML text for work item "{2}" is not a parseable integral value.

Cause: The value for tag "{1}" was not an integer.

Action: If the work item XML has not been constructed by the process domain, ensure that the XML format is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02133: error while attempting to expire the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02134: error while attempting to extend the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02135: error while attempting to execute the manage method on the work manager for node "{0}"; the exception reported is: "{1}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the node.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02136: error while attempting to resume the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02137: error while attempting to suspend the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02138: The method invocation "{0}" is returning an invalid number of callback arguments.

Cause: This was an internal error. More than one return value was returned. Currently, a maximum of one return value is permitted from a method invocation; the actual number of values returned for this invocation was "{1}".

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02139: The method invocation "{0}" is throwing an invalid exception object.

Cause: This was an internal error. The exception object did not extend the Throwable class. The object thrown was of class "{1}".

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02140: failure to invoke the method "{0}" on the performer "{1}"; the exception reported is: "{2}"

Cause: An exception was thrown while performing a callback to an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the performer.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02141: error while attempting to execute the cancelPerform method on the work performer for node "{0}"; the exception reported is: "{1}"

Cause: An exception was thrown while canceling an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the node.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02142: error while attempting to execute the perform method on the work performer for node "{0}"; the exception reported is: "{1}"

Cause: An exception was thrown while executing an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the node.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02143: error while attempting to throw the exception "{0}" from the activity "{1}"; the exception reported is: "{2}"

Cause: An exception is thrown while throwing an exception from an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the activity.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02149: The instance identifier "{0}" is missing its domain ID; this ID specifies the BPEL domain from which the instance is generated.

Cause: This was an internal error. The instance domain ID was not set upon creation and rehydration.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02150: The process domain is unable to fetch the activity "{0}" from the data source.

Cause: The activity key "{0}" did not refer to a valid activity, or the activity was removed from the data source.

Action: Check the work_item database table with the activity key; if the referred row cannot be found, check the audit trail for the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02151: More than one activity from domain "{1}" is returned when querying with the key "{0}".

Cause: Multiple activities were bound to the custom key "{0}". Only one activity should be returned per key.

Action: If the key is a user-specified custom key, ensure that the key is unique.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02152: The process domain is unable to fetch the instance with key "{0}" from the data source.

Cause: The instance key "{0}" did not refer to a valid instance, or the instance was removed from the data source (this might have been the case if the BPEL global transaction was modified by an external source).

Action: Check the cube_instance database table with the instance key; if the referred row cannot be found, check the server logs for traces related to this instance key. You could run select count(*) from cube_instance where cikey = {0}; on soainfra schema; If this query does not return any result, cube instance was not saved due to some error, most likely because of rollback of transaction. Please check soa server logs for any exception/error prior to this error. If query returns one row, the error could be some temporary error or race condition which can only be analyzed by Oracle Support.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02154: Multiple instances are returned when querying with the key "{0}", while only one instance is expected.

Cause: Multiple instances of a business process were created with the key "{0}". Each instance should be uniquely identified by a key.

Action: If the key is a user-specified custom key, ensure that the key is unique.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02155: The process domain is unable to fetch the bytes for the business document "{0}" from the data source.

Cause: The document key "{0}" did not refer to a valid document, or the document was removed from the data source.

Action: Check the xml_document database table with the document key; if the referred row cannot be found, check the server logs for traces related to this document key.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02156: The process domain is unable to fetch the scope context data for the instance with key "{0}" from the data source.

Cause: The instance key "{0}" did not refer to a valid instance, or the instance was removed from the data source.

Action: Check the cube_scope database table with the instance key; if the referred row cannot be found, check the server logs for traces related to this instance key.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02157: failure to read the audit trail for instance "{0}"; the exception reported is: {1}

Cause: An exception was thrown while writing the audit trail bytes to the in-memory buffer after those bytes were read from the data store.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace related to this in-memory buffer writing problem.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02158: failure to create the scope deserializer object for instance "{0}"; the exception reported is: {1}

Cause: An exception was thrown while creating a deserializer from the scope bytes.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace related to this deserializer creation problem.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02159: The process domain is unable to fetch the invocation content for the message "{0}" from the data source.

Cause: The message key "{0}" did not refer to a valid invocation message, or the invocation message was removed from the data source (this might have been the case if the BPEL global transaction was modified by an external source).

Action: Check the invoke_message database table with the message key; if the referred row cannot be found, check the server logs for traces related to this message key.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02160: The process domain is unable to fetch the callback content for the message "{0}" from the data source.

Cause: The message key "{0}" did not refer to a valid callback message, or the callback message was removed from the data source (this might have been the case if the BPEL global transaction was modified by an external source).

Action: Check the dlv_message database table with the message key; if the referred row cannot be found, check the server logs for traces related to this message key.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02161: The process domain is unable to fetch the audit detail bytes for the instance "{0}", detail ID "{1}" from the data store.

Cause: The instance identifier "{0}" or detail identifier "{1}", or both, did not refer to a valid entry in the audit_details table; this row might have been manually removed from the table.

Action: Check the audit_details database table with the identifiers named in the error message; if the referred row cannot be found, check the server logs for traces related to these identifiers.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02162: The instance index "{0}" is not within the valid range.

Cause: The index "{0}" for instance "{1}" was out of range.

Action: Change the index value in the xpath function or the facade API call to conform to the valid index range. Try a value between 1 and {2} (inclusive).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02163: cannot access scope "{0}"; scope is already released

Cause: This was an internal error. An attempt was made to access a scope that has already been released.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02164: An unknown cache policy "{0}" is specified for property "{1}".

Cause: The cache policy "{0}" was not recognized. The list of valid cache policies is { lru, auto, soft-filo, soft-lru, hybrid }.

Action: Change the cache policy configuration property to one of the recognized values. The valid cache policies are lru, auto, soft-filo, soft-lru, and hybrid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02165: cannot initialize connection pool for connection factory "{0}"; the reason is {1}

Cause: An exception was thrown while initializing the JMS connection pool.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02166: failure to finalize the compensation node "{0}" for the second time; the exception reported is: {1}

Cause: An exception was thrown while attempting to execute a compensation activity.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02167: The process ("{1}", revision "{2}") for instance "{0}" is not loaded by the domain; the instance is marked as stale.

Cause: The archive for process "{1}" of revision "{2}" might have been deleted from the domain manually. In this case, the domain would not have been able to mark all instances that belonged to the process as being stale.

Action: Check if the process has been manually deleted from the domain.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02168: A problem occurs while reading the sensor file "{0}"; the exception reported is: {1}

Cause: An exception was thrown while trying to access the sensor file named in the error message.

Action: Ensure that the file exists. If it has been manually deleted, then redeploy the process.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02169: A problem occurs while reading the sensor action file "{0}"; the exception reported is: {1}

Cause: An exception was thrown while trying to access the sensor action file named in the error message.

Action: Ensure that the file exists. If the file has been manually deleted, then redeploy the process.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02171: A problem occurs while updating the label status "{0}" in instance "{1}".

Cause: This label was not detected during process compilation.

Action: Redeploy the process and try again. If the redeployment step does not work, then contact Oracle Support Services. Provide the error message, the composite source, and the exception trace in the server log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02177: failure to create the data source "{0}"; the exception reported is: {1}

Cause: An exception was thrown while attempting to create a data source.

Action: Set the logging level to debug mode, check the log for the underlying exception trace related to this data source creation problem.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02178: the BPEL process "{0}" with revision "{1}" is not loaded.

Cause: The process was not initialized properly, or the process was disabled.

Action: Set the logging level to debug mode, check the log for the underlying exception trace related to this process loading problem.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02180: The current JTA transaction is aborting due to a user rollback fault being thrown.

Cause: This exception was caused by a bpelx:rollback fault being thrown or a ROLLBACK_ONLY FabricInvocationException being thrown. BPEL engine is directed to roll back the current JTA transaction.

Action: There is no action recommended.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02181: The current JTA transaction is marked as rollback-only when performing the activity "{0}".

Cause: The reason was {1}.

Action: Check on the activity which invokes a subprocess or downstream process that results in the JTA transaction being marked as rollback-only.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02182: catching unhandled fault "{0}" when processing instance "{1}" for process "{2}"

Cause: The exception was {3}.

Action: Check the error log file and the audit trail for instance "{1}" for more information. Try to use BPEL fault handlers to catch the faults in the BPEL process "{2}". If this is a system exception, please report this to the system administrator.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02183: bpel engine can not execute activities without an active transaction. please debug the invoked subsystem on why the tranasction is not in active status. the bpel instance id is "{0}".

Cause: The reason was {1}.

Action: Consult the system administrator regarding this error.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02184: The process domain was unable to serialize the activity guide milestone state data for instance "{0}" into a binary byte stream. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown from the underlying serialization sub-system.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02185: The process domain was unable to deserialize the activity guide milestone state data for instance "{0}" from its binary byte representation. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown from the underlying serialization sub-system.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02186: The process domain was unable to fetch the activity guide instance with key "{0}" from the datasource.

Cause: The instance key "{0}" does not refer to a valid activity guide instance, or the instance has been removed from the datasource (this may be case if the BPEL global transaction has been modified by an external source).

Action: Check the "ag_instance" database table; if the row cannot be found, check the server logs.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02187: Failed to load activity guide instance with key "{0}" from the datasource. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown while loading activity guide instance from the datasource.

Action: Please check the log for the underlying exception trace. Be sure to set the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02188: Failed to insert activity guide instance with key "{0}" to the datasource. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown while inserting activity guide instance to the datasource.

Action: Please check the log for the underlying exception trace. Be sure to set the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02189: Failed to update activity guide instance with key "{0}" in the datasource. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown while updating activity guide instance to the datasource.

Action: Please check the log for the underlying exception trace. Be sure to set the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02190: Failed to evaluate expression "{0}" in field "{1}" in activity guide instance with key "{2}". The exception reported is: "{3}"

Cause: The expression may not have been constructed correctly.

Action: Make sure that the expression is constructed correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02191: The activity guide definition at "{0}" could not be read.

Cause: The activity guide definition either is missing or invalid.

Action: Make sure that the activity guide definition is available at the specified URL and that it is a valid XML document.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02192: The activity guide definition at "{0}" does not conform to the activity guide definition XML schema definition. The errors are "{1}"

Cause: The activity guide definition does not conform to the activity guide definition XML schema.

Action: Make sure that the activity guide definition conforms to the activity guide definition XML schema definition.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02193: The activity guide definition at "{0}" could not be validated against the activity guide definition XML schema definition.

Cause: The activity guide definition is missing.

Action: Make sure that the activity guide definition is available at the specified URL and that it is a valid XML document.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02194: The milestone instance with name "{0}" cannot be found in activity guide instance with ciKey "{1}".

Cause: This 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 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 may have been caused by some logical errors in the program.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02197: The "{0}" operation on activity guide instance "{1}" for milestone "{2}" is invalid.

Cause: The milestone's expiration date is not set or milestone is configured to continue post expiration

Action: Please check configuration settings for the milestone "{2}") in BPEL designer.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02198: The current JTA transaction is aborting due to an user rollback fault being thrown. The upstream component should retry in a new JTA transaction upon catching this fault.

Cause: This exception was caused by a global retry fault being thrown from downstream component. The user had directed the BPEL engine to roll back the current JTA transaction and retry within new JTA transactions for the specified number of times and retry interval.

Action: There is no action recommended.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02199: The transaction became inactive when executing activity "{0}" for instance "{1}", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "{2}".

Cause: The reason was {3}.

Action: Consult the system administrator regarding this error.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02200: Master conversation ID is not available in context when executing work item "{0}" in component "{1}".

Cause: Master conversation ID was not supplied by the master process when initiating the call to the detail process.

Action: Make sure the master process's invoke activity to have bpelx:invokeAsDetail and bpelx:detailLabel attributes properly supplied.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02201: The process "{0}" has been suspended. No operations can be performed on the process or any instance belonging to the process if the process is suspended.

Cause: The process is suspended; therefore it did not process any requests.

Action: Consult the administrator if this process has been suspended.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02202: The process domain is unable to create Workitem for the activity "{0}"

Cause: Refer to cause

Action: Refer to cause for an action
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02203: The sub-process named "{0}" cannot be resolved. The sub-process is referred to by the process "{1}"

Cause: The previously resolved sub-process was undeployed while this process was dehydrated.

Action: Consult the system administrator regarding this error. The sub-process needs to be re-deployed.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02205: The sub-process named "{0}" cannot be resolved. The sub-process is referred to by the process "{1}".

Cause: The sub-process is not deployed, or the specified version of the sub-process in not deployed.

Action: Consult the system administrator regarding this error. The sub-process needs to be deployed, or the sub-process caller revised to use a different deployed sub-process.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02206: Model.xml file not found for component "{0}"

Cause: Model.xml file was not generated for the component

Action: If component is BPEL 2.0, Model.xml file is not needed and thus does not get generated and this error is expected
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02207: Transaction associated with bpel.config.transaction=notSupported setting.

Cause: Transaction was associated with business flow that was executing with bpel.config.transaction=notSupported configuration setting.

Action: Please enable application server transaction logs and BPEL engine logs and provide logs to Oracle Support for further analysis.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03001: The process domain is unable to determine the database type. The version table contains the vendor type for the current data source. The exception reported is: {0}

Cause: There was a problem with connecting to the data source where the version information was stored.

Action: Check all of the following to determine the location of the problem with connecting to the data source. Verify that the machine that hosts the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for OraBPEL has been installed in the data source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03002: The server is unable to look up the database schema version.The exception reported is: {0}

Cause: There was a problem with connecting to the data source where the version information is stored.

Action: Check all of the following to determine the location of the problem with connecting to the data source. Verify that the machine that hosts the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for OraBPEL has been installed in the data source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03003: The database schema version {0} from the database does not match the version {1} expected by the server.

Cause: The database schema for the SOA installation was not properly installed, or the installation was using a database schema installed for a prior release.

Action: The database schema currently in place has probably been configured for a previous release. Reinstall the database schema and start the server again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03004: The database table "version" does not contain a data source vendor type

Cause: The database schema may have been modified by hand.

Action: Reinstall the database schema and start the process domain again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03005: The database table "version" does not contain a version guid.

Cause: The database schema may have been modified by hand.

Action: Reinstall the database schema and start the server again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03010: error while trying to instantiate the class {0} as the adapter manifest for {1}, data source {2}, the exception reported is: {3}

Cause: The adapter manifest class named in the error message was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03011: The class {0} (for the adapter manifest for {1}, data source {2}) does not implement the IServerAdaptorManifest interface

Cause: This was an internal error. All adapter manifests registered with the system must conform to the IServerAdaptorManifest interface, and this one does not.

Action: Contact Oracle Support Services. Be sure to provide the error message and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03012: The adapter manifest class name for {0}, data source {1} is not specified

Cause: The adapter manifest class named in the error message was not in the system class path.

Action: Ensure that the Oracle BPEL libraries are set correctly in the system class path. If the libraries are configured correctly, the adapter configuration files might have been modified.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03013: cannot instantiate an instance for the class {0}

Cause: This was an internal error. Java class {0} that must be dehydrated or rehydrated within the OraBPEL server must implement the java.io.Serializable interface. And it must implement a default constructor.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03410: error while trying to instantiate the agent class {0}; The exception reported was: {1}

Cause: The agent class might have relied on a class that was not found in the class path, or it might have relied on a JDK feature that was not compatible with the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03411: invalid agent class

Cause: This was an internal error. The agent class {0} did not implement the IAgent interface. All agents managed by the system must implement this interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03800: The process domain is not able to resolve which correlation set definition to apply to the received callback message for the operation {0}.

Cause: Correlation set definitions were registered with the process domain using operation name and process ID. The callback message was most likely missing the process ID.

Action: If the callback client is external, check that the callback URL contains the process identifier. If the client is another BPEL process, check that the correlation set is defined correctly in the receiving BPEL process.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03801: The received callback message is missing the operation name parameter. The process domain cannot resolve which correlation set definition to apply to the message without this parameter.

Cause: The callback message did not pass the operation name in the SOAP action property.

Action: If the callback client is external, check that the operation name is being passed in the message correctly. If the client is another BPEL process, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03802: The correlation set definition for operation {0}, process {1}, is not registered with the server.

Cause: The correlation set was not defined in the process.

Action: Redeploy the process to the container.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03803: The process domain cannot look up the engine bean; this bean is responsible for processing the callback of a received message. The exception reported is: {0}

Cause: This was an internal error. The SOA installation was not configured properly.

Action: Check that the engine bean has been properly deployed to the server and can be properly mounted from a Java class.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03804: The synchronous polling thread is timing out waiting for a result from instance "{0}".

Cause: The callee was a durable synchronous process that had not reached its reply activity within the allotted timeout period.

Action: There may be a problem completing instance named in the error message. Check the process console for more information.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03805: The process domain is unable to find the protocol handler for the conversation type "{0}".

Cause: This was an internal error. Only the SOAP protocol handler is active by default.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03806: The process domain is unable to process the callback for received message "{0}", for conversation "{1}", and the subscriber "{2}". The exception reported is: {3}

Cause: This error contained exceptions thrown from the underlying callback handler layer.

Action: Check the exception trace in the log (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03810: A similar receive activity is being declared in the same process.

Cause: Another receive activity or equivalent (currently, onMessage branch in a pick activity) has already been enabled with the partnerLink "{0}", operation name "{1}" and correlation set "{2}" (or conversation ID). Appendix A - Standard Faults in the BPEL 1.1 specification specifies a fault should be thrown under these conditions.

Action: Redeploy the process after removing the conflicting receive activities.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03811: No correlation sets are defined for operation "{0}" (process "{1}").

Cause: There were no correlation sets defined for the operation and process named in the error message. All receive operations that do not use WS-Addressing to correlate messages must define at least one correlation set.

Action: Check the BPEL source to ensure that at least one correlationSet is defined for the operation named in the error message.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03812: cannot find the property alias "{0}", message type "{1}"

Cause: The property alias named in the error message was not defined in the BPEL/WSDL source.

Action: Check the BPEL/WSDL source to ensure that the property alias named in the error message has been defined.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03813: failure to evaluate the correlationAlias query "{0}" on the element "{1}".

Cause: The property alias was not defined correctly in the BPEL/WSDL source, or the payload is not as expected.

Action: Check the BPEL/WSDL source to ensure that property alias is defined correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03850: Not able to acquire lock on entity, Db query for update NoWait(QoS is configured DirectWrite), or object lock in Coherence cache(QoS is configured CacheEnabled)

Cause: More than one thread is contending for this entity

Action: rescheduled for auto recovery
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03851: Not able to acquire lock on entity, Db query for update NoWait(QoS is configured DirectWrite), or object lock in Coherence cache(QoS is configured CacheEnabled)

Cause: More than one thread is contending for this entity

Action: rescheduled for auto recovery
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03852: Not able to acquire lock on entity, Db query for update NoWait(QoS is configured DirectWrite), or object lock in Coherence cache(QoS is configured CacheEnabled)

Cause: More than one thread is contending for this entity

Action: rescheduled for auto recovery
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03853: Could not load Database Object of type "{1}" for key "{2}".

Cause: Dispatcher message was pre-maturely scheduled while global transaction had not committed.

Action: Engine will automatically retry. If all engine attempts fail, manual/auto recovery may be required.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04000: The process domain is unable to count the number of instances. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04001: The process domain is unable to count the number of instances for the process "{0}" (revision "{1}"). The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04002: An attempt to fetch the instances using the where condition "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the SQL statement was constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04003: An attempt to fetch the work items using the where condition "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04004: The process domain is unable to insert the current log entries for the instance "{0}" to the audit trail table. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04005: The process domain is unable to insert the current audit trail detail entries for the instance "{0}" to the audit details table. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04006: The process domain is unable to store the work items for the synchronous instance "{0}" to the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04007: The process domain is unable to store the audit trail for the synchronous instance "{0}" to the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04008: Unable to set the auto commit level for the current data source connection. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibit this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04009: unable to commit the current data source transaction; the exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibit this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04010: The process domain is unable to purge the instances from the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04011: The process domain is unable to delete the document "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04012: The process domain is unable to delete all the instances for the process "{0}" (revision "{1}") from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04013: The process domain is unable to fetch a list of the expired work items in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04014: The process domain is unable to look up the type for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04017: The process domain is unable to find the work items for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04018: The process domain is unable to find the audit trail entry for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04019: The process domain is unable to find the work items for the synchronous instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04020: The process domain is unable to find the audit trail for the synchronous instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04025: The process domain is unable to decode the properties for message GUID {0}, which are stored in column {1}; the exception reported is: {2}

Cause: This is an internal error. The properties have not been encoded properly.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-04026: The process domain is unable to find any pending callback messages in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04027: The process domain is unable to find any pending invoke messages in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04028: The process domain is unable to find any pending subscriptions in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04029: The process domain is unable to mark all instances (and activities) with process GUID {0} as stale. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04030: An attempt to fetch the audit details for the instance "{0}" (detail ID {1}) from the data source fails. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04031: An attempt to fetch the audit details for the instance "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04032: The process domain is unable to read the audit detail for detailId "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibit this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04033: The process domain is unable to fetch the document "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04034: The process domain is unable to find the closed instances for the domain "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04035: The process domain is unable to fetch the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04036: The process domain is unable to fetch the scope activation message with key "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04037: The process domain is unable to fetch the work item "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04038: The process domain is unable to update or insert the document "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04039: The process domain is unable to update the key table "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04040: The process domain is unable to update the LOB column "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04041: The process domain is unable to update or insert the instance "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04042: The process domain is unable to update or insert the serialized scope for the instance "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04043: The process domain is unable to delete or insert the scope activation message with key "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04044: The process domain is unable to update or insert the work item "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04045: The process domain is unable to batch update or insert the work items for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04046: The process domain is unable to batch insert a series of synchronous work items into the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04048: The process domain is unable to insert the delivery data for conversation "{0}", subscriber "{1}" in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04049: The process domain is unable to select the delivery data for conversation "{0}" (subscriber "{1}") from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04050: The process domain is unable to select the delivery data for conversation "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04052: The process domain is unable to select the delivery data for subscriber "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04053: The process domain is unable to update the state of the delivery subscription "{1}" for conversation "{0}". The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04054: The process domain is unable to update the state of the delivery subscription "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04055: The process domain {0} is unable to delete handled delivery subscriptions. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04056: The process domain is unable to insert the delivery data for the message {0} and the operation {1} in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04057: The process domain is unable to delete the delivery data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04058: The process domain "{0}" is unable to delete the handled delivery data from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04059: The process domain is unable to select the delivery data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04060: The process domain is unable to select the delivery data for the message {0} and the operation {1} from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04061: The process domain is unable to update the state of the delivery the message {0}. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04062: The process domain is unable to delete the invocation data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04063: The process domain "{0}" is unable to delete the handled invocation data from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04064: The process domain is unable to select the invocation data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04065: The process domain is unable to select the invocation data for the process "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04066: The process domain is unable to insert the invocation data for the message {0} and the operation {1} in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04067: The process domain is unable to update the state of the invocation the message {0}. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04069: The process domain is unable to fetch a list of the stale instances belonging to the process "{0}" (revision "{1}"). The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04076: The process domain is unable to look up the TX data source "{0}".

Cause: The J2EE container was not configured properly; a data source with the expected name has not been created or has been removed.

Action: Verify that the machine hosting the data source is physically connected to the network. In addition, verify that the connection pool properties, as defined in the application server startup properties, are valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04077: The process domain is unable to establish a connection with the data source with the connection URL "{0}". The exception reported is: {1}

Cause: The J2EE container was not configured properly; the connection parameters for the data source might not have been correct.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04078: The process domain is unable to release its data source connection. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the transaction has become corrupt.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04079: cannot read BLOB stream from the data source with key "{0}"; the exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibited this action.

Action: Verify that the machine hosting the data source is physically connected to the network. In addition, verify that the connection pool properties, as defined in the application server startup properties, are valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04080: The data stream for the instance or activity object "{0}" is not found in the data source.

Cause: The data stream with the instance or activity object key named in the error message was not found.

Action: Verify that the instance or activity key named in the error message refers to a valid instance or activity that has been started and not removed from the process domain.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04082: The process domain is unable to delete the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04083: The process domain is unable to insert or update the exception entry for the activity "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04084: The process domain is unable to delete the exception entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04085: The process domain is unable to find the activity in the domain "{0}" with the custom key "{1}". The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04087: failure to find schedulable activities for domain "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04090: The process domain is unable to read the serialized scope for the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04091: The process domain is unable to read the indexes for the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04092: The process domain is unable to update or insert the indexes for the instance "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04099: The process domain is unable to find instances with root ID "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04100: The process domain is unable to find any invoke messages with the specified where condition in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04101: The process domain is unable to find any callback messages with the specified where condition in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04102: The process domain is unable to insert the process event for process "{0}" (revision "{1}") in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04103: The process domain is unable to find any process events with the specified where condition in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04108: The process domain is unable to select the attachment by the key "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04109: The process domain is unable to delete the attachment by the key "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04110: The process domain is unable to insert the attachment into the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04111: The process domain is unable to select the attachment reference "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04112: The process domain is unable to insert the attachment reference into the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04113: The process domain is unable to remove the attachment reference of the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04121: An attempt to fetch the test details using the where condition "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04122: The process domain is unable to insert or update test details for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04123: The process domain is unable to update the state of the following delivery messages "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04124: The process domain is unable to update the state of the following delivery subscriptions "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04125: The process domain is unable to select the number of detail instances for the master instance specified by the conversation ID "{0}".

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04126: The process domain is unable to select document references for the instance ID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04127: The process domain is unable to insert document references for the instance ID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04128: The process domain is unable to select document references for delivery message GUID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04129: The process domain is unable to insert document references for delivery message GUID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04132: cannot read CLOB stream from the data source with the key "{0}"; the exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibited this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Additionally verify that the connection pool properties as defined in the application server startup properties are valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04138: The process domain is unable to store the test definition for process "{0}", revision "{1}", test suite "{2}", location "{3}" in the data source. The exception reported is: {4}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04139: The process domain is unable to delete the test definition for the process "{0}", revision "{1}", test suite "{2}", location "{3}" in the data source. The exception reported is: {4}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04140: The process domain is unable to delete test definitions for the process "{0}", revision "{1}" in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04141: The process domain is unable to delete the events logged for the process "{0}", revision "{1}" from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04142: The process domain is unable to delete the events logged for the domain. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04143: The process domain is unable to insert the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04144: The process domain is unable to update the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04145: The process domain is unable to find the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04146: The process domain is unable to delete the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04147: The process domain was unable to fetch the activity guide instance with key "{0}" from the datastore. The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04148: The process domain was unable to update the activity guide instance with key "{0}" in the datastore. The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource, or the data segment may be full.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04149: The process domain was unable to insert the activity guide instance with key "{0}" to the datastore. The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource, or the data segment may be full.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04150: The process domain was unable to insert the audit counter for instance "{0}". The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04151: The process domain was unable to update the audit counter for the instance "{0}". The exception reported is: {1}

Cause: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Action: There is a problem accessing the SOA datasource, or the data segment may be full.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04152: The process domain was unable to select the audit counter for the instance "{0}" from the datastore. The exception reported is: {1}

Cause: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Action: There is a problem accessing the SOA datasource.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04153: The process domain was unable to select for update on the audit counter for the instance "{0}" from the datastore. The exception reported is: {1}

Cause: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Action: There is a problem accessing the SOA datasource.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04160: Cannot locak invoke message for processing.

Cause: Either Db row is locked by another thread or not enough ITLs required by concurrency is not available

Action: DB tuning may help.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04161: Cannot locak subscription for processing.

Cause: Either Db row is locked by another thread or not enough ITLs required by concurrency is not available

Action: DB tuning may help.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05000: failure to fetch the dispatcher trace for the engine "{0}"; the exception reported is: {1}

Cause: The dispatcher trace XML file was written to an output buffer that was not sized correctly.

Action: Contact Oracle Support Services. Provide the error message and the process that appeared to cause the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05001: The message handler for the class {0} is not registered.

Cause: This was an internal error. It occurred because the dispatcher message handler was not registered in the MessageRegistry class.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05002: error while attempting to process the message "{0}"; the reported exception is: {1}

Cause: This error contained an exception thrown by the message handler.

Action: Contact Oracle Support Services. Please provide the SOA server logs to support. You could also enable debug logs for logger oracle.soa.bpel.engine and reproduce the problem and provide soa server diagnostics logs to Oracle Support. Please be advised that setting logger to debug level may degrade SOA server performance. Please consult Oracle Support before enabling it
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05003: No message local handler is implemented for the message "{0}".

Cause: This was an internal error. It occurred when a remote message was handled locally.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05004: error while sending a batch message to the dispatch queue; the exception reported is: {0}

Cause: There was a problem with enqueuing the message to the JMS queue or the dispatcher EJB could not be found in the JNDI context.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05005: The process domain is unable to send a message to the JMS queue "{0}". The exception reported is: {1}

Cause: There was a problem with enqueuing the message to the JMS queue; the queue configuration might be incorrect.

Action: Verify that the JMS service for the application server has been configured properly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05006: error while scheduling a batch message with the dispatcher; the exception reported is: {0}

Cause: There was a problem finding the dispatcher EJB in the current JNDI context.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05007: there is no active transaction while scheduling a message with the dispatcher

Cause: this usually happens if the underlying subsystem rollback back the transaction without bubbling up the system or transaction exception to the bpel layer

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05213: The process identifier "{0}" for the BPEL process archive "{1}" is not valid.

Cause: The process identifier for the BPEL process archive named in the message was not valid.

Action: Ensure that the deployment descriptor contained in the BPEL process archive named in the error message has a valid process ID. Process identifiers might start with a letter, a dollar sign ($) or an underscore (_); process characters (other than the first character) include a letter, a number, a dollar sign ($), an underscore (_) or a hyphen (-).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05214: The process revision tag "{0}" for the BPEL process archive "{1}" is not valid.

Cause: The process revision tag for the BPEL process archive named in the message was not valid.

Action: Ensure that the deployment descriptor contained in the BPEL process archive named in the error message has a valid revision tag. Valid revision tags may contain the following characters: a letter, a number, a dollar sign ($), an underscore (_), a hyphen (-), or a period (.).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05215: The process domain is encountering the following errors while loading the process "{0}" (composite "{1}"): {2}.

Cause: This error contained an exception thrown by the underlying process loader module.

Action: Check the exception trace in the log (with logging level set to debug mode). If there is a patch installed on the server, verify that the bpelcClasspath domain property includes the patch classes.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05216: The class {0} for the process "{1}" (revision "{2}") does not implement the ICubeProcess interface.

Cause: The current BPEL component named in the error message was probably compiled with an older version of SCAC. All process classes contained within the process domain must implement this interface.

Action: Recompile the SOA composite again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05217: error while attempting to instantiate the class {0} for the process "{1}" (revision "{2}"); the exception reported was: {3}

Cause: This error contained an exception thrown by the underlying process loader module.

Action: Verify the exception trace in the log (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05222: cannot find class for type {0}

Cause: This was an internal error. The persistence manager for the type named in the error message could not be found in the class path. All required persistence managers should be registered by default.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05225: The persistence manager class {0} for the type {1} does not implement the IPersistenceManager interface.

Cause: This was an internal error. All persistence managers registered with the system must conform to the IPersistenceManager interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05226: error while attempting to instantiate the persistence manager class {0} for type {1}; the exception reported was: {2}

Cause: The persistence manager class named in the error message was not in the system class path or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05243: failure to obtain load lock for process "{0}"; the exception reported is: {1}

Cause: The lock timeout was too small for the current load or there was a large number of process modification requests.

Action: The default timeout is 120 seconds. If this is not sufficient, customize the value using the JVM system property orabpel.process.lock.timeout, which is added to the JVM start line.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05244: failure to obtain load lock for process "{0}"; timed out after {1} seconds.

Cause: The lock timeout was too small for the current load or there was a large number of process modification requests.

Action: The default timeout is 120 seconds. If this is not sufficient, customize the value using the JVM system property orabpel.process.lock.timeout, which is added to the JVM start line.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05250: error while attempting to deploy the BPEL component file "{0}"; the exception reported is: {1}

Cause: This error contained an exception thrown by the underlying deployment module.

Action: Please enable debug level for logger oracle.soa.bpel.engine.deployment and retry to deploy and provide soa server diagnostics logs to Oracle Support.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05252: The bpel container could not find persistence manager {0} for type {1} in the classpath

Cause: During dehydration the bpel container would serialize all the objects in the scope, each object in the scope should have a persistence manager registered or available in the classpath, otherwise bpel container would not know how to serialize the object for the dehydration store.

Action: Please make sure the persistence manager {0} for type {1} is available in classpath. please refer the documentation on how to write a persistence manager.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05253: Cannot re-deploy a durable process "{0}" with keepInstancesOnRedeploy=true.

Cause: A durable BPEL process cannot be deployed when the flag keepInstancesOnRedeploy is set to "true".

Action: Remove the keepInstancesOnRedeploy flag and try again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05254: Cannot re-deploy process "{0}", error during checksum calculation due to "{1}"

Cause: Error during checksum calculation

Action: Please Contact Oracle Support Services. Provide the error message and the exception trace in the log files
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-08015: cannot find operation {0} of portType {1} in the WSDLs of composite "{2}

Cause: In the composite named in the error message, either the WSDL that defined portType named in the error message was changed, or there were multiple definitions of the same portType.

Action: Ensure that there is only one definition of portType named in the error message and redeploy the composite.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09004: cannot convert the object of the class {0} to XML text

Cause: The object of the class named in the error message was not converted to XML text because of the exception: {1}

Action: Ensure that a valid marshaller is registered for the class named in the error message and refer to the BPEL developer guide about how to create a marshaller for a JAVA type.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09006: A mismatch of a schema-generated object version cannot be used in the system.

Cause: Either the XML schema class {0} has been compiled with an older version of SCHEMAC, or the BPEL process domain to which the class is deployed could not use the helper classes that were generated for this class.

Action: Recompile XML schema using the SCHEMAC tool that is bundled with the current process domain.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09007: error while attempting to instantiate the XML marshaller class {0}

Cause: The exception reported was: {1}

Action: Ensure that marshaller is defined, and that it is available in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09008: error while marshalling the object to XML

Cause: The class {0} did not implement the com.collaxa.cube.engine.xml.IMarshaller interface.

Action: Ensure that the marshaller class {0} implements the correct interface. All XML marshallers used in the BPEL must implement this interface.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09009: The BPEL service engine is not able to instantiate the schema registry.

Cause: The class {0} (for the run-time schema registry) did not implement the ISchemaRegistry interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09010: error attempting to create the schema registry class {0}

Cause: This is an internal error. The exception reported was: {1}

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09200: When performing the assign operation, the to node {0} is invalid.

Cause: The node named in the error message was either null or an empty node set, and it was not an instance of org.w3c.Element.

Action: Verify the node value at line number {1} is not null and is an instance of org.w3c.Element.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09204: The result of from-spec is null.

Cause: Either the from node value or the xpath query in the from node value was invalid.

Action: According to BPEL4WS spec 1.1 section 14.3, the from node value should not be empty. Verify the from node value at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09205: The assign activity of the to node query is returning zero node.

Cause: Either the to node data or the xpath query in the to node was invalid.

Action: According to BPEL4WS spec 1.1 section 14.3, verify the to node value at line number {1} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09207: There is an error while parsing the xml data.

Cause: The XML data was not valid; the reason was {0}.

Action: Ensure the XML data is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09219: failure to save the element {0} during dehydration

Cause: This element was not a root element and the scope had reference to this element. The scope should have references only to root element.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09221: failure to serialize the element {0} to the binary format during dehydration

Cause: The exception reported was: {1}

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09222: failure to deserialize the document {0} from binary format during dehydration

Cause: The exception reported was: {1}

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09223: The assign activity part and query {0} are returning multiple nodes.

Cause: The assign activity part and query named in the error message returned multiple nodes. It should return single node.

Action: According to BPEL4WS specification 1.1 section 14.3, the assign activity part and query named in the error message should not return multiple nodes. Verify the part and xpath query named in the error message at line number {1} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09224: cannot set a nonelement value to an element-based variable

Cause: An attempt to assign a nonelement value to an element-based variable failed.

Action: Verify the BPEL source for invalid assign activities.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09225: cannot set a nonmessage value to a message-based variable

Cause: An attempt to assign a nonmessage value to a message-based variable failed.

Action: Verify the BPEL source for invalid assign activities.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09226: cannot use a simple type variable in the setVariableData method

Cause: It was not allowed to use simple type variable in setVariableData method.

Action: Verify the BPEL JAVA exec source code for invalid assign activities.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09227: The from-spec for {2} operation must return either an attribute list or an element list.

Cause: The from-spec did not return an attribute list or an element list.

Action: Verify the assign activity for the operation named in the error message at line number {1} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09228: The message part {2} of the WSDL variable {3} is not an XML element; {4} operation cannot be performed.

Cause: The operation named in the error message was not performed because the named message part of the WSDL variable named in the error message was not an XML element.

Action: Verify the message part named in the error message is a valid XML element at line number {1} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09229: The to-spec does not yield any data; the {1} operation cannot be performed.

Cause: The operation named in the error message was not performed because to-spec did not yield any data.

Action: Verify the to-spec of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09230: The parent of the selection result {1} does not exist or is not an XML element; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the parent of the selection result named in the error message did not exist or was not an XML element.

Action: Verify the element of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09231: The selection result at list entry {1} does not have a parent node; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result at the list entry named in the error message did not have a parent node.

Action: Verify the list entry of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09232: The selection result at list entry {1} is not an XML node; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result at the list entry named in the error message was not an XML node.

Action: Verify the list entry of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09233: The selection result at list entry {1} is not an XML element; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result at the list entry named in the error message was not an XML element.

Action: Verify the list entry of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09234: The selection result of {1} is not an XML element; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result named in the error message was not an XML element.

Action: Verify the assign activity at line number {0} in the BPEL source and ensure the run-time data is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09240: failure of the copyList assign operation

Cause: The element list specified by the to-spec used in the copyList operation was not contiguous.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09241: The copyList assign operation fails due to a type mismatch.

Cause: The from-list of copyList was element-based, while the to-list was not element-based.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09242: The copyList assign operation fails due to a type mismatch.

Cause: The from-list of the copyList operation was attribute-based, but the to-list was not attribute-based.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09243: The copyList assign operation fails.

Cause: The element returned from the to-list spec of the copyList operation did not have an element parent.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source and ensure that the run-time to-list data is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09244: The copyList assign operation fails.

Cause: The element returned from the to-list spec of the copyList operation did not have a parent node.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source and ensure the run-time to-list data is valid
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09245: The copyList assign operation fails.

Cause: The members of the to-list spec of the copyList operation did not share the same parent node.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source and ensure the run-time to-list data is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09248: cannot instantiate document builder {0}

Cause: The reason was: {1}

Action: Ensure that document builder class named in the error message exists in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09249: error while parsing the XML text {0}

Cause: The XML text was invalid because {1}.

Action: Verify that the XML text is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09250: error while creating the XML document

Cause: The reason was {0}.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09251: cannot perform copy XMLNS for prefix:{0}

Cause: Namespaces conflicted: {1} and {2}

Action: Verify the from element data of the assign operation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09252: cannot perform copy

Cause: The bpelx:copyQName attribute on copy assign element is set to "yes", but the result of the from-spec is not a QName.

Action: Verify the from-spec of the assign operation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09500: An error occurs while processing the XPath expression; the expression is {0}

Cause: The XPath expression failed to execute; the reason was: {1}

Action: Check the detailed root cause described in the exception message text and verify that the XPath query is correct.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09501: An error occurs while registering the XPath function {0}

Cause: Registering the XPath function failed; the reason was: {1}

Action: Check the detailed root cause described in the exception message text and verify that the XPath function named in the error message is defined in the domain property file.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09502: The syntax error occurs while parsing XPath expression {0}, at position {2}

Cause: The XPath query syntax was wrong; the exception 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-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-09510: {0} expression: "{1}" has invalid syntax.

Cause: The {0} expression is invalid because: {2}

Action: Check the syntax of the {0} expression.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09511: {0} expression: "{1}" executed with an exception.

Cause: The {0} expression most likely did not execute correctly because: {2}

Action: Check the source of the {0} expression and the assumptions that are made in the process.
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

ORABPEL-22001: An error occurs while analytics process activity execution for activity {0} and event {1}.

Cause: The analytics process activity execution failed.

Action: Examine the log file for the exception of executing an analytics process activity.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-22002: An error occurs while analytics get the activity path information.

Cause: The analytics get activity path failed.

Action: Examine the log file for the exception of getting activity path information.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-22003: 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-22004: 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-22005: An error occurs while analytics pubishes data to BAM.

Cause: The analytics BAM publish failed.

Action: Examine the log file for the exception of publishing analytics data to BAM server.
Level: 1

Type: ERROR

Impact: Programmatic

37 ORACLESTATE-COMMON-00001 to ORACLESTATE-COMMON-00001

ORACLESTATE-COMMON-00001: Unknown Exception

Cause: Some unknown error

Action: None
Level: 1

Type: SEVERE

Impact: WebService

38 ORACLESTATE-INMEMORY-00001 to ORACLESTATE-INMEMORY-00001

ORACLESTATE-INMEMORY-00001: InMemory Physical Store not found: {0}

Cause: A named in-memory physical store was requested, but no physical store with the given name could be found

Action: Make sure persistence configuration is correct.
Level: 1

Type: SEVERE

Impact: WebService

39 ORACLESTATE-INMEMORYRA-00001 to ORACLESTATE-INMEMORYRA-00003

ORACLESTATE-INMEMORYRA-00001: Unknown Xid: {0}

Cause: An unknown Xid was given to the resource adapter by the transaction manager.

Action: None
Level: 1

Type: SEVERE

Impact: WebService

ORACLESTATE-INMEMORYRA-00002: Cannot prepare Xid: {0}

Cause: An Xid was given to the resource adapter prepare method, and we were unable to prepare it for unknown reasons.

Action: None
Level: 1

Type: SEVERE

Impact: WebService

ORACLESTATE-INMEMORYRA-00003: Unsupported flags in XAResource start: {0}

Cause: An unsupported flag value was given to the resource adapter XAResource.start method. Only TMNOFLAGS is supported.

Action: None
Level: 1

Type: SEVERE

Impact: WebService

40 ORAMED-01001 to ORAMED-09001

ORAMED-01001: Error occurred while assigning to target "{0}" using expression "{1}".

Cause: Error occurred while assigning to target "{0}" using expression "{1}".

Action: Check if source message has right values or source expression is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01002: Metadata error occurred while assigning. Check if source and target expression are valid. ["{0}"].

Cause: Metadata error occurred while assigning. Check if source and target expression are valid. ["{0}"].

Action: Modify source or target for valid expression. Empty string, null and invalid expressions are not allowed
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01003: Invalid source used while assigning. Check if source expression is valid. ["{0}"].

Cause: Invalid source used while assigning. Check if source expression is valid. ["{0}"].

Action: Modify source for valid expression.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01004: Source evaluated from expression "{0}" is invalid.

Cause: Source evaluated from expression "{0}" is invalid.

Action: Check the expression for correctness. Modify the source expression based on the requirement, otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01005: Target creation for target expression "{0}" failed.

Cause: Target creation for target expression "{0}" failed.

Action: Check if the target expression is valid, otherwise, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01006: Encountered variable which is not supported or implemented "{0}".

Cause: Encountered variable which is not supported or implemented "{0}".

Action: Check if source and target expression for valid variable like $in, $out, $initial and so forth, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01007: Header variable "{0}" not recognized.

Cause: Header variable "{0}" not recognized.

Action: Header variable should be of the format $in.header.<prefix>_<root-elem>. Fix the header variable.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01008: Property "{0}" not found in "{1}" message.

Cause: Property "{0}" not found in "{1}" message.

Action: Check source and target expression for valid property name otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01009: Failed to assign element "{0}" to element "{1}". Parent node not found.

Cause: Failed to assign element "{0}" to element "{1}". Parent node not found.

Action: Check target expression for valid element associated with proper owner document, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01010: Failed to assign source "{0}" to target part "{1}". Assigning Text data to part is not supported unless target part is available.

Cause: Failed to assign source "{0}" to target part "{1}". Assigning Text data to part is not supported unless target part is available.

Action: Check source and target expression for valid expression, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01011: Failed to assign attachment "{0}" from source to target. Attachment not available in source message.

Cause: Failed to assign attachment "{0}" from source to target. Attachment not available in source message.

Action: Check source expression is valid, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01012: Part "{0}" not found in source message.

Cause: Part "{0}" not found in source message.

Action: Check source and target expression for valid part name otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01013: Encountered dynamic assign which is not supported "{0}".

Cause: Encountered dynamic assign which is not supported "{0}".

Action: Check if source has valid dynamic assign. Otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01014: Encountered assign fragment with type "{0}". Supported are xml and xquery.

Cause: Encountered assign fragment with type "{0}". Supported are xml and xquery.

Action: Check if source has valid assign. Otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01015: Error occurred while evaluating xpath expression "{0}".

Cause: Error occurred while evaluating xpath expression "{0}".

Action: Check if xpath expression is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01101: Error evaluating filter expression.

Cause: Error evaluating filter expression.

Action: Ensure that the filter expression is valid, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01102: Error evaluating filter expression, "{0}". Root-cause: "{1}".

Cause: Error evaluating filter expression, "{0}". Root-cause: "{1}".

Action: Ensure that the filter expression metadata is valid, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01104: Encountered variable which is not supported "{0}".

Cause: Encountered variable which is not supported "{0}".

Action: Check if source has valid variable $in, filter expression is supported only for inbound expression. Otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01105: Encountered dynamic filter which is not supported "{0}".

Cause: Encountered dynamic filter which is not supported "{0}".

Action: Check if source has valid dynamic filter expression. Supported only for inbound expression. Otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01201: Error occurred while transforming payload using "{0}" for target part "{1}".

Cause: Error occurred while transforming payload using "{0}" for target part "{1}".

Action: Review the XSL/XQuery or source payload. Either the XSL/XQuery defined does not match with the payload or payload is invalid.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01202: Fatal error occurred while transforming payload using XSL "{0}" for target part "{1}".

Cause: Fatal error occurred while transforming payload using XSL "{0}" for target part "{1}".

Action: Review the XSL for any syntax error.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01203: No part exists with name "{0}" in source message.

Cause: No part exists with name "{0}" in source message.

Action: Review the transformation definition in mplan. Contact Oracle Support Services if the error cannot be fixed.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01204: Initial source message is not available in the context. Failed evaluating "{0}".

Cause: Initial source message is not available in the context. Failed evaluating "{0}".

Action: Review the transformation/assign definition in mplan. Accessing initial source message is not supported during callback.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01205: Failed to persist streaming attachment for message "{0}".

Cause: Failed to persist streaming attachment for message "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01206: Encountered dynamic transformation which is not supported "{0}".

Cause: Encountered dynamic transformation which is not supported "{0}".

Action: Check if source has valid dynamic transformation. Otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01301: Schematron validation fails with error "{0}".

Cause: Schematron validation fails with error "{0}".

Action: Fix the payload.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01302: Response payload for operation "{0}" is invalid.

Cause: Response payload for operation "{0}" is invalid.

Action: Response received by Mediator was either invalid or null. Examine why the service being invoked by Mediator is returning a null/invalid response. You can also try invoking the service directly and see if it sends back proper response.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01303: XSD schema validation fails with error "{0}".

Cause: XSD schema validation fails with error "{0}".

Action: Fix payload and resubmit.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01304: Schematron validation failure.

Cause: Schematron validation failure.

Action: Fix payload or schematron definition and resubmit.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01305: Group ID validation failure.

Cause: Group ID validation failure.

Action: XPATH Expression returned null Group Id. Check the XPATH expression, fix the payload and resubmit.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01306: Sequence ID validation failure."{0}".

Cause: Sequence ID validation failure."{0}".

Action: SequenceID value is incorrect. Either XPATh Expression returned null or sequenceID value does not fall within the sequence range. Check the XPATH expression, fix the payload and resubmit.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01351: Unable to execute "{0}" method on callout instance of "{1}".

Cause: Unable to execute "{0}" method on callout instance of "{1}".

Action: Check server log for any exceptions. Check if there is an issue in implementation of Java callout class.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01360: Wrong source message type. Neither a NormalizedMessage nor a BusinessEvent, message type class :{1}

Cause: Wrong source message type. Neither a NormalizedMessage nor a BusinessEvent, message type class :{1}

Action: Contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01361: Mediator does not support the Resequencing strategy."{0}"

Cause: Mediator does not support the Resequencing strategy."{0}"

Action: Mediator does not support the Resequencing strategy. Refer to the documentation of resequencer for more details.You can also contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01362: Unexpected runtime error occurred while processing the message.

Cause: Unexpected runtime error occurred while processing the message.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01363: Mediator does not have content to respond to the request-response type operation operation "{0}".

Cause: Mediator does not have content to respond to the request-response type operation operation "{0}".

Action: Examine your design to rectify, or reset the property oracle.soa.mediator.twoway.allowNullReply to true.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02001: This error occurs because of invalid filter expression "{0}".

Cause: This error occurs because of invalid filter expression "{0}".

Action: Review the filter expression and check for possible syntax errors in the filter expression.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02002: Invalid filter metadata "{0}". Either no filter expression specified or expression may be invalid.

Cause: Invalid filter metadata "{0}". Either no filter expression specified or expression may be invalid.

Action: Fix the filter condition metadata.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02051: Invalid callout implementation "{0}".

Cause: Invalid callout implementation "{0}".

Action: Fix the callout implementation.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02101: Cannot load XSL transform into the cache for XSL or XSLT "{0}".

Cause: Cannot load XSL transform into the cache for XSL or XSLT "{0}".

Action: Check XSL file for any syntax error and fix the same.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02102: Invalid part type "{0}".

Cause: Invalid part type "{0}".

Action: Ensure that the parts provided in transformation/xpath are valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02103: Invalid assign expression "{0}".

Cause: Invalid assign expression "{0}".

Action: Check assign xpath expression for any syntax error. If there are any syntax errors, correct the xpath expression.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02201: Could not load schema document into the cache for XSD "{0}". Reason : {1}

Cause: Could not load schema document into the cache for XSD "{0}". Reason : {1}

Action: Check the XSD schema for any syntax error and fix the same.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02202: Invalid part name in metadata for schematron validator "{0}".

Cause: Invalid part name in metadata for schematron validator "{0}".

Action: Fix the schematron metadata.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02203: Could not load schematron file {0}.

Cause: Could not load schematron file {0}.

Action: Provide the correct schematron document.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02204: Could not load wsdl interface for message with component dn "{0}".

Cause: Could not load wsdl interface for message with component dn "{0}".

Action: Fix the component to point to valid wsdl.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02205: Schematron document for schematron file {0} is invalid.

Cause: Schematron document for schematron file {0} is invalid.

Action: Fix the schematron document.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02206: Could not create XSD validator for schema with target namespace "{0}" for message "{1}".

Cause: Could not create XSD validator for schema with target namespace "{0}" for message "{1}".

Action: Check XML schema for any syntax error.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02207: Failed to validate redeployment of mediator.

Cause: Failed to validate redeployment of mediator.

Action: Configure composite properly, otherwise contact Oracle for support.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02208: Component is not valid. Either component/componentDN is null or there is a mismatch between "{0}" and "{1}"

Cause: Component is not valid. Either component/componentDN is null or there is a mismatch between "{0}" and "{1}"

Action: Configure composite properly, otherwise contact Oracle for support.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02209: Failed to fetch mediator from source URI "{0}".

Cause: Failed to fetch mediator from source URI "{0}".

Action: Configure composite properly.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02210: Encountered dynamic schematron which is not valid "{0}".

Cause: Encountered dynamic schematron which is not valid "{0}".

Action: Check if source has valid dynamic schematron validator. Otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02301: Could not load mediator mplan information. Reason : {0}

Cause: Could not load mediator mplan information. Reason : {0}

Action: Check your mediator mplan for any syntax error.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02302: Could not load metadata manager. Reason : {0}.

Cause: Could not load metadata manager. Reason : {0}.

Action: Check your composite configuration.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02303: Composite reference {0} not found for operation {1}.

Cause: Composite reference {0} not found for operation {1}.

Action: Check your composite.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02304: Could not load mediator mplan for componentDN "{0}" . It may be undeployed.

Cause: Could not load mediator mplan for componentDN "{0}" . It may be undeployed.

Action: Using SOA Enterprise Manager, check if composite is deployed. If the composite is not deployed, you can try deploying the composite again.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02305: Could not find mediator case for case name "{0}" . Mediator component may be redeployed with different case names.

Cause: Could not find mediator case for case name "{0}" . Mediator component may be redeployed with different case names.

Action: This message will be put in error state. Fix the mplan by adding the right case and then recover it through EM.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02401: Got invalid response from decision service : {0}

Cause: Got invalid response from decision service : {0}

Action: Ensure that the decision service used by the mediator is configured properly.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02402: Could not invoke decision service : {0}

Cause: Could not invoke decision service : {0}

Action: Ensure that the decision service used by the mediator is configured properly.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02403: Dynamic mplan returned by decision service is invalid. Mplan returned by decision service : {0}

Cause: Dynamic mplan returned by decision service is invalid. Mplan returned by decision service : {0}

Action: Ensure that the decision service used by the mediator is configured properly.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03001: Unable to lock Resequencer Groups for container ID "{0}" and timestamp "{1}".

Cause: Unable to lock Resequencer Groups for container ID "{0}" and timestamp "{1}".

Action: Unable to lock Resequencer Groups. Check your database connection.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03002: Unable to retrieve locked Resequencer Groups for containerId "{0}" and timestamp "{1}".

Cause: Unable to retrieve locked Resequencer Groups for containerId "{0}" and timestamp "{1}".

Action: Unable to retrieve lock Resequencer Groups. Check your database connection.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03003: Unable to store Resequencer Group."{0}".

Cause: Unable to store Resequencer Group."{0}".

Action: Unable to store Resequencer Group. Check your database connection or check data.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03004: Unable to store Resequencer Message."{0}"

Cause: Unable to store Resequencer Message."{0}"

Action: Unable to store Resequencer Message. Check your database connection or check data.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03005: Unable to unlock Resequencer Groups for container ID "{0}" and timestamp "{1}".

Cause: Unable to unlock Resequencer Groups for container ID "{0}" and timestamp "{1}".

Action: Unable to unlock Resequencer Groups. Check your database connection.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03006: Unable to retrieve Resequencer message. "{0}"

Cause: Unable to retrieve Resequencer message. "{0}"

Action: Unable to retrieve Resequencer message. Check your database connection.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03101: Unable to get subscriptions for message "{0}"

Cause: Unable to get subscriptions for message "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03102: Error creating cache for cache policy "{0}". Reason : {1}

Cause: Error creating cache for cache policy "{0}". Reason : {1}

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03103: Cannot load Cache entry with NULL or EMPTY key.

Cause: Cannot load Cache entry with NULL or EMPTY key.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03104: Do not cache RuntimeESBSystem object for NULL or EMPTY system GUID.

Cause: Do not cache RuntimeESBSystem object for NULL or EMPTY system GUID.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03105: Could not read WSDL Definition for WSDL with NULL or EMPTY file name.

Cause: Could not read WSDL Definition for WSDL with NULL or EMPTY file name.

Action: The WSDL file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03106: Do not cache WSDL Definition for NULL or EMPTY WSDL file name.

Cause: Do not cache WSDL Definition for NULL or EMPTY WSDL file name.

Action: The WSDL file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03107: Could not read Schema Document for XSD with NULL or EMPTY file name.

Cause: Could not read Schema Document for XSD with NULL or EMPTY file name.

Action: The XSD schema file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03108: Do not cache Schema Document for NULL or EMPTY XSD file name.

Cause: Do not cache Schema Document for NULL or EMPTY XSD file name.

Action: The XSD schema file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03109: Could not read parsed filter expression for NULL or EMPTY expression.

Cause: Could not read parsed filter expression for NULL or EMPTY expression.

Action: The filter expression is null or empty. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03110: Information to process an incoming callback message is not available.

Cause: Information to process an incoming callback message is not available.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03201: Retry of deferred message failed.

Cause: Retry of deferred message failed.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03202: Retry of callback message failed.

Cause: Retry of callback message failed.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03203: Retry of timeout message failed.

Cause: Retry of timeout message failed.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03301: Unexpected exception in case execution "{0}".

Cause: Unexpected exception in case execution "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03302: Unexpected exception in one-way operation "{0}" on reference "{1}".

Cause: Unexpected exception in one-way operation "{0}" on reference "{1}".

Action: Check whether the reference service is properly configured and running or look at exception for analyzing the reason or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03303: Unexpected exception in request response operation "{0}" on reference "{1}".

Cause: Unexpected exception in request response operation "{0}" on reference "{1}".

Action: Check whether the reference service is properly configured and running or look at exception for analyzing the reason or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03304: Unexpected exception in asynchronized request execution "{0}".

Cause: Unexpected exception in asynchronized request execution "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03401: Context lookup failed "{0}".

Cause: Context lookup failed "{0}".

Action: Ensure that the topic is mapped to a JNDI tree.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03402: Error creating "{0}".

Cause: Error creating "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03403: Subscriber does not exist for system "{0}".

Cause: Subscriber does not exist for system "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03405: Error converting field "{0}".

Cause: Error converting field "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03406: Publisher does not exist for system "{0}".

Cause: Publisher does not exist for system "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03408: Unable to store deferred message "{0}".

Cause: Unable to store deferred message "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03409: Invalid, premature, or already-handled callback message. No correlation found for message with conversation ID "{0}".

Cause: Invalid, premature, or already-handled callback message. No correlation found for message with conversation ID "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03501: Unable to start transaction; transaction status is "{0}".

Cause: Unable to start transaction; transaction status is "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03502: Unable to resume transaction.

Cause: Unable to resume transaction.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03503: Unable to commit transaction. Transaction has been rolled back.

Cause: Unable to commit transaction. Transaction has been rolled back.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03504: Unable to rollback transaction.

Cause: Unable to rollback transaction.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03505: "{0}" object not found in JNDI tree.

Cause: "{0}" object not found in JNDI tree.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03506: Unable to get transaction status.

Cause: Unable to get transaction status.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03507: Unable to set rollback only for transaction; transaction status is "{0}".

Cause: Unable to set rollback only for transaction; transaction status is "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03508: One of the routing rule execution resulted in a transaction rollback.

Cause: One of the routing rule execution resulted in a transaction rollback.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03509: Unable to suspend transaction.

Cause: Unable to suspend transaction.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03510: Error obtaining Transaction Manager.

Cause: Error obtaining Transaction Manager.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03511: "{0}" object not found in jndi tree

Cause: "{0}" object not found in jndi tree

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03601: Unable to create transformer. It could be because of transformation file or configuration issues. Reason : "{0}"

Cause: Unable to create transformer. It could be because of transformation file or configuration issues. Reason : "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03602: Unable to create document.

Cause: Unable to create document.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03603: Unable to register base function "{0}" for "{1}".

Cause: Unable to register base function "{0}" for "{1}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03604: Unable to stream xslt results into temp file "{0}"

Cause: Unable to stream xslt results into temp file "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03651: Unable to create callout instance for "{0}".

Cause: Unable to create callout instance for "{0}".

Action: Ensure that your callout configuration is correct. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03652: Unable to execute "{0}" method on callout instance of "{1}".

Cause: Unable to execute "{0}" method on callout instance of "{1}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03701: Unable to configure xpath transformer.

Cause: Unable to configure xpath transformer.

Action: Check log file for any exceptions to fix the configuration otherwise contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03702: Unable to resolve source expression "{0}".

Cause: Unable to resolve source expression "{0}".

Action: Check log file for any exceptions to fix the expression otherwise contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03801: Unable to initialize filter/validator. "{0}" is not supported.

Cause: Unable to initialize filter/validator. "{0}" is not supported.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03802: Unable to create initial context.

Cause: Unable to create initial context.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03803: Unable to initialize Container ID Manager.

Cause: Unable to initialize Container ID Manager.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04001: Error executing service due to server down "{0}". Reason : {1}

Cause: Error executing service due to server down "{0}". Reason : {1}

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04002: Error executing service due to server down "{0}". Reason : {1}

Cause: Error executing service due to server down "{0}". Reason : {1}

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04004: Error persisting resequencer message "{0}". Reason : {1}

Cause: Error persisting resequencer message "{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-04101: Error receiving DB message.

Cause: Error receiving DB message.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04102: Error publishing DB message.

Cause: Error publishing DB message.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04201: Metadata error occurred while using DVM. Check if DVM location, source domain, source value expression and dynamic parameters are valid. ["{0}"].

Cause: Metadata error occurred while using DVM. Check if DVM location, source domain, source value expression and dynamic parameters are valid. ["{0}"].

Action: Modify required parameters. Empty string, null and invalid expressions are not allowed otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04202: Invalid source value expression used while configuring DVM. Check if source value expression is valid. ["{0}"].

Cause: Invalid source value expression used while configuring DVM. Check if source value expression is valid. ["{0}"].

Action: Modify source value for valid expression.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04203: Error occurred while overriding information via DVM lookup Check if DVM location "{0}", source domain "{1}" and source expression "{2}" is valid.

Cause: Error occurred while overriding information via DVM lookup Check if DVM location "{0}", source domain "{1}" and source expression "{2}" is valid.

Action: Modify required parameters. Empty string, null and invalid expressions are not allowed otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04204: Part "{0}" not found in source message.

Cause: Part "{0}" not found in source message.

Action: Check source expression for valid part name otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04205: Property "{0}" not found in "{1}" message.

Cause: Property "{0}" not found in "{1}" message.

Action: Check source expression for valid property name otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04206: Encountered variable which is not supported "{0}".

Cause: Encountered variable which is not supported "{0}".

Action: Check if source has valid variable $in, lookup is supported only for inbound expression. Otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04207: Metadata error occurred while using Business Rule. Check if decision service reference and operation are valid. ["{0}"].

Cause: Metadata error occurred while using Business Rule. Check if decision service reference and operation are valid. ["{0}"].

Action: Modify required parameters. Empty string, null and invalid expressions are not allowed otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04208: Encountered multiple dynamic values to be applied on one static routing rule ["{0}"]. Multiple dynamic values are not supported in static routing rule.

Cause: Encountered multiple dynamic values to be applied on one static routing rule ["{0}"]. Multiple dynamic values are not supported in static routing rule.

Action: Modify Business Rules or DVM to generate only one dynamic value, otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04209: Encountered 11g version dynamic routing metadata. 11g dynamic routing metadata is not supported. ["{0}"] 11g dynamic routing rule has to be upgraded.

Cause: Encountered 11g version dynamic routing metadata. 11g dynamic routing metadata is not supported. ["{0}"] 11g dynamic routing rule has to be upgraded.

Action: Refer to the documentation of dynamic routing upgrade for more details, otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04301: XQuery execution evaluated in null result.

Cause: XQuery execution evaluated in null result.

Action: Please make sure the XQuery content will result in non null value, otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04302: Failed to obtain XQuery connection. ["{0}"]

Cause: Failed to obtain XQuery connection. ["{0}"]

Action: Please check the logs for more details, otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04303: Failed to initialize XQuery. Cause ["{0}"].

Cause: Failed to initialize XQuery. Cause ["{0}"].

Action: Please check the logs for more details, otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04304: Parameter configured for XQuery transformation is incorrect. ["{0}"].

Cause: Parameter configured for XQuery transformation is incorrect. ["{0}"].

Action: Ensure that the XQuery parameters provided in transformation are valid, otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04305: Failed to resolve XQuery external variable "{0}"

Cause: Failed to resolve XQuery external variable "{0}"

Action: External variable which is declared in transformation param must be mediator implicit variables.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04306: Evaluating the implicit mediator XQuery variables resulted in {0}

Cause: Evaluating the implicit mediator XQuery variables resulted in {0}

Action: External variable which is declared in transformation param must be mediator implicit variables. Otherwise please check the logs for more details.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04307: Unable to execute XQuery expression for "{0}".

Cause: Unable to execute XQuery expression for "{0}".

Action: Check log file for any exceptions to fix the expression otherwise contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04308: Unable to bind XQuery external variables. Cause = {0}

Cause: Unable to bind XQuery external variables. Cause = {0}

Action: Check log file for any exceptions to fix the expression otherwise contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04309: Failed to transform XQuery {0}. XQuery execution must result in XML element or document to assign it to the target.

Cause: Failed to transform XQuery {0}. XQuery execution must result in XML element or document to assign it to the target.

Action: Check log file for any exceptions to fix the expression otherwise contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04310: Invalid XQuery implicit variable {0} declared of type {1} Mediator implicit variables which are declared as XQuery external variables must conform to their equivalent type. For ex: $in.<part-name> can be document or element.

Cause: Invalid XQuery implicit variable {0} declared of type {1} Mediator implicit variables which are declared as XQuery external variables must conform to their equivalent type. For ex: $in.<part-name> can be document or element.

Action: Check log file for any exceptions to fix the external variables otherwise contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-09001: Parameter name contains "{0}" qname "{1}".

Cause: Parameter name contains "{0}" qname "{1}".

Action: Verify Name-Value parameters to be of the form 'name1=value1 name2=value2' with value not having any spaces.
Level: 1

Type: ERROR

Impact: Programmatic

41 OWS-00016 to OWS-60003

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00018: getElementDateValue exception {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00019: DOM Exception from removeElement {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00020: problem found in XML parsing: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00021: Error creating XML mapping factory: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

OWS-00023: could not copy {0} to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00024: {0} Failed to load dependent class: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00025: Exception converting WSDL types to XML Schema: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00028: Warning while processing WSM client configuration: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00031: Warning while processing WSM server configuration: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: WebService

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: WebService

OWS-00036: XML fragment top level tag name "{0}" has been corrected to "{1}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00037: No method found in SEI: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00038: A WSDL port in the model is missing a name

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00039: The schema using the namespace of {0} may cause unexpected failures, use {1} instead.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00040: The element {0} in the supplied deployment descriptor will be ignored.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

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: WebService

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: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00056: JMS delivery mode "{0}" is invalid, ignore this setting.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00057: The received SOAP fault contains non standard fault element: "{0}". This element will be ignored.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00058: The class "{0}" exists, but could not be loaded.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

OWS-00060: Ignoring property name "{0}" in Java exception "{1}" because it is not JAX-RPC compliant

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00061: Ignoring property name "{0}" in Java class "{1}" because it is not JAX-RPC compliant

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

OWS-00064: Attribute "schemaLocation" is not present on a schema import element.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00065: Interface "{0}" is not JAX-RPC compliant: it does not extend java.rmi.Remote.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00066: Method "{0}" is not JAX-RPC compliant: it does not throw java.rmi.RemoteException.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

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: WebService

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: WebService

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: SEVERE

Impact: WebService

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: WebService

OWS-00075: Schema with schema namespace {0} is not supported

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

OWS-00077: The Value Type class: {0} does not have a valid Java Bean pattern.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: WebService

OWS-00086: The nested generic type {0} is not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

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: WebService

OWS-00103: nested model group is not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00104: namespace name constraint is not supported (except for ##any, ##other).

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00105: choice is not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00106: wildcard or element is not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00107: multiple occurrences are not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00108: simple or mixed content is not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00109: a mismatch was detected in the parent type.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00110: an unsupported simple type.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00111: expected a soap-enc type.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00112: found a simple type with attributes.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00113: mixed content was seen, this may not be a valid SOAP type.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

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: WebService

OWS-00119: Deleting field: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00126: Deleting unused method: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00129: Changing parameter type of "{0}" from "{1}" to "{2}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00130: Adding new parameter "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00131: Deleting old parameter "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00132: Changing return type of "{0}" from "{1}" to "{2}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00136: Adding initializer "{0}" to field "{1}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00137: Removing initializer "{0}" from field "{1}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00138: Changing initializer of field "{0}" from "{1}" to "{2}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00142: local transport error: {0}

Cause: Error occcured while processing request

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00171: deserialization error: {0}

Cause: Deserializer failed.

Action: Check the incoming message.
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00173: malformed array type: {0}

Cause: The arrayType attribute is missing. The array index is less than 0 or the end index is less than the start index.

Action: Check the incoming message. Check the incoming message.
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00176: missing array position attribute

Cause: Sparse array does not have a position attribute

Action: Check the incoming message
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00178: unexpected null value during serialization or deserialization

Cause: Serializer cannot serialize a null object for a non-nillable parameter.Deserializer cannot deserialize null to a non-nillable object.

Action: Make sure the parameter is not null. Check the incoming message.
Level: 1

Type: SEVERE

Impact: WebService

OWS-00179: Unexpected error while processing a SOAP Message during {0}, message={1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00186: malformed array dimensions: {0}

Cause: The dimensions of the array specified in the SOAP message cannot be translated into a valid number. The bounds of the array are invalid. For example the lower bound of the array is larger than the upper bound.

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00254: generator error: {0}

Cause: An unexpected exception occurred during a generation operation.

Action: Contact Oracle Support Services.
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: WebService

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: WebService

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: SEVERE

Impact: WebService

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: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00315: invalid state while modeling operation: {0}

Cause: System Internal Error

Action: Contact Oracle Support Services
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00339: IO error in processing schemas: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00340: The value of service-interface {0} MUST be package qualified. It is changed to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00341: unrecognized type encountered: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00342: exception occurred while processing type {0}, {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

OWS-00344: Port "{0}" does not contain any usable operations

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

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: WebService

OWS-00347: ignoring operation "{0}": not request-response or one-way

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00348: ignoring RPC-style operation "{0}": parameters are not encoded

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

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: WebService

OWS-00351: ignoring header "{0}" of binding operation "{1}": not literal

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00352: ignoring header "{0}" of binding operation "{1}": not SOAP-encoded

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

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: WebService

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: WebService

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: WebService

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: WebService

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: WebService

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: WebService

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: SEVERE

Impact: WebService

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: WebService

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: SEVERE

Impact: WebService

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: WebService

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: WebService

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: SEVERE

Impact: WebService

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: WebService

OWS-00367: a class by name : "{0}" is already available in the classpath

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00368: failed to make an unique serializer class : "{0}" , the error :"{1}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00369: failed to find accessor method "{0}" in Java type "{1}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00370: model is missing

Cause: The system is missing a model.

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: SEVERE

Impact: WebService

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: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00378: Enumeration {0} is not supported

Cause: The enumeration is not supported.

Action: Modify the schema to remove this enumeraton.
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: WebService

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: WebService

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: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00390: unrecognized fault block

Cause: The response fault is invalid.

Action: Verify the content of the fault response.
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00397: XML reader error: {0}

Cause: XMLReader cannot close the reading stream.

Action: Check network connection and file system connection.
Level: 1

Type: SEVERE

Impact: WebService

OWS-00398: XML parsing error: {0}

Cause: XMLReader cannot read the next element.

Action: Validate the XML document.
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00401: XML writer error: {0}

Cause: XML Writer encounters an IOException.

Action: Check network connection and file system connection.
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: WebService

OWS-00436: -import requires a WSDL-based configuration file

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00437: -define requires a service-based configuration file

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

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: WebService

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: SEVERE

Impact: WebService

OWS-00451: parsing failed: {0}

Cause: ParserConfigurationException is thrown from the parser while parsing the WSDL.

Action: Unexpected internal error.
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00493: Warning: {0} is already defined. Ignoring.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00500: The annotation type or property "{0}" has been deprecated in this version of Oracle WebServices.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-00544: Error destroying interceptors {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00545: Unable to read SOAP message {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00546: Invalid port configuration {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00547: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-00549: The WSDL has overloaded operations "{0}".

Cause: The WSDL has overloaded operations.

Action: Avoid using overloaded operations.
Level: 1

Type: WARNING

Impact: WebService

OWS-00550: JDK1.5 enum is not supported "{0}".

Cause: JDK1.5 enum is not supported

Action: Provide a custom seriallizer.
Level: 1

Type: SEVERE

Impact: WebService

OWS-00551: You are running on JDK6 which comes with JAX-WS 2.1 API and JAXB 2.2 API, but this tool requires JAX-WS 2.2 API and JAXB 2.2.1 API. Use the endorsed standards override mechanism (http://java.sun.com/javase/6/docs/technotes/guides/standards/).

Cause: JDK 1.6 not configured correctly for JAX-WS

Action: Provide an endorsed folder with the newer jars
Level: 1

Type: SEVERE

Impact: WebService

OWS-03002: Failed to load wsm config schema: {0}

Cause: Failed to load wsm config schema.

Action: Please check the WSM configuration schema.
Level: 1

Type: WARNING

Impact: WebService

OWS-03003: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

OWS-03005: Unable to connect to URL: {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-03009: Error reading client wsmgmt configuration {0}

Cause: Unexpected error occurs while reading client configuration file

Action: NONE
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-03011: Error parsing client wsmgmt configuration file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-03012: Error parsing client wsmgmt configuration file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-04007: Error in system configured ejb prehandler: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04011: Error in resolving the webservice endpoint: {0}

Cause: Failed to determine the WebService Endpoint for the servlet

Action: None
Level: 1

Type: SEVERE

Impact: WebService

OWS-04014: Error in system configured servlet post-handler: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04018: Error processing soap message over jms :{0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04020: Error during handler invocation:

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04024: Error in system configured ejb post-handler: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

OWS-04029: Error in system configured servlet pre-handler: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04039: Error closing connection: {0}

Cause: Failed to close the connection to specific database

Action: None
Level: 1

Type: SEVERE

Impact: WebService

OWS-04042: Error happened while loading the DDs

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04043: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04044: The referenced wsdl file has changed, please re-deploy {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-04047: Cannot create xslt transformer

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04048: xslt transformation failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04050: Unable to load the webservices management interceptor pipeline

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04061: Internal JMX error {0}

Cause: Internal error while configuring JMX

Action: None
Level: 1

Type: SEVERE

Impact: WebService

OWS-04062: XML parser configuartion error {0}

Cause: An unexpected error occured while parsing configuring the XML parser

Action: None
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-04067: Error reading config file {0}

Cause: Failed to read the interceptor configuration file

Action: None
Level: 1

Type: SEVERE

Impact: WebService

OWS-04068: Error serializing default config {0}

Cause: Failed to serialize the default configuration for interceptor.

Action: None
Level: 1

Type: SEVERE

Impact: WebService

OWS-04069: Error serializing global configuration for {0} interceptor {1}

Cause: Failed to serialize global configration for interceptor.

Action: None
Level: 1

Type: SEVERE

Impact: WebService

OWS-04070: Error serializing configuration {0}

Cause: Failed to serialize the configuration

Action: None
Level: 1

Type: SEVERE

Impact: WebService

OWS-04071: Unrecognized interceptor configuration: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04072: Error writing config file {0}

Cause: Error writing the configuration file for interceptor to FileManager

Action: None
Level: 1

Type: SEVERE

Impact: WebService

OWS-04073: Error parsing wsmgmt configuration file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04074: Error parsing wsmgmt configuration file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04075: Error parsing wsmgmt configuration file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04086: {0}

Cause: An unexpected error occured

Action: None
Level: 1

Type: SEVERE

Impact: WebService

OWS-04092: Unable to configure parser: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04093: Unable to parse schema: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04094: unknown tag <{0}> in {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: WebService

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: WebService

OWS-04102: Unable to configure dynamic provider endpoint across cluster due to exception {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04103: Unknown element <{0}> in descriptor: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-04107: The proprietary implementor type is not specified.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-04111: Proxy information not set, external import downloads may fail.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

OWS-04113: Policy advertisement failed for {0}: {1}

Cause: Failed to advertise the policy in the WSDL

Action: None
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-04116: The error stack trace: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-04117: {0}

Cause: Exception occured while configuring dynamic provider based endpoint

Action: None
Level: 1

Type: SEVERE

Impact: WebService

OWS-04119: Local service registration failed for {0}: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

OWS-04123: Unsupported oracle-webservices deployment descriptor for module {0}, schema version {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-04131: SOAP must understand error. MustUnderstand headers:["{0}"] are not understood.

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: SEVERE

Impact: WebService

OWS-04132: FastInfoset is disabled for this service

Cause: A FastInfoset message was received for a service that has FastInfoset disabled

Action: Please enable FastInfoset for the web service or send a non-FastInfoset input message
Level: 1

Type: WARNING

Impact: WebService

OWS-04136: JRF WebServices are not supported in 'Restricted JRF'.

Cause: Trying to deploy JRF WebServices which is not supported in 'Restricted JRF'.

Action: Use 'Full JRF' for deploying application that uses JRF WebServices implementation.
Level: 1

Type: SEVERE

Impact: WebService

OWS-04137: DTD is not supported

Cause: Sending SOAP request with DTD

Action: Do not use DTD in SOAP request to JRF web services
Level: 1

Type: SEVERE

Impact: WebService

OWS-08008: Web service artifact generation failed.

Cause: Web service artifact generation failed.

Action: Verify and correct by the error message and stack trace.
Level: 1

Type: SEVERE

Impact: WebService

OWS-08010: Incorrect packaging ({0}): WSDL should be packaged in a directory named either 'META-INF/wsdl' or 'WEB-INF/wsdl'.

Cause: Incorrect WSDL packaging.

Action: Verify that the correct the WSDL packaging configurations.
Level: 1

Type: WARNING

Impact: WebService

OWS-08015: No web service named '{0}' is defined. Ignoring the proprietary configuration for this web service.

Cause: Web service name is not properly defined.

Action: Verify that the web service name from the proprietary configuration.
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-15006: Multiple WSIFProvider found supporting the same namespace URI ''{0}''. Found (''{1}'')

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-15008: WSIFDefaultCorrelationService removing correlator due to timeout. ID:''{0}''

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-15010: Exception thrown while processing asynchronous response - ''{0}''

Cause: Exception thrown while processing asynchronous response

Action: None
Level: 1

Type: SEVERE

Impact: WebService

OWS-25106: Internal error: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-25108: Some messages have not been acknowledged

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-25111: Error sending LastMessage: {0}

Cause: Unknown

Action: Check server logs for additional details.
Level: 1

Type: SEVERE

Impact: WebService

OWS-25112: The WS-RM client interceptor encountered an exception while handling a response, {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-25113: Duplicate eliminated for message #{0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-25118: Skip null in handling outbound message {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-25119: Forcing wsa:Action inside RM code to {0}. Please, verify your addressing handler configuration

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-25168: An attempt was made to terminate a WS-RM sequence inactivity monitor for the sequence identified by {0}, which is not currently being monitored.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50001: The @WebService.portName is not allowed on endpoint interfaces.: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50002: The @WebService.serviceName is not allowed on endpoint interfaces.: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50003: Could not find schema type : {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-50010: Dispatch currently does not support REST style service.

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: WebService

OWS-50013: Could not determine a valid protocol binding to generate for the binding public static final 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: WebService

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: WebService

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: WebService

OWS-50016: IOException converting AddressingInfo to public static final String.

Cause: IO error converting addressing info to public static final String

Action: correctAddressingInfo
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: WebService

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: WebService

OWS-50030: wsdlDocumentLocation is currently not supported.

Cause: WSDLDocumentLocation is currently not supported

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-50034: The method "{0}" is ignored. {1}

Cause: The JAVA method is ignored in WSDL generation.

Action:
Level: 1

Type: WARNING

Impact: WebService

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:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: WebService

OWS-50040: Failed while accessing Keystore details.

Cause: Keystore details are not setup.

Action: Configure keystore details for the server.
Level: 1

Type: SEVERE

Impact: WebService

OWS-50042: [MessageID: {0}] Request MDB could not complete asynchronous request processing successfully. No response will be sent to the client. Analyze the details of the exception as it is likely server side configuration error.

Cause: Asynchronous request processing resulted in exception

Action: Analyze the exception and take appropriate action.
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-50044: [MessageID: {0}] Could not post 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: SEVERE

Impact: WebService

OWS-50045: Could not close the connection to JMS queue

Cause: Internal error.

Action: Can be ignored.
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: WebService

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 not correctly specified in the source 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: SEVERE

Impact: WebService

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: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-50059: [MessageID: {0}] Error while processing the message off the JMS queue.

Cause: System error

Action: Analyze the exception details.
Level: 1

Type: SEVERE

Impact: WebService

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: WebService

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: SEVERE

Impact: WebService

OWS-50064: [MessageID: {0}] Failed to send async response to client-side callback receiver.

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: SEVERE

Impact: WebService

OWS-50066: Could not save the context for async service in cache with the key "{0}".

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: SEVERE

Impact: WebService

OWS-50067: Could not cleanup the context for async service from cache as it was not found.

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: WARNING

Impact: WebService

OWS-50069: Could not remove the saved context for async service from cache with the key "{0}".

Cause: Internal system error

Action: Internal system error.
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-50073: [MessageID: {0}] Encountered exception or error while invoking user's Java Web Service method.

Cause: This might be because of invalid request, missing resources in the service implementation or a bug.

Action: Analyze the exception or error details.
Level: 1

Type: SEVERE

Impact: WebService

OWS-50080: [MessageID: {0}] Response MDB encountered exception during asynchronous response processing.

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: SEVERE

Impact: WebService

OWS-50081: [MessageID: {0}] Response MDB encountered exception.

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: SEVERE

Impact: WebService

OWS-50082: [MessageID: {0}] Response MDB will not retry sending response as callback service sent soap fault back. HTTP response code received by response MDB 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 client-side callback service properly.
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-50096: [MessageID: {0}] User transaction is being rolled back 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: SEVERE

Impact: WebService

OWS-50100: [MessageID: {0}] Could not get the transaction manager (javax.transaction.TransactionManager).

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: SEVERE

Impact: WebService

OWS-50102: [MessageID: {0}] Could not resume the suspended main transaction.

Cause: Internal system error

Action: Internal system error.
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-50107: [MessageID: {0}] Could not rollback the main transaction

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: SEVERE

Impact: WebService

OWS-50108: [MessageID: {0}] Could not commit the main transaction

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: SEVERE

Impact: WebService

OWS-50109: [MessageID: {0}] HTTP response code received from client-side callback service is "{1}".

Cause: Callback service returned HTTP response other than 200 or 202.

Action: Analyze the details of soap message returned by callback service or the HTTP error code.
Level: 1

Type: SEVERE

Impact: WebService

OWS-50111: [MessageID: {0}] Received soap fault from the client-side callback service.

Cause: Callback has sent a soap fault as the response.

Action: Analyze the fault and configure the callback service properly.
Level: 1

Type: SEVERE

Impact: WebService

OWS-50112: [MessageID: {0}] Could not dump the soap message

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-50115: Exception in handler chain

Cause: Handler chain has thrown some exception

Action: Look at the details of exception.
Level: 1

Type: SEVERE

Impact: WebService

OWS-50117: Unsupported message context, jaxws handler will not be called

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50118: Unsupported message context, "{0}" could not handle fault

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50121: Error parsing handler chain: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50122: Could not process callback interface "{0}". Any methods defined in the interface will be ignored

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50123: Unsupported operation when generating schemas "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50124: Unknown Exception when generating schemas: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50125: Could not load schema from location "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50127: Could not determine wsdl ports.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50128: Could not find service "{0}"; Using first service in WSDL instead.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50129: No wsdl location or document specified

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50130: No web module with name of "{0}" so a new war will be created

Cause: TBD

Action: TBD
Level: 1

Type: SEVERE

Impact: WebService

OWS-50131: Found web module with name of "{0}", so the generated contents will be merged.

Cause: TBD

Action: TBD
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-50133: Error extracting war "{0}".

Cause: TBD

Action: TBD
Level: 1

Type: SEVERE

Impact: WebService

OWS-50134: Error while processing ejb-jar.xml for ejb module at "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50135: Could not load jaxrpc annotation parser, the webservices in this ejb will not be manageable

Cause: TBD

Action: TBD
Level: 1

Type: SEVERE

Impact: WebService

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: WebService

OWS-50138: Could not write operation metadata for "{0}".

Cause: Exception in writing operation metadata

Action: Analyze the exception.
Level: 1

Type: SEVERE

Impact: WebService

OWS-50139: HandlerChain configuration file: "{0}".

Cause: TBD

Action: TBD
Level: 1

Type: SEVERE

Impact: WebService

OWS-50140: Failed to resolve HandlerChain annotation "file" value ({0}) as it is specified on "{1}"

Cause: TBD

Action: TBD
Level: 1

Type: SEVERE

Impact: WebService

OWS-50141: Fabric Registration ignored because this service does not use SDO binding.

Cause: TBD

Action: TBD
Level: 1

Type: SEVERE

Impact: WebService

OWS-50143: Fabric Registration ignored because Register class "{0}" can not be instantiated.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50144: Fabric Registration ignored because Register class "{0}" can not be accessed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50146: Fabric Registration failed due to exception: "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50147: SDO Type Registration failed due to exception: "{0}".

Cause: TBD

Action: TBD
Level: 1

Type: SEVERE

Impact: WebService

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: WebService

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: WebService

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: WebService

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: WebService

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: WebService

OWS-50155: Error processing handler chain: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

OWS-50156: Unsupported type when generating schemas: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

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: WebService

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: SEVERE

Impact: WebService

OWS-50177: Could not read saved context for async service from cache using the key: "{0}".

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: SEVERE

Impact: WebService

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: WebService

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: WebService

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: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-50198: The content negotiation strategy {0} is incompatible with a service that has FastInfoset disabled according to the WSDL

Cause: The content negotiation strategy provided is incompatible with a Service that has FastInfoset Disabled

Action: Do not supply a content negotiation strategy On the client
Level: 1

Type: SEVERE

Impact: WebService

OWS-50199: The FastInfoset content negotiation strategy '{0}' specified in the request context property conflicts with the value '{1}' specified on the feature object

Cause: The content negotiation request context property provided conflicts with the content negotiation feature set on the same client

Action: Supply either a content negotiation request context property or a feature, not both. If both are provided, make sure they are set to the same value
Level: 1

Type: SEVERE

Impact: WebService

OWS-50200: The FastInfosetFeature provided on the client has enabled = {0}, while the service WSDL has enabled = {1}. The client value will override the value read from the WSDL

Cause: The FastInfosetFeature provided on the client is different from that advertised on the service WSDL - client feature will be used as an override

Action: Make sure that the intent was to override the value advertised in the service WSDL - if not, remove the feature on the client
Level: 1

Type: WARNING

Impact: WebService

OWS-50201: Found invalid policy references on WebService endpoint. Please make sure you do not have mulitple or conflicting policy refrerences on your webservice endpoint.

Cause: There is invalid policy set due to conflicting or multiple policy references of same category on given JAXWS endpoint.

Action: Make sure that there are no multiple or conflicting policy refeences specified on webservcie endpoint.
Level: 1

Type: SEVERE

Impact: WebService

OWS-50205: Could not create request and response JMSChannel instances required to post JMS messages.

Cause: Internal system error

Action: Analyze the details of the exception
Level: 1

Type: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

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: SEVERE

Impact: WebService

OWS-51501: No schema mapping found for class {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: WebService

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:
Level: 1

Type: WARNING

Impact: WebService

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: SEVERE

Impact: WebService

42 PKI-01001 to PKI-07022

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-02012: Unable to lock file at

Cause: May be file channel get closed or blocked while getting lock on p12 or sso file in wallet.

Action: Try to achieve lock again on wallet.
Level: 1

Type: ERROR

Impact: Other

PKI-02013: Unable to create/parse RSA credentials.

Cause: RSA algorithm to create key pair is missing.

Action: A JCE implementation that supports RSA is required.
Level: 1

Type: ERROR

Impact: Other

PKI-02014: Unable to create/parse ECC credentials.

Cause: ECC algorithm to create key pair is missing.

Action: A JCE implementation that supports ECC is required.
Level: 1

Type: ERROR

Impact: Other

PKI-02015: Trust Flags are not enabled for the wallet.

Cause: Trust flags are getting assigned to certificates but the wallet containing them are not permitted to have trust flags.

Action: Wallet should be trust flag enabled before assigning trust flags to the certificates.
Level: 1

Type: ERROR

Impact: Other

PKI-02016: Trust Flags are already enabled for the wallet.

Cause: Trying to enable wallet for trust flag but it is already enabled.

Action: Wallet is already permitted for trust flags.Do not try to enable it again.
Level: 1

Type: ERROR

Impact: Other

PKI-02017: Thread %d attempted to release non-existent lock

Cause: Lock does not exist.

Action: Please check the existence of lock before releasing it.
Level: 1

Type: ERROR

Impact: Other

PKI-02018: PKCS12 file does not exist.

Cause: PKCS12 file path is not valid or empty in given parameters while importing pkcs12 file.

Action: PKCS12 file path should be valid before importing it.
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-03006: An entry already exists for map {0} and key {1}

Cause: Credentials already exist in Secret store.

Action: Different username and password to be used to store credentials in secret store.
Level: 1

Type: ERROR

Impact: Other

PKI-03007: An entry does not exist for map {0} and key {1}

Cause: Credentials do not exist in Secret store.

Action: Credentials need to be stored before modification can be done on them.
Level: 1

Type: ERROR

Impact: Other

PKI-03008: The specified credential map name is invalid

Cause: Map name given is not valid.

Action: Map name should be valid.
Level: 1

Type: ERROR

Impact: Other

PKI-03009: The specified credential key name is invalid

Cause: Key name is not valid or present.

Action: Key name should be valid.
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.

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: An entry with the specified alias already exists 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 is 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 private 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-04019: Certificate uses unsupported Public Key Algorithm %s.

Cause: Key algorithm used is different than RSA or ECC.

Action: RSA and ECC are only supported
Level: 1

Type: ERROR

Impact: Other

PKI-04020: The certificate already exists in the given path

Cause: Certificate already exists at given path.

Action: Path should be valid to create a new certificate.
Level: 1

Type: ERROR

Impact: Other

PKI-04021: Invalid value(s) of Trust Flags provided.

Cause: Trust flag value(s) provided is/are not according to given ones.

Action: Trust Flags value should be valid one.
Level: 1

Type: ERROR

Impact: Other

PKI-04022: Invalid value of Serial Number provided.

Cause: Serial number is not valid. It does not consist of numeric value

Action: Serial number should be valid.
Level: 1

Type: ERROR

Impact: Other

PKI-04023: No Matching certificate found for given input parameters.

Cause: No certificate is found for given subject.

Action: Subject should be valid of a existing certificate.
Level: 1

Type: ERROR

Impact: Other

PKI-04024: Cannot assign Trust Flags while importing a certificate chain.

Cause: Same Trust flag is getting assigned to all certificates in chain.

Action: All certificates in chain cannot be assigned same trust flag .Correct trust flags need to be assigned.
Level: 1

Type: ERROR

Impact: Other

PKI-04025: Unique certificate cannot be identified.

Cause: Multiple certificates with matching parameters exist.

Action: There should be single certificate of matching subject to do modifications on it
Level: 1

Type: ERROR

Impact: Other

PKI-04026: CRL's signer certificate is not valid.

Cause: Certificate has been expired.

Action: Certificate should be valid before getting added to CRL.
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-05007: Given CRL already Exists.

Cause: CRL is already present at given path

Action: Valid CRL path should be given to create.
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 certificate 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

PKI-07008: Keysize must be 512 or 768 or 1024 or 2048 or 4096.

Cause: Keysize value given for certificate is not from recommended ones.

Action: Keysize value for RSA should be either 512 or 768 or 1024 or 2048 or 4096.
Level: 1

Type: ERROR

Impact: Other

PKI-07009: The elliptic curve name must be one of the fifteen NIST recommended ones.

Cause: elliptic curve values given for certificate is not from supported ones.

Action: Elliptic curve values should be one of recommended ones.
Level: 1

Type: ERROR

Impact: Other

PKI-07010: A key size must be specified when creating an RSA key.

Cause: Keysize value has not been provided for RSA key algorithm.

Action: Keysize value is required for RSA key algorithm
Level: 1

Type: ERROR

Impact: Other

PKI-07011: A curve name must be specified when creating an EC key.

Cause: Curve name is missing for ECC key algorithm.

Action: Curve name should be provided for ECC key algorithm
Level: 1

Type: ERROR

Impact: Other

PKI-07012: Unable to migrate to jks.Trust store password is required.

Cause: Trust store password is missing.

Action: Trust store password is required during jks migration.
Level: 1

Type: ERROR

Impact: Other

PKI-07013: Unable to migrate to jks.Key store location is required.

Cause: Key store location is missing while migrating jks.

Action: Key store location is required.
Level: 1

Type: ERROR

Impact: Other

PKI-07014: Unable to import private key.

Cause: Error occurred while importing private key to the wallet.

Action: Importing private key is not successful.
Level: 1

Type: ERROR

Impact: Other

PKI-07015: Unable to import private key.

Cause: Certificate is missing of which private key needs to be imported.

Action: Certificate is required.
Level: 1

Type: ERROR

Impact: Other

PKI-07016: Unable to export private key.

Cause: Private key file name is required

Action: Alias should be valid.
Level: 1

Type: ERROR

Impact: Other

PKI-07017: Unable to export private key.

Cause: Private key is not present in wallet for this alias.

Action: Alias should be valid.
Level: 1

Type: ERROR

Impact: Other

PKI-07018: Operation is unsuccessful. Alias is missing.

Cause: Alias is missing in given parameters to search certificate

Action: Alias is required.
Level: 1

Type: ERROR

Impact: Other

PKI-07019: Unable to export certificate chain

Cause: File to which certificate chain needs to be exported is not present.

Action: File path should be present and be valid.
Level: 1

Type: ERROR

Impact: Other

PKI-07020: Unable to export certificate chain. Certificate chain is not present in wallet.

Cause: Given parameters do not match with any certificate in wallet.

Action: All input parameters to detect certificate chain should be valid and present.
Level: 1

Type: ERROR

Impact: Other

PKI-07021: Keysize cannot be null or empty.

Cause: Keysize would be either null or empty.

Action: Keysize is required.
Level: 1

Type: ERROR

Impact: Other

PKI-07022: Keysize or serial number cannot be null or empty.

Cause: Keysize or serial number would be either null or empty.

Action: keysize and serial number are required.
Level: 1

Type: ERROR

Impact: Other

43 RCU-06000 to RCU-07005

RCU-06000: Unable to connect to the database.

Cause: Could not connect to the database. Required database connection field(s) "{0}" is/are empty.

Action: Enter valid value in all required field(s).
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06001: Port number validation failed.

Cause: An invalid port number {0} was specified. A valid port number ranges from 0 to 65535.

Action: Enter a valid port number.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06002: Prerequisite validation failed.

Cause: The minimum requirements to load metadata repository were not met for the specified database.

Action: Modify the database configuration to meet the prerequisite requirements.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06003: No metadata repository schema can be dropped.

Cause: RCU could not find the Schema Version Registry in the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06004: Empty database user password.

Cause: Password for the SYS database user not specified.

Action: Enter the password for the SYS user.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06005: Unable to execute sql query.

Cause: Database not in open state.

Action: Make sure that the database is open.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06011: Prefix validation failed.

Cause: An invalid prefix was specified. A valid prefix can contain only alpha-numeric characters. It should not start with a number and should not contain any special characters.

Action: Select a prefix from the existing prefixes or enter a new prefix.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06012: Unable to find any prefix.

Cause: There were no existing prefixes in the Schema Version Registry of the specified database.

Action: Refer to the rcu logs or contact the system administrator.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06013: Prefix validation failed.

Cause: Specified prefix could not be found. Existing prefixes are: {0}

Action: Specify a valid prefix from the existing prefix list.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06014: invalid component

Cause: Specified component did not exist.

Action: Provide a component that exists.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06015: Component validation failed.

Cause: No component was selected or specified.

Action: Select or specify at least one component.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06016: Invalid prefix specified.

Cause: The specified prefix already exists.

Action: Specify another prefix.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06017: Valid component is not specified.

Cause: There was no prefix specified and the specified component already exists.

Action: If the component is non-prefixable, only one instance can exist. To re-create the instance, drop it first and then create it again.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06018: Schema owner validation failed.

Cause: Value for schema owner {0} was not provided.

Action: Provide values for all schema owners.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06019: Invalid format was provided for schema owner {0}.

Cause: Prefixable components should have the schema owner in the following format <prefix>_<Any String> where the prefix is {1}.

Action: Ensure that the schema owners of all prefixable components begin with the prefix, followed by "_".
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06020: Invalid schema owner {0}.

Cause: Schema owner {0} was duplicated. Schema owners must be unique.

Action: Provide unique schema owners.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06021: Existing components cannot be specified.

Cause: The specified component ({0}) was non-prefixable, and it already exists.

Action: Deselect the non-prefixable component as it already exists.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06022: RCU cannot be executed in resume mode.

Cause: No components to resume execution.

Action: Run RCU without resume option.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06030: Tablespace {0} validation for component {1} failed.

Cause: The specified tablespace {0} for component {1} did not have enough free space to hold the repository. The required free space is {2} MB, but the available space was {3} MB.

Action: Modify the properties of the tablespace or change the prerequisite value.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06051: RCUCommandLine Error - command line options validation failed.

Cause: Invalid option specified.

Action: Provide valid command line options. Remove the invalid option:
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06052: RCUCommandLine Error - Error while validating command line arguments.

Cause: Invalid format/order of command line options and values.

Action: Ensure that the format/order of the options and values in the command line are correct.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06053: RCUCommandLine Error - command line option validation failed.

Cause: More than one mutually exclusive option passed.

Action: Provide valid command line options. Provide only one valid option from this list:
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06054: RCUCommandLine Error - Database type validation failed.

Cause: Database type was not provided.

Action: Provide the database type.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06055: RCUCommandLine Error - command line arguments validation failed.

Cause: Database connect string was not provided.

Action: Provide the database connect string.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06056: RCUCommandLine Error - Database host name validation failed.

Cause: Database host name was not provided.

Action: Provide the database host name.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06057: RCUCommandLine Error - Database port number validation failed.

Cause: Database port number was not provided.

Action: Provide the database port number.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06058: RCUCommandLine Error - Database service name validation failed.

Cause: Database service name was not provided.

Action: Provide the database service name.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06059: RCUCommandLine Error - Database user validation failed.

Cause: Database user was not provided.

Action: Provide the database user.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06060: RCUCommandLine Error - Database password validation failed.

Cause: Database password was not provided.

Action: Provide the database password.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06061: RCUCommandLine Error - Database role validation failed.

Cause: Database role was not provided.

Action: Provide the database role.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06062: RCUCommandLine Error - Schema prefix validation failed.

Cause: Schema prefix was not provided.

Action: Provide the schema prefix.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06063: RCUCommandLine Error - Tablespace name validation failed.

Cause: Tablespace name is not provided. Pass DEFAULT_VALUE to use default tablespace name.

Action: Provide the tablespace name.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06064: RCUCommandLine Error - Schema owner name validation failed.

Cause: Schema owner name is not provided. Pass DEFAULT_VALUE to use default schema owner name.

Action: Provide the schema owner.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06065: RCUCommandLine Error - component name validation failed.

Cause: Invalid component name(s) were provided : {0}

Action: Provide valid component name(s). Supported component names can be obtained by running "-listComponents" command.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06066: RCUCommandLine Error - Error occurred while validating Checkpoint object.

Cause: Checkpoint object was not found or was not readable. Cannot proceed in resume mode.

Action: Refer to the RCU log and make sure that checkpoint object exists to continue in resume mode.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06067: RCUCommandLine Error - checkpoint validation failed.

Cause: No pending components found in checkpoint. Cannot proceed in resume mode.

Action: Invoke RCU without resume option.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06068: Checkpoint object cannot be created.

Cause: Failed to write checkpoint object.

Action: Refer to the RCU log for details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06080: Global prerequisite check failed for the specified database.

Cause: Global prerequisite check failed. Check requirement for the specified database.

Action: Modify the database configuration to meet the global prerequisite requirements.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06081: Internal Error - unable to run prereq query in the specified database.

Cause: Unable to obtain properties of the specified database.

Action: Make sure that the database is in a proper state.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06082: Tablespace prerequisite check failed for the selected component.

Cause: Tablespace prerequisite check failed. Check tablespace requirement for each selected component.

Action: Modify the properties of the tablespace or change the prerequisite value.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06083:

Cause: Prerequisite check failed for selected component.

Action: Refer to the RCU logs for additional details. Make sure that the prerequisite requirements are met.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06084: {0} failed.

Cause: invalid format for Java prerequisite: {0}

Action: Make sure that the java prerequisite is in a valid format.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06085: Java prerequisite is not met.

Cause: Error occurred while executing Java prerequisite: {0}

Action: 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: Repository Configuration

RCU-06090: Connection step validation failed.

Cause: Skipping main operation: failed to connect to database because database details were missing or invalid.

Action: Provide correct database details and try again.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06091: Component validation failed.

Cause: One or more component specific validation failed.

Action: Check log for more details and fix the validation error.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06092: Components are not selected properly.

Cause: Component Selection validation failed. Refer to log at {0} for details.

Action: Select one or more components to continue.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06093: Skipping main operation because of validation error.

Cause: Failed to validate schema tablespace.

Action: Check the properties of the database and the tablespaces specified.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06100: Prerequisite check failed.

Cause: Exception while executing prerequisite {0}.

Action: Refer to the logs for details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06101: The database prerequisite check failed for {0}

Cause: Prerequisite failed for {0}. Current Value is {2}. It should {3} {1}

Action: Modify database configuration to meet the prerequisite requirement.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06102: The database prerequisite check failed for {0}.

Cause: The prerequisite {0} returned an empty result.

Action: Modify the database configuration to meet the prerequisite requirements.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06103: The database option prerequisite check failed.

Cause: The database option prerequisite check failed for: {0} Required Value = {1}, Current Value = {2}

Action: Make sure that the database option has the required value.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06104: The database object prerequisite check failed.

Cause: The database object prerequisite check fails for: {0} This object does not exist or its status is not valid.

Action: Make sure that the database object exists and is valid.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06105: The database component prerequisite check failed.

Cause: The database component prerequisite check failed for {0}. This component does not exist or its status is not valid.

Action: Make sure that the database component exists and is valid.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06106: The database version prerequisite failed.

Cause: The database version prerequisite failed because the current database version is not supported with RCU. Current Version is {1}. It should be {2} {0}.

Action: Make sure that the database version being used is supported with RCU.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06107: The database initialization parameter prerequisite check failed.

Cause: The database initialization parameter prerequisite check failed for {0}. Current Value is {2}. It should {3} {1}.

Action: Make sure that the database initialization parameter has the required value.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06108: The database tablespace free space prerequisite check failed.

Cause: The database tablespace free space prerequisite check failed for {0}. Current space is {2}. It should be {3} {1}.

Action: Modify the properties of the tablespace or change the prerequisite value.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06120: Component dependencies check failed.

Cause: Component dependencies not met for components with following ids: {0}.

Action: Select the dependent components and try again.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06121: Component dependencies check failed.

Cause: Required dependent components were not selected.

Action: Select the dependent components and try again.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06130: Action failed

Cause: Action failed - {0}.

Action: Check the actions for the component or contact the system administrator.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06131: Error while connecting to the database.

Cause: An error occurred while connecting to the database.

Action: Provide correct database details and try again, or contact the system administrator.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06132: The database type of the specified database is not supported - {0}

Cause: The database type of the specified database was not supported.

Action: Use a database type that is supported.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06133: Error while executing host command action.

Cause: An error occurred while trying to execute host command action.

Action: Check the host command action for the component or contact the system administrator.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06134: Error while executing JDBC action.

Cause: An error occurred while trying to execute JDBC action.

Action: Check the jdbc action for the component or contact the system administrator.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06135: Error while executing Java action.

Cause: An error occurred while trying to execute Java action.

Action: Check the java action for the component or contact the system administrator.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06136: Error while executing SQLPlus action.

Cause: An error occurred while trying to execute SQLPlus action.

Action: Check the sqlplus action for the component or contact the system administrator.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06138: The operation has been halted.

Cause: The operation was halted.

Action: Click continue or restart the operation.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06139: Invalid consolidated schema name {0}.

Cause: Consolidated schema {0} exists in database, but schema version registry table did not have an entry for the schema with expected status. The consolidated schema should be created through RCU.

Action: Provide valid consolidated schema name.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06140: Invalid schemas to be consolidated.

Cause: {0} was not a valid schema in the given database.

Action: Provide valid schema name for consolidation.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06141: Schema validation failed.

Cause: {0} cannot be consolidated.

Action: Refer logs for details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06142: Provided schema cannot be consolidated.

Cause: Validation of consolidate schema failed.

Action: Check the logs for details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06143: Provided schema name is not a valid consolidated schema.

Cause: Provided schema exists in database, but the schema was not valid for given consolidate operation.

Action: Make sure schema is of type "CONSOLIDATED".
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06144: Same component type schemas are provided for consolidation.

Cause: Both schemas {0} and {1} are of type {2}. Schemas of same type cannot be consolidated.

Action: Make sure that schemas to be consolidated are not of the same component.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06146: Invalid consolidated schema name.

Cause: {0} was not a valid schema in the provided database.

Action: Make sure the scripts generated during consolidateGrant are executed.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06147: Invalid command line option specified.

Cause: Consolidate operations are supported only in silent mode.

Action: Invoke the command with "-silent" option.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06148: Consolidated schema validation failed.

Cause: Consolidation of an existing schema is not allowed. {0} already consolidated to the schemas {1}.

Action: Execute "dropConsolidatedSchema" to delete the existing schema and recreate it using "consolidate". To recreate the synonyms to the existing schemas use "-reconsolidate" option.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06149: Consolidate schema validation failed.

Cause: Failed to find consolidated schema definition for {0}. Cannot execute reconsolidate on this schema.

Action: Refer to RCU logs for any errors.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06150: Consolidate schema validation failed.

Cause: Specified schema {0} already exists in the database.

Action: Drop the existing schema or generate the script using different schema name.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06151: Consolidate schema validation failed.

Cause: Specified schema {0} does not exist in the database. Could not execute "reconsolidate" option.

Action: Use "consolidate" option to create the consolidated schema.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06152: Consolidate schema name validation failed.

Cause: Specified schema name "{0}" length exceeds allowed number of characters. Maximum number of characters allowed in consolidated schema name is 25.

Action: Specify valid value for consolidated schema name.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06153: Edition value of {0} is empty.

Cause: Specified database type is EBR. But the schema to be consolidated "{0}" is not created with this edition, "{1}". Schemas to be consolidated have to be created in the same edition as the value specified for consolidate schema.

Action: Ensure that the schemas to be consolidated exist in the same edition as that of the consolidated schema.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06154: Specified edition/schema name is invalid.

Cause: Schemas to be consolidated have to be created in the same edition as the value specified for consolidate schema. "{0}" schema is created with edition "{1}". But the edition specified for consolidate schema is "{2}"

Action: Ensure that the schemas to be consolidated exist in the same edition as that of the consolidated schema.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06155: Invalid database type or schemas to be consolidated.

Cause: Specified database type is ORACLE. Consolidated schema could not be created using schemas created in EBR database type. "{0}" schema is created with EBR as database type.

Action: Ensure that the schemas to be consolidated are not created using EBR database type.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06156: Validation of edition failed.

Cause: Edition was not specified or was empty value.

Action: Specify the value of edition for EBR database type.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06157: Internal error occurred.

Cause: Execution of sql query, {0} failed.

Action: Refer to the RCU logs for details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06158: Unable to verify components of the schemas to be consolidated.

Cause: Error in checking whether the component {0} is consolidatable.

Action: Refer to the RCU logs for details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06159: Invalid command line arguments.

Cause: Validation of the command line parameters for listSchemas operation failed.

Action: Refer to the RCU logs for details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06160: Invalid database type for "listSchemas" operation.

Cause: "listSchemas" operation is supported only on ORACLE and EBR

Action: Provide valid database type.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06161: Consolidated schema cannot be dropped.

Cause: Validation of drop consolidated schema failed. Specified consolidated schema was invalid.

Action: Check the logs for details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06162: Invalid consolidated schema name.

Cause: Consolidated schema name was not provided.

Action: Provide valid consolidated schema name using "{0}" parameter.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06163: Invalid schema specified for consolidation.

Cause: Specified schema {0} was not a valid schema in the schema version registry info.

Action: Provide valid schema name.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06164: Invalid schema name specified for drop operation.

Cause: {0} is not of type "CONSOLIDATED". "-dropConsolidatedSchema" operation can be used only to drop consolidated schemas.

Action: Specify valid consolidated schema name.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06165: Invalid consolidated schema name.

Cause: Consolidated schema name was not provided.

Action: Provide valid value for {0}.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06166: Invalid schemas to be consolidated.

Cause: Consolidated schema list was not provided.

Action: Provide valid value for {0}.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06167: Missing command line arguments for consolidate operation.

Cause: Valid value was not specified for consolidated schema name.

Action: Provide the argument {0} for consolidate operation.Refer to RCU help for details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06168: Missing command line arguments for consolidate operation.

Cause: Valid value was not specified for schemas to be consolidated.

Action: Provide the argument {0} for consolidate operation.Refer to RCU help for details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06169: Unable to write properties to response file.

Cause: An IO error occurred while writing into response file.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06170: Unable to generate response file.

Cause: An Internal error happened during response file generation.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06171: Initialization of properties from RCU Response template failed.

Cause: Unable to read the RCUResponse.xml template from RCU jar.

Action: Contact the administrator to resolve the issue.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06172: Error in reading properties from RCU Response template.

Cause: A Jaxb error was thrown while parsing the template xml.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06173: Unable to generate RCUResponse file.

Cause: An error occurred while generating RCUResponse file.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06174: Could not create the response file directory

Cause: Unable to create the response file directory {0}. This could be due to permission related issue.

Action: Check if neccessary permissions are present to create the directory {0}.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06175: Could not create response file.

Cause: Unable to create the response file {0}. This could be due to permission related issue.

Action: Check if neccessary permissions are present to create the response file {0}.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06176: {0} is not a valid directory for generating response file.

Cause: {0} could be a non existent directory or it could already contain an existing response file.

Action: Choose a different location or clean the directory {0}.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06177: Unable to use the specified response file location.

Cause: {0} file already exists under the given directory {1}.

Action: Specify different directory for response file.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06178: Unable to use the specified wallet file location.

Cause: {0} wallet file already exists under the given directory {1}.

Action: Specify different directory for wallet file.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06179: An internal error occurred while initializing.

Cause: Initialization of response file reader failed.

Action: Check the log for more details and contact the administrator to resolve the issue
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06180: Unsupported RCU Operation

Cause: No value was specified for the property "operation".

Action: Refer to the RCU guide or command line help for a list of valid RCU operations.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06181: Unsupported RCU Operation

Cause: Value provided for the property "operation" was not a valid RCU operation.

Action: Refer to the RCU guide or command line help for a list of valid RCU operations.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06182: No value specified for a mandatory property.

Cause: Value for property "{0}" was not provided in the response file.

Action: Provide valid value in the response file.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06183: Some properties in the response file are missing values.

Cause: Some of the mandatory properties in the response file were missing values.

Action: Refer to the log for details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06184: An internal error occurred while initializing.

Cause: Error encountered while reading the response file.

Action: Check the logs for more details and contact the administrator to resolve the issue.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06185: Invalid response file.

Cause: Response file was either null or it did not have read permissions.

Action: Provide a valid response file.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06186: Invalid "schemaPrefix" for generating wallet.

Cause: "schemaPrefix" cannot be empty while generating wallet.

Action: Provide a valid "schemaPrefix".
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06187: Invalid "dbUser" for generating wallet

Cause: "dbUser" could not be empty while generating wallet.

Action: Provide a valid "dbUser".
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06188: Invalid "schemaName" for generating wallet

Cause: "schemaName" could not be empty while generating wallet.

Action: Provide a valid "schemaName".
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06189: Unable to create Oracle wallet

Cause: Directory {0} was either not found or was not a directory.

Action: Provide a valid directory path.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06190: Unable to create Oracle Wallet at {0}.

Cause: An internal error occurred while creating Oracle Wallet at {0}.

Action: Check the log for more details and contact the administrator to resolve the issue.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06191: Unable to get wallet data for alias {0} from {1}.

Cause: A file read error occurred while reading data from wallet {1}

Action: Make sure that the wallet file has read permissions.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06192: Specified wallet location is not a valid directory.

Cause: Wallet location specified did not exist.

Action: Provide a valid wallet location.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06193: Wallet alias is not valid.

Cause: Specified value for wallet alias was empty.

Action: Provide a valid wallet alias.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06194: Unable to add entry {0} to wallet at {1}.

Cause: A file read or write error or a security error was thrown while writing into wallet at {1}.

Action: Check the log for more details and contact the administrator to resolve the issue.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06195: Invalid wallet directory location for creating wallet.

Cause: Specified location {0} had wallet file in it.

Action: Provide different directory location for creating wallet.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06196: Unable to create directory {0}.

Cause: A file read or write error occurred while creating directory {0}.

Action: Check if you have permissions to create the directory {0}. Contact the administrator if problem persists.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06197: Invalid arguments specified for the {1} operation.

Cause: Some of the argument(s) specified, "{0}" were not valid for the {1} operation.

Action: Refer to the RCU guide or command line help for list of valid arguments.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06198: invalid SSL arguments.

Cause: SSL authentication requires client and server authentication or encryption details.

Action: Provide the properties as key-value pair separated by comma using the argument "-sslArgs".
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06199: invalid "serverDN" value.

Cause: Value for "serverDN" was not provided. "serverDN" is a mandatory parameter for SSL connection.

Action: Provide a valid value for "serverDN" argument. To disable the serverDN check, provide the property "oracle.net.ssl_server_dn_match=false" in "-sslArgs".
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06200: Error while validating TDE check on database.

Cause: TDE was not enabled in the database.

Action: Specify "-encryptTablespace false" argument.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06202: RCUCommandLine Error - validation of RCU command line options failed.

Cause: Invalid command line option was specified.

Action: Provide one of the following options:
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06203: Invalid script location is provided.

Cause: Script Location was not provided or was empty string.

Action: Specify a valid location.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06204: Specified script location is invalid.

Cause: The specified directory did not exist.

Action: Specify an existing directory.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06205: Database type validation failed.

Cause: Invalid database type. Valid database types are: {0}

Action: Provide valid database type.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06206: invalid Component {0}.

Cause: Skipping {0} component as config or storage file was missing for the component.

Action: Specify a valid component name.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06250: Internal Error while parsing component metadata files.

Cause: Specified schema base definition {0} not found in the Oracle Home. Schema base definition of {1} was wrong.

Action: Check the logs for more details and contact the administrator to resolve the issue.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06251: Consolidated schema component not specified.

Cause: Component "{0}" is consolidated to the schema of the component "{1}". For dropping consolidated schema, the component "{1}" has to be provided for drop operation.

Action: Specify "{0}" in the components to be dropped.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06252: Consolidated component is not found in the Oracle Home.

Cause: Component "{0}" is consolidated to the schema of the component "{1}". For dropping consolidated schema, all the consolidated components have to be present in the Oracle Home.

Action: Invoke dropRepository from Oracle Home which contains the component {0}.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06253: Tablespace configuration of component "{0}" cannot be overridden.

Cause: Component "{0}" is consolidated to the schema of the component "{1}". "{0}" could not configure custom tablespace.

Action: Override the tablespace configuration of the component "{0}" which will be used by the component "{1}" also.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06301: invalid password.

Cause: Password was not provided for {0} in the wallet.

Action: Provide a valid password.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06302: Command line arguments validation failed.

Cause: Value for "{0}" was not provided.

Action: Provide values for both "-compInfoXMLLocation" and "-storageXMLLocation" or invoke without any of these arguments.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-06303: internal error

Cause: Value for "{0}" was not provided in rcu properties file.

Action: Provide valid values for properties "COMPONENT_INFO_LOCATION" and "STORAGE_INFO_LOCATION" in rcu properties file located at {0}
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-07000: The referenced variable validation fails.

Cause: The referenced variable "{0}" is not defined.

Action: Provide the required variable value.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-07001: invalid database password.

Cause: Database password was not provided.

Action: Specify valid value for database password.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-07002: Validation of SSL arguments fails.

Cause: SSL arguments are not provided in proper format.

Action: Refer help for details.
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-07003: Command line argument validation fails.

Cause: Invalid command line argument.

Action: Refer help for supported arguments. Remove invalid option
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-07004: ServerDN validation fails.

Cause: Value for serverDN is not provided. "serverDN" is mandatory parameter for SSL connection.

Action: To disable the serverDN check, provide the property "oracle.net.ssl_server_dn_match=false" in "-sslArgs"
Level: 1

Type: ERROR

Impact: Repository Configuration

RCU-07005: Validation of log location failed.

Cause: Could not create the log directory {0}.

Action: Make sure that the specified log directory and system temporary directory has write permission.
Level: 1

Type: ERROR

Impact: Repository Configuration

44 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-67000: Creation of Reports Server instance {0} on machine {1} failed

Cause: Attempt to create reports server instance failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67001: Removal of Reports Server instance {0} failed

Cause: Attempt to remove reports server instance failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67002: Unable to register reports server configuration mbeans

Cause: Reports server configuration mbeans registration failed

Action: For assistance, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

REP-67004: Validation of component failed: {0}

Cause: Component is not successfully validated for attempted operation

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67100: Unable to calculate checksum of file {0}

Cause: Checksum calculation of file failed

Action: For assistance, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

REP-67101: Error in replicating reports server configuration

Cause: Replication of configuration from AdminServer machine to managed server failed

Action: For assistance, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

REP-67200: Creation of Reports Tools instance {0} on machine {1} failed

Cause: Attempt to create reports tools instance failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67201: Removal of Reports Tools instance {0} failed

Cause: Attempt to remove reports tools instance failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67202: Unable to register reports tools configuration mbeans

Cause: Reports tools configuration mbeans registration failed

Action: For assistance, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

REP-67204: Validation of component failed: {0}

Cause: Component is not successfully validated for attempted operation

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67300: Unable to calculate checksum of file {0}

Cause: Checksum calculation of file failed

Action: For assistance, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

REP-67301: Error in replicating reports tools configuration

Cause: Replication of configuration from AdminServer machine to managed server failed

Action: For assistance, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

REP-67400: Creation of Reports Bridge instance {0} on machine {1} failed

Cause: Attempt to create reports bridge instance failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67401: Removal of Reports Bridge instance {0} failed

Cause: Attempt to remove reports bridge instance failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67402: Unable to register reports bridge configuration mbeans

Cause: Reports bridge configuration mbeans registration failed

Action: For assistance, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

REP-67404: Validation of component failed: {0}

Cause: Component is not successfully validated for attempted operation

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67500: Unable to calculate checksum of file {0}

Cause: Checksum calculation of file failed

Action: For assistance, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

REP-67501: Error in replicating reports bridge configuration

Cause: Replication of configuration from AdminServer machine to managed server failed

Action: For assistance, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

REP-67550: Component {0} already exists in domain

Cause: Component with given name already exists in domain

Action: Provide a unique component name
Level: 1

Type: ERROR

Impact: Other

REP-67551: Component {0} cannot be removed because it is in state {1}

Cause: Component is not in following states : SHUTDOWN, FAILED_NOT_RESTARTABLE, FAILED

Action: Shutdown the component
Level: 1

Type: ERROR

Impact: Other

REP-67552: Component is not configured to OID

Cause: Component is not associated to OID

Action: Associate component to OID
Level: 1

Type: ERROR

Impact: Other

REP-67600: Connect to a WebLogic server before using this command

Cause: Not connected to Weblogic server

Action: Connect to Weblogic server using appropriate WLST command
Level: 1

Type: ERROR

Impact: Other

REP-67601: createReportsServerInstance command failed

Cause: Attempt to create reports server instance failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67602: deleteReportsServerInstance command failed

Cause: Attempt to remove reports server instance failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67603: Argument {0} is not valid

Cause: Invalid argument provided to WLST command

Action: Provide correct argument to WLST command
Level: 1

Type: ERROR

Impact: Other

REP-67604: The following required arguments are missing :{0}

Cause: Required argument not provided to WLST command

Action: Provide required argument to WLST command
Level: 1

Type: ERROR

Impact: Other

REP-67608: associateStandaloneServer command failed

Cause: Association of reports server to OID failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67610: dissociateStandaloneServer command failed

Cause: Dissociation of reports server from OID failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67612: associateInprocessServer command failed

Cause: Association of reports server to OID failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67614: dissociateInprocessServer command failed

Cause: Dissociation of reports server from OID failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67700: Connect to a WebLogic server before using this command

Cause: Not connected to Weblogic server

Action: Connect to Weblogic server using appropriate WLST command
Level: 1

Type: ERROR

Impact: Other

REP-67701: createReportsToolsInstance() failed

Cause: Attempt to create reports tools instance failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67702: deleteReportsToolsInstance() failed

Cause: Attempt to remove reports tools instance failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67703: Argument {0} is not valid

Cause: Invalid argument provided to WLST command

Action: Provide correct argument to WLST command
Level: 1

Type: ERROR

Impact: Other

REP-67704: The following required arguments are missing :{0}

Cause: Required argument not provided to WLST command

Action: Provide required argument to WLST command
Level: 1

Type: ERROR

Impact: Other

REP-67800: Connect to a WebLogic server before using this command

Cause: Not connected to Weblogic server

Action: Connect to Weblogic server using appropriate WLST command
Level: 1

Type: ERROR

Impact: Other

REP-67801: createReportsBridgeInstance() failed

Cause: Attempt to create reports bridge instance failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67802: deleteReportsBridgeInstance() failed

Cause: Attempt to remove reports bridge instance failed

Action: Check the actual error message and take appropriate action
Level: 1

Type: ERROR

Impact: Other

REP-67803: Argument {0} is not valid

Cause: Invalid argument provided to WLST command

Action: Provide correct argument to WLST command
Level: 1

Type: ERROR

Impact: Other

REP-67804: The following required arguments are missing :{0}

Cause: Required argument not provided to WLST command

Action: Provide required argument to WLST command
Level: 1

Type: ERROR

Impact: Other

REP-67900: Reports 12c Application not found deployed for managed server {0}

Cause: Reports 12c Application not found deployed for managed server

Action: Start reports managed servers once so that reports 12c applications get automatically deployed. Then shutdown managed servers.
Level: 1

Type: ERROR

Impact: Other

REP-67901: Component of type {0} and name {1} does not exist in 12c domain

Cause: Reports system component not found in 12c domain

Action: Use WLST command to create reports component in 12c domain
Level: 1

Type: ERROR

Impact: Other

REP-67902: Config file not found : {0}

Cause:

Action: Reports installation is corrupted
Level: 1

Type: ERROR

Impact: Other

REP-67903: Topology document parsing error

Cause:

Action: Reports 11g domain is corrupted
Level: 1

Type: ERROR

Impact: Other

REP-67904: Topology document not found : {0}

Cause: Reports 11g domain is corrupted or is already upgraded

Action: Contact the system administrator
Level: 1

Type: ERROR

Impact: Other

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

45 SDP-25001 to SDP-26551

SDP-25001: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25002: Unable to create JNDI Context.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check the JNDI Context initialization parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-25003: Unable to create an instance of Driver Locator.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25004: Message could not be delivered to client due to rollback at the client application. Message ID {0}.

Cause: The client did rollback on the transaction, hence the message could not be re-delivered to the client.

Action: Check why the client did rollback
Level: 1

Type: WARNING

Impact: Process

SDP-25005: Failed to create Sending Core instance.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25006: Failed to remove an EJB instance.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25007: An error occurred while processing an outbound message.

Cause: The outbound JMS message does not contain a valid message or request information.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25008: An error occurred while processing an outbound message.

Cause: An exception has occurred while processing the outbound message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25009: An error occurred while storing a message.

Cause: An exception has occurred while processing the message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25010: An error occurred while sending an outbound message.

Cause: An exception has occurred while processing the outbound message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25011: An error occurred while transforming an outbound message.

Cause: An exception has occurred while processing the outbound message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25012: An error occurred while processing error statuses.

Cause: An exception has occurred while processing error statuses.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25013: An error occurred while resending an outbound message.

Cause: An exception has occurred while processing the resent outbound message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25014: A JMS exception occurred, trying to recover

Cause: A JMS exception occurred

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25015: There are no transformed messages of message {0} for recipients {1}. Skipping message delivery to these recipients.

Cause: An error has occurred while transforming an outbound message.

Action: Use the messageId to trace the message handling.
Level: 1

Type: WARNING

Impact: Process

SDP-25016: Could not get TimerService or Timers.

Cause: Could not get TimerService or Timers.

Action: Check application server status.
Level: 1

Type: ERROR

Impact: Process

SDP-25017: Could not cancel timer.

Cause: Could not cancel timer

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25020: Unable to schedule a timed failover event.

Cause: An exception has occurred while scheduling a timed failover event.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25021: An error occurred while processing a timed failover event.

Cause: An exception has occurred while processing a timed failover event.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25022: Unable to schedule a timed resend event.

Cause: An exception has occurred while scheduling a timed resend event.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25030: Unable to schedule a timer to refresh the driver locator cache.

Cause: An exception has occurred while scheduling a timer to refresh the driver cache.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25032: An error occurred while registering driver information {0}.

Cause: An exception has occurred while registering the driver information.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25033: An error occurred while unregistering driver information {0}.

Cause: An exception has occurred while unregistering the driver information.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25034: There are total {0} registered User Messaging Drivers. Driver(s): {1}.

Cause: A Messaging Driver registered with the Messaging Server

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25035: Messaging store not found.

Cause: An exception has occurred while attempting to find the messaging store.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25036: An error occurred while registering driver information at User preference subsystem {0}.

Cause: An exception has occurred while registering the driver information at User preference subsystem.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25037: An error occurred while unregistering driver information at User preference subsystem {0}.

Cause: An exception has occurred while unregistering the driver information at User preference subsystem.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25040: Unable to create an instance of CommandReceiverBean.

Cause: An exception has occurred while attempting to process a command.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25042: An error occurred while processing a command message.

Cause: An exception has occurred while attempting to process a command.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25043: An unknown command message was received, ignoring: {0}.

Cause: The engine received an unknown command message and was unable to process the command.

Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.
Level: 1

Type: WARNING

Impact: Process

SDP-25055: Failed to create Receiving Core instance.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25057: An error occurred while processing an inbound JMS message.

Cause: The inbound JMS message does not contain a valid message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25058: An error occurred while processing an inbound message.

Cause: An exception has occurred while processing the inbound message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25059: An unknown JMS message is received, ignoring: {0}.

Cause: The engine received an unknown JMS message and was unable to process it.

Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.
Level: 1

Type: WARNING

Impact: Process

SDP-25060: There is no application that has registered this address as an access point. The message will be delivered when the access point is registered. Address={0}

Cause: There is no application that has registered this recipient address as an access point.

Action: Register the access point. The message is kept in a pending queue until an application registers a corresponding access point.
Level: 1

Type: WARNING

Impact: Process

SDP-25061: An error occurred while processing inbound message statuses.

Cause: An exception has occurred while attempting to process inbound message statuses.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25063: Status not delivered to client since no client information found for application {0}.

Cause: There is no application client information stored.

Action: Check the log file for additional information.
Level: 1

Type: WARNING

Impact: Process

SDP-25064: An error occurred while recording a status processing update.

Cause: An exception has occurred while attempting to record a status processing update.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25065: An error occurred while sending a message to failover address {0}.

Cause: An exception has occurred while sending out a failover message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25066: An error occurred while processing an outbound message status.

Cause: An exception has occurred while attempting to process an outbound message status.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25070: Unable to retrieve messaging engine sending and/or receiving queues from configuration.

Cause: A severe configuration error has occurred and the system is not functional.

Action: Check the messaging engine configuration and the stack trace, if available, for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25081: An error occurred while adding a message converter rule: {0}.

Cause: An invalid message converter rule was provided.

Action: Check the log file for additional details.
Level: 1

Type: WARNING

Impact: Process

SDP-25082: No predicates and/or devices matched. Ignoring converter rule (MIME type: {0}, delivery type: {1}, predicate: {2}).

Cause: An invalid message converter rule was provided.

Action: Check the log file for additional details.
Level: 1

Type: WARNING

Impact: Process

SDP-25083: Message content is not an instance of MimeMultipart.

Cause: An invalid message content was provided to this converter.

Action: Check the current log file for additional details. Check User Messaging Service Javadoc on OTN for more information on sending MimeMultipart messages.
Level: 1

Type: WARNING

Impact: Process

SDP-25085: Message {0} has a nonunique Message ID or recipient, and does not look like a redelivery attempt.

Cause: A message was sent or received that appears to be a duplicate of an already processed message; re-enqueuing message with delay specified.

Action: Ensure that messages are assigned unique Message IDs.
Level: 1

Type: WARNING

Impact: Process

SDP-25087: No matching driver found for {0} = {1}.

Cause: No matching driver found for the given property.

Action: Check that there is a correctly deployed and configured driver matching the given property.
Level: 1

Type: WARNING

Impact: Process

SDP-25088: Unable to refresh the driver locator cache, due to exception.

Cause: An error has occurred while refreshing the driver locator cache.

Action: Check the reported error message and correct any configuration problems.
Level: 1

Type: ERROR

Impact: Process

SDP-25089: Status could not be delivered to client due to rollback at the client application. Message ID {0} {1}.

Cause: The client did rollback on the transaction, hence the status could not be re-delivered to the client.

Action: Check why the client did rollback
Level: 1

Type: WARNING

Impact: Process

SDP-25101: Caught a database exception.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25106: Conflicting recipient IDs for Message {0}.

Cause: A conflict between recipient identifiers has been detected.

Action: Ensure that applications are using unique Message IDs.
Level: 1

Type: WARNING

Impact: Process

SDP-25107: Message ID {0} in Status object does not match previously recorded Message ID {1}.

Cause: A status object returned from a driver contained a different Message ID than expected.

Action: Ensure that drivers are mapping Gateway IDs to Message IDs correctly.
Level: 1

Type: WARNING

Impact: Process

SDP-25109: Failed to initialize persistence context.

Cause: An exception has occurred while initializing the persistence context.

Action: Check the stack trace for more details.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25202: Parameter {0} is missing in SOAPMessageContext sent from client. Generating default value.

Cause: The client application sent a message without required attribute.

Action: Make sure the client application add ApplicationName, ApplicationInstanceName, and ClientType to the SOAPMessageContext.
Level: 1

Type: WARNING

Impact: Process

SDP-25250: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25251: Messaging Exception while processing Parlay X request.

Cause: A Messaging Exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25252: Exception while initializing Parlay X Messaging servlet.

Cause: An exception occurred while initializing the Parlay X Messaging servlet.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25253: Exception while initializing Parlay X Messaging content servlet.

Cause: An exception occurred while initializing the Parlay X Messaging content servlet.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25254: Exception while processing SOAP attachment content.

Cause: An exception occurred while processing message content in a SOAP attachment.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25255: Message contains multiple attachments. All but first attachment will be ignored.

Cause: The client application sent a message with multiple attachment parts.

Action: Client applications should send one attachment part per message. Complex content should be sent as a MIME Multipart object.
Level: 1

Type: WARNING

Impact: Process

SDP-25256: Parameter {0} is missing in SOAPMessageContext sent from client. Generating default value.

Cause: The client application sent a message without required attribute.

Action: Make sure the client application add ApplicationName, ApplicationInstanceName, and ClientType to the SOAPMessageContext.
Level: 1

Type: WARNING

Impact: Process

SDP-25257: Error initializing JAXP DatatypeFactory. Some data types may not be converted correctly.

Cause: Could not acquire instance of class javax.xml.datatype.DatatypeFactory. Marshalling/unmarshalling of some XML elements may not happen correctly.

Action: Ensure that the server's JAXP framework is configured correctly.
Level: 1

Type: WARNING

Impact: Process

SDP-25300: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25301: JNDI context is null.

Cause: JNDI context was null.

Action: See the Javadoc on Oracle Technology Network (OTN) for more information about how to instantiate a JNDI context.
Level: 1

Type: ERROR

Impact: Process

SDP-25302: EJB home for UserPrefsService is null.

Cause: EJB home for UserPrefsService is null.

Action: See the Javadoc on Oracle Technology Network (OTN) for more information about how to specify an EJB home.
Level: 1

Type: ERROR

Impact: Process

SDP-25303: Unable to connect to User Messaging Service (UMS) server at {0}.

Cause: EJB Naming Exception was caught when creating a UserPrefsServices object.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25304: EJB Remote Exception was caught at server {0}.

Cause: EJB Remote Exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25305: EJB Create Exception was caught at server {0}.

Cause: EJB Create Exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25306: XML Document object is null.

Cause: XML Document object is null.

Action: Specify a valid XML document object.
Level: 1

Type: ERROR

Impact: Process

SDP-25307: No file to upload. File name is not set.

Cause: The file name to be uploaded was not set.

Action: Invoke setFileName() to set the file name.
Level: 1

Type: ERROR

Impact: Process

SDP-25308: The file, {0}, cannot be read.

Cause: The file cannot be read.

Action: Check the file.
Level: 1

Type: ERROR

Impact: Process

SDP-25309: File not found: {0}.

Cause: The file with the given file name does not exist.

Action: Check to see if the path and file name are correct. File name must be in /path/filename or file://path/filename format.
Level: 1

Type: ERROR

Impact: Process

SDP-25311: The document cannot be uploaded. Parser and stack are out of sync. Tag name: {0} Local name: {1}.

Cause: The document cannot be uploaded because parser and stack were out of sync.

Action: Fix mismatched tags.
Level: 1

Type: ERROR

Impact: Process

SDP-25312: Provisioning Exception was caught.

Cause: Provisioning Exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25314: Rule {0} is already defined.

Cause: Rule with the same name was already defined.

Action: Choose a different rule name to avoid conflict.
Level: 1

Type: ERROR

Impact: Process

SDP-25316: Input parameter, UserPrefsServices, is null.

Cause: The UserPrefsServices object was null.

Action: Pass a valid UserPrefsServices object as a parameter. Check User Messaging Service Javadoc on OTN for more information.
Level: 1

Type: ERROR

Impact: Process

SDP-25317: Required input parameter, UserID, is null.

Cause: Failed to invoke method, because required input parameter, UserID, is null.

Action: Pass a valid UserID. Check User Messaging Service Javadoc on OTN for more information.
Level: 1

Type: ERROR

Impact: Process

SDP-25318: Invalid input parameter. DeviceAddress object is null.

Cause: Input parameter, DeviceAddress object, is null.

Action: Pass a valid DeviceAddress object. Check User Messaging Service Javadoc on OTN for more information.
Level: 1

Type: ERROR

Impact: Process

SDP-25319: UserRuleSet is not set. Call initProcessor() first.

Cause: UserRuleSet object is null.

Action: Call initProcessor() first to complete initialization.
Level: 1

Type: ERROR

Impact: Process

SDP-25320: Rule Set is null.

Cause: The Rule Set was not available or could not be created.

Action: Use a valid Rule Set.
Level: 1

Type: ERROR

Impact: Process

SDP-25321: XML String representing the Rule Set is null.

Cause: The XML document element representing the Rule Set was null or empty.

Action: Use a valid Rule Set XML element.
Level: 1

Type: ERROR

Impact: Process

SDP-25322: User Rule Set is null.

Cause: The User Rule Set was not available or could not be created.

Action: Use a valid User Rule Set object.
Level: 1

Type: ERROR

Impact: Process

SDP-25323: User Rule Set is inconsistent. See exception for more details.

Cause: User Rule Set is inconsistent.

Action: Check User Rule Set for consistency.
Level: 1

Type: ERROR

Impact: Process

SDP-25324: XML document is invalid. See exception for details.

Cause: XML document is invalid. See stacktrace for more details.

Action: Validate the XML document.
Level: 1

Type: ERROR

Impact: Process

SDP-25325: Cannot serialize Rule Session.

Cause: Cannot serialize Rule Session, which is not critical.

Action: No action needed.
Level: 1

Type: WARNING

Impact: Process

SDP-25326: Filter XML is null.

Cause: The Preference Rules were missing or inconsistent.

Action: Use a well-formed User Preference XML document.
Level: 1

Type: ERROR

Impact: Process

SDP-25327: Cannot create Rule Session.

Cause: Cannot create Rule Session.

Action: No action needed.
Level: 1

Type: WARNING

Impact: Process

SDP-25328: UserPrefsException was caught.

Cause: UserPrefsException was caught.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25329: Rule {0} does not exist.

Cause: The expected rule was not found.

Action: Check the rule by name on the User Preference page.
Level: 1

Type: ERROR

Impact: Process

SDP-25330: Business Term Type has changed. Term = {0}.

Cause: Business Term Type has changed.

Action: Recheck the Preference Rules.
Level: 1

Type: WARNING

Impact: Process

SDP-25331: Cannot instantiate User Preferences Services.

Cause: Cannot instantiate User Preferences Services due to an initialization error.

Action: Check User Prefs Services configuration.
Level: 1

Type: WARNING

Impact: Process

SDP-25334: Device name is null.

Cause: Device name is null.

Action: Provide a valid Device name.
Level: 1

Type: ERROR

Impact: Process

SDP-25336: Input parameter, UserPrefsObject, is null.

Cause: Required parameter, UserPrefsObject, is null.

Action: Provide a valid UserPrefsObject.
Level: 1

Type: ERROR

Impact: Process

SDP-25337: Failed to move a rule: origin rule number is out of the range of existing rules.

Cause: Origin rule number is not valid.

Action: Specify a valid rule number.
Level: 1

Type: ERROR

Impact: Process

SDP-25341: The order of calling methods is wrong.

Cause: The order of calling methods is wrong.

Action: Check the order of the methods being called.
Level: 1

Type: ERROR

Impact: Process

SDP-25343: No devices are defined.

Cause: Tried to call delivery preferences without defining devices.

Action: Define devices for use with delivery preferences.
Level: 1

Type: ERROR

Impact: Process

SDP-25344: Invalid action {0} is found and ignored.

Cause: An invalid action was detected.

Action: Use one of the valid actions: BROADCAST, FAIL_OVER, and DO_NOT_SEND.
Level: 1

Type: WARNING

Impact: Process

SDP-25345: Runtime exception was caught.

Cause: Runtime exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25346: No configured Business Terms are available, only system terms will be used.

Cause: Business Term configuration could not be read.

Action: Ensure that business term configuration is correct
Level: 1

Type: WARNING

Impact: Process

SDP-25347: Device {0} cannot be added because it is present in the list.

Cause: A device was present in the list already.

Action: Ensure that the device to be added is not in the device list.
Level: 1

Type: WARNING

Impact: Process

SDP-25348: Failed to move a device: device ID index number is out of the range of device list.

Cause: Device ID index number is not valid.

Action: Specify a valid device ID index number.
Level: 1

Type: ERROR

Impact: Process

SDP-25349: Name of rule is not set.

Cause: Rule name was not set.

Action: Set the name of the rule.
Level: 1

Type: ERROR

Impact: Process

SDP-25350: FilterOperation of a rule is not set.

Cause: FilterOperation of a rule was not set.

Action: Set the FilterOperation of the rule.
Level: 1

Type: ERROR

Impact: Process

SDP-25351: ActionOperation of a rule is not set.

Cause: ActionOperation of a rule was not set.

Action: Set the ActionOperation of the rule.
Level: 1

Type: ERROR

Impact: Process

SDP-25352: Condition of a rule is not set.

Cause: Condition of a rule was not set.

Action: Set the condition of the rule.
Level: 1

Type: ERROR

Impact: Process

SDP-25353: unable to send a BROADCAST message because no address is set.

Cause: An address has not been set for the BROADCAST action.

Action: Set at least one address for the BROADCAST action.
Level: 1

Type: ERROR

Impact: Process

SDP-25354: A failover address is not set for the FAIL_OVER action.

Cause: An address has not been set for the FAIL_OVER action.

Action: Set at least one address for the FAIL_OVER action.
Level: 1

Type: ERROR

Impact: Process

SDP-25356: Cannot persist device address {0} for user GUID {1}, because one already exists.

Cause: An identical device address already exists.

Action: Remove the conflicting device address, overwrite it, or specify a different address.
Level: 1

Type: WARNING

Impact: Process

SDP-25361: The Java VM does not support the encoding {0}.

Cause: The Java VM does not support the encoding used for XML string representing the RuleSet.

Action: Check your server Java VM and make sure it supports the encoding.
Level: 1

Type: ERROR

Impact: Process

SDP-25387: Rule fact for term {0} has been ignored as it does not have the correct type, {1}.

Cause: The fact from user or application had an incorrect data type.

Action: Provide the fact with the correct data type as indicated.
Level: 1

Type: WARNING

Impact: Process

SDP-25388: Device named {0} of user {1} not found.

Cause: The user does not have a device with that name.

Action: Check username and device name.
Level: 1

Type: WARNING

Impact: Process

SDP-25390: Failed to set default address of MESSAGING of user {0}.

Cause: Failed to set default address

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25400: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25403: Error in registering messaging Runtime MBeans.

Cause: Exception was thrown.

Action: Check stack trace
Level: 1

Type: ERROR

Impact: Process

SDP-25404: Error in unregistering messaging Runtime MBeans.

Cause: Exception was thrown.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25405: Naming exception thrown looking up Management Store: Unable to initialize SDP Messaging Runtime MBeans.

Cause: Naming exception thrown while looking up the Management Store EJB.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25406: Create exception thrown while creating Management Store: Unable to initialize SDP Messaging Runtime MBeans.

Cause: Create exception thrown while creating Management Store EJB.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25407: Exception initializing Runtime MBean.

Cause: An exception was thrown during runtime MBean initialization.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25408: Invalid query parameter: query field: {0}, query condition: {1}, query value: {2}.

Cause: Invalid combination of query parameters or invalid query value.

Action: Check stack trace.
Level: 1

Type: WARNING

Impact: Process

SDP-25409: Unable to initialize the composite type for the MBean.

Cause: OpenDataException was caught.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25410: Unable to convert to composite type and return composite data for the MBean. Name: {0}.

Cause: OpenDataException was caught.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25416: Error occurred while attempting to get the parent server MBean for {0}.

Cause: An exception was thrown while attempting to get the parent server MBean.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25500: Failed to schedule Timer.

Cause: Timer could not be scheduled in the TimerManager

Action: Check stack trace, diagnostic dump
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25501: Exception when delivering pending messages.

Cause: Exception when delivering pending messages

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25502: Unable to create JNDI Context.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check the JNDI Context initialization parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-25503: Unable to connect to the messaging server.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check that the messaging server is up. Check the JNDI Context initialization parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-25504: Unable to register application information with the messaging server.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check that the messaging server is up. Check the JNDI Context initialization parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-25505: Unable to enqueue outbound message.

Cause: Engine Sending Queue may not be available.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25506: Unable to get receiving queues from application information.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check the Application information properties.
Level: 1

Type: ERROR

Impact: Process

SDP-25507: Unable to enqueue inbound message status because no engine queues were found.

Cause: The client is not aware of any engine queues to enqueue the status.

Action: Check that the application is registered successfully with the messaging server.
Level: 1

Type: ERROR

Impact: Process

SDP-25508: Unable to enqueue inbound message status.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25510: An error occurred while attempting to retrieve the actual password from the credential store.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25511: An error occurred while dequeuing a message from the application receiving queue.

Cause: An invalid JMS message was dequeued by the Dispatcher MDB.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25512: An invalid message was dequeued from the application receiving queue: {0}.

Cause: An invalid JMS message was dequeued by the Dispatcher MDB.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25513: JNDI lookup of application callback listener failed.

Cause: An invalid callback listener was previously registered and could not be invoked.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25514: An error occurred while dispatching an inbound message to the application {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25515: An error occurred while dispatching an inbound status to the application {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25516: Message/Status listener not configured. Suspending messaging client MDB to disable asynchronous message/status callbacks.

Cause: Message/Status listener was not configured by the application.

Action: If the application requires asynchronous message/status callbacks, configure the listener information. Otherwise, ignore this warning.
Level: 1

Type: WARNING

Impact: Process

SDP-25517: Messaging client MDB suspend failed: {0}.

Cause: 1) The Messaging client was unable to access the MDB MBean because the container may not be in RUNNING state. 2) The server administrator username 'weblogic' does not exist.

Action: 1) Check the state of the container. Check the stack trace for more details. 2) Specify a valid server administrator username using the system property -Doracle.ums.admin.user and restart the server.
Level: 1

Type: WARNING

Impact: Process

SDP-25519: QueueWorker rejected.

Cause: QueueWorker rejected

Action: Check WorkManager configuration.
Level: 1

Type: ERROR

Impact: Process

SDP-25524: Client called the deprecated method acknowledge().

Cause: The method acknowledge is deprecated.

Action: Use global transactions instead to achieve reliable message reception.
Level: 1

Type: WARNING

Impact: Process

SDP-25532: An error occurred while retrieving the Application Information from the application JNDI context.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25541: An error occurred while generating received message statuses.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25542: Security principal in client EJB Context "{0}" does not match security principal in ApplicationInfo "{1}". This may cause permission errors during future Messaging Client operations.

Cause: The security principal in the current EJBContext is different from the ApplicationInfo security principal field specified when creating the Messaging Client instance (or the default value, if no principal was provided).

Action: Ensure that the security principals used by this application for all Messaging Client operations match one another.
Level: 1

Type: WARNING

Impact: Process

SDP-25543: The current authenticated user "{0}" does not match the configured security principal "{1}".

Cause: The security principal in effect for the current thread is different from the security principal field specified when creating the Messaging Client instance.

Action: Ensure that the security principals used by this application for all Messaging Client operations match one another, or avoid configuring a specific security principal.
Level: 1

Type: WARNING

Impact: Process

SDP-25700: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25701: Unable to instantiate class {0}.

Cause: Unable to instantiate a class.

Action: Check to see if that class is in classpath or not.
Level: 1

Type: ERROR

Impact: Process

SDP-25702: Unable to set content of Message object.

Cause: Unable to set content of a message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25703: Exception when getting cluster name for server {0}.

Cause: Could not get cluster name from RuntimeServiceMBean

Action: Check the stack trace for more details
Level: 1

Type: ERROR

Impact: Process

SDP-25704: Error in setMultiplePayload.

Cause: An error occurred in setMultiplePayLoad().

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25705: Exception printing message content.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25706: Failed to clone message content.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25707: Failed to clone headers. Message = {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25708: Unable to perform JNDI lookup of JMS QCF: {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25709: Unable to perform JNDI lookup.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25710: Exception caught when calling onMessage(), will rollback transaction.

Cause: Exception caught when calling onMessage(), will rollback transaction.

Action: Check log to get more information.
Level: 1

Type: WARNING

Impact: Process

SDP-25711: Received unknown object: {0} on queue {1}.

Cause: Received unknown object in JMS queue

Action: Check log to get more information.
Level: 1

Type: WARNING

Impact: Process

SDP-25712: Message received with invalid format: {0} on queue {1}.

Cause: Invalid message received on JMS queue

Action: Check log to get more information.
Level: 1

Type: ERROR

Impact: Process

SDP-25713: Unable to perform JNDI lookup of JMS Queue: {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25714: Failed to obtaining destination availability for queue with JNDI name: {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25715: Invalid format, skipping: {0}.

Cause: Invalid queue information.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25716: Error occurred in looking up QueueConnectionFactory in JNDI, skipping: {0}

Cause: Error occurred in looking up QueueConnectionFactory in JNDI.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25717: Error occurred in looking up Queue in JNDI, skipping: {0}.

Cause: Error occurred in looking up queue in JNDI.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25718: Error occurred in getQueueInfoList.

Cause: Error occurred in getQueueInfoList().

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25719: The JMS receiver could not connect to the JMS destination. The error was: {1}. Please ensure the destination is available at the JNDI name {0}. The JMS receiver will periodically attempt to resolve this destination and additional warnings may be issued.

Cause: The JMS receiver could not connect to the JMS destination.

Action: Check the JMS system resource and the JMS server for additional information.
Level: 1

Type: WARNING

Impact: Process

SDP-25725: Message serialization failed.

Cause: Failed to serialize message due to I/O Error.

Action: Ensure that content is being created according to recommendations for Message class.
Level: 1

Type: ERROR

Impact: Process

SDP-25728: Could not determine server platform type. Generic values will be used for platform-specific data.

Cause: The Java EE server platform could not be determined. Either this application is executing in a Java SE environment, or the Java EE server is configured incorrectly.

Action: If executing in a Java SE environment, no action is necessary. Otherwise ensure that Java Required Files module is deployed to this environment.
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25729: An exception occurred while enabling the WS-Security configuration: {0}.

Cause: An exception occurred while attaching a WS-Security policy to a web service client or endpoint.

Action: Ensure that any WS-Security policies are specified in the correct format.
Level: 1

Type: WARNING

Impact: Process

SDP-25730: QueueWorker got exception.

Cause: QueueWorker got exception.

Action: Check the log for related information.
Level: 1

Type: WARNING

Impact: Process

SDP-25731: Failed to find database entry to update. Id: {0}

Cause: Failed to find database entry to update.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25800: Oracle User Messaging Service configuration is successfully upgraded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25801: Shall upgrade driver {0} using configuration file at {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25802: Driver {0} upgraded using {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25803: Driver {0} already upgraded. Ignoring configuration in {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25804: Shall upgrade server {0} using configuration file at {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25805: Server {0} upgraded using {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25806: Server {0} already upgraded. Ignoring configuration in {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25807: Shall upgrade user preference configuration for {0} using file at {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25808: User preference configuration for {0} upgraded using {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25809: Invalid managed server entered. Continue upgrade to see if we still can do a remote copy of the 11g configuration files.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25810: Custom deployed UMS application {0} will be deleted from the domain.

Cause: Custom deployed UMS applications are not supported any longer.

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25811: Failed to read configuration for driver {0}, {1}. Probably due to targeted driver without configuration.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25812: Ignoring configuration for application {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25820: Error in upgrading Oracle User Messaging Service configuration. Reason: {0}

Cause: An unexpected error occurred during Oracle User Messaging Service configuration upgrade.

Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25821: Failed to read the configuration file {0}.

Cause: The configuration file is missing or in wrong format.

Action: Check if the configuration file exists with correct format. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25822: Failed to save the configuration at {0}.

Cause: Error occured while saving the configuration to the configuration file.

Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25823: Failed to delete the old configuration file at {0}.

Cause: Error occurred while deleting the old configuration file.

Action: Check the file system. Correct the problem before running the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Process

SDP-25824: Failed to parse the configuration file at {0}.

Cause: Error occured while parsing the configuration file.

Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Process

SDP-25825: Error during copy of configuration files from remote managed server {0}.

Cause: Old 11g configuration files where due to some problem not copied correct to the AdminServer. It could be that the plugin is missing information needed to connect to and copy the configuration from one of the managed servers. Or it could be that the sshd is not running on all the managed servers.

Action: Check the error messages in the log file to see what the problem is. Correct the problem before running the Upgrade Assistant again or perform a manual copy of the old configuration from the remote managed servers to the AdminServer.
Level: 1

Type: ERROR

Impact: Process

SDP-25826: Error connecting to remote managed server {0}.

Cause: It could be that the plugin is missing information needed to connect to one of the managed servers. Or it could be that the sshd is not running on all the managed servers.

Action: Check the error messages in the log file to see what the problem is. Correct the problem before running the Upgrade Assistant again or perform a manual copy of the old configuration from the remote managed servers to the AdminServer.
Level: 1

Type: ERROR

Impact: Process

SDP-25827: Neither the configuration nor the data entered by the user provides all information needed to copy the UMS 11g configuration files.

Cause: Upgrade Assistant does not have all information about the remote managed servers to be able to connect and copy the UMS 11g configuration files.

Action: Make sure to fill in name and address for all remote managed Servers that does not have this information configured.
Level: 1

Type: ERROR

Impact: Process

SDP-25850: Oracle User Messaging Service schema upgraded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25851: Oracle User Messaging Service schema upgrade is valid.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25852: Oracle User Messaging Service schema version {0} is the latest one. Upgrade is not required.

Cause: Specified Oracle User Messaging Service database schema version is the latest one. Upgrade is not required.

Action: No user action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25853: Oracle User Messaging Service schema upgrade is invalid.

Cause: Specified User Messaging Service schema was updated but is invalid.

Action: Restore the User Messaging Service schema from a backup and retry. Check the error messages in Oracle User Messaging Service component log files. Correct the problem before running the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Process

SDP-25854: The upgrade is not supported from Oracle User Messaging Service schema version of {0}.

Cause: An unsupported base schema version was being upgraded.

Action: Refer to the Oracle User Messaging Service Upgrade Guide for supported versions to upgrade.
Level: 1

Type: ERROR

Impact: Process

SDP-25855: Error in upgrading Oracle User Messaging Service schema. {0}

Cause: An unexpected error occurred during Oracle User Messaging Service schema upgrade.

Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25856: Oracle User Messaging Service schema status is invalid.

Cause: Specified Oracle User Messaging Service database schema was invalid.

Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25857: Error in Oracle User Messaging Service schema readiness check.

Cause: An unexpected error occurred during Oracle User Messaging Service schema readiness check.

Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: ERROR

Impact: Process

SDP-26000: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26001: Cannot create JNDI Context.

Cause: Cannot create JNDI Context.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26002: The driver {0} is operational

Cause: The driver is operational

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26003: Driver {0} is not configured with required properties. Driver disabled until configured.

Cause: Driver was not configured with all required properties.

Action: Configure this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26004: No Messaging Engine Queue information to enqueue status.

Cause: No Engine Queue information to enqueue status.

Action: Check that the Engine is deployed. Check Engine Queue information.
Level: 1

Type: ERROR

Impact: Process

SDP-26005: Dispatcher failed to find a driver.

Cause: Dispatcher failed to find a driver.

Action: Compare delivery type and content type between message and available drivers.
Level: 1

Type: WARNING

Impact: Process

SDP-26006: An error occurred while processing an outbound message.

Cause: An error occurred while processing an outbound message.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26007: No configuration was found for this Driver deployment: {0}. Driver disabled until a configuration is created.

Cause: No configuration was found for this Driver deployment.

Action: Create a configuration this SMPP Driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26008: Invalid configuration for driver {0}. Driver disabled until configured.

Cause: Invalid configuration for driver

Action: Correct the driver configuration.
Level: 1

Type: WARNING

Impact: Process

SDP-26009: Could not get JNDI InitialContext.

Cause: None

Action: None
Level: 1

Type: ERROR

Impact: Process

SDP-26010: Failed to start driver: {0}.

Cause: Failed to start driver.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26011: Failed to register driver in UMS engine: {0}.

Cause: Failed to register driver in UMS engine.

Action: Check stack trace and diagnostic dump for more details.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-26012: Timed out while waiting for SubDrivers to start: {0}.

Cause: Timed out while waiting for SubDrivers to start.

Action: Check stack trace and diagnostic dump for more details.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-26013: Failed to stop driver: {0}.

Cause: Unable to stop driver.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26014: Unable to process inbound message/status.

Cause: Exception occurred while processing inbound message/status.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26015: Unable to process command message.

Cause: Exception occurred while processing command message.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26016: Error occurred while attempting to get the parent server MBean for {0}

Cause: Error occurred while attempting to get the parent server MBean

Action: Check stack trace for more details
Level: 1

Type: ERROR

Impact: Process

SDP-26017: Failed to invoke registerDriverInfo() for driver: {0}

Cause: Exception thrown while invoking registerDriverInfo().

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26018: Invalid {0} value: {1}

Cause: The driver has been configured with an invalid property value.

Action: Review the driver configuration and ensure that the property is valid.
Level: 1

Type: WARNING

Impact: Process

SDP-26019: Error occurred while registering driver {0}

Cause: Error occurred while registering driver.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26020: Registration of driver {0} succeeded.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26021: Timed out while waiting for reply from Messaging engine.

Cause: The registration command timed out in the JMS queue because the Messaging engine is down or the system is under heavy load.

Action: Check if the Messaging engine is up and ensure the system is not under extremely heavy load.
Level: 1

Type: WARNING

Impact: Process

SDP-26022: Illegal DeliveryType specified, ignoring type {0}.

Cause: Illegal DeliveryType specified.

Action: Check message delivery type.
Level: 1

Type: ERROR

Impact: Process

SDP-26023: Benchmark logging is enabled for all inbound messages, which may slow down system performance. To disable it, unset environment variable sdpm_inbound_benchmark_logging and restart.

Cause: Benchmark logging is enabled when environment variable sdpm_inbound_benchmark_logging=true.

Action: To disable benchmark logging, unset environment variable sdpm_inbound_benchmark_logging and restart.
Level: 1

Type: WARNING

Impact: Process

SDP-26024: Registration of driver {0} did not complete. Current state is {1}. Will retry periodically until messaging server responds.

Cause: None

Action: None
Level: 1

Type: WARNING

Impact: Process

SDP-26025: Error when registering messaging driver Runtime MBeans for {0}.

Cause: Exception was thrown.

Action: Check stack trace
Level: 1

Type: ERROR

Impact: Process

SDP-26026: Error in unregistering messaging driver Runtime MBeans.

Cause: Exception was thrown.

Action: Check stack trace
Level: 1

Type: ERROR

Impact: Process

SDP-26027: Ignoring property {0} with unsupported Java type {1} during driver initialization.

Cause: A property with an unsupported Java type was found in 'usermessagingconfig.xml' during driver initialization.

Action: Use one of the following valid Java types: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Character
Level: 1

Type: WARNING

Impact: Process

SDP-26028: Ignoring property {0} with invalid value {1} and/or Java type {2} during driver initialization.

Cause: A property with an invalid value and/or unsupported Java type was found in 'usermessagingconfig.xml' during driver initialization.

Action: Use a valid value and/or one of the following valid Java types: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Character
Level: 1

Type: WARNING

Impact: Process

SDP-26029: Exception occurred during driver configuration initialization for {0}.

Cause: An exception occurred during driver configuration initialization.

Action: Check the stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-26030: Failed to schedule work {0}

Cause: An exception occurred while scheduling a work.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26031: Lookup of encoded credential value {0} in the credential store for property {1} failed during driver initialization. Passing through the value as-is.

Cause: A property with an invalid encoded credential value was found in 'usermessagingconfig.xml' during driver initialization.

Action: Use a valid encoded credential value and ensure the application has permission grants to access the credential store.
Level: 1

Type: WARNING

Impact: Process

SDP-26032: JNDI lookup of driver connection factory {0} failed with the following error message: {1}. Will retry until successful.

Cause: Driver connection factory could not be located in JNDI. Driver registration will not occur until this lookup succeeds.

Action: Wait for server startup to proceed. If driver registration does not occur, ensure that the driver connection factory JNDI name is configured correctly.
Level: 1

Type: WARNING

Impact: Process

SDP-26033: Started messaging driver: {0}

Cause: Driver was started.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26034: Stopped messaging driver: {0}

Cause: Driver was stopped.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26035: JNDI lookup of server command endpoint {0} failed. Will retry until successful.

Cause: Messaging Server command module could not be located in JNDI. Driver registration will not occur until this lookup succeeds.

Action: Wait for server startup to proceed. If driver registration does not occur, ensure that the messaging server is deployed and started.
Level: 1

Type: WARNING

Impact: Process

SDP-26036: Unable to perform JNDI lookup.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26037: Unable to create JMSMessageReceiver

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26038: Failed to retrieve credential from credential store for user {0}

Cause: Failed to retrieve credential from credential store for the specified user.

Action: Check stack trace or error log.
Level: 1

Type: ERROR

Impact: Process

SDP-26039: Driver {0} does not have inbound configuration. No messages (including information about bounced emails) are received.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26040: Driver {0} does not have outbound configuration. Messages cannot be sent through this driver.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26041: An attempt to configure inbound for driver {0} was detected. All required properties was not configured so the whole configuration (inbound and outbound) will be invalidated. Driver disabled until configured.

Cause: An attempt to configure inbound for the driver was detected. All required properties was not configured so the whole configuration (inbound and outbound) will be invalidated. Driver disabled until configured.

Action: Remove inbound configuration or configure all required properties for this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26042: An attempt to configure outbound for driver {0} was detected. All required properties was not configured so the whole configuration (inbound and outbound) will be invalidated. Driver disabled until configured.

Cause: An attempt to configure outbound for the driver was detected. All required properties was not configured so the whole configuration (inbound and outbound) will be invalidated. Driver disabled until configured.

Action: Remove outbound configuration or configure all required properties for this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26043: Driver {0} lost connection to the external gateway. Will try to reconnect.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

SDP-26044: Driver {0} reconnected to the external gateway.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26100: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26101: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26102: Error while writing e-mail message content.

Cause: An exception has occurred while writing e-mail content and headers to an e-mail message.

Action: Check stack trace or error log.
Level: 1

Type: WARNING

Impact: Process

SDP-26103: Error while writing e-mail subject.

Cause: Cannot write the subject.

Action: Check stack trace or error log.
Level: 1

Type: WARNING

Impact: Process

SDP-26104: Recipient address error.

Cause: Recipient e-mail address has an error.

Action: Check and see if the recipient e-mail address is correct.
Level: 1

Type: WARNING

Impact: Process

SDP-26105: Unable to deliver to following address(es): {0} Reason: {1}

Cause: One or more recipient e-mail addresses had an error.

Action: Ensure that the e-mail address is correct.
Level: 1

Type: WARNING

Impact: Process

SDP-26106: Failed to send the e-mail message

Cause: Unable to login to SMTP server.

Action: Check SMTP server host name, port, user name, and password.
Level: 1

Type: WARNING

Impact: Process

SDP-26107: Failed to add header - name: {0} value: {1}

Cause: Unable to add an e-mail header to a multipart message

Action: Check the stack trace or error log.
Level: 1

Type: WARNING

Impact: Process

SDP-26108: Content type parsing error {0}.

Cause: Error occurred while trying to parse the content type.

Action: Check and see if the content type is specified correctly.
Level: 1

Type: WARNING

Impact: Process

SDP-26109: Caught exception while closing connection to e-mail server.

Cause: An exception was caught while closing connection.

Action: Check stack trace or error log.
Level: 1

Type: ERROR

Impact: Process

SDP-26110: Failed to start Email Driver

Cause: Failed to start Email Driver.

Action: Check stack trace or error log. Check e-mail driver parameters and make sure all email servers are running.
Level: 1

Type: ERROR

Impact: Process

SDP-26111: Failed to retrieve credential from credential store for user {0}

Cause: Failed to retrieve credential from credential store for the specified user.

Action: Check stack trace or error log.
Level: 1

Type: ERROR

Impact: Process

SDP-26112: Authentication failed: user={0}, host={1}:{2}, sslEnabled={3}

Cause: Authentication failed for the specified user, server, port, and sslEnabled parameters.

Action: Check stack trace or error log. Check the username, password, server, port, and sslEnabled parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-26118: Failed to open folder {0} for user {1}

Cause: Folder name is not correct or does not exist.

Action: Check folder name spelling.
Level: 1

Type: ERROR

Impact: Process

SDP-26119: Max retry limit reached for trying to connect to user {0}

Cause: Email driver has reached Max retry limit to connect to user.

Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.
Level: 1

Type: WARNING

Impact: Process

SDP-26122: An exception has been thrown when connecting to user {0}

Cause: Email driver could not connect to user.

Action: Check username and password. Make sure the user exists and is accessible.
Level: 1

Type: ERROR

Impact: Process

SDP-26123: Could not initialize Email Store for: user {0}, server {1}, folder {2}, sslEnabled {3}

Cause: Could not initialize Email Store for the specified user, server, folder, and sslEnabled parameters.

Action: Check stack trace or error log. Check the username, password, server, folder and sslEnabled parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-26126: Unrecoverable message - {0}

Cause: failed to recover an e-mail message

Action: Check stack trace or error log.
Level: 1

Type: WARNING

Impact: Process

SDP-26130: Ignoring property {0} with invalid value {1} during driver initialization.

Cause: A property with an invalid value was found in 'usermessagingconfig.xml' during driver initialization.

Action: Ensure the value configured value is valid.
Level: 1

Type: WARNING

Impact: Process

SDP-26131: Lookup of encoded credential value {0} in the credential store for property {1} failed during driver initialization.

Cause: A property with an invalid encoded credential value was found in 'usermessagingconfig.xml' during driver initialization.

Action: Use a valid encoded credential value and ensure the application has permission grants to access the credential store.
Level: 1

Type: WARNING

Impact: Process

SDP-26134: Email Driver {0} is not configured with incoming mail properties. No emails (including information about bounced emails) are received.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26135: Email Driver {0} is not configured with outgoing mail properties. Emails cannot be sent through this driver.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26136: Driver property OutgoingDefaultFromAddr is deprecated. Use DefaultSenderAddress instead.

Cause: Driver property OutgoingDefaultFromAddr in 'usermessagingconfig.xml' is deprecated.

Action: Use DefaultSenderAddress instead.
Level: 1

Type: WARNING

Impact: Process

SDP-26137: Both DefaultSenderAddress and the deprecated OutgoingDefaultFromAddr is configured in 'usermessagingconfig.xml'. DefaultSenderAddress will be used.

Cause: Both OutgoingDefaultFromAddr and DefaultSenderAddress is configured in 'usermessagingconfig.xml'. DefaultSenderAddress will be used.

Action: Remove configuration for OutgoingDefaultFromAddr.
Level: 1

Type: WARNING

Impact: Process

SDP-26138: Message was not delivered. No valid sender(From) address available.

Cause: No sender address set in message and DefaultSenderAddress is not configured in 'usermessagingconfig.xml'.

Action: Set sender(From) address in message or set DefaultSenderAddress in 'usermessagingconfig.xml'.
Level: 1

Type: WARNING

Impact: Process

SDP-26150: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26151: Failed to process a received message in SMPP driver, because driver context is null

Cause: Driver context is null

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26152: WorkManager object is null in SMPP driver.

Cause: The caller of setWorkManager() passed in a null WorkManager object as an argument

Action: Make sure WorkManager object is not null.
Level: 1

Type: ERROR

Impact: Process

SDP-26153: Failed to connect to server, host: {0}, port: {1} (local address: {2}, local port: {3})

Cause: Failed to connect to server with the specified parameters.

Action: Check the stack trace and the specified parameters. Ensure that the network is operational.
Level: 1

Type: ERROR

Impact: Process

SDP-26155: unable to initialize SMPP driver, because a driver attribute, sms.account.id, is not set.

Cause: The account ID was not set.

Action: Set the correct account information.
Level: 1

Type: ERROR

Impact: Process

SDP-26156: Failed to initialize SMPP Driver because driver attributes sms.server.host, sms.server.transmitter.port or sms.server.receiver.port is not set.

Cause: SMSC server or account information is not correct or missing.

Action: Check those parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-26158: Caught exception while closing connection

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26159: Illegal data length value from SMSC received and ignored: {0}

Cause: SMPP Driver has detected a corrupted data field from SMSC and it is trying to recover.

Action: This error suggests communication errors between SMPP driver and SMSC. Check to see if this driver supports that SMSC.
Level: 1

Type: WARNING

Impact: Process

SDP-26160: No configuration was found for this SMPP Driver deployment: {0}. Driver disabled until a configuration is created.

Cause: No configuration was found for this SMPP Driver deployment.

Action: Create a configuration this SMPP Driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26161: Starting SMPP Driver: {0}

Cause: SMPP Driver resource adapter initialization.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26163: Data stream ended unexpectedly while reading packet from SMSC

Cause: The data stream ended unexpectedly while reading a packet from the SMSC. Message or command will be dropped.

Action: None.
Level: 1

Type: WARNING

Impact: Process

SDP-26164: Failed to bind receiver connection; will retry until bind operation is successful.

Cause: Could not bind to the SMSC as a receiver. Bind operation will be retried periodically until it is successful.

Action: None required. Change value of configuration parameter "BindRetryDelay" to adjust retry interval.
Level: 1

Type: WARNING

Impact: Process

SDP-26165: Lookup of encoded credential value for account {0} in the credential failed during driver initialization.

Cause: Lookup of encoded credential value in the credential failed during driver initialization.

Action: Check the stack trace for more details. Ensure that the encoded indirect password and the credential store are properly configured.
Level: 1

Type: WARNING

Impact: Process

SDP-26166: SMPP Driver {0} is not configured with all required properties. Driver disabled until configured.

Cause: SMPP Driver was not configured with all required properties.

Action: Configure this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26200: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26205: Exception while getting content from message with id={0}

Cause: Exception while getting content from message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26213: Exception while sending message - from: {0} to: {1}.

Cause: Exception while sending message.

Action: Check stack trace and recipient address
Level: 1

Type: WARNING

Impact: Process

SDP-26214: Caught an exception in XMPP driver while sending out a message.

Cause: An exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26225: Received Error Message. Code: {0} Text: {1}.

Cause: Received Error Message.

Action: Check error code and error message.
Level: 1

Type: WARNING

Impact: Process

SDP-26236: Got an exception when receiving a message.

Cause: Got an exception when receiving a message.

Action: Check to see if the message is well-formed.
Level: 1

Type: WARNING

Impact: Process

SDP-26300: A Twitter exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26301: Got an exception when receiving tweets.

Cause: An exception has occurred when receiving tweets.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26302: Got an exception when receiving direct messages.

Cause: An exception has occurred when receiving direct message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26303: Exception caught during attributes transferring of an inbound direct message.

Cause: An exception has occurred when transferring attributes of a direct message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26304: Exception caught during attributes transferring of an inbound tweet.

Cause: An exception has occurred when transferring attributes of a tweet.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26305: Got an exception when building an inbound UMS message from a received tweet or direct message.

Cause: An exception has occurred when rebuilding an inbound UMS message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26306: Required OAuth login information is missing or incomplete. Consumer key, consumer secret, access token, and/or access token secret is not set.

Cause: At least one of Twitter consumer key, consumer secret, access token, and access token secret is missing or not set.

Action: Check the log file for the missing field(s).
Level: 1

Type: ERROR

Impact: Process

SDP-26307: Required xAuth login information for user {0} is missing or incomplete. Both username and password are required.

Cause: Username or password is missing or not set.

Action: Check the log file for the missing field(s).
Level: 1

Type: ERROR

Impact: Process

SDP-26308: No configuration was found for this Twitter Driver deployment: {0}. Driver disabled until a configuration is created.

Cause: No configuration was found for this Twitter Driver deployment.

Action: Create a configuration this Twitter Driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26309: Twitter Driver {0} is not configured with all required properties. Driver disabled until configured.

Cause: Twitter Driver was not configured with all required properties.

Action: Configure this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26310: Twitter Driver not properly configured. AuthenticationMode {0} is unknown and not supported.

Cause: Twitter Driver not properly configured. AuthenticationMode given is unknown and not supported.

Action: Configure and restart this driver.
Level: 1

Type: ERROR

Impact: Process

SDP-26311: Retweet id string {0} in meta data could not be converted to long. No tweet for messageId {1}

Cause: Retweet id string in meta data could not be converted to long.

Action: Check how the application generates the meta data.
Level: 1

Type: WARNING

Impact: Process

SDP-26312: Ignoring reply id string {0} in meta data that could not be converted to long.

Cause: Ignoring reply id string in meta data that could not be converted to long.

Action: Check how the application generates the meta data.
Level: 1

Type: WARNING

Impact: Process

SDP-26313: Ignoring geo location string ({0}) in meta data that could not be converted to (double,double).

Cause: Ignoring geo location string in meta data that could not be converted to (double,double).

Action: Check how the application generates the meta data.
Level: 1

Type: WARNING

Impact: Process

SDP-26314: Failed to verify the credentials.

Cause: Failed to verify the credentials.

Action: Check the Twitter Driver configuration.
Level: 1

Type: WARNING

Impact: Process

SDP-26315: Failed to send tweet due to rate limitation.

Cause: Failed to send tweet due to rate limitation.

Action: Adjust the send rate or modify the Twitter Account settings.
Level: 1

Type: WARNING

Impact: Process

SDP-26316: Failed to receive tweet due to rate limitation.

Cause: Failed to receive tweet due to rate limitation.

Action: Wait or modify the Twitter Account settings.
Level: 1

Type: WARNING

Impact: Process

SDP-26317: Twitter exception when sending tweet. Msg={0}

Cause: Twitter exception when sending tweet.

Action: Check the Twitter Exception message.
Level: 1

Type: WARNING

Impact: Process

SDP-26450: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26451: One or more sets of extension endpoints were configured using identical protocols and mapped domains: {0}.

Cause: Each of the listed protocol/domain pairs is used to configure multiple extension endpoints.

Action: Remove the conflicting endpoint configuration, or ensure that each endpoint has unique protocol and mapped domain parameters.
Level: 1

Type: WARNING

Impact: Process

SDP-26452: No extension endpoint could be found for the specified recipient address.

Cause: None of the configured extension endpoints matched the protocol and domain of the message recipient.

Action: Ensure that an endpoint is configured for the desired protocol and domain, or configure a default (empty) domain.
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26453: No configuration was found for this Extension Driver deployment: {0}. Driver disabled until a configuration is created.

Cause: No configuration was found for this Email Driver deployment.

Action: Create a configuration this Email Driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26454: Extension Driver {0} is not configured with at least one extension point with a valid endpoint URL and protocol. Driver disabled until configured.

Cause: Extension Driver is not configured with at least one extension point with a valid endpoint URL and protocol.

Action: Configure this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26455: Error while processing Extension Driver configuration with Endpoint URL: {0}. The configuration must contains a valid endpoint URL and protocol.

Cause: An error occurred while processing the Extension Driver configuration.

Action: Check the corresponding configuration. The configuration must contains a valid endpoint URL and protocol.
Level: 1

Type: ERROR

Impact: Process

SDP-26456: An exception occurred while enabling the WS-Security configuration: {0}

Cause: An exception occurred while attaching a WS-Security policy to a web service client or endpoint.

Action: Ensure that any WS-Security policies are specified in the correct format.
Level: 1

Type: ERROR

Impact: Process

SDP-26457: An exception occurred while constructing the SOAP message: {0}

Cause: An exception occurred while constructing the SOAP message

Action: Check the configuration of the server.
Level: 1

Type: ERROR

Impact: Process

SDP-26500: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26501: Failed to deliver a message to the gateway at {0}. No Status could be generated for the failed message.

Cause: A message failed to be delivered to the gateway.

Action: Check the connectivity to the gateway
Level: 1

Type: ERROR

Impact: Process

SDP-26502: Unable to connect to the Feedback service at {0}. Will retry to connect.

Cause: Unable to poll the Feedback service, due to a network problem.

Action: Check the connectivity to the Feedback service.
Level: 1

Type: ERROR

Impact: Process

SDP-26503: Unable to poll the Feedback service at {0}.

Cause: Unable to poll the Feedback service, probably due to a network problem.

Action: Check the connectivity to the Feedback service.
Level: 1

Type: ERROR

Impact: Process

SDP-26550: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26551: Failed to deliver a message to the gateway at {0}. No Status could be generated for the failed message.

Cause: A message failed to be delivered to the gateway.

Action: Check the connectivity to the gateway
Level: 1

Type: ERROR

Impact: Process

46 SOA-06000 to SOA-67028

SOA-06000: No processor registered for asynchronous job type: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-06001: Skipped recovery attempt for fault {0} : {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06002: Recovery attempt for fault {0} failed : {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06003: Recovery attempt for fault {0} succeeded

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06004: Exception encountered during recovery attempt: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06005: The {0} service engine does not support automated fault recovery

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06006: The composite {0} is not in a state for which recovery can be performed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06007: Fault is unrecoverable

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06008: Incorrect job type: {0} ; Expected {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-06009: Scheduled asynchronous job: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06010: Updated status for asynchronous job {0} : {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06011: Recorded results for asynchronous job {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06012: The results for job {0} are not available because the processing has not yet completed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06013: Processing asynchronous {0} job {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06014: The processing of asynchronous job {0} failed: {1} : {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06015: {1} faults matched the filter criteria associated with the bulk fault recovery job {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-06016: The composite {0} could not be found

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-06017: The Fabric mesh could not be accessed: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-06018: Fault state unknown for faultId {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-06019: operation to retrieve sca entity associated data failed {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-06020: The scheduling of asynchronous job {0} failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-10000: Import type {0} is not currently defined. The only valid import types are "wsdl" and "edl". If you are attempting to import an xsd file, please do so through a WSDL document.

Cause: The import type specified for the composite import is unrecognized

Action: Make sure the import type is one of the currently recognized types (.edl, .wsdl)
Level: 1

Type: ERROR

Impact: Configuration

SOA-10001: No binding node (e.g. <binding.ws>) found for {0}. Please make sure that the composite specifies a binding of a given type.

Cause: No bindings are configured for the given service or reference

Action: Check that the composite's services and references specify at least one binding.
Level: 1

Type: ERROR

Impact: Configuration

SOA-10002: Unable to add a code source to the composite classloader due to an exception. Please ensure that the proper resources are available in the SCA-INF/classes, SCA-INF/gen-classes, and SCA-INF/lib composite archive sub-directories.

Cause: Unable to add a code source to the composite's classloader due to an exception

Action: Ensure that resources are available in the SCA-INF/classes, SCA-INF/gen-classes, and SCA-INF/lib composite archive sub-directories.
Level: 1

Type: ERROR

Impact: Deployment

SOA-10003: Failed to retrieve the application topology node from the TopologyService using {0}.

Cause: Unable to retrieve a toplogy node from the Toplogy Service

Action: Please check whether the toplogy node path is valid
Level: 1

Type: ERROR

Impact: Deployment

SOA-10004: Failed to create MAS-enabled componentType lookup; {0}.

Cause: Unable to create a strategy that enables the lookup of .componentType files in a MAS environment

Action: Make sure the toplogy node path, composite home directory, and strategy class name are correct
Level: 1

Type: ERROR

Impact: Deployment

SOA-10005: Failed to retrieve {0} document from topology node {1}.

Cause: Unable to retrieve a document from the topolgy node

Action: Make sure the toplogy node path, composite home directory, and the document name are correct
Level: 1

Type: WARNING

Impact: Other

SOA-10006: Error occurred while retrieving {0} document from topology node {1}. The underlying cause was a {2}.

Cause: An error occurred during the retrieval of a document from a topology node

Action: Make sure the resource path is valid and that the deployment succeeded
Level: 1

Type: ERROR

Impact: Configuration

SOA-10007: Error occurred while attempting to retrieve message part {0} from a normalized message payload with elements {1}.

Cause: An attemp to retrieve a message part of a given name from a Normalized Message failed

Action: Make sure that there is no mismatch between the WSDL defined part name and a configured part name
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-10008: Error occurred during deployment of component: {0} to service engine: {1}, for composite: {2}

Cause: An error occurred during component deployment

Action: Please check the root cause of the failure
Level: 1

Type: ERROR

Impact: Deployment

SOA-10009: Error occurred during creation of domain/instance noun: {0}

Cause: An error occurred during creating noun for domain/instance

Action: Please check the root cause of the failure
Level: 1

Type: ERROR

Impact: Configuration

SOA-10010: Error occurred while getting portable mbean factory: {0}

Cause: An error occurred while getting portable mbean factory

Action: Please check the root cause of the failure
Level: 1

Type: ERROR

Impact: Configuration

SOA-20000: Message Router for {0} is null. Please validate that the composite deployment completed successfully by checking the server logs.

Cause: There is no message router found for the composite

Action: Check that the composite deployment completed successfully
Level: 1

Type: ERROR

Impact: Deployment

SOA-20001: Message Router for {0} is not able to process messages. The composite state is set to "off". The composite can be turned "on" by using the administrative consoles.

Cause: The composite state or mode do not allow processing of messages

Action: Use the management consoles to set the mode and state of the composite to enable processing
Level: 1

Type: ERROR

Impact: Configuration

SOA-20002: No path info set for provider invocation. Unable to determine composite and service for processing.

Cause: There is no path information in the inovcation URI that facilitates routing of the message to the composite service

Action: Make sure that the invoking URL is of the form http://host:port/soa-infra/services/applicationName/compositeName/serviceName
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20003: Unable to register service.

Cause: There was an issue during the attempt to create the endpoint for the composite service

Action: Make sure that the WSDL either has a service and port that correspond to the values specified in the composite file or that there is no empty service node in the WSDL
Level: 1

Type: ERROR

Impact: Deployment

SOA-20004: Unable to deregister service.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20006: Unable to register reference {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20007: Cannot find binding component for service "{0}".

Cause: There is no binding component configured in the SOA Platform that can handle the given service binding type

Action: Make sure that the binding type specified for the composite's service is valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20008: Cannot find binding component for reference "{0}".

Cause: There is no binding component configured in the SOA Platform that can handle the given reference binding type

Action: Make sure that the binding type specified for the composite's reference is valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20009: Cannot find service engine for component "{0}" in composite "{1}".

Cause: There is no service engine configured in the SOA Platform that can handle the given component implmentation type

Action: Make sure that the implementation type specifed for the composite's component is valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20010: Unable to find Binding Component for type "{0}".

Cause: No binding component found for the given type

Action: Make sure the configured type has a corresponding SOA Platform configured binding component
Level: 1

Type: ERROR

Impact: Configuration

SOA-20011: Unable to find Service Engine for type "{0}".

Cause: No service engine found for the given type

Action: Make sure the configured type has a corresponding SOA Platform configured service engine
Level: 1

Type: ERROR

Impact: Configuration

SOA-20012: Unable to find component or reference identified by "{0}".

Cause: Unable to find a component or reference of the given name in the composite

Action: Make sure the composite wires are properly formed and reference existing components and/or references
Level: 1

Type: ERROR

Impact: Configuration

SOA-20013: MDS Root mis-configuration.

Cause: The MDS root directory is misconfigured

Action: Make sure the composite directories specified in the deployed-composites.xml file are correct
Level: 1

Type: ERROR

Impact: Deployment

SOA-20018: Cannot read WSDL "{0}" from Metadata Manager.

Cause: There was a problem reading a WSDL document from the MDS repository

Action: Make sure the composite imports point to the valid WSDL paths
Level: 1

Type: ERROR

Impact: Deployment

SOA-20019: Object "{0}" does not exist in metadata repository.

Cause: The requested file or resource does not exist in the MDS repository

Action: Make sure the resource path is valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20020: Deployment of composite "{0}" failed: {1}.

Cause: Unable to deploy the composite

Action: Check the associated exception for more information
Level: 1

Type: ERROR

Impact: Deployment

SOA-20021: Undeployment of composite "{0}" failed: {1}.

Cause: There was an error generated during the undeployment of a composite

Action: Check the associated exception for more information concerning the undeployment issue
Level: 1

Type: ERROR

Impact: Deployment

SOA-20025: Failed to find a WSDL Definition for service: "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20026: Failed to find composites to deploy based on path: "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20027: Unable to create interceptors, InterceptorChainFactory may not be defined for "{0}".

Cause: There was a problem creating an interceptor chain associated with the composite

Action: Make sure that the interceptor chain factories are configured in the SOA platform's configuation file located in the fabric war's WEB-INF directory
Level: 1

Type: ERROR

Impact: Deployment

SOA-20028: Unable to create mbeans for the composite "{0}" because of error "{1}".

Cause: There was an error generated during the creation of the composite MBean

Action: Check the associated exception for the cause of the error
Level: 1

Type: ERROR

Impact: Deployment

SOA-20029: Unable to unregister mbean for the composite "{0}" because of error "{1}".

Cause: There was an error while attempting to unregister the composite MBean

Action: Check the associated exception for the cause of the error
Level: 1

Type: ERROR

Impact: Deployment

SOA-20030: Unable to unregister deployed composites runtime mbean because of error "{0}".

Cause: There was an error while attempting to unregister the deployed composites MBean

Action: Check the associated exception for the cause of the error
Level: 1

Type: ERROR

Impact: Deployment

SOA-20031: An active composite for "{0}" has already been registered. Only one active composite is allowed.

Cause: An attempt was made to deploy an active composite for an application that already has an active composite

Action: Make sure that only one active composite is associated with a given application. You can deactive/activate composites via the management consoles
Level: 1

Type: ERROR

Impact: Deployment

SOA-20032: The composite "{0}" is retired. New instances cannot be initiated.

Cause: An attempt was made to initiate a composite instance using a retired composite

Action: Make sure to create a new instance with an active composite. The composite mode can be configured via the management consoles
Level: 1

Type: ERROR

Impact: Deployment

SOA-20034: No composite found for application "{0}", composite name "{1}" and revision "{2}".

Cause: An attempt was made to reload a composite application for which resources can not be found in the metadata repository

Action: Make sure that the application name, composite name, revision, and label specify a valid metadata store
Level: 1

Type: ERROR

Impact: Configuration

SOA-20035: Composite "{0}" has already been loaded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20036: Composite "{0}" has been loaded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20037: Composite home directory "{0}" does not exist.

Cause: The composite home directory specified is not valid

Action: Make sure the composite home directory specified in deployed-composites.xml is valid
Level: 1

Type: ERROR

Impact: Deployment

SOA-20038: Composite "{0}" does not exist.

Cause: No composite message router was found for the specified composite

Action: Make sure the composite distinguished name specified is valid and that the composite application deployed successfully
Level: 1

Type: ERROR

Impact: Deployment

SOA-20039: Operation not supported.

Cause: An attempt was made to undeploy using the deployment update mechanism

Action: N/A
Level: 1

Type: ERROR

Impact: Deployment

SOA-20040: Message exchange pattern not currently supported.

Cause: The attempted message exchange pattern is not supported

Action: Make sure that the composite wiring is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20041: Deployment failure on rollback: {0}

Cause: An error was raised during an attempt to rollback a composite deployment

Action: Make sure that all composite resources have been removed
Level: 1

Type: ERROR

Impact: Deployment

SOA-20042: Not enough information to ascertain composite name from pathInfo "{0}".

Cause: The path information in the URI was not sufficient enough to identify a composite

Action: Make sure that the URL used to invoke the composite service has the proper application name, composite name, revision, and label
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20043: No deployed composite found for path "{0}".

Cause: The path information in the URI was not sufficient enough to identify a composite

Action: Make sure that the URL used to invoke the composite service has the proper application name, composite name, revision, and label
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20044: Unable to retrieve resource "{0}" associated with composite "{1}".

Cause: An attempt to retrive a composite application associated resource (e.g. a WSDL file) failed

Action: Make sure the URL specified is correct
Level: 1

Type: ERROR

Impact: Deployment

SOA-20045: No WSDL URL provided

Cause: No WSDL URI was specified for the composite associated WSDL

Action: Make sure the WSDL import in the composite file is valid and specifies a URI for the file
Level: 1

Type: ERROR

Impact: Deployment

SOA-20046: Deployment of MBEANS for composite "{0}" failed: {1}.

Cause: There was a problem deploying the composite MBeans

Action: Check the associated exception for more information. There may have been a problem deregistering the MBean during a previous undeployment.
Level: 1

Type: ERROR

Impact: Deployment

SOA-20047: Unable to initialize composite parser: {0}.

Cause: Unable to initialize the composite parser

Action: Make sure that any parser providers registered in the fabric war web.xml file are valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20048: Unable to discover local host name: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20049: Unable to register composite loader due to exception: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20050: Binding components failed to create holder type for {0}.

Cause: The required holder class is not available on the classpath

Action: Make sure the holder class is available in the classpath
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20051: Return value from the Java Service method {0} is invalid.

Cause: The service returned a value of a different type than was expected

Action: Verify that the service and the WSDL correspond
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20052: Binding Component failed to access holder value for {0}.

Cause: Unable to call a setter/getter on the holder class instance

Action: Make sure the access method is public
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20053: Binding Component is unable to locate operation {0} for java service {1}.

Cause: The requested method does not exist on the target service class

Action: Verify that the target service implements all methods defined in the WSDL
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20054: Binding Component failed to invoke method {0}.

Cause: The requested method of the target service is not public

Action: Verify that the targets service's methods are public
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20055: Missing WebResult method annoation for java service {0}.

Cause: The @WebResult annotation is not defined for the service interface

Action: Make sure the @WebResult annotation is specified in the service interface
Level: 1

Type: ERROR

Impact: Programmatic

SOA-20056: Could not locate service for {0}.

Cause: The requested service is not registered

Action: Make sure the service is registered and named correctly
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20057: Could not find invocation context containing sdo metadata for component {0}.

Cause: The requested service is not registered

Action: Make sure the service is registered and named correctly
Level: 1

Type: ERROR

Impact: Deployment

SOA-20058: Could not find registry for {0}.

Cause: The requested service registry does not exist

Action: Make sure that the registry is available and named correctly
Level: 1

Type: ERROR

Impact: Deployment

SOA-20059: Unable to copy the WSDL definition due to exception

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20060: Partname metadata for the parameter {0} is missing.

Cause: A parameter of a method of the service interface is missing the @PartName annotation

Action: Make sure the @PartName annotation is specified for the parameters of the method
Level: 1

Type: ERROR

Impact: Programmatic

SOA-20061: Input argument {0} has a wrong parameter java type.

Cause: Unable to create an instance of a parameter value

Action: Make sure the parameter classes are available and have default constructors
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20097: Binding component is unable to load schema from this location: {0}

Cause: Could not load an imported schema

Action: Make sure the schema is available in the location specfied in the WSDL
Level: 1

Type: ERROR

Impact: Deployment

SOA-20098: Binding component failed to initialize.

Cause: There was an internal error during initialization

Action: Please contact support
Level: 1

Type: ERROR

Impact: Deployment

SOA-20099: WSDL port metadata in composite {0} not found

Cause: There was an internal error during load

Action: Please contact support
Level: 1

Type: ERROR

Impact: Deployment

SOA-20100: Binding component failed to register Metadata types with SDO provider.

Cause: There was an internal error during load

Action: Please contact support
Level: 1

Type: ERROR

Impact: Deployment

SOA-20101: Metadata for operation {0}, service {1} can not be found.

Cause: The operation was not defined in the service WSDL

Action: Make sure the operation is defined in the service WSDL
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20102: An error occurred while scheduling deployment. Exception reported is "{0}"

Cause: There was an error while attempting to schedule a deployment

Action: Check the associated exception for the cause of the error
Level: 1

Type: ERROR

Impact: Deployment

SOA-20104: The composite for model "{0}" is not found!

Cause: There was an error during retrieval of the service associated composite

Action: Make sure the composite is valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20106: Binding Component is unable to load schema at "{0}" due to missing system id in the referencing source schema.

Cause: Unable to load schema due to missing system id in the referencing WSDL or schema

Action: Ensure the system id is defined in the WSDL
Level: 1

Type: ERROR

Impact: Deployment

SOA-20107: Configuration Error in Java Binding. Unable to find portType or interface.

Cause: Service or port names were not specified in the binding configuration

Action: Make sure the service and port name are available in the binding configuration
Level: 1

Type: ERROR

Impact: Configuration

SOA-20108: The resource "{0}" not found in the composite "{1}"

Cause: Unable to retrieve a resource from the composite's MDS repository

Action: Make sure the resource path specified, relative to composite URI, is correct
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20109: Invocation Exception: {0}:

Cause: The service generated an error during invocation

Action: Ensure that the service is operating correctly
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20110: This {0} method is not implemented!

Cause: One way operations are not supported for SDO dynamic stubs

Action: Consider using an alternate message exchange pattern
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20111: Binding Component failed to create user defined faults.

Cause: A SOAP fault was generated by the service invocation

Action: Ensure that the service is operating properly. The fault may be expected.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20112: The called service raised a fault.

Cause: The service generated an exception

Action: Ensure that the service is operating properly
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20113: Unable to access the following endpoint(s): {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20114: Unable to update reference instance with response payload due to exception

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20115: Illegal modification to existing composite {0}. Changes are not allowed to elements of the composite distinguished name (application name, composite name, revision, and label). If you are attempting a re-deployment of a failed deployment, please undeploy and then deploy the composite.

Cause: The attempted change of the deployed composite file was not valid

Action: Make sure the change you are making is allowed
Level: 1

Type: ERROR

Impact: Deployment

SOA-20116: Only changes to policy references of {1} of composite {0} are supported by the Web Service Binding Components. All other changes (e.g. changes to the port attribute of a binding) will be ignored.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20117: The wire target URI {1}/{2} for composite {0} is not valid. No service {2} is defined for component {1} in its componentType file. Please check the componentType file for component {1} for valid service names.

Cause: The composite wire appears to be malformed since no such component/service pair exists

Action: Please check the componentType file for the component for valid service names.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20118: The wire source URI {1}/{2} for composite {0} is not valid. No reference {2} is defined for component {1} in its componentType file. Please check the componentType file for component {1} for valid reference names.

Cause: The composite wire appears to be malformed since no such component/reference pair exists

Action: Please check the componentType file for the component for valid reference names.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20119: Unable to find a WSDL that has a definition for service {0} and port {1}. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server.

Cause: Unable to find a WSDL that has a definition corresponding to the provided service and port names

Action: Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server.
Level: 1

Type: ERROR

Impact: Deployment

SOA-20120: Unable to find a composite definition in {0}. Please make sure there is a composite.xml definition file that defines a composite with the same name as the composite name in the composite JAR name.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20121: An attempt was made to deploy a composite ''{0}'' that has already been deployed. This is an internal error, and does not require any action. The original composite definition remains in effect.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20122: Unable to find a file named ''adf-config.xml'' in the search path starting at {0}. The ''adf-config.xml'' file is required to configure the MDS instance used for composite deployment. Repackage the composite application, providing an MDS store a and namespace named after the composite name.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20124: Unable to process the MDS configuration at {0}. Please verify the formatting and contents of the ''adf-config.xml'' file. Also, check the rest of the log for MDS failures, which could help point out the root cause of the processing failure.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20125: Cannot create an XSLT transformer. Please ensure that your JAXP environmentis properly configured with an XSLT 1.0 transformer.

Cause: Unable to create the adf-config xml transformer

Action: Make sure the adf-config file is property formatted
Level: 1

Type: ERROR

Impact: Deployment

SOA-20126: Updating MDS configuration at {0} with file-based MDS root {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20127: Exception when processing MDS configuration.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20128: The context header qname is invalid or malformed. Please check that the correct context header qname is specified for the contextHeadersQNames property in the fabric-config.xml file

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20129: Could not create a context header due to exception

Cause: Unable to create the context header

Action: Ensure that the context provider implementation is valid and working
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20130: Entry Binding Component: invocation of service {0}, operation {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20131: External Binding Component: invocation of service {0}, operation {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20132: Binding Component found port type: {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20133: Binding Component registered the following schema with SDO implementation within context of classloader {1} ==> {0}

Cause:

Action:
Level: 32

Type: TRACE

Impact: Other

SOA-20134: No annotation found on service interface.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20135: Exception creating JAXWS servant. Exception: {0}, Message: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20136: WS Binding: exception during SOAP invocation: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20138: No oracle-archive.xml found; will use file scanning for application ''{0}''

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20139: Unable to find a registered server for pathInfo {0}. Please ensure that the given composite is deployed. If this is occurring during the processing of a callback, please make sure that the "#" delimiter in the callback URL is properly encoded.

Cause: The path provided in the invocation URI does not map to a deployed composite

Action: Make sure the URI is correct and references a deployed composite application
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20141: Schema validation failed for message part {0}. Please ensure at the message sender level that the data sent is schema compliant.

Cause: Validation of the message part against its schema failed.

Action: Please take actions at the message sender to ensure that the data is schema compliant.
Level: 1

Type: ERROR

Impact: Data

SOA-20143: Unable to register a service endpoint for a defined reference callback. Please ensure the WSDL and reference configuration are correct.

Cause: Unable to register a callback endpoint for the defined reference callback

Action: Make sure that the application configuration is correct. For example, ensure that the associated WSDL does not have any mis-spelled message names.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20144: Unable to find a target component or reference based on invocation context {0}. Please check the composite file and make sure a wire exists for the specified reference or source URI.

Cause: Unable to find a wire for the reference

Action: Make sure that the service or component reference is actually wired to a target
Level: 1

Type: ERROR

Impact: Deployment

SOA-20145: The serviceName/serviceID attribute is missing.

Cause: Unable to find serviceName attribute for the binding

Action: Make sure that the serviceName is specified in the composite
Level: 1

Type: ERROR

Impact: Deployment

SOA-20146: Unable to deploy service {0} with multiple WS bindings. Please make sure there is only one WS binding for the given service in the composite file.

Cause: Unable to deploy a service with multiple WS bindings

Action: Make sure that the service has only one WS binding
Level: 1

Type: ERROR

Impact: Deployment

SOA-20147: javaInterface name for the binding is missing or the interface class is not available.

Cause: Unable to find javaInterface attribute for the binding

Action: Make sure that javaInterface attribute is specified on the composite
Level: 1

Type: ERROR

Impact: Deployment

SOA-20148: null

Cause: Failure in looking up EJB

Action: Make sure JNDI properties, jndi name specified are correct.
Level: 1

Type: ERROR

Impact: Deployment

SOA-20149: Caller is not in allowed role!

Cause: Failure in authenticating ejb invocation

Action: Make sure invocation client has the right role mapped.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20150: SOA EJB Invoker could not load bean interface class defined for service {0}.

Cause: Failure in loading ejb interface class

Action: Make sure interface class is included in the deployment package.
Level: 1

Type: ERROR

Impact: Deployment

SOA-20151: SOA EJB Invoker could not locate composite for service {0}.

Cause: Failure in locating composite

Action: Make sure the composite configuration is correct
Level: 1

Type: ERROR

Impact: Configuration

SOA-20152: SOA EJB Invoker could not locate method named {0} with {1} of arguments on interface class {2} for service.

Cause: Failure in locating method

Action: Make sure the composite configuration is correct
Level: 1

Type: ERROR

Impact: Configuration

SOA-20153: Failure in processing jps credential store properties, exception stack: {0} .

Cause: Failure in processing credential store properties

Action: Make sure the properties are specified correctly or permission to access the the store has been setup.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20154: The path "{0}" has already been used by another direct binding. Please select a different path override.

Cause: Illegal pathOverride used in composite configuration. The alias name has already been used for other another direct binding.

Action: Select a different path alias for the direct binding component.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20155: Expected protocol ''soadirect'', got ''{0}'' instead.

Cause: Illegal protocol used in direct binding composite configuration.

Action: Correct path should start with "soadirect"
Level: 1

Type: ERROR

Impact: Configuration

SOA-20156: Invalid service path "{0}".

Cause: Service Path used in the invocation is invalid.

Action: Correc the service path.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20157: Service not found for path "{0}".

Cause: Service not found for the path name used in the invocation.

Action: Check composite configuration to see if the path name used matches.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20158: Direct binding component failed to initialize.

Cause: Exception occured during the direct binding component initialization.

Action: Check the exception for detailed failure cause.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20159: Direct binding component not initialized.

Cause: Direct binding component has not been initialized.

Action: Check server startup log to see any detailed exception log.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20160: Could not obtain keystore location or password

Cause: Could not obtain the keystore location or password for setting up 2 Way SSL

Action: Make sure that the keystore is available in the default location or is specified in the SOA configuration. In addition, make sure the keystore password is configured in the credential store.
Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-20161: Unable to create SSL Socket Factory

Cause: Could not create the SSLSocketFactory for supporting 2 Way SSL

Action: Check the associated exception for the cause of the failure.
Level: 1

Type: ERROR

Impact: Network

SOA-20168: Could not find a port for the dynamic reference given service name {0} and port type {1}

Cause: Could not find a port that matched the supplied service name and port type for the dynamic reference

Action: Check the dynamic reference configuration and the supplied WSDL to ensure proper configuration.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20169: Folder {0} is not able to process messages. The folder state is set to "off". The folder can be turned "on" by using the administrative consoles.

Cause: The folder state or mode do not allow processing of messages

Action: Use the management consoles to set the mode and state of the folder to enable processing
Level: 1

Type: ERROR

Impact: Configuration

SOA-20170: Partition {0} does not exist. Make sure the partition was created and exists.

Cause: The folder can not be found

Action: Check the folder name and make sure such a folder was created and exists
Level: 1

Type: ERROR

Impact: Configuration

SOA-20171: Cannot find port type {0} in the WSDL. Make sure the port type is defined in the WSDL

Cause: The port type cannot be found

Action: Check the WSDL and make sure the port type is defined in the WSDL
Level: 1

Type: ERROR

Impact: Configuration

SOA-20172: No source URI specified for the given invocation or callback. Please make sure there is a wire specified for the context {0}.

Cause: No source URI for the wire

Action: Check the composite and make sure a wire is defined for the interaction.This is most likely an indication of an error in the wiring.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20173: @WebService or @PortableWebService annotation is required, but not found on {0}.

Cause: Interface class does not contain @WebService annoation.

Action: Add @WebService annotation that describes the service in the interface class.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20174: Failed to get application helper context using service id ''{0}''.

Cause: Unable to create application helper context.

Action: Check the underlying cause from the SDO implementation.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-20175: Binding property {0} overridden by a message property of the same name.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20176: Both csf-key and username/password have been set. The csf-key will be used for authentication processing.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20177: Could not lookup the service endpoint from UDDI either due to a UDDI connection error or the provided ServiceKey {0} was invalid.

Cause: Could not lookup service endpoint from UDDI. Either by error on UDDI connection or invalid ServiceKey

Action: Check the OSR-UDDI inquiryUrl configuration and the supplied ServiceKey to ensure proper configuration.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20178: Unsupported interface type: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20179: Ejb Binding is not found.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20180: Unable to load interface class {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20181: Unknown service: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20182: JNDI name {0} already exists.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20183: Could not find method {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20184: Ejb Reference binding failed to invoke ejb.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20185: Ejb Reference binding failed to create jndi initial context.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20186: No ejb registered with the jndi name: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20187: Invalid EJB2 beans. Create method returned null for : {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20188: Failed to invoke create method on the bean.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20189: Invalid bean. EJB2 reference does not implement Home interface.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20190: Unable to register JNDI binding.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20191: Unable to unregister JNDI binding.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20192: No response for invocation.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20193: Conversion of BizFault failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20194: Java based Ejb service binding started a transaction.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20195: Java based Ejb service binding committed the transaction.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20196: Java based Ejb service binding rollback the transaction.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20197: Failed to initialize ADR home directories.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20206: Failed to register SOA diagnostic dumps, DFW (diagnostic framework) not available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20207: Failed to deregister SOA diagnostic dumps, DFW (diagnostic framework) not available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20208: Failed to deregister SOA diagnostic dumps, local soa dumps registry not available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20209: No MBean server found, can not register SOA dump: soa.env.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20210: Can not find facade locator, the following SOA diagnostic dumps not registered: {0}, {1}, {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20211: Failed to look up SOA data source: jndi = [{0}], soa.db dump can not be registered.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20212: SOA data source not available (NULL), soa.db dump not registered.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20213: JNDI context not available, can not look up SOA data source, no DB dump (soa.db) registration.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20214: Not registering SOA incident rules file.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20215: Not unregistering SOA incident rules file {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20216: Not registering custom incident rules file {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20217: Not unregistering custom incident rules file {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20265: No binding found for reference [{1}] of composite [{0}]. A callback endpoint can not be created. Please make sure the composite is deployed to this server.

Cause: There is no reference binding available or deployed

Action: Check that the composite deployment completed successfully and is targeted for this server.
Level: 1

Type: ERROR

Impact: Deployment

SOA-20266: The composites {0} failed during server startup. Please check the logs for more information.

Cause: Composites failed in deployment during server restart

Action: Check the associated exception for more information
Level: 1

Type: ERROR

Impact: Deployment

SOA-20273: Failed to activate weblogic config changes. FailureException: {0}, Failure Message: {1}. {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20274: Failed to cancel pending weblogic onfig changes. Failure Message: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20275: Failed to initialize FolderAppRoleManager. Partition specific soa roles will not be created. Failure: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20277: An error occurred while creating the application role named [{0}].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20278: An error occurred while looking up local jndi edit config mbean. {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20279: An error occurred looking up workmanager named [{0}], use workmanager named [{1}] instead.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20280: Created workmanager named [{0}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20281: Error occurred while destroying a partition.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20282: Approle [{0}] for the folder already exists. It will be deleted and recreated.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20283: Failed to lookup soainfra application name, using [soa-infra] instead.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20284: Failed to set AppSecurityContext id to soa application.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20285: JAXBConfigPersistenceHandler is null. WorkManagerGroup configuration changes will not be persisted.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20286: FolderAppRoleManager was not initialized properly. Partition roles will not be created.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20287: Failed to readjust workmanager MaxThreadsConstraint based on soa datasource max capacity size.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20289: Cannot find the capacity constraint named [{0}] in the domain.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20290: Default SOA WorkManager is used for {0} work execution since the partition workmanager is not available. {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20291: SOA Executor WorkManager work with id [{0}] has been rejected. {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20298: Error caught when registering SOA dump: [{0}], error message: [{1}], stacktrace: [{2}]

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20304: Failed to look up SOA data source: jndi = [{0}], soa.edn registered but not able to capture diagnostic in DB.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20305: JNDI context not available, can not look up SOA data source, soa.edn registered but not able to capture diagnostic in DB.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20306: SOA data source not available (NULL), soa.edn registered but not able to capture diagnostic in DB.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20307: Invalid format used for the cluster operation message.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20309: Failed to process workmanager group cluster notification message for [{0} {1} operation].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20311: Failed to activate max thread configuration update. A restart will be necessary.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20315: Failed to save rejected message for service [{0}] of binding type [{1}].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20317: Failed to invoke health check on startup.

Cause: Could not invoke health check

Action: Contact Oracle support.
Level: 1

Type: WARNING

Impact: Other

SOA-20318: On startup, health check id {0} passed for category ''{1}''. Ran {2} checks.

Cause: Health check completed successfully

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20319: On startup, health check id {0} passed with warning(s) for category ''{1}''. Ran {2} checks. Number of warnings={3}.

Cause: Health check completed with warning

Action: Check the health check result for details.
Level: 1

Type: WARNING

Impact: Other

SOA-20320: On startup, health check id {0} did not pass for category ''{1}''. Ran {2} checks. Number of errors={3}, warnings={4}, failures={5}.

Cause: Health check completed with error

Action: Check the health check result for details.
Level: 1

Type: ERROR

Impact: Other

SOA-20321: On startup, health check id {0} failed for category ''{1}''. Ran {2} checks. Number of failures={3}, errors={4}, warnings={5}.

Cause: Health check failed to complete

Action: Check the health check result for details.
Level: 1

Type: WARNING

Impact: Other

SOA-20323: SOA server is in quiesce mode - incoming requests will be persisted and processing will be resumed when server is back in running mode.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20324: Tenant not found with the specified id: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-20325: Tenant not found with the specified name: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-20327: On startup, there were no health check in category ''{0}'' that could be run.

Cause: Health check was not run since all checks were disabled or not applicable.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20329: The size of the requested audit trail for flow id "{0}" is larger than the configured threshold of "{1}" characters.

Cause: The size of the audit trail is larger than the configured threshold.

Action: If the resources are available, increase the instanceTrackingAuditTrailThreshold attribute of the AuditConfig MBean to view this audit trail.
Level: 1

Type: WARNING

Impact: Configuration

SOA-20330: TenantManager instance did not return a valid partition directory.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-20331: URL resolver properties loaded from {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-20332: Unable to load url resolver properties from {0}. Exception: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-20333: No tenant partition directory is found. Token updates are not saved.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-20334: No domain config directory is found. Token updates are not saved.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-20335: Unable to discover cluster info. Exception:

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-20336: null

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-20337: null

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-20338: Variable {0} is not found in the token configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-20339: Unable to find server SelfTuning Mbean instance.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-20340: Unable to find soainfra application deployment mbean instance.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-20341: Unable to find resource group named ''{0}''.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-20342: Unable to find edit session named ''{0}''.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-20343: Found an invalid token "{0}". Invalid tokens will not be used for token url replacement.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-20344: Failed to register soa datasource listener. DataSource capacity change will not be monitored. Failure: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-20345: Warning: MBean "{0}" has failed to register.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-20346: Warning: failed to unregister mbean. {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-20347: Warning: failed to find mbean matching {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-20348: Encountered an unexpected failure in the SOA debugger module. This failure should not affect the execution of the composite instance, however, the SOA debugger may not function correctly.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-21500: Error occurred when creating target MDS instance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21501: Error occurred when rolling back MDS label.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21502: Error occurred when creating MDS label.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21503: MDS store of namespace {0} does not have versioning support. Cannot be used in MAS based deployment.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21504: Only single composite is supported in a SAR archive.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21505: Invalid composite name in undeploy: {0}, both composite name and revision need to be specified.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21506: Cannot find revision in undeploy : {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21507: Error reading deployed-composites.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21508: Cannot find composite deployment coordinator.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21509: Error in reading data from deployer client.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21510: There was an error deploying the composite on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21511: Cannot find archive: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21512: Data transfer error in MDS.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21513: Command {0} not supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21514: MDS Transfer directory {0} already exists for composite {1}. Removing and replacing to deploy new version of composite.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-21515: Cannot find composite {0} in sar file : {1}. Abort deployment.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21516: Cannot find base composite for: {0}. Abort redeployment.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21517: Composite with same revision ID already exists: {0}. Please set the overwrite flag or use different revision ID. Abort deployment.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21518: Protocol {0} is not supported. Only http is supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21519: Error parsing composite {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21520: Cannot find shared data archive: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21521: Error removing archive data from MDS for composite: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21522: Error occurs in applying deployment plan {1} to sar file: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21523: Composite {0} cannot be automatically set as default due to state: {1} or mode: {2}. The state needs to be on and the mode needs to be active.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-21524: Error occurred in processing sar file {0} before transferring into MDS store. Please make sure the sar file is a valid jar file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21525: Cannot find JPS context: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21526: Error occurs in checking JPS role.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21527: User {0} does not 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-21532: CompositeDeploymentServlet initialized.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-21533: User [{0}] has been successfully authorized.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21534: Start unzipping data to base directory: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21535: Complete unzipping data.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21536: Calling DeployManager to attach deployplan: {0} to SAR file: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21537: Sending back error message: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21538: Removing temporary directory: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21539: Perform deployment operation with redeploy flag: {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-21540: Perform undeployment operation: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21541: Calling coordinator to undeploy {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21542: Undeploying revision: {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-21543: Deploying SAR file: {0} to domain: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21544: Deploying shared data file: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21545: Calling coordinator to deploy {0}, with isForceDefault flag: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21546: Calling coordinator to update composite. base composite: {0}, new composite: {1}, isForceDefault flag: {2}, keepInstancesOnRedeploy flag: {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21547: AutoDeployer-> starting deploying shared data file: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21548: AutoDeployer-> shared data file {0} was successfully deployed. Time spent: {1} sec. This file will be removed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21549: AutoDeployer-> starting deploying SAR file: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21550: AutoDeployer-> SAR file {0} was successfully deployed. Time spent: {1} sec. SAR file will be removed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21551: AutoDeployer-> removing temporary MDS data directory {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21552: Preparing transferring data into MDS for package: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21553: Transferred data into MDS successfully for package: {0}. Transferred size: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21554: Removed extra data from MDS successful for package: {0}. Removed size: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21555: Preparing removing data from MDS for package: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21556: Removed data from MDS successfully for package: {0}. Removed size: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21557: CompositeDeploymentServlet-----> completed deploying {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21558: CompositeDeploymentServlet-----> completed undeploying {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21559: CompositeDeploymentServlet-----> completed redeploying {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21560: Cannot remove temporary directory: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-21562: Composite from sar file: {0} already exists in the target server. Will NOT attempt redeployment and this sar file will be removed from the autodeploy directory.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21563: The composite ({0}) imported a shared library: {1}/{2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21564: The classloader for the shared library ({1}/{2}) referenced by the composite ({0}) cannot be found.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-21566: There was an error exporting composite on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21567: Sending back jar file: {0} of length: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21568: CompositeDeploymentServlet-----> completed exporting composite {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21569: CompositeDeploymentServlet-----> completed exporting post deployment updates {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21570: CompositeDeploymentServlet-----> completed importing post deployment updates {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21571: There was an error exporting post deployment changes on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21572: There was an error importing post deployment changes on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21573: CompositeDeploymentServlet-----> completed exporting shared data of pattern {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21574: There was an error exporting shared data on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21575: adf-config.xml file cannot be null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21576: Cannot find adf-config file: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21577: Cannot get adf-config file URL: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21578: Cannot create SOA MDS instance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21579: Cannot find composite: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21580: Cannot find deployed-composites.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21581: The composite name in composite.xml of the jar file: {0} does not match the composite name to be updated: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21582: The composite revision in composite.xml of the jar file: {0} does not match the composite revision to be updated: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21583: Composite does not exist, cannot import updates: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21584: Composite label cannot be null: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21585: Error read deployed-composites.xml: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21586: Cannot find deployed-composites.xml to save.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21587: Cannot update deployed-composites.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21588: There was an error removing shared data on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21589: CompositeDeploymentServlet-----> completed removing shared data of folder {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21590: Error occurred when modifying the revision in composite.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21591: Cannot find Fabric lifecycle: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21592: SOA platform is not fully started. Please retry later.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21593: Calling coordinator to deploy resource files.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21598: Calling coordinator to patch composite {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21601: Calling coordinator to process pre-deployment hook {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21618: MbeanDeployer-> starting deploying SAR file: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21619: MbeanDeployer-> SAR file {0} was successfully deployed. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21620: Notify shared data update.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-21621: CompositeDeploymentServlet-----> completed updating shared data successfully. Time spent: {0} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21622: Notify resource bundle update.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-21623: CompositeDeploymentServlet-----> completed updating resource bundle successfully. Time spent: {0} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21800: Merge tools failed: {0}. Please check log file for more information.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21801: Cannot find merge tool registration file: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21802: Cannot parse mergetool-registry.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21803: Please use JDeveloper to customize the composite of new revision before merge, since the composite of previous revision had been customized.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21804: Invalid target found when creating BindingContainerProxy, target::{0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21805: Invalid target type when calling {0}, instance::{1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21806: Error building composite model from: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21807: ReferenceConfigModel not available for key={0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21808: Invalid inputs, difference in reference entries found original composite.xml {0} DT@RT composite.xml {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21809: Exception [{0}] when creating composite model serializer, exception message: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21810: Error [{0}] when creating composite model serializer, error message: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21811: Error [{0}] when marshaling composite model into XML, error message: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21812: Can not create the merged composite.xml file at path={0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21813: Exception when write to merged composite.xml at path={0}, exception=[{1}]

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21814: Invalid target found when creating PolicyReferenceContainerProxy, target::{0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21815: Invalid target found when creating PropertyContainerProxy, target::{0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21816: Invalid location for composite application, it must be a directory where artifacts of the composite reside, the parameter is [{0}]

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21817: Missing directory where the resulted composite.xml will be written...

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21818: Exception when parsing composite.xml: e={0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21819: Inconsistency found between v2 and the result composite.xml regarding callbacks in {0} with key = {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21820: Inconsistency found between v1 and DT@RT composite.xml regarding callbacks setting, parent type=[{0}], key={1} in v1 composite.xml has callback : {2}, in DT@RT composite.xml has callback {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21821: Inconsistent binding configuration detected between v1 composite.xml and DT@RT composite.xml, binding in v1:[{0}], binding in DT@RT:[{1}].

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21822: Inconsistency found between v1 and DT@RT composite.xml regarding services setting, service[key={0}] in v1 composite.xml {1}, in DT@RT composite.xml {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21823: Inconsistency found between v1 and DT@RT composite.xml regarding components setting, component[key={0}] in v1 composite.xml {1}, in DT@RT composite.xml {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21824: Missing composite.xml for [{0}]

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21825: No merge operation, the composite.xml containing DT@RT customization does not present at [{0}].

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21826: Cannot find composite sar file: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21827: File: {0} is not a composite sar file because composite.xml is not found in this file.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21828: No merge operation, the sensor.xml containing DT@RT customization does not present at [{0}].

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21829: No merge operation, the sensorAction.xml containing DT@RT customization does not present at [{0}].

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22000: The shared library "{0}" is not deployed; Thus, it cannot be redeployed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22001: The shared library "{0}" is already deployed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22002: Deploying new shared library: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22003: Redeploying shared library: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22004: Found shared library "{0}" in the MDS repository

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22005: Found version {1} of shared library "{0}" in the MDS repository

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22006: {0} was removed from the MDS repository

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22007: {0} was not removed from the MDS repository

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22008: {0} was not removed from the MDS repository (It may not be empty)

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22009: Failed to remove shared library {0}/{1} from the MDS repository

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22010: SharedLibraryDeploymentCoordinator not found

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22011: {0} is not a directory

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22012: Failed to delete {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22013: {0} does not exist, so nothing to delete.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22014: Shared library {0}/{1} has subscribers.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-22015: The shared library {0}/{1} cannot be undeployed because it is referenced by one or more composites: {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22016: A shared library classloader named {0} was created for {1}/{2}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22017: The classloader {0} for shared library {1}/{2} has been committed.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22018: The following codesources were added to the shared library ({0}/{1}) classloader: {2}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22019: The classloader {0} for shared library {1}/{2} has been closed.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22101: There was an error validating the composite patch on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22102: There was an error validating composite patch(s) on {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22103: The composite archive, {0}, does not contain a SAR file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22104: The SAR file, {0}, is not a composite patch archive.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22105: The sar file, {0}, does not contain a SCA-INF/patch.xml file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22106: The deployed composite corresponding to the archive {0} cannot be found

Cause:

Action:
Level: 1

Type: ERROR

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: SOA Folder 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: SOA Folder was successfully deleted.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25063: All composites in the folder were successfully started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25064: All composites in the folder were successfully stopped.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25065: All composites in the folder were successfully activated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25066: All composites in the folder 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 SOA folder operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25083: create folder 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 folder operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25086: start composites in folder operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25087: stop composites in folder operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25088: activate composites in folder operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25089: retire composites in folder operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25090: list all folder 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.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25103: Composite ({0}) endpoint ({1}) is successfully activated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25104: Composite ({0}) endpoint ({1}) is successfully deactivated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25105: Requested updates cannot be found.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25106: Requested shared data cannot be found.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25107: SOA Platform is quiesced.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25108: SOA Platform is not quiesced.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-50000: This profile contains the standard SOA platform and the BPM technologies.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50001: This profile contains the SOA Foundation technologies.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50002: This profile contains the BPEL SOA components.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50003: This profile contains the BPEL and Workflow technologies.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50004: This profile contains the standard SOA platform and the BPM technologies, plus the FULL adapter set.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50005: This profile contains the SOA Foundation technologies, plus the FULL adapter Set.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50006: This profile contains the SOA Foundation technologies as well as the B2B technologies.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50007: This profile contains the standalone B2B/Healthcare technologies.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50008: This profile contains the SOA platform and BPM technologies enabled in version 11g. This profile is meant for upgrade use cases.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50009: This profile contains the SOA platform technologies enabled in version 11g. This profile is meant for upgrade use cases.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-50010: Error occurred while trying to get the current SOA Profile name.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

SOA-50011: Error occurred while trying to obtain profile description for profile {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

SOA-50012: Error occurred while trying to query the status of the SOA Technology {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

SOA-50013: Error occurred while trying to change the current profile to {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50014: Error occurred while trying to get the domain directory from JRF.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50015: Error occurred while trying to get the domain install templates from CIE.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50016: Errors occurred while trying to obtain the list of supported profiles for this SOA domain. This likely means that there is a configuration error with the domain.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50017: No Profile found with this name {0}. Please select from one of the supported profiles.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50018: Exception occurred while trying to change profiles to {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50019: Error while attempting to get admin server connection info.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50020: Error occurred while creating WebLogic deployment Manager.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50021: No profile commands registered with this manager. This is likely a problem with the initialization of the profile manager.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50022: Attempt to change the current SOA Profile has failed. Please check the server log for details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50023: Error occurred while trying to update the current SOA Profile to {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50024: Attempt to deploy internal modules failed during a targeting change for application {0}. Please check the server log for details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50025: Attempt to undeploy internal modules failed during a targeting change for application {0}. Please check the server log for details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50026: Error during edit session operation. The operation that failed is {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50027: Error occurred while trying to obtain the AppDeploymentMBean for application {0}. The MBean is not available.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50028: Error occurred while trying to obtain the source path for application {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50029: Error occurred while waiting for a deployment operation to complete. Deployment command is null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50030: Error while trying to setup internal modules. Application {0} not available.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50031: Error in internal module setup for application {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50032: Error in internal module operation {0}. Deployment result is {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50033: No Targets were found that support soa-infra. This is a deployment error or an installation problem.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50034: Start module attempt for module name {0} failed. Deployment status = {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50035: Set of {0} modules for the new profile cannot be null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50036: Set of {0} modules for the new profile cannot be empty.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50037: Exception encountered during {0} module targeting for SOA profile transition.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50038: Module name {0} to be targeted is not found. This could be an installation problem, or could mean that a profile was chosen that does not match with the components installed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50039: Module name {0} to be un-targeted is not found. This could be an installation problem, or could mean that a profile was chosen that does not match with the components installed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50040: Error occurred during targeting operations for a SOA Profile transition.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-50041: The Modularity operation for the following modules: ({0}) has timed out waiting for a server deployment operation to complete. Please increase the value of the {1} system property and restart the server before attempting this command again.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-65001: No global transaction is currently associated with the executing thread "{0}".

Cause: No global transaction is currently associated with the calling thread.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65002: Failure to unwrap the wrapped DMS ExecutionContext "{0}" and associate it with the thread "{1}".

Cause: An error occured while unwrapping a DMS ExecutionContext.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65003: An error occurred while executing SOA's Instance Tracking Audit interceptor. See nested exception for root cause.

Cause: An error occured while executing the SOA Instance Tracking Audit Interceptor.

Action: Correct issue associated with the error's route cause.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65004: No FlowId is associated with request.

Cause: A request was not associated with a FlowId

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65005: No Component Instance ID is associated with the Executing Thread's DMS Execution Context

Cause: The Component Instance ID was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65006: No Component Instance ID creation time is associated with the Executing Thread's DMS Execution Context

Cause: The Component Instance ID creation time was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65007: The CommonFault associated with FaultId "{0}" could not be retrieved from the database.

Cause: The CommonFault associated with a given FaultId could not be retrieved

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65008: The fault Id was not associated with the Executing Thread DMS Execution Context.

Cause: The fault Id was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65009: The fault context was not associated with the Executing Thread DMS Execution Context.

Cause: The fault context was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65010: The Composite Sca Entity ID was not associated with the Executing Thread DMS Execution Context.

Cause: The composite Sca Entity Id was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65011: No Object found with JNDI Name "{0}"

Cause: No Object found with this JNDI Name

Action: Check values provided
Level: 1

Type: ERROR

Impact: Configuration

SOA-65012: Cannot cast object with jndi name "{0}" to class "{1}"

Cause: Invalid Class assignment for object with this JNDI Name

Action: Contact oracle support
Level: 1

Type: ERROR

Impact: Configuration

SOA-65013: Invalid async component state process count with original value "{0}" to new value "{1}"

Cause: Invalid async parallel process count with conflict of original and new value

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65014: Invalid async parallel process call sequence, the setPartialExecutions should be executed first with flow id "{0}" to component instance id "{1}"

Cause: Invalid async parallel process call sequence, the setPartialExecutions should be executed first.

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65015: Invalid async component completed process count with new value "{0}" to available partial parallel process count value "{1}"

Cause: Invalid async completed process count with conflict of new value and available partial parallel process count value

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65016: The FlowId "{0}" is not a valid FlowId. Valid values are numeric values.

Cause: Invalid FlowId format

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65017: The original Flow Event associated with the business flow "{0}" is missing.

Cause: Flow Trace issue.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65018: Invalid SCAEntityId "{0}".

Cause: The SCAEntityId value is not valid.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65019: The CommonFault associated with the Component Fault Key "{0}" could not be retrieved from the database.

Cause: No Fault is associated with the provided component fault key

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65020: The Composite Sca Entity ID Entry Time was not associated with the Executing Thread DMS Execution Context for the following FlowId "{0}".

Cause: The composite Sca Entity Id Entry Time was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65021: An error occurred while collecting sensor data.

Cause: An error occured while collecting sensor data

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65022: An invalid Flow id value was provided "{0}".

Cause: An invalid FlowId value was provided.

Action: FlowId values must be positive numeric values.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65023: Composite instance associated with FlowId "{0}" and Composite Instance Id "{1}" could not be found.

Cause: Internal instance tracking properties are missing.

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65024: The JPA persistence layer is not in health state.

Cause: The JPA persistence layer is not in health state.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65025: Unknown instance tracking policy name "{0}"

Cause: The supplied or configured instance tracking persistence policy name is unrecognized

Action: Configure the policy with a valid policy name choice
Level: 1

Type: WARNING

Impact: Configuration

SOA-65026: Setting instance tracking persistence policy to "{0}"

Cause: The instance tracking policy has been initialized on server start or reconfigured

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-65027: Unknown audit store policy name "{0}"

Cause: The supplied or configured audit store policy name is unrecognized

Action: Configure the policy with a valid policy name choice
Level: 1

Type: WARNING

Impact: Configuration

SOA-65028: Setting audit store policy to "{0}"

Cause: The audit store policy has been initialized on first use after server start

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-65029: Changing the audit store policy from "{1}" to "{0}"

Cause: The audit store policy has been reconfigured by the administrative user

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-65030: ''undeploy'' event was received for composite "{0}" and ScaEntityId "{1}". Marking associated active composite instances as stale.

Cause: Marking composite instance as stale suring undeployment

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-65031: The following error occurred while marking composite instances as stale during undeployment for composite "{0}" and ScaEntityId "{1}". {2}

Cause: An error occured while marking composite instances as stale during undeployment

Action:
Level: 1

Type: ERROR

Impact: Configuration

SOA-65032: The callback properties associated with Flow Id "{0}", Component Instance Id "{1}" and Internal Id "{2}" could not be retrieved.

Cause: Callback properties could not be retrieved. See error message and associated Exception for details.

Action:
Level: 1

Type: WARNING

Impact: Configuration

SOA-65033: Invalid component instance id "{0}" associated with Flow Entry for Flow Id "{1}" and component type "{2}".

Cause: The provided component instance id could not be converted to a number.

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65034: Error while retrieving Composite Instance associated with Flow Id "{0}", Composite SCA Entity Id "{1}" and creation time "{2}".

Cause: See child exception.

Action: See child exception.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65035: Error while retrieving Flow events for correlated flow "{0}" from Flow "{1}".

Cause: See child exception.

Action: See child exception.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65036: The flow instance for Flow Id "{0}" could not be retrieved from the database

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65037: Error while retrieving Flow events for correlated flow "{0}" associated with Correlation Flow ID "{1}".

Cause: See child exception.

Action: See child exception.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65038: null

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65039: null

Cause: See child exception.

Action: See child exception.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65040: Error while retrieving Composite Instance associated Composite Id "{0}".

Cause: See child exception.

Action: See child exception.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65041: AuditService is not available

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65042: An error occurred while creating DAO "{0}".

Cause: See child exception.

Action: See child exception.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65043: The Composite Instance ID was not associated with the Executing Thread DMS Execution Context for the following FlowId "{0}".

Cause: The composite instance ID was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65044: Error while retrieving Async Component State associated with Flow Id "{0}" and Component Instance Id "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65045: The SCASensorValue associated with ComponentInstanceId "{0}" and SensorName "{1}" could not be retrieved from the database.

Cause: The SCASensorValue associated with the given ComponentInstanceId and SensorName could not be retrieved

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65046: The SCAAsyncComponentState associated with FlowId "{0}" and ComponentInstanceId "{1}" could not be retrieved from the database.

Cause: The SCAAsyncComponentState associated with the given FlowId and ComponentInstanceId could not be retrieved

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65047: The FlowInstance associated with FlowId "{0}" could not be retrieved from the database.

Cause: The FlowInstance associated with the given FlowId could not be retrieved

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65048: The FlowInstance associated with CorrelationFlowId "{0}" could not be retrieved from the database.

Cause: The FlowInstance associated with the given CorrelationFlowId could not be retrieved

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65049: An error occurred while retrieving DAO "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65050: The FlowAssociation associated with FlowId "{0}" and CorrelationFlowId "{1}" could not be retrieved from the database.

Cause: The FlowAssociation associated with the given FlowId and CorrelationFlowId could not be retrieved

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65051: The SCAMetaData associated with FlowId "{0}", CIKey "{1}", InternalID "{2}" and MetaDataCategory "{3}" could not be retrieved from the database.

Cause: The SCAMetaData associated with the given FlowId, CIKey, InternalId and MetaDataCategory could not be retrieved

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65052: An error occurred while processing Flow Events associated with flow ID "{0}" in the context of migration.

Cause: Error while processing Flow Events associated with migration

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65053: Cannot create audit store policy of type "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65054: Cannot update null DAO.

Cause: The data access object was null

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65055: Failed to publish AuditEvent.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65056: Unknown audit store policy "{0}". Defaulting to policy "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65057: Failed to retrieve SOA configuration while retrieving audit store policy. Defaulting to policy "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65058: Policy "{0}" does not implement instance access policy.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65059: Failed to publish AuditDetails.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65060: Cannot flush buffered instances because there is no MGIContext currently set.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65061: Cannot participate in global transaction when MGIContext is using a local transaction.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65062: Cannot call onCommit before preCommit.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65063: Error performing operation "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65064: Unsupported DAO type "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65065: Failed to look up Spring bean "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65066: The callback properties associated with Flow Id "{0}", Component Instance Id "{1}" and Internal Id "{2}" could not be persisted.

Cause: Callback properties could not be persisted. See error message and associated Exception for details.

Action:
Level: 1

Type: WARNING

Impact: Configuration

SOA-65067: MGIContext is not set on current thread

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65068: Current thread is already associated with an MGIContext belonging to another FlowId. Existing MGIContext FlowId = {0}. Current FlowId = {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65069: Exception while persisting Instance Tracking data as part of transaction rollback. Pending operations: "{0}". Transaction status: "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65070: Exception while executing transaction synchronizer afterCompletion on TransactionSynchronizer "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65071: Audit event:"{0}" is not persisted

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65072: The callback properties associated with Flow Id "{0}", Component Instance Id "{1}" and Internal Id "{2}" could not be found.

Cause: Either: 1) A write failure occurred while storing the callback properties during the original request 2) The original request used the local callback optimization but the callback did not use the optimization 3) The front end host configuration is misconfigured which can result in local optimization issues

Action: Either: 1) Check the logs for the host that made the request for any possible failures while persisting the callback properties 2) Check the composite.xml of this composite and ensure the "oracle.webservices.local.optimization" property is applied consistently to the participating bindings 3) Check the front end host configuration for the servers or cluster involved
Level: 1

Type: WARNING

Impact: Configuration

SOA-65073: The provided flow instance title "{0}" is longer than the allowable maximum of 100 characters. The operation will proceed but the title will be truncated to 100 characters.

Cause: The provided flow instance title is longer than the allowable maximum of 100 characters.

Action: No action required. The operation will proceed but the title will be truncated to 100 characters.
Level: 1

Type: WARNING

Impact: Configuration

SOA-65074: The provided composite instance title "{0}" is longer than the allowable maximum of 100 characters. The operation will proceed but the title will be truncated to 100 characters.

Cause: The provided composite instance title is longer than the allowable maximum of 100 characters.

Action: No action required. The operation will proceed but the title will be truncated to 100 characters.
Level: 1

Type: WARNING

Impact: Configuration

SOA-65075: An error occurred while converting the metrics to XML.

Cause: See nested exception.

Action: See nested exception.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65076: Failure during ICS tracking integration

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65077: Correlation Flow Id "{0}" of new MGIContext "{1}" does not match Correlation Flow Id "{2}" of existing MGIContext "{3}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-67001: CircuitBreaker: Fault occured for reference -> "{0}"

Cause: Downstream system is unavailable.

Action:
Level: 1

Type: TRACE

Impact: Programmatic

SOA-67002: CircuitBreaker: Resuming suspended service -> "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67003: CircuitBreaker: Error sending notification when suspending/resuming a service

Cause: Error sending notification when suspending/resuming a service

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-67004: CircuitBreakerHistory: Adminstrator resumed {0} -> "{1}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67005: CircuitBreakerHistory: CircuitBreakerHistory: Resumed {0} -> "{1}" because downstream system is now available -> "{2}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67006: CircuitBreaker: Suspending service -> "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-67007: The adapter has been suspended due to outbound endpoint errored {0} times in {1} minutes. Outbound Endpoint: {2} Composite: {3} Partition: {4} Suspended Since: {5} The suspended adapter will retry the flow every {6} minute(s) or you can resume the adapter manually from EM. SOA Infra -> {7}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-67008: CircuitBreakerHistory: Suspending {0} -> "{1}" because downstream system is unavailable -> "{2}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67009: CircuitBreaker: Schedule TrickleFeed for -> "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67010: CircuitBreaker: Cancel TrickleFeed for -> "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67011: CircuitBreaker: Initializing suspended services during initialization.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67012: CircuitBreaker: Suspending service -> "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67013: CircuitBreaker: Trickle message for -> "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67014: CircuitBreaker: Can't send trickle feed, ResiliencyManager not initialized in Fabric

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67015: CircuitBreakerHistory: CircuitBreakerHistory: Resumed Web Service -> "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-67016: CircuitBreaker: Removing suspended services for undployed composite -> "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67017: CircuitBreaker: Resuming service -> "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-67018: "{0}" has been resumed because the outbound endpoint, "{1}" has recovered.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-67019: "{0}" has been manually resumed by the administrator

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-67020: ResiliencyPersistenceStore: Error while binding the Spring Application Context associate with SOA Resiliency Persistence functionality

Cause: Error while binding the Spring Application Context associate with SOA Resiliency Persistence functionality

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-67021: ResiliencyPersistenceStore: Error looking up EntityManager using JDNI name "{0}" for persistence unit 'soa_resiliency_persistence_unit'.

Cause: Error looking up EntityManager for persistence unit 'soa_resiliency_persistence_unit'.

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-67022: CircuitBreaker: Schedule Ramp-up job for -> "{0}" ({1}ms over {2} minutes)

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67023: CircuitBreaker: Cancel Ramp-up job for -> "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67024: CircuitBreaker: Set process delay of "{0}" for -> "{1}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67025: CircuitBreaker: Can't update process delay, ResiliencyManager not initialized in Fabric

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67026: CircuitBreaker: Adapter type "{0}" does not support suspend/resume functionality

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

SOA-67027: CircuitBreaker: Error looking up the RestService, "{0}", using RestServiceStore

Cause: Error looking up a RestService using RestServiceStore

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-67028: CircuitBreaker: Error reading/writing to resiliency tables

Cause: Error reading or writting to resiliency tables.

Action:
Level: 1

Type: ERROR

Impact: Programmatic

47 SOAPWS-BUF-00001 to SOAPWS-BUF-00005

SOAPWS-BUF-00001: No BufferingFeature registered for targetUri: {0}

Cause: A request to buffer a message used an unknown targetUri

Action: None
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-BUF-00002: Attempt to register targetURI=''{0}'' currently associated with BufferingRuntime=''{1}'' with a DIFFERENT BufferingRuntime=''{2}''.

Cause: A request to buffer a message used a targetUri that has already been associated with another buffering configuration. This is not allowed because a given targetURI MUST be routed to a unique BufferingFeature instance.

Action: None
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-BUF-00003: Cannot create a BufferingRuntime when effective buffering configuration (via WebServiceBufferingMBean/BufferingFeature) for a client/service is disabled altogether ({0}) or both request and response queues are disabled ({1})

Cause: A request to buffer a message was made but buffering configuration (via WebServiceBufferingMBean/BufferingFeature) makes the Buffering Service unavailable.

Action: None
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-BUF-00004: Invalid effective (based on direction of message, request/response) queue JNDI name: {0}

Cause: Queue configuration for the current message direction (request or response) gives an invalid JNDI name

Action: Check the queue configuration and give valid JNDI names
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-BUF-00005: Could not enqueue buffered message

Cause: There was an error enqueuing a message to the underlying buffering provider

Action: Check JMS configuration, and runtime state, including quotas
Level: 1

Type: SEVERE

Impact: WebService

48 SOAPWS-DATABIND-221200 to SOAPWS-DATABIND-221600

SOAPWS-DATABIND-221200: XML factory configuration error for "{0}".

Cause: This message indicates that the XML factory may not be configured correctly.

Action: No action is required.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221201: The mapping file (SystemId: "{0}") cannot be read.

Cause: This message indicates that the mapping file cannot be read.

Action: No action is required.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221202: The operation "{0}" is undefined in the WSDL.

Cause: This message indicates that the operation is undefined in the WSDL

Action: No action is required.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221203: The body part "{0}" is undefined in the WSDL.

Cause: This message indicates that the body part is undefined in the WSDL

Action: No action is required.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221204: The body part "{0}" of the input message is undefined in the WSDL.

Cause: This message indicates that the body part is undefined in the WSDL

Action: No action is required.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221205: "{0}" @WebMethod annotation has "exclude" element that is used with other elements like "action" or "operationName".

Cause: This message indicates that the @WebMethod annotation is invalid.

Action: Remove the annotation members.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221206: Unsupported Type {0} on {1}

Cause: This message indicates that the method has parameter or return value of unsupported type.

Action: Exclude the method
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221207: No valid method to be exposed on {0}

Cause: This message indicates that there is no valid WebMethod to be expose.

Action: No action
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221208: XML parsing error {0}

Cause: This message indicates an XML parsing error.

Action: No action.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221209: Databinding runtime error "{0}".

Cause: This message indicates a databinding runtime error.

Action: No action is required.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221210: The exception "{0}" is not bound to any service fault.

Cause: This message indicates the exception to be serialized is not bound to any declared service fault.

Action: No action is required.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221211: The wsdl:operation@name overloading is not supported. Please use "WebMethod operationName" annotation on {0} to customize the operation name.

Cause: This message indicates that some overloaded JAVA methods reult in wsdl:operation overloading which is not supported.

Action: Please use @WebMethod.operationName annotation to customize the operation name.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221212: The parameter or return value {0} of this method is annotated as a anonymous schema type; RequestWrapper and ResponseWrapper are required for WSDL generation.

Cause: The method is using document-literal wrapper style mapping, and a parameter or return value of this method is annotated as a anonymous schema type.

Action: Run JAXWS Tool to generate the wrapper classes
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221213: Missing required XML element "{0}" in the payload.

Cause: This message indicates that the there is a required element missing in the SOAP Body.

Action: Make sure the wire message is conformant to the WSDL/Schema
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221215: WSRuntimeImpl.init - failed to initialize WSDL from URL "{0}" Exception occurred: "{1}"

Cause: This message indicates that the WSDL at specified URL could either not be read or processing the wsdl failed for the specified reason

Action: Make sure the WSDL is available and valid, or take other action warranted by the exception message
Level: 1

Type: WARNING

Impact: WebService

SOAPWS-DATABIND-221403: Schema generation error.

Cause: This message indicates a JAXB error during schema generation.

Action: Ensure that your data is valid. Try enabling debug.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221406: unknown primitive: "{0}".

Cause: This message indicates a JAXB error during schema generation.

Action: Please ensure the product is installed correctly.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221407: unknown class name: "{0}".

Cause: This message indicates a JAXB error during schema generation.

Action: Please ensure the product is installed correctly.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221408: JAXB tool debug "{0}".

Cause: This message indicates a JAXB error during schema generation.

Action: Please ensure the product is installed correctly.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221409: Runtime initialization failure

Cause: This message indicates a JAXB runtime error creating a Runtime instance.

Action: Ensure that your data is valid. Try enabling debug.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221411: Cannot set fragment property on marshaller.

Cause: Toplink JAXB did not accept the Marshaller.JAXB_FRAGMENT property

Action: Ensure that you have the latest Eclipeslink jar.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221415: unmarshal FAILED, tag: {0}, class: {1}

Cause: This message indicates a JAXB failure unmarshalling an object.

Action: Ensure that your data is valid. Try enabling debug.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221416: marshal FAILED: <{0}> type: {1}, value: {2}

Cause: This message indicates a JAXB failure marshalling an object.

Action: Ensure that your data is valid. Try enabling debug.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221419: Incompatible revision for Eclipselink jar: found {0}. Revision must be {1} or higher.

Cause: This message indicates a version incompatibility between the libraries and the databinding code.

Action: Ensure that your Eclipselink is up-to-date.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221500: Failed to copy schemas due to exception {0}.

Cause: SDODatabindingTool runtime failure.

Action: Check input schemas objects system file paths.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221501: Schema source system id is missing

Cause: SDODatabinding runtime failure

Action: Set the input schema source system id.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221502: Invalid Filename created from System id of [{0}];

Cause: SDODatabinding runtime failure

Action: Set the correct file name.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221503: Failed to output source for [0].

Cause: SDODatabinding runtime failure

Action: Check the exception trace.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221504: The named property [{0}] is not found in this object instance.

Cause: SDODatabinding runtime failure

Action: Check type definitions in the schema set used.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221505: Object instance of type [{0}] is not a valid SDO object.

Cause: SDODatabinding runtime failure

Action: Check the input objects creation.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221506: Package name change is not supported in SDO databinding plugin.

Cause: SDODatabinding tool runtime failure

Action: None
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221507: Unable to locate request schema [{0}] due to exception {1}.

Cause: SDODatabinding tool runtime failure

Action: Correct the URL or make sure the schema does exist at the given URL.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221508: SDO databinding context has not been initialized.

Cause: SDODatabinding tool runtime failure

Action: Intialize SDO Databinding Context with application specific schemas.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221509: SDOBindingHandler encountered an exception while serializating the input.

Cause: SDODatabinding tool runtime failure

Action: None
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221510: SDOBindingHandler encountered an exception while deserializing the input.

Cause: SDODatabinding tool runtime failure

Action: None
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221511: Invalid SDO data type: {0}

Cause: SDODatabinding tool runtime failure

Action: Replace with a supported SDO primitive type.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-DATABIND-221600: JAXB runtime error "{0}".

Cause: This message indicates a JAXB runtime error.

Action: No action is required.
Level: 1

Type: SEVERE

Impact: WebService

49 SOAPWS-JMS-225010 to SOAPWS-JMS-225012

SOAPWS-JMS-225010: Error starting the JMS listener {0} {1}

Cause: Cannot start JMS listener

Action: Please check the JMS configuration.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-JMS-225011: Error closing JMS connection {0} {1}

Cause: Cannot close JMS connection

Action: Please check the JMS configuration.
Level: 1

Type: SEVERE

Impact: WebService

SOAPWS-JMS-225012: JMS onMessage exception {0} {1}

Cause: Exception in processing JMS onMessage

Action: Please check the exception cause details.
Level: 1

Type: SEVERE

Impact: WebService

50 TOP-00001 to TOP-28007

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 a type that implements {1}.

Cause: When using Java&nbsp;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 EclipseLink 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.

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 with the value [{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.

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.

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 [{1}] 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 of type [{1}] but the mapping uses transparent indirection (lazy loading), requiring it to be a superclass of [{2}].

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}] returns [{1}] but the mapping uses transparent indirection (lazy loading), requiring it to be a superclass of [{2}].

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}] takes [{1}] but the mapping uses transparent indirection (lazy loading), requiring it to be a superclass of [{2}].

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}] does not 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}] does not 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&nbsp;99-13 and "Indirection, Serialization, and Detachment" on page&nbsp;30-10.
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} exceeded. 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} exceeded. 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 exceeded. 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}]. Ensure that the class [{2}] 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: ConfigurationVerify the class name given in JDBCLogin.
Level: 1

Type: Error

Impact: 4005: DATABASE_ACCESSOR_NOT_CONNECTEDThe session is not connected to the database while attempting to read or write on the database.An application may have to log in again because the connection to the database might have been lost.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 log out 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 (see "Understanding Sequencing in Relational Projects" on page&nbsp;17-15) 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-04014: Cannot register SynchronizationListener.

Cause: TopLink cannot register the synchronization listener: underlying_exception_string. 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. When a unit of work is created and the external global transaction is not in existence, or if the system cannot acquire a reference to it, this error is reported.

Action: Verify that a JTS transaction is in progress before acquiring the unit of work.
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 to NULL 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-06093: Invalid Type Expression on [{0}]. The class does not have a descriptor, or a descriptor that does not use inheritance or uses a ClassExtractor for inheritance

Cause: The buildSelectionCriteria method was invoked on a mapping that was neither one-to-one nor one-to-many. Only the one-to-one and one-to-many mapping exposes this public API to build selection criteria. Using the buildSelectionCriteria method with other mapping types will not return correct results.

Action: Use the buildSelectionCriteria method only with one-to-one and one-to-many mappings.
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 descriptor 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: Cannot 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 EclipseLink 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.
Level: 1

Type: Error

Impact: Configuration

TOP-07013: You are using the deprecated SessionManager API and no EclipseLink.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 parents

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. 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. 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-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-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-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-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. 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&nbsp;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.
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/eclipselink-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}Consider using an alternative identity map to prevent this situation.{2}Refer to the EclipseLink documentation for more details regarding identity maps .

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}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 encrypting 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).

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 EclipseLink uses 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. 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 does not 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.

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 nested UnitOfWork. 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 UnitOfWork 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 UnitOfWork 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 UnitOfWork 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 fetch 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 UnitOfWork 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} does not 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} does not 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} does not 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 does not 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 UnitOfWork.

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-07153: Mapping annotations cannot be applied to fields or properties that 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. Where a @OneToMany is not mapped by another entity (i.e. it is the owning side and is uni-directional) a @JoinTable must be specified, not @JoinColumn(s). If @JoinTable is not specified, a default join table will be used instead; Specify @JoinTable only if the default configuration should be overridden.

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 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 annotations 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 because it is reserved for defaulting a sequence generator "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 because 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: OracleJDBC_10_1_0_2ProxyConnectionCustomizer 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: OracleJDBC_10_1_0_2ProxyConnectionCustomizer 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: OracleJDBC_10_1_0_2ProxyConnectionCustomizer requires PersistenceUnitProperties.ORACLE_PROXY_TYPE property value to be either Integer or convertable to Integer: for instance OracleConnection.PROXYTYPE_USER_NAME or 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 Collection

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 EclipseLink.

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: Null or zero primary key encountered in UnitOfWork clone [{0}], primary key [{1}]. Set descriptor''s IdValidation or the "eclipselink.id-validation" property.

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 an attribute-override 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&nbsp;QL parser does not recognize a clause in the EJB&nbsp;QL string.

Action: Validate the EJB&nbsp;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&nbsp;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&nbsp;QL string was not found.

Action: Ensure that the class is on the appropriate classpath.
Level: 1

Type: Error

Impact: Programmatic

TOP-08004: Error compiling the query [{0}], line {1}, column {2}: unknown identification variable [{3}]. The FROM clause of the query does not declare an identification variable [{3}].

Cause: TopLink was unable to resolve the alias used in the EJB&nbsp;QL string.

Action: Validate the identifiers used in the EJB&nbsp;QL string.
Level: 1

Type: Error

Impact: Programmatic

TOP-08005: Error compiling the query [{0}]. A problem was encountered resolving the class name - The class [{1}] 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: Error compiling the query [{0}]. A problem was encountered resolving the class name - The descriptor for [{1}] 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&nbsp;QL string.
Level: 1

Type: Error

Impact: Programmatic

TOP-08009: Problem compiling the query [{0}]. The expression [{1}] is currently not supported.

Cause: An unsupported expression was used in the EJB&nbsp;QL.

Action: Change the query to use only supported expressions.
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:
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-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&nbsp;28-6 or "Creating an EIS Interaction for a Named Query" on page&nbsp;25-25).
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&nbsp;28-6 or "Creating an EIS Interaction for a Named Query" on page&nbsp;25-25).
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&nbsp;28-6 or "Creating an EIS Interaction for a Named Query" on page&nbsp;25-25).
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 Projects" on page&nbsp;17-7).
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&nbsp;21-3 or "Configuring EIS Connection Specification Options at the Session Level" on page&nbsp;84-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 Projects" on page&nbsp;17-7).
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 Projects" on page&nbsp;17-7).
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 Projects" on page&nbsp;17-7).
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&nbsp;28-6 or "Creating an EIS Interaction for a Named Query" on page&nbsp;25-25).
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 Projects" on page&nbsp;17-7).
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 Projects" on page&nbsp;17-7).
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 Projects" on page&nbsp;17-7).
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&nbsp;28-6 or "Creating an EIS Interaction for a Named Query" on page&nbsp;25-25).
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&nbsp;21-3 or "Configuring EIS Connection Specification Options at the Session Level" on page&nbsp;84-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&nbsp;53, "Understanding EIS Mappings".
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 announcment

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, check your properties are set correctly.

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} and Topic Factory {1}. Also, check your context properties are set correctly.

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 deserialize 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: Attempt to parse an integer index from the XPath string xpathString.

Action: Ensure that the XPath is specified correctly.
Level: 1

Type: Error

Impact: Programmatic

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.

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

Cause: Error occurred during the object marshalling.

Action: See the generated exception for the root cause.

TOP-25004: An error occurred unmarshalling the document

Cause: Error while setting up an oracle.toplink.sessions.entitymanager.EntityManagerFactory.

Action: Ensure the correct setup of the EntityManagerFactory: initializeFromMain method of the EntityContainer should return true.
Level: 1

Type: Error

Impact: Programmatic

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.

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

Cause: Validation error.

Action: See the generated exception for the root cause.

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

Cause: A default root element was not specified for the XMLDescriptor mapped to the root-level object.

Action: Set a default root element on any XMLDescriptor that will be marshalled as a root-level object.

TOP-25007: A descriptor for class {0} was not found in the project. For JAXB, if the JAXBContext was bootstrapped using TypeMappingInfo[] you must call a marshal method that accepts TypeMappingInfo as an input parameter.

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

Cause: A descriptor for class ClassName was not found in the project.

Action: Ensure that the descriptor for this class exists.

TOP-25008: A descriptor with default root element {0} was not found in the project

Cause: A descriptor with the default root element element was not found in the project.

Action: Ensure that the descriptor for this class exists and that its default root element is specified.
Level: 1

Type: Error

Impact: Programmatic

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.

TOP-25010: A schema reference was not specified for the XMLDescriptor mapped to {0}

Cause: A schema reference was not specified for the XMLDescriptor mapped to.

Action: Set a schema reference on the correct descriptor.
Level: 1

Type: Error

Impact: Programmatic

Cause: A schema reference is not specified for the XMLDescriptor mapped to target.

Action: Specify the schema reference for the descriptor.

TOP-25011: A null argument was encountered

Cause: A null argument was encountered.

Action: Ensure that no null parameters are passed into any marshal or unmarshall methods on XMLMarshaller.
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

Cause: Failure to resolve the XML schema.

Action: See the generated exception for the root cause.

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

Cause: Failure to set schemas.

Action: See the generated exception for the root cause.

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

Cause: Error during the schema platform instantiation.

Action: See the generated exception for the root cause.

TOP-25015: An error occurred trying to resolve the namespace URI for {0}. A namespace resolver was not specified on the descriptor.

Cause: Failure to resolve the namespace URI for target.

Action: Specify a namespace resolver on the descriptor
Level: 1

Type: Error

Impact: Programmatic

Cause: An error occurred trying to resolve the namespace URI for. 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.

TOP-25016: A namespace for the prefix {0} was not found in the namespace resolver.

Cause: A namespace for the prefix prefix was not found in the namespace resolver.

Action: Ensure that the namespace for this prefix exists in the namespace resolver.
Level: 1

Type: Error

Impact: Programmatic

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.

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-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: EclipseLink 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: EclipseLink 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 and external transaction controller. 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 should return 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

51 UCM-CS-000001 to UCM-CS-800280

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-000007: Out of memory exception

Cause: An out of memory 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: INCIDENT_ERROR

Impact: Logging

UCM-CS-000008: service exception

Cause: A service 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-000009: data exception

Cause: A data 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-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: INCIDENT_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: INCIDENT_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-050026: Database running out of tablespace

Cause: The database system is running out of tablespace.

Action: Details are usually 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: INCIDENT_ERROR

Impact: Programmatic

UCM-CS-050027: Possible database connection failure encountered. Error message: ({0}).

Cause: The system has encountered a database connection failure.

Action: Details are usually 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: INCIDENT_ERROR

Impact: Programmatic

UCM-CS-050028: Unable to create database connection for the database {0} with connection string {1}. Please make sure that the connection string, user and password are correct.

Cause: The system has encountered an issue with creating a 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: INCIDENT_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 creating 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 creating 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 creating 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-800279: 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-800280: Offsite FTP cannot change to the directory '{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

52 UPG-OHS-00001 to UPG-OHS-00012

UPG-OHS-00001: Source path {0} does not refer to an Oracle HTTP Server {1} component.

Cause: An invalid source directory was specified.

Action: Select a valid Oracle HTTP Server component configuration directory.
Level: 1

Type: WARNING

Impact: UA

UPG-OHS-00002: An unknown error occurred while logging the migration results from file {0}.

Cause: The file specified could not be read, or Upgrade Assistant logging failed.

Action: Check for other errors with the upgrade task.
Level: 1

Type: WARNING

Impact: UA

UPG-OHS-00003: The configuration file {0} has an invalid format.

Cause: The file specified cannot be parsed due to an invalid or unexpected format.

Action: The information in the file specified must be migrated manually.
Level: 1

Type: WARNING

Impact: UA

UPG-OHS-00004: An error occurred while updating configuration file {0}.

Cause: The cause is unknown.

Action: The information in the file specified must be migrated manually.
Level: 1

Type: WARNING

Impact: UA

UPG-OHS-00005: An error occurred while copying configuration file {0} to {1}.

Cause: The cause is unknown.

Action: The source file specified must be manually copied to the destination file specified.
Level: 1

Type: WARNING

Impact: UA

UPG-OHS-00006: An error occurred while reading file {0}.

Cause: The cause is unknown.

Action: The information in the file specified must be migrated manually.
Level: 1

Type: WARNING

Impact: UA

UPG-OHS-00007: The OHS version {0} is not supported for upgrade.

Cause: This OHS Upgrade Assistant plugin supports upgrade only from OHS 11.1.1.6.0 onwards.

Action: Upgrade to a minimum supported version(11.1.1.6.0) and then try to upgrade henceforth.
Level: 1

Type: WARNING

Impact: UA

UPG-OHS-00008: The files at location {0} are inaccessible.

Cause: Files at this location do not have required permissions.

Action: Change the access permissions of the files at this location.
Level: 1

Type: WARNING

Impact: UA

UPG-OHS-00009: Path {0} does not exist.

Cause: The expected file is missing.

Action: Verify the source OHS installation.
Level: 1

Type: WARNING

Impact: UA

UPG-OHS-00010: Unable to parse {0} of the domain.

Cause: The syntax of the file is incorrect.

Action: Verify that the configuration of source domain is proper.
Level: 1

Type: WARNING

Impact: UA

UPG-OHS-00011: The import of wallet failed.

Cause: KSS operations failed.

Action: Import the wallets manually.
Level: 1

Type: WARNING

Impact: UA

UPG-OHS-00012: KSS operations failed.

Cause: The cause is unknown.

Action: Import the wallets manually.
Level: 1

Type: WARNING

Impact: UA

53 UPGAST-00001 to UPGAST-05005

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-00007: Domain {0} is configured as a compact domain which is not a valid starting point for upgrade.

Cause: A compact configured domain was specified.

Action: Specify a domain that is not configured as a compact domain.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00008: failed to copy {0} to domain

Cause: Unable to copy the specified file to the domain.

Action: See the Upgrade Assistant log file for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00009: Invalid log level: {0}.

Cause: The log level specified was not recognized.

Action: Run the command again, specifying a valid log level. Enter the command ua -help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00010: Port number {0} is not valid.

Cause: The port number specified was not a positive numeric value or was out of range.

Action: Specify a valid port number.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00011: Host name {0} is not valid or unknown.

Cause: Lookup of the specified host name failed.

Action: Specify a valid host name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00012: Required port is missing.

Cause: A required port was not entered.

Action: Enter the required port.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00013: Required user name is missing.

Cause: A required user name was not entered.

Action: Enter the required user name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00014: unable to connect to WebLogic Server at {0}:{1}

Cause: Failed connecting to the WebLogic Server at the specified host and port.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00015: Required listen address is missing.

Cause: A required listen address was not entered.

Action: Enter the required listen address.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00016: Required password is missing.

Cause: A required password was not entered.

Action: Enter the required password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00017: Required confirm password is missing.

Cause: A required confirm password was not entered.

Action: Enter the required confirm password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00018: Password and confirm password do not match.

Cause: The password and confirm password do not have the same value.

Action: Enter the same value for the password and confirm password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00019: User name may not contain commas, tabs, spaces, or any of the following characters: {0}

Cause: An invalid user name was specified.

Action: Enter the user name using only valid characters.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00020: Listen address {0} is not valid or unknown.

Cause: Lookup of the specified listen address failed.

Action: Specify a valid listen address.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00021: WLST script failure, see {0} for details

Cause: The execution of a WLST script has failed

Action: Check the specified WLST output file for the details of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00023: Standalone template {0} does not exist for component {1} of type {2}.

Cause: A template was not found for the listed component.

Action: Install the components standalone environment and then rerun the upgrade in that standalone environment.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00024: failed reading {0}

Cause: Unable to read or parse the specified file.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00025: The password must be at least 8 alphanumeric characters with at least one number or special character.

Cause: An invalid password was specified.

Action: Enter a password using 8 alphanumeric characters with at least one number or special character.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00026: failed reading {0}

Cause: Unable to read or parse the specified OPMN file.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00027: OPMN file {0} does not exist in the instance directory.

Cause: The specified OPMN file did not exist.

Action: Specify a valid instance directory where the specified OPMN file exists
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00028: Template {0} does not exist for component {1} of type {2}.

Cause: A template was not found for the listed component.

Action: Install the listed component and then rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00029: Directory is not a valid domain for upgrade. {0}

Cause: The specified directory was not a valid Oracle WebLogic domain for standalone upgrades. The domain was not created during a previous standalone upgrade.

Action: Specify an Oracle WebLogic domain that is created during a previous standalone upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00030: The specified domain name {0} is invalid. It must include only alphanumeric characters, hyphens ("-") or underscore characters ("_") and contain at least one letter but must not start with a number.

Cause: An invalid domain name was specified.

Action: Enter a valid domain name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00031: unable to get the active DomainMBean for the WebLogic Server domain

Cause: Failed getting the active DomainMBean for the WebLogic Server domain.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00032: unable to communicate with the WebLogic Server

Cause: Communication with the WebLogic Administrative Server was either lost or never established.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00033: Required domain directory is missing.

Cause: A required domain directory was not entered.

Action: Enter the required domain directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00037: unable to fetch or store attribute "{0}" in the WebLogic Server

Cause: 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-00039: failed deleting {0}

Cause: Unable to delete the specified file.

Action: Manually delete the specified file.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00040: unable to get the DomainRuntimeMBean for the WebLogic Server domain

Cause: Failed getting the DomainRuntimeMBean for the current WebLogic Server domain.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00041: 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 Upgrade Assistant log file for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00047: failed to read the installer inventory

Cause: The install inventory could not be accessed.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00048: unable to open the file

Cause: Failed to open the file.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00049: unable to read the file

Cause: Failed to read the 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: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00054: An error occured loading the domain configuration file {0}

Cause: Either the specified directory does not contain the expected file, or the file does not conform to the expected syntax.

Action: Specify a valid WebLogic domain root directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00056: error initializing upgrade plug-in for {0}

Cause: An unexpected error occurred initializing an upgrade plug-in.

Action: Contact My Oracle Support. See the secondary error message for additional details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00058: {0} file does not exist or cannot be accessed.

Cause: The specified file did not exist or could not be accessed.

Action: Make sure the path to the file is correct.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-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-00093: {0} directory does not exist or is not a directory.

Cause: The specified directory did not exist or was not a directory.

Action: Specify a valid directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00094: {0} directory already exists.

Cause: The specified directory already existed.

Action: Specify a valid directory that does not exist.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00095: {0} directory is not writable.

Cause: The specified directory must have write permissions.

Action: Specify a directory that is writable or correct the permissions.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00096: error initializing the help system

Cause: An error occurred while setting up the help system.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00097: The IP address of the host {0} cannot be determined.

Cause: The network address of the specified host could not be determined.

Action: Check the validity of the specified host.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00098: error setting the Oracle look-and-feel for the graphical user interface

Cause: An error occurred while setting the appearance for the graphical user interface.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00107: The DISPLAY environment variable is not set. The graphical user interface (GUI) requires that this environment variable be set on UNIX.

Cause: The required DISPLAY environment variable was not defined.

Action: Set the required DISPLAY environment variable and then rerun the Upgrade Assistant.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00173: The plugin for {0} has requested an input value named {1} but that name is not in the upgrade descriptor.

Cause: There was an inconsistency between the plugin descriptor definition and the input values requested by the plugin.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00174: failed to create or write to response file

Cause: The file specified for saving responses could not be created or written to.

Action: Specify a file in a location that is writable.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00175: Can not read response file {0}.

Cause: The file specified for reading responses does not exist, or can not be read.

Action: Specify a readable response file.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00176: Response file specifies an unknown upgrade step {0}.

Cause: The response file specifies an upgrade that is unknown in this Fusion Middleware installation. Either the response file is for some other environment, or the Upgrade Descriptor files have not been properly installed.

Action: Specify a response file generated for this installation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00177: Response file line is not understood: {0}

Cause: The response file contains syntax errors.

Action: Correct the syntax errors in the response file and run the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00178: Response file specifies a bad input name, {0}.

Cause: The response file contains syntax errors, or is not of the correct version.

Action: Correct the syntax errors in the response file and run the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00180: error loading upgrade plug-in for {0}

Cause: An unexpected error occurred loading an upgrade plug-in.

Action: Contact My Oracle Support. See the secondary error message for additional details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00181: error during execution of upgrade plug-in for {0}

Cause: An unexpected error occurred during execution of an upgrade plug-in.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00182: The examination phase for plug-in {0} will not be run due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevented the examination phase from running.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00183: The upgrade phase for plug-in {0} will not be run due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevented the upgrade phase from running.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00185: failed to load JDBC driver

Cause: There was a failure loading a JDBC driver.

Action: See the log file for details. Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00186: unable to connect to database as the DBA user name {0}

Cause: Required fields to connect to a database were not supplied.

Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00187: Unable to connect to WebLogic Admin Server. Some fields are empty.

Cause: Required fields to connect to a WebLogic Admin Server were not supplied.

Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-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 My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00190: {0} component version is {1}, status is {2}, upgraded flag is {3}

Cause: After a successful schema upgrade the SCHEMA_VERSION_REGISTRY status column is not "VALID", or the upgraded column is not "Y".

Action: Contact My Oracle Support.
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.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00192: A dependency by component {0} on component {1} is unresolved.

Cause: A required component was not found while discovering upgrade components and their dependencies.

Action: Make sure the required component has been installed and that its upgrade descriptor XML file is in the plugins/upgrade directory of their product home.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00196: The validate method for plug-in {0} will not be called due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevents the validate method from executing.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00198: Descriptor tag {0} is only allowed in components of type={1}

Cause: An upgrade plugin descriptor is improperly formed.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00200: Message reference {0} is not defined in resource bundle {1}.

Cause: An upgrade plugin descriptor is referencing an undefined message.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00202: Unable to validate credentials. Some fields are empty.

Cause: Required fields to validate credentials were not supplied.

Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00203: validate method is not implemented by plug-in {0} for input named {1}.

Cause: Required validate method was not implemented by plug-in or the signature of the validate method is incorrect.

Action: Implement the required validate method with the correct signature.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00204: Response file specifies an unknown field "{0}".

Cause: The response file specifies an input value with a qualified field name that is unknown for inputs of this type.

Action: Specify a response file generated for this installation or correct your editing error.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00205: Response file specifies an incorrect or no format version. Version must be {0}.

Cause: The fileFormatVersion specified in the [GENERAL] section of the file is either missing or incorrect for this program.

Action: Generate new response files using the same version of the program that is going to read them.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00206: No upgrade descriptor files were found in the Oracle home, yet a response file was specified.

Cause: Either this Oracle home contains no upgradable components and you are using a response file generated for a different installation, or the installation is incomplete or damaged.

Action: Make sure that this installation is the one you intended to upgrade, and that the Upgrade Descriptor files are in the plugins/upgrade/ directories
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00207: The Upgrade Descriptor in file {0} specifies a bad value "{1}" for the attribute named "{2}".

Cause: An attribute in a tag in an Upgrade Descriptor, which provides information to the Upgrade Assistant about individual upgrade plugins, contains an improper value.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00208: An unrecognized database type "{0}" was specified in a descriptor or response file.

Cause: Database type names in descriptor and response files must come from a fixed list of names. A name was encountered which is not on the list.

Action: Correct the spelling of your database type and run the program again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00209: directory path is not specified

Cause: A required directory path was not entered.

Action: Enter the required directory path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00210: file path is not specified

Cause: A required file path was not entered.

Action: Enter the required file path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00211: The response file specified a dependency on a plugin numbered {0} but either no plugin in the file has that as an INSTANCE value, or the descriptor file does not indicate that such a dependency is possible.

Cause: All dependsOnPluginInstance properties must refer to numbers defined earlier in the response file with a pluginInstance property, and must refer to a plugin to which such a dependency is allowed by the upgrade descriptor file.

Action: If you created or edited the response file, correct the error and try again. If this is a response file generated by the Upgrade Assistant, contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00212: unable to connect to database as the schema user {0}

Cause: Required fields to connect to a database were not supplied.

Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00213: Unable to connect to database as the dba user "{0}".

Cause: The database connection failed for the specified reason.

Action: Correct the problem using information provided in the log file; then retry the operation. In particular if the indicated reason is "Login has timed out" verify that the host and port are correct and make sure the database is up and is configured for network access.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00214: Unable to connect to database as the schema user "{0}".

Cause: The database connection failed for the specified reason.

Action: Correct the problem using information provided in the log file; then retry the operation. In particular if the indicated reason is "Login has timed out" verify that the host and port are correct and make sure the database is up and is configured for network access.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00215: Upgrade is not being done due to examine failures.

Cause: When using a response file, actual upgrades are not done if any plugin can not complete its EXAMINE phase.

Action: Correct the problem using information provided in the log file; then retry the operation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00216: A library file "{0}" referred to in an Upgrade Descriptor file does not exist.

Cause: Upgrade Plugins can refer to other JAR files. A file in such a reference can not be found. This can be caused by an incorrect installation.

Action: Contact My Oracle Support
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00217: directory path is not specified {0}

Cause: A required directory path was not entered.

Action: Enter the required directory path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00218: file path is not specified {0}

Cause: A required file path was not entered.

Action: Enter the required file path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00219: No schemas were found for component {0} in the Schema Version Registry.

Cause: A database query to get a list of schemas from the Schema Version Registry returned an empty list.

Action: Verify that you have schemas for the specified component.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00220: failed to get a list of schemas from the Schema Version Registry

Cause: A database query to get a list of schemas from the Schema Version failed.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00221: unexpected error upgrading schema

Cause: An unexpected error occurred during schema upgrade.

Action: Check the error messages in the Upgrade Assistant log files. Correct the problem before running the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00222: invalid database type specified

Cause: An invalid database type was specified.

Action: The database type specified is not supported by the RCU JDBCEngine. Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00223: The upgrade of "{0}" is being skipped because the upgrade for "{1}" has either failed or been skipped.

Cause: One component upgrade which is a pre-requisite for a second component's upgrade has not finished successfully. Therefore the second component's upgrade has not been executed.

Action: Fix the original problem and run Upgrade again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00224: The specified database does not contain any schemas for {0} or the database user lacks privilege to view the schemas.

Cause: The database you have specified does not contain any schemas registered as belonging to the component you are upgrading, or else the current database user lacks privilege to query the contents of the schema version registry.

Action: Verify that the database contains schema entries in schema version registry. If it does not, specify a different database. Verify that the user has DBA privilege. Connect to the database as DBA.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00225: The response file contains a non-numeric value "{0}" where a number is required.

Cause: Plugin ID numbers must be decimal integers.

Action: Correct the response file and run the program again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00226: The database connect string format is incorrect. The correct format is: {0}

Cause: The database connect string format was specified incorrectly.

Action: Enter the database connect string using the correct format.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00227: Oracle instance directory path is not specified

Cause: A required Oracle instance directory path was not entered.

Action: Enter the required Oracle instance directory path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00228: Oracle instance directory path is not specified {0}

Cause: A required Oracle instance directory path was not entered.

Action: Enter the required Oracle instance directory path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00229: The directory {0} is not an 11g Oracle instance directory.

Cause: The directory specified was not a valid 11g Oracle instance directory.

Action: Enter a valid 11g Oracle instance directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00230: No editions were found

Cause: A database query to get a list of editions returned an empty list.

Action: Verify that you have editions enabled and have created one or more editions.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00231: failed to get a list of editions

Cause: A database query to get a list of editions failed

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00232: database query for compatibility failed: {0}

Cause: A database query to check that database compatibility is 11.2.0 or greater failed

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00233: database compatibility must be 11.2.0 or greater not {0}

Cause: An EBR-enabled Oracle database requires that compatibility parameter be set to "11.2.0" or greater. However the actual compatibility was less than version 11.2.0

Action: Issue the SQL command ALTER SYSTEM SET COMPATIBLE = '11.2.0' SCOPE=SPFILE.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00235: Schema version registry table does not exist for component {0}

Cause: An attempt to list the contents of the schema version registry table for the component failed because the schema version registry does not exist.

Action: This is an informational message. No further action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-00236: There is no schema version registry entry for component {0}

Cause: An attempt to list the contents of the schema version registry table for the component failed because no registry entry exists for the component.

Action: This is an informational message. No further action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-00237: A duplicate component definition for component {0} has been detected in product home {1}.

Cause: Component names must be unique within an Oracle home. Either the component descriptor files are incorrect, or multiple copies of the same component have been installed in the same Oracle home.

Action: Remove the duplicate installations, or contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00238: A dependency by component {0} on component {1} is unresolved. Upgrades of component {0} will be disabled.

Cause: A dependent component was not found while discovering upgrade components and their dependencies.

Action: Make sure the required component has been installed.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00239: messageclass attribute must be specified for message reference {0}

Cause: A resource bundle was not specified in the component's upgrade descriptor.

Action: Specify the component's resource bundle using the messageclass attribute.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00240: An unexpected error was encountered while monitoring the progress of a plugin.

Cause: During the upgrade phase of a plugin, the upgrade monitor thread encountered an error while shutting down

Action: The Fusion Middleware schema upgrade was not impacted and the error can be ignored.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00244: unable to connect to {0} Server {1}

Cause: Required fields to connect to the specified Server were not supplied.

Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00245: An unexpected error has occurred while initializing internal data structures.

Cause: A problem was encountered while setting up the internal WLS descriptor.

Action: Contact My Oracle Support
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00246: The selected domain has a version of {0} which is less than the minimum of {1}.

Cause: Upgrade requires the domain to be at a certain minimum version, which this domain does not meet.

Action: Select a different domain, or run the Reconfiguration tool before trying to upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00247: unable to connect to WebLogic Server at {0}:{1} {2}

Cause: Failed connecting to the WebLogic Server at the specified host and port.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00248: Descriptor item {0} missing required "text" attribute.

Cause: The named input tag in an upgrade descriptor does not have a required "text" attribute.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00249: isOptionalInputRequired method is not implemented by plug-in {0} for input named {1}.

Cause: Required isOptionalInputRequired method was not implemented by plug-in or the signature of the isOptionalInputRequired is incorrect.

Action: Implement the required isOptionalInputRequired method with the correct signature.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00250: Required input {0} is missing from section {1} in the response file.

Cause: The response file does not supply any values for a required input.

Action: Correct the response file and retry the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00251: An error occured reading Upgrade Descriptor file {0}

Cause: The file does not conform to the expected syntax.

Action: See the secondary message for additional information. Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00252: Required input {0} is missing from section {1} in response file.

Cause: The response file does not supply any values for an optional input that the plugin indicates it needs in this case.

Action: Correct the response file and retry the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00254: invalid response file contents

Cause: The response file is not a valid response file.

Action: Specify a response file generated for this installation or correct your editing error. See secondary message for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00255: More than one component definition contains an upgrade for a component. The following component descriptor files each contain an upgrade for component {0}: {1}

Cause: There must be only one upgrader of a component within an Oracle home. Two or more schema input declarations exist that are upgrading the same component-id.

Action: Remove the duplicate upgrades, or contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00256: Upgrade is being skipped because the -examine flag is set

Cause: When using a response file, actual upgrades are not done when the -examine command line option is set.

Action: If you want to perform an actual upgrade in response file mode remove the -examine flag from the command line. If you intended to perform just the examine phase, no action is necessary.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00257: The -examine flag is only allowed with the -response flag

Cause: You cannot specify -examine command line option without the -response option.

Action: You cannot specify the -examine flag when running the upgrade tool in GUI mode. If you want to perform an examine without an actual upgrade you must also specify -response on the command line.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00258: Component plugin {0} named in response file is not in domain {1}.

Cause: The response file references a component plugin which is not configured in the specified domain.

Action: Specify a response file generated for this domain.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00259: The getInitialValue method for plug-in {0} will not be called due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevents the getInitialValue method from executing.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00260: getInitialValue method is not implemented by plug-in {0} for input named {1}.

Cause: Required getInitialValue method was not implemented by plug-in or the signature of the getInitialValue method is incorrect.

Action: Implement the required getInitialValue method with the correct signature.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00261: The isOptionalInputRequired method for plug-in {0} will not be called due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevents the isOptionalInputRequired method from executing.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00262: The log directory did not exist or cannot be accessed: {0}.

Cause: The log directory specified was not recognized as an existing, writable directory.

Action: Run the command again, specifying a valid log directory. If necessary create the log directory and make sure it is a writable directory. See the command line help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00263: The response file contained both configuration type and schema type upgrades.

Cause: The response file contains a mix of configuration type and schema type upgrades.

Action: Change the response file to specify only configuration type or schema type upgrades then rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00264: Bad "name" attribute value in Upgrade Descriptor.

Cause: Names in Upgrade Descriptor files must be alphanumeric.

Action: Correct the name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00265: Directory is not a valid domain for upgrade. {0}

Cause: The specified directory was not a valid Oracle WebLogic domain.

Action: Specify an existing WebLogic domain directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00266: Oracle instance directory {0} is not a unique directory path.

Cause: A duplicate Oracle instance directory path was specified.

Action: Specify Oracle instance directoies that are not duplicated.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00267: isUpgradeRequired method is not implemented by plug-in {0}.

Cause: Required isUpgradeRequired method was not implemented by plug-in or the signature of the isUpgradeRequired is incorrect.

Action: Implement the required isUpgradeRequired method with the correct signature.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00268: The response file specified is not for a standalone upgrade.

Cause: The response file contained WebLogic credentials that are not valid during a standalone upgrade.

Action: Regenerate the response file and rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00269: The response file specified is not for an upgrade requiring WebLogic credentials.

Cause: The response file does not contain WebLogic credentials that are required during an online upgrade.

Action: Regenerate the response file and rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00270: Directory is not a valid domain for upgrade. {0}

Cause: The specified directory was not a valid Oracle WebLogic domain.

Action: See the log file for details. Specify a valid WebLogic domain directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00271: Validation of specified domain failed. {0}

Cause: The specified domain failed validation which will prevent domain reconfiguration.

Action: Refer to the Troubleshooting section of your upgrade documentation for info on supported domain upgrades. See the log file for details of the validation failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00272: Unable to connect to EBR-enabled Oracle database for schema {0} because an edition name was not specified.

Cause: An edition name must be provided to establish a connection to an EBR-enabled Oracle Database.

Action: Add an edition name to the response file (when using response file mode).
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00273: Initialization of the inputs for schema {0} in component {1} failed with the error: {2}

Cause: One of the inputs was not valid.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00280: The -examine flag is not allowed with the -readiness flag

Cause: You cannot specify -examine command line option with the -readiness option.

Action: You cannot specify the -examine flag when running the upgrade tool in readiness check mode. If you want to perform an examine without an actual upgrade you must remove the -response option from the command line.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00281: Upgrade is being skipped because the -readiness flag is set

Cause: Actual upgrades are not done when the -readiness command line option is set.

Action: If you want to perform an actual upgrade remove the -readiness flag from the command line. If you intended to perform just the readiness phase, no action is necessary.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00282: Upgrade readiness check completed with one or more errors.

Cause: Examine the readiness check report file and the log file to understand which checks failed.

Action: Correct the problem using information provided in the log file; then retry the operation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00283: The readiness check phase for plug-in {0} will not be run due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevents the readiness check phase from running.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00284: The isUpgradeRequired method for plug-in {0} will not be called due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevents the isUpgradeRequired method from executing.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00286: A response file referenced one or more schema user names that did not have a matching datasource in the specified domain.

Cause: The auto-datasource option found one or more schema user names that did not have a matching datasource.

Action: Review the domain's datasources and response file specified during upgrade to identify the mismatch.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00287: The getPluginInstantiationCount method for plug-in {0} will not be called due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevents the getPluginInstantiationCount method from executing.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00288: Duplicate schema version registry entries matched the auto-datasource query.

Cause: The auto-datasource option found more than one schema version registry entry that matched the component-id and data source user name.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00289: Plugin {0} disabled, isUpgradeRequired returned exception.

Cause: The plugin threw an exception while processing the request to determine if it has schemas within the domain to upgrade.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00290: Plugin {0} disabled, the auto-datasource request returned an error.

Cause: The auto-datasource option failed while processing the request for this plugin.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00291: The schema newversion attribute is missing for component {0}

Cause: The upgrade framework has detected that the required schema newversion= attribute was missing in an upgrade descriptor file.

Action: Correct the upgrade descriptor file. Starting in release 12.1.3 the <schema> tags must include a newversion= attribute that shows what the schema version number will become after sucecssful upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00292: Null value found in UAWLSINTERNAL field "{0}" of the response file.

Cause: A value necessary for identifying the WLS domain is missing.

Action: Correct the response file and rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00294: Unable to establish a connection to a WLS server.

Cause: Attempt was made to connect to a WLS server during an offline upgrade.

Action: Correct the response file and rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00295: The selected domain has a version of {0} which must be less than the current version {1}.

Cause: Running readiness checks requires the domain to be at a version prior to the current version. This prerequisite has not been met.

Action: Choose a different domain that is for a previous version of Oracle Fusion Middleware.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00296: The Upgrade Descriptor in file {0} specifies an illegal combination of attributes "{1}" and "{2}".

Cause: A tag in an Upgrade Descriptor, which provides information to the Upgrade Assistant about individual upgrade plugins, contains two attributes whose values are incompatible with each other.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00297: no text found for offset {0}, read amount {1}, document length {2}

Cause: Unknown; possibly the result of previous errors.

Action: Refresh the file viewer window if possible.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00298: find position {0}, offset, {1}, search string {2}

Cause: Unknown; possibly the result of previous errors.

Action: Refresh the file viewer window if possible.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00300: The preselected check box for {0} has been deselected by the user

Cause: The user has manually unchecked an upgrade item that was preselected by Upgrade Assistant.

Action: Make sure that Oracle's recommendation to always upgrade this item really does not apply to your situation. If you are unsure then this box should be checked in most cases
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00301: getTableRowCount method is not implemented by plug-in {0} for input named {1}.

Cause: Required getTableRowCount method was not implemented by plug-in or the signature of the getTableRowCount method is incorrect.

Action: Implement the required getTableRowCount method with the correct signature.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00302: An exception occured while constructing the backing model for table input {0}.

Cause: A call to the plugin method "getTableRowCount" or "getInitialValue" failed.

Action: See the log file for exception details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00303: Schema upgrade disabled for plugin {0} because feature set {1} is not installed.

Cause: A plugin declared a dependency on a feature set, and the needed feature set is not installed. Schema upgrade of the component is disallowed.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00304: The updateOptionalInputPage method cannot be called for the non-optional input {0}.

Cause: An error occurred calling the updateOptionalInputPage method.

Action: Change the specified input to be optional.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00305: The updateOptionalCustomInput method cannot be called for the non-optional input {0}.

Cause: An error occurred calling the updateOptionalCustomInput method.

Action: Change the specified input to be optional.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00306: The updateOptionalInputPage method can only be called for top level inputs. Input {0} is a custom input or option input.

Cause: An error occurred calling the updateOptionalInputPage method.

Action: Change the specified input to be a top level input.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00307: The updateOptionalCustomInput method cannot be called for the non-custom input {0}.

Cause: An error occurred calling the updateOptionalCustomInput method.

Action: Change the specified input to be a custom input.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00308: An exception occured while resizing the backing model for table input {0}.

Cause: A call to the plugin method "getTableRowCount" failed.

Action: See the log file for exception details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00309: An invalid database URL was specified for schema {0}: {1}

Cause: An incorrectly formed database URL was identified.

Action: Fix the datasource definition in your domain configuration using the WebLogic Server Administration Console.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00310: An invalid database URL was specified for datasource {0} with schema {1}: {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00320: Exception raised while running a concurrent upgrade task. {0}

Cause: An exception was raised while running a upgrade task in a concurrent thread. Check the stack trace for detailed information.

Action: Attempt to correct the environment problem if any, then retry the upgrade. Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00321: The -threads option was passed an illegal value for number of threads: {0}. Must be an integer from {1} to {2}.

Cause: The -threads option was passed a value that is outside the permitted range of threads.

Action: Run the command again, specifying a valid number of threads, this value determines the number of schema upgrade plugins that can be run at the same time. See the command line help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00323: Was unable to terminate the thread executor pool

Cause: The thread pool that is used to schedule multiple plugins concurrently, could not be terminated after being shut down. The cause of this is unknown.

Action: There is a very long timeout in order to give the thread pool ample time to terminate but the timeout period was still exceeded. There should not be any adverse affect due to this error
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00324: Was unable to terminate the thread executor pool, timeout reached while performing {0}.

Cause: The thread pool that is used to schedule multiple plugins concurrently, could not be terminated after being shut down. The timeout period was reached

Action: There is a very long timeout in order to give the thread pool ample time to terminate but the timeout period was still exceeded. There should not be any adverse affect due to this error.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00325: database query for server identify failed: {0}

Cause: A database query to compare database server identity failed

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00328: The schema version registry table does not exist on this database.

Cause: The schema version registry table does not exist, because the required 12c schemas, such as the new Service Table schema, have not been created by RCU. The registry table must exist in order to run Upgrade Assistant.

Action: Create the required 12c schema using RCU before running the Upgrade Assistant. Refer to the upgrade planning guide for the list of required schemas for this release.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00329: The schema version registry "edition" column does not exist on this database.

Cause: The schema version registry table "edition" column does not exist, because the required 12c schemas, such as the new Service Table schema have not been created by RCU. The registry table must exist in order to run Upgrade Assistant.

Action: Create the required 12c schemas using RCU before running the Upgrade Assistant. Refer to the upgrade planning guide for the list of required schemas for this release.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00330: Unable to query schema version registry for schema: {0}

Cause: An attempt to perform schema version registry queries failed.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00352: The -readiness option is not allowed in a standalone environment.

Cause: You cannot specify the -readiness option in a standalone installation.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00353: Upgrade readiness check was unable to locate a standard query method for {0}

Cause: Readiness check was unable to locate the code for a standard query.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00355: The selected domain has a version of {0} which appears to not be a valid version number.

Cause: Upgrade requires the domain to be at a certain version, which this domain does not meet.

Action: Select a different domain, or run the Reconfiguration tool before trying to upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00356: The specified domain has a version of {0} which is less than the minimum of {1}.

Cause: The domain is at a version less than the minimum version.

Action: Specify a domain that is more recent than the minimum viable version.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00357: Upgrade readiness check returned an empty result set for test {0}, schema tag {1}, database object {2}

Cause: Readiness check encountered an error during execution of a standard query.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00358: Upgrade readiness check encountered an unexpected error for test {0}, schema tag {1}, database object {2}

Cause: Readiness check encountered an error during execution of a standard query.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00359: Upgrade readiness check encountered a method invocation error for test {0}, schema tag {1}, database object {2}, query {3}

Cause: Readiness check encountered an error during execution of a standard query.

Action: Contact My Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00370: getTablespaceName is only supported for Oracle Database not {0}.

Cause: An upgrade plugin used an API that is only supported for the Oracle Database.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00371: A database query to return tablespace name failed: {0}

Cause: A database query to identify the tablespace failed

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00372: A database query to detect consolidated schema failed: {0}

Cause: A database query to detect if this schema is consolidated failed

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00373: A readiness check that does not apply to consolidated schemas has been skipped for test {0}, schema tag {1}, database object {2}

Cause: A standard readiness test was called that does not apply to consolidated schemas. The upgrade framework has skipped the test. This is a successful outcome.

Action: No further action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-00374: SQL Query failed because it is only applicable to a consolidated schema: {0}

Cause: A database query that obtains information specific to consolidated schemas was called for a non-consolidated schema.

Action: No further action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-05001: Error connecting to {0} as user {1}.

Cause: A error occurred attempting to connect to the specified database.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05002: Error creating Java DB schema {0}.

Cause: A error occurred attempting to create the specified Java DB schema.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05003: Error getting the Java DB Schema Version Registry table.

Cause: A error occurred locating the Schema Version Registry table for a Java DB.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05004: Error registering the JDBC drver class {0}.

Cause: A error occurred registering the specified JDBC driver.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-05005: Unsupported database {0} identified.

Cause: A database that is not supported was specified.

Action: Specify a supported database.
Level: 1

Type: ERROR

Impact: Upgrade

54 WC-05319 to WC-05370

WC-05319: Failed to retrieve security parent portal for the child portal {0}

Cause: Failure in retrieving security parent

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05319: Failed to retrieve security parent portal for the child portal {0}

Cause: Failure in retrieveing security parent

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05320: Failed to copy security data for portal {0}

Cause: Copy of security data from the security parent failed

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05320: Failed to copy security data for portal {0}

Cause: Copy of security data from the security parent failed

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05321: Failed to delete portal {0} and all its children

Cause: Deletion of portal along with children failed

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05321: Failed to delete portal {0} and all its children

Cause: Deletion of portal along with children failed

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05322: Failed to retrieve parent portal for the child portal {0}

Cause: Failure in retrieving parent portal

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05322: Failed to retrieve parent portal for the child portal {0}

Cause: Failure in retrieving parent portal

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05323: Failed to retrieve child portals for portal {0}

Cause: Failure in retrieving child portals

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05323: Failed to retrieve child portals for portal {0}

Cause: Failure in retrieving child portals

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05324: Failed to set inheritance from parent for portal {0}

Cause: Failure in setting the inheritance flag for child portals

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05324: Failed to set inheritance from parent for portal {0}

Cause: Failure in setting the inheritance flag for child portals

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05370: Failed to retrieve root portal for portal {0}

Cause: Failure in retrieving root portal

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05370: Failed to retrieve root portal for portal {0}

Cause: Failure in retrieving root portal

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

55 WCC-ADF-10000 to WCC-ADF-30002

WCC-ADF-10000: An internal error occurred.

Cause: An internal error occurred.

Action: Report the error details to Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCC-ADF-10001: File not found: {0}

Cause: There was no file at the specified path.

Action: Correct the path or create the missing file.
Level: 1

Type: ERROR

Impact: Files

WCC-ADF-10002: Invalid file name: {0}

Cause: The file name is invalid.

Action: Check the file name, it may contain reserved characters.
Level: 1

Type: ERROR

Impact: Files

WCC-ADF-10003: Error executing the 'toString' method: {0}

Cause: The method 'toString' threw an exception.

Action: Review the error reported in the chained exception.
Level: 1

Type: WARNING

Impact: Other

WCC-ADF-10004: The type '{0}' could not be converted to '{1}'.

Cause: The conversion between two types failed.

Action: Ensure the type conversion is valid.
Level: 1

Type: ERROR

Impact: Programmatic

WCC-ADF-10005: Item not found: {0}

Cause: An item with the specified primary key could not be found.

Action: Verify that the primary key matches that of an existing item.
Level: 1

Type: ERROR

Impact: Programmatic

WCC-ADF-10006: Initialize user data cache: {0} entries, {1} milliseconds

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

WCC-ADF-10007: Invalid value for Java system property {0}: {1}

Cause: The Java system property had an invalid value.

Action: Review and correct the value
Level: 1

Type: WARNING

Impact: Configuration

WCC-ADF-10008: Unable to connect profiler: {0}

Cause: The profiler could not connect to the specified hostname and port.

Action: Ensure a profiler client is running on that hostname and port
Level: 1

Type: WARNING

Impact: Logging

WCC-ADF-10009: Profiler connected: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

WCC-ADF-10010: Profiler disconnected

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

WCC-ADF-10200: Localization key '{0}' was not found in '{1}'.

Cause: An internal warning occurred.

Action: Report the warning to Oracle Support Services
Level: 1

Type: WARNING

Impact: Logging

WCC-ADF-10201: Message key was not found. Parameters: {0} {1} {2} {3} {4} {5}

Cause: An internal warning occurred.

Action: Report the warning to Oracle Support Services
Level: 1

Type: WARNING

Impact: Logging

WCC-ADF-10202: Log message requires localization due to the log level: {0}

Cause: An internal warning occurred.

Action: Report the warning to Oracle Support Services
Level: 1

Type: WARNING

Impact: Logging

WCC-ADF-10203: Error initializing localization preferences for mode: {0}

Cause: Localization preferences for the given mode could not be initialized.

Action: Review the error reported in the chained exception.
Level: 1

Type: ERROR

Impact: Other

WCC-ADF-10400: The cause of the exception cannot be set.

Cause: The exception already contains a cause. It could not be updated to this cause.

Action: The cause is logged. No action required.
Level: 1

Type: WARNING

Impact: Other

WCC-ADF-10401: Server error cannot be mapped: '{0}' '{1}'

Cause: This error is not handled by the UI client.

Action: Report the details of the issue to Oracle Support Services.
Level: 1

Type: WARNING

Impact: Programmatic

WCC-ADF-10600: The XML document could not be parsed.

Cause: The XML document is not valid and/or well formed.

Action: Review and correct the XML document.
Level: 1

Type: ERROR

Impact: Files

WCC-ADF-10601: Node '{0}' has more than one child element named '{1}'.

Cause: The XML document was not valid.

Action: Review and correct the XML document.
Level: 1

Type: ERROR

Impact: Files

WCC-ADF-10602: Node '{0}' has more than one text child.

Cause: The XML document was not valid.

Action: Review and correct the XML document.
Level: 1

Type: ERROR

Impact: Files

WCC-ADF-10700: Application configuration from wcc-adf-config in adf-config.xml or MDS override: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

WCC-ADF-10701: Temporary directory does not exist: {0}

Cause: The specified temporary directory did not exist.

Action: Specify a valid and readable/writable temporary directory in the configuration.
Level: 1

Type: ERROR

Impact: Configuration

WCC-ADF-10702: The application configuration property '{0}' has an invalid value: '{1}'

Cause: The application configuration property has an invalid value.

Action: Consult the documentation and specify a valid value.
Level: 1

Type: ERROR

Impact: Configuration

WCC-ADF-10703: It is strongly recommended to set the \'applicationUrl\' configuration property in the form \'https://host[:port]\'

Cause: Oracle strongly recommends setting the 'applicationUrl' property to a secure (https) URL.

Action: Specify a secure (https) URL value.
Level: 1

Type: WARNING

Impact: Configuration

WCC-ADF-10801: Invalid WccInstance name: {0}

Cause: A WccInstance with the specified name could not be found.

Action: Review and correct the WccInstance name.
Level: 1

Type: ERROR

Impact: Configuration

WCC-ADF-10802: Invalid configuration parameter for WccInstance '{0}'. Parameter: {1}={2}

Cause: A WccInstance configuration parameter was not correct.

Action: Review and correct the WccInstance configuration parameter.
Level: 1

Type: ERROR

Impact: Configuration

WCC-ADF-10900: Required feature is not enabled on the WebCenter Content Server instance '{0}'. Feature: '{1}', Minimum level: {2}

Cause: A required feature was not enabled on the WebCenter Content Server instance, or the feature level did not meet the minimum requirement.

Action: Enable the required feature on the WebCenter Content Server instance and ensure the feature is at the minimum required level.
Level: 1

Type: ERROR

Impact: Configuration

WCC-ADF-10901: If the workflow feature is to be used, it is recommended to enable the feature 'WfDbInQueue' by setting the 'config.cfg' option 'UseDatabaseWfInQueue=1' on the WebCenter Content Server instance '{0}'.

Cause: A recommended feature on the WebCenter Content Server should be enabled if the workflow feature is to be used..

Action: Enable the required feature on the WebCenter Content Server instance if the workflow feature is to be used.
Level: 1

Type: WARNING

Impact: Configuration

WCC-ADF-10902: Required Content Server feature has been enabled. The content server must be restarted before the configuration changes will take place.

Cause: After enabling the required content server feature, the content server must be restarted.

Action: The content server must be restarted before the configuration changes will take place.
Level: 1

Type: ERROR

Impact: Configuration

WCC-ADF-11000: Connection '{0}' could not be created for instance '{1}'.

Cause: An error occurred while attempting to create the connection.

Action: Review the connection configuration and the error reported in the chained exception.
Level: 1

Type: ERROR

Impact: Requests/Responses

WCC-ADF-11001: IdcContext could not be created for user '{0}', connection '{1}', instance '{2}'.

Cause: An error occurred while attempting to create the user IdcContext.

Action: Review the connection configuration and the error reported in the chained exception.
Level: 1

Type: ERROR

Impact: Requests/Responses

WCC-ADF-11002: Connection created: instance '{0}', connection '{1}', server URL '{2}', admin user '{3}'

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

WCC-ADF-11003: RIDC Client Library Version: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

WCC-ADF-11004: Credential could not be fetched.

Cause: An error occurred while fetching the credentials.

Action: Review the credential access permission and the error reported in the chained exception.
Level: 1

Type: ERROR

Impact: Configuration

WCC-ADF-11005: Credential user '{0}' fetched successfully from connection architecture layer.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

WCC-ADF-11006: Connection architecture mbean could not be found.

Cause: An error occurred while getting the credential username from connection architecture mbean.

Action: Review the error reported in the chained exception.
Level: 1

Type: ERROR

Impact: Configuration

WCC-ADF-11400: Error executing WebCenter Content service '{0}'.

Cause: An error occurred while executing a WebCenter Content service.

Action: Review the error reported in the chained exception.
Level: 1

Type: ERROR

Impact: Requests/Responses

WCC-ADF-11401: Error executing WebCenter Content service '{0}': {1} (status code: {2}, message key: {3})

Cause: An error occurred while executing a WebCenter Content service.

Action: Review the error message.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-11402: '{0}' could not be converted to RIDC string.

Cause: An internal error occurred.

Action: Report the details of this error Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCC-ADF-11403: RIDC string '{0}' could not be converted to type '{1}'.

Cause: An internal error occurred.

Action: Report the details of this error Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCC-ADF-11404: Unsupported data type: {0}

Cause: An attribute definition specified an unsupported data type.

Action: Review and correct the attribute definition.
Level: 1

Type: ERROR

Impact: Programmatic

WCC-ADF-11420: The Content Server request has timed out, but the operation should continue to run on the server.

Cause: The Content Server request didn't return a response before the RIDC socket read timeout expired.

Action: The Content Server request was not aborted, and the operation may continue to run after the timeout. No action required.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-11600: Operation cannot target more than one WccInstance.

Cause: The requested operation targeted two or more WccInstances.

Action: Target a single WccInstance with the operation.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

WCC-ADF-11800: File system operation failed on file or directory: {0}

Cause: A file system operation failed on the specified file or directory.

Action: Check the underlying error and file system permissions by the process attempting the operation.
Level: 1

Type: ERROR

Impact: Files

WCC-ADF-11801: File or directory cannot be deleted: {0}

Cause: The specified file or directory could not be deleted.

Action: Check file system permissions for the process attempting to perform the delete.
Level: 1

Type: WARNING

Impact: Files

WCC-ADF-11802: File or directory cannot be created: {0}

Cause: The specified file or directory could not be created.

Action: Check file system permissions for the process attempting to perform the delete.
Level: 1

Type: ERROR

Impact: Files

WCC-ADF-11803: The file cannot be moved from '{0}' to '{1}'.

Cause: The specified file could not be moved.

Action: Check file system permissions for the process attempting to perform the operation.
Level: 1

Type: ERROR

Impact: Files

WCC-ADF-11804: The uploaded file cannot be larger than {0}.

Cause: The uploaded file was larger than the maximum allowed.

Action: Reduce the file size and try the upload again.
Level: 32

Type: NOTIFICATION

Impact: Files

WCC-ADF-11805: The following HTTP error occured while transfering file content: {0}

Cause: An HTTP error occured while transfering file content.

Action: Examine the HTTP error code, message, and the server state and logs.
Level: 1

Type: ERROR

Impact: Requests/Responses

WCC-ADF-11806: The uploaded file cannot be empty.

Cause: The uploaded file was empty.

Action: Upload a non-zero length file.
Level: 32

Type: NOTIFICATION

Impact: Files

WCC-ADF-11807: The content of one or more documents was not available, possibly due to a system error or because your session was idle for too long.

Cause: The uploaded file token was not found.

Action: Re-try the upload.
Level: 32

Type: NOTIFICATION

Impact: Files

WCC-ADF-11808: The temporary directory structure '{0}' has been tampered with. Ensure the application configuration property 'temporaryDirectory' points to a secure filesystem.

Cause: The temporary directory structure has been tampered with.

Action: Ensure the application configuration property 'temporaryDirectory' points to a secure filesystem.
Level: 1

Type: ERROR

Impact: Files

WCC-ADF-12416: An item with the specified identifier does not exist, or cannot be accessed due to insufficient privileges.

Cause: The specified item did not exist or could not be accessed.

Action: Specify an existing item you have access to.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12417: An item with the specified name already exists.

Cause: The specified item name matched an existing name.

Action: Specify an item name that does not already exist.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12418: You do not have sufficient privileges to access an item or perform the operation.

Cause: The user had insufficient privileges to perform the operation.

Action: Perform the operation as a user with sufficient privileges.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12419: The folder is not empty.

Cause: The operation was not performed on an empty folder as expected.

Action: Perform the operation on an empty folder.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12420: You must be authenticated and have sufficient privileges to perform the operation.

Cause: The user attempting the operation had insufficient privileges, or was unauthenticated.

Action: Perform the operation as an authenticated user with sufficient privileges.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12421: The name must not contain any reserved characters such as : / \ * " < > | ?

Cause: The name contained one or more illegal characters.

Action: Choose a name that does not include any illegal characters.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12422: The name must not start or end with whitespace.

Cause: The specified name started and/or ended with whitespace.

Action: Choose a name that does not start or end with whitespace.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12423: The name is {0} characters too long.

Cause: The specified name was too long.

Action: Choose a shorter name.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12424: The name is reserved by the system.

Cause: The specified name matched a reserved system name.

Action: Choose a different name.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12425: The name must not contain consecutive spaces.

Cause: The name contains consecutive spaces.

Action: Choose a name that does not contain consecutive spaces.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12430: You do not have permission to perform this operation with the specified metadata.

Cause: The user did not have permission to perform the operation with the specified metadata.

Action: Modify the metadata or perform the operation as a user with sufficient privileges.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12431: A document with the specified Document ID already exists.

Cause: The specified Document ID matched the Document ID of a document that already exists.

Action: For new documents, choose a Document ID that does not already exist.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12432: The expiration date cannot be before the release date.

Cause: The expiration date cannot be before the release date.

Action: Choose an expiration date after the release date.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12433: You would not have Write access to the Access Control List.

Cause: The user would not have Write access to the Access Control List.

Action: Grant Write access to the Access Control List.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12434: You would not have Admin access to the Access Control List.

Cause: The user would not have Admin access to the Access Control List.

Action: Grant Admin access to the Access Control List.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12435: There was an error executing the search, possibly because the search expression was invalid.

Cause: The search query cannot be executed as specified.

Action: Check the search term syntax and try again.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12436: The value entered for '{0}' exceeds {1} characters, the maximum length allowed for this field.

Cause: The value entered for the field is too long.

Action: Enter a value up to the maximum allowed length.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12437: You do not have Write access to folder '{0}'.

Cause: The user does not have write access to the folder.

Action: Select a folder that has write access.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12438: A null value cannot be propagated for field '{0}'.

Cause: The value entered for the field may not be null.

Action: Enter a non-null value.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12439: Item '{0}' cannot be revised because the source and destination have different types.

Cause: The source and destination items have different types.

Action: Manually resolve the conflict by deleting or renaming the destination item.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12440: You do not have sufficient privileges to access the content account '{1}'.

Cause: The user does not have sufficient privileges to access the specified account.

Action: Select an account that gives the user sufficient privileges.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12441: The document is not in workflow.

Cause: The user is trying to approve or reject a document that is not in workflow.

Action: Refresh the document information.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12442: You are not a reviewer for workflow step '{0}'.

Cause: The user is not a reviewer for the current workflow step.

Action: Refresh the document information.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12443: The document is not in a workflow review step.

Cause: The document is not in a workflow review step.

Action: Refresh the document information.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12444: You are not a contributor for workflow step '{0}'.

Cause: The user is not a contributor for the current workflow step.

Action: Refresh the document information.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12470: You selected a revision that is not the latest revision of the document.

Cause: The user selected a revision other than the latest revision of the document.

Action: Refresh the document information, select the latest revision and retry the operation.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12471: You selected a document that is not checked out or a revision that is not the latest revision of the document.

Cause: The user selected a revision other than the latest revision of the document or the document is not checked out.

Action: Refresh the document information, select the latest revision and retry the operation.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12472: You may not move content between the two library or folder types.

Cause: The user is attempting to move content between two types of libraries or folders that do not allow the operation.

Action: Select a destination compatible with the source and re-try the move operation.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12473: You may not move or copy a document pending initial workflow contribution.

Cause: The user is attempting to move or copy a document pending initial workflow contribution.

Action: Try the operation again after the document is out of the initial workflow contribution.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12474: You entered the invalid value '{0}' for the Revision field.

Cause: The value entered for the Revision field is not valid.

Action: Enter a valid value.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12475: The document is checked out by another user.

Cause: The user is attempting to check out or check in a document that is checked out by another user.

Action: Try the operation again after the document is no longer checked out by another user.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12476: The folder '{0}' could not be renamed.

Cause: An error occurred while renaming a folder.

Action: Some system folders cannot be renamed.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12480: You may not copy or move a folder into itself or its descendant.

Cause: Copying or moving a folder into itself or its descendant is prohibited.

Action: Select a destination for copy or move that is neither the source folder nor its descendant.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12490: A value is required for field '{0}'.

Cause: The required field does not have a value.

Action: Enter a value for the required field. If the required field is hidden, make sure it has a default valued defined in Content Server.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12495: The item cannot be accessed because it was moved to Trash.

Cause: An attempt was made to access a Trash item from outside the context of the Trash listing.

Action: Refresh the page where the item was displayed, and verify that the item is no longer displayed after the page has reloaded.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12800: The cloud folder could not be found within the Oracle Documents Cloud Service. The folder may be missing, or the cloud service may be unavailable.

Cause: Its linked folder in Oracle Documents Cloud Service no longer exists or is not accessible.

Action: Verify its counterpart in Oracle Documents Cloud Service still exists and is accessible.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12801: The action failed in Oracle Documents Cloud Service.

Cause: The action could not be performed in Oracle Documents Cloud Service.

Action: Content Server doesn't provide much details on this error. Report the error to Oracle Support Services.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12802: The cloud folder cannot be shared with your Oracle Documents account.

Cause: You don't have a personal account for Oracle Documents Cloud Service, or the e-mail address in your WebCenter Content preferences doesn't correspond with your Oracle Documents account.

Action: Make sure you have a personal account in Oracle Documents Cloud Service, and that your WebCenter Content e-mail address setting corresponds with that account.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12803: This file type is not supported by Oracle Documents Cloud Service.

Cause: This file type is not allowed to be stored in the Oracle Documents repository.

Action: Don't attempt to copy files of this type to Oracle Documents Cloud Service.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12804: This cloud folder has already been shared with your Oracle Documents account.

Cause: If a cloud folder is currently shared with a particular account, it cannot be shared with that same account again.

Action: Don't attempt to share this cloud folder with your Oracle Documents account again unless the existing share has been removed.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-12805: You're already the owner of this cloud folder. Sharing it with your own Oracle Documents account is not a valid operation.

Cause: The owner of a cloud folder can't share that folder with their own account.

Action: Don't attempt to share this cloud folder with your Oracle Documents account.
Level: 32

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-14001: The number of accounts assigned to you exceeds the maximum number of accounts allowed by this query, so the listing may not include all the items you have access to. Note that you can still perform operations (such as uploading content or creating folders) for all your accounts, even though the results of those operations may not be visible in the listing if the account is among those truncated from the query.

Cause: The number of accounts assigned exceeds the maximum allowed by the query.

Action: Report the issue to your system administrator.
Level: 24

Type: NOTIFICATION

Impact: Requests/Responses

WCC-ADF-20200: The type '{1}' was unexpected for field '{0}' (treating as STRING).

Cause: A field had an unexpected data type.

Action: Report the details of this warning Oracle Support Services.
Level: 1

Type: WARNING

Impact: Data

WCC-ADF-30000: The Faces Servlet filter '{0}' is not configured correctly.

Cause: The Faces Servlet filter was not configured correctly.

Action: Check the documentation for the proper filter configuration.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

WCC-ADF-30001: Cannot find UI component '{0}'.

Cause:

Action:
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCC-ADF-30002: WCCADF mbean could not be registered.

Cause: An error occurred while registering the WCCADF mbean.

Action: Review the error reported in the chained exception.
Level: 1

Type: ERROR

Impact: Configuration

56 WCS-03051 to WCS-90200

WCS-03051: No event is selected.

Cause: There was invalid or missing information in the connection.xml or adf-config.xml file.

Action: Verify that the connections.xml and adf-config.xml file contains a valid entry with the correct connection information.
Level: 1

Type: WARNING

Impact: Other

WCS-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-03052: event date validation error

Cause: An invalid date or time was selected for the event.

Action: Verify the date and time.
Level: 1

Type: ERROR

Impact: Other

WCS-03053: No upcoming events were found.

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the adapter was not defined.

Action: Verify that the connections.xml file contains a valid connection for the Portal Events service, and the Portal Events server is running
Level: 1

Type: WARNING

Impact: Other

WCS-03053: No upcoming events were found.

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the adapter was not defined.

Action: Verify that the connections.xml file contains a valid connection for the Portal Events service, and the Portal Events server is running
Level: 1

Type: WARNING

Impact: Other

WCS-03101: The Events service is not able to acquire an adapter from the server.

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the adapter was not defined.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the specified adapter is defined.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-03114: failure to send personal event

Cause: Either the connections.xml file did not contain a valid connection for the Mail service, or the Mail server was down.

Action: Verify that the connections.xml file contains a valid connection for the Mail service, and the Mail server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03115: failure to log in to the Exchange server

Cause: The credential for the Personal Events service was not configured properly or the Exchange server was not running.

Action: Verify that the credential for the Personal Events service is correct, and the Exchange server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03116: failure to log in to the Exchange server

Cause: The credential for the Personal Events service credential was not configured properly.

Action: Verify that the credential for the Personal Events service is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-03117: Failed to login to the exchange server.

Cause: The credential for the Personal Events service is not configured properly or the exchange server is not running.

Action: Verify that the credential for the Personal Events service is correct, and the exchange server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03117: Failed to login to the exchange server.

Cause: The credential for the Personal Events service is not configured properly or the exchange server is not running.

Action: Verify that the credential for the Personal Events service is correct, and the exchange server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03118: Failed to login to the exchange server.

Cause: The credential for the Personal Events service credential is not configured properly.

Action: Verify that the credential for the Personal Events service is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-03118: Failed to login to the exchange server.

Cause: The credential for the Personal Events service credential is not configured properly.

Action: Verify that the credential for the Personal Events service is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-03201: The Events service is not able to acquire an adapter for an Events server.

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service.
Level: 1

Type: ERROR

Impact: Other

WCS-03201: The Events service is not able to acquire an adapter for an Events server.

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service.
Level: 1

Type: ERROR

Impact: Other

WCS-03202: The Events service is unavailable.

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03202: The Events service is unavailable.

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03203: Data query in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03203: Data query in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03204: Create event in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03204: Create event in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03205: Update event in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03205: Update event in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03206: Delete event in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03206: Delete event in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03207: Send event mail in Events service failed

Cause: Either the connections.xml file did not contain a valid connection for the Mail service, or the Mail server was down.

Action: Verify that the connections.xml file contains a valid connection for the Mail service, and Mail server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-03209: Cannot create the category

Cause: The category could not be created because a category of the same name already exists.

Action: Select the existing category.
Level: 1

Type: ERROR

Impact: Other

WCS-03210: cannot add the portal event to the personal calendar

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03210: cannot add the portal event to the personal calendar

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03211: cannot add the portal event to the personal calendar

Cause: The Personal Events service was not configured properly in connections.xml or the Personal Events service is down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03211: cannot add the portal event to the personal calendar

Cause: The Personal Events service was not configured properly in connections.xml or the Personal Events service is down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03212: cannot add the portal event to the personal calendar

Cause: The credential for the Personal Events service was not configured properly.

Action: Verify that the credential for the Personal Events service is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-03212: cannot add the portal event to the personal calendar

Cause: The credential for the Personal Events service was not configured properly.

Action: Verify that the credential for the Personal Events service is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-03213: Failure to create category

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03213: Failure to create category

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03214: failure to retrieve categories

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03214: failure to retrieve categories

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03215: failure to retrieve portal event list

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03215: failure to retrieve portal event list

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03216: failure to retrieve portal event detail

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03216: failure to retrieve portal event detail

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03217: failure to check the relationship for the event

Cause: Either the connections.xml file did not contain a valid connection entry for the Relationship service,or the Relationship service was down.

Action: Verify that the connections.xml file contains a valid entry for the Relationship service, the Relationship service is running.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-03226: You do not have permission to manage the event or your permission to manage the event is revoked. Refresh the Events task flow to see the changes if necessary.

Cause: You do not have permission to manage this event or your permission to manage this event is revoked.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03227: Event not found.

Cause: The event doesn't exist or was deleted.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03227: Event not found.

Cause: The event doesn't exist or was deleted.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03228: The Events service is currently disabled, preventing you from performing this operation. Contact your administrator.

Cause: The Events service is currently disabled.

Action: Contact your administrator. Enable the Events service.
Level: 1

Type: WARNING

Impact: Other

WCS-03228: The Events service is currently disabled, preventing you from performing this operation. Contact your administrator.

Cause: The Events service is currently disabled.

Action: Contact your administrator. Enable the Events service.
Level: 1

Type: WARNING

Impact: Other

WCS-03301: The Web Conference service is unavailable.

Cause: Either the connections.xml file did not contain a valid connection entry, or the adapter was not defined in the adf-config.xml file.

Action: Verify that the connections.xml file contains a valid connection entry, and the specified adapter is defined in the adf-config.xml file.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-03310: The Conference service is not properly configured.

Cause: The ambiguous connections of Conference service were found in connections.xml.

Action: Verify that the connections.xml file contains a valid entry for the Conference service.
Level: 1

Type: ERROR

Impact: Other

WCS-03701: WebCenter Tasks service unable to acquire a data connection.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03702: Tasks query failed in WebCenter Task service.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03703: Create task failed in WebCenter Task service.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03704: Task update failed in WebCenter Tasks service.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03705: Task purge failed in WebCenter Tasks service.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03706: Task delete failed in WebCenter Tasks service.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03707: The adf-config.xml element associated with the BPEL connection to be used by the To-Dos and Group Tasks service was not present.

Cause: "The application\'s adf-config.xml file was missing the adf-task-config element containing a BPELConnection name.

Action: Add the adf-config.xml entry associated with the To-Dos and Group Tasks service\'s BPEL connection using the appropriate configuration manipulation.
Level: 1

Type: ERROR

Impact: Other

WCS-04001: unable to resolve the name {0}

Cause: The object with the given name could not be found.

Action: Check the JNDI configuration or the context passed.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-04010: failure to create, update, or fetch the service configuration file {0}, due to: {1}

Cause: One of the following was the cause: There was a concurrent modification by another user; there was an MDS I/O exception; the metadata was not found; a validation error occurred; or the update was not supported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-04011: unable to find the service configuration file {0}, due to: {1}

Cause: The service was not provisioned for this portal.

Action: Provision this service or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04011: unable to find the service configuration file {0}, due to: {1}

Cause: The service was not provisioned for this portal.

Action: Provision this service or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04012: unable to find the credentials for user {0}

Cause: The credentials were either not supplied, or were invalid.

Action: Supply credentials using the External Application configured for the service.
Level: 1

Type: WARNING

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-04021: Not an instance of {1} : {0}

Cause: Supplied class is not an instance of SessionManager class.

Action: Check the service configuration property "session.manager.class".
Level: 1

Type: ERROR

Impact: Other

WCS-04022: The service is unavailable.

Cause: Cannot establish connection to the server, either the server is down or the connect details are wrong.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04022: The service is unavailable.

Cause: Cannot establish connection to the server, either the server is down or the connect details are wrong.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04023: Cache not available.

Cause: Cache is not initialized.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-04025: Session not initialized {0}.

Cause: Either initialize method on the session is not invoked or initialization has failed.

Action: Check logs for more details or Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04026: session instance acquired is null from SessionFactory: {0}

Cause: SessionFactory returned null session instance. Wrong factory implementation.

Action: Check the SessionFactory implementation for more details or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04026: session instance acquired is null from SessionFactory: {0}

Cause: SessionFactory returned null session instance. Wrong factory implementation.

Action: Check the SessionFactory implementation for more details or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04027: Session Factory class not defined.

Cause: Either the service-config for the session is missing or "session.factory.class" property is missing.

Action: Check the service-config.xml for the given session type exists and "session.factory.class" property is defined with a qualified class name that is available in the classpath. Contact system administrator for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-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-04030: System user session is requested from session {0}, but administrator user name is not defined in the connection nor in adf-config.

Cause: Missing "admin.user" property from connection and/or adf-config.xml.

Action: Ensure that either the connection or ADF service-config contains a property called "admin.user" with a valid administrator user.
Level: 1

Type: WARNING

Impact: Other

WCS-04031: Unexpected error occurred, due to : {0}

Cause: An unexpected server exception occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04031: Unexpected error occurred, due to : {0}

Cause: An unexpected server exception occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04032: Could not get access to cache object.

Cause: API should be invoked only for getting access to the root cache.

Action: Try using correct API.
Level: 1

Type: WARNING

Impact: Other

WCS-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-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-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-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-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-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-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-04040: CacheFactory not specified.

Cause: CacheFactory instance is not found.

Action: Set appropriate CacheFactory instance on the Cache class.
Level: 1

Type: ERROR

Impact: Other

WCS-04041: No default or active connection available for: {0}

Cause: There is no default or active connection defined for this connection type.

Action: At least one connection must be defined default or active for this connection type.
Level: 1

Type: WARNING

Impact: Other

WCS-04041: No default or active connection available for: {0}

Cause: There is no default or active connection defined for this connection type.

Action: At least one connection must be defined default or active for this connection type.
Level: 1

Type: WARNING

Impact: Other

WCS-04042: Enterprise role not found: {0}.

Cause: Unable to find the enterprise role with the supplied name in the backend server.

Action: Check group with the given identity exists in the backend server.
Level: 1

Type: WARNING

Impact: Other

WCS-04042: Enterprise role not found: {0}.

Cause: Unable to find the enterprise role with the supplied name in the backend server.

Action: Check group with the given identity exists in the backend server.
Level: 1

Type: WARNING

Impact: Other

WCS-04043: Service is disabled for the current Portal: {0}.

Cause: Service is disabled for the current Portal.

Action: Enable this service or contact the Portal Moderator.
Level: 1

Type: WARNING

Impact: Other

WCS-04043: Service is disabled for the current Portal: {0}.

Cause: Service is disabled for the current Portal.

Action: Enable this service or contact the Portal Moderator.
Level: 1

Type: WARNING

Impact: Other

WCS-04201: Error loading relationship service implementation

Cause: The relationship service encountered a problem while loading a relationship service implementation.

Action: Check the stack trace for more information
Level: 1

Type: ERROR

Impact: Other

WCS-04201: Error loading relationship service implementation

Cause: The relationship service encountered a problem while loading a relationship service implementation.

Action: Check the stack trace for more information
Level: 1

Type: ERROR

Impact: Other

WCS-04206: Error checking create permission

Cause: There was an error loading the relationship security provider.

Action: Check to make sure that the relationship security provider is properly configured.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-04415: Service {0} returned null for target view object with objectId: {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04417: Could not find {0} parameter for the Links Detail taskflow.

Cause: The parameter is required for processing links-detail task flow.

Action: Make sure the parameter is bound to a non-null value.
Level: 1

Type: ERROR

Impact: Other

WCS-04417: Could not find {0} parameter for the Links Detail taskflow.

Cause: The parameter is required for processing links-detail task flow.

Action: Make sure the parameter is bound to a non-null value.
Level: 1

Type: ERROR

Impact: Other

WCS-04418: User principal is null.

Cause: The user principal returned by the security context was null.

Action: Make sure security is property configured for the application.
Level: 1

Type: WARNING

Impact: Other

WCS-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-04419: Links components cannot render

Cause: The links-detail-popup task flow panelWindow was not found.

Action: Make sure the view includes the links-detail-popup task flow.
Level: 1

Type: WARNING

Impact: Other

WCS-04420: The image file {0} you tried to select was invalid. Provide a valid image file.

Cause: Unable to embed the image as the file is null or invalid.

Action: Select a valid image file
Level: 1

Type: ERROR

Impact: Other

WCS-04420: The image file {0} you tried to select was invalid. Provide a valid image file.

Cause: Unable to embed the image as the file is null or invalid.

Action: Select a valid image file
Level: 1

Type: ERROR

Impact: Other

WCS-04421: The taskflow id {0} was invalid. Provide a valid taskflow id.

Cause: Unable to retrieve the taskflow as the id is null or invalid.

Action: Specify a valid taskflow Id.
Level: 1

Type: ERROR

Impact: Other

WCS-04421: The taskflow id {0} was invalid. Provide a valid taskflow id.

Cause: Unable to retrieve the taskflow as the id is null or invalid.

Action: Specify a valid taskflow Id.
Level: 1

Type: ERROR

Impact: Other

WCS-04422: The NewRelatedObject returned from the service {0} was invalid.

Cause: Unable to process the returned object.

Action: Return a valid object for linking.
Level: 1

Type: ERROR

Impact: Other

WCS-04422: The NewRelatedObject returned from the service {0} was invalid.

Cause: Unable to process the returned object.

Action: Return a valid object for linking.
Level: 1

Type: ERROR

Impact: Other

WCS-04601: unexpected error

Cause: An unexpected error occurred for the RTC service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-04625: Failed to instantiate IMPSession for the logged-in user.

Cause: The adapter class could not be instantiated.

Action: Ensure that the property 'adapter-class' has been defined for the adapter in the adf-config.xml and is valid.
Level: 1

Type: WARNING

Impact: Other

WCS-04701: Unable to load LCS adapter: base connection URL is missing.

Cause: The property 'base.connection.url' was missing.

Action: Ensure that the LCS connection entry contains the 'base.connection.url' property and points to a valid URL.
Level: 1

Type: ERROR

Impact: Other

WCS-04702: Unable to load LCS adapter: LCS PoolName is missing.

Cause: The property 'LCSPoolName' was missing.

Action: Ensure that the LCS connection entry in connections.xml contains the 'LCSPoolName' property and contains a valid LCS pool name.
Level: 1

Type: WARNING

Impact: Other

WCS-04703: Unable to perform operation {0}

Cause: Failed to perform the operation on remote Web service.

Action: Ensure that the RTC configuration is correct, the remote system is available, and the errors generated in the remote system's logs have been fixed.
Level: 1

Type: ERROR

Impact: Other

WCS-04704: Failed to log on user {0}.

Cause: User login failed.

Action: Check user credentials and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-04705: Exception caught while fetching buddy list for user {0}

Cause: Failed to retrieve buddy list from the Remote Service.

Action: Ensure that valid LCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04706: Exception caught while fetching presence information using user account {0}

Cause: Failed to fetch presence information from the remote service .

Action: Ensure that valid LCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04707: Failed to add user {0} to the logged in user''s buddy list (logged in user:{1})

Cause: Failed to update buddy list of the user.

Action: Ensure that the server is up and responding.
Level: 1

Type: WARNING

Impact: Other

WCS-04708: Failed to remove user {0} from the logged in user''s buddy list (logged in user:{1})

Cause: Failed to update buddy list of the user.

Action: Ensure that the server is up and responding.
Level: 1

Type: WARNING

Impact: Other

WCS-04709: Account field missing from user credentials

Cause: Can't login to server without the account information.

Action: Ensure that a valid sip address value is supplied as the Account in credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-04710: Connection not defined

Cause: Connection is not defined.

Action: Ensure that the connection is defined.
Level: 1

Type: WARNING

Impact: Other

WCS-04711: External application ID not defined.

Cause: The required configuration parameter External Application ID was not found.

Action: Contact your system Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04801: Invalid timeout value specified: {0} Defaulting to {1}

Cause: The presence cache timeout value was either null or not a valid number.

Action: Ensure that the 'rtc.cache.time' attribute is not null and contains a valid number.
Level: 1

Type: WARNING

Impact: Other

WCS-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-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-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-04806: Unable to acquire associated external application details.

Cause: The external application was not found for the external application ID.

Action: Ensure that external application ID refers to a valid external application.
Level: 1

Type: ERROR

Impact: Other

WCS-04851: Failed to generate endpoint to talk to OCS WebService.

Cause: The webservice is unreachable.

Action: Ensure that the OCS connection entry contains the 'base.connection.url' property and points to a valid URL.
Level: 1

Type: ERROR

Impact: Other

WCS-04851: Failed to generate endpoint to talk to OCS WebService.

Cause: The webservice is unreachable.

Action: Ensure that the OCS connection entry contains the 'base.connection.url' property and points to a valid URL.
Level: 1

Type: ERROR

Impact: Other

WCS-04852: Unable to perform operation {0}

Cause: Failed to perform the operation on remote Web service.

Action: Ensure that the RTC configuration is correct, the remote system is available, and the errors generated in the remote system's logs have been fixed.
Level: 1

Type: ERROR

Impact: Other

WCS-04852: Unable to perform operation {0}

Cause: Failed to perform the operation on remote Web service.

Action: Ensure that the RTC configuration is correct, the remote system is available, and the errors generated in the remote system's logs have been fixed.
Level: 1

Type: ERROR

Impact: Other

WCS-04853: Exception caught while fetching buddy list for user {0}

Cause: Failed to retrieve buddy list from the Remote Service.

Action: Ensure that valid OCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04853: Exception caught while fetching buddy list for user {0}

Cause: Failed to retrieve buddy list from the Remote Service.

Action: Ensure that valid OCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04854: Exception caught while fetching presence information using user account {0}

Cause: Failed to fetch presence information from the remote service.

Action: Ensure that valid OCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04854: Exception caught while fetching presence information using user account {0}

Cause: Failed to fetch presence information from the remote service.

Action: Ensure that valid OCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04855: Account field missing from user credentials

Cause: Cannot login to server without the account information.

Action: Ensure that a valid sip address value is supplied as the Account in credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-04855: Account field missing from user credentials

Cause: Cannot login to server without the account information.

Action: Ensure that a valid sip address value is supplied as the Account in credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-04856: Connection not defined

Cause: Connection is not defined.

Action: Ensure that the connection is defined.
Level: 1

Type: WARNING

Impact: Other

WCS-04856: Connection not defined

Cause: Connection is not defined.

Action: Ensure that the connection is defined.
Level: 1

Type: WARNING

Impact: Other

WCS-04857: External application ID not defined.

Cause: The required configuration parameter External Application ID was not found.

Action: Contact your system Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04857: External application ID not defined.

Cause: The required configuration parameter External Application ID was not found.

Action: Contact your system Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04876: Exception caught while fetching buddy list for user {0}

Cause: Failed to retrieve buddy list from the Remote Service.

Action: Ensure that valid OCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04877: Exception caught while fetching presence information using user account {0}

Cause: Failed to fetch presence information from the remote service .

Action: Ensure that valid OCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04878: Account field missing from user credentials

Cause: Can't login to server without the account information.

Action: Ensure that a valid sip address value is supplied as the Account in credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-04879: Failed to add users as buddies

Cause: Can't add users as buddies on beehive server.

Action: Ensure that valid admin details have been supplied in the connection.
Level: 1

Type: WARNING

Impact: Other

WCS-04901: Not initializing RtcAction {0} as it does not extend from RtcAction

Cause: Specified class does not extend from RtcAction.

Action: Ensure that the specified class is a proper subclass of RtcAction.
Level: 1

Type: WARNING

Impact: Other

WCS-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-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-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-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-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-04906: Cannot process call request : Incorrect call method supplied

Cause: User has supplied an incorrect call method.

Action: Ensure that correct call method is supplied. Refer to the documentation to find the supported call methods.
Level: 1

Type: WARNING

Impact: Other

WCS-04907: Cannot process call request : Call domain not specified in connection.

Cause: User has selected PSTN call method but has not supplied the call.domain property.

Action: Ensure that correct call.domain has been supplied in connection/adf-config.
Level: 1

Type: WARNING

Impact: Other

WCS-04907: Cannot process call request : Call domain not specified in connection.

Cause: User has selected PSTN call method but has not supplied the call.domain property.

Action: Ensure that correct call.domain has been supplied in connection/adf-config.
Level: 1

Type: WARNING

Impact: Other

WCS-04908: Cannot process call request : User name is missing or not provided.

Cause: User name is missing or it has not been provided.

Action: Ensure that correct user name is provided, contact administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-04908: Cannot process call request : User name is missing or not provided.

Cause: User name is missing or it has not been provided.

Action: Ensure that correct user name is provided, contact administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05001: Cannot retrieve the metadata for a portal

Cause: Unable to fetch the portal metadata due to an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05001: Cannot retrieve the metadata for a portal

Cause: Unable to fetch the portal metadata due to an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05002: An error occurred while trying to get the ScopeAPI implementation for the service {0}.

Cause: Service {0} does not support provisioning.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-05003: The service object passed to the wrapper is null.

Cause: A null service object was retrieved from the service registry.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05004: A portal template named {0} already exists.

Cause: Name specified for the portal template was not unique. A template with the same name already exists.

Action: Provide a unique name for the portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05004: A portal template named {0} already exists.

Cause: Name specified for the portal template was not unique. A template with the same name already exists.

Action: Provide a unique name for the portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05005: Cannot create portal template

Cause: No name was provided for the portal template.

Action: Provide a unique name for the portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05005: Cannot create portal template

Cause: No name was provided for the portal template.

Action: Provide a unique name for the portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05006: Unable to retrieve information about {0}.

Cause: No portal template was found with the name specified.

Action: Provide the name of an existing portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05006: Unable to retrieve information about {0}.

Cause: No portal template was found with the name specified.

Action: Provide the name of an existing portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05007: The reference to the portal template metadata {0} is invalid.

Cause: No portal template was found with the name specified.

Action: Provide the name of an existing portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05007: The reference to the portal template metadata {0} is invalid.

Cause: No portal template was found with the name specified.

Action: Provide the name of an existing portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05008: Unable to get mutable metadata for the portal template {0}

Cause: Some portion of the portal template metadata has already been modified.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05008: Unable to get mutable metadata for the portal template {0}

Cause: Some portion of the portal template metadata has already been modified.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05009: Metadata for the portal template {0} is invalid.

Cause: MDS reported a metadata validation error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05009: Metadata for the portal template {0} is invalid.

Cause: MDS reported a metadata validation error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05010: An error occurred reading or writing metadata of portal template {0}.

Cause: MDS reported an IO error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05010: An error occurred reading or writing metadata of portal template {0}.

Cause: MDS reported an IO error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05011: The commit operation failed due to a concurrent metadata change for portal template {0}.

Cause: MDS reported a concurrent metadata change error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05011: The commit operation failed due to a concurrent metadata change for portal template {0}.

Cause: MDS reported a concurrent metadata change error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05012: Couldn''t retrieve the portal members email ids for {0} due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05012: Couldn''t retrieve the portal members email ids for {0} due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05013: Unable to execute portal related operation on {0}

Cause: Either the metadata did not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has already been changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05013: Unable to execute portal related operation on {0}

Cause: Either the metadata did not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has already been changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05014: Unable to get metadata for portal {0}.

Cause: Either the metadata did not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has already been changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05014: Unable to get metadata for portal {0}.

Cause: Either the metadata did not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has already been changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05015: Cannot create metadata for portal {0}

Cause: Metadata for the specified portal already exists.

Action: Provide a different name.
Level: 1

Type: ERROR

Impact: Other

WCS-05015: Cannot create metadata for portal {0}

Cause: Metadata for the specified portal already exists.

Action: Provide a different name.
Level: 1

Type: ERROR

Impact: Other

WCS-05018: The reference to the metadata of portal {0} is invalid.

Cause: The metadata reference was invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05018: The reference to the metadata of portal {0} is invalid.

Cause: The metadata reference was invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05019: Unable to get mutable metadata for portal {0}

Cause: Some portion of the portal metadata has already been modified.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05019: Unable to get mutable metadata for portal {0}

Cause: Some portion of the portal metadata has already been modified.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05020: Metadata of portal {0} is invalid.

Cause: MDS reported a metadata validation error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05020: Metadata of portal {0} is invalid.

Cause: MDS reported a metadata validation error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05021: An error occurred reading or writing metadata of portal {0}.

Cause: MDS reported an IO error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05021: An error occurred reading or writing metadata of portal {0}.

Cause: MDS reported an IO error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05022: The commit operation failed due to a concurrent metadata change for portal {0}.

Cause: MDS reported a concurrent metadata change error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05022: The commit operation failed due to a concurrent metadata change for portal {0}.

Cause: MDS reported a concurrent metadata change error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05023: Cannot retrieve a list of members for the current portal.

Cause: An error occurred trying to access the specified portal.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05023: Cannot retrieve a list of members for the current portal.

Cause: An error occurred trying to access the specified portal.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05025: Could not create portal {0} from portal template {1}.

Cause: An internal error occurred.

Action: Contact Administrator.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05025: Could not create portal {0} from portal template {1}.

Cause: An internal error occurred.

Action: Contact Administrator.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05026: Could not create portal template {1} from portal {0}.

Cause: Either the specified portal template already exists or the name was invalid.

Action: Provide a valid,unique name for the portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05026: Could not create portal template {1} from portal {0}.

Cause: Either the specified portal template already exists or the name was invalid.

Action: Provide a valid,unique name for the portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05027: Unable to get preference metadata for portal {0}

Cause: Either the metadata does not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05027: Unable to get preference metadata for portal {0}

Cause: Either the metadata does not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05035: Unexpected error in renaming portal from {0} to {1}. Contact administrator or try again after some time.

Cause: An invalid character was found in the name.

Action: Remove the invalid character(s) from the name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05035: Unexpected error in renaming portal from {0} to {1}. Contact administrator or try again after some time.

Cause: An invalid character was found in the name.

Action: Remove the invalid character(s) from the name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05036: A portal with the URL {0} already exists.

Cause: A portal with the specified URL exists.

Action: Specify a unique name for the portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05036: A portal with the URL {0} already exists.

Cause: A portal with the specified URL exists.

Action: Specify a unique name for the portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05037: The portal template name contains an invalid character {0}.

Cause: An invalid character was found in the portal template name.

Action: Remove the invalid character(s) from the portal template name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05037: The portal template name contains an invalid character {0}.

Cause: An invalid character was found in the portal template name.

Action: Remove the invalid character(s) from the portal template name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05038: A portal template named {0} already exists.

Cause: A portal template with the specified name already exists.

Action: Specify a unique name for the portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05038: A portal template named {0} already exists.

Cause: A portal template with the specified name already exists.

Action: Specify a unique name for the portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05039: An error occurred attempting to save this portal as a portal template.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05039: An error occurred attempting to save this portal as a portal template.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05040: The portal name contains one or more blank space characters.

Cause: A blank was found in the portal name. Blank spaces are not allowed.

Action: Remove all blank spaces from the portal name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05040: The portal name contains one or more blank space characters.

Cause: A blank was found in the portal name. Blank spaces are not allowed.

Action: Remove all blank spaces from the portal name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05041: The portal template name contains one or more blank space characters.

Cause: A blank space was found in the name of the portal template. Blank spaces are not allowed.

Action: Remove all blank spaces from the portal template name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05041: The portal template name contains one or more blank space characters.

Cause: A blank space was found in the name of the portal template. Blank spaces are not allowed.

Action: Remove all blank spaces from the portal template name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05042: Unable to get metadata {1} for portal {0}.

Cause: Either the metadata did not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has already been changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05042: Unable to get metadata {1} for portal {0}.

Cause: Either the metadata did not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has already been changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05043: A portal with title {0} already exists. While the portal may not be available to you, another portal has that title. Choose a different title for your portal.

Cause: A portal with the specified display name exists.

Action: Specify a unique display name for the portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05043: A portal with display name {0} already exists. It may be used as a hidden portal by other users.

Cause: A portal with the specified display name exists.

Action: Specify a unique display name for the portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05047: Sending invitation to user(s) failed. The reason is : {0}.

Cause: Connection details for the BPEL server providing portal invitation services were not available.

Action: Ask your administrator to configure a connection to the BPEL server providing portal invitation services.
Level: 1

Type: ERROR

Impact: Other

WCS-05047: Sending invitation to user(s) failed. The reason is : {0}.

Cause: Connection details for the BPEL server providing portal invitation services were not available.

Action: Ask your administrator to configure a connection to the BPEL server providing portal invitation services.
Level: 1

Type: ERROR

Impact: Other

WCS-05048: Unexpected error occurred while trying to invite user(s) to portal {0}

Cause: The BPEL server that provides the portal invitation service might have been down.

Action: Ask your administrator to restart the BPEL server, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05048: Unexpected error occurred while trying to invite user(s) to portal {0}

Cause: The BPEL server that provides the portal invitation service might have been down.

Action: Ask your administrator to restart the BPEL server, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05058: Cannot create policy store metadata for portal {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05058: Cannot create policy store metadata for portal {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05059: Cannot save the changes

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05059: Cannot save the changes

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05063: Cannot delete portal {0} due to unknown errors.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05063: Cannot delete portal {0} due to unknown errors.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05065: Cannot not get the list of available services

Cause: No services were available in the service registry.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05065: Cannot not get the list of available services

Cause: No services were available in the service registry.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05066: An error occurred while attempting to unsubscribe a user from portal {0}.

Cause: The BPEL server supporting portal unsubscription may be down

Action: Ask your administrator to restart the BPEL server and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05066: An error occurred while attempting to unsubscribe a user from portal {0}.

Cause: The BPEL server supporting portal unsubscription may be down

Action: Ask your administrator to restart the BPEL server and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05067: Unable to send unsubscription request to Portal Manager(s). The reason is : {0}.

Cause: Connection details for the BPEL server providing portal unsubscription services were not available.

Action: Ask your administrator to configure a connection to the BPEL server providing portal unsubscription services.
Level: 1

Type: ERROR

Impact: Other

WCS-05067: Unable to send unsubscription request to moderator(s). The reason is : {0}.

Cause: Connection details for the BPEL server providing portal unsubscription services were not available.

Action: Ask your administrator to configure a connection to the BPEL server providing portal unsubscription services.
Level: 1

Type: ERROR

Impact: Other

WCS-05068: An error occurred attempting to unsubscribe user from portal {0}: {1}.

Cause: Connection details for the BPEL server providing portal unsubscription services were not available.

Action: Ask your administrator to configure a connection to the BPEL server providing portal unsubscription services.
Level: 1

Type: ERROR

Impact: Other

WCS-05068: An error occurred attempting to unsubscribe user from portal {0}: {1}.

Cause: Connection details for the BPEL server providing portal unsubscription services were not available.

Action: Ask your administrator to configure a connection to the BPEL server providing portal unsubscription services.
Level: 1

Type: ERROR

Impact: Other

WCS-05069: Unable to send subscription notification to Portal Manager(s). The reason is : {0}.

Cause: The BPEL URL has not been configured yet.

Action: Notify your administrator that the BPEL service supporting portal subscription is not configured
Level: 1

Type: ERROR

Impact: Other

WCS-05069: Unable to send subscription notification to moderator(s). The reason is : {0}.

Cause: The BPEL URL has not been configured yet.

Action: Notify your administrator that the BPEL service supporting portal subscription is not configured
Level: 1

Type: ERROR

Impact: Other

WCS-05070: An error occurred attempting to subscribe a user to portal{0}.

Cause: The BPEL server providing the portal subscription service may be down.

Action: Ask your administrator to restart the BPEL server, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05070: An error occurred attempting to subscribe a user to portal{0}.

Cause: The BPEL server providing the portal subscription service may be down.

Action: Ask your administrator to restart the BPEL server, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05071: An error occurred attempting to subscribe user to portal {0}: {1}.

Cause: The BPEL server providing the portal subscription service may be down.

Action: Ask your administrator to restart the BPEL server, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05071: An error occurred attempting to subscribe user to portal {0}: {1}.

Cause: The BPEL server providing the portal subscription service may be down.

Action: Ask your administrator to restart the BPEL server, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05072: Error occurred while navigating to portal {0}.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05072: Error occurred while navigating to portal {0}.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05073: Could not create portal with name {0}

Cause: The portal name provided could not be created.

Action: Please contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05073: Could not create portal with name {0}

Cause: The portal name provided could not be created.

Action: Please contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05074: An error occurred attempting to access a page of the renamed portal.

Cause: The portal rename operation was not successful.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05074: An error occurred attempting to access a page of the renamed portal.

Cause: The portal rename operation was not successful.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05075: An error occurred attempting to rename a portal.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05075: An error occurred attempting to rename a portal.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05077: Could not retrieve portal workflow configuration. Please contact administrator.

Cause: An error occurred attempting to retrieve the BPEL Several URL configured in connections.xml

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05077: Could not retrieve portal workflow configuration. Please contact administrator.

Cause: An error occurred attempting to retrieve the BPEL Several URL configured in connections.xml

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05078: Cannot delete workflow approval metadata from the portal

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05078: Cannot delete workflow approval metadata from the portal

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05079: Cannot get the security handler for portal template {0}

Cause: The policy store metadata was not available for portal template security initialization.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05079: Cannot get the security handler for portal template {0}

Cause: The policy store metadata was not available for portal template security initialization.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05080: Cannot create the portal template {0}

Cause: The portal template was not created due to an error reported by the metadata store.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05080: Cannot create the portal template {0}

Cause: The portal template was not created due to an error reported by the metadata store.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05081: Unable to retrieve metadata object for portal {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05081: Unable to retrieve metadata object for portal {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05082: Adding workflow approval metadata to the portal failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05082: Adding workflow approval metadata to the portal failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05083: An error occurred attempting to rename portal {0} to {1}.

Cause: The portal rename operation was successful.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05083: An error occurred attempting to rename portal {0} to {1}.

Cause: The portal rename operation was successful.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05084: An unexpected error occurred attempting to delete portal {0}.

Cause: The portal delete operation was unsuccessful.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05084: An unexpected error occurred attempting to delete portal {0}.

Cause: The portal delete operation was unsuccessful.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05085: Portal name cannot be null

Cause: Portal name was blank.

Action: Enter a valid alphanumeric name for the portal
Level: 1

Type: ERROR

Impact: Other

WCS-05085: Portal name cannot be null

Cause: Portal name was blank.

Action: Enter a valid alphanumeric name for the portal
Level: 1

Type: ERROR

Impact: Other

WCS-05086: Portal name is a reserved keyword.

Cause: The portal name specified was a reserved keyword.

Action: Specify a valid alphanumeric name for the portal which excludes the following reserved keywords: webcenter, pages, page, spaces, space, group, groups, space, spaces, webcenter space, webcenter spaces, webcenter Portal, WebCenter Portal, WebCenter Portal spaces, portal, webcenter administration, my spaces, admin, last, system.
Level: 1

Type: ERROR

Impact: Other

WCS-05086: Portal name is a reserved keyword.

Cause: The portal name specified was a reserved keyword.

Action: Specify a valid alphanumeric name for the portal which excludes the following reserved keywords: webcenter, pages, page, spaces, space, group, groups, space, spaces, webcenter space, webcenter spaces, webcenter Portal, WebCenter Portal, WebCenter Portal spaces, portal, webcenter administration, my spaces, admin, last, system.
Level: 1

Type: ERROR

Impact: Other

WCS-05087: The portal name contains invalid characters. Only alphanumeric and space characters are allowed.

Cause: Portal name contained non-alphanumeric/space characters.

Action: Specify a valid alphanumeric name for the portal that only contains a-z, A-Z, 0-9, _, or a space character
Level: 1

Type: ERROR

Impact: Other

WCS-05087: The portal name contains invalid characters. Only alphanumeric and space characters are allowed.

Cause: Portal name contained non-alphanumeric/space characters.

Action: Specify a valid alphanumeric name for the portal that only contains a-z, A-Z, 0-9, _, or a space character
Level: 1

Type: ERROR

Impact: Other

WCS-05088: Cannot delete the seeded portal template {0}

Cause: An attempt was made to delete a seeded portal template.

Action: Do not try to delete a seeded portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05088: Cannot delete the seeded portal template {0}

Cause: An attempt was made to delete a seeded portal template.

Action: Do not try to delete a seeded portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05089: Connection details for the BPEL server providing portal notification services are not available. Unable to send add or delete notifications to members of portal{0}

Cause: Connection details for the BPEL server providing portal invitation services were not available or configured incorrectly.

Action: Ask your administrator to configure a connection to the BPEL server providing portal notification services.
Level: 1

Type: ERROR

Impact: Other

WCS-05089: Connection details for the BPEL server providing portal notification services are not available. Unable to send add or delete notifications to members of portal{0}

Cause: Connection details for the BPEL server providing portal invitation services were not available or configured incorrectly.

Action: Ask your administrator to configure a connection to the BPEL server providing portal notification services.
Level: 1

Type: ERROR

Impact: Other

WCS-05090: An error occurred attempting to send a notification to a member added to or deleted from portal {0}

Cause: An error occurred attempting to send a portal notification.

Action: Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Other

WCS-05090: An error occurred attempting to send a notification to a member added to or deleted from portal {0}

Cause: An error occurred attempting to send a portal notification.

Action: Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Other

WCS-05091: Connection details for the BPEL server providing notification services in WebCenter Portal not found.

Cause: Connection details for the BPEL server providing notification services in WebCenter Portal were not available.

Action: Ask the administrator to configure a connection to the BPEL server providing notification services in WebCenter Portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05091: Connection details for the BPEL server providing notification services in WebCenter Portal not found.

Cause: Connection details for the BPEL server providing notification services in WebCenter Portal were not available.

Action: Ask the administrator to configure a connection to the BPEL server providing notification services in WebCenter Portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05092: One of the arguments passed to API call {0} is null

Cause: A null argument was passed to an API call

Action: Invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05092: One of the arguments passed to API call {0} is null

Cause: A null argument was passed to an API call

Action: Invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05093: Portal template name cannot be null

Cause: No name was specified for the portal template.

Action: Specify a valid alphanumeric name for portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05093: Portal template name cannot be null

Cause: No name was specified for the portal template.

Action: Specify a valid alphanumeric name for portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05094: Portal template name is a reserved keyword.

Cause: The template name specified was a reserved keyword.

Action: Specify a valid alphanumeric name for the template which excludes the following reserved keywords: admin, builder, group, groups, home, last, page, pages, my portals, my spaces, portal, portals, spaces, space, system, webcenter, webcenter administration, webcenter portal, webcenter portals, webcenter space, webcenter spaces.
Level: 1

Type: ERROR

Impact: Other

WCS-05094: Portal template name is a reserved keyword.

Cause: The template name specified was a reserved keyword.

Action: Specify a valid alphanumeric name for the template which excludes the following reserved keywords: webcenter, pages, page, spaces, space, group, groups, space, spaces, webcenter space, webcenter spaces, webcenter Portal, WebCenter Portal, WebCenter Portal spaces, WebCenter Portal spaces, portal, webcenter administration, my spaces, admin, last
Level: 1

Type: ERROR

Impact: Other

WCS-05095: Template name contains invalid characters. Only alphanumeric and space characters are allowed.

Cause: Template name contains non-alphanumeric or space characters

Action: Specify a valid alphanumeric name for the template that only contains:a-z, A-Z, 0-9, _, or a space character
Level: 1

Type: ERROR

Impact: Other

WCS-05095: Template name contains invalid characters. Only alphanumeric and space characters are allowed.

Cause: Template name contains non-alphanumeric or space characters

Action: Specify a valid alphanumeric name for the template that only contains:a-z, A-Z, 0-9, _, or a space character
Level: 1

Type: ERROR

Impact: Other

WCS-05096: A portal template with name {0} already exists.

Cause: A portal template with the specified name exists.

Action: Specify a unique name.
Level: 1

Type: ERROR

Impact: Other

WCS-05096: A portal template with name {0} already exists.

Cause: A portal template with the specified name exists.

Action: Specify a unique name.
Level: 1

Type: ERROR

Impact: Other

WCS-05097: Cannot upload portal icon

Cause: An error occurred while attempting to upload the file to WebCenter Portal

Action: Try again or contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-05097: Cannot upload portal icon

Cause: An error occurred while attempting to upload the file to WebCenter Portal

Action: Try again or contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-05098: Cannot upload a portal logo

Cause: An error occurred attempting to upload the file to WebCenter Portal

Action: Try again or contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-05098: Cannot upload a portal logo

Cause: An error occurred attempting to upload the file to WebCenter Portal

Action: Try again or contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-05099: Unable to set lock on portal {0}

Cause: A lock could not be acquired for this portal.

Action: Try again later.
Level: 1

Type: ERROR

Impact: Other

WCS-05099: Unable to set lock on portal {0}

Cause: A lock could not be acquired for this portal.

Action: Try again later.
Level: 1

Type: ERROR

Impact: Other

WCS-05100: Unable to execute operation on portal {0}

Cause: Portal {0} was locked by some other operation.

Action: Wait for the first operation to complete and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05100: Unable to execute operation on portal {0}

Cause: Portal {0} was locked by some other operation.

Action: Wait for the first operation to complete and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05101: Unable to execute portal operation

Cause: The portal was locked by some other operation.

Action: Wait for the first operation to complete and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05101: Unable to execute portal operation

Cause: The portal was locked by some other operation.

Action: Wait for the first operation to complete and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05102: Error creating portal {0} from portal template {1}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05102: Error creating portal {0} from portal template {1}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05103: Errors while renaming portal {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05103: Errors while renaming portal {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05104: Unexpected error while trying to request change membership to portal {0}

Cause: The BPEL server might have been down.

Action: Ensure BPEL server is up and retry. Contact the portal manager for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05104: Unexpected error while trying to request change membership to portal {0}

Cause: The BPEL server might have been down.

Action: Ensure BPEL server is up and retry. Contact the portal moderator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05105: Unexpected error while trying to send notification to user {0}

Cause: The BPEL server might have been down.

Action: Ensure BPEL server is up and retry. Contact the portal manager for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05105: Unexpected error while trying to send notification to user {0}

Cause: The BPEL server might have been down.

Action: Ensure BPEL server is up and retry. Contact the portal moderator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05106: Unexpected error creating region in cache

Cause: An attempt to create a region in the JOC (Java Object Cache) failed.

Action: Ensure that the JOC configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-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-05107: Unexpected error getting object {0} from region {1} in cache

Cause: An attempt to retrieve an object from the cache failed.

Action: Ensure that the JOC configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05108: Search {0} for portal returned more than {2} results.

Cause: Search matched {1} results for portal template. The maximum number of result records allowed for this report is {1}.

Action: Restrict your query further, or use a different query.
Level: 1

Type: ERROR

Impact: Other

WCS-05108: Search {0} for portal returned more than {2} results.

Cause: Search matched {1} results for portal template. The maximum number of result records allowed for this report is {1}.

Action: Restrict your query further, or use a different query.
Level: 1

Type: ERROR

Impact: Other

WCS-05109: Portal operation resulted in unexpected exception.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05109: Portal operation resulted in unexpected exception.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05111: Creating template resulted in unexpected exception.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05111: Creating template resulted in unexpected exception.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05112: Fetching portal member count resulted in unexpected exception.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05112: Fetching portal member count resulted in unexpected exception.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05113: An error occurred while trying to provision the service {0}. The service did not get provisioned.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-05117: An error occurred while trying to load the configuration screen for the selected service.

Cause: An unexpected error occurred.

Action: Reload the browser page, and if problem persists, contact the administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05118: Failed to delete portal {0} security metadata

Cause: Deletion of portal security metadata failed

Action: An unexpected error occurred while trying to deleting portal {0}. Please contact administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05118: Failed to delete portal {0} security metadata

Cause: Deletion of portal security metadata failed

Action: An unexpected error occurred while trying to deleting portal {0}. Please contact administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05119: An unexpected error occurred while trying to provision/unprovision services.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-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-05120: An unexpected error occurred while trying to save the configuration for the service {0}.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05121: An unexpected error occurred while trying to upload an image for portal {0}.

Cause: An unexpected error occurred during image upload.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05121: An unexpected error occurred while trying to upload an image for portal {0}.

Cause: An unexpected error occurred during image upload.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05122: There was an error while fetching the GUID for portal {0}.

Cause: An unexpected error occurred while fetching the GUID for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05122: There was an error while fetching the GUID for portal {0}.

Cause: An unexpected error occurred while fetching the GUID for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05123: Metadata Not Found Exception occurred while fetching the service config metadata for a portal {0}.

Cause: An unexpected error occurred while fetching the service config metadata for portal {0}

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05123: Metadata Not Found Exception occurred while fetching the service config metadata for a portal {0}.

Cause: An unexpected error occurred while fetching the service config metadata for portal {0}

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05124: An exception occurred while fetching the Portal Manager for portal {0}.

Cause: An unexpected error occurred while fetching the Portal Manager for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05124: An exception occurred while fetching the Portal Manager for portal {0}.

Cause: An unexpected error occurred while fetching the Portal Manager for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05125: An exception occurred while fetching the Portal Manager for portal {0}.

Cause: An unexpected error occurred while fetching the Portal Manager for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05125: An exception occurred while fetching the Portal Manager for portal {0}.

Cause: An unexpected error occurred while fetching the Portal Manager for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05126: An exception occurred while fetching the GUID for portal {0}.

Cause: An unexpected error occurred while fetching the GUID for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05126: An exception occurred while fetching the GUID for portal {0}.

Cause: An unexpected error occurred while fetching the GUID for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05127: An exception occurred while fetching the contacts list for portal {0}.

Cause: An unexpected error occurred fetching the contacts list for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05127: An exception occurred while fetching the contacts list for portal {0}.

Cause: An unexpected error occurred fetching the contacts list for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05128: An exception occurred while fetching the GUID for portal {0}.

Cause: An unexpected error occurred while fetching the GUID for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05128: An exception occurred while fetching the GUID for portal {0}.

Cause: An unexpected error occurred while fetching the GUID for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05129: Error occurred while launching the delete role confirmation.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-05135: Error occurred while editing the custom attribute name={0} and value={1}.

Cause: An unexpected error occurred while editing the custom attribute.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05136: Error occurred while fetching the custom attributes for portal {0}.

Cause: An unexpected error occurred while fetching the custom attribute.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05136: Error occurred while fetching the custom attributes for portal {0}.

Cause: An unexpected error occurred while fetching the custom attribute.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05137: No Such Attribute exists.

Cause: Unable to find the custom attributes

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05137: No Such Attribute exists.

Cause: Unable to find the custom attributes

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05138: Unexpected error in getting the list of portals. You can try again later or contact Administrator.

Cause: Unexpected error in getting portals.

Action: Please contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05138: Unexpected error in getting the list of portals. You can try again later or contact Administrator.

Cause: Unexpected error in getting portals.

Action: Please contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05139: Unexpected error in retrieving portal {0}.

Cause: Unexpected error in retrieving the portal.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05139: Unexpected error in retrieving portal {0}.

Cause: Unexpected error in retrieving the portal.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05140: Unexpected error while rolling back the service {0}

Cause: Error in rolling back the service.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05140: Unexpected error while rolling back the service {0}

Cause: Error in rolling back the service.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05141: Unknown errors creating portal. Please contact Administrator.

Cause: Post creating the portal, there were errors.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05141: Unknown errors creating portal. Please contact Administrator.

Cause: Post creating the portal, there were errors.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05142: Portal was created successfully but refreshing the portal list failed. You may try to refresh the portal list manually.

Cause: List refresh failed after creating portal.

Action: Manually refresh the portal list.
Level: 1

Type: ERROR

Impact: Other

WCS-05142: Portal was created successfully but refreshing the portal list failed. You may try to refresh the portal list manually.

Cause: List refresh failed after creating portal.

Action: Manually refresh the portal list.
Level: 1

Type: ERROR

Impact: Other

WCS-05143: Errors were encountered in creating portal. The main error is - {0}. You may want to delete the current portal if it is visible in your lists. Contact the administrator if the problem persists.

Cause: Errors were seen in post-processing the create portal.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05143: Errors were encountered in creating portal. The main error is - {0}. You may want to delete the current portal if it is visible in your lists. Contact the administrator if the problem persists.

Cause: Errors were seen in post-processing the create portal.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05144: Errors were encountered while creating the portal. The main error is - {0}. Rollback of the creation also failed. You may want to clean the current portal if it is visible in your lists. You may want to try to create the portal again later or contact the administrator.

Cause: Error in post-processing the portal.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05144: Errors were encountered while creating the portal. The main error is - {0}. Rollback of the creation also failed. You may want to clean the current portal if it is visible in your lists. You may want to try to create the portal again later or contact the administrator.

Cause: Error in post-processing the portal.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05145: Portal created with the following warning(s) : {0}

Cause: Portal was created with warnings.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05145: Portal created with the following warning(s) : {0}

Cause: Portal was created with warnings.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05146: Unexpected errors in deleting the portal. Contact Administrator.

Cause: Unexpected error in deleting the portal.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05146: Unexpected errors in deleting the portal. Contact Administrator.

Cause: Unexpected error in deleting the portal.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05147: Deletion of the portal resulted in errors. The main error is - {0}. You may want to try deleting the portal again later. If the error persists, contact the administrator.

Cause: Delete of the portal resulted in error.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05147: Deletion of the portal resulted in errors. The main error is - {0}. You may want to try deleting the portal again later. If the error persists, contact the administrator.

Cause: Delete of the portal resulted in error.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05148: Deletion of portal resulted in errors. The main error is - {0}. Rollback of the deletion failed as well. You may want to try deleting the portal again later. If the error persists, contact the administrator.

Cause: Delete of the portal resulted in error.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05148: Deletion of portal resulted in errors. The main error is - {0}. Rollback of the deletion failed as well. You may want to try deleting the portal again later. If the error persists, contact the administrator.

Cause: Delete of the portal resulted in error.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05149: Portal was deleted successfully but refreshing the portal list failed. You may try to refresh the portal list manually.

Cause: List refresh failed after deleting portal.

Action: You can refresh the portal list manually.
Level: 1

Type: ERROR

Impact: Other

WCS-05149: Portal was deleted successfully but refreshing the portal list failed. You may try to refresh the portal list manually.

Cause: List refresh failed after deleting portal.

Action: You can refresh the portal list manually.
Level: 1

Type: ERROR

Impact: Other

WCS-05150: Unexpected errors in renaming the portal. Contact Administrator.

Cause: Unknown errors in renaming the portal.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05150: Unexpected errors in renaming the portal. Contact Administrator.

Cause: Unknown errors in renaming the portal.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05151: Rename of the portal resulted in errors. The main error is - {0}. You may want to try to rename the portal again later. If the error persists, contact the administrator.

Cause: Rename of the portal resulted in error.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05151: Rename of the portal resulted in errors. The main error is - {0}. You may want to try to rename the portal again later. If the error persists, contact the administrator.

Cause: Rename of the portal resulted in error.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05152: Rename of the portal resulted in errors. The main error is - {0}. Rollback of renaming also failed. You may want to try to rename the portal again later or contact the administrator.

Cause: Portal was renamed but there were errors in processing.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05152: Rename of the portal resulted in errors. The main error is - {0}. Rollback of renaming also failed. You may want to try to rename the portal again later or contact the administrator.

Cause: Portal was renamed but there were errors in processing.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05153: Portal was renamed successfully but refreshing the portal list failed. You may try to refresh the portal list manually.

Cause: Refreshing the list after renaming the portal failed.

Action: Manually refresh the list of portals.
Level: 1

Type: ERROR

Impact: Other

WCS-05153: Portal was renamed successfully but refreshing the portal list failed. You may try to refresh the portal list manually.

Cause: Refreshing the list after renaming the portal failed.

Action: Manually refresh the list of portals.
Level: 1

Type: ERROR

Impact: Other

WCS-05154: Portal was renamed with warnings. These are some of the warnings - {0}.

Cause: Portal was renamed with warnings.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05154: Portal was renamed with warnings. These are some of the warnings - {0}.

Cause: Portal was renamed with warnings.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05155: Unexpected error in retrieving the portal list.

Cause: Unexpected error in retrieving the portal list.

Action: Try again after some time. If problem persist, contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05155: Unexpected error in retrieving the portal list.

Cause: Unexpected error in retrieving the portal list.

Action: Try again after some time. If problem persist, contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05156: Unexpected error while provisioning some optional services in the portal. You may want to provision them again by going to portal Administration.

Cause: Unexpected error while provisioning some optional services in the portal.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05156: Unexpected error while provisioning some optional services in the portal. You may want to provision them again by going to portal Administration.

Cause: Unexpected error while provisioning some optional services in the portal.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05157: Provisioning some optional services {0} in the portal did not go through successfully. You may want to provision them again by going to portal Administration.

Cause: Provisioning some optional services in the portal did not go through successfully.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05157: Provisioning some optional services {0} in the portal did not go through successfully. You may want to provision them again by going to portal Administration.

Cause: Provisioning some optional services in the portal did not go through successfully.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05158: Unexpected error while unprovisioning the services.

Cause: Unexpected error in unprovisioning the services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05158: Unexpected error while unprovisioning the services.

Cause: Unexpected error in unprovisioning the services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05159: Portal was deleted with warnings. These are some of the warnings - {0}.

Cause: Portal was renamed with warnings.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05159: Portal was deleted with warnings. These are some of the warnings - {0}.

Cause: Portal was renamed with warnings.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05160: Unexpected errors while granting user access on new portal {0}. Please contact Administrator.

Cause: Unexpected errors while granting access on new portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05160: Unexpected errors while granting user access on new portal {0}. Please contact Administrator.

Cause: Unexpected errors while granting access on new portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05161: Unexpected errors while removing access on new portal {0}. Please contact Administrator.

Cause: Unexpected errors while removing access on new portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05161: Unexpected errors while removing access on new portal {0}. Please contact Administrator.

Cause: Unexpected errors while removing access on new portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05162: Unknown error while removing access for portal {0}

Cause: Unexpected errors while removing access on portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05162: Unknown error while removing access for portal {0}

Cause: Unexpected errors while removing access on portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05163: Unknown error while mapping access for the new portal {0}

Cause: Unexpected errors while mapping access on portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05163: Unknown error while mapping access for the new portal {0}

Cause: Unexpected errors while mapping access on portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05164: Unexpected errors in provisioning services for new portal {0}

Cause: Unexpected errors in provisioning services for new portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05164: Unexpected errors in provisioning services for new portal {0}

Cause: Unexpected errors in provisioning services for new portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05165: Unknown error while reprovisioning services since delete failed for portal {0}

Cause: Unexpected errors while reprovisioning services on portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05165: Unknown error while reprovisioning services since delete failed for portal {0}

Cause: Unexpected errors while reprovisioning services on portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05166: Unknown error while creating metadata for new template {0}

Cause: Unexpected errors while copying metadata from portal {0} to template {1}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05166: Unknown error while creating metadata for new template {0}

Cause: Unexpected errors while copying metadata from portal {0} to template {1}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05167: Unknown error in creating metadata for the new portal {0}

Cause: Unexpected errors while creating metadata for portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05167: Unknown error in creating metadata for the new portal {0}

Cause: Unexpected errors while creating metadata for portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05168: Unknown error in renaming the portal.

Cause: Unexpected errors in renaming the portal.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05168: Unknown error in renaming the portal.

Cause: Unexpected errors in renaming the portal.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05169: Unknown error in renaming services from portal {0} to portal {1}.

Cause: Unexpected errors in renaming the services.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05169: Unknown error in renaming services from portal {0} to portal {1}.

Cause: Unexpected errors in renaming the services.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05170: Updates or deletes are being performed on portal {0} by another Portal Manager. Please try again after some time.

Cause: Portal {0} is already being deleted.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05170: Updates or deletes are being performed on portal {0} by another moderator. Please try again after some time.

Cause: Portal {0} is already being deleted.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05171: Error occurred while trying to determine if service {0} is provisioned in the current portal.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05171: Error occurred while trying to determine if service {0} is provisioned in the current portal.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05172: The role {0} does not exist and hence could not be assigned to the user {1}.

Cause: Role {0} may have already been deleted .

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-05174: Error occurred while accessing footer information.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05175: Portal {0} already exists.

Cause: Name specified for the portal was not unique. A portal with the same name already exists.

Action: Provide a unique name for the portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05175: Portal {0} already exists.

Cause: Name specified for the portal was not unique. A portal with the same name already exists.

Action: Provide a unique name for the portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05176: Portal name must contain at least one alphanumeric character

Cause: Portal name did not contain any alphanumeric characters

Action: Provide at least one alphanumeric character for portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-05176: Portal name must contain at least one alphanumeric character

Cause: Portal name did not contain any alphanumeric characters

Action: Provide at least one alphanumeric character for portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-05177: Unable to perform the operation on the selected portal(s) due to unknown errors

Cause: Selection of portal(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05177: Unable to perform the operation on the selected portal(s) due to unknown errors

Cause: Selection of portal(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05178: Failed to refresh the portal list due to unknown errors

Cause: Unknown error occurred while trying to refresh the portal list

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05178: Failed to refresh the portal list due to unknown errors

Cause: Unknown error occurred while trying to refresh the portal list

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05179: Unable to perform the operation on the selected portal template(s) due to unavoidable errors

Cause: Selection of portal template(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05179: Unable to perform the operation on the selected portal template(s) due to unavoidable errors

Cause: Selection of portal template(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05180: An error occurred while trying to delete the portal template(s).

Cause: Selection of portal template(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05180: An error occurred while trying to delete the portal template(s).

Cause: Selection of portal template(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05181: Error while creating portal

Cause: Error occurred during portal creation

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05181: Error while creating portal

Cause: Error occurred during portal creation

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05182: Error in closing the Create Portal dialog.

Cause: Error occurred while closing the Create Portal dialog

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05182: Error in closing the Create Portal dialog.

Cause: Error occurred while closing the Create Portal dialog

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05183: Another user is modifying the settings. Please try after some time.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05183: Another user is modifying the settings. Please try after some time.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05184: Unable to delete selected portal(s).

Cause: Selection of portal(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05184: Unable to delete selected portal(s).

Cause: Selection of portal(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05185: Unable to export selected portal(s) due to unknown errors

Cause: Selection of portal(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05185: Unable to export selected portal(s) due to unknown errors

Cause: Selection of portal(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05186: Error occurred while checking existing status of portal {0}.

Cause: An unexpected error occurred while checking existing status of the portal.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05186: Error occurred while checking existing status of portal {0}.

Cause: An unexpected error occurred while checking existing status of the portal.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05187: Error occurred while retrieving portal {0} creation date

Cause: An unexpected error occurred while retrieving the portal creation date.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05187: Error occurred while retrieving portal {0} creation date

Cause: An unexpected error occurred while retrieving the portal creation date.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05188: Error occurred while retrieving portal {0} status changed date.

Cause: An unexpected error occurred while retrieving the portal status changed date.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05188: Error occurred while retrieving portal {0} status changed date.

Cause: An unexpected error occurred while retrieving the portal status changed date.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05189: Failed to validate the name/display name

Cause: Failed to validate the name/display name

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05189: Failed to validate the name/display name

Cause: Failed to validate the name/display name

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05190: An error occurred in post-processing the invite for {0} in portal {1}. Please contact Administrator.

Cause: Unable to cleanup invited status metadata

Action: Please contact Administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05190: An error occurred in post-processing the invite for {0} in portal {1}. Please contact Administrator.

Cause: Unable to cleanup invited status metadata

Action: Please contact Administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05191: Unexpected error occurred while saving the portal changes.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05191: Unexpected error occurred while saving the portal changes.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05192: Unexpected error occurred while making portal public.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05192: Unexpected error occurred while making portal public.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05193: Unexpected error retrieving data for the Portal Switcher.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05193: Unexpected error retrieving data for the Portal Switcher.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05194: Portal template {0} based on portal {1} created successfully with the errors.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05194: Portal template {0} based on portal {1} created successfully with the errors.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05195: Portal template {0} deletion failed due to concurrent operation performed on the same resource by some other user.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05195: Portal template {0} deletion failed due to concurrent operation performed on the same resource by some other user.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05197: Portal mail ID is not available because the Mail service is not configured.

Cause: Portal mail ID is not available because the Mail service is not configured.

Action: Contact the administrator to configure the Mail service.
Level: 1

Type: ERROR

Impact: Other

WCS-05197: Portal mail ID is not available because the Mail service is not configured.

Cause: Portal mail ID is not available because the Mail service is not configured.

Action: Contact the administrator to configure the Mail service.
Level: 1

Type: ERROR

Impact: Other

WCS-05198: Failed to initialize cache for portal template {0}.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05198: Failed to initialize cache for portal template {0}.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05200: Failed to update cache for portal template {0}.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05200: Failed to update cache for portal template {0}.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05201: Unknown error occurred while processing the templates.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-05203: Template name must contain at least one alphanumeric character

Cause: Template name did not contain any alphanumeric characters

Action: Provide at least one alphanumeric character for template name.
Level: 1

Type: ERROR

Impact: Other

WCS-05204: Portal display name cannot be null.

Cause: Portal display name was blank.

Action: Enter a valid alphanumeric name for the portal display name
Level: 1

Type: ERROR

Impact: Other

WCS-05204: Portal display name cannot be null.

Cause: Portal display name was blank.

Action: Enter a valid alphanumeric name for the portal display name
Level: 1

Type: ERROR

Impact: Other

WCS-05205: Portal display name is a reserved keyword. One of: {0}

Cause: The portal display name specified was a reserved keyword

Action: Specify a valid alphanumeric name for the portal display name which excludes the following reserved keywords: admin, builder, group, groups, home, last, page, pages, my portals, my spaces, portal, portals, spaces, space, system, webcenter, webcenter administration, webcenter portal,webcenter portals, webcenter space, webcenter spaces.
Level: 1

Type: ERROR

Impact: Other

WCS-05205: Portal display name is a reserved keyword. One of: {0}

Cause: The portal display name specified was a reserved keyword

Action: Specify a valid alphanumeric name for the portal display name which excludes the following reserved keywords: webcenter, pages, page, spaces, space, group, groups, space, spaces, webcenter space, webcenter spaces, webcenter Portal, WebCenter Portal, WebCenter Portal spaces, portal, webcenter administration, my spaces, admin, last.
Level: 1

Type: ERROR

Impact: Other

WCS-05206: The portal name contains invalid characters.

Cause: Portal display name contained non-alphanumeric/space characters.

Action: Specify a valid alphanumeric name for the portal display name that only contains a-z, A-Z, 0-9, _, or a space character
Level: 1

Type: ERROR

Impact: Other

WCS-05206: The portal name contains invalid characters.

Cause: Portal display name contained non-alphanumeric/space characters.

Action: Specify a valid alphanumeric name for the portal display name that only contains a-z, A-Z, 0-9, _, or a space character
Level: 1

Type: ERROR

Impact: Other

WCS-05207: The portal name must contain at least one letter or number.

Cause: Portal display name did not contain any alphanumeric characters

Action: Provide at least one alphanumeric character for portal display name.
Level: 1

Type: ERROR

Impact: Other

WCS-05207: The portal name must contain at least one letter or number.

Cause: Portal display name did not contain any alphanumeric characters

Action: Provide at least one alphanumeric character for portal display name.
Level: 1

Type: ERROR

Impact: Other

WCS-05208: Select at least one portal to change state/status of portal.

Cause: No portal has been selected or changing the state.

Action: Select at least one portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05208: Select at least one portal to change state/status of portal.

Cause: No portal has been selected or changing the state.

Action: Select at least one portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05209: There are no templates available for creating the portal(s). You should refresh the list of templates by going to the Portal Templates page or create new templates or publish available templates if any to continue creating portal(s). If the problem persists, contact system administrator

Cause: No templates available for creating portal.

Action: Create new templates or publish existing templates if any.
Level: 1

Type: ERROR

Impact: Other

WCS-05209: There are no templates available for creating the portal(s). You should refresh the list of templates by going to the Portal Templates page or create new templates or publish available templates if any to continue creating portal(s). If the problem persists, contact system administrator

Cause: No templates available for creating portal.

Action: Create new templates or publish existing templates if any.
Level: 1

Type: ERROR

Impact: Other

WCS-05210: Unknown error occurred while initiating creation of a portal.

Cause: Unable to launch the Create Portal dialog.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05210: Unknown error occurred while initiating creation of a portal.

Cause: Unable to launch the Create Portal dialog.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05211: Unknown error occurred while retrieving the list of templates.

Cause: Unknown error occurred while retrieving the list of templates.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05211: Unknown error occurred while retrieving the list of templates.

Cause: Unknown error occurred while retrieving the list of templates.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05212: User {0} not authorized to perform the operation {1}:{2}

Cause: User {0} not authorized to perform the operation {1}:{2}

Action: User {0} not authorized to perform the operation {1}:{2}
Level: 1

Type: ERROR

Impact: Other

WCS-05212: User {0} not authorized to perform the operation {1}:{2}

Cause: User {0} not authorized to perform the operation {1}:{2}

Action: User {0} not authorized to perform the operation {1}:{2}
Level: 1

Type: ERROR

Impact: Other

WCS-05213: Unexpected Error occurred while performing the method {0}. Contact system administrator.

Cause: Unexpected Error occurred while performing the method {0}.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05213: Unexpected Error occurred while performing the method {0}. Contact system administrator.

Cause: Unexpected Error occurred while performing the method {0}.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05214: Unable to retrieve information about {0} as another user is modifying the {0}. Please try again after some time.

Cause: Cannot retrieve metadata for portal {0} as another user is modifying the settings. Please try after some time.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05214: Unable to retrieve information about {0} as another user is modifying the {0}. Please try again after some time.

Cause: Cannot retrieve metadata for portal {0} as another user is modifying the settings. Please try after some time.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05215: User(s) added successfully, but sending notification to the user(s) failed

Cause: The BPEL server may be down.

Action: Ensure BPEL server is up and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-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-05216: User was removed successfully, but sending notification to the user failed

Cause: The BPEL server may be down.

Action: Ensure BPEL server is up and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-05217: User role was modified successfully, but sending notification to the user failed

Cause: The BPEL server may be down.

Action: Ensure BPEL server is up and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-05217: User role was modified successfully, but sending notification to the user failed

Cause: The BPEL server may be down.

Action: Ensure BPEL server is up and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-05218: Unknown error occurred while navigating to portal {0}.

Cause: Unable to navigate to the portal.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05218: Unknown error occurred while navigating to portal {0}.

Cause: Unable to navigate to the portal.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05219: Try accessing the portal from the Portal Switcher menu or the Portal page if the portal creation resulted in warnings. If the portal is not listed, refresh the list. If the portal is still not visible, report the error to your administrator. If the portal creation resulted in error, try deleting the portal if it is visible or else request the administrator to delete the portal

Cause: You can try accessing the portal from the Portal Switcher menu or the Portal page. If the portal is not listed, try refreshing the listing on the Portal page.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05219: Try accessing the portal from the Portal Switcher menu or the Portal page if the portal creation resulted in warnings. If the portal is not listed, refresh the list. If the portal is still not visible, report the error to your administrator. If the portal creation resulted in error, try deleting the portal if it is visible or else request the administrator to delete the portal

Cause: You can try accessing the portal from the Portal Switcher menu or the Portal page. If the portal is not listed, try refreshing the listing on the Portal page.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05220: Deletion or Rename is being performed on portal {0} by another Portal Manager. Refresh the list of portals and try again after some time.

Cause: Portal {0} is already being deleted or renamed.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05220: Deletion or Rename is being performed on portal {0} by another Moderator. Refresh the list of portals and try again after some time.

Cause: Portal {0} is already being deleted or renamed.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05221: An unexpected error occurred while trying to delete portal template. Try again after some time. If the problem persists, contact administrator.

Cause: An unexpected error occurred while trying to delete portal template.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05221: An unexpected error occurred while trying to delete portal template. Try again after some time. If the problem persists, contact administrator.

Cause: An unexpected error occurred while trying to delete portal template.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05222: Some optional services in the portal could not be provisioned as they were disabled. You may want to provision them again by going to portal Administration.

Cause: Unexpected error while provisioning some optional services in the portal.

Action: Contact Administrator and look in the logs for information about the specific service that has been disabled.
Level: 1

Type: ERROR

Impact: Other

WCS-05222: Some optional services in the portal could not be provisioned as they were disabled. You may want to provision them again by going to portal Administration.

Cause: Unexpected error while provisioning some optional services in the portal.

Action: Contact Administrator and look in the logs for information about the specific service that has been disabled.
Level: 1

Type: ERROR

Impact: Other

WCS-05223: Admin Role does not exist in the policy store for portal {0}, so creating it

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05223: Admin Role does not exist in the policy store for portal {0}, so creating it

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05224: Unexpected error occurred while revoking portal public status.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05224: Unexpected error occurred while revoking portal public status.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05225: Cannot retrieve the portal distribution list for {0} due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05225: Cannot retrieve the portal distribution list for {0} due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05226: Cannot retrieve the portal managers list for {0} due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05226: Cannot retrieve the portal moderators list for {0} due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05227: Cannot retrieve the Webcenter Portal administrators list due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05227: Cannot retrieve the Webcenter Portal administrators list due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05228: Unable to send change membership notification. The reason is : {0}.

Cause: The BPEL URL has not been configured yet.

Action: Notify your administrator that the BPEL service supporting portal subscription is not configured
Level: 1

Type: ERROR

Impact: Other

WCS-05228: Unable to send change membership notification. The reason is : {0}.

Cause: The BPEL URL has not been configured yet.

Action: Notify your administrator that the BPEL service supporting portal subscription is not configured
Level: 1

Type: ERROR

Impact: Other

WCS-05229: Cannot retrieve portal workflow configuration. Please contact your administrator.

Cause: The BPEL URL has not been configured yet.

Action: Notify your administrator that the BPEL service supporting portal subscription is not configured
Level: 1

Type: ERROR

Impact: Other

WCS-05229: Cannot retrieve portal workflow configuration. Please contact your administrator.

Cause: The BPEL URL has not been configured yet.

Action: Notify your administrator that the BPEL service supporting portal subscription is not configured
Level: 1

Type: ERROR

Impact: Other

WCS-05230: An error occurred while searching invited user {0} in portal {1}. Contact your administrator.

Cause: Unable to search invited status metadata

Action: Contact your administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05230: An error occurred while searching invited user {0} in portal {1}. Contact your administrator.

Cause: Unable to search invited status metadata

Action: Contact your administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05231: Cannot retrieve user {0} email ID in portal {1} due to {2}

Cause: Failed to retrieve email id due to {2}

Action: Contact your administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05231: Cannot retrieve user {0} email ID in portal {1} due to {2}

Cause: Failed to retrieve email id due to {2}

Action: Contact your administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05232: Template publishing role does not exist in the policy store for portal {0}, so creating it

Cause: Copy of the role failed, now trying to sanitize the portal security data

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05232: Template publishing role does not exist in the policy store for portal {0}, so creating it

Cause: Copy of the role failed, now trying to sanitize the portal security data

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05233: Sanitizing template {0} failed unable to copy the publish data

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05233: Sanitizing template {0} failed unable to copy the publish data

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05234: WebCenter Portal is not configured with BPEL server information.

Cause: BPEL server is not configured.

Action: Contact your administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05234: WebCenter Portal is not configured with BPEL server information.

Cause: BPEL server is not configured.

Action: Contact your administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05235: WebCenter Portal is not properly configured with the required BPEL server information.

Cause: BPEL server information is not correct.

Action: Contact your administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05235: WebCenter Portal is not properly configured with the required BPEL server information.

Cause: BPEL server information is not correct.

Action: Contact your administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05236: BPEL server is either down or not properly configured.

Cause: Either the BPEL server is down or the portal workflows are not configured properly

Action: Contact your administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05236: BPEL server is either down or not properly configured.

Cause: Either the BPEL server is down or the portal workflows are not configured properly

Action: Contact your administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05237: Unexpected error occurred rebuilding the user portals list.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05237: Unexpected error occurred rebuilding the user portals list.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05238: Unexpected error occurred rebuilding the public portals list.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05238: Unexpected error occurred rebuilding the public portals list.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05239: Unable to retrieve portal tags.

Cause: An error occurred while trying to retrieve the tags for portal.

Action: Please contact Administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05239: Unable to retrieve portal tags.

Cause: An error occurred while trying to retrieve the tags for portal.

Action: Please contact Administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05240: Unable to create portal tags.

Cause: An error occurred while trying to create the tags for portal.

Action: Please contact Administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05240: Unable to create portal tags.

Cause: An error occurred while trying to create the tags for portal.

Action: Please contact Administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05241: Error occurred while getting portal activity streaming preferences.

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05241: Error occurred while getting portal activity streaming preferences.

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05242: Error occurred while fetching the portal members information.

Cause: Error occurred while fetching the portal members information.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05242: Error occurred while fetching the portal members information.

Cause: Error occurred while fetching the portal members information.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05243: Unexpected error deriving {0} list.

Cause: An unexpected error occurred.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05243: Unexpected error deriving {0} list.

Cause: An unexpected error occurred.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05244: The member's current role is selected. If you want to change this member's role, choose another role from the list.

Cause: The new role is same as the old role.

Action: Select new role.
Level: 1

Type: ERROR

Impact: Other

WCS-05244: The member's current role is selected. If you want to change this member's role, choose another role from the list.

Cause: The new role is same as the old role.

Action: Select new role.
Level: 1

Type: ERROR

Impact: Other

WCS-05246: Unexpected error persisting portal information to tables

Cause: Error saving portal information to the database

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05246: Unexpected error persisting portal information to tables

Cause: Error saving portal information to the database

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05247: Unable to retrieve mail ID for the portal.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05247: Unable to retrieve mail ID for the portal.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05248: Unable to find security policy store metadata while creating portal template {0}

Cause: An error was detected in the application's configuration.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05248: Unable to find security policy store metadata while creating portal template {0}

Cause: An error was detected in the application's configuration.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05249: Unexpected error occurred fetching ratings table from repository.

Cause: An unexpected error occurred fetching the bulk ratings table from the repository.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05249: Unexpected error occurred fetching ratings table from repository.

Cause: An unexpected error occurred fetching the bulk ratings table from the repository.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05250: Unable to delete portal {0} as either it is being exported or imported. Please refresh the list portals list and try again later.

Cause: Attempt to delete portal {0} when the portal is being exported/imported.

Action: Try delete after sometime. Contact the administrator if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05250: Unable to delete portal {0} as either it is being exported or imported. Please refresh the list portals list and try again later.

Cause: Attempt to delete portal {0} when the portal is being exported/imported.

Action: Try delete after sometime. Contact the administrator if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05251: Unable to delete the portal template {0} as either it is being exported or imported. Please refresh the portal templates list and try again later.

Cause: Attempt to delete portal template {0} when the portal is being exported/imported.

Action: Try delete after sometime. Contact the administrator if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05251: Unable to delete the portal template {0} as either it is being exported or imported. Please refresh the portal templates list and try again later.

Cause: Attempt to delete portal template {0} when the portal is being exported/imported.

Action: Try delete after sometime. Contact the administrator if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05252: Unexpected error in getting information from users table

Cause: Error in getting information from the database

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05252: Unexpected error in getting information from users table

Cause: Error in getting information from the database

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05253: Role {1} of a user {0} is changed successfully to Role {2}, with failures in some of the services {3}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05253: Role {1} of a user {0} is changed successfully to Role {2}, with failures in some of the services {3}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05254: Unexpected error occurred while refreshing the portal cache

Cause: Unexpected error occurred while refreshing the portal cache

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05254: Unexpected error occurred while refreshing the portal cache

Cause: Unexpected error occurred while refreshing the portal cache

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05255: Unexpected error occurred while cleaning up some of the permissions

Cause: Failed to clean up the policies post portal creation due to unexpected error

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05255: Unexpected error occurred while cleaning up some of the permissions

Cause: Failed to clean up the policies post portal creation due to unexpected error

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05256: Error while deleting security metadata for portal {0}.

Cause: An unexpected error occurred while deleting security metadata for portal. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-05256: Error while deleting security metadata for portal {0}.

Cause: An unexpected error occurred while deleting security metadata for portal. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-05267: Error while deleting security metadata for portal template {0}.

Cause: An unexpected error occurred while deleting security metadata for portal template. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-05267: Error while deleting security metadata for portal template {0}.

Cause: An unexpected error occurred while deleting security metadata for portal template. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-05268: Error occurred while fetching the portal data.

Cause: Error occurred while fetching the portal data.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05268: Error occurred while fetching the portal data.

Cause: Error occurred while fetching the portal data.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05269: Error occurred while fetching the portal template data.

Cause: Error occurred while fetching the portal template data.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05269: Error occurred while fetching the portal template data.

Cause: Error occurred while fetching the portal template data.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05270: You can add only a total of {0} items including subportals to the selected set. Remove items from selected set and try to add again.

Cause: Limit of selected set exceeded.

Action: Remove items from selected set and add again.
Level: 1

Type: ERROR

Impact: Other

WCS-05270: You can add only a total of {0} items including subportals to the selected set. Remove items from selected set and try to add again.

Cause: Limit of selected set exceeded.

Action: Remove items from selected set and add again.
Level: 1

Type: ERROR

Impact: Other

WCS-05271: Please select one or more row to add.

Cause: No rows selected to add.

Action: Select one or more rows and add again.
Level: 1

Type: ERROR

Impact: Other

WCS-05271: Please select one or more row to add.

Cause: No rows selected to add.

Action: Select one or more rows and add again.
Level: 1

Type: ERROR

Impact: Other

WCS-05272: Unexpected errors while granting user access on new portal template {0}. Please contact Administrator.

Cause: Unexpected errors while granting access on new group template : {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05272: Unexpected errors while granting user access on new portal template {0}. Please contact Administrator.

Cause: Unexpected errors while granting access on new group template : {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05273: Unknown error in removing access for the portal template {0}

Cause: Unexpected errors while removing access on portal template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05273: Unknown error in removing access for the portal template {0}

Cause: Unexpected errors while removing access on portal template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05274: Unable to find the security management lock for template {0}

Cause: Unable to find the security management lock for template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05274: Unable to find the security management lock for template {0}

Cause: Unable to find the security management lock for template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05275: Unexpected errors in provisioning services for new portal template {0}

Cause: Unexpected errors in provisioning services for new portal template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05275: Unexpected errors in provisioning services for new portal template {0}

Cause: Unexpected errors in provisioning services for new portal template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05276: Unknown error in reprovisioning services since delete failed for portal template {0}

Cause: Unexpected errors while reprovisioning services on portal template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05276: Unknown error in reprovisioning services since delete failed for portal template {0}

Cause: Unexpected errors while reprovisioning services on portal template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05277: Unknown error in mapping access for the new portal template {0}

Cause: Unexpected errors while mapping access on portal template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05277: Unknown error in mapping access for the new portal template {0}

Cause: Unexpected errors while mapping access on portal template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05278: Portal template {0} already exists.

Cause: Name specified for the portal template was not unique. A portal template with the same name already exists.

Action: Provide a unique name for the portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05278: Portal template {0} already exists.

Cause: Name specified for the portal template was not unique. A portal template with the same name already exists.

Action: Provide a unique name for the portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05279: Unexpected error while rolling back the template during {0}

Cause: Error in rolling back the plugin.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05279: Unexpected error while rolling back the template during {0}

Cause: Error in rolling back the plugin.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05280: Creation of portal template resulted in error. Rollback of the create template failed as well. The main error is - {0}. You may delete the template if it is available in the list as this template is in unusable state.

Cause: Error in rolling back the plugin.

Action: Try deleting this template if it is available on the Portale Templates page.
Level: 1

Type: ERROR

Impact: Other

WCS-05280: Creation of portal template resulted in error. Rollback of the create template failed as well. The main error is - {0}. You may delete the template if it is available in the list as this template is in unusable state.

Cause: Error in rolling back the plugin.

Action: Try deleting this template if it is available on the Portale Templates page.
Level: 1

Type: ERROR

Impact: Other

WCS-05281: Rollback of portal template metadata also resulted in error. The main error is - {0}. Try deleting the template from the Portal Templates page if it is available as this template is in unusable state.

Cause: Error in deleting the template metadata.

Action: Try deleting this template if it is available on the Portal Templates page.
Level: 1

Type: ERROR

Impact: Other

WCS-05281: Rollback of portal template metadata also resulted in error. The main error is - {0}. Try deleting the template from the Portal Templates page if it is available as this template is in unusable state.

Cause: Error in deleting the template metadata.

Action: Try deleting this template if it is available on the Portal Templates page.
Level: 1

Type: ERROR

Impact: Other

WCS-05282: Unexpected errors in deleting the portal template. Contact Administrator.

Cause: Unexpected error in deleting the portal template.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05282: Unexpected errors in deleting the portal template. Contact Administrator.

Cause: Unexpected error in deleting the portal template.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05283: Deletion of the portal template resulted in errors. The main error is - {0}. You may want to try again later. If the error persists, contact the administrator.

Cause: Delete of the portal template resulted in error.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05283: Deletion of the portal template resulted in errors. The main error is - {0}. You may want to try again later. If the error persists, contact the administrator.

Cause: Delete of the portal template resulted in error.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05284: Deletion of portal template resulted in errors. Rollback of the deletion failed as well. The main error is -{0}. You may want to try again later. If the error persists, contact the administrator.

Cause: Delete of the portal template resulted in error.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05284: Deletion of portal template resulted in errors. Rollback of the deletion failed as well. The main error is -{0}. You may want to try again later. If the error persists, contact the administrator.

Cause: Delete of the portal template resulted in error.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05285: Portal template was deleted successfully but refreshing the portal template list failed. You may try to refresh the portal template list manually.

Cause: List refresh failed after deleting portal template.

Action: You can refresh the portal template list manually.
Level: 1

Type: ERROR

Impact: Other

WCS-05285: Portal template was deleted successfully but refreshing the portal template list failed. You may try to refresh the portal template list manually.

Cause: List refresh failed after deleting portal template.

Action: You can refresh the portal template list manually.
Level: 1

Type: ERROR

Impact: Other

WCS-05286: Updates or deletes are being performed on portal template {0} by another Portal Manager. Please try again after some time.

Cause: Portal template {0} is already being deleted.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05286: Updates or deletes are being performed on portal template {0} by another Moderator. Please try again after some time.

Cause: Portal template {0} is already being deleted.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05287: Unexpected errors occurred while creating template {0}.

Cause: Unexpected errors occurred while creating template.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05287: Unexpected errors occurred while creating template {0}.

Cause: Unexpected errors occurred while creating template.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05288: Creation of template resulted in errors. The main error is - {0}. Try again after some time or contact administrator

Cause: Template creation resulted in errors.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05288: Creation of template resulted in errors. The main error is - {0}. Try again after some time or contact administrator

Cause: Template creation resulted in errors.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05289: Unexpected error occurred while executing pre portal template creation due to {0}.

Cause: Unexpected error occurred while executing pre portal template creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05289: Unexpected error occurred while executing pre portal template creation due to {0}.

Cause: Unexpected error occurred while executing pre portal template creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05290: Base portal name cannot be null

Cause: Base portal name cannot be null

Action: Enter a value for base portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05290: Base portal name cannot be null

Cause: Base portal name cannot be null

Action: Enter a value for base portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05291: Error occurred while executing custom pre portal creation code due to {0}.

Cause: Error occurred while executing custom pre portal creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05291: Error occurred while executing custom pre portal creation code due to {0}.

Cause: Error occurred while executing custom pre portal creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05292: Error occurred while executing custom post portal creation code due to {0}.

Cause: Error occurred while executing custom post portal creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05292: Error occurred while executing custom post portal creation code due to {0}.

Cause: Error occurred while executing custom post portal creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05293: Error occurred while executing custom pre portal deletion code due to {0}.

Cause: Error occurred while executing custom pre portal deletion due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05293: Error occurred while executing custom pre portal deletion code due to {0}.

Cause: Error occurred while executing custom pre portal deletion due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05294: Error occurred while executing custom post portal deletion code due to {0}.

Cause: Error occurred while executing custom post portal deletion due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05294: Error occurred while executing custom post portal deletion code due to {0}.

Cause: Error occurred while executing custom post portal deletion due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05295: Error occurred while executing custom pre portal rename code due to {0}.

Cause: Error occurred while executing custom pre portal rename due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05295: Error occurred while executing custom pre portal rename code due to {0}.

Cause: Error occurred while executing custom pre portal rename due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05296: Error occurred while executing custom post portal rename code due to {0}.

Cause: Error occurred while executing custom post portal rename due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05296: Error occurred while executing custom post portal rename code due to {0}.

Cause: Error occurred while executing custom post portal rename due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05297: Error occurred while executing custom pre portal template creation code due to {0}.

Cause: Error occurred while executing custom pre portal template creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05297: Error occurred while executing custom pre portal template creation code due to {0}.

Cause: Error occurred while executing custom pre portal template creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05298: Error occurred while executing custom post portal template creation code due to {0}.

Cause: Error occurred while executing custom post portal template creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05298: Error occurred while executing custom post portal template creation code due to {0}.

Cause: Error occurred while executing custom post portal template creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05299: Portal template created with the following warning(s) : {0}

Cause: Portal was created with warnings.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05299: Portal template created with the following warning(s) : {0}

Cause: Portal was created with warnings.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05300: Error occurred while executing custom pre portal template deletion code due to {0}.

Cause: Error occurred while executing custom pre portal template deletion due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05300: Error occurred while executing custom pre portal template deletion code due to {0}.

Cause: Error occurred while executing custom pre portal template deletion due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05301: Error occurred while executing custom post portal template deletion code due to {0}.

Cause: Error occurred while executing custom post portal template deletion due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05301: Error occurred while executing custom post portal template deletion code due to {0}.

Cause: Error occurred while executing custom post portal template deletion due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05302: Unexpected error occurred while executing pre portal creation due to {0}.

Cause: Unexpected error occurred while executing pre portal creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05302: Unexpected error occurred while executing pre portal creation due to {0}.

Cause: Unexpected error occurred while executing pre portal creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05303: Unable to add {0} as it conflicts with another portal on target application.

Cause: Conflict cannot be imported.

Action: Deselect the conflict row and add again.
Level: 1

Type: ERROR

Impact: Other

WCS-05303: Unable to add {0} as it conflicts with another portal on target application.

Cause: Conflict cannot be imported.

Action: Unselect the conflict row and add again.
Level: 1

Type: ERROR

Impact: Other

WCS-05309: Unexpected error occurred during updating template {0}

Cause: Unexpected error occurred during updating template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05309: Unexpected error occurred during updating template {0}

Cause: Unexpected error occurred during updating template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05310: Template Display Name is null

Cause: Template Display Name is null.

Action: Enter valid values.
Level: 1

Type: ERROR

Impact: Other

WCS-05310: Template Display Name is null

Cause: Template Display Name is null.

Action: Enter valid values.
Level: 1

Type: ERROR

Impact: Other

WCS-05311: Template display name is a reserved keyword. One of: {0}

Cause: The template display name specified was a reserved keyword

Action: Specify a valid alphanumeric name for the template display name which excludes the following reserved keywords: webcenter, pages, page, Spaces, Space, group, groups, Space, Spaces, webcenter Space, webcenter Spaces, webcenter Portal, WebCenter Portal, WebCenter Portal Spaces, portal, webcenter administration, my Spaces, admin, last.
Level: 1

Type: ERROR

Impact: Other

WCS-05311: Template display name is a reserved keyword. One of: {0}

Cause: The template display name specified was a reserved keyword

Action: Specify a valid alphanumeric name for the template display name which excludes the following reserved keywords: webcenter, pages, page, Spaces, Space, group, groups, Space, Spaces, webcenter Space, webcenter Spaces, webcenter Portal, WebCenter Portal, WebCenter Portal Spaces, portal, webcenter administration, my Spaces, admin, last.
Level: 1

Type: ERROR

Impact: Other

WCS-05312: The template display name contains invalid characters. Only alphanumeric and space characters are allowed.

Cause: Template display name contained non-alphanumeric/space characters.

Action: Specify a valid alphanumeric name for the template display name that only contains a-z, A-Z, 0-9, _, or a space character
Level: 1

Type: ERROR

Impact: Other

WCS-05312: The template display name contains invalid characters. Only alphanumeric and space characters are allowed.

Cause: Template display name contained non-alphanumeric/space characters.

Action: Specify a valid alphanumeric name for the template display name that only contains a-z, A-Z, 0-9, _, or a space character
Level: 1

Type: ERROR

Impact: Other

WCS-05313: Portal display name must contain at least one alphanumeric character

Cause: Portal display name did not contain any alphanumeric characters

Action: Provide at least one alphanumeric character for portal display name.
Level: 1

Type: ERROR

Impact: Other

WCS-05313: Portal display name must contain at least one alphanumeric character

Cause: Portal display name did not contain any alphanumeric characters

Action: Provide at least one alphanumeric character for portal display name.
Level: 1

Type: ERROR

Impact: Other

WCS-05314: Portal template with display name {0} already exists.

Cause: Portal template with display name {0} already exists.

Action: Enter another display Name.
Level: 1

Type: ERROR

Impact: Other

WCS-05314: Portal template with display name {0} already exists.

Cause: Portal template with display name {0} already exists.

Action: Enter another display Name.
Level: 1

Type: ERROR

Impact: Other

WCS-05315: Unexpected error occurred while fetching template displayName {0}.

Cause: Template with display name {0} already exists.

Action: Enter another display Name.
Level: 1

Type: ERROR

Impact: Other

WCS-05315: Unexpected error occurred while fetching template displayName {0}.

Cause: Template with display name {0} already exists.

Action: Enter another display Name.
Level: 1

Type: ERROR

Impact: Other

WCS-05316: Unexpected error occurred while creating role {0} for template {1}

Cause: Unexpected error occurred while creating role {0} for template {1}.

Action: Try again after some time or Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05316: Unexpected error occurred while creating role {0} for template {1}

Cause: Unexpected error occurred while creating role {0} for template {1}.

Action: Try again after some time or Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05317: Unexpected error occurred while saving members data from portal {0} to template {1}

Cause: Unexpected error occurred while saving members data from portal {0} to template {1}.

Action: Try again after some time or contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05317: Unexpected error occurred while saving members data from portal {0} to template {1}

Cause: Unexpected error occurred while saving members data from portal {0} to template {1}.

Action: Try again after some time or contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05318: Unexpected error occurred while copying member from template {0} to portal {1}

Cause: Unexpected error occurred while copying member {0} whose role {1} due to {3}.

Action: Try again after some time or Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05318: Unexpected error occurred while copying member from template {0} to portal {1}

Cause: Unexpected error occurred while copying member {0} whose role {1} due to {3}.

Action: Try again after some time or Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05325: Parent portal cannot be null

Cause: Parent portal was null.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05325: Parent portal cannot be null

Cause: Parent portal was null.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05326: Failed to set parent portal

Cause: Error in setting parent portal

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05326: Failed to set parent portal

Cause: Error in setting parent portal

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05327: Unexpected error occurred while making the template {0} public.

Cause: Unexpected error occurred while making the template {0} public.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05327: Unexpected error occurred while making the template {0} public.

Cause: Unexpected error occurred while making the template {0} public.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05328: Unexpected error occurred while fetching the templates.

Cause: UUnexpected error occurred while fetching the templates.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05328: Unexpected error occurred while fetching the templates.

Cause: UUnexpected error occurred while fetching the templates.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05329: Unexpected error occurred while deleting the template during overriding the template {0}.

Cause: Unexpected error occurred while deleting the template while overriding the template.

Action: Contact Administrator or Try again after some time
Level: 1

Type: ERROR

Impact: Other

WCS-05329: Unexpected error occurred while deleting the template during overriding the template {0}.

Cause: Unexpected error occurred while deleting the template while overriding the template.

Action: Contact Administrator or Try again after some time
Level: 1

Type: ERROR

Impact: Other

WCS-05330: Unexpected error occurred while overriding the template {0}.

Cause: Unexpected error occurred while overriding the template.

Action: Contact Administrator or Try again after some time
Level: 1

Type: ERROR

Impact: Other

WCS-05330: Unexpected error occurred while overriding the template {0}.

Cause: Unexpected error occurred while overriding the template.

Action: Contact Administrator or Try again after some time
Level: 1

Type: ERROR

Impact: Other

WCS-05331: Unexpected error occurred while saving the template permissions.

Cause: Unexpected error occurred while saving the template permissions.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05331: Unexpected error occurred while saving the template permissions.

Cause: Unexpected error occurred while saving the template permissions.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05332: Unexpected error occurred while fetching the supported languages for this portal.

Cause: Unexpected error occurred while fetching the supported languages.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05332: Unexpected error occurred while fetching the supported languages for this portal.

Cause: Unexpected error occurred while fetching the supported languages.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05333: Unexpected error occurred while launching the portal in edit mode.

Cause: Unexpected error occurred while launching the portal in edit mode.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05333: Unexpected error occurred while launching the portal in edit mode.

Cause: Unexpected error occurred while launching the portal in edit mode.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05334: This operation is not possible on multiple portals. Select one portal to proceed with the operation.

Cause: Unable to perform the operation on multiple portals.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05334: This operation is not possible on multiple portals. Select one portal to proceed with the operation.

Cause: Unable to perform the operation on multiple portals.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05335: Unexpected error occurred while launching the About Portal dialog.

Cause: Unexpected error occurred while launching the About Portal dialog.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05335: Unexpected error occurred while launching the About Portal dialog.

Cause: Unexpected error occurred while launching the About Portal dialog.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05336: Portal not specified

Cause: The supplied portal name was null or blank.

Action: Specify a valid portal name that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-05336: Portal not specified

Cause: The supplied portal name was null or blank.

Action: Specify a valid portal name that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-05337: Membership not changed for user {0}. You cannot manage your own membership.

Cause: Changing one's own membership in a portal is not allowed.

Action: Select users other than the current user to change their membership.
Level: 1

Type: WARNING

Impact: Other

WCS-05337: Membership not changed for user {0}. You cannot manage your own membership.

Cause: Changing one's own membership in a portal is not allowed.

Action: Select users other than the current user to change their membership.
Level: 1

Type: WARNING

Impact: Other

WCS-05338: Unexpected error occurred while publishing portal template(s)

Cause: Unexpected error occurred while publishing portal template(s)

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05338: Unexpected error occurred while publishing portal template(s)

Cause: Unexpected error occurred while publishing portal template(s)

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05339: Unable to create portal as the template name is not specified.

Cause: Template is not selected.

Action: Select at least one template to create portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05339: Unable to create portal as the template name is not specified.

Cause: Template is not selected.

Action: Select at least one template to create portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05340: Unknown errors occurred while saving the cache for portal {0}, try setting the values again in the portal administration settings.

Cause: Error while saving cache.

Action: Retry again from Settings screen.
Level: 1

Type: ERROR

Impact: Other

WCS-05340: Unknown errors occurred while saving the cache for portal {0}, try setting the values again in the portal administration settings.

Cause: Error while saving cache.

Action: Retry again from Settings screen.
Level: 1

Type: ERROR

Impact: Other

WCS-05341: Portal display name must be less than 200 characters.

Cause: Portal display name exceeded 200 characters.

Action: Specify portal display name less than 200 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05341: Portal display name must be less than 200 characters.

Cause: Portal display name exceeded 200 characters.

Action: Specify portal display name less than 200 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05342: Portal name must be less than 200 characters.

Cause: Portal name exceeded 200 characters.

Action: Specify portal name less than 200 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05342: Portal name must be less than 200 characters.

Cause: Portal name exceeded 200 characters.

Action: Specify portal name less than 200 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05343: Portal template display name must be less than 200 characters.

Cause: Portal template display name exceeded 200 characters.

Action: Specify portal template display name less than 200 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05343: Portal template display name must be less than 200 characters.

Cause: Portal template display name exceeded 200 characters.

Action: Specify portal template display name less than 200 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05344: Portal template name must be less than 200 characters.

Cause: Portal template name exceeded 200 characters.

Action: Specify portal template name less than 200 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05344: Portal template name must be less than 200 characters.

Cause: Portal template name exceeded 200 characters.

Action: Specify portal template name less than 200 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05345: Keywords must be less than 4000 characters.

Cause: Keywords exceeded 4000 characters.

Action: Specify keywords less than 4000 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05345: Keywords must be less than 4000 characters.

Cause: Keywords exceeded 4000 characters.

Action: Specify keywords less than 4000 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05346: Description must be less than 4000 characters.

Cause: Description exceeded 4000 characters.

Action: Specify description less than 4000 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05346: Description must be less than 4000 characters.

Cause: Description exceeded 4000 characters.

Action: Specify description less than 4000 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05347: Select at least one portal to continue the operation.

Cause: Select at least one portal to continue.

Action: Select at least one portal to continue.
Level: 1

Type: ERROR

Impact: Other

WCS-05347: Select at least one portal to continue the operation.

Cause: Select at least one portal to continue.

Action: Select at least one portal to continue.
Level: 1

Type: ERROR

Impact: Other

WCS-05348: Unexpected error occurred while publishing following portal template(s) {0}

Cause: Unexpected error occurred while publishing following portal template(s) {0}

Action: Contact Administrator or try again after some time.
Level: 1

Type: ERROR

Impact: Other

WCS-05348: Unexpected error occurred while publishing following portal template(s) {0}

Cause: Unexpected error occurred while publishing following portal template(s) {0}

Action: Contact Administrator or try again after some time.
Level: 1

Type: ERROR

Impact: Other

WCS-05349: Unexpected error occurred while launching Rename dialog

Cause: Unexpected error occurred while launching Rename dialog

Action: Contact Administrator or try again after some time.
Level: 1

Type: ERROR

Impact: Other

WCS-05349: Unexpected error occurred while launching Rename dialog

Cause: Unexpected error occurred while launching Rename dialog

Action: Contact Administrator or try again after some time.
Level: 1

Type: ERROR

Impact: Other

WCS-05350: Unexpected error occurred while launching Set Access dialog

Cause: Unexpected error occurred while launching Set Access dialog

Action: Contact Administrator or try again after some time.
Level: 1

Type: ERROR

Impact: Other

WCS-05350: Unexpected error occurred while launching Set Access dialog

Cause: Unexpected error occurred while launching Set Access dialog

Action: Contact Administrator or try again after some time.
Level: 1

Type: ERROR

Impact: Other

WCS-05351: Unexpected error occurred while unpublishing portal template(s)

Cause: Unexpected error occurred while unpublishing portal template(s)

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05351: Unexpected error occurred while unpublishing portal template(s)

Cause: Unexpected error occurred while unpublishing portal template(s)

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05352: Unexpected error occurred while unpublishing following portal template(s) {0}

Cause: Unexpected error occurred while unpublishing following portal template(s) {0}

Action: Contact Administrator or try again after some time.
Level: 1

Type: ERROR

Impact: Other

WCS-05352: Unexpected error occurred while unpublishing following portal template(s) {0}

Cause: Unexpected error occurred while unpublishing following portal template(s) {0}

Action: Contact Administrator or try again after some time.
Level: 1

Type: ERROR

Impact: Other

WCS-05353: Select at least one portal to copy data to template.

Cause: Select at least one portal to copy data to template.

Action: Select at least one portal to copy data to template.
Level: 1

Type: ERROR

Impact: Other

WCS-05353: Select at least one portal to copy data to template.

Cause: Select at least one portal to copy data to template.

Action: Select at least one portal to copy data to template.
Level: 1

Type: ERROR

Impact: Other

WCS-05354: Portal template metadata {0} not found.

Cause: Portal template metadata not found.

Action: Portal template metadata not found.
Level: 1

Type: ERROR

Impact: Other

WCS-05354: Portal template metadata {0} not found.

Cause: Portal template metadata not found.

Action: Portal template metadata not found.
Level: 1

Type: ERROR

Impact: Other

WCS-05355: Unable to set parent for one or more selected portal(s).

Cause: Failed to set parent for selected portal(s)

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05355: Unable to set parent for one or more selected portal(s).

Cause: Failed to set parent for selected portal(s)

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05356: The new parent {0} specified cannot be a child portal in the hierarchy of {1}.

Cause: The new parent {0} is a child portal in the hierarchy of {1}.

Action: Choose a different parent portal
Level: 1

Type: ERROR

Impact: Other

WCS-05356: The new parent {0} specified cannot be a child portal in the hierarchy of {1}.

Cause: The new parent {0} is a child portal in the hierarchy of {1}.

Action: Choose a different parent portal
Level: 1

Type: ERROR

Impact: Other

WCS-05357: The new parent is one of the selected portals for reparenting. Choose a different parent

Cause: The new parent {0} is one of the selected portal for reparenting.

Action: Choose a different parent portal
Level: 1

Type: ERROR

Impact: Other

WCS-05357: The new parent is one of the selected portals for reparenting. Choose a different parent

Cause: The new parent {0} is one of the selected portal for reparenting.

Action: Choose a different parent portal
Level: 1

Type: ERROR

Impact: Other

WCS-05358: The new parent and child portal cannot be same

Cause: The new parent and child portal specified are same.

Action: Choose a different parent portal
Level: 1

Type: ERROR

Impact: Other

WCS-05358: The new parent and child portal cannot be same

Cause: The new parent and child portal specified are same.

Action: Choose a different parent portal
Level: 1

Type: ERROR

Impact: Other

WCS-05359: The URL contains invalid characters

Cause: Value entered in the url is not proper

Action: Only the following characters are allowed: A-Z, a-z, 0-9, _
Level: 1

Type: ERROR

Impact: Other

WCS-05359: The URL contains invalid characters

Cause: Value entered in the url is not proper

Action: Only the following characters are allowed: A-Z, a-z, 0-9, _
Level: 1

Type: ERROR

Impact: Other

WCS-05360: The URL contains non-English characters

Cause: Non-ascii, multibyte characters entered in the pretty URL

Action: Only English names and ascii characters are supported
Level: 1

Type: ERROR

Impact: Other

WCS-05360: The URL contains non-English characters

Cause: Non-ascii, multibyte characters entered in the pretty URL

Action: Only English names and ascii characters are supported
Level: 1

Type: ERROR

Impact: Other

WCS-05361: Error occurred while fetching the custom attributes

Cause: An unexpected error occurred while fetching the custom attribute.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05361: Error occurred while fetching the custom attributes

Cause: An unexpected error occurred while fetching the custom attribute.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05362: The archive that you are trying to import is not a valid {0} archive. Refer to the Spaces diagnostic log file for more information or contact your system administrator.

Cause: The supplied file to import was not a valid archive.

Action: Retry the import operation with a valid archive.
Level: 1

Type: ERROR

Impact: Other

WCS-05362: The archive that you are trying to import is not a valid {0} archive. Refer to the Spaces diagnostic log file for more information or contact your system administrator.

Cause: The supplied file to import was not a valid archive.

Action: Retry the import operation with a valid archive.
Level: 1

Type: ERROR

Impact: Other

WCS-05363: The URL contains invalid characters. Permitted characters: A-Z, a-z, 0-9, _

Cause: Value entered in the url is not proper

Action: Only the following characters are allowed: A-Z, a-z, 0-9, _
Level: 1

Type: ERROR

Impact: Other

WCS-05363: The URL contains invalid characters. Permitted characters: A-Z, a-z, 0-9, _

Cause: Value entered in the url is not proper

Action: Only the following characters are allowed: A-Z, a-z, 0-9, _
Level: 1

Type: ERROR

Impact: Other

WCS-05364: The portal template name contains non-English characters

Cause: Non-ascii, multibyte characters entered in the pretty URL

Action: Only English names and ascii characters are supported
Level: 1

Type: ERROR

Impact: Other

WCS-05364: The portal template name contains non-English characters

Cause: Non-ascii, multibyte characters entered in the pretty URL

Action: Only English names and ascii characters are supported
Level: 1

Type: ERROR

Impact: Other

WCS-05365: Membership not changed for group {0}. You cannot manage the membership of this group because your own membership is granted through this group. Only direct members who have manage permission can manage the membership of groups.

Cause: Changing one's own membership in a portal is not allowed.

Action: Select users other than the current user to change their membership.
Level: 1

Type: WARNING

Impact: Other

WCS-05365: Membership not changed for group {0}. You cannot manage the membership of this group because your own membership is granted through this group. Only direct members who have manage permission can manage the membership of groups.

Cause: Changing one's own membership in a portal is not allowed.

Action: Select users other than the current user to change their membership.
Level: 1

Type: WARNING

Impact: Other

WCS-05366: Unexpected error occurred while fetching list of all portals

Cause: Unexpected error occurred while fetching list of all portals

Action: Unexpected error occurred while fetching list of all portals
Level: 1

Type: ERROR

Impact: Other

WCS-05366: Unexpected error occurred while fetching list of all portals

Cause: Unexpected error occurred while fetching list of all portals

Action: Unexpected error occurred while fetching list of all portals
Level: 1

Type: ERROR

Impact: Other

WCS-05367: Unable to display the list of portals you have access on due to unexpected errors. Try again after some time or contact administrator if the problem persists.

Cause: Unexpected error occurred while fetching list of all portals

Action: Unexpected error occurred while fetching list of all portals
Level: 1

Type: ERROR

Impact: Other

WCS-05367: Unable to display the list of portals you have access on due to unexpected errors. Try again after some time or contact administrator if the problem persists.

Cause: Unexpected error occurred while fetching list of all portals

Action: Unexpected error occurred while fetching list of all portals
Level: 1

Type: ERROR

Impact: Other

WCS-05368: Portal GUID not specified

Cause: The supplied portal GUID was null or blank.

Action: Specify a valid portal GUID that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-05368: Portal GUID not specified

Cause: The supplied portal GUID was null or blank.

Action: Specify a valid portal GUID that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-05369: Portal not found

Cause: The system could not find the specified portal.

Action: Specify a valid portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05369: Portal not found

Cause: The system could not find the specified portal.

Action: Specify a valid portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05370: Internal handler error

Cause: The internal handler for portal {0} failed.

Action: Refer to logs for more information and contact the administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05370: Internal handler error

Cause: The internal handler for portal {0} failed.

Action: Refer to logs for more information and contact the administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05371: The list of portal name passed was null

Cause: The list of portal names passed to fetch the metadata was empty.

Action: Pass a valid list of values.
Level: 1

Type: ERROR

Impact: Other

WCS-05371: The list of portal name passed was null

Cause: The list of portal names passed to fetch the metadata was empty.

Action: Pass a valid list of values.
Level: 1

Type: ERROR

Impact: Other

WCS-05372: The customizations available in portal template {1} were not copied to portal {0} since that process was interrupted.

Cause: Thread executing the customization document copy has been cancelled.

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05372: The customizations available in portal template {1} were not copied to portal {0} since that process was interrupted.

Cause: Thread executing the customization document copy has been cancelled.

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05373: The customizations available in portal template {1} were not copied to portal {0} since that process has timed-out.

Cause: Thread executing the customization document copy has been timed out

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05373: The customizations available in portal template {1} were not copied to portal {0} since that process has timed-out.

Cause: Thread executing the customization document copy has been timed out

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05374: The customizations available in portal template {1} were not copied to portal {0} due to unexpected errors.

Cause: Thread executing the customization document copy has failed to unexpected errors

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05374: The customizations available in portal template {1} were not copied to portal {0} due to unexpected errors.

Cause: Thread executing the customization document copy has failed to unexpected errors

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05375: The customizations available in portal {1} were not copied to portal template {0} since that process was interrupted.

Cause: Thread executing the customization document copy has been cancelled.

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05375: The customizations available in portal {1} were not copied to portal template {0} since that process was interrupted.

Cause: Thread executing the customization document copy has been cancelled.

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05376: The customizations available in portal {1} were not copied to portal template {0} since that process has timed-out.

Cause: Thread executing the customization document copy has been timed out

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05376: The customizations available in portal {1} were not copied to portal template {0} since that process has timed-out.

Cause: Thread executing the customization document copy has been timed out

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05377: The customizations available in portal {1} were not copied to portal template {0} due to unexpected.

Cause: Thread executing the customization document copy has failed to unexpected errors

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05377: The customizations available in portal {1} were not copied to portal template {0} due to unexpected.

Cause: Thread executing the customization document copy has failed to unexpected errors

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05378: Unable to launch About Portal Template dialog.

Cause: Unable to launch About Portal Template dialog.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-05378: Unable to launch About Portal Template dialog.

Cause: Unable to launch About Portal Template dialog.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-05379: Unable to perform the operation on multiple portal templates.

Cause: Unable to perform the operation on multiple portal templates.

Action: Select a single portal template only and retry the operation
Level: 1

Type: ERROR

Impact: Other

WCS-05379: Unable to perform the operation on multiple portal templates.

Cause: Unable to perform the operation on multiple portal templates.

Action: Select a single portal template only and retry the operation
Level: 1

Type: ERROR

Impact: Other

WCS-05380: Select at least one portal template to continue the operation.

Cause: Select at least one portal template to continue.

Action: Select at least one portal template to continue.
Level: 1

Type: ERROR

Impact: Other

WCS-05380: Select at least one portal template to continue the operation.

Cause: Select at least one portal template to continue.

Action: Select at least one portal template to continue.
Level: 1

Type: ERROR

Impact: Other

WCS-05381: User {0} does not have permission to view portal {1}.

Cause: User {0} does not have permission to view portal {1}.

Action: User {0} does not have permission to view portal {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05381: User {0} does not have permission to view portal {1}.

Cause: User {0} does not have permission to view portal {1}.

Action: User {0} does not have permission to view portal {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05382: User {0} does not have permission to manage portal {1}.

Cause: User {0} does not have permission to manage portal {1}.

Action: User {0} does not have permission to manage portal {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05382: User {0} does not have permission to manage portal {1}.

Cause: User {0} does not have permission to manage portal {1}.

Action: User {0} does not have permission to manage portal {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05383: User {0} does not have the permission to create portal {1}.

Cause: User {0} does not have the permission to create the portal.

Action: User {0} does not have the permission to create the portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05383: User {0} does not have the permission to create portal {1}.

Cause: User {0} does not have the permission to create the portal.

Action: User {0} does not have the permission to create the portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05384: User {0} does not have the permission to view the portal template {1}.

Cause: User {0} does not have the permission to view the portal template {1}.

Action: User {0} does not have the permission to view the portal template {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05384: User {0} does not have the permission to view the portal template {1}.

Cause: User {0} does not have the permission to view the portal template {1}.

Action: User {0} does not have the permission to view the portal template {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05385: User {0} does not have permission to create portal template.

Cause: User {0} does not have permission to create portal template.

Action: User {0} does not have permission to create portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05385: User {0} does not have permission to create portal template.

Cause: User {0} does not have permission to create portal template.

Action: User {0} does not have permission to create portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05386: User {0} does not have permission to manage portal template {1}.

Cause: User {0} does not have permission to manage portal template {1}.

Action: User {0} does not have permission to manage portal template {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05386: User {0} does not have permission to manage portal template {1}.

Cause: User {0} does not have permission to manage portal template {1}.

Action: User {0} does not have permission to manage portal template {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05387: User {0} does not have permission to edit portal {1}.

Cause: User {0} does not have permission to edit portal {1}.

Action: User {0} does not have permission to edit portal {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05387: User {0} does not have permission to edit portal {1}.

Cause: User {0} does not have permission to edit portal {1}.

Action: User {0} does not have permission to edit portal {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05388: Unexpected error occurred while creating portal {0} from portal template {1}. Try again after some time. If the problem persists, contact Administrator

Cause: Unexpected error occurred while creating portal {0} from portal template {1}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05388: Unexpected error occurred while creating portal {0} from portal template {1}. Try again after some time. If the problem persists, contact Administrator

Cause: Unexpected error occurred while creating portal {0} from portal template {1}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05389: User {0} does not have permission to manage security of portal {1}.

Cause: User {0} does not have permission to manage security of portal {1}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05389: User {0} does not have permission to manage security of portal {1}.

Cause: User {0} does not have permission to manage security of portal {1}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05390: Unexpected error occurred while deleting portal {0}. Try again after some time. If the problem persists, contact Administrator.

Cause: Unexpected error occurred while deleting portal {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05390: Unexpected error occurred while deleting portal {0}. Try again after some time. If the problem persists, contact Administrator.

Cause: Unexpected error occurred while deleting portal {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05391: Unexpected error occurred while creating portal template {1} from portal {0}. Try again after some time. If the problem persists, contact Administrator.

Cause: Unexpected error occurred while creating portal template {1} from portal {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05391: Unexpected error occurred while creating portal template {1} from portal {0}. Try again after some time. If the problem persists, contact Administrator.

Cause: Unexpected error occurred while creating portal template {1} from portal {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05392: Unexpected error occurred while deleting portal template {0}. Try again after some time. If the problem persists, contact Administrator.

Cause: An unexpected error occurred while deleting portal template {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05392: Unexpected error occurred while deleting portal template {0}. Try again after some time. If the problem persists, contact Administrator.

Cause: An unexpected error occurred while deleting portal template {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05393: User {0} is not authorized to refresh Portal cache.

Cause: User {0} is not authorized to refresh Portal cache.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05393: User {0} is not authorized to refresh Portal cache.

Cause: User {0} is not authorized to refresh Portal cache.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05394: An unexpected error occurred while creating portal preference metadata.

Cause: An unexpected while creating portal preference metadata.

Action: Contact the administrator or try again later.
Level: 1

Type: ERROR

Impact: Other

WCS-05394: An unexpected error occurred while creating portal preference metadata.

Cause: An unexpected while creating portal preference metadata.

Action: Contact the administrator or try again later.
Level: 1

Type: ERROR

Impact: Other

WCS-05395: User {0} does not have permission to view portal {0}, the portal is not discoverable, and self-subscription is not enabled.

Cause: User {0} does not have permission to view portal {0}, the portal is not discoverable, and self-subscription is not enabled.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05395: User {0} does not have permission to view portal {0}, the portal is not discoverable, and self-subscription is not enabled.

Cause: User {0} does not have permission to view portal {0}, the portal is not discoverable, and self-subscription is not enabled.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05396: An unexpected error occurred while trying to drop the role {0} in portal {1}.

Cause: An unexpected error occurred while trying to drop the role {0} in portal {1}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05396: An unexpected error occurred while trying to drop the role {0} in portal {1}.

Cause: An unexpected error occurred while trying to drop the role {0} in portal {1}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05397: An unexpected error occurred while trying to set welcome message {0} for invited non-member in portal {1}.

Cause: An unexpected error occurred while trying to set welcome message {0} for invited non-member in portal {1}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05397: An unexpected error occurred while trying to set welcome message {0} for invited non-member in portal {1}.

Cause: An unexpected error occurred while trying to set welcome message {0} for invited non-member in portal {1}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05398: An unexpected error occurred while trying to set welcome message {0} for invited member in portal {1}.

Cause: An unexpected error occurred while trying to set welcome message {0} for invited member in portal {1}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05398: An unexpected error occurred while trying to set welcome message {0} for invited member in portal {1}.

Cause: An unexpected error occurred while trying to set welcome message {0} for invited member in portal {1}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05399: An unexpected error occurred while trying to set add member message {0} in portal {1}.

Cause: An unexpected error occurred while trying to set add member message {0} in portal {1}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05399: An unexpected error occurred while trying to set add member message {0} in portal {1}.

Cause: An unexpected error occurred while trying to set add member message {0} in portal {1}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05400: An unexpected error occurred while trying to get portal members.

Cause: An unexpected error occurred while trying to get portal members.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05400: An unexpected error occurred while trying to get portal members.

Cause: An unexpected error occurred while trying to get portal members.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05401: Changing role for invited members, is not supported.

Cause: Changing role for invited members, is not supported.

Action: For changing the role of Invited Members, delete the existing invite for the member and invite the member again with the new role.
Level: 1

Type: WARNING

Impact: Other

WCS-05401: Changing role for invited members, is not supported.

Cause: Changing role for invited members, is not supported.

Action: For changing the role of Invited Members, delete the existing invite for the member and invite the member again with the new role.
Level: 1

Type: WARNING

Impact: Other

WCS-05402: Unexpected error occurred while deleting the customization documents for portal {0}.

Cause: Unexpected error occurred while deleting the customization documents for portal {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05402: Unexpected error occurred while deleting the customization documents for portal {0}.

Cause: Unexpected error occurred while deleting the customization documents for portal {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05403: Unexpected error occurred while getting Parent Display Name for portal {0} due to {1}.

Cause: Unexpected error occurred while getting Parent Display Name for portal {0} due to {1}.

Action: Contact Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05403: Unexpected error occurred while getting Parent Display Name for portal {0} due to {1}.

Cause: Unexpected error occurred while getting Parent Display Name for portal {0} due to {1}.

Action: Contact Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05404: Unexpected error occurred while getting URL of parent portal for portal {0} due to {1}.

Cause: Unexpected error occurred while getting URL of parent portal for portal {0} due to {1}.

Action: Contact Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05404: Unexpected error occurred while getting URL of parent portal for portal {0} due to {1}.

Cause: Unexpected error occurred while getting URL of parent portal for portal {0} due to {1}.

Action: Contact Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05405: Unexpected error occurred while deleting the package containing assets for portal {0}.

Cause: Unexpected error occurred while deleting the package containing generic-site-resources documents for portal {0}.

Action: Contact Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05405: Unexpected error occurred while deleting the package containing assets for portal {0}.

Cause: Unexpected error occurred while deleting the package containing generic-site-resources documents for portal {0}.

Action: Contact Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05406: Unable to create portal as a portal with the URL or display name {0} already exists.

Cause: A portal with the specified URL or display name already exists.

Action: Specify a unique UURL or display name for the portal.
Level: 1

Type: WARNING

Impact: Other

WCS-05406: Unable to create portal as a portal with the URL or display name {0} already exists.

Cause: A portal with the specified URL or display name already exists.

Action: Specify a unique UURL or display name for the portal.
Level: 1

Type: WARNING

Impact: Other

WCS-05407: Unable to create portal as portal name is a reserved keyword. One of: {0}

Cause: The portal name specified was a reserved keyword.

Action: Specify a valid alphanumeric name for the portal which excludes the following reserved keywords: webcenter, pages, page, Spaces, Space, group, groups, Space, Spaces, webcenter Space, webcenter Spaces, webcenter Portal, WebCenter Portal, WebCenter Portal Spaces, portal, webcenter administration, my Spaces, admin, last.
Level: 1

Type: ERROR

Impact: Other

WCS-05407: Unable to create portal as portal name is a reserved keyword. One of: {0}

Cause: The portal name specified was a reserved keyword.

Action: Specify a valid alphanumeric name for the portal which excludes the following reserved keywords: webcenter, pages, page, Spaces, Space, group, groups, Space, Spaces, webcenter Space, webcenter Spaces, webcenter Portal, WebCenter Portal, WebCenter Portal Spaces, portal, webcenter administration, my Spaces, admin, last.
Level: 1

Type: ERROR

Impact: Other

WCS-05408: Unable to create portal as portal display name is a reserved keyword. One of: {0}

Cause: The portal display name specified was a reserved keyword

Action: Specify a valid alphanumeric name for the portal display name which excludes the following reserved keywords: webcenter, pages, page, Spaces, Space, group, groups, Space, Spaces, webcenter Space, webcenter Spaces, webcenter Portal, WebCenter Portal, WebCenter Portal Spaces, portal, webcenter administration, my Spaces, admin, last.
Level: 1

Type: ERROR

Impact: Other

WCS-05408: Unable to create portal as portal display name is a reserved keyword. One of: {0}

Cause: The portal display name specified was a reserved keyword

Action: Specify a valid alphanumeric name for the portal display name which excludes the following reserved keywords: webcenter, pages, page, Spaces, Space, group, groups, Space, Spaces, webcenter Space, webcenter Spaces, webcenter Portal, WebCenter Portal, WebCenter Portal Spaces, portal, webcenter administration, my Spaces, admin, last.
Level: 1

Type: ERROR

Impact: Other

WCS-05409: Simulated error condition during creation of portal {0} for internal test purposes.

Cause: Simulated error condition during creation of portal {0} for internal test purposes.

Action: This is just for negative tests.
Level: 1

Type: ERROR

Impact: Other

WCS-05409: Simulated error condition during creation of portal {0} for internal test purposes.

Cause: Simulated error condition during creation of portal {0} for internal test purposes.

Action: This is just for negative tests.
Level: 1

Type: ERROR

Impact: Other

WCS-05410: Unexpected error occurred while deleting the portal template(s) {0}

Cause: Unexpected error occurred while deleting following portal template(s) {0}

Action: Contact Administrator or try again after some time.
Level: 1

Type: ERROR

Impact: Other

WCS-05410: Unexpected error occurred while deleting the portal template(s) {0}

Cause: Unexpected error occurred while deleting following portal template(s) {0}

Action: Contact Administrator or try again after some time.
Level: 1

Type: ERROR

Impact: Other

WCS-05411: Couldn''t get the first accessible page for portal {0} due to {1}.

Cause: Error in getting the first accessible page for the portal.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05411: Couldn''t get the first accessible page for portal {0} due to {1}.

Cause: Error in getting the first accessible page for the portal.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05412: Unexpected error occurred in setting {0} as parent of portal {1} due to {2}.

Cause: Error in setting the parent portal.

Action: Contact the application administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05412: Unexpected error occurred in setting {0} as parent of portal {1} due to {2}.

Cause: Error in setting the parent portal.

Action: Contact the application administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05413: Unexpected error while setting the parent to {0} due to {1}.

Cause: Error in setting the parent and security parent for the scope

Action: Contact the application administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05413: Unexpected error while setting the parent to {0} due to {1}.

Cause: Error in setting the parent and security parent for the scope

Action: Contact the application administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05414: User {0} is not authorized to generate site maps for this site.

Cause: User {0} is not authorized to generate site maps for this site.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05414: User {0} is not authorized to generate Sitemaps for this site.

Cause: User {0} is not authorized to generate Sitemaps for this site.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05415: Unexpected error while getting the site map index.

Cause: Error in getting the site map index.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05415: Unexpected error while getting the sitemap index.

Cause: Error in getting the sitemap index.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05416: Unexpected error while getting the site map for portal {0}.

Cause: Error in getting the portal site map.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05416: Unexpected error while getting the sitemap for portal {0}.

Cause: Error in getting the portal sitemap.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05417: Unexpected error while generating the site map.

Cause: Error while generating the site map.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05417: Unexpected error while generating the sitemap.

Cause: Error while generating the sitemap.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05418: Unexpected error while generating the site map for portal {0}.

Cause: Error while generating the portal site map.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05418: Unexpected error while generating the sitemap for portal {0}.

Cause: Error while generating the portal sitemap.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05419: Unexpected error while updating the site map for portal {0}.

Cause: Error while updating the site map.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05419: Unexpected error while updating the sitemap for portal {0}.

Cause: Error while updating the sitemap.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05420: Unexpected error occurred while deleting the portal entry from default portal metadata due to {0}.

Cause: Error while deleting the portal from default portal metadta.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05420: Unexpected error occured while deleting the portal entry from default portal metadata due to {0}.

Cause: Error while deleting the portal from default portal metadta.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05421: Unexpected error occurred while renaming the portal entry from default portal metadata due to {0}.

Cause: Error while renaming the portal from default portal metadta.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05421: Unexpected error occured while renaming the portal entry from default portal metadata due to {0}.

Cause: Error while renaming the portal from default portal metadta.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05422: Error fetching parent space for space {0} due to {1}

Cause: Error occurred while fetching parent space.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05422: Error fetching parent space for space {0} due to {1}

Cause: Error occured while fetching parent space.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05423: Unexpected error occurred while fetching the Portal Manager list for space{0} due to {1}

Cause: Error occurred while fetching the list of Portal Managers.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05423: Unexpected error occured while fetching the moderator list for space{0} due to {1}

Cause: Error occured while fetching the list of moderators.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05424: Attribute value not specified

Cause: Attribute value cannot be null or blank.

Action: Please enter a valid value.
Level: 1

Type: WARNING

Impact: Other

WCS-05425: Attribute name not specified

Cause: Attribute name cannot be null or blank.

Action: Please enter a valid name.
Level: 1

Type: WARNING

Impact: Other

WCS-05426: Failed to update last active time for user guid {0} with exception {1}.

Cause: Unexpected error while updating last active time for user guid {0} due to exception {1}.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05427: Exceptions occurred while revoking role {1} for user {0} due to failures in some of the services {2}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05428: Unexpected error occurred while revoking roles for member {0}. Refer to the diagnostic WebCenter Portal log file for more information or contact your system administrator.

Cause: Unexpected error occurred while deleting role(s).

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05429: User {0} cannot be removed from portal {1} because {0} is the only member assigned to the Portal Manager role in the portal.

Cause: You cannot remove a member from a portal if that member is the sole Portal Manager of the portal.

Action: Assign another member as the portal manager, then proceed to remove the current user.
Level: 1

Type: WARNING

Impact: Other

WCS-05430: Cannot delete portal {0} as the Portal API cannot find this portal.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05431: Cannot create portal {0} due to error encountered when creating Portal object.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05432: Cannot create portal {0} due to error encountered when updating Portal object.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05433: Cannot create portal {0} due to error encountered when updating Portal object - {0}.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05434: User {0} does not have the privileges required for deployment operation on Portals. Verify that the user has ''Create Portal'' permission while performing the deployment operation.

Cause: Verify that the user has Create Portal permission while performing the deployment operation.

Action: Try performing the operation as an administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05435: User {0} does not have the privileges required for deployment operation on portal {1}. Verify that the user has ''Manage Portal'' permission while performing the deployment operation.

Cause: Verify that the user has Manage Portal permission while performing the deployment operation.

Action: Try performing the operation as an administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05436: User {0} does not have the privileges required for deployment operation on Portals. Verify that the user has ''Deploy'' permission while performing the deployment operation.

Cause: Verify that the user has Deploy permission while performing the deployment operation.

Action: Try performing the operation as an administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05437: User {0} does not have the privileges required for propagation operation on portal {1}. Verify that the user has ''Manage Portal'' permission while performing the propagation operation.

Cause: Verify that the user has Manage Portal permission while performing the propagation operation.

Action: Try performing the operation as an administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05438: User {0} does not have the privileges required for propagation operation on Portals. Verify that the user has ''Deploy'' permission while performing the propagation operation.

Cause: Verify that the user has Deploy permission while performing the propagation operation.

Action: Try performing the operation as an administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05439: User {0} does not have the privileges required for import operation on Portals. Verify that the user has ''Create Portal'' permission while performing the import operation.

Cause: Verify that the user has Create Portal permission while performing the import operation.

Action: Try performing the operation as an administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05440: User {0} does not have the privileges required for import operation on Portals. Verify that the user has ''Deploy'' permission while performing the import operation to be able to import the shared assets.

Cause: Verify that the user has Deploy permission while performing the import operation to be able to import the shared assets.

Action: Try performing the operation as an administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05441: User {0} does not have the privileges required for this operation on portal {1}. Verify that the user has ''Manage Portal'' permission while performing the export, deployment or propagation operation.

Cause: Verify that the user has Manage Portal permission while performing the export, deployment or propagation operation.

Action: Try performing the operation as an administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05442: User {0} does not have the privileges required for this operation on Portals. Verify that the user has ''Deploy'' permission while performing the deployment or propagation operation to be able to export the shared assets.

Cause: Verify that the user has Deploy permission while performing the deployment or propagation operation to be able to export the shared assets.

Action: Try performing the operation as an administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05443: User {0} does not have the privileges required for this operation on Portal Templates.

Cause: Check if the user has required permission on Portal Templates for performing lifecycle operations.

Action: Try performing the operation as an administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05444: User {0} does not have the privileges required for this operation on the WebCenter Portal Server application.

Cause: Check if the user has required permission on WebCenter Portal Server application for performing lifecycle operations.

Action: Try performing the operation as an administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05445: User {0} does not have the privileges required for import operation on portal {1}. Verify that the user has ''Manage Portal'' permission while performing the import operation.

Cause: Verify that the user has Manage Portal permission while performing the import operation.

Action: Try performing the operation as an administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05446: List of Members cannot be empty

Cause: Members List passed is empty.

Action: Please enter a valid value.
Level: 1

Type: WARNING

Impact: Other

WCS-05447: Role Name cannot be empty

Cause: Role Name is empty.

Action: Please enter a valid Role Name.
Level: 1

Type: WARNING

Impact: Other

WCS-05448: Base Role Name cannot be empty

Cause: Base Role Name is empty.

Action: Please enter a valid Base Role Name.
Level: 1

Type: WARNING

Impact: Other

WCS-05449: Portal Image URL cannot be empty

Cause: Portal Image URL is empty.

Action: Please enter a valid Image URL.
Level: 1

Type: WARNING

Impact: Other

WCS-05450: Attribute type not specified

Cause: Attribute type cannot be null or blank.

Action: Please enter a valid type.
Level: 1

Type: WARNING

Impact: Other

WCS-05451: New Portal name for rename not specified

Cause: New Portal Name cannot be null or blank.

Action: Please enter a valid Portal name.
Level: 1

Type: WARNING

Impact: Other

WCS-05452: Unexpected error occurred while performing the method {0}. Contact Administrator and check the logs for more details

Cause: Runtime error occurred while performing method {0}.

Action: Contact Administrator and check logs.
Level: 1

Type: WARNING

Impact: Other

WCS-05701: Deleting portal {0} failed

Cause: WebService API failed to execute deleting web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05701: Deleting portal {0} failed

Cause: WebService API failed to execute deleting web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05702: Creating portal {0} failed

Cause: WebService API failed to execute create web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05702: Creating portal {0} failed

Cause: WebService API failed to execute create web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05703: An error occurred while revoking the roles {1} for users in portal {0}

Cause: WebService API failed to execute revoke role web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05703: An error occurred while revoking the roles {1} for users in portal {0}

Cause: WebService API failed to execute revoke role web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05704: An error occurred while granting roles for {1} users in portal {0}

Cause: WebService API failed to execute grant role web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05704: An error occurred while granting roles for {1} users in portal {0}

Cause: WebService API failed to execute grant role web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05705: Getting portal template {0} metadata failed

Cause: WebService API failed to execute get portal template metadata web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05705: Getting portal template {0} metadata failed

Cause: WebService API failed to execute get portal template metadata web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05706: Getting portal metadata {0} failed

Cause: WebService API failed to execute get portal metadata web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05706: Getting portal metadata {0} failed

Cause: WebService API failed to execute get portal metadata web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05707: Getting portals for search string {0} failed

Cause: WebService API failed to execute get spaces web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05707: Getting portals for search string {0} failed

Cause: WebService API failed to execute get spaces web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05708: Getting portal templates for search string {0} failed

Cause: WebService API failed to execute get template web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05708: Getting portal templates for search string {0} failed

Cause: WebService API failed to execute get template web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05709: Setting the Custom Attributes for scope {0} failed

Cause: WebService API failed to execute Custom Attributes.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05709: Setting the Custom Attributes for scope {0} failed

Cause: WebService API failed to execute Custom Attributes.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05710: An error occurred while attempting to retrieve spaces web service endpoint configured in connections.xml of caller application

Cause: Unable to retrieve spaces web service endpoint configured in caller applications connections.xml

Action: Please check spaces web service endpoint configured in connections.xml
Level: 1

Type: ERROR

Impact: Other

WCS-05710: An error occurred while attempting to retrieve spaces web service endpoint configured in connections.xml of caller application

Cause: Unable to retrieve spaces web service endpoint configured in caller applications connections.xml

Action: Please check spaces web service endpoint configured in connections.xml
Level: 1

Type: ERROR

Impact: Other

WCS-05711: One of the arguments passed to API call {0} is null

Cause: A null argument was passed to an API call

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05711: One of the arguments passed to API call {0} is null

Cause: A null argument was passed to an API call

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05712: No portal name is provided

Cause: Portal name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05712: No portal name is provided

Cause: Portal name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05713: No portal template name is provided

Cause: Portal template name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05713: No portal template name is provided

Cause: Portal template name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05714: No portal user name is provided

Cause: Portal user name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05714: No portal user name is provided

Cause: Portal user name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05715: No portal role name is provided

Cause: Portal role name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05715: No portal role name is provided

Cause: Portal role name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05716: No portal custom attribute name is provided

Cause: Portal custom attribute name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05716: No portal custom attribute name is provided

Cause: Portal custom attribute name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05717: No portal custom attribute value is provided

Cause: Portal custom attribute value is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05717: No portal custom attribute value is provided

Cause: Portal custom attribute value is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05718: Error while setting the new end point for the space web services

Cause: Portal web services client already has an endpoint {0}

Action: It cannot be overridden at the runtime. Try setting it in connections.xml and restarting the application
Level: 1

Type: ERROR

Impact: Other

WCS-05718: Error while setting the new end point for the space web services

Cause: Portal web services client already has an endpoint {0}

Action: It cannot be overridden at the run-time. Try setting it in connections.xml and restarting the application
Level: 1

Type: ERROR

Impact: Other

WCS-05719: Portal web service client is null

Cause: Portal web service client is null

Action: You need to set the context for the client and then initialize it
Level: 1

Type: ERROR

Impact: Other

WCS-05719: Portal web service client is null

Cause: Portal web service client is null

Action: You need to set the context for the client and then initialize it
Level: 1

Type: ERROR

Impact: Other

WCS-05720: An unexpected error occurred while instantiating space web services client

Cause: Unable to create an instance of GroupSpaceWSClient

Action: Please verify the context parameters or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05720: An unexpected error occurred while instantiating space web services client

Cause: Unable to create an instance of GroupSpaceWSClient

Action: Please verify the context parameters or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05721: An error occurred when user {0} tried to accept invite for portal {2} with role {1}

Cause: Failed to execute acceptance of portal invite

Action: Check the parameters being passed to the acceptInvite API or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05721: An error occurred when user {0} tried to accept invite for portal {2} with role {1}

Cause: Failed to execute acceptance of portal invite

Action: Check the parameters being passed to the acceptInvite API or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05722: An error occurred when user {0} tried to reject the invite for portal {1}

Cause: Failed to execute rejection of portal invite

Action: Check the parameters being passed to the rejectInvite API or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05722: An error occurred when user {0} tried to reject the invite for portal {1}

Cause: Failed to execute rejection of portal invite

Action: Check the parameters being passed to the rejectInvite API or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05723: An error occurred while fetching the roles for portal {0}

Cause: An error occurred while fetching the roles for portal {0}

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05723: An error occurred while fetching the roles for portal {0}

Cause: An error occurred while fetching the roles for portal {0}

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05724: An error occurred while inviting {0} members to portal {1}

Cause: An error occurred while inviting the members to portal {1}

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05724: An error occurred while inviting {0} members to portal {1}

Cause: An error occurred while inviting the members to portal {1}

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05725: An error occurred while creating the portal template {0} based on portal {1}

Cause: An error occurred while creating the portal template {0}

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05725: An error occurred while creating the portal template {0} based on portal {1}

Cause: An error occurred while creating the portal template {0}

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05726: An error occurred while fetching the roles for portal template {0}

Cause: An error occurred while fetching the roles for portal template {0}

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05726: An error occurred while fetching the roles for portal template {0}

Cause: An error occurred while fetching the roles for portal template {0}

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05727: The Service ID {0}, is invalid.

Cause: An error occurred while fetching the RSS Feed URL for the Service ID, {0}.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05727: The Service ID {0}, is invalid.

Cause: An error occurred while fetching the RSS Feed URL for the Service ID, {0}.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05728: An error occurred while checking if a login user {0} is a member of portal {1}

Cause: An error occurred while checking if a login user {1} is a member of portal {0}

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05728: An error occurred while checking if a login user {0} is a member of portal {1}

Cause: An error occurred while checking if a login user {1} is a member of portal {0}

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05729: Deleting portal template {0} failed

Cause: WebService API failed to execute deleting web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05729: Deleting portal template {0} failed

Cause: WebService API failed to execute deleting web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05730: Search on portals for search string {0} failed

Cause: WebService API failed to execute search for portals.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05730: Search on portals for search string {0} failed

Cause: WebService API failed to execute search for portals.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05731: Creation of role {0} failed in portal {1}

Cause: WebService API failed to execute create role for portals.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05731: Creation of role {0} failed in portal {1}

Cause: WebService API failed to execute create role for portals.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05732: Dropping of role {0} failed in portal {1}

Cause: WebService API failed to execute drop role for portals.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05732: Dropping of role {0} failed in portal {1}

Cause: WebService API failed to execute drop role for portals.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05733: Failed to get role information for identity {0} in portal {1}

Cause: WebService API failed to get role information.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05733: Failed to get role information for identity {0} in portal {1}

Cause: WebService API failed to get role information.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05734: Failed to get member information for portal {0}

Cause: WebService API failed to get member information.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05734: Failed to get member information for portal {0}

Cause: WebService API failed to get member information.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05735: Search on portal templates for search string {0} failed

Cause: WebService API failed to execute search for portal template.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05735: Search on portal templates for search string {0} failed

Cause: WebService API failed to execute search for portal template.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05736: No image URL is provided

Cause: Image URL is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05736: No image URL is provided

Cause: Image URL is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05737: Unexpected error occurred in preparing image URL {0}

Cause: An error occurred in preparing image URL

Action: Make sure that the URL passed is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05737: Unexpected error occurred in preparing image URL {0}

Cause: An error occurred in preparing image URL

Action: Make sure that the URL passed is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05738: Failed to grant role for some members in portal {0}.

Cause: WebService API failed to execute grant role web service call for some or all members. This may be because these members already have provided role grants.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-05739: An error occurred while revoking roles for some users in portal {0}.

Cause: WebService API failed to execute revoke role web service call for some members.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05900: Unexpected error occurred while performing operation.

Cause: Error occurred due to unknown cause

Action: Try the operation again or contact oracle support
Level: 1

Type: ERROR

Impact: Other

WCS-05900: Unexpected error occurred while performing operation.

Cause: Error occurred due to unknown cause

Action: Try the operation again or contact oracle support
Level: 1

Type: ERROR

Impact: Other

WCS-06001: JCR session leak: leaked {0} sessions during {1} request to URI {2}.

Cause: JCR sessions have not been returned to the pool after the request ended.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-06002: Connection "{0}" is not a content repository connection.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06004: Error getting default IdcContext for connection "{0}": {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06004: Error getting default IdcContext for connection "{0}": {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06005: Error getting admin IdcContext for connection "{0}": {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06005: Error getting admin IdcContext for connection "{0}": {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06006: Error getting IdcClient for connection "{0}": {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06006: Error getting IdcClient for connection "{0}": {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06007: Invalid maximum binary cache entry size: {0}. The value must be a number.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06007: Invalid maximum binary cache entry size: {0}. The value must be a number.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06008: The connection "{0}" is not an Oracle Content Server connection.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06008: The connection "{0}" is not an Oracle Content Server connection.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06009: There was an error looking up connection {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06009: There was an error looking up connection {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06902: Incomplete repository connection, cannot login.

Cause: The repository configuration details are not valid and a classpath issue prevented the loading of the underlying JCR repository.

Action: Verify that all the configuration parameters are correct and check the message from the underlying exception.
Level: 1

Type: WARNING

Impact: Other

WCS-06902: Incomplete repository connection, cannot login.

Cause: The repository configuration details are not valid and a classpath issue prevented the loading of the underlying JCR repository.

Action: Verify that all the configuration parameters are correct and check the message from the underlying exception.
Level: 1

Type: WARNING

Impact: Other

WCS-06905: Credentials for connection {0} not found using External Application Identifier {1}.

Cause: An attempt to fetch user credentials failed. User credentials may not have been provisioned or the external application configuration may be incorrect.

Action: Verify the external application configuration. If necessary, provision credentials for the user.
Level: 1

Type: WARNING

Impact: Other

WCS-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-06906: invalid credentials for connection {0} using External Application Identifier {1}

Cause: An attempt to log in using the provisioned credentials failed. The user's credentials for this connection might have been changed or the external application configuration might have been incorrect.

Action: If the provisioned credentials for the given user are not valid, then those credentials must be provisioned again. It might also be necessary to verify the external application configuration.
Level: 1

Type: WARNING

Impact: Other

WCS-06908: JCR Repository creation failure.{0}

Cause: A JCR repository instance could not be created from the parameters provided.

Action: Check the configuration parameters, and retry.
Level: 1

Type: WARNING

Impact: Other

WCS-06908: JCR Repository creation failure.{0}

Cause: A JCR repository instance could not be created from the parameters provided.

Action: Check the configuration parameters, and retry.
Level: 1

Type: WARNING

Impact: Other

WCS-06910: External Application Definition not found using External Application Identifier {0}

Cause: An attempt to fetch user credentials failed. The External Application ID is incorrect.

Action: Verify that the External Application definition has been created for this connection.
Level: 1

Type: WARNING

Impact: Other

WCS-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-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-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-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-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-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-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-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-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: runtime error obtaining content repository

Cause: An unexpected runtime exception occurred.

Action: Use the associated runtime 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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-07022: After fail-over, failed to get the item {0} from the repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07023: Please refresh to see the latest content (View > Refresh Content).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07023: Please refresh to see the latest content (View > Refresh Content).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07024: Please refresh to see the latest content (View > Refresh Content). You may need to navigate up the folder hierarchy before refreshing.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07024: Please refresh to see the latest content (View > Refresh Content). You may need to navigate up the folder hierarchy before refreshing.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07025: Unable to rename the selected document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-07061: The document is checked out by another user.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07062: The document is checked out by user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07062: The document is checked out by user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07063: The document is not checked out.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-07072: The destination cannot be a child folder of the source folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07073: Unable to display item properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07073: Unable to display item properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07074: Unable to save item properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07074: Unable to save item properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07075: No transfer data found for data flavor {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07075: No transfer data found for data flavor {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07076: No value found for task flow parameter {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07076: No value found for task flow parameter {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07077: An error occurred while adding the content presenter task flow to the page.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07077: An error occurred while adding the content presenter task flow to the page.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07078: The class method ''{0}.{1}'' cannot be called with a null or empty argument ''{2}''.

Cause: The specified method call cannot be called with the specified argument with value of null.

Action: Ensure the specified argument has a non-null value.
Level: 1

Type: ERROR

Impact: Other

WCS-07078: The class method ''{0}.{1}'' cannot be called with a null or empty argument ''{2}''.

Cause: The specified method call cannot be called with the specified argument with value of null.

Action: Ensure the specified argument has a non-null value.
Level: 1

Type: ERROR

Impact: Other

WCS-07079: Datasource type ''{0}'' was expected but found ''{1}''.

Cause: The configured datasource type did not match the expected datasource type.

Action: Correct the presenter configuration to the expected datasource type.
Level: 1

Type: ERROR

Impact: Other

WCS-07079: Datasource type ''{0}'' was expected but found ''{1}''.

Cause: The configured datasource type did not match the expected datasource type.

Action: Correct the presenter configuration to the expected datasource type.
Level: 1

Type: ERROR

Impact: Other

WCS-07080: Error retrieving node(s).

Cause: An error was encountered retrieving node(s).

Action: Please contact a system administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-07080: Error retrieving node(s).

Cause: An error was encountered retrieving node(s).

Action: Please contact a system administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-07081: Error saving Content Presenter Configuration.

Cause: An error was encountered saving the specified configuration document.

Action: Please contact a system administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-07081: Error saving Content Presenter Configuration.

Cause: An error was encountered saving the specified configuration document.

Action: Please contact a system administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-07082: Query expression must be a valid, non-empty expression.

Cause: The specified query expression was invalid.

Action: Review the specified query expression and correct it.
Level: 1

Type: ERROR

Impact: Other

WCS-07082: Query expression must be a valid, non-empty expression.

Cause: The specified query expression was invalid.

Action: Review the specified query expression and correct it.
Level: 1

Type: ERROR

Impact: Other

WCS-07083: The datasource type ''{0}'' requires ''{1}'' to be set.

Cause: The specified datasource type is not consistent with the datasource state.

Action: Specific datasource types require different parameters to be set. Please resolve this situation.
Level: 1

Type: ERROR

Impact: Other

WCS-07083: The datasource type ''{0}'' requires ''{1}'' to be set.

Cause: The specified datasource type is not consistent with the datasource state.

Action: Specific datasource types require different parameters to be set. Please resolve this situation.
Level: 1

Type: ERROR

Impact: Other

WCS-07084: Invalid datasource type ''{0}''. Valid datasource types:{1}.

Cause: The specified datasource type was invalid.

Action: Correct the specified datasource type to one of the examples provided in the error message.
Level: 1

Type: ERROR

Impact: Other

WCS-07084: Invalid datasource type ''{0}''. Valid datasource types:{1}.

Cause: The specified datasource type was invalid.

Action: Correct the specified datasource type to one of the examples provided in the error message.
Level: 1

Type: ERROR

Impact: Other

WCS-07085: The configuration {0} is required.

Cause: You have not specified the mentioned configuration item.

Action: Make sure the mentioned configuration item is provided for this presenter instance.
Level: 1

Type: ERROR

Impact: Other

WCS-07085: The configuration {0} is required.

Cause: You have not specified the mentioned configuration item.

Action: Make sure the mentioned configuration item is provided for this presenter instance.
Level: 1

Type: ERROR

Impact: Other

WCS-07086: Both page size and maximum results are required and must be a positive integer (pageSize:{0}, maxResults:{1}).

Cause: You have not specified the page size and maximum results.

Action: Correct the page size and maximum results.
Level: 1

Type: ERROR

Impact: Other

WCS-07086: Both page size and maximum results are required and must be a positive integer (pageSize:{0}, maxResults:{1}).

Cause: You have not specified the page size and maximum results.

Action: Correct the page size and maximum results.
Level: 1

Type: ERROR

Impact: Other

WCS-07087: Error loading task-flow instance configuration

Cause: An error occurred while loading the task-flow instance configuration.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07087: Error loading task-flow instance configuration

Cause: An error occurred while loading the task-flow instance configuration.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07088: Error saving task-flow instance configuration

Cause: An error occurred while saving the task-flow instance configuration.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07088: Error saving task-flow instance configuration

Cause: An error occurred while saving the task-flow instance configuration.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07089: Unable to save Content Presenter configuration data.

Cause: An error occurred while saving the presenter configuration data.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07089: Unable to save presenter configuration data.

Cause: An error occurred while saving the presenter configuration data.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07090: Unable to retrieve presenter configuration data.

Cause: An error occurred while retrieving the presenter configuration data.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07090: Unable to retrieve presenter configuration data.

Cause: An error occurred while retrieving the presenter configuration data.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07091: Unable to retrieve presenter template data.

Cause: An error occurred while retrieving the presenter template data.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07091: Unable to retrieve presenter template data.

Cause: An error occurred while retrieving the presenter template data.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07092: An error occurred while running the query.

Cause: An error occurred while previewing the query.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07092: An error occurred while running the query.

Cause: An error occurred while previewing the query.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07093: An error occurred while retrieving the node.

Cause: An error occurred while retrieving the node.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07093: An error occurred while retrieving the node.

Cause: An error occurred while retrieving the node.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07094: Maximum results (current:{0}) must be an integer between {1} and {2}.

Cause: The value you have specified for maximum results must inclusively be between the range specified.

Action: Correct the maximum results to be inclusively be between the specified range.
Level: 1

Type: ERROR

Impact: Other

WCS-07094: Maximum results (current:{0}) must be an integer between {1} and {2}.

Cause: The value you have specified for maximum results must inclusively be between the range specified.

Action: Correct the maximum results to be inclusively be between the specified range.
Level: 1

Type: ERROR

Impact: Other

WCS-07095: An error occurred while running the query.

Cause: A general repository exception has occurred.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07095: An error occurred while running the query.

Cause: A general repository exception has occurred.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07096: Unable to retrieve properties for the specified item.

Cause: An error occurred while retrieving properties for the specified item.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07096: Unable to retrieve properties for the specified item.

Cause: An error occurred while retrieving properties for the specified item.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07097: Unable to retrieve markup for the specified item: {0}

Cause: An error occurred while retrieving markup for the specified item.

Action: Check the base exception for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07097: Unable to retrieve markup for the specified item: {0}

Cause: An error occurred while retrieving markup for the specified item.

Action: Check the base exception for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07098: Unable to delete the selected version.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07098: Unable to delete the selected version.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07099: Unable to retrieve workflow approvers for the specified item: {0}

Cause: An error occurred while retrieving workstate approvers for the specified item.

Action: Check the base exception for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07099: Unable to retrieve workflow approvers for the specified item: {0}

Cause: An error occurred while retrieving workstate approvers for the specified item.

Action: Check the base exception for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07100: Oracle Content Server error: {0}

Cause: An unexpected error occurred in the Oracle Content Server.

Action: Check the Oracle Content Server logs for details on this exception.
Level: 1

Type: WARNING

Impact: Other

WCS-07100: Oracle Content Server error: {0}

Cause: An unexpected error occurred in the Oracle Content Server.

Action: Check the Oracle Content Server logs for details on this exception.
Level: 1

Type: WARNING

Impact: Other

WCS-07101: Repository error: {0}

Cause: An unexpected error occurred in the content repository.

Action: Check the base exception and repository's log for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07101: Repository error: {0}

Cause: An unexpected error occurred in the content repository.

Action: Check the base exception and repository's log for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07102: Repository error

Cause: An unexpected error occurred in the content repository.

Action: Check the base exception and repository's log for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07102: Repository error

Cause: An unexpected error occurred in the content repository.

Action: Check the base exception and repository's log for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07103: Unsupported repository operation

Cause: The Documents service tried to invoke an operation that is not supported by the underlying document repository.

Action: Avoid this operation with this repository.
Level: 1

Type: WARNING

Impact: Other

WCS-07103: Unsupported repository operation

Cause: The Documents service tried to invoke an operation that is not supported by the underlying document repository.

Action: Avoid this operation with this repository.
Level: 1

Type: WARNING

Impact: Other

WCS-07104: Access Denied

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07104: Access Denied

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07105: Versioning is not supported on this repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07105: Versioning is not supported on this repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07106: Locking is not supported on this repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07106: Locking is not supported on this repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07107: The recent documents query is not supported on this repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07107: The recent documents query is not supported on this repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07108: Repository error: {0}

Cause: An unexpected error occurred in the content repository.

Action: Check the base exception and repository's log for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07108: Repository error: {0}

Cause: An unexpected error occurred in the content repository.

Action: Check the base exception and repository's log for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07109: Unable to save Content Presenter configuration data because no content item was selected. Select a content item before proceeding further.

Cause: An error occurred while saving the presenter configuration data without a content item.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07201: Unable to approve the selected document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07201: Unable to approve the selected document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07202: Unable to reject the selected document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07202: Unable to reject the selected document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07203: Error initializing the user security cache.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07203: Error initializing the user security cache.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07204: Unable to create new wiki page.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07204: Unable to create new wiki page.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07205: Unable to find parent folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07205: Unable to find parent folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07206: parent folder is not set.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07206: parent folder is not set.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07207: Could not retrieve links count for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07207: Could not retrieve links count for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07208: Could not retrieve tags count for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07208: Could not retrieve tags count for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07209: Could not retrieve comments count for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07209: Could not retrieve comments count for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07210: Could not retrieve likes count for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07210: Could not retrieve likes count for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07211: Could not retrieve likes/comments count for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07211: Could not retrieve likes/comments count for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07212: Error trying to retrieve spaces page for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07212: Error trying to retrieve spaces page for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07213: Could not set the security on the folder or document.

Cause: An error occurred while trying to update the item's security.

Action: Review the associated error messages.
Level: 1

Type: WARNING

Impact: Other

WCS-07213: Could not set the security on the folder or document.

Cause: An error occurred while trying to update the item's security.

Action: Review the associated error messages.
Level: 1

Type: WARNING

Impact: Other

WCS-07214: The Scenario datasource was not constructed correctly

Cause: Either the conductor or the scenario have not be set correctly.

Action: Review the specified conductor service and scenario configurations to make sure they are correct.
Level: 1

Type: ERROR

Impact: Other

WCS-07214: The Scenario datasource was not constructed correctly

Cause: Either the conductor or the scenario have not be set correctly.

Action: Review the specified conductor service and scenario configurations to make sure they are correct.
Level: 1

Type: ERROR

Impact: Other

WCS-07215: Failed to get UCM configuration settings.

Cause: An error occurred while getting configuration information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07215: Failed to get UCM configuration settings.

Cause: An error occurred while getting configuration information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07216: The workflow settings could not be saved as there are too many approvers. Please reduce the number of approvers.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07216: The workflow settings could not be saved as there are too many approvers. Please reduce the number of approvers.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07217: Unable to add the following approvers to the workflow, the approvers username limit has been reached.{0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07217: Unable to add the following approvers to the workflow, the approvers username limit has been reached.{0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07218: Unknown error while retrieving recent documents

Cause: An unknown error occurred while querying for recent documents.

Action: Check the underlying exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07218: Unknown error while retrieving recent documents

Cause: An unknown error occurred while querying for recent documents.

Action: Check the underlying exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07219: Invalid parameter combination: the connection name specified by resourceId = {0} is not the same as specified in parameter connectionName = {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07219: Invalid parameter combination: the connection name specified by resourceId = {0} is not the same as specified in parameter connectionName = {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07220: Invalid parameter combination: the item identified by resourceId = {0} is not a child of startFolderPath = {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07220: Invalid parameter combination: the item identified by resourceId = {0} is not a child of startFolderPath = {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07221: {0} is not a valid resource identifier.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07221: {0} is not a valid resource identifier.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07222: The item with resourceId = {0} does not exist or is not accessible.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07222: The item with resourceId = {0} does not exist or is not accessible.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07223: Invalid content id ''{0}'' for datasource type ''{1}''.

Cause: The specified content id was invalid.

Action: Correct the specified content id to a valid id.
Level: 1

Type: ERROR

Impact: Other

WCS-07223: Invalid content id ''{0}'' for datasource type ''{1}''.

Cause: The specified content id was invalid.

Action: Correct the specified content id to a valid id.
Level: 1

Type: ERROR

Impact: Other

WCS-07225: The object is not a Document Library resource.

Cause: An unexpected condition has occurred.

Action: Contact your Oracle support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07225: The object is not a Document Library resource.

Cause: An unexpected condition has occurred.

Action: Contact your Oracle support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07226: Failed to set ACL on content item as item ACL has been changed concurrently.

Cause: The attempt to change the security settings has failed because the settings have already been changed by another user.

Action: Re-try the operation against the refreshed view of the item's security policy.
Level: 1

Type: ERROR

Impact: Other

WCS-07226: Failed to set ACL on content item as item ACL has been changed concurrently.

Cause: The attempt to change the security settings has failed because the settings have already been changed by another user.

Action: Re-try the operation against the refreshed view of the item's security policy.
Level: 1

Type: ERROR

Impact: Other

WCS-07227: Modifications to an item's security policy are not supported.

Cause: An attempt has been made to modify an item's security policy.

Action: An item's security policy must be updated entirely and not partially.
Level: 1

Type: ERROR

Impact: Other

WCS-07227: Modifications to an item's security policy are not supported.

Cause: An attempt has been made to modify an item's security policy.

Action: An item's security policy must be updated entirely and not partially.
Level: 1

Type: ERROR

Impact: Other

WCS-07228: Failed to set ACL on content item {0}.

Cause: The attempt to set ACL security on an Oracle Content Server repository item has failed.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07228: Failed to set ACL on content item {0}.

Cause: The attempt to set ACL security on an Oracle Content Server repository item has failed.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07229: Failed to restore content item {0} for security settings.

Cause: The attempt to restore a content item from its identifier has failed.

Action: Retry the security settings operation.
Level: 1

Type: ERROR

Impact: Other

WCS-07229: Failed to restore content item {0} for security settings.

Cause: The attempt to restore a content item from its identifier has failed.

Action: Retry the security settings operation.
Level: 1

Type: ERROR

Impact: Other

WCS-07230: Determining if Content Server is configured to support item level security failed.

Cause: An error occurred while getting configuration information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07230: Determining if Content Server is configured to support item level security failed.

Cause: An error occurred while getting configuration information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07231: Determining if Content Server is configured to support Slide Previewer failed.

Cause: An error occurred while getting configuration information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07231: Determining if Content Server is configured to support Slide Previewer failed.

Cause: An error occurred while getting configuration information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07232: Error discovering if user has admin access to file or folder.

Cause: An error occurred when trying to discover if the current user has admin capabilities for the file or folder.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07232: Error discovering if user has admin access to file or folder.

Cause: An error occurred when trying to discover if the current user has admin capabilities for the file or folder.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07233: Cannot perform action, item is in a workflow.

Cause: An action is being attempted on a document which is in a workflow.

Action: Retry the action, when the workflow is complete.
Level: 1

Type: WARNING

Impact: Other

WCS-07233: Cannot perform action, item is in a workflow.

Cause: An action is being attempted on a document which is in a workflow.

Action: Retry the action, when the workflow is complete.
Level: 1

Type: WARNING

Impact: Other

WCS-07234: Fetching Workflow data from Content Server failed.

Cause: An error occurred while getting workflow information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07234: Fetching Workflow data from Content Server failed.

Cause: An error occurred while getting workflow information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07235: No connection specified for Documents to use.

Cause: An attempt was made to use Documents without explicitly specifying a connection or configuring a primary connection.

Action: Either explicitly supply Documents with a connection or specify a primary connection in the ADF configuration.
Level: 1

Type: ERROR

Impact: Other

WCS-07235: No connection specified for Documents to use.

Cause: An attempt was made to use Documents without explicitly specifying a connection or configuring a primary connection.

Action: Either explicitly supply Documents with a connection or specify a primary connection in the ADF configuration.
Level: 1

Type: ERROR

Impact: Other

WCS-07237: Determining if Content Server is configured with AutoVue failed.

Cause: An error occurred while getting configuration information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07237: Determining if Content Server is configured with AutoVue failed.

Cause: An error occurred while getting configuration information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07238: Unexpected exception: {0}

Cause: An unexpected exception occurred.

Action: Check the server logs for details on this exception.
Level: 1

Type: WARNING

Impact: Other

WCS-07238: Unexpected exception: {0}

Cause: An unexpected exception occurred.

Action: Check the server logs for details on this exception.
Level: 1

Type: WARNING

Impact: Other

WCS-07239: Unexpected error

Cause: An unexpected error occurred.

Action: Check the server logs for details on this error.
Level: 1

Type: ERROR

Impact: Other

WCS-07239: Unexpected error

Cause: An unexpected error occurred.

Action: Check the server logs for details on this error.
Level: 1

Type: ERROR

Impact: Other

WCS-07240: Unsupported resource type

Cause: The Documents service tried to perform an operation on a resource but failed to do so because the resource type was not recognized.

Action: Avoid this operation with this particular type of resource.
Level: 1

Type: WARNING

Impact: Other

WCS-07240: Unsupported resource type

Cause: The Documents service tried to perform an operation on a resource but failed to do so because the resource type was not recognized.

Action: Avoid this operation with this particular type of resource.
Level: 1

Type: WARNING

Impact: Other

WCS-07241: Renaming the root folder is not allowed.

Cause: An attempt was made to rename the root folder.

Action: Avoid the rename operation with the root folder.
Level: 1

Type: WARNING

Impact: Other

WCS-07241: Renaming the root folder is not allowed.

Cause: An attempt was made to rename the root folder.

Action: Avoid the rename operation with the root folder.
Level: 1

Type: WARNING

Impact: Other

WCS-07242: Error reading the document's content.

Cause: The document's content could not be accessed.

Action: Verify that the document is available.
Level: 1

Type: WARNING

Impact: Other

WCS-07242: Error reading the document's content.

Cause: The document's content could not be accessed.

Action: Verify that the document is available.
Level: 1

Type: WARNING

Impact: Other

WCS-07243: Error performing paste.

Cause: An error prevented the items from being pasted at the destination folder.

Action: Verify that the destination folder still exists, is writable, and no items with the same names exist there.
Level: 1

Type: ERROR

Impact: Other

WCS-07243: Error performing paste.

Cause: An error prevented the items from being pasted at the destination folder.

Action: Verify that the destination folder still exists, is writable, and no items with the same names exist there.
Level: 1

Type: ERROR

Impact: Other

WCS-07244: When searching between dates, if the dates are not specified in ascending order, the search may not return any results.

Cause: The begin and end dates have been specified in the wrong order.

Action: Specify the dates in ascending order.
Level: 1

Type: WARNING

Impact: Other

WCS-07244: When searching between dates, if the dates are not specified in ascending order, the search may not return any results.

Cause: The begin and end dates have been specified in the wrong order.

Action: Specify the dates in ascending order.
Level: 1

Type: WARNING

Impact: Other

WCS-07245: Operation not allowed on Public folders.

Cause: An attempt has been made to perform an illegal operation on a Public folder.

Action: Do not select a Public folder when performing operations such as delete and rename. If performing a copy or move operation then select item(s) inside the Public folder, not the Public folder itself.
Level: 1

Type: ERROR

Impact: Other

WCS-07245: Operation not allowed on Public folders.

Cause: An attempt has been made to perform an illegal operation on a Public folder.

Action: Do not select a Public folder when performing operations such as delete and rename. If performing a copy or move operation then select item(s) inside the Public folder, not the Public folder itself.
Level: 1

Type: ERROR

Impact: Other

WCS-07246: Approver list is too large for current workflow.

Cause: Unable to save the set of approvers for the workflow as the usernames exceed the 255 character limit.

Action: Reduce the approvers for the workflow.
Level: 1

Type: ERROR

Impact: Other

WCS-07246: Approver list is too large for current workflow.

Cause: Unable to save the set of approvers for the workflow as the usernames exceed the 255 character limit.

Action: Reduce the approvers for the workflow.
Level: 1

Type: ERROR

Impact: Other

WCS-07247: Could not list the items in a folder;

Cause: An error occurred while trying to list the items in a folder.

Action: Make sure that the content repository connection is accessible and that the folder exists. Navigate to another folder in the hierarchy.
Level: 1

Type: WARNING

Impact: Other

WCS-07247: Could not list the items in a folder;

Cause: An error occurred while trying to list the items in a folder.

Action: Make sure that the content repository connection is accessible and that the folder exists. Navigate to another folder in the hierarchy.
Level: 1

Type: WARNING

Impact: Other

WCS-07248: Unable to open the editor.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07248: Unable to open the editor.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07249: Could not connect to the content repository.

Cause: A error occurred while trying to connect to the content repository.

Action: Make sure that the content repository is running and accessible.
Level: 1

Type: ERROR

Impact: Other

WCS-07249: Could not connect to the content repository.

Cause: A error occurred while trying to connect to the content repository.

Action: Make sure that the content repository is running and accessible.
Level: 1

Type: ERROR

Impact: Other

WCS-07250: Provisioning of the Documents service failed.

Cause: An error occurred while trying to provision the Documents service.

Action: Make sure that the content repository connection is accessible. Check the Oracle Content Server logs for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07250: Provisioning of the Documents service failed.

Cause: An error occurred while trying to provision the Documents service.

Action: Make sure that the content repository connection is accessible. Check the Oracle Content Server logs for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07251: The item may have been deleted or has already been approved or rejected.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07251: The item may have been deleted or has already been approved or rejected.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07252: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07252: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07253: Unexpected error evaluating property ''{0}'' of base {1}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-07253: Unexpected error evaluating property ''{0}'' of base {1}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-07254: Click the blog name in the banner to refresh with the latest content.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07254: Click the blog name in the banner to refresh with the latest content.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07255: Typical causes are that you do not have permission or one or more child items are currently in an active workflow.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07256: Error while showing configure content manager pop up.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07257: Error while saving wcc pin to page definition file.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07258: Cannot find region with id {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07259: Cannot find rich popup with id {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07260: Error while viewing the document. Document identifier: {0}, revision identifier: {1} and document account: {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07261: Error while viewing the contents of folder. Folder identifier: {0} and folder account: {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07262: An error occurred while checking permission on content.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07263: Please refresh to see the latest content.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07501: There is no role matching the given ID: {0}.

Cause: The application attempted to look up a service role with an invalid role ID.

Action: Ensure that your application uses a valid service role ID.
Level: 1

Type: ERROR

Impact: Other

WCS-07501: There is no role matching the given ID: {0}.

Cause: The application attempted to look up a service role with an invalid role ID.

Action: Ensure that your application uses a valid service role ID.
Level: 1

Type: ERROR

Impact: Other

WCS-07502: Cannot grant super administrator role for scope {1}.

Cause: Could not grant the super administrator role to the scope. The super administrator role can only be granted to the default scope; other roles must be granted on a portal scope.

Action: Verify that the role mapping is correctly defined.
Level: 1

Type: ERROR

Impact: Other

WCS-07502: Cannot grant super administrator role for scope {1}.

Cause: Could not grant the super administrator role to the scope. The super administrator role can only be granted to the default scope; other roles must be granted on a portal scope.

Action: Verify that the role mapping is correctly defined.
Level: 1

Type: ERROR

Impact: Other

WCS-07503: Cannot log on to the content repository.

Cause: The username and password used for the current login were not correct.

Action: Check the username and password.
Level: 1

Type: WARNING

Impact: Other

WCS-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-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-07505: The repository login was interrupted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07601: Unable to read document metadata (''{0}'',''{1}'').

Cause: Generally caused by a malformed xml document.

Action: Check the specified xml document for errors.
Level: 1

Type: ERROR

Impact: Other

WCS-07601: Unable to read document metadata (''{0}'',''{1}'').

Cause: Generally caused by a malformed xml document.

Action: Check the specified xml document for errors.
Level: 1

Type: ERROR

Impact: Other

WCS-07602: Document metadata (''{0}'',''{1}'') is expected to be of type ''{2}'', but found ''{3}''.

Cause: Generally caused by a malformed xml document with an incorrect namespace.

Action: Check the specified xml document and make sure the xmlns attribute is set to 'http://xmlns.oracle.com/webcenter/content/templates/registry'.
Level: 1

Type: ERROR

Impact: Other

WCS-07602: Document metadata (''{0}'',''{1}'') is expected to be of type ''{2}'', but found ''{3}''.

Cause: Generally caused by a malformed xml document with an incorrect namespace.

Action: Check the specified xml document and make sure the xmlns attribute is set to 'http://xmlns.oracle.com/webcenter/content/templates/registry'.
Level: 1

Type: ERROR

Impact: Other

WCS-07603: No content list template or content template found in registry(''{0}'',''{1}'').

Cause: Generally caused by an empty display template descriptor.

Action: Check the specified xml document and make sure that either content-templates or content-list-templates are defined.
Level: 1

Type: ERROR

Impact: Other

WCS-07603: No content list template or content template found in registry(''{0}'',''{1}'').

Cause: Generally caused by an empty display template descriptor.

Action: Check the specified xml document and make sure that either content-templates or content-list-templates are defined.
Level: 1

Type: ERROR

Impact: Other

WCS-07604: Default template view named ''{0}'' not found for content type ''{1}''.

Cause: A content type has been configured in the template registry with a default template that has not been found.

Action: Check the specified xml document and make sure a template view exists with the id of the defaultView specified on the content type.
Level: 1

Type: ERROR

Impact: Other

WCS-07604: Default template view named ''{0}'' not found for content type ''{1}''.

Cause: A content type has been configured in the template registry with a default template that has not been found.

Action: Check the specified xml document and make sure a template view exists with the id of the defaultView specified on the content type.
Level: 1

Type: ERROR

Impact: Other

WCS-07605: There are duplicate template categories with id ''{0}''.

Cause: There are duplicate template categories that are defined with the specified id.

Action: Check the template registry document and make sure and change the name of the specified template category.
Level: 1

Type: ERROR

Impact: Other

WCS-07605: There are duplicate template categories with id ''{0}''.

Cause: There are duplicate template categories that are defined with the specified id.

Action: Check the template registry document and make sure and change the name of the specified template category.
Level: 1

Type: ERROR

Impact: Other

WCS-07606: There are duplicate content types by name ''{0}''.

Cause: There are duplicate content types that are defined with the specified name.

Action: Check the template registry document and make sure and change the name of the specified content type.
Level: 1

Type: ERROR

Impact: Other

WCS-07606: There are duplicate content types by name ''{0}''.

Cause: There are duplicate content types that are defined with the specified name.

Action: Check the template registry document and make sure and change the name of the specified content type.
Level: 1

Type: ERROR

Impact: Other

WCS-07607: There are duplicate content repositories by name ''{0}'' and type ''{1}''.

Cause: There are duplicate content repositories that are defined with the specified name.

Action: Check the template registry document and make sure and change the name of the specified content repository.
Level: 1

Type: ERROR

Impact: Other

WCS-07607: There are duplicate content repositories by name ''{0}'' and type ''{1}''.

Cause: There are duplicate content repositories that are defined with the specified name.

Action: Check the template registry document and make sure and change the name of the specified content repository.
Level: 1

Type: ERROR

Impact: Other

WCS-07608: There are duplicate template views by id ''{0}''.

Cause: There are duplicate template views that are defined with the specified id.

Action: Check the template registry document and make sure and change the id of the specified template view.
Level: 1

Type: ERROR

Impact: Other

WCS-07608: There are duplicate template views by id ''{0}''.

Cause: There are duplicate template views that are defined with the specified id.

Action: Check the template registry document and make sure and change the id of the specified template view.
Level: 1

Type: ERROR

Impact: Other

WCS-07609: The class method ''{0}.{1}'' cannot be called with a null argument ''{2}''.

Cause: The specified method call cannot be called with the specified argument with value of null.

Action: Ensure the specified argument has a non-null value.
Level: 1

Type: ERROR

Impact: Other

WCS-07609: The class method ''{0}.{1}'' cannot be called with a null argument ''{2}''.

Cause: The specified method call cannot be called with the specified argument with value of null.

Action: Ensure the specified argument has a non-null value.
Level: 1

Type: ERROR

Impact: Other

WCS-07610: Unable to locate resource key ''{0}'' in bundle ''{1}''.

Cause: The display template registry is configured with a resource bundle and key that is unable to be found.

Action: Check the specified resource bundle and ensure that the specified key exists.
Level: 1

Type: WARNING

Impact: Other

WCS-07610: Unable to locate resource key ''{0}'' in bundle ''{1}''.

Cause: The display template registry is configured with a resource bundle and key that is unable to be found.

Action: Check the specified resource bundle and ensure that the specified key exists.
Level: 1

Type: WARNING

Impact: Other

WCS-07611: No template category defined by id ''{0}''.

Cause: The display template registry does not contain a category configuration by the specified id.

Action: Add the specified category id to the template registry.
Level: 1

Type: WARNING

Impact: Other

WCS-07611: No template category defined by id ''{0}''.

Cause: The display template registry does not contain a category configuration by the specified id.

Action: Add the specified category id to the template registry.
Level: 1

Type: WARNING

Impact: Other

WCS-07612: No template view defined by id ''{0}''.

Cause: The display template registry does not contain a template configuration by the specified id.

Action: Add the specified template id to the template registry.
Level: 1

Type: WARNING

Impact: Other

WCS-07612: No template view defined by id ''{0}''.

Cause: The display template registry does not contain a template configuration by the specified id.

Action: Add the specified template id to the template registry.
Level: 1

Type: WARNING

Impact: Other

WCS-07613: No template registry found in application.

Cause: The display template registry does not exist or cannot be found.

Action: Check application configuration and ensure registry is properly configured.
Level: 1

Type: WARNING

Impact: Other

WCS-07613: No template registry found in application.

Cause: The display template registry does not exist or cannot be found.

Action: Check application configuration and ensure registry is properly configured.
Level: 1

Type: WARNING

Impact: Other

WCS-07614: Default template view named ''{0}'' not found in template category ''{1}''.

Cause: A category has been configured in the template registry with a default template view that has not been found.

Action: Check the specified xml document and make sure a template view exists with the id of the defaultView specified on the category.
Level: 1

Type: ERROR

Impact: Other

WCS-07614: Default template view named ''{0}'' not found in template category ''{1}''.

Cause: A category has been configured in the template registry with a default template view that has not been found.

Action: Check the specified xml document and make sure a template view exists with the id of the defaultView specified on the category.
Level: 1

Type: ERROR

Impact: Other

WCS-07615: Default category named ''{0}'' not found in the registry.

Cause: A default category has been configured in the template registry that has not been found.

Action: Check the specified xml document and make sure a the default category has been defined.
Level: 1

Type: ERROR

Impact: Other

WCS-07615: Default category named ''{0}'' not found in the registry.

Cause: A default category has been configured in the template registry that has not been found.

Action: Check the specified xml document and make sure a the default category has been defined.
Level: 1

Type: ERROR

Impact: Other

WCS-07616: No template view defined by id ''{0}'' and category ''{1}''.

Cause: The display template registry does not contain a template configuration by the specified category and view.

Action: Add the specified template id to the template registry.
Level: 1

Type: WARNING

Impact: Other

WCS-07616: No template view defined by id ''{0}'' and category ''{1}''.

Cause: The display template registry does not contain a template configuration by the specified category and view.

Action: Add the specified template id to the template registry.
Level: 1

Type: WARNING

Impact: Other

WCS-07617: A general display template error has occurred.

Cause: An unexpected exception has occurred processing the display template registry.

Action: Review the original stacktrace cause for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07617: A general display template error has occurred.

Cause: An unexpected exception has occurred processing the display template registry.

Action: Review the original stacktrace cause for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07618: No default template view specified for category id ''{0}''. Returning the default view for the default category.

Cause: The specified category in the template registry is not configured with a default view, but has been referenced using the default behavior.

Action: Update the specified category in the template registry to configure a default view.
Level: 1

Type: WARNING

Impact: Other

WCS-07618: No default template view specified for category id ''{0}''. Returning the default view for the default category.

Cause: The specified category in the template registry is not configured with a default view, but has been referenced using the default behavior.

Action: Update the specified category in the template registry to configure a default view.
Level: 1

Type: WARNING

Impact: Other

WCS-07619: Invalid configuration for category id ''{0}''. Could not find view defined for view id ''{1}''.

Cause: The specified category in the template registry is configured with no default templates.

Action: Update the registry to only include a single default template for the category.
Level: 1

Type: WARNING

Impact: Other

WCS-07619: Invalid configuration for category id ''{0}''. Could not find view defined for view id ''{1}''.

Cause: The specified category in the template registry is configured with no default templates.

Action: Update the registry to only include a single default template for the category.
Level: 1

Type: WARNING

Impact: Other

WCS-07620: Invalid configuration for category id ''{0}''. Multiple templates found for view id ''{1}''.

Cause: The specified category in the template registry is configured with multiple templates.

Action: Update the registry to only include a single template for the category and view id combination.
Level: 1

Type: WARNING

Impact: Other

WCS-07620: Invalid configuration for category id ''{0}''. Multiple templates found for view id ''{1}''.

Cause: The specified category in the template registry is configured with multiple templates.

Action: Update the registry to only include a single template for the category and view id combination.
Level: 1

Type: WARNING

Impact: Other

WCS-07621: Invalid configuration for content type name ''{0}'' in repository name ''{1}'' configuration.

Cause: The specified category in the template registry is configured with no default templates.

Action: Update the registry to only include a single default template for the category.
Level: 1

Type: WARNING

Impact: Other

WCS-07621: Invalid configuration for content type name ''{0}'' in repository name ''{1}'' configuration.

Cause: The specified category in the template registry is configured with no default templates.

Action: Update the registry to only include a single default template for the category.
Level: 1

Type: WARNING

Impact: Other

WCS-07622: Invalid configuration for content type name ''{0}'' in repository ''{1}''. Multiple default templates found.

Cause: The specified category in the template registry is configured with multiple templates.

Action: Update the registry to only include a single template for the category and view id combination.
Level: 1

Type: WARNING

Impact: Other

WCS-07622: Invalid configuration for content type name ''{0}'' in repository ''{1}''. Multiple default templates found.

Cause: The specified category in the template registry is configured with multiple templates.

Action: Update the registry to only include a single template for the category and view id combination.
Level: 1

Type: WARNING

Impact: Other

WCS-07701: severe internal error while getting the template view ID

Cause: An irrecoverable internal error has occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-07701: severe internal error while getting the template view ID

Cause: An irrecoverable internal error has occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-07702: Error while getting the template view ID

Cause: An error occurred while determining the template for a node.

Action: Check the underlying exception.
Level: 1

Type: WARNING

Impact: Other

WCS-07702: Error while getting the template view ID

Cause: An error occurred while determining the template for a node.

Action: Check the underlying exception.
Level: 1

Type: WARNING

Impact: Other

WCS-07703: No request dispatcher for template viewID {0} located at {1}

Cause: An error occurred while trying to dispatch the request to the template. The target template may not exist.

Action: Check that the target template exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07703: No request dispatcher for template viewID {0} located at {1}

Cause: An error occurred while trying to dispatch the request to the template. The target template may not exist.

Action: Check that the target template exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07704: Error processing the display template include for template viewID {0} located at {1}

Cause: An error occurred while processing the template include. This may result from a syntax or logic error in the template code.

Action: Check the underlying exception for the details of the error.
Level: 1

Type: ERROR

Impact: Other

WCS-07704: Error processing the display template include for template viewID {0} located at {1}

Cause: An error occurred while processing the template include. This may result from a syntax or logic error in the template code.

Action: Check the underlying exception for the details of the error.
Level: 1

Type: ERROR

Impact: Other

WCS-07710: Error while getting the template view ID because of null node or view, node: {0}, view: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07710: Error while getting the template view ID because of null node or view, node: {0}, view: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07712: Error setting up context for template. {0}

Cause: An error occurred while trying to setup the context for the template.

Action: Check the underlying error.
Level: 1

Type: ERROR

Impact: Other

WCS-07712: Error setting up context for template. {0}

Cause: An error occurred while trying to setup the context for the template.

Action: Check the underlying error.
Level: 1

Type: ERROR

Impact: Other

WCS-07713: Internal error: illegal reentrant use of template context.

Cause: An internal error was detected, attempted reentrant use of template context.

Action: Contact your Oracle Support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07713: Internal error: illegal reentrant use of template context.

Cause: An internal error was detected, attempted reentrant use of template context.

Action: Contact your Oracle Support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07714: Error tearing down context for template. {0}

Cause: An error occurred while trying to teardown the context for the template.

Action: Check the underlying error.
Level: 1

Type: WARNING

Impact: Other

WCS-07714: Error tearing down context for template. {0}

Cause: An error occurred while trying to teardown the context for the template.

Action: Check the underlying error.
Level: 1

Type: WARNING

Impact: Other

WCS-07715: Error popping context, found another template context. {0}. {1}.

Cause: An error occurred while trying to pop the context, found another template context.

Action: Contact your Orale support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07715: Error popping context, found another template context. {0}. {1}.

Cause: An error occurred while trying to pop the context, found another template context.

Action: Contact your Orale support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07716: Error popping context, found another context. {0}.

Cause: An error occurred while trying to pop the context, found another context.

Action: Contact your Oracle support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07716: Error popping context, found another context. {0}.

Cause: An error occurred while trying to pop the context, found another context.

Action: Contact your Oracle support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07717: Error while invoking component.

Cause: An error occurred while invoking the template component.

Action: Check the underlying exception.
Level: 1

Type: WARNING

Impact: Other

WCS-07717: Error while invoking component.

Cause: An error occurred while invoking the template component.

Action: Check the underlying exception.
Level: 1

Type: WARNING

Impact: Other

WCS-07718: Error when resuming context: no queued context to resume.

Cause: Template context cannot be resumed, as context queue is empty.

Action: Contact your Oracle support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07718: Error when resuming context: no queued context to resume.

Cause: Template context cannot be resumed, as context queue is empty.

Action: Contact your Oracle support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07719: Error when resuming context: no context to resume.

Cause: Template context cannot be resumed, as there is no context to resume.

Action: Contact your Oracle support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07719: Error when resuming context: no context to resume.

Cause: Template context cannot be resumed, as there is no context to resume.

Action: Contact your Oracle support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07720: Error retrieving Region Template from WebCenter Content.

Cause: An error occurred retrieving the Region Template from the WebCenter Content server.

Action: Check the exception for the underlying cause.
Level: 1

Type: ERROR

Impact: Other

WCS-07801: Cannot seed the WebCenter data into the content repository.

Cause: An error occurred while seeding data for the Documents service in the content repository.

Action: Check the underlying exception and content repository log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-07810: Error obtaining the content repository connection "{0}".

Cause: A JNDI Naming Exception occurred while attempting to obtain the content repository connection.

Action: Verify that connections.xml contains a valid content repository connection.
Level: 1

Type: ERROR

Impact: Other

WCS-07811: Unsupported repository connection "{0}" for the Documents service.

Cause: The specified content repository is not currently supported for Documents service WebCenter Portal integration. The supported content repository types is Oracle Content Server.

Action: Verify that adf-config.xml and connections.xml contain a valid entry for the Documents service repository.
Level: 1

Type: ERROR

Impact: Other

WCS-07811: Unsupported repository connection "{0}" for the Documents service.

Cause: The specified content repository is not currently supported for Documents service WebCenter Portal integration. The supported content repository types is Oracle Content Server.

Action: Verify that adf-config.xml and connections.xml contain a valid entry for the Documents service repository.
Level: 1

Type: ERROR

Impact: Other

WCS-07812: Cannot remove permissions, {0}, for user/group, {1}, to the account for the folder, {2}.

Cause: The application failed to remove permissions for the user/group on the folder.

Action: Check that the permissions and user/group are valid and that the folder exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07812: Cannot remove permissions, {0}, for user/group, {1}, to the account for the folder, {2}.

Cause: The application failed to remove permissions for the user/group on the folder.

Action: Check that the permissions and user/group are valid and that the folder exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07813: Cannot grant permissions, {0}, for user, {1}, to the account for the folder, {2}.

Cause: The application failed to grant permissions for the user on the folder.

Action: Check that the permissions and user are valid and that the folder exists.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-07823: Cannot grant the account, {0}, to all users.

Cause: An error occurred while trying to grant the account to all users.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07824: Unable to get the admin session to the Oracle Content Server repository.

Cause: An error occurred while trying to obtain an admin session to the Oracle Content Server repository.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07824: Unable to get the admin session to the Oracle Content Server repository.

Cause: An error occurred while trying to obtain an admin session to the Oracle Content Server repository.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07825: Cannot remove role, {0}, for user/group, {1}.

Cause: The application failed to remove the specified role from the user/group.

Action: Check the role and user/group are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-07825: Cannot remove role, {0}, for user/group, {1}.

Cause: The application failed to remove the specified role from the user/group.

Action: Check the role and user/group are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-07826: Cannot remove role {0} and permissions, {1}, to the account for the folder, {2} for the user/group {3}.

Cause: The application failed to remove the role and permissions on the folder for the user/group.

Action: Check that the permissions and user/group are valid and that the folder exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07826: Cannot remove role {0} and permissions, {1}, to the account for the folder, {2} for the user/group {3}.

Cause: The application failed to remove the role and permissions on the folder for the user/group.

Action: Check that the permissions and user/group are valid and that the folder exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07827: Cannot add role, {0}, for user/group, {1}.

Cause: The application failed to add the specified role to the user/group.

Action: Check the role and user/group are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-07827: Cannot add role, {0}, for user/group, {1}.

Cause: The application failed to add the specified role to the user/group.

Action: Check the role and user/group are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-07828: Cannot add role {0} and permissions, {1}, to the account for the folder, {2} for the user/group {3}.

Cause: The application failed to add the role and permissions on the folder for the user/group.

Action: Check that the permissions and user/group are valid and that the folder exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07828: Cannot add role {0} and permissions, {1}, to the account for the folder, {2} for the user/group {3}.

Cause: The application failed to add the role and permissions on the folder for the user/group.

Action: Check that the permissions and user/group are valid and that the folder exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07829: Cannot update the account for the portal {0}, with permission, {1}, for all users.

Cause: An error occurred while trying to update the portal account for all users.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07829: Cannot update the account for the portal {0}, with permission, {1}, for all users.

Cause: An error occurred while trying to update the portal account for all users.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07830: Cannot set default attributes, {0}, for the key, {1}

Cause: An error occurred while trying to set default attributes for the specified key.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-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-07831: Cannot delete default attributes for the key, {0}.

Cause: An error occurred while trying to delete default attributes for the specified key.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07832: Cannot determine account and permission from the default attributes for the portal, {0}.

Cause: An error occurred while trying to determine the account and permission from the default attributes for the portal. The default attributes are not in the correct format.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07832: Cannot determine account and permission from the default attributes for the portal, {0}.

Cause: An error occurred while trying to determine the account and permission from the default attributes for the portal. The default attributes are not in the correct format.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07833: The Java Object Cache is not available.

Cause: An error occurred while trying to retrieve the cache.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-07838: Java Object Cache, release ownership failed.

Cause: A cache unlock operation on a cached object failed.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07839: Invalid document service ADF configuration.

Cause: The documents services configuration in adf-config.xml is invalid.

Action: Verify that the documents services configuration in adf-config.xml conforms to the documents service configuration data schema.
Level: 1

Type: ERROR

Impact: Other

WCS-07839: Invalid document service ADF configuration.

Cause: The documents services configuration in adf-config.xml is invalid.

Action: Verify that the documents services configuration in adf-config.xml conforms to the documents service configuration data schema.
Level: 1

Type: ERROR

Impact: Other

WCS-07840: Cannot get folder with the GUID, {0}, from the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07840: Cannot get folder with the GUID, {0}, from the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07845: Error loading Site Studio content.

Cause: An error occurred while loading data for Site Studio into the content repository.

Action: Check the underlying exception and content repository log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07846: Error checking Site Studio content into Content Server.

Cause: An error occurred while checking in Site Studio content into the content repository.

Action: Check the underlying exception and content repository log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07847: Error checking installation of SiteStudio on Content Server.

Cause: An error occurred while checking the installation of the Site Studio in the content repository.

Action: Check the underlying exception and content repository log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07848: Error creating temporary directory to extract SiteStudio content to.

Cause: An error occurred while creating the directory to extract the Site Studio content to.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07850: Failed to destroy Java Object Cache region, {0}.

Cause: An error occurred while trying to destroy the Doclib Java Object Cache region.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07850: Failed to destroy Java Object Cache region, {0}.

Cause: An error occurred while trying to destroy the Doclib Java Object Cache region.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07857: Cannot get the version for the {0} component from the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07857: Cannot get the version for the {0} component from the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07863: Cannot determine if Document Library supports Enterprise Roles.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07863: Cannot determine if Document Library supports Enterprise Roles.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07864: Cannot enable the workflow {0}.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07864: Cannot enable the workflow {0}.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07865: Cannot create the workflow with the name {0}.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07865: Cannot create the workflow with the name {0}.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07866: Cannot create the workflow step {0} for the workflow {1}.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07866: Cannot create the workflow step {0} for the workflow {1}.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07867: Cannot get the portal account from the GUID {0}.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07867: Cannot get the portal account from the GUID {0}.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07868: Cannot propagate account for the portal folder {0} to its contents.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07868: Cannot propagate account for the portal folder {0} to its contents.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07870: Security settings are only supported for Oracle Content Server.

Cause: An attempt has been made to set security for a non Oracle Content Server repository.

Action: To enable security, use Oracle Content Server.
Level: 1

Type: ERROR

Impact: Other

WCS-07870: Security settings are only supported for Oracle Content Server.

Cause: An attempt has been made to set security for a non Oracle Content Server repository.

Action: To enable security, use Oracle Content Server.
Level: 1

Type: ERROR

Impact: Other

WCS-07871: Cannot set default attributes, for the key, {1}

Cause: An error occurred while trying to get default attributes for the specified key.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07871: Cannot set default attributes, for the key, {1}

Cause: An error occurred while trying to get default attributes for the specified key.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07872: Unable to upgrade the WebCenter data in the Oracle Content Server repository.

Cause: A Content Server error occurred while upgrading the WebCenter data in the repository.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07872: Unable to upgrade the WebCenter data in the Oracle Content Server repository.

Cause: A Content Server error occurred while upgrading the WebCenter data in the repository.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07873: Cannot get the workflow {0}.

Cause: A Content Server error occurred while getting the workflow.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07873: Cannot get the workflow {0}.

Cause: A Content Server error occurred while getting the workflow.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07874: The documents services configuration in adf-config.xml is invalid, one of the settings is being used in another Webcenter's configuration.

Cause: Either the portal root or application name in the Document Properties is the same as another WebCenter instance using the same Content Server.

Action: Ensure the portal root and application are both unique and not being used in another WebCenter's configuration using the same Content Server.
Level: 1

Type: ERROR

Impact: Other

WCS-07874: The documents services configuration in adf-config.xml is invalid, one of the settings is being used in another Webcenter's configuration.

Cause: Either the portal root or application name in the Document Properties is the same as another WebCenter instance using the same Content Server.

Action: Ensure the portal root and application are both unique and not being used in another WebCenter's configuration using the same Content Server.
Level: 1

Type: ERROR

Impact: Other

WCS-07875: Can not get the folder metadata for the scope, {0}.

Cause: A Content Server error occurred while getting the scope's folder metadata.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07875: Can not get the folder metadata for the scope, {0}.

Cause: A Content Server error occurred while getting the scope's folder metadata.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07877: Error invalidating the VCR cache entry for {0}.

Cause: An error happened while trying to remove an item from the VCR cache.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07877: Error invalidating the VCR cache entry for {0}.

Cause: An error happened while trying to remove an item from the VCR cache.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07878: Error determining if a scope in the export set has document library provisioned.

Cause: An error happened while trying to determine if the scope is provisioned.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07878: Error determining if a scope in the export set has document library provisioned.

Cause: An error happened while trying to determine if the scope is provisioned.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07879: Error while writing doclib provisioned scope to export file.

Cause: An error happened while trying to output the scopes which have document library provisioned.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07879: Error while writing doclib provisioned scope to export file.

Cause: An error happened while trying to output the scopes which have document library provisioned.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07880: Error while writing the doclib export document to MDS for portal(s) {0}.

Cause: An error happened while trying to write the document containing the document library export data to MDS.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07880: Error while writing the doclib export document to MDS for portal(s) {0}.

Cause: An error happened while trying to write the document containing the document library export data to MDS.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07884: Error while reading the set of doclib provisioned scopes from the export file.

Cause: An error happened while trying to read the scopes which have document library provisioned from the export file.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07884: Error while reading the set of doclib provisioned scopes from the export file.

Cause: An error happened while trying to read the scopes which have document library provisioned from the export file.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07885: Error while reading the doclib export document from MDS for portals{0} .

Cause: An error happened while trying to read the document containing the document library export data from MDS.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07885: Error while reading the doclib export document from MDS for portals{0} .

Cause: An error happened while trying to read the document containing the document library export data from MDS.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07886: Error provisioning document library for a scope in the import set.

Cause: An error happened while trying to provisioning document library during import.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07886: Error provisioning document library for a scope in the import set.

Cause: An error happened while trying to provisioning document library during import.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07887: No document library export data found for import in MDS under path {0} for portal(s) {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07887: No document library export data found for import in MDS under path {0} for portal(s) {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07888: Invalid datasource type ''{0}''. Valid datasource types:{1}.

Cause: The specified datasource type was invalid.

Action: Correct the specified datasource type to one of the examples provided in the error message.
Level: 1

Type: ERROR

Impact: Other

WCS-07888: Invalid datasource type ''{0}''. Valid datasource types:{1}.

Cause: The specified datasource type was invalid.

Action: Correct the specified datasource type to one of the examples provided in the error message.
Level: 1

Type: ERROR

Impact: Other

WCS-07889: Query expression must be a valid, non-empty expression.

Cause: The specified query expression was invalid.

Action: Review the specified query expression and correct it.
Level: 1

Type: ERROR

Impact: Other

WCS-07889: Query expression must be a valid, non-empty expression.

Cause: The specified query expression was invalid.

Action: Review the specified query expression and correct it.
Level: 1

Type: ERROR

Impact: Other

WCS-07890: The Scenario datasource was not constructed correctly

Cause: Either the conductor or the scenario have not be set correctly.

Action: Review the specified conductor service and scenario configurations to make sure they are correct.
Level: 1

Type: ERROR

Impact: Other

WCS-07890: The Scenario datasource was not constructed correctly

Cause: Either the conductor or the scenario have not be set correctly.

Action: Review the specified conductor service and scenario configurations to make sure they are correct.
Level: 1

Type: ERROR

Impact: Other

WCS-07891: Failed to get UCM configuration settings.

Cause: An error occurred while getting configuration information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07891: Failed to get UCM configuration settings.

Cause: An error occurred while getting configuration information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07892: Invalid content id ''{0}'' for datasource type ''{1}''.

Cause: The specified content id was invalid.

Action: Correct the specified content id to a valid id.
Level: 1

Type: ERROR

Impact: Other

WCS-07892: Invalid content id ''{0}'' for datasource type ''{1}''.

Cause: The specified content id was invalid.

Action: Correct the specified content id to a valid id.
Level: 1

Type: ERROR

Impact: Other

WCS-07893: The datasource type ''{0}'' requires ''{1}'' to be set.

Cause: The specified datasource type is not consistent with the datasource state.

Action: Specific datasource types require different parameters to be set. Please resolve this situation.
Level: 1

Type: ERROR

Impact: Other

WCS-07893: The datasource type ''{0}'' requires ''{1}'' to be set.

Cause: The specified datasource type is not consistent with the datasource state.

Action: Specific datasource types require different parameters to be set. Please resolve this situation.
Level: 1

Type: ERROR

Impact: Other

WCS-07894: Both page size and maximum results are required and must be a positive integer (pageSize:{0}, maxResults:{1}).

Cause: You have not specified the page size and maximum results.

Action: Correct the page size and maximum results.
Level: 1

Type: ERROR

Impact: Other

WCS-07894: Both page size and maximum results are required and must be a positive integer (pageSize:{0}, maxResults:{1}).

Cause: You have not specified the page size and maximum results.

Action: Correct the page size and maximum results.
Level: 1

Type: ERROR

Impact: Other

WCS-07895: Maximum results (current:{0}) must be an integer between {1} and {2}.

Cause: The value you have specified for maximum results must inclusively be between the range specified.

Action: Correct the maximum results to be inclusively be between the specified range.
Level: 1

Type: ERROR

Impact: Other

WCS-07895: Maximum results (current:{0}) must be an integer between {1} and {2}.

Cause: The value you have specified for maximum results must inclusively be between the range specified.

Action: Correct the maximum results to be inclusively be between the specified range.
Level: 1

Type: ERROR

Impact: Other

WCS-07896: An error occurred while retrieving the node.

Cause: An error occurred while retrieving the node.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07896: An error occurred while retrieving the node.

Cause: An error occurred while retrieving the node.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07897: Error retrieving node(s).

Cause: An error was encountered retrieving node(s).

Action: Please contact a system administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-07897: Error retrieving node(s).

Cause: An error was encountered retrieving node(s).

Action: Please contact a system administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-07898: The datasource type ''{0}'' is currently not supported for custom folder.

Cause: The specified datasource type is not supported for ContentListFactory custom folder.

Action: Only specific datasource types are supported. Please resolve this situation.
Level: 1

Type: ERROR

Impact: Other

WCS-07898: The datasource type ''{0}'' is currently not supported for custom folder.

Cause: The specified datasource type is not supported for ContentListFactory custom folder.

Action: Only specific datasource types are supported. Please resolve this situation.
Level: 1

Type: ERROR

Impact: Other

WCS-07899: Cannot update the seeded role, {0}, in the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07899: Cannot update the seeded role, {0}, in the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07900: Can not perform document library role mapping, role mapper is not initialized.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07900: Can not perform document library role mapping, role mapper is not initialized.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07901: Can not perform document library role mapping, role mapper was initialized with a different scope to that being processed. Initialized with scope {0} and processing with scope {1}.

Cause: The document library role mapper can only process actions for the scope with which it was initialized. A request has been made to process role mapping for a different scope which is not permitted.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07901: Can not perform document library role mapping, role mapper was initialized with a different scope to that being processed. Initialized with scope {0} and processing with scope {1}.

Cause: The document library role mapper can only process actions for the scope with which it was initialized. A request has been made to process role mapping for a different scope which is not permitted.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07902: Can not perform document library role mapping, the scope does not have Document Library provisioned.

Cause: The document library role mapper can only map roles for a scope which has document library provisioned.

Action: Check the scope has document library provisioned.
Level: 1

Type: ERROR

Impact: Other

WCS-07902: Can not perform document library role mapping, the scope does not have Document Library provisioned.

Cause: The document library role mapper can only map roles for a scope which has document library provisioned.

Action: Check the scope has document library provisioned.
Level: 1

Type: ERROR

Impact: Other

WCS-07903: Invalid repository name {0}.

Cause: An invalid repository was specified.

Action: Verify that a valid repository is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-07903: Invalid repository name {0}.

Cause: An invalid repository was specified.

Action: Verify that a valid repository is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-07904: Error while exporting the documents content.

Cause: An error happened while trying to export the documents content of the scopes being exported.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07904: Error while exporting the documents content.

Cause: An error happened while trying to export the documents content of the scopes being exported.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07905: Error while getting the documents contents of the source scope.

Cause: An error happened while trying to get the documents of the source scope from the Content Server.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07905: Error while getting the documents contents of the source scope.

Cause: An error happened while trying to get the documents of the source scope from the Content Server.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07906: No scopes have been specified for export.

Cause: No portals have been specified to be exported.

Action: Specify scopes to be exported.
Level: 1

Type: WARNING

Impact: Other

WCS-07906: No scopes have been specified for export.

Cause: No portals have been specified to be exported.

Action: Specify scopes to be exported.
Level: 1

Type: WARNING

Impact: Other

WCS-07907: Error while importing the documents content.

Cause: An error happened while trying to import the documents content of the scopes being imported.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07907: Error while importing the documents content.

Cause: An error happened while trying to import the documents content of the scopes being imported.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07908: Group Space folder does not exist in target instance can not proceed with import.

Cause: The scope has not been provisioned in the target instance, can not proceed to import data into the target instance.

Action: Ensure WebCenter Export Import has completed successfully and the Scope is provisioned in the target instance.
Level: 1

Type: ERROR

Impact: Other

WCS-07908: Group Space folder does not exist in target instance can not proceed with import.

Cause: The scope has not been provisioned in the target instance, can not proceed to import data into the target instance.

Action: Ensure WebCenter Export Import has completed successfully and the Scope is provisioned in the target instance.
Level: 1

Type: ERROR

Impact: Other

WCS-07909: The import archive {0} was not found, no document data will be imported.

Cause: The archive containing the documents data was not found. Import of documents content will not occur.

Action: Ensure WebCenter Export included the exporting of documents content..
Level: 1

Type: WARNING

Impact: Other

WCS-07909: The import archive {0} was not found, no document data will be imported.

Cause: The archive containing the documents data was not found. Import of documents content will not occur.

Action: Ensure WebCenter Export included the exporting of documents content..
Level: 1

Type: WARNING

Impact: Other

WCS-07910: Unable to delete data in the target scope prior to import.

Cause: An error happened while trying to delete existing data in the target scope before import commences.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07910: Unable to delete data in the target scope prior to import.

Cause: An error happened while trying to delete existing data in the target scope before import commences.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07911: Unable to create document in target scope.

Cause: An error happened while trying to create a document in the target scope.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07911: Unable to create document in target scope.

Cause: An error happened while trying to create a document in the target scope.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07916: The following documents were not imported {0}.

Cause: The documents in the list could not be imported into the target UCM.

Action: Check the logs for more information.
Level: 1

Type: WARNING

Impact: Other

WCS-07916: The following documents were not imported {0}.

Cause: The documents in the list could not be imported into the target UCM.

Action: Check the logs for more information.
Level: 1

Type: WARNING

Impact: Other

WCS-07917: Error creating content URL.

Cause: An error occurred creating a content URL.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07917: Error creating content URL.

Cause: An error occurred creating a content URL.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07918: The content item {0} was not imported. An item with the filename {1} already exists in the folder.

Cause: Oracle Content Server does not permit multiple content items with the same filename to be checked into the same folder. The content item being imported has the same filename as an existing content item in the same folder. The duplicate document has not been imported.

Action: Check the source UCM instance and either remove the duplicate content items, or ensure the import has imported the correct version of the content item.
Level: 1

Type: WARNING

Impact: Other

WCS-07918: The content item {0} was not imported. An item with the filename {1} already exists in the folder.

Cause: Oracle Content Server does not permit multiple content items with the same filename to be checked into the same folder. The content item being imported has the same filename as an existing content item in the same folder. The duplicate document has not been imported.

Action: Check the source UCM instance and either remove the duplicate content items, or ensure the import has imported the correct version of the content item.
Level: 1

Type: WARNING

Impact: Other

WCS-07919: The content item {0} was not imported. The filename {1} contains an invalid characters.

Cause: The filename of the file being imported contains invalid characters, the document can not be checked in.

Action: Check the logs for more information.
Level: 1

Type: WARNING

Impact: Other

WCS-07919: The content item {0} was not imported. The filename {1} contains an invalid characters.

Cause: The filename of the file being imported contains invalid characters, the document can not be checked in.

Action: Check the logs for more information.
Level: 1

Type: WARNING

Impact: Other

WCS-07920: An error occurred loading the names of additional content attributes.

Cause: An error occurred loading the names of additional content attributes.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07920: An error occurred loading the names of additional content attributes.

Cause: An error occurred loading the names of additional content attributes.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07923: No primary content repository connection.

Cause: There is no content repository connection name set as the primary connection.

Action: Set a content repository connection as the primary connection.
Level: 1

Type: ERROR

Impact: Other

WCS-07923: No primary content repository connection.

Cause: There is no content repository connection name set as the primary connection.

Action: Set a content repository connection as the primary connection.
Level: 1

Type: ERROR

Impact: Other

WCS-07924: Error checking foldering service (Framework Folders/folders_g) of content server.

Cause: An error occurred while checking doclib foldering service implementation of content server.

Action: Check the underlying exception and content repository log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07925: Foldering service from content server {0} and Portal Server Configuration {1} do not match.

Cause: Value stored in WC_PORTAL_PROPERTIES table and response from content server is not same.

Action: Contact System Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-07926: Framework Folders version on Oracle WebCenter Content Server is not supported for Oracle WebCenter Portal. The supported versions are {0} and later.

Cause: Framework Folders version on Oracle WebCenter Content Server is not supported for Oracle WebCenter Portal. The supported versions are 2.1 and later.

Action: Contact System Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-07927: Error creating system library list.

Cause: An error occurred while creating system library list from Oracle WebCenter Content Server.

Action: Check the underlying exception in WebCenter Portal and Content Server logs for additional information.
Level: 1

Type: ERROR

Impact: Other

WCS-07928: Failed to get document rules from Oracle WebCenter Content Server.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07929: Failed to add document rule {0} to Oracle WebCenter Content Server.

Cause:

Action:
Level: 1

Type: WARNING

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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-08024: Input parameter value "{0}" supplied is invalid.

Cause: Invalid input parameter value is supplied.

Action: Provide valid values for the input parameters.
Level: 1

Type: ERROR

Impact: Other

WCS-08025: You do not have permission to see forums for this portal.

Cause: User is not authorized to access the forum.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08025: You do not have permission to see forums for this portal.

Cause: User is not authorized to access the forum.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08026: You do not have permission to see recent topics for this portal.

Cause: User is not authorized to access the recent topics.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08026: You do not have permission to see recent topics for this portal.

Cause: User is not authorized to access the recent topics.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08027: You do not have permission to see popular topics for this portal.

Cause: User is not authorized to access the popular topics.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08027: You do not have permission to see popular topics for this portal.

Cause: User is not authorized to access the popular topics.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08028: {0} not accessible.

Cause: Contact your administrator for access.

Action: Check if data exist or check for appropriate permissions.
Level: 1

Type: WARNING

Impact: Other

WCS-08028: {0} not accessible.

Cause: Contact your administrator for access.

Action: Check if data exist or check for appropriate permissions.
Level: 1

Type: WARNING

Impact: Other

WCS-08029: Could not connect to the configured discussions server.

Cause: Configured discussion server is not reachable.

Action: Check if server details are correct or contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08029: Could not connect to the configured discussions server.

Cause: Configured discussion server is not reachable.

Action: Check if server details are correct or contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08201: Not able to create forum configuration file for community "{0}" due to : {1}.

Cause: Possible failure creating the category or forum, or an issue with the MDS write operation.

Action: Contact your system administrator or read the discussion forum service configuration documentation for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-09026: Error processing the message.

Cause: The message might have been sent with improper encoding.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-09027: The number of recipients for the mail:{0} has exceeded the maximum limit:{1} set by the space administrator.

Cause: The number of recipients for the mail has exceeded the maximum limit set by the space administrator.

Action: Reduce the number of recipients or contact the space administrator to change the maximum limit
Level: 1

Type: ERROR

Impact: Other

WCS-09027: The number of recipients for the mail:{0} has exceeded the maximum limit:{1} set by the space administrator.

Cause: The number of recipients for the mail has exceeded the maximum limit set by the space administrator.

Action: Reduce the number of recipients or contact the space administrator to change the maximum limit
Level: 1

Type: ERROR

Impact: Other

WCS-09201: Distribution list "{0}" already exists.

Cause: A distribution list with the supplied name already exists.

Action: Create the distribution list with a different name.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-09520: Expiry date cannot be earlier than start date.

Cause: Expiry date is specified to be earlier than start date.

Action: Specify expiry date to be later than start date.
Level: 1

Type: WARNING

Impact: Other

WCS-09521: Not able to query data from SQL Connection.

Cause: Possible reasons: The database is down or invalid SQL Connection configuration in the DataSource.

Action: Configure the correct SQL Connection in the DataSource.
Level: 1

Type: ERROR

Impact: Other

WCS-09521: Not able to query data from SQL Connection.

Cause: Possible reasons: The database is down or invalid SQL Connection configuration in the DataSource.

Action: Configure the correct SQL Connection in the DataSource.
Level: 1

Type: ERROR

Impact: Other

WCS-09522: Announcement parent not accessible.

Cause: Contact your administrator for access to announcements.

Action: Check if announcements parent exists or user has permissions to access announcements.
Level: 1

Type: WARNING

Impact: Other

WCS-09522: Announcement parent not accessible.

Cause: Contact your administrator for access to announcements.

Action: Check if announcements parent exists or user has permissions to access announcements.
Level: 1

Type: WARNING

Impact: Other

WCS-09523: Could not connect to the configured discussions server.

Cause: Configured discussion server is not reachable.

Action: Check if server details are correct or contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-09523: Could not connect to the configured discussions server.

Cause: Configured discussion server is not reachable.

Action: Check if server details are correct or contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-09601: Not able to create announcement configuration file for community {0} due to : {1}.

Cause: Possible failure creating category or announcement or an issue with the MDS write operation.

Action: Contact your system administrator or read the announcement service configuration documentation for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-11020: Error storing uploaded file content.

Cause: Uploaded file could not be stored.

Action: Check other errors for cause.
Level: 1

Type: WARNING

Impact: Other

WCS-11021: Error verifying CSRF token: ADF session scope token null.

Cause: CSRF could not be verified as session CSRF null.

Action: Contact your Oracle Support representative.
Level: 1

Type: WARNING

Impact: Other

WCS-11022: CSRF token check fail, session and request token mis-match.

Cause: CSRF verification failed as request and session tokens do not match.

Action: Contact your Oracle Support representative.
Level: 1

Type: WARNING

Impact: Other

WCS-11023: CSRF token check fail, session and multi-part form token mis-match. Form: {0} Session {1}

Cause: CSRF verification failed as session and multipart form tokens do not match.

Action: Contact your Oracle Support representative.
Level: 1

Type: WARNING

Impact: Other

WCS-11024: Cannot write file as CSRF not verified.

Cause: File write prohibitied as CSRF not verified.

Action: Contact your Oracle Support representative.
Level: 1

Type: WARNING

Impact: Other

WCS-11025: Error while writing response..

Cause: An error occured on sending upload response.

Action: Check other errors for cause.
Level: 1

Type: WARNING

Impact: Other

WCS-12001: Following services are not configured: {0}. Configure these services and retry the operation.

Cause: Portals imported requires some services that are not configured in the instance.

Action: Ensure that the specified services are included and configured in the application and restart the import process.
Level: 1

Type: ERROR

Impact: Other

WCS-12001: No handlers could be found for services with IDs: {0}.

Cause: Handlers enable services to manage their data and metadata in the manner best suited to each service. Handlers that were recorded by the system during export were not available on import.

Action: Ensure that the specified services are included and configured in the application and restart the import process.
Level: 1

Type: ERROR

Impact: Other

WCS-12002: The handler found in the classpath at run time cannot process the data or metadata of the archive: {0}.

Cause: Handlers enable services to manage their data and metadata in the manner best suited to each service. The version of the handler used during import was not compatible with the version of the handler used while creating the data or metadata on export.

Action: Include compatible versions of handlers in the application and restart the import process.
Level: 1

Type: ERROR

Impact: Other

WCS-12002: The handler found in the classpath at run time cannot process the data or metadata of the archive: {0}.

Cause: Handlers enable services to manage their data and metadata in the manner best suited to each service. The version of the handler used during import was not compatible with the version of the handler used while creating the data or metadata on export.

Action: Include compatible versions of handlers in the application and restart the import process.
Level: 1

Type: ERROR

Impact: Other

WCS-12003: The required handlers are not found: {0}.

Cause: Handlers enable services to manage their data and metadata in the manner best suited to each service. Not all handlers that were used while creating this archive could be found during the import.

Action: Ensure that the specified services are included and configured in the application and restart the import process.
Level: 1

Type: ERROR

Impact: Other

WCS-12003: The required handlers are not found: {0}.

Cause: Handlers enable services to manage their data and metadata in the manner best suited to each service. Not all handlers that were used while creating this archive could be found during the import.

Action: Ensure that the specified services are included and configured in the application and restart the import process.
Level: 1

Type: ERROR

Impact: Other

WCS-12004: Unable to retrieve the JAXB bean for the export/import document in MDS.

Cause: An error occurred in the MDS configuration of the application.

Action: Check the MDS configuration files of the application.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-12007: Scope with name {0} already exists in the import destination and it does not match with the scope being imported.

Cause: A scope with the specified name already exists for the current application instance. This caused a conflict between the source and target instances.

Action: Delete the scope from the current application instance and reattempt the import.
Level: 1

Type: ERROR

Impact: Other

WCS-12008: The export archive is from an older version of WebCenter Portal and is not compatible with the current version.

Cause: The export archive is created using an older version. This archive cannot be imported into the current version of WebCenter Portal.

Action: Reattempt import with a newer export archive.
Level: 1

Type: ERROR

Impact: Other

WCS-12008: The export archive is from an older application and is not compatible with the current version of application.

Cause: The export archive is created using an older version. This archive cannot be imported into the current version of application.

Action: Reattempt import with a newer export archive.
Level: 1

Type: ERROR

Impact: Other

WCS-12009: The Lifecycle Manager MBean cannot be deregistered.

Cause: There are numerous possible reasons for this failure.

Action: For information, review other messages in the log file and the reported exception stacks.
Level: 1

Type: WARNING

Impact: Other

WCS-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-12010: The Lifecycle Manager MBean cannot be created and registered. This problem will not prevent the application from running. However, the Lifecycle Manager will be unavailable.

Cause: There are numerous possible reasons for this failure.

Action: For information, review other messages in the log file and the reported exception stacks.
Level: 1

Type: WARNING

Impact: Other

WCS-12012: Information related to run time MBeans cannot be saved in the ADFContext application scope.

Cause: The system failed to store data in the ADFContext application scope. Lifecycle functions may not be available.

Action: Review the log files to see if there are any other problems which may have resulted in the ADFContext object becoming unusable.
Level: 1

Type: WARNING

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-12046: MDSException while creating lifecycle document in MDS transfer source

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12047: The import archive file does not contain a metadata archive.

Cause: The supplied file to import was not a valid export archive.

Action: Retry the import operation with a valid export archive.
Level: 1

Type: ERROR

Impact: Other

WCS-12047: The import archive file does not contain a metadata archive.

Cause: The supplied file to import was not a valid export archive.

Action: Retry the import operation with a valid export archive.
Level: 1

Type: ERROR

Impact: Other

WCS-12048: FileNotFoundException extracting metadata transport archive

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Resolve any hardware or file system errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-12063: MDSException occurred while removing lock {0}:{1}

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12064: A lock is blocking application import.

Cause: Another operation was being performed that prevented the import.

Action: Retry the import operation after the other operation is complete.
Level: 1

Type: ERROR

Impact: Other

WCS-12064: A lock is blocking application import.

Cause: Another operation was being performed that prevented the import.

Action: Retry the import operation after the other operation is complete.
Level: 1

Type: ERROR

Impact: Other

WCS-12065: A lock is blocking application import.

Cause: Another operation was being performed that prevented the import.

Action: Retry the import operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12065: A lock is blocking application import.

Cause: Another operation was being performed that prevented the import.

Action: Retry the import operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12066: MDSException while creating application import lock

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-12094: MDSException while constructing metadata store for MDS transfer

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12095: Import archive file does not exist or could not be read.

Cause: The specified file could not be found either because it does not exist or does not have the correct access permissions.

Action: Check that the path is correct, the file exists and has the appropriate access permissions.
Level: 1

Type: ERROR

Impact: Other

WCS-12095: Import archive file does not exist or could not be read.

Cause: The specified file could not be found either because it does not exist or does not have the correct access permissions.

Action: Check that the path is correct, the file exists and has the appropriate access permissions.
Level: 1

Type: ERROR

Impact: Other

WCS-12096: A lock is blocking application export.

Cause: Another operation was being performed that prevented the export.

Action: Retry the export operation after the other operation is complete.
Level: 1

Type: ERROR

Impact: Other

WCS-12096: A lock is blocking application export.

Cause: Another operation was being performed that prevented the export.

Action: Retry the export operation after the other operation is complete.
Level: 1

Type: ERROR

Impact: Other

WCS-12097: A lock is blocking application export.

Cause: Another operation was being performed that prevented the export.

Action: Retry the export operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12097: A lock is blocking application export.

Cause: Another operation was being performed that prevented the export.

Action: Retry the export operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12098: MDSException while creating application export lock

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-12101: Unable to find data source

Cause: The data source hasn't been configured

Action: Configure the data source
Level: 1

Type: ERROR

Impact: Other

WCS-12102: An exception occurred while refreshing lock {0}:{1}

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12102: An exception occurred while refreshing lock {0}:{1}

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12103: Unexpected RuntimeException performing MDS transfer.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12103: Unexpected RuntimeException performing MDS transfer.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12104: Unexpected exception occurred while exporting portlet producer information. The producer may be down or unavailable.

Cause: The possible causes could be the portlet producer is down or unavailable, errors from the portlet producer, or application configuration.

Action: Check that the portlet producers are available, and then retry the export. Review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12104: Unexpected exception occurred while exporting portlet producer information. The producer may be down or unavailable.

Cause: The possible causes could be the portlet producer is down or unavailable, errors from the portlet producer, or application configuration.

Action: Check that the portlet producers are available, and then retry the export. Review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12106: Document {0} has been excluded from the export set.

Cause: The path of the document exceeds file system constraints and therefore cannot be exported.

Action: None
Level: 1

Type: ERROR

Impact: Other

WCS-12106: Document {0} has been excluded from the export set.

Cause: The path of the document exceeds file system constraints and therefore cannot be exported.

Action: None
Level: 1

Type: ERROR

Impact: Other

WCS-12107: InvalidReferenceException constructing MDS rename plan for upgrade.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12107: InvalidReferenceException constructing MDS rename plan for upgrade.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12108: MDSException performing MDS rename for upgrade.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12108: MDSException performing MDS rename for upgrade.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12109: MDSException while committing metadata changes for upgrade.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12109: MDSException while committing metadata changes for upgrade.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12110: Unable to import Scope {0} under Scope {0}

Cause: Unable to import scope under itself

Action: Import the scope either as a root level scope or specify a different parent for the scope.
Level: 1

Type: ERROR

Impact: Other

WCS-12110: Unable to import Scope {0} under Scope {0}

Cause: Unable to import scope under itself

Action: Import the scope either as a root level scope or specify a different parent for the scope.
Level: 1

Type: ERROR

Impact: Other

WCS-12111: Unable to import {0} as a root level scope as it inherits security.

Cause: Unable to import scope as a root level scope as it inherits security.

Action: Import the scope as a subscope and not as a root level scope.
Level: 1

Type: ERROR

Impact: Other

WCS-12111: Unable to import {0} as a root level scope as it inherits security.

Cause: Unable to import scope as a root level scope as it inherits security.

Action: Import the scope as a subscope and not as a root level scope.
Level: 1

Type: ERROR

Impact: Other

WCS-12112: The parent scope {0} does not exist

Cause: Unable to import as the parent scope does not exist

Action: Import the scope either as a root level scope or specify a different parent for the scope.
Level: 1

Type: ERROR

Impact: Other

WCS-12112: The parent scope {0} does not exist

Cause: Unable to import as the parent scope does not exist

Action: Import the scope either as a root level scope or specify a different parent for the scope.
Level: 1

Type: ERROR

Impact: Other

WCS-12113: Export operation aborted due to the following reasons. {0}

Cause: Export operation aborted

Action: Retry the operation fixing the cause of failure
Level: 1

Type: ERROR

Impact: Other

WCS-12113: Export operation aborted due to the following reasons. {0}

Cause: Export operation aborted

Action: Retry the operation fixing the cause of failure
Level: 1

Type: ERROR

Impact: Other

WCS-12114: Failed to fetch the handler due to invalid resource type - {0}

Cause: Invalid Resource type is passed during import.

Action: Retry the operation with the correct resource type.
Level: 1

Type: ERROR

Impact: Other

WCS-12114: Failed to fetch the handler due to invalid resource type - {0}

Cause: Invalid Resource type is passed during import.

Action: Retry the operation with the correct resource type.
Level: 1

Type: ERROR

Impact: Other

WCS-12115: Portal Export operation aborted due to the following reasons. {0}

Cause: Backup operation aborted

Action: Retry the operation fixing the cause of failure
Level: 1

Type: ERROR

Impact: Other

WCS-12115: Portal Export operation aborted due to the following reasons. {0}

Cause: Backup operation aborted

Action: Retry the operation fixing the cause of failure
Level: 1

Type: ERROR

Impact: Other

WCS-12116: Exception while creating the export label

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12116: Exception while creating the export label

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12117: Portal {0} already exists. If you want to overwrite the portal use the ''overwrite'' option.

Cause: Portal already exists.

Action: If you want to overwrite the existing portal, use the ''overwrite'' option.
Level: 1

Type: ERROR

Impact: Other

WCS-12117: Portal {0} already exists. If you want to overwrite the portal use the 'overwrite' option.

Cause: Portal already exists.

Action: If you want to overwrite the existing portal, use the 'overwrite' option.
Level: 1

Type: ERROR

Impact: Other

WCS-12118: A SQL exception {0} was caught while closing the resultset.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12119: Unable to upload as the archive does not contain a shared asset.

Cause: The asset you are trying to upload belongs to a specific portal, it is not a shared asset.

Action: Verify which portal owns the asset and then upload the asset to that portal.
Level: 1

Type: ERROR

Impact: Other

WCS-12120: Unable to upload the asset as the archive does not contain an asset that belongs to this portal.

Cause: The asset you are trying to upload belongs to a different portal.

Action: Verify which portal owns the asset and then upload the asset to that portal.
Level: 1

Type: ERROR

Impact: Other

WCS-12121: A lock is blocking the deployment of portal: {0}.

Cause: Another operation was being performed that prevented the deployment.

Action: Retry the deployment operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12122: A lock is blocking the propagation of portal: {0}.

Cause: Another operation was being performed that prevented the propagation.

Action: Retry the propagation operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12123: Unable to deploy the portal "{0}" because this portal is currently being deployed to the target "{1}" by "{2}". Try again later.

Cause: Deployment of the specified portal to the specific target portal server was being performed that prevented this current deployment operation.

Action: Retry the deployment operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12124: Unable to deploy the portal "{0}" because changes for this portal are currently being propagated to the target "{1}" by "{2}". Try again later.

Cause: Propagation of the specified portal to the specific target portal server was being performed that prevented this current deployment operation.

Action: Retry the deployment operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12125: Changes for portal "{0}" cannot be propagated because this portal is currently being deployed to the target "{1}" by "{2}". Try again later.

Cause: Deployment of the specified portal to the specific target portal server was being performed that prevented this current propagation operation.

Action: Retry the propagation operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12126: Changes for portal "{0}" cannot be propagated because changes for this portal are currently being propagated to the target "{1}" by "{2}". Try again later.

Cause: Propagation of the specified portal to the specific target portal server was being performed that prevented this current propagation operation.

Action: Retry the propagation operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12127: MDSException while creating portal deployment 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-12128: An exception occurred while exporting the persistence data.

Cause: An exception was thrown while exporting the persistence data for the portal.

Action: Retry the operation. If the exception occurs again, review the full exception stack for details.
Level: 1

Type: ERROR

Impact: Other

WCS-12129: An exception occurred while importing the persistence data.

Cause: An exception was thrown while importing the persistence data for the portal.

Action: Retry the operation. If the exception occurs again, review the full exception stack for details.
Level: 1

Type: ERROR

Impact: Other

WCS-12130: No user created assets of type "{0}" exist in the portal "{1}" for export.

Cause: No user created assets of the specified type exist in the portal for export.

Action: Refresh the list of assets to see if the assets you are attempting to still exist.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12131: No user created global assets of type "{0}" exist for export.

Cause: No user created global assets of the specified type exist for export.

Action: Refresh the list of assets to see if the assets you are attempting to still exist.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12132: Changes for portal "{0}" cannot be propagated because Oracle WebCenter Content Server is not configured properly.

Cause: Propagation of the specified portal failed because Oracle WebCenter Content Server has not been configured properly.

Action: Retry the propagation operation after fixing the Oracle WebCenter Content Server configuration on the Oracle WebCenter Portal Server instance.
Level: 1

Type: ERROR

Impact: Other

WCS-12133: Specify a valid name for the asset archive. Usage of special character / or \ is not allowed.

Cause: Usage of special character / or \ is not allowed.

Action: Specify a valid name for the asset archive.
Level: 1

Type: ERROR

Impact: Other

WCS-12134: Invalid asset archive extension provided: {0}. Specify a valid name for the asset archive using the file extension {1}.

Cause: Invalid asset archive extension specified.

Action: Specify a valid name for the asset archive using the file extension ''.aar''.
Level: 1

Type: ERROR

Impact: Other

WCS-12135: Specify a valid name for the asset archive using the file extension {0}.

Cause: Invalid file extension specified.

Action: Specify a valid name for the asset archive using the file extension ''.aar''.
Level: 1

Type: ERROR

Impact: Other

WCS-12136: An exception occurred while finding the conflicting assets.

Cause: An exception was thrown while finding the conflicting assets.

Action: Retry the operation. If the exception occurs again, review the full exception stack for details.
Level: 1

Type: ERROR

Impact: Other

WCS-12900: Invalid portal template archive extension provided: {0}. Specify a valid name for the portal template archive and use the file extension {1}.

Cause: Invalid portal template archive extension specified.

Action: Specify a valid name for the portal template archive and use the file extension '.par'
Level: 1

Type: ERROR

Impact: Other

WCS-12901: An unexpected error has occurred, unable to save the archive: {0}

Cause: Unexpected erro occurred while saving the archive.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-12902: Specify an archive that exists on the server.

Cause: Unable to locate archive for import.

Action: Specify a valid archive that exists on the server and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-12903: An unexpected error has occurred, unable to complete the import process.

Cause: Unable to complete the import process.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-12904: Unable to upload archive from the local file system.

Cause: Unable to upload the archive from the local file system.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-12905: Cannot save the export archive to the local file system because the file size exceeds the maximum value allowed.

Cause: Cannot save the export archive to the local file system because the file size exceeds the maximum value allowed.

Action: Save the archive to a server and then transfer the file separately.
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-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-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-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-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-12953: A listener cannot be registered to generate notification about the progress of the export. The export will continue but notification will not be generated on its progress.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12955: The notification arrived out of sequence. Latest sequence:{0}; sequence of this notification:{1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12955: The notification arrived out of sequence. Latest sequence:{0}; sequence of this notification:{1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12957: Exception occurred while importing data. No data imported.

Cause: The issue may be due to a hardware error or an application configuration error.

Action: Review other messages in the log file and the reported exception stacks for additional information. Resolve any application configuration or hardware errors.
Level: 1

Type: WARNING

Impact: Other

WCS-12957: Exception occurred while importing data. No data imported.

Cause: The issue may be due to a hardware error or an application configuration error.

Action: Review other messages in the log file and the reported exception stacks for additional information. Resolve any application configuration or hardware errors.
Level: 1

Type: WARNING

Impact: Other

WCS-12958: Import failed with errors.

Cause: The issue may be due to a hardware error or an application configuration error.

Action: Review other messages in the log file and the reported exception stacks for additional information. Resolve any application configuration or hardware errors.
Level: 1

Type: ERROR

Impact: Other

WCS-12958: Import failed with errors.

Cause: The issue may be due to a hardware error or an application configuration error.

Action: Review other messages in the log file and the reported exception stacks for additional information. Resolve any application configuration or hardware errors.
Level: 1

Type: ERROR

Impact: Other

WCS-12959: Export failed with errors.

Cause: The issue may be due to a hardware error or an application configuration error.

Action: Review other messages in the log file and the reported exception stacks for additional information. Resolve any application configuration or hardware errors.
Level: 1

Type: ERROR

Impact: Other

WCS-12959: Export failed with errors.

Cause: The issue may be due to a hardware error or an application configuration error.

Action: Review other messages in the log file and the reported exception stacks for additional information. Resolve any application configuration or hardware errors.
Level: 1

Type: ERROR

Impact: Other

WCS-12980: Service {0} has not been provisioned for Scope {1}.

Cause: The Service has not been provisioned for the specified Scope.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-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-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-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-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-12985: An error occurred invoking isProvisioned for service {0}.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: WARNING

Impact: Other

WCS-12986: An error occurred invoking isEnabled for service {0}.

Cause: The possible causes could be coding or application configuration.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: WARNING

Impact: Other

WCS-12986: An error occurred invoking isEnabled for service {0}.

Cause: The possible causes could be coding or application configuration.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: WARNING

Impact: Other

WCS-14001: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-14025: An error occurred accessing the WebCenter metadata repository.

Cause: An error occurred accessing the repository.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-14026: List column values were converted or deleted based on list column changes during import: scope={0}, list={1}, column={2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-14026: List column values were converted or deleted based on list column changes during import: scope={0}, list={1}, column={2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-14027: List are not enabled for this portal or a parent portal.

Cause: Lists are not enabled in this portal.

Action: Enable lists if required by this portal.
Level: 1

Type: WARNING

Impact: Other

WCS-14027: List are not enabled for this portal or a parent portal.

Cause: Lists are not enabled in this portal.

Action: Enable lists if required by this portal.
Level: 1

Type: WARNING

Impact: Other

WCS-14028: Enabling lists failed.

Cause: An error occurred enabling lists.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-14028: Enabling lists failed.

Cause: An error occurred enabling lists.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-14029: Lists not enabled for portal {0}.

Cause: Lists not enabled for the specified portal.

Action: Enable lists for the specified portal.
Level: 1

Type: ERROR

Impact: Other

WCS-14029: Lists not enabled for portal {0}.

Cause: Lists not enabled for the specified portal.

Action: Enable lists for the specified portal.
Level: 1

Type: ERROR

Impact: Other

WCS-14030: An error occurred registering the WebCenter list visualizations.

Cause: An error occurred registering visualizations..

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-14031: An Object of type {0} with id={1} could not be deleted.

Cause: The specified object could not be deleted. This may be due to the a constraint.

Action: Check the constraints.
Level: 1

Type: ERROR

Impact: Other

WCS-14501: The list was not found.

Cause: The list could not be found.

Action: Remove the list view for the invalid list from the page.
Level: 1

Type: ERROR

Impact: Other

WCS-14501: The list was not found.

Cause: The list could not be found.

Action: Remove the list view for the invalid list from the page.
Level: 1

Type: ERROR

Impact: Other

WCS-14502: Another user deleted the row while you modified it. Discard any unsaved changes, then refresh the list.

Cause: Another user deleted the row while you modified it.

Action: Discard any unsaved changes, then refresh the list.
Level: 1

Type: ERROR

Impact: Other

WCS-14502: Another user deleted the row while you modified it. Discard any unsaved changes, then refresh the list.

Cause: Another user deleted the row while you modified it.

Action: Discard any unsaved changes, then refresh the list.
Level: 1

Type: ERROR

Impact: Other

WCS-14503: Another user modified a row while you modified it. Discard any unsaved changes, then refresh the list.

Cause: Another user modified a row while you modified it.

Action: Discard any unsaved changes, then refresh the list.
Level: 1

Type: ERROR

Impact: Other

WCS-14503: Another user modified a row while you modified it. Discard any unsaved changes, then refresh the list.

Cause: Another user modified a row while you modified it.

Action: Discard any unsaved changes, then refresh the list.
Level: 1

Type: ERROR

Impact: Other

WCS-14504: Another user deleted the list after you displayed it. Discard any unsaved changes, then refresh the list.

Cause: Another user deleted the list after you displayed it.

Action: Discard any unsaved changes, then refresh the list.
Level: 1

Type: ERROR

Impact: Other

WCS-14504: Another user deleted the list after you displayed it. Discard any unsaved changes, then refresh the list.

Cause: Another user deleted the list after you displayed it.

Action: Discard any unsaved changes, then refresh the list.
Level: 1

Type: ERROR

Impact: Other

WCS-14505: Another user modified this list after you displayed it. Discard any unsaved changes, then refresh the list.

Cause: Another user modified this list after you displayed it.

Action: Discard any unsaved changes, then refresh the list.
Level: 1

Type: ERROR

Impact: Other

WCS-14505: Another user modified this list after you displayed it. Discard any unsaved changes, then refresh the list.

Cause: Another user modified this list after you displayed it.

Action: Discard any unsaved changes, then refresh the list.
Level: 1

Type: ERROR

Impact: Other

WCS-14506: Invalid minimum/maximum range

Cause: Minimum value must be less than or equal to maximum value.

Action: Modify the minimum value or maximum value.
Level: 1

Type: ERROR

Impact: Other

WCS-14506: Invalid minimum/maximum range

Cause: Minimum value must be less than or equal to maximum value.

Action: Modify the minimum value or maximum value.
Level: 1

Type: ERROR

Impact: Other

WCS-14507: Default value is out of range

Cause: Default value must be between the minimum and maximum values.

Action: Modify the default value, minimum value, or maximum value.
Level: 1

Type: ERROR

Impact: Other

WCS-14507: Default value is out of range

Cause: Default value must be between the minimum and maximum values.

Action: Modify the default value, minimum value, or maximum value.
Level: 1

Type: ERROR

Impact: Other

WCS-14508: An error occurred accessing the WebCenter repository.

Cause: An error occurred accessing the repository.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-14508: An error occurred accessing the WebCenter repository.

Cause: An error occurred accessing the repository.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-14509: Your permission to perform this operation was revoked. Refresh the list and discard unsaved changes.

Cause: Your permission to perform this operation was revoked.

Action: Request permission to perform this operation.
Level: 1

Type: ERROR

Impact: Other

WCS-14509: Your permission to perform this operation was revoked. Refresh the list and discard unsaved changes.

Cause: Your permission to perform this operation was revoked.

Action: Request permission to perform this operation.
Level: 1

Type: ERROR

Impact: Other

WCS-14510: The Lists service was disabled, preventing you from performing this operation. Refresh the list and discard unsaved changes.

Cause: The Lists service was disabled, preventing you from performing this operation.

Action: Enable the Lists service.
Level: 1

Type: ERROR

Impact: Other

WCS-14510: The Lists service was disabled, preventing you from performing this operation. Refresh the list and discard unsaved changes.

Cause: The Lists service was disabled, preventing you from performing this operation.

Action: Enable the Lists service.
Level: 1

Type: ERROR

Impact: Other

WCS-14514: An unexpected error occurred. Please retry the operation.

Cause: An unexpected error occurred.

Action: Retry the operation. If the problem persists, contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-14516: The WebCenter metadata repository was temporarily unavailable. Please retry the operation.

Cause: The connection to the WebCenter metadata repository failed.

Action: Retry the operation. If the problem persists, contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-14517: Another user deleted the list after you displayed it. Discard any unsaved changes, then click Close to exit list edit mode.

Cause: Another user deleted the list after you displayed it.

Action: Discard any unsaved changes, then click Close to exit list edit mode.
Level: 1

Type: ERROR

Impact: Other

WCS-14517: Another user deleted the list after you displayed it. Discard any unsaved changes, then click Close to exit list edit mode.

Cause: Another user deleted the list after you displayed it.

Action: Discard any unsaved changes, then click Close to exit list edit mode.
Level: 1

Type: ERROR

Impact: Other

WCS-14518: Another user deleted the list. Click Close to exit list edit mode.

Cause: Another user deleted the list.

Action: Click Close to exit list edit mode.
Level: 1

Type: ERROR

Impact: Other

WCS-14518: Another user deleted the list. Click Close to exit list edit mode.

Cause: Another user deleted the list.

Action: Click Close to exit list edit mode.
Level: 1

Type: ERROR

Impact: Other

WCS-14519: The list row was not found.

Cause: The list row could not be found.

Action: None.
Level: 1

Type: ERROR

Impact: Other

WCS-14519: The list row was not found.

Cause: The list row could not be found.

Action: None.
Level: 1

Type: ERROR

Impact: Other

WCS-14522: Lists are disabled, preventing you from performing this operation. Enable lists to continue making changes.

Cause: Lists are disabled, preventing you from performing this operation.

Action: Enable lists.
Level: 1

Type: ERROR

Impact: Other

WCS-14522: Lists are disabled, preventing you from performing this operation. Enable lists to continue making changes.

Cause: Lists are disabled, preventing you from performing this operation.

Action: Enable lists.
Level: 1

Type: ERROR

Impact: Other

WCS-18001: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-18421: Message cannot be added to Message Board.

Cause: User is not authorized to add message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18422: Failed to retrieve Message Board message

Cause: Message does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18422: Failed to retrieve Message Board message

Cause: Message does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18423: Failed to find the portal of the message board.

Cause: The portal doesn't exist.

Action: Contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18423: Failed to find the portal of the message board.

Cause: The portal doesn't exist.

Action: Contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18424: Failed to find the user of the message board.

Cause: The user doesn't exist.

Action: Contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18424: Failed to find the user of the message board.

Cause: The user doesn't exist.

Action: Contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18425: Failed to attach file to selected portal.

Cause: The portal does not exist or does not have document services configured.

Action: Contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18425: Failed to attach file to selected portal.

Cause: The portal does not exist or does not have document services configured.

Action: Contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18451: Unexpected error getting preference.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18451: Unexpected error getting preference.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18452: Unexpected error saving preference.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18452: Unexpected error saving preference.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18453: Encountered exception: {0}. For diagnosis, turn on the logging level to FINEST and retry the operation. Details about the current state: {1}.

Cause: An unexpected error occurred.

Action: To diagnose the error, turn on the logging level to FINEST and retry the operation.
Level: 1

Type: WARNING

Impact: Other

WCS-18453: Encountered exception: {0}. For diagnosis, turn on the logging level to FINEST and retry the operation. Details about the current state: {1}.

Cause: An unexpected error occurred.

Action: To diagnose the error, turn on the logging level to FINEST and retry the operation.
Level: 1

Type: WARNING

Impact: Other

WCS-18501: Error retrieving {0}''s Profile

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18501: Error retrieving the Profile

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18502: User: {0} not found in identity store.

Cause: An unexpected error occurred.

Action: Check if the specified user exists in the configured identity store and 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-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-18504: unexpected error operating on personal status note

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18505: unexpected error saving profile

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18506: User does not have the privilege required to access the user profile.

Cause: Either the system policy or the target user's access control settings restrict the current user from performing this operation.

Action: Contact the Administrator to grant the required permission, or contact the target user to allow access.
Level: 1

Type: ERROR

Impact: Other

WCS-18506: User does not have the privilege required to access the user profile.

Cause: Either the system policy or the target user's access control settings restrict the current user from performing this operation.

Action: Contact the Administrator to grant the required permission, or contact the target user to allow access.
Level: 1

Type: ERROR

Impact: Other

WCS-18507: Insufficient Privilege.

Cause: Cannot Edit Profile.

Action: Contact Webcenter Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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: The photo may not have been saved. Please refresh to find out and then retry the operation. If the issue persists 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-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-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-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-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-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-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-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-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-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-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-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-18525: Unexpected error saving attribute: {0}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with the error on the log.
Level: 1

Type: ERROR

Impact: Other

WCS-18526: User does not have the privilege required for updating the user profile

Cause: The system policy restricts the current user from updating the user profile.

Action: Contact the Administrator to obtain the required permission.
Level: 1

Type: ERROR

Impact: Other

WCS-18526: User does not have the privilege required for updating the user profile

Cause: The system policy restricts the current user from updating the user profile.

Action: Contact the Administrator to obtain the required permission.
Level: 1

Type: ERROR

Impact: Other

WCS-18527: The image file {0} you tried to upload was invalid. Provide a valid image file.

Cause: Unable to upload the image as the file is null or invalid.

Action: Upload a valid image file
Level: 1

Type: ERROR

Impact: Other

WCS-18527: The image file {0} you tried to upload was invalid. Provide a valid image file.

Cause: Unable to upload the image as the file is null or invalid.

Action: Upload a valid image file
Level: 1

Type: ERROR

Impact: Other

WCS-18528: Unexpected error instantiating object.

Cause: Unexpected error instantiating object.

Action: contact the administrator
Level: 1

Type: ERROR

Impact: Other

WCS-18528: Unexpected error instantiating object.

Cause: Unexpected error instantiating object.

Action: contact the administrator
Level: 1

Type: ERROR

Impact: Other

WCS-18529: Error instantiating profile (user name: {0}, GUID: {1})

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18529: Error instantiating profile (user name: {0}, GUID: {1})

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18530: Unable to retrieve display name for profile (user name: {0}, GUID: {1}) in locale {2}. For diagnosis, turn on the logging level to FINEST and retry the operation. Error summary: {3}.

Cause: An unexpected error occurred.

Action: To diagnose the error, turn on the logging level to FINEST and retry the operation.
Level: 1

Type: WARNING

Impact: Other

WCS-18530: Unable to retrieve display name for profile (user name: {0}, GUID: {1}) in locale {2}. For diagnosis, turn on the logging level to FINEST and retry the operation. Error summary: {3}.

Cause: An unexpected error occurred.

Action: To diagnose the error, turn on the logging level to FINEST and retry the operation.
Level: 1

Type: WARNING

Impact: Other

WCS-18531: Error navigating the hierarchy

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18531: Error navigating the hierarchy

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18532: Unexpected error writing vcard

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18532: Unexpected error writing vcard

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18533: Unexpected error retrieving reporting chain

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18533: Unexpected error retrieving reporting chain

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18534: Unexpected error searching user profiles

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18534: Unexpected error searching user profiles

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18535: User: {0} not found in identity store or user does not have the required privilege for updating the user profile.

Cause: Either user is not available in the user repository or system policy restriction is applied.

Action: contact the administrator
Level: 1

Type: ERROR

Impact: Other

WCS-18535: User: {0} not found in identity store or user does not have the required privilege for updating the user profile.

Cause: Either user is not available in the user repository or system policy restriction is applied.

Action: contact the administrator
Level: 1

Type: ERROR

Impact: Other

WCS-18536: User Class type not expected, found: {0} expected{1}.

Cause: The User instance found in the cache is not of the expected Class type.

Action: Check if the Profile Service Lifecycle Listener is executed which sets the appropriate UserFactory.
Level: 1

Type: ERROR

Impact: Other

WCS-18536: User Class type not expected, found: {0} expected{1}.

Cause: The User instance found in the cache is not of the expected Class type.

Action: Check if the Profile Service Lifecyle Listener is executed which sets the appropriate UserFactory.
Level: 1

Type: ERROR

Impact: Other

WCS-18537: Error updating {0} with {1} and {2}.

Cause: The cause of this error could be MetadataNotFoundException, UnsupportedUpdateException, MDSIOException, ConcurrentMOChangeException or ValidationException

Action: Check if the pages.xml is present, you have update permission on the document or if the pages.xml has some invalid content. If all the things listed are fine then try again after sometime.
Level: 1

Type: ERROR

Impact: Other

WCS-18537: Error updating {0} with {1} and {2}.

Cause: The cause of this error could be MetadataNotFoundException, UnsupportedUpdateException, MDSIOException, ConcurrentMOChangeException or ValidationException

Action: Check if the pages.xml is present, you have update permission on the document or if the pages.xml has some invalid content. If all the things listed are fine then try again after sometime.
Level: 1

Type: ERROR

Impact: Other

WCS-18538: An unknown error occurred while trying to determine security attributes of type {0}

Cause: Review the logs for the underlying exception

Action: Take action based on the underlying exception. Rerun the crawl.
Level: 1

Type: WARNING

Impact: Other

WCS-18539: An unknown error occurred while trying to determine security attributes of type {0} for user {1}

Cause: Review the logs for the underlying exception

Action: Take action based on the underlying exception. Rerun the crawl.
Level: 1

Type: WARNING

Impact: Other

WCS-18540: Unknown error accessing assets

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18540: Unknown error accessing assets

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18541: Action {0} cannot be executed on asset type {1}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18541: Action {0} cannot be executed on asset type {1}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18542: You do not have privileges to perform {0} on {1}.

Cause: The user does not have permission to perform the action on the given asset or asset type.

Action: Contact your administrator to give you privileges to perform the required action.
Level: 1

Type: WARNING

Impact: Other

WCS-18542: You do not have privileges to perform {0} on {1}.

Cause: The user does not have permission to perform the action on the given asset or asset type.

Action: Contact your administrator to give you privileges to perform the required action.
Level: 1

Type: WARNING

Impact: Other

WCS-18543: Unknown error while determining if user can access asset manager in scope {0}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-18543: Unknown error while determining if user can access asset manager in scope {0}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-18544: Unknown error while determining if user can access {0} asset type in asset manager in scope {1}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-18544: Unknown error while determining if user can access {0} asset type in asset manager in scope {1}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-18545: Unknown error while deleting assets permission for scope {0}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-18545: Unknown error while deleting assets permission for scope {0}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-18546: Selected operation cannot be performed as the asset is already deleted, refresh the list using the refresh icon.

Cause: The asset on which the action is being performed does not exist.

Action: Refresh the list using the Refresh icon.
Level: 1

Type: ERROR

Impact: Security

WCS-18546: Selected operation cannot be performed as the asset is already deleted, refresh the list using the refresh icon.

Cause: The asset on which the action is being performed does not exist.

Action: Refresh the list using the Refresh icon.
Level: 1

Type: ERROR

Impact: Security

WCS-18701: An unexpected error occurred in the Feedback sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-18720: Failed to query preferences for Feedback object.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18751: Unknown error accessing portal assets

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18751: Unknown error accessing portal assets

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18752: Unknown error in instantiating portal assets factory

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18752: Unknown error in instantiating portal assets factory

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18753: Unexpected error occurred while adding a portal asset.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18753: Unexpected error occurred while adding a portal asset.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18754: Unexpected error occurred while deleting a portal asset

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18754: Unexpected error occurred while deleting a portal asset

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18755: Unexpected error occurred while updating a portal asset

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18755: Unexpected error occurred while updating a portal asset

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18756: Unexpected error occurred while getting the list of portal assets

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18756: Unexpected error occurred while getting the list of portal assets

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18757: Portal asset for update is not valid

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18757: Portal asset for update is not valid

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18758: An attribute in this asset is not valid.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18758: An attribute in this asset is not valid.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18759: An error occurred in setting up the asset

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18759: An error occurred in setting up the asset

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18760: Copy operation resulted in error. If you see the asset in asset manager, delete it.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18760: Copy operation resulted in error. If you see the asset in asset manager, delete it.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18761: Delete operation resulted in error. If you see the asset in asset manager, try deleting it again.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18761: Delete operation resulted in error. If you see the asset in asset manager, try deleting it again.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18762: You do not have the privileges required to perform this operation.

Cause: No privilege to do the current operation

Action: Contact webcenter administrator for change in role.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18762: You do not have the privileges required to perform this operation.

Cause: No privilege to do the current operation

Action: Contact webcenter administrator for change in role.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18763: Asset with the same display name already exists.

Cause: An unexpected error occurred.

Action: Enter a new display name for the asset.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18763: Asset with the same display name already exists.

Cause: An unexpected error occurred.

Action: Enter a new display name for the asset.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18764: An unexpected error occurred while trying to check {0} access for {1}, denying access.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-18764: An unexpected error occurred while trying to check {0} access for {1}, denying access.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-18765: Unable to import, as the asset being imported conflicts with another asset.

Cause: Another asset in the target has the metadata file or jspx with the same path as the asset being imported.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-18765: Unable to import, as the asset being imported conflicts with another asset.

Cause: Another asset in the target has the metadata file or jspx with the same path as the asset being imported.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-18766: Unable to import as the asset being imported conflicts with another asset of a different type in the same portal.

Cause: Either the metadata file or jspx with the same path already exists on the target application in same scope.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-18766: Unable to import as the asset being imported conflicts with another asset of a different type in the same portal.

Cause: Either the metadata file or jspx with the same path already exists on the target application in same scope.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-18767: Unable to validate the content of the archive. Import of asset is aborted.

Cause: Error while trying to check if a document exists in MDS.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-18767: Unable to validate the content of the archive. Import of asset is aborted.

Cause: Error while trying to check if a document exists in MDS.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-18768: Unable to import as {1}, as the asset in the archive is of type {0}

Cause: Select the correct asset type to import.

Action: Select the correct asset type to import.
Level: 1

Type: ERROR

Impact: Other

WCS-18768: Unable to import as {1}, as the asset in the archive is of type {0}

Cause: Select the correct asset type to import.

Action: Select the correct asset type to import.
Level: 1

Type: ERROR

Impact: Other

WCS-18769: Encountered exception while trying to determine if path {0} points to an asset, resorting to default security check.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-18769: Encountered exception while trying to determine if path {0} points to an asset, resorting to default security check.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-18770: Asset with id "{0}" does not exist.

Cause: The asset was possibly deleted by another user.

Action: Refresh the asset manager to see if the asset still exists
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18770: Asset with id "{0}" does not exist.

Cause: The asset was possibly deleted by another user.

Action: Refresh the asset manager to see if the asset still exists
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18771: Unable to export as the asset is type {0} but was invoked as {1}

Cause: Incorrect asset type

Action: Select the correct asset type to import.
Level: 1

Type: ERROR

Impact: Other

WCS-18771: Unable to export as the asset is type {0} but was invoked as {1}

Cause: Incorrect asset type

Action: Select the correct asset type to import.
Level: 1

Type: ERROR

Impact: Other

WCS-18772: Unable to upload as the asset belongs to {0} but is being uploaded into {1}

Cause: The asset you are trying to upload belongs to a different portal.

Action: Verify which portal owns the asset and then upload the asset to that portal.
Level: 1

Type: ERROR

Impact: Other

WCS-18772: Unable to upload as the asset belongs to {0} but is being uploaded into {1}

Cause: The asset you are trying to upload belongs to a different portal.

Action: Verify which portal owns the asset and then upload the asset to that portal.
Level: 1

Type: ERROR

Impact: Other

WCS-18773: Unable to upload the asset. The owner of the asset is not valid.

Cause: Cannot identify the owner of the asset.

Action: The archive is corrupt with invalid documents. Contact Oracle Support Services and provide log information.
Level: 1

Type: ERROR

Impact: Other

WCS-18773: Unable to upload the asset. The owner of the asset is not valid.

Cause: Cannot identify the owner of the asset.

Action: The archive is corrupt with invalid documents. Contact Oracle Support Services and provide log information.
Level: 1

Type: ERROR

Impact: Other

WCS-18774: Global asset of type "{2}", with ID "{0}" does not exist.

Cause: The specified asset was probably deleted by another user.

Action: Refresh the list of assets to see if the asset still exists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18774: Global asset with ID "{0}" does not exist.

Cause: The specified asset was probably deleted by another user.

Action: Refresh the list of assets to see if the asset still exists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18775: Asset of type "{2}", with ID "{0}" does not exist in the portal "{1}".

Cause: The specified asset was probably deleted by another user.

Action: Refresh the list of assets to see if the asset still exists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18775: Asset with ID "{0}" does not exist in the portal "{1}".

Cause: The specified asset was probably deleted by another user.

Action: Refresh the list of assets to see if the asset still exists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18776: You do not have the permissions required to perform the operation. Verify that you have the appropriate Create/Edit/Delete permission for the type of shared asset you are attempting to upload/download.

Cause: Verify that you have the appropriate Create/Edit/Delete permission.

Action: Contact your WebCenter Portal administrator to request the required permissions.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18776: You do not have the permissions required to perform the operation. Verify that you have the appropriate Create/Edit/Delete permission for the type of shared asset you are attempting to upload/download.

Cause: Verify that you have the appropriate Create/Edit/Delete permission.

Action: Contact your WebCenter Portal administrator to request the required permissions.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18777: You do not have the permissions required to perform the operation. Verify that you have the appropriate Create/Edit/Delete permission for all portal assets or for the specific type of portal asset you are attempting to upload/download.

Cause: Verify that you have the appropriate Create/Edit/Delete asset permissions for the portal.

Action: Contact the portal administrator to request the required permissions.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18777: You do not have the permissions required to perform the operation. Verify that you have the appropriate Create/Edit/Delete permission for all portal assets or for the specific type of portal asset you are attempting to upload/download.

Cause: Verify that you have the appropriate Create/Edit/Delete asset permissions for the portal.

Action: Contact the portal administrator to request the required permissions.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18778: Unable to upload as the archive does not contain a shared asset.

Cause: The asset you are trying to upload belongs to a specific portal, it is not a shared asset.

Action: Verify which portal owns the asset and then upload the asset to that portal.
Level: 1

Type: ERROR

Impact: Other

WCS-18778: Unable to upload as the archive does not contain a shared asset.

Cause: The asset you are trying to upload belongs to a specific portal, it is not a shared asset.

Action: Verify which portal owns the asset and then upload the asset to that portal.
Level: 1

Type: ERROR

Impact: Other

WCS-18779: Unable to upload the asset as the archive does not contain an asset that belongs to this portal.

Cause: The asset you are trying to upload belongs to a different portal.

Action: Verify which portal owns the asset and then upload the asset to that portal.
Level: 1

Type: ERROR

Impact: Other

WCS-18779: Unable to upload the asset as the archive does not contain an asset that belongs to this portal.

Cause: The asset you are trying to upload belongs to a different portal.

Action: Verify which portal owns the asset and then upload the asset to that portal.
Level: 1

Type: ERROR

Impact: Other

WCS-18780: Global asset of type "{2}", with name "{0}" does not exist.

Cause: The specified asset was probably deleted by another user.

Action: Refresh the list of assets to see if the asset still exists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18780: Global asset of type "{2}", with name "{0}" does not exist.

Cause: The specified asset was probably deleted by another user.

Action: Refresh the list of assets to see if the asset still exists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18781: Asset of type "{2}", with name "{0}" does not exist in the portal "{1}".

Cause: The specified asset was probably deleted by another user.

Action: Refresh the list of assets to see if the asset still exists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18781: Asset of type "{2}", with name "{0}" does not exist in the portal "{1}".

Cause: The specified asset was probably deleted by another user.

Action: Refresh the list of assets to see if the asset still exists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18782: Name or Resource Id of the resource to be exported is not specified. Specify either the name or the Id of the resource.

Cause: Name or ID of the resource to be exported in not mentioned.

Action: Specify either the name or the ID of the resource.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18782: Name or Resource Id of the resource to be exported is not specified. Specify either the name or the Id of the resource.

Cause: Name or ID of the resource to be exported in not mentioned.

Action: Specify either the name or the ID of the resource.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18783: Name, Resource Id and type of the resource to be exported do not match.

Cause: Name, Resource Id and type of the resource to be exported do not match.

Action: Specify either the name or the ID of the resource.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18783: Name, Resource Id and type of the resource to be exported do not match.

Cause: Name, Resource Id and type of the resource to be exported do not match.

Action: Specify either the name or the ID of the resource.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18784: Asset is a system asset. You cannot export system assets.

Cause: The asset you are trying to export is a system asset.

Action: Refer to export documentation for more information or contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18784: Asset is a system asset. You cannot export system assets.

Cause: The asset you are trying to export is a system asset.

Action: Refer to export documentation for more information or contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18785: Asset is a system asset. You cannot import system assets.

Cause: The asset you are trying to import is a system asset.

Action: Refer to import documentation for more information or contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18785: Asset is a system asset. You cannot import system assets.

Cause: The asset you are trying to import is a system asset.

Action: Refer to import documentation for more information or contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18786: Global asset of type "{3}", with the name "{0}" already exists with a different guid "{2}".

Cause: An unexpected error occurred.

Action: Enter a new display name for the global asset.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18787: Asset of type "{3}", with the name "{0}" already exists in the portal "{1}" with a different guid "{2}".

Cause: An unexpected error occurred.

Action: Enter a new display name for the asset.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18788: Asset of type "{1}", with id "{0}" is a system asset. You cannot export system assets.

Cause: The asset you are trying to export is a system asset.

Action: Refer to export documentation for more information or contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18789: Asset of type "{1}", with name "{0}" is a system asset. You cannot export system assets.

Cause: The asset you are trying to export is a system asset.

Action: Refer to export documentation for more information or contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18790: Portal asset for copy is not valid

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18791: The asset archive specified is not a valid asset archive.

Cause: The asset archive specified is not a valid asset archive.

Action: Verify the asset archive and provide a valid archive.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18792: An exception occurred while exporting the persistence data for the asset named "{0}".

Cause: An exception occurred while exporting the persistence data for the asset.

Action: Verify the asset data in the persistence store and retry the operation.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18793: An exception occurred while importing the persistence data for the asset with id "{0}".

Cause: An exception occurred while importing the persistence data for the asset.

Action: Verify the asset data in the persistence store and retry the operation.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18801: Access Policy for component "{0}" could not be saved.

Cause: There was an error in saving access policy.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18802: Access Policy for component "{0}" defined by {1} could not be read.

Cause: There was an error in reading access policies of the component.

Action: Verify in 'Display Options' tab that the el expression in 'Show Component' property is not malformed
Level: 1

Type: WARNING

Impact: Other

WCS-18803: Attribute "{0}" could not be read for component "{1}"

Cause: There was an error in reading an attribute of the component.

Action: Verify in 'Display Options' tab that the el expression in 'Show Component' property is not malformed
Level: 1

Type: WARNING

Impact: Other

WCS-18804: Attribute "rendered" of component "{0}" having EL expression "{1}" could not be parsed.

Cause: There was an error in parsing EL Expression of attribute "rendered"

Action: Verify in 'Display Options' tab that the el expression in 'Show Component' property is not malformed
Level: 1

Type: WARNING

Impact: Other

WCS-18805: Attributes of component "{0}" has not been modified.

Cause: Attributes of selected component has not been modified.

Action: Message is informational only
Level: 1

Type: WARNING

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-19001: Unexpected error occurred

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19002: Unable to execute operation on {0}

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19002: Unable to execute operation on {0}

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19003: Metadata file {0} not found

Cause: The expected metadata file was not found

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-19004: Unexpected error occurred while creating page table

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19005: Internal error while creating policy store metadata for {0}

Cause: Policy store for WebCenter Portal not found

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19005: Internal error while creating policy store metadata for {0}

Cause: Policy store for WebCenter Portal not found

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19007: Unable to copy application or portal policies for {0}

Cause: Exception occurred while copying policies for WebCenter Portal.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19007: Unable to copy application or portal policies for {0}

Cause: Exception occurred while copying policies for WebCenter Portal.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19008: No matching users were found with search string {0}

Cause: No users matched the search string you entered: {0}

Action: Enter a new search term and try again
Level: 1

Type: ERROR

Impact: Other

WCS-19008: No matching users were found with search string {0}

Cause: No users matched the search string you entered: {0}

Action: Enter a new search term and try again
Level: 1

Type: ERROR

Impact: Other

WCS-19010: Couldn''t retrieve metadata for role {0}

Cause: No roles matched the search string you entered: {0}

Action: Enter a new search term and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19010: Couldn''t retrieve metadata for role {0}

Cause: No roles matched the search string you entered: {0}

Action: Enter a new search term and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19013: User not specified

Cause: A null or empty string was provided for the user name.

Action: Enter a valid user name.
Level: 1

Type: ERROR

Impact: Other

WCS-19013: User not specified

Cause: A null or empty string was provided for the user name.

Action: Enter a valid user name.
Level: 1

Type: ERROR

Impact: Other

WCS-19014: Role not specified

Cause: A null or empty string was provided for the role name.

Action: Enter a valid role name.
Level: 1

Type: ERROR

Impact: Other

WCS-19014: Role not specified

Cause: A null or empty string was provided for the role name.

Action: Enter a valid role name.
Level: 1

Type: ERROR

Impact: Other

WCS-19016: Unable to grant user {2} with role {1} in {0}

Cause: An attempt to grant a user role failed. Either, role {1} does not exist, user {0} does not exist, or the user is already granted the role

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19016: Unable to grant user {2} with role {1} in {0}

Cause: An attempt to grant a user role failed. Either, role {1} does not exist, user {0} does not exist, or the user is already granted the role

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19017: Unable to revoke role {1} from identity {0}

Cause: An attempt to grant a identity role failed. Either, role {1} does not exist,identity {0} does not exist, or the identity does not have the specified role.

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19017: Unable to revoke role {1} from identity {0}

Cause: An attempt to grant a identity role failed. Either, role {1} does not exist,identity {0} does not exist, or the identity does not have the specified role.

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19018: Unable to add role {0} to the policy store

Cause: An attempt to create a new role failed. Either the role already exists, or the policy store is currently unavailable

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-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-19019: An error occurred while trying to remove role {0} from the policy store

Cause: An attempt to delete the specified role failed. Either the role does not exist, or the policy store is currently unavailable.

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19020: Identity {0} has already been granted the role(s).

Cause: User has been already granted the same role.

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19020: Identity {0} has already been granted the role(s).

Cause: User has been already granted the same role.

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19022: Role {0} already exists in the policy store

Cause: An attempt to create a new role failed because the policy store contains a role with the name specified.

Action: Enter a unique name for the role.
Level: 1

Type: ERROR

Impact: Other

WCS-19022: Role {0} already exists in the policy store

Cause: An attempt to create a new role failed because the policy store contains a role with the name specified.

Action: Enter a unique name for the role.
Level: 1

Type: ERROR

Impact: Other

WCS-19025: Only authenticated users can perform the requested operation

Cause: You do not have sufficient privileges to perform the requested operations.

Action: Ask your WebCenter Portal administrator to grant you the appropriate privileges and then try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19025: Only authenticated users can perform the requested operation

Cause: You do not have sufficient privileges to perform the requested operations.

Action: Ask your WebCenter Portal administrator to grant you the appropriate privileges and then try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19026: Unable to revoke permission {0}

Cause: The specified permission was not removed from the policy store. The permission may not exist

Action: Check whether the permission exists in the policy store
Level: 1

Type: ERROR

Impact: Other

WCS-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-19027: Unable to grant permission {0}

Cause: The user was not granted the specified permission. The user may already be assigned that permission.

Action: Check whether the user is assigned this permission.
Level: 1

Type: ERROR

Impact: Other

WCS-19029: Policy for WebCenter Portal could not be found

Cause: Policy for WebCenter Portal was missing from the policy store.

Action: Check the policy store for WebCenter Portal is configured correctly.
Level: 1

Type: ERROR

Impact: Other

WCS-19029: Policy for WebCenter Portal could not be found

Cause: Policy for WebCenter Portal was missing from the policy store.

Action: Check the policy store for WebCenter Portal is configured correctly.
Level: 1

Type: ERROR

Impact: Other

WCS-19030: Page definition for page {0} not found

Cause: Page definition for page {0} does not exist.

Action: Check whether the page definition for page {0} exists
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-19066: Unable to set up the default shell handler factory.

Cause: An internal error occurred while setting up the default shell handler factory.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19067: Unable to navigate to the page. Page creation might have failed or an error occurred while attempting to load the new page. Open your Manage Pages dialog box to see if the page exists. If the problem persists, contact your administrator.

Cause: An error occurred trying to reference the newly created page (the page may not have been created properly).

Action: Try to selecting the new page from the pages dropdown list. If the page is not listed, try creating the page again
Level: 1

Type: ERROR

Impact: Other

WCS-19067: Unable to navigate to the page. Page creation might have failed or an error occurred while attempting to load the new page. Open your Manage Pages dialog box to see if the page exists. If the problem persists, contact your administrator.

Cause: An error occurred trying to reference the newly created page (the page may not have been created properly).

Action: Try to selecting the new page from the pages dropdown list. If the page is not listed, try creating the page again
Level: 1

Type: ERROR

Impact: Other

WCS-19068: Unable to create page in the current scope

Cause: An unexpected error occurred while trying to create a page in a scope.

Action: Ask your WebCenter Portal administrator to resolve the issue.
Level: 1

Type: ERROR

Impact: Other

WCS-19068: Unable to create page in the current scope

Cause: An unexpected error occurred while trying to create a page in a scope.

Action: Ask your WebCenter Portal administrator to resolve the issue.
Level: 1

Type: ERROR

Impact: Other

WCS-19070: Unable to delete page {0} ({1})

Cause: An attempt to delete a page failed. Either the page and/or its associated files (for example, ADFm page definition) have been modified but not saved

Action: Verify that the page is not being modified and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-19073: Unable to register page {0} (of scope {1}) for navigation

Cause: An error occurred while registering the page {0}.

Action: Try to register the page again and if unsuccessful contact Oracle Support.
Level: 1

Type: WARNING

Impact: Other

WCS-19075: No users available

Cause: No users found in the identity store associated with WebCenter Portal.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19075: No users available

Cause: No users found in the identity store associated with WebCenter Portal.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19077: Permission class {0} does not have proper constructor method

Cause: The specified class does not have the required constructor

Action: Provide the required constructor in the specified class
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-19084: Permission class{0} can not be instantiated

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19085: Unable to instantiate the policy store for WebCenter Portal

Cause: An error occurred while trying to access the policy store associated with WebCenter Portal.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19085: Unable to instantiate the policy store for WebCenter Portal

Cause: An error occurred while trying to access the policy store associated with WebCenter Portal.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19088: Failed to register application management beans

Cause: Application management beans(MBean) registration failed.Either there are issues with OC4J or the application was not packaged properly.

Action: Restart OC4J or examine OC4J log files for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-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-19089: Failed to unregister application management beans

Cause: Application management beans(MBean) unregistration failed. Either the Mbeans were not registered or the Mbeans were already unregistered.

Action: Examine the OC4J log files for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-19090: An unexpected error has occurred, unable to complete the export process.

Cause: The export process failed due to an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19090: An unexpected error has occurred, unable to complete the export process.

Cause: The export process failed due to an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19101: Unable to save the export archive on the local file system due to an unexpected error.

Cause: Unexpected error occurred while saving the export archive on the local file system.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-19102: Unexpected error occurred while exporting the security policy. Unable to export the policy store.

Cause: An unexpected error occurred while exporting policy store metadata to the local file system.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19104: Unable to export connection details for external application with ID {0}

Cause: An internal error occurred. Unable to retrieve details for an external application appearing in WebCenter Portal.

Action: Ask your WebCenter Portal administrator to clean up external applications appearing in the Sidebar or reconfigure the external application connection using Enterprise Manager.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19104: Unable to export connection details for external application with ID {0}

Cause: An internal error occurred. Unable to retrieve details for an external application appearing in WebCenter Portal.

Action: Ask your WebCenter Portal administrator to clean up external applications appearing in the Sidebar or reconfigure the external application connection using Enterprise Manager.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19105: Unable to find connection details for external application with ID {0}

Cause: No connection details found for external application with the specified ID.

Action: Remove the external application link associated with the specified ID from the Applications pane in the Sidebar.
Level: 1

Type: WARNING

Impact: Other

WCS-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-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-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-19108: Invalid time format {0} retrieved from the preference store.

Cause: An attempt was made to retrieve time information but the source time format was invalid.

Action: Verify whether the time format source returns the correct time format
Level: 1

Type: WARNING

Impact: Other

WCS-19109: Unable to find service.

Cause: Unable to find the service metadata in WebCenter Portal

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19109: Unable to find service.

Cause: Unable to find the service metadata in WebCenter Portal

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19110: Specify a location on server.

Cause: Unable to locate archive for import.

Action: Specify the archive's name and server location, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19111: Specify an archive that exists on the file system.

Cause: Unable to locate archive for import.

Action: Specify a valid archive that exists on the file system and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19112: Specify a server location.

Cause: Unable to locate the specified directory for the export archive.

Action: Specify a valid directory on the server for the export archive and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19113: Specify an existing directory on the server.

Cause: Unable to locate the specified directory.

Action: Specify a valid directory on the server and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19114: Specify a valid name for the portal archive. Usage of special character / or \ is not allowed.

Cause: Usage of special character / or \ is not allowed.

Action: Specify a valid name for the portal archive.
Level: 1

Type: ERROR

Impact: Other

WCS-19115: Specify a valid name for the portal template archive. Usage of special character / or \ is not allowed.

Cause: Usage of special character / or \ is not allowed.

Action: Specify a valid name for the portal template archive.
Level: 1

Type: ERROR

Impact: Other

WCS-19116: Specify a valid name for the portal archive with the file extension {0}.

Cause: Invalid file extension specified.

Action: Specify a valid name for the portal archive with the file extension '.par'
Level: 1

Type: ERROR

Impact: Other

WCS-19117: Specify a valid name for the portal template archive with the file extension {0}.

Cause: Invalid file extension specified.

Action: Specify a valid name for the portal template archive with the file extension '.par'
Level: 1

Type: ERROR

Impact: Other

WCS-19118: Invalid portal archive extension provided: {0}. Specify a valid name for the portal archive and use the file extension {1}.

Cause: Invalid portal archive extension specified.

Action: Specify a valid name for the portal archive and use the file extension '.par'
Level: 1

Type: 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-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-19120: Unable to add link as no proper handler found for the selected resource type

Cause: An attempt to add a new link but the resource being added is neither a task flow or an external application.

Action: Only task flows or external application link can be included.
Level: 1

Type: ERROR

Impact: Other

WCS-19121: Unable to retrieve the shell configuration metadata

Cause: The metadata file is corrupt or missing.

Action: Ensure that the file exists and complies with the schema.Alternatively, contact your WebCenter Portal administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-19121: Unable to retrieve the shell configuration metadata

Cause: The metadata file is corrupt or missing.

Action: Ensure that the file exists and complies with the schema.Alternatively, contact your WebCenter Portal administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-19122: Invalid shell panel name

Cause: The shell panel name was probably NULL.

Action: Provide a valid shell panel name.
Level: 1

Type: ERROR

Impact: Other

WCS-19122: Invalid shell panel name

Cause: The shell panel name was probably NULL.

Action: Provide a valid shell panel name.
Level: 1

Type: ERROR

Impact: Other

WCS-19123: Unable to retrieve the shell handler for the current request {1}

Cause: The shell handler was not set for the current request

Action: Verify the URL and that the WebCenter Portal shell filter is configured to handle requests of this kind
Level: 1

Type: WARNING

Impact: Other

WCS-19123: Unable to retrieve the shell handler for the current request {1}

Cause: The shell handler was not set for the current request

Action: Verify the URL and that the WebCenter Portal shell filter is configured to handle requests of this kind
Level: 1

Type: WARNING

Impact: Other

WCS-19124: Unable to save changes to shell metadata

Cause: An error occurred while saving the shell metadata document.

Action: Ensure that the shell metadata document is not corrupt and is writable and personalizable.
Level: 1

Type: ERROR

Impact: Other

WCS-19124: Unable to save changes to shell metadata

Cause: An error occurred while saving the shell metadata document.

Action: Ensure that the shell metadata document is not corrupt and is writeable and personalizable.
Level: 1

Type: ERROR

Impact: Other

WCS-19125: Account for user {0} is disabled

Cause: The account for user {0} account is disabled.

Action: Ask the WebCenter Portal administrator to activate the account.
Level: 1

Type: ERROR

Impact: Other

WCS-19125: Account for user {0} is disabled

Cause: The account for user {0} account is disabled.

Action: Ask the WebCenter Portal administrator to activate the account.
Level: 1

Type: ERROR

Impact: Other

WCS-19126: Account for user {0} is inactive

Cause: The account for user {0} is disabled.

Action: Ask the WebCenter Portal administrator to activate the account.
Level: 1

Type: ERROR

Impact: Other

WCS-19126: Account for user {0} is inactive

Cause: The account for user {0} is disabled.

Action: Ask the WebCenter Portal administrator to activate the account.
Level: 1

Type: ERROR

Impact: Other

WCS-19127: The account for user {0} is locked

Cause: The account is locked for user {0}

Action: Ask the WebCenter Portal administrator to unlock the account.
Level: 1

Type: ERROR

Impact: Other

WCS-19127: The account for user {0} is locked

Cause: The account is locked for user {0}

Action: Ask the WebCenter Portal administrator to unlock the account.
Level: 1

Type: ERROR

Impact: Other

WCS-19128: Password has expired for user account {0}

Cause: Password for this user has expired

Action: Contact the WebCenter Portal administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-19128: Password has expired for user account {0}

Cause: Password for this user has expired

Action: Contact the WebCenter Portal administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-19129: Incorrect Old Password for user account {0}

Cause: The old password specified for this user is not correct.

Action: Enter the correct password
Level: 1

Type: ERROR

Impact: Other

WCS-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-19130: Password for user account {0} is null

Cause: No password was specified.

Action: Enter a valid password.
Level: 1

Type: ERROR

Impact: Other

WCS-19131: Error occurred granting permissions to user {0} for the newly created page {1}

Cause: An unexpected error occurred while granting the user permission

Action: Contact the WebCenter Portal administrator
Level: 1

Type: WARNING

Impact: Other

WCS-19131: Error occurred granting permissions to user {0} for the newly created page {1}

Cause: An unexpected error occurred while granting the user permission

Action: Contact the WebCenter Portal administrator
Level: 1

Type: WARNING

Impact: Other

WCS-19132: Unable to retrieve the permission target for page {0}

Cause: An unexpected error occurred. The ADFm page definition of the page may be missing

Action: Ensure that the page definition exists and is valid.
Level: 1

Type: WARNING

Impact: Other

WCS-19132: Unable to retrieve the permission target for page {0}

Cause: An unexpected error occurred. The ADFm page definition of the page may be missing

Action: Ensure that the page definition exists and is valid.
Level: 1

Type: WARNING

Impact: Other

WCS-19133: Unable to determine the page in focus

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-19133: Unable to determine the page in focus

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-19134: Unable to hide a page, locked by another user

Cause: An attempt was made to hide a page that is currently locked by another user.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19134: Unable to hide a page, locked by another user

Cause: An attempt was made to hide a page that is currently locked by another user.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19135: No page selected for hiding

Cause: Unable to determine which page has focus.

Action: Select the page you want to hide and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19135: No page selected for hiding

Cause: Unable to determine which page has focus.

Action: Select the page you want to hide and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19136: Unable to hide the page.

Cause: An attempt was made to hide the last open page.

Action: Open some other page and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19136: Unable to hide the page.

Cause: An attempt was made to hide the last open page.

Action: Open some other page and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19137: Unable to determine the page focus for hiding

Cause: Unable to determine which page has focus.

Action: Select the page you want to hide and try again. Alternatively, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19137: Unable to determine the page focus for hiding

Cause: Unable to determine which page has focus.

Action: Select the page you want to hide and try again. Alternatively, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19138: Unable to encode the value {1} of parameter {0} using encoding format {2}

Cause: The encoding format was unexpectedly invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-19156: You cannot send an invite to this user as an invite has already been sent.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19157: Portal {0} may have been deleted or renamed

Cause: An attempt was made to access a portal that has been deleted or renamed.

Action: Contact the portal moderator or try searching for the portals.
Level: 1

Type: ERROR

Impact: Other

WCS-19157: Portal {0} may have been deleted or renamed

Cause: An attempt was made to access a portal that has been deleted or renamed.

Action: Contact the portal moderator or try searching for the portals.
Level: 1

Type: ERROR

Impact: Other

WCS-19158: Cannot personalize visibility of page {0} in portal {1}

Cause: A personalization attempt failed. Either the backing store could not be accessed or some other personalization operation was performed simultaneously.

Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19158: Cannot personalize visibility of page {0} in portal {1}

Cause: A personalization attempt failed. Either the backing store could not be accessed or some other personalization operation was performed simultaneously.

Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19159: Unable to save page creation

Cause: An attempt to save the new page failed. Either the back-end store could not be accessed or another page was created simultaneously.

Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19159: Unable to save page creation

Cause: An attempt to save the new page failed. Either the back-end store could not be accessed or another page was created simultaneously.

Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19160: Unable to save the personal sequence of pages in scope {0}

Cause: An attempt to personalize the page sequence failed. Either the back-end store could not be accessed or some other personalization operation was performed simultaneously

Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19160: Unable to save the personal sequence of pages in scope {0}

Cause: An attempt to personalize the page sequence failed. Either the back-end store could not be accessed or some other personalization operation was performed simultaneously

Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19161: Unable to save the change in sequence of pages in scope {0}

Cause: An attempt to change page sequence failed. Either the back-end store could not be accessed or a similar operation was performed simultaneously.

Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19161: Unable to save the change in sequence of pages in scope {0}

Cause: An attempt to change page sequence failed. Either the back-end store could not be accessed or a similar operation was performed simultaneously.

Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19162: Revoke role completed with errors The mapping of roles failed

Cause: Changes in services failed due to the following errors

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-19171: Application role {0} to be granted is not found

Cause: Specified role was not found.

Action: Check the role name {0} and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19172: Internal error while creating security manager for portal {0}

Cause: Unable to resolve the Scope GUID for Scope {0}

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19172: Internal error while creating security manager for portal {0}

Cause: Unable to resolve the Scope GUID for Scope {0}

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19173: New passwords for user account {0} do not match

Cause: Passwords were entered incorrectly.

Action: Enter the correct passwords.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-19178: User Not Found

Cause: User Not Found

Action: Enter a username
Level: 1

Type: WARNING

Impact: Other

WCS-19179: Group not found or multiple groups with the same name exist.

Cause: Group not found or multiple groups with the same name exist

Action: Enter a Group
Level: 1

Type: WARNING

Impact: Other

WCS-19179: Group not found or multiple groups with the same name exist.

Cause: Group not found or multiple groups with the same name exist

Action: Enter a Group
Level: 1

Type: WARNING

Impact: Other

WCS-19180: User with this name doesn't exist

Cause: User with this name doesn't exist

Action: Enter a role which has users
Level: 1

Type: WARNING

Impact: Other

WCS-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-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-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-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-19184: Unable to delete link/folder {0}

Cause: The metadata file could have got corrupt or removed

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-19185: Role cannot be created because it contains special characters

Cause: Creation of Role {0} failed because it contains special characters

Action: Remove special characters used in your role and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19185: Role cannot be created because it contains special characters

Cause: Creation of Role {0} failed because it contains special characters

Action: Remove special characters used in your role and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19186: Role {0} cannot be created, as the role of same name exists in the policy store

Cause: Creation of Role {0} failed because policy store already contains a role of same name

Action: Try changing role name
Level: 1

Type: ERROR

Impact: Other

WCS-19186: Role {0} cannot be created, as the role of same name exists in the policy store

Cause: Creation of Role {0} failed because policy store already contains a role of same name

Action: Try changing role name
Level: 1

Type: ERROR

Impact: Other

WCS-19187: Granting of Role {0} partially succeeded for identity {1}. Granting permissions for {2} failed. You can take actions regarding these warnings in portal settings.

Cause: Granting of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19187: Granting of Role {0} partially succeeded for identity {1}. Granting permissions for {2} failed. You can take actions regarding these warnings in portal settings.

Cause: Granting of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19188: Revoking of Role {0} partially succeeded for identity {1}. Revoking permissions for {2} failed. You can take actions regarding these warnings in portal settings.

Cause: revoking of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19188: Revoking of Role {0} partially succeeded for identity {1}. Revoking permissions for {2} failed. You can take actions regarding these warnings in portal settings.

Cause: revoking of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19189: Mapping the permissions {0} failed. You may want to try the operation again after some time or can contact Administrator.

Cause: Granting of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-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-19190: Fatal Error while granting role for certain services.

Cause: Granting of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19191: User(s) {0} has already been granted the role {1}.

Cause: Current User / Role {0} has been already granted the application role.

Action: Don't Provision this user since it is already provisioned.
Level: 1

Type: ERROR

Impact: Other

WCS-19191: User(s) {0} has already been granted the role {1}.

Cause: Current User / Role {0} has been already granted the application role.

Action: Don't Provision this user since it is already provisioned.
Level: 1

Type: ERROR

Impact: Other

WCS-19192: Role has been granted with errors. You might want to contact Administrator or Remove/Grant Role again.

Cause: Role was granted with errors.

Action: Contact the Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-19203: Fatal error while creating the role. Please contact Administrator with error reference.

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19204: Unable to save Invite message for portal {0} due to unknown errors. Please try later or contact administrator

Cause: Error occurred while obtaining the invite message

Action: Try later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19204: Unable to save Invite message for portal {0} due to unknown errors. Please try later or contact administrator

Cause: Error occurred while obtaining the invite message

Action: Try later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19205: Unable to save member changes for a portal{0} due to unknown errors. Please try later or contact administrator

Cause: Error occurred while saving the member changes

Action: Try later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19205: Unable to save member changes for a portal{0} due to unknown errors. Please try later or contact administrator

Cause: Error occurred while saving the member changes

Action: Try later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19206: Could not find security policy in the archive file being imported.

Cause: The security policy file was not found in import archive.

Action: Export the data again and try the import operation again.
Level: 1

Type: ERROR

Impact: Other

WCS-19206: Could not find security policy in the archive file being imported.

Cause: The security policy file was not found in import archive.

Action: Export the data again and try the import operation again.
Level: 1

Type: ERROR

Impact: Other

WCS-19207: One or more mandatory roles are not found in the copied instance for scope {0}. Role Name: {1}

Cause: One or more mandatory roles are not found in the copied instance.

Action: Add the mandatory role {1} in the security metadata to get WebCenter Portal functionality or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19207: One or more mandatory roles are not found in the copied instance for scope {0}. Role Name: {1}

Cause: One or more mandatory roles are not found in the copied instance.

Action: Add the mandatory role {1} in the security metadata to get WebCenter Portal functionality or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19208: Deletion of security metadata failed for scope {0}

Cause: Deletion of roles for the current scope {0} has failed.

Action: Try later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19208: Deletion of security metadata failed for scope {0}

Cause: Deletion of roles for the current scope {0} has failed.

Action: Try later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19209: An unexpected error occurred while trying to upload WebCenter Portal logo to path {0}

Cause: MDS StreamedObject creation failed for WebCenter Portal logo

Action: Contact administrator for further assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-19209: An unexpected error occurred while trying to upload WebCenter Portal logo to path {0}

Cause: MDS StreamedObject creation failed for WebCenter Portal logo

Action: Contact administrator for further assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-19210: The image upload failed as the image file you tried to upload was invalid. Provide a valid image file.

Cause: Unable to upload the WebCenter Portal logo as the file is null or not available.

Action: Upload a valid image file
Level: 1

Type: ERROR

Impact: Other

WCS-19210: The image upload failed as the image file you tried to upload was invalid. Provide a valid image file.

Cause: Unable to upload the WebCenter Portal logo as the file is null or not available.

Action: Upload a valid image file
Level: 1

Type: ERROR

Impact: Other

WCS-19211: An error occurred while trying to retrieve the templates to be used for page creation. Please contact Administrator with error reference.

Cause: An unexpected error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-19219: Unexpected error occurred while deleting the page

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19220: Search for role {0} resulted in more than one result. Please contact Administrator to get it rectified

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19220: Search for role {0} resulted in more than one result. Please contact Administrator to get it rectified

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19221: While provisioning the services, errors were encountered for following services - {0}. Check if these services have been configured correctly.

Cause: While copying the services, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-19227: Unexpected error occurred while restoring the page

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19228: Unexpected error occurred while creating list of pages

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19228: Unexpected error occurred while creating list of pages

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19229: Error occurred in getting the complete list of pages you can access. Please contact the administrator.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-19232: While provisioning the services, errors were encountered for following services - {0}. Check if these services have been configured correctly.

Cause: While provisioning the services, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19233: While renaming all the provisioned services, errors were encountered for following services - {0}.

Cause: While renaming the portal, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19233: While renaming all the provisioned services, errors were encountered for following services - {0}.

Cause: While renaming the portal, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19234: While unprovisioning the services, errors were encountered for following services - {0}.

Cause: While unprovisioning the services, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-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-19235: Unknown error occurred. Please contact Administrator.

Cause: Unknown error occurred.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19236: The following service(s) are currently unavailable: {0}. If the problem persists contact your administrator.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19236: The following service(s) are currently unavailable: {0}. If the problem persists contact your administrator.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19237: Unable to export the portal {0}. Either the portal does not exist or the portal is being exported/imported by another user. Refresh the portal list and try again.

Cause: Unable to acquire a lock on the scope of portal.

Action: Refresh the portal list and try again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19237: Unable to export the portal {0}. Either the portal does not exist or the portal is being exported/imported by another user. Refresh the portal list and try again.

Cause: Unable to acquire a lock on the scope of portal.

Action: Refresh the portal list and try again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19238: Unable to export the portal template {0}. Either the portal template does not exist or the portal template is being exported/imported by another user. Refresh the portal template list and try again.

Cause: Unable to acquire a lock on the scope of portal template.

Action: Refresh the portal template list and try again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19238: Unable to export the portal template {0}. Either the portal template does not exist or the portal template is being exported/imported by another user. Refresh the portal template list and try again.

Cause: Unable to acquire a lock on the scope of portal template.

Action: Refresh the portal template list and try again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19239: Unable to import portals as required resources are not available. Portals being replaced on the target either do not exist or are being exported/imported by another user. Refresh the portal list and try again.

Cause: Unable to acquire a global lock to prevent create, delete, rename or import operations on portals.

Action: Wait for some time and try the import operation again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19239: Unable to import portals as required resources are not available. Portals being replaced on the target either do not exist or are being exported/imported by another user. Refresh the portal list and try again.

Cause: Unable to acquire a global lock to prevent create, delete, rename or import operations on portals.

Action: Wait for some time and try the import operation again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19240: Unable to import portal templates as required resources are not available. Portal templates being replaced on the target either do not exist or are being exported/imported by another user. Refresh the portal template list and try again.

Cause: Unable to acquire a global lock to prevent create, delete, rename or import operations on portal templates.

Action: Wait for some time and try the import operation again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19240: Unable to import portal templates as required resources are not available. Portal templates being replaced on the target either do not exist or are being exported/imported by another user. Refresh the portal template list and try again.

Cause: Unable to acquire a global lock to prevent create, delete, rename or import operations on portal templates.

Action: Wait for some time and try the import operation again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19241: Errors occurred in the page.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-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-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-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-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-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-19247: Modification of role operation not supported for scope {0}

Cause: Currently the modification of role not supported.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19248: Portal {0} being exported is either online or being exported/imported by another user. Wait for some time and try the export operation again.

Cause: Portal is either online or blocked by another user/process.

Action: Refresh the portal list and try to export the portal again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19248: Portal {0} being exported is either online or being exported/imported by another user. Wait for some time and try the export operation again.

Cause: Portal is either online or blocked by another user/process.

Action: Refresh the portal list and try to export the portal again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19249: Portal template {0} you are trying to export is being exported/imported by another user. Wait for some time and try the export operation again.

Cause: Portal template is blocked by another user/process.

Action: Refresh the portal template list and try to export the portal template again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19249: Portal template {0} you are trying to export is being exported/imported by another user. Wait for some time and try the export operation again.

Cause: Portal template is blocked by another user/process.

Action: Refresh the portal template list and try to export the portal template again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19250: Portal template {0} you are trying to import is being exported/imported by another user on the target. Wait for some time and try the import operation again.

Cause: Portal template is blocked by another user/process.

Action: Wait for some time and try to import the portal template again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19250: Portal template {0} you are trying to import is being exported/imported by another user on the target. Wait for some time and try the import operation again.

Cause: Portal template is blocked by another user/process.

Action: Wait for some time and try to import the portal template again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19251: You are trying to import portals but the archive specified contains portal templates. Check the archive file and try again.

Cause: You are trying to import portals but the archive specified contains portal templates.

Action: Use an export archive that contains portals.
Level: 1

Type: ERROR

Impact: Other

WCS-19251: You are trying to import portals but the archive specified contains portal templates. Check the archive file and try again.

Cause: You are trying to import portals but the archive specified contains portal templates.

Action: Use an export archive that contains portals.
Level: 1

Type: ERROR

Impact: Other

WCS-19252: You are trying to import portal templates but the archive specified contains portals. Check the archive file and try again.

Cause: You are trying to import portal templates but the archive specified contains portals.

Action: Use an export archive that contains portal templates.
Level: 1

Type: ERROR

Impact: Other

WCS-19252: You are trying to import portal templates but the archive specified contains portals. Check the archive file and try again.

Cause: You are trying to import portal templates but the archive specified contains portals.

Action: Use an export archive that contains portal templates.
Level: 1

Type: ERROR

Impact: Other

WCS-19253: Cannot locate the document ''{0}''.

Cause: The path is incorrect or it is not available in the system.

Action: Verify whether the path is correct and is available in the system.
Level: 1

Type: ERROR

Impact: Other

WCS-19253: Cannot locate the document ''{0}''.

Cause: The path is incorrect or it is not available in the system.

Action: Verify whether the path is correct and is available in the system.
Level: 1

Type: ERROR

Impact: Other

WCS-19254: Error occurred while reading the WebCenter Portal environment configuration file {0}.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19254: Error occurred while reading the WebCenter Portal environment configuration file {0}.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19255: Unexpected error occurred while navigating to portal administration pages.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19255: Unexpected error occurred while navigating to portal administration pages.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19256: Error occurred while saving the folder.

Cause: An unexpected error occurred while saving the folder.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-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-19257: Unexpected error occurred while acquiring the write lock on the document {0}.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19258: Error occurred while clearing the deleted/renamed portal page.

Cause: Error occurred while clearing the deleted/renamed portal page.

Action: Error occurred while clearing the deleted/renamed portal page.
Level: 1

Type: ERROR

Impact: Other

WCS-19258: Error occurred while clearing the deleted/renamed portal page.

Cause: Error occurred while clearing the deleted/renamed portal page.

Action: Error occurred while clearing the deleted/renamed portal page.
Level: 1

Type: ERROR

Impact: Other

WCS-19259: Portal "{0}" on the target application is either online or being exported/imported by another user. Wait for some time and try the import operation again.

Cause: Portal either online or blocked by another user/process.

Action: Wait for some time and try the import operation again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19259: Portal "{0}" on the target application is either online or being exported/imported by another user. Wait for some time and try the import operation again.

Cause: Portal either online or blocked by another user/process.

Action: Wait for some time and try the import operation again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19260: The current process could not be executed. Wait for some time and try again.

Cause: An unexpected error occurred while saving administration changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19260: The current process could not be executed. Wait for some time and try again.

Cause: An unexpected error occurred while saving administration changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19261: Error occurred while saving administration changes.

Cause: An unexpected error occurred while saving administration changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19261: Error occurred while saving administration changes.

Cause: An unexpected error occurred while saving administration changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19262: Another administrator is modifying the setting. Try again later.

Cause: An unexpected error occurred while saving administration changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19262: Another administrator is modifying the setting. Try again later.

Cause: An unexpected error occurred while saving administration changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19263: Fatal error occurred while getting the roles for current scope.

Cause: An unexpected error occurred while getting the roles.

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-19267: Error occurred while reading the list of tabs from persistence store.

Cause: An unexpected error occurred while reading the list of tabs.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19268: Following error occurred while storing the list of tabs to persistence store - {0}

Cause: An unexpected error occurred while storing the list of tabs.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19268: Following error occurred while storing the list of tabs to persistence store - {0}

Cause: An unexpected error occurred while storing the list of tabs.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19269: Error in processing the pages.

Cause: Unexpected error occurred while adding the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19269: Error in processing the pages.

Cause: Unexpected error occurred while adding the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19270: Error in processing the pages.

Cause: Unexpected error occurred while removing the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19270: Error in processing the pages.

Cause: Unexpected error occurred while removing the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19271: Error in processing the pages.

Cause: Unexpected error occurred while finding the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19271: Error in processing the pages.

Cause: Unexpected error occurred while finding the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19272: Error in processing the pages.

Cause: Unexpected error occurred while creating the menu model.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19272: Error in processing the pages.

Cause: Unexpected error occurred while creating the menu model.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19273: Error in navigation.

Cause: Unexpected error occurred while navigating to secondary page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19273: Error in navigation.

Cause: Unexpected error occurred while navigating to secondary page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19274: Error in processing the pages.

Cause: Unexpected error occurred while preparing the children.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19274: Error in processing the pages.

Cause: Unexpected error occurred while preparing the children.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19275: Error in processing the pages.

Cause: Unexpected error occurred while preparing the page for current request.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19275: Error in processing the pages.

Cause: Unexpected error occurred while preparing the page for current request.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19276: Error in navigation.

Cause: Unexpected error occurred while getting the navigable path to the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19276: Error in navigation.

Cause: Unexpected error occurred while getting the navigable path to the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19277: An error occurred while changing the page visibility. Refresh the page list and retry.

Cause: Unexpected error occurred while changing the page's visibility.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19277: An error occurred while changing the page visibility. Refresh the page list and retry.

Cause: Unexpected error occurred while changing the page's visibility.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19278: Error in renaming the page.

Cause: Unexpected error occurred while changing the page name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19278: Error in renaming the page.

Cause: Unexpected error occurred while changing the page name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19279: Error in creating a copy of the page.

Cause: Unexpected error occurred while copying the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19279: Error in creating a copy of the page.

Cause: Unexpected error occurred while copying the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19280: The role name {0} is reserved, please use some other name.

Cause: Unexpected error occurred while creating the role name.

Action: Try creating a role with some other name.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-19281: Unexpected error occurred while refreshing list of pages.

Cause: Unexpected error occurred while refresh.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19282: Unable to save the BusinessRole sequence of pages.

Cause: An attempt to customize the BR page sequence failed. Either the back-end store could not be accessed or some other customization operation was performed simultaneously

Action: Try the operation again. If the problem persists, contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19282: Unable to save the BusinessRole sequence of pages.

Cause: An attempt to customize the BR page sequence failed. Either the back-end store could not be accessed or some other customization operation was performed simultaneously

Action: Try the operation again. If the problem persists, contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19283: Error in reordering the pages.

Cause: Unexpected error occurred while reordering the pages.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-19284: Error in reordering the business role pages.

Cause: Unexpected error occurred while reordering the business role pages.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19285: Error in reordering the pages.

Cause: Unexpected error occurred while reordering the pages.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19285: Error in reordering the pages.

Cause: Unexpected error occurred while reordering the pages.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19286: Error in moving the page up.

Cause: Unexpected error occurred while moving the page up.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-19287: Error in moving the page down.

Cause: Unexpected error occurred while moving the page down.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19288: Error in processing the pages.

Cause: Unexpected error occurred while closing the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19288: Error in processing the pages.

Cause: Unexpected error occurred while closing the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19289: Unexpected error in closing page(s).

Cause: Unexpected error occurred while closing the pages.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19289: Unexpected error in closing page(s).

Cause: Unexpected error occurred while closing the pages.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19290: Unexpected error in getting list of moderators.

Cause: Unexpected error occurred while getting the list of moderators.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-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-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-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-19294: Unexpected error occurred while trying to navigate to bookmark.

Cause: Unexpected error occurred while trying to navigate to bookmark.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19295: Error occurred while reverting administration changes.

Cause: An unexpected error occurred while reverting administration changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19295: Error occurred while reverting administration changes.

Cause: An unexpected error occurred while reverting administration changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19296: The application failed to access backend data store and cannot process requests

Cause: Access to backend data store failed

Action: Ensure the back-end data store that contains the WebCenter Portal schema and MDS schema is accessible.
Level: 1

Type: ERROR

Impact: Other

WCS-19296: The application failed to access backend data store and cannot process requests

Cause: Access to backend data store failed

Action: Ensure the back-end data store that contains the WebCenter Portal schema and MDS schema is accessible.
Level: 1

Type: ERROR

Impact: Other

WCS-19297: The URL typed by current user is not accessible, so redirecting to the unAuthorized page

Cause: The current user does not have privileges to see the current URL

Action: Please contact system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-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-19298: Unexpected error occurred, please retry the operation

Cause: An internal error occurred

Action: Retry the operation. Contact Oracle Support Services if the issue persists.
Level: 1

Type: ERROR

Impact: Other

WCS-19299: Unexpected error occurred while preparing the administration pages

Cause: An internal error occurred

Action: Retry the operation. Contact Oracle Support Services if the issue persists.
Level: 1

Type: ERROR

Impact: Other

WCS-19299: Unexpected error occurred while preparing the administration pages

Cause: An internal error occurred

Action: Retry the operation. Contact Oracle Support Services if the issue persists.
Level: 1

Type: ERROR

Impact: Other

WCS-19300: Unexpected error trying to restore the Login page

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-19302: Unexpected error trying to open the Login page for edit

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19303: Unexpected error occurred while moving a page to top of the pages list

Cause: Unexpected error occurred while moving a page to top of the pages list

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19303: Unexpected error occurred while moving a page to top of the pages list

Cause: Unexpected error occurred while moving a page to top of the pages list

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19304: Unexpected error occurred while moving a page to bottom of the pages list

Cause: Unexpected error occurred while moving a page to bottom of the pages list

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19304: Unexpected error occurred while moving a page to bottom of the pages list

Cause: Unexpected error occurred while moving a page to bottom of the pages list

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19305: Drag and drop is not allowed for ungrouped view

Cause: Drag and drop was attempted in ungrouped view

Action: Drag and drop operation is not allowed for ungrouped view
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-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-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-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-19309: Unexpected error retrieving services for configuration

Cause: An unexpected error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19310: Unexpected error occurred while trying to retrieve list of languages

Cause: Unexpected error occurred while trying to retrieve list of languages

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19310: Unexpected error occurred while trying to retrieve list of languages

Cause: Unexpected error occurred while trying to retrieve list of languages

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19311: Error occurred granting role {0} in {1}. Refresh the members list to see which users were added successfully. Some errors are displayed below. Contact your administrator for a complete list of errors.

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19311: Error occurred granting role {0} in {1}. Refresh the members list to see which users were added successfully. Some errors are displayed below. Contact your administrator for a complete list of errors.

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19312: Identities : {0}, failed with the errors {1}

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19312: Identities : {0}, failed with the errors {1}

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19313: Setting {0} role for {1} failed. Please contact Administrator

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19313: Setting {0} role for {1} failed. Please contact Administrator

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19314: Portal template {0} is an out-of-the-box template. You cannot export out-of-the-box portal templates.

Cause: Portal template is an out-of-the-box template.

Action: Refer to export documentation for more information or contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19314: Portal template {0} is an out-of-the-box template. You cannot export out-of-the-box portal templates.

Cause: Portal template is an out-of-the-box template.

Action: Refer to export documentation for more information or contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19315: One or more pages of portal {0} are being edited by other users. Wait for some time and try again.

Cause: One or more portal pages are being edited by other users. You cannot export when pages are in edit mode.

Action: Close all the pages from edit mode or contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19315: One or more pages of portal {0} are being edited by other users. Wait for some time and try again.

Cause: One or more portal pages are being edited by other users. You cannot export when pages are in edit mode.

Action: Close all the pages from edit mode or contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19316: One or more pages of portal {0} are being edited by other users. Wait for some time and try again.

Cause: One or more portal pages are being edited by other users. You cannot import when pages are in edit mode..

Action: Close all the pages from edit mode or contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19316: One or more pages of portal {0} are being edited by other users. Wait for some time and try again.

Cause: One or more portal pages are being edited by other users. You cannot import when pages are in edit mode..

Action: Close all the pages from edit mode or contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19317: An unexpected error has occurred while sending notification to the administrator.

Cause: An unexpected error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19317: An unexpected error has occurred while sending notification to the administrator.

Cause: An unexpected error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19318: Granting of Role {0} partially succeeded for identity {1}. Granting permissions for {2} failed.

Cause: Granting of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-19320: File {0} in location {1} already exists. Do you want to overwrite it?

Cause: File already exists in the location where the export archive is being saved.

Action: Enter a new location or overwrite the file.
Level: 1

Type: ERROR

Impact: Other

WCS-19321: Issues were faced while provisioning the service(s) - {0}. Check the portal services settings page if these services have been provisioned.

Cause: While provisioning the services, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19321: Issues were faced while provisioning the service(s) - {0}. Check the portal services settings page if these services have been provisioned.

Cause: While provisioning the services, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19322: You do not have sufficient permission to edit the page.

Cause: Your permission to edit the page might have been revoked.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19322: You do not have sufficient permission to edit the page.

Cause: Your permission to edit the page might have been revoked.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19323: The image file {0} you tried to upload was invalid. Provide a valid image file.

Cause: Unable to upload the image as the file is null or invalid.

Action: Upload a valid image file
Level: 1

Type: ERROR

Impact: Other

WCS-19323: The image file {0} you tried to upload was invalid. Provide a valid image file.

Cause: Unable to upload the image as the file is null or invalid.

Action: Upload a valid image file
Level: 1

Type: ERROR

Impact: Other

WCS-19324: An error occurred while cleaning the pages from persistence store for current user.

Cause: An unexpected error occurred while cleaning the list of pages.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19324: An error occurred while cleaning the pages from persistence store for current user.

Cause: An unexpected error occurred while cleaning the list of pages.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19325: One needs to login to access this url {0}

Cause: Public Users don't have access to this url

Action: Please login first.
Level: 1

Type: ERROR

Impact: Other

WCS-19325: One needs to login to access this url {0}

Cause: Public Users don't have access to this url

Action: Please login first.
Level: 1

Type: ERROR

Impact: Other

WCS-19326: Couldn''t invalidate joc region {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19326: Couldn''t invalidate joc region {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19327: Could not delete joc region {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19327: Could not delete joc region {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19328: Could not add object {1} to joc region {0} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19328: Could not add object {1} to joc region {0} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19329: Could not replace object {1} in joc region {0} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19329: Could not replace object {1} in joc region {0} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19330: Could not retrieve object {1} from joc region {0} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19330: Could not retrieve object {1} from joc region {0} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19331: Could not invalidate object {1} in joc region {0} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19331: Could not invalidate object {1} in joc region {0} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19332: Unexpected error occurred while processing roles in {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19332: Unexpected error occurred while processing roles in {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19333: Unexpected error occurred while processing users in {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19333: Unexpected error occurred while processing users in {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19334: Unexpected error occurred while retrieving all users who have been assigned {0} in {1}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19334: Unexpected error occurred while retrieving all users who have been assigned {0} in {1}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19335: Could not validate user due to {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19335: Could not validate user due to {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19336: Unexpected error occurred while retrieving enterprise roles for user {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19336: Unexpected error occurred while retrieving enterprise roles for user {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19337: Unexpected error occurred while retrieving application role {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19337: Unexpected error occurred while retrieving application role {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19338: Could not retrieve display name for user {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19338: Could not retrieve display name for user {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19339: Unable to retrieve user mail ID for {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19339: Unable to retrieve user mail ID for {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19340: Unable to retrieve members mailing list for {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19340: Unable to retrieve members mailing list for {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19341: Could not verify lifecycle block status due to {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19341: Could not verify lifecycle block status due to {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19342: Unexpected error occurred while retrieving users / groups who have been granted application role {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19342: Unexpected error occurred while retrieving users / groups who have been granted application role {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19343: Unable to send notification to administrator(s). The reason is : {0}.

Cause: The BPEL server is not configured

Action: Configure workflows.
Level: 1

Type: ERROR

Impact: Other

WCS-19343: Unable to send notification to administrator(s). The reason is : {0}.

Cause: The BPEL server is not configured

Action: Configure workflows.
Level: 1

Type: ERROR

Impact: Other

WCS-19344: User(s) {0} has already been invited to portal.

Cause: An unexpected error occurred while inviting users.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19344: User(s) {0} has already been invited to portal.

Cause: An unexpected error occurred while inviting users.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19345: Errors occurred in inviting user(s) to join the portal {1} as role {0}. Please refresh the members list below to see the latest status about the invited users. Some of the errors are displayed below( Please note that following list may not be listing all the errors. For the complete list of errors, please contact the administrator).

Cause: An unexpected error occurred while inviting users.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19345: Errors occurred in inviting user(s) to join the portal {1} as role {0}. Please refresh the members list below to see the latest status about the invited users. Some of the errors are displayed below( Please note that following list may not be listing all the errors. For the complete list of errors, please contact the administrator).

Cause: An unexpected error occurred while inviting users.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19346: User {0} not invited to portal {1}.

Cause: User {0} not invited to portal {1}.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19346: User {0} not invited to portal {1}.

Cause: User {0} not invited to portal {1}.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19347: The default shell-config document cannot be read for looking up application-specific URL parameters, due to {0}.

Cause: The metadata repository might be down or the document may have got corrupted.

Action: Verify that the metadata repository is up and the document contents are valid.
Level: 1

Type: WARNING

Impact: Other

WCS-19347: The default shell-config document cannot be read for looking up application-specific URL parameters, due to {0}.

Cause: The metadata repository might be down or the document may have got corrupted.

Action: Verify that the metadata repository is up and the document contents are valid.
Level: 1

Type: WARNING

Impact: Other

WCS-19348: Error occurred during permissions related operations. Refresh the roles screen to see the updated information. Contact your administrator for the list of errors.

Cause: An unexpected error occurred during permission related operations.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19348: Error occurred during permissions related operations. Refresh the roles screen to see the updated information. Contact your administrator for the list of errors.

Cause: An unexpected error occurred during permission related operations.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19349: Could not find application role matching the search string {0} due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19349: Could not find application role matching the search string {0} due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19350: Removing role mapping related to service {0} failed due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19350: Removing rolemapping related to service {0} failed due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19351: Could not send notification to administrator as server may be down or Portal workflows are not accessible. Try again after some time.

Cause: Failed to connect to SOA server.

Action: Check if the SOA server is up or if Portal workflows are deployed on SOA server.
Level: 1

Type: ERROR

Impact: Other

WCS-19351: Could not send notification to administrator as server may be down or Portal workflows are not accessible. Try again after some time.

Cause: Failed to connect to SOA server.

Action: Check if the SOA server is up or if Portal workflows are deployed on SOA server.
Level: 1

Type: ERROR

Impact: Other

WCS-19352: Unable to complete the export process as required resources are not available. Another export or import process might be in progress. Please try export again after sometime.

Cause: Export operation failed. Either another export process or portal operation is in progress.

Action: Wait for some time and try the export operation again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19352: Unable to complete the export process as required resources are not available. Another export or import process might be in progress. Please try export again after sometime.

Cause: Export operation failed. Either another export process or portal operation is in progress.

Action: Wait for some time and try the export operation again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19353: Import failed. The portal archive contains new portals without security information.

Cause: The portal archive you are trying to import contains new portals without security. All new portals must include security information.

Action: Export the portals again with security and try again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19353: Import failed. The portal archive contains new portals without security information.

Cause: The portal archive you are trying to import contains new portals without security. All new portals must include security information.

Action: Export the portals again with security and try again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19354: The page {0} (in {1}) cannot be copied due to {2}.

Cause: An error occurred while trying to copy the page.

Action: Refine the logging level, retry the operation, and check the logs for more information about the error, or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19354: The page {0} (in {1}) cannot be copied due to {2}.

Cause: An error occurred while trying to copy the page.

Action: Refine the logging level, retry the operation, and check the logs for more information about the error, or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19355: Unable to make updates to the attributes of the page {0} due to {1}.

Cause: An error occurred while trying to make updates to the page attributes.

Action: Refine the logging level, retry the operation, and check the logs for more information about the error, or contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19355: Unable to make updates to the attributes of the page {0} due to {1}.

Cause: An error occurred while trying to make updates to the page attributes.

Action: Refine the logging level, retry the operation, and check the logs for more information about the error, or contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19356: Unable to open the requested page.

Cause: An unexpected error while opening the page or while creating a copy of it for editing.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19356: Unable to open the requested page.

Cause: An unexpected error while opening the page or while creating a copy of it for editing.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19357: Could not find the page label due to {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19357: Could not find the page label due to {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19358: Identity(s) {0} has already been added to portal.

Cause: An unexpected error occurred while adding users.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19358: Identity(s) {0} has already been added to portal.

Cause: An unexpected error occurred while adding users.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19359: You cannot invite yourself as a member.

Cause: Operation not allowed.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19359: You cannot invite yourself as a member.

Cause: Operation not allowed.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19360: Could not retrieve the role {0}. Please contact administrator.

Cause: An unexpected error occurred.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19360: Could not retrieve the role {0}. Please contact administrator.

Cause: An unexpected error occurred.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19361: Could not find the page visibility due to {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19361: Could not find the page visibility due to {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19362: You cannot add yourself as a member.

Cause: Operation not allowed.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19362: You cannot add yourself as a member.

Cause: Operation not allowed.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19363: SDP Messaging URL cannot be obtained due to {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19363: SDP Messaging URL cannot be obtained due to {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19364: Unable to compute context URL for page {0} with title {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19364: Unable to compute context URL for page {0} with title {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19365: Unable to change password. Contact administrator.

Cause: An unexpected error occurred while setting the password.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19365: Unable to change password. Contact administrator.

Cause: An unexpected error occurred while setting the password.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19366: Export failed. The export process took too long to complete. Use the export WLST command to perform this export operation.

Cause: Export timeout occurred. Either the export set is too large or the policy store information to be exported is too large.

Action: Try exporting fewer portals or use WLST to perform the export operation.
Level: 1

Type: ERROR

Impact: Other

WCS-19366: Export failed. The export process took too long to complete. Use the export WLST command to perform this export operation.

Cause: Export timeout occurred. Either the export set is too large or the policy store information to be exported is too large.

Action: Try exporting fewer portals or use WLST to perform the export operation.
Level: 1

Type: ERROR

Impact: Other

WCS-19367: Import failed. The import process took too long to complete. Use the import WLST command to perform this import operation.

Cause: Import timeout occurred. Either the import set is too large or the policy store information to be imported is too large.

Action: Try importing fewer portals or use WLST to perform the import operation.
Level: 1

Type: ERROR

Impact: Other

WCS-19367: Import failed. The import process took too long to complete. Use the import WLST command to perform this import operation.

Cause: Import timeout occurred. Either the import set is too large or the policy store information to be imported is too large.

Action: Try importing fewer portals or use WLST to perform the import operation.
Level: 1

Type: ERROR

Impact: Other

WCS-19368: Could not find the secondary tab for the current request. PrimaryTab found : {0}, SubTabs : {1}, LastAccesedPage(From previous session) : {2}, Page service cache : {3}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19368: Could not find the secondary tab for the current request. PrimaryTab found : {0}, SubTabs : {1}, LastAccesedPage(From previous session) : {2}, Page service cache : {3}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19369: Get Member Info not supported for scope

Cause: Currently get Member Info not supported.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19369: Get Member Info not supported for scope

Cause: Currently get Member Info not supported.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19370: You can not invite a group for the portal subscription

Cause: Inviting group is not supported

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19370: You can not invite a group for the portal subscription

Cause: Inviting group is not supported

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19371: Failed to read the notification message from backend datastore

Cause: Notification message is null, try setting it

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19371: Failed to read the notification message from backend datastore

Cause: Notification message is null, try setting it

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19372: Group name is empty

Cause: Given group name is empty

Action: Please pass the correct group name
Level: 1

Type: ERROR

Impact: Other

WCS-19372: Group name is empty

Cause: Given group name is empty

Action: Please pass the correct group name
Level: 1

Type: ERROR

Impact: Other

WCS-19373: Granting of role {0} failed for identities {1}.

Cause: Exception occurred while granting a role {0} to identities {1}

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19373: Granting of role {0} failed for identities {1}.

Cause: Exception occurred while granting a role {0} to identities {1}

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19374: Group {0} grant to {1} failed for users {2}. The following users are already granted a role: {3}

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19374: Group {0} grant to {1} failed for users {2}. The following users are already granted a role: {3}

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19375: Group {0} is not found in Identity Store

Cause: Given group name is not found

Action: Please pass the correct group name
Level: 1

Type: ERROR

Impact: Other

WCS-19375: Group {0} is not found in Identity Store

Cause: Given group name is not found

Action: Please pass the correct group name
Level: 1

Type: ERROR

Impact: Other

WCS-19376: {0} User(s) including {1} have already been granted role(s) {2}.

Cause: User(s) already granted roles.

Action: User(s) already granted roles.
Level: 1

Type: ERROR

Impact: Other

WCS-19376: {0} User(s) including {1} have already been granted role(s).

Cause: User(s) already granted roles.

Action: User(s) already granted roles.
Level: 1

Type: ERROR

Impact: Other

WCS-19377: Group(s) {0} has already been granted role(s).

Cause: Group(s) already granted role(s)

Action: Group(s) already granted role(s)
Level: 1

Type: ERROR

Impact: Other

WCS-19377: Group(s) {0} has already been granted role(s).

Cause: Group(s) already granted role(s)

Action: Group(s) already granted role(s)
Level: 1

Type: ERROR

Impact: Other

WCS-19378: Unable to grant role mapping permissions for role {0} in scope {1}

Cause: The role was not granted role mapping permissions. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19378: Unable to grant role mapping permissions for role {0} in scope {1}

Cause: The role was not granted role mapping permissions. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19379: Unable to drop role mapping permissions for role {0} in scope {1}

Cause: There was an error while dropping role mapping permissions for the role. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19379: Unable to drop role mapping permissions for role {0} in scope {1}

Cause: There was an error while dropping role mapping permissions for the role. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19380: Unexpected error while restoring the Default Profile Gallery Page.

Cause: There was an error while removing the profile page customization. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19380: Unexpected error while restoring the Default Profile Gallery Page.

Cause: There was an error while removing the profile page customization. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19381: Unexpected error occurred while setting the language

Cause: Unexpected error occurred while trying to save the language choice

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19381: Unexpected error occurred while setting the language

Cause: Unexpected error occurred while trying to save the language choice

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19382: Copying of members failed for following identities {0}

Cause: Copying of members failed for following identities {0}.

Action: Try again after some time or Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19382: Copying of members failed for following identities {0}

Cause: Copying of members failed for following identities {0}.

Action: Try again after some time or Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19383: Operation not allowed on child portal {0}

Cause: Child portal does not support the operation.

Action: Perform on correct parent portal or Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19383: Operation not allowed on child portal {0}

Cause: Child portal does not support the operation.

Action: Perform on correct parent portal or Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19384: Unexpected error occurred while getting the list of page templates

Cause: Unexpected error occurred while getting the list of Page Templates

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19384: Unexpected error occurred while getting the list of page templates

Cause: Unexpected error occurred while getting the list of Page Templates

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19385: Unexpected error occurred while getting the list of Resource Catalogs

Cause: Unexpected error occurred while getting the list of Resource Catalogs

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19385: Unexpected error occurred while getting the list of Resource Catalogs

Cause: Unexpected error occurred while getting the list of Resource Catalogs

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19386: Unexpected error occurred while getting the languages

Cause: Unexpected error occurred while trying to retrieve the languages

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19386: Unexpected error occurred while getting the languages

Cause: Unexpected error occurred while trying to retrieve the languages

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19387: Unexpected error occurred while creating translations for the imported portal.

Cause: Unexpected error occurred while creating the translations.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19387: Unexpected error occurred while creating translations for the imported portal.

Cause: Unexpected error occurred while creating the translations.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19388: Unexpected error occurred while collapsing the sidebar

Cause: Unexpected error occurred while

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19388: Unexpected error occurred while collapsing the sidebar

Cause: Unexpected error occurred while

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19389: Unexpected error occurred while expanding the sidebar

Cause: Unexpected error occurred while

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19389: Unexpected error occurred while expanding the sidebar

Cause: Unexpected error occurred while

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19390: Unexpected error occurred while getting the list of recently accessed portals.

Cause: Unexpected error occurred while getting the list of recently accessed portals.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19390: Unexpected error occurred while getting the list of recently accessed portals.

Cause: Unexpected error occurred while getting the list of recently accessed portals.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19391: Unexpected error downloading vcard

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19391: Unexpected error downloading vcard

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19392: Unexpected error looking up user profile

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19392: Unexpected error looking up user profile

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19393: Unexpected error launching resource

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19393: Unexpected error launching resource

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19394: Unexpected error occurred while getting the list of portals current user can access.

Cause: Unexpected error occurred while getting the list of portals current user can access.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19394: Unexpected error occurred while getting the list of portals current user can access.

Cause: Unexpected error occurred while getting the list of portals current user can access.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19395: A page named {0} already exists.

Cause: A page with the specified name exists.

Action: Specify a unique name for the page.
Level: 1

Type: ERROR

Impact: Other

WCS-19395: A page named {0} already exists.

Cause: A page with the specified name exists.

Action: Specify a unique name for the page.
Level: 1

Type: ERROR

Impact: Other

WCS-19396: Unexpected error while restoring the Default Page.

Cause: There was an error while removing the page customization. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19396: Unexpected error while restoring the Default Page.

Cause: There was an error while removing the page customization. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19397: Unexpected error while changing the permission model for portal {0}.

Cause: Unexpected error while changing the permission model for portal {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19397: Unexpected error while changing the permission model for portal {0}.

Cause: Unexpected error while changing the permission model for portal {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19398: No users/groups selected

Cause: No users/groups were selected to perform the requested operation on.

Action: Select one or more users/groups and retry the operation.
Level: 1

Type: ERROR

Impact: Other

WCS-19398: No users/groups selected

Cause: No users/groups were selected to perform the requested operation on.

Action: Select one or more users/groups and retry the operation.
Level: 1

Type: ERROR

Impact: Other

WCS-19399: Exception occurred while searching groups for a user :{0}

Cause: An unexpected error/exception occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19399: Exception occurred while searching groups for a user :{0}

Cause: An unexpected error/exception occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19400: Failed to determine public access on page {0} due to {1}

Cause: An unexpected error/exception occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19400: Failed to determine public access on page {0} due to {1}

Cause: An unexpected error/exception occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19401: "Unexpected error getting read lock on {0}

Cause: An unexpected error/exception occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19401: "Unexpected error getting read lock on {0}

Cause: An unexpected error/exception occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19402: Error determining the template for the current page

Cause: Unexpected severe error.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19402: Error determining the template for the current page

Cause: Unexpected severe error.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19403: Error occurred while fetching the list of navigations.

Cause: Unexpected error while fetching list of navigations.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19403: Error occurred while fetching the list of navigations.

Cause: Unexpected error while fetching list of navigations.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19404: Scope list cannot be empty.

Cause: Unexpected error while fetching list of portals.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19404: Scope list cannot be empty.

Cause: Unexpected error while fetching list of portals.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19405: Unable to set the security parent of {0} to {1}.

Cause: Unexpected error while setting the security parent.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19405: Unable to set the security parent of {0} to {1}.

Cause: Unexpected error while setting the security parent.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19406: Unable to delete base docs from archive.

Cause: Unexpected error while deleting base docs from archive.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19406: Unable to delete base docs from archive.

Cause: Unexpected error while deleting base docs from archive.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19407: Resources conflict. Base resource on target is not same as the base resource on source. Import cannot proceed.

Cause: Resources conflict occurred at the target.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19407: Resources conflict. Base resource on target is not same as the base resource on source. Import cannot proceed.

Cause: Resources conflict occurred at the target.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19408: Unable to flush changes for deleted base docs from archive.

Cause: Unexpected error while deleting base docs from archive.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19408: Unable to flush changes for deleted base docs from archive.

Cause: Unexpected error while deleting base docs from archive.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19409: Could not create site registry as folder does not exists.

Cause: Unexpected error while creating the site registry.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19409: Could not create site registry as folder does not exists.

Cause: Unexpected error while creating the site registry.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19410: Error occurred while refreshing template cache.

Cause: Unexpected error occurred while refreshing template cache.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19410: Error occurred while refreshing template cache.

Cause: Unexpected error occurred while refreshing template cache.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19411: {0}.

Cause: Unexpected error while fetching list of navigations.

Action: Contact Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19411: {0}.

Cause: Unexpected error while fetching list of navigations.

Action: Contact Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19412: Error occurred while saving the custom attributes in metadata.

Cause: Unexpected error occurred while saving the custom attributes in metadata.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19412: Error occurred while saving the custom attributes in metadata.

Cause: Unexpected error occurred while saving the custom attributes in metadata.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19413: Error occurred while granting permission to portal {0} for the provisioned service(s).

Cause: Unexpected error occurred while granting permission.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19413: Error occurred while granting permission to portal {0} for the provisioned service(s).

Cause: Unexpected error occurred while granting permission.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19414: Error occurred while checking for portal permission.

Cause: Error occurred while checking community manage permission.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19414: Error occurred while checking for portal permission.

Cause: Error occurred while checking community manage permission.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19415: For user {0}, couldn''t retrieve the list of pages last accessed due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19415: For user {0}, couldn''t retrieve the list of pages last accessed due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19416: Check for valid repository failed.

Cause: Either the database is down or the WebCenter Portal repository is not installed.

Action: Check the exception's details to why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WCS-19416: Check for valid repository failed.

Cause: Either the database is down or the WebCenter Portal repository is not installed.

Action: Check the exception's details to why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WCS-19417: For user {0}, the last accessed page couldn''t be found due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19417: For user {0}, the last accessed page couldn''t be found due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19418: For user {0}, couldn''t clean the last accessed page due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19418: For user {0}, couldn''t clean the last accessed page due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19419: For user {0}, couldn''t retrieve the last accessed page in {1} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19419: For user {0}, couldn''t retrieve the last accessed page in {1} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19420: Unexpected error occurred while checking custom access for the portal {0}.

Cause: Likely the authorizer class specified in WebCenter Portal configuration could not be accessed. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19420: Unexpected error occurred while checking custom access for the portal {0}.

Cause: Likely the authorizer class specified in WebCenter Portal configuration could not be accessed. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19421: Denying access for scope {0} as {1} property not specified in WebCenter Portal configuration

Cause: The authorizer class is not specified against specified property in WebCenter Portal Configuration

Action: Define the specified property pointing to the required ResourceAuthorizer implementation in WebCenter Portal configuration
Level: 1

Type: WARNING

Impact: Other

WCS-19421: Denying access for scope {0} as {1} property not specified in WebCenter Portal configuration

Cause: The authorizer class is not specified against specified property in WebCenter Portal Configuration

Action: Define the specified property pointing to the required ResourceAuthorizer implementation in WebCenter Portal configuration
Level: 1

Type: WARNING

Impact: Other

WCS-19422: Grant Role to Role Mapped Service for Portal User role not supported in scope {0}

Cause: Grant Role to Role Mapped Service for Portal User role not supported in scope {0}.

Action: Do not try this operation in this scope
Level: 1

Type: ERROR

Impact: Other

WCS-19422: Grant Role to Role Mapped Service for Portal User role not supported in scope {0}

Cause: Grant Role to Role Mapped Service for Portal User role not supported in scope {0}.

Action: Do not try this operation in this scope
Level: 1

Type: ERROR

Impact: Other

WCS-19423: Grant Role to Role Mapped Service for Public User role not supported in scope {0}

Cause: Grant Role to Role Mapped Service for Public User role not supported in scope {0}.

Action: Do not try this operation in this scope
Level: 1

Type: ERROR

Impact: Other

WCS-19423: Grant Role to Role Mapped Service for Public User role not supported in scope {0}

Cause: Grant Role to Role Mapped Service for Public User role not supported in scope {0}.

Action: Do not try this operation in this scope
Level: 1

Type: ERROR

Impact: Other

WCS-19424: Unable to delete site resource registry file from archive.

Cause: Unexpected error while deleting site resource registry file from archive.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19424: Unable to delete site resource registry file from archive.

Cause: Unexpected error while deleting site resource registry file from archive.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19425: Checking whether portal is published to Portal user is not supported in Home Portal.

Cause: An attempt was made to check whether the portal is published to Portal user in Home portal.

Action: This API must be invoked in the context of portal and not Home portal
Level: 1

Type: ERROR

Impact: Other

WCS-19425: Checking whether portal is published to Portal user is not supported in Home Portal.

Cause: An attempt was made to check whether the portal is published to Portal user in Home portal.

Action: This API must be invoked in the context of portal and not Home portal
Level: 1

Type: ERROR

Impact: Other

WCS-19426: Encountered exception: {0}. For diagnosis, turn on the logging level to FINEST and retry the operation. Details about the current state: {1}

Cause: An exception was encountered unexpectedly.

Action: Turn on the logging level to FINEST and retry the operation.
Level: 1

Type: WARNING

Impact: Other

WCS-19426: Encountered exception: {0}. For diagnosis, turn on the logging level to FINEST and retry the operation. Details about the current state: {1}

Cause: An exception was encountered unexpectedly.

Action: Turn on the logging level to FINEST and retry the operation.
Level: 1

Type: WARNING

Impact: Other

WCS-19427: Error in setting Show Page of the business role page.

Cause: Unexpected error occurred while setting Show Page of the business role page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19427: Error in setting Show Page of the business role page.

Cause: Unexpected error occurred while setting Show Page of the business role page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19428: Unexpected error occurred while importing the security policy. Unable to import the policy store.

Cause: An unexpected error occurred while importing policy store metadata from the import archive.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19428: Unexpected error occurred while importing the security policy. Unable to import the policy store.

Cause: An unexpected error occurred while importing policy store metadata from the import archive.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19429: Unexpected error occurred while checking if the current user can {0} the scope {1}.

Cause: Unexpected error occurred while checking if the current user can {0} the scope {1}.

Action: Try again later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19429: Unexpected error occurred while checking if the current user can {0} the scope {1}.

Cause: Unexpected error occurred while checking if the current user can {0} the scope {1}.

Action: Try again later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19430: Unexpected error occurred while checking if the current user can {0} the asset {1} in scope {2}.

Cause: Unexpected error occurred while checking if the current user can {0} the asset {1} in scope {2}.

Action: Try again later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19430: Unexpected error occurred while checking if the current user can {0} the asset {1} in scope {2}.

Cause: Unexpected error occurred while checking if the current user can {0} the asset {1} in scope {2}.

Action: Try again later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19431: Unexpected error occurred while fetching roles for user {0} in portal {1}.

Cause: Unexpected error occurred while fetching roles for user {0} in portal {1}.

Action: Try again later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19431: Unexpected error occurred while fetching roles for user {0} in portal {1}.

Cause: Unexpected error occurred while fetching roles for user {0} in portal {1}.

Action: Try again later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19432: Fetching the roles of current user is not supported in default scope.

Cause: Fetching the roles of current user is not supported in default scope.

Action: Do not try this operation
Level: 1

Type: ERROR

Impact: Other

WCS-19432: Fetching the roles of current user is not supported in default scope.

Cause: Fetching the roles of current user is not supported in default scope.

Action: Do not try this operation
Level: 1

Type: ERROR

Impact: Other

WCS-19433: Unexpected error occurred while setting action {0} to role {1}.

Cause: Unexpected error occurred while setting action {0} to role {1}.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19433: Unexpected error occurred while setting action {0} to role {1}.

Cause: Unexpected error occurred while setting action {0} to role {1}.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19434: Fatal error occurred while getting members count.

Cause: An unexpected error occurred while getting the members count.

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19434: Fatal error occurred while getting members count.

Cause: An unexpected error occurred while getting the members count.

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19435: Couldn''t get the first accessible page for the Home portal due to {1}.

Cause: Error in getting the first accessible page for the Home portal.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19435: Couldn''t get the first accessible page for the Home portal due to {1}.

Cause: Error in getting the first accessible page for the Home portal.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19436: The community query permission is not found

Cause: The community query permission is not found.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19436: The community query permission is not found

Cause: The community query permission is not found.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19437: The community manage membership permission is not found

Cause: The community manage membership permission is not found.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19437: The community manage membership permission is not found

Cause: The community manage membership permission is not found.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19438: The community view membership permission is not found

Cause: The community view membership permission is not found.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19438: The community view membership permission is not found

Cause: The community view membership permission is not found.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19439: The community edit membership permission is not found

Cause: The community edit membership permission is not found.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19439: The community edit membership permission is not found

Cause: The community edit membership permission is not found.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19440: One or more pages of portal {0} is being edited by other users. The export archive may not contain the page changes.

Cause: One or more portal pages is being edited by other users. The export archive may not contain the page changes.

Action: Close all pages open in edit mode and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19440: One or more pages of portal {0} is being edited by other users. The export archive may not contain the page changes.

Cause: One or more portal pages is being edited by other users. The export archive may not contain the page changes.

Action: Close all pages open in edit mode and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19441: One or more pages of portal {0} is being edited by other users. The import may not complete properly.

Cause: One or more portal page is in edit mode. The import may not complete properly.

Action: Close all pages open in edit mode and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19441: One or more pages of portal {0} is being edited by other users. The import may not complete properly.

Cause: One or more portal page is in edit mode. The import may not complete properly.

Action: Close all pages open in edit mode and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19442: Invalid input - unmatched quotes

Cause: A string was provided with unmatched quotes.

Action: Ensure all quotes are opened and closed.
Level: 1

Type: ERROR

Impact: Other

WCS-19442: The method {0} is currently not supported.

Cause: There is no implementation for this method.

Action: Do not use this API.
Level: 1

Type: ERROR

Impact: Other

WCS-19443: Unexpected error occurred while creating the experience definition document due to {0}.

Cause: Unexpected error occurred while creating the experience definition document.

Action: Try again later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19444: Unexpected error occurred while extracting the rules parameters due to {0}.

Cause: Unexpected error occurred while extracting the rules parameters.

Action: Try again later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19445: Unexpected error occurred while evaluating the rules due to {0}.

Cause: Unexpected error occurred while evaluating the rules.

Action: Try again later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19446: Unexpected error occurred while loading the experience defintion due to {0}.

Cause: Unexpected error occurred while evaluating the rules.

Action: Try again later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19447: Unexpected error occurred while loading the experience rules due to {0}.

Cause: Unexpected error occurred while evaluating the rules.

Action: Try again later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19448: Unexpected error occurred while loading the experience definition document due to {0}.

Cause: Unexpected error occurred while loading the experience definition document.

Action: Try again later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19449: Unexpected error occurred while checking if the experience defintion is enabled due to {0}.

Cause: Unexpected error occurred while checking if the experience defintion.

Action: Try again later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19450: Unable to fetch custom property {0} at the application level

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: WARNING

Impact: Other

WCS-19450: Unable to fetch custom property {0} at the application level

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: WARNING

Impact: Other

WCS-19451: Unable to fetch custom property {0} from scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: WARNING

Impact: Other

WCS-19451: Unable to fetch custom property {0} from scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: WARNING

Impact: Other

WCS-19452: Could not initialize Default Portal Setting

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Other

WCS-19452: Could not initialize Default Portal Setting

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Other

WCS-19453: Could not update the default portal identity settings

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Other

WCS-19453: Could not update the default portal identity settings

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Other

WCS-19454: Could not update the default portal public setting

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Other

WCS-19454: Could not update the default portal public setting

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Other

WCS-19455: Could not update the default portal default setting

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Other

WCS-19455: Could not update the default portal default setting

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Other

WCS-19456: Could not set the redirect on login setting for default portal

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Other

WCS-19456: Could not set the redirect on login setting for default portal

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Other

WCS-19457: Could not update default portal settings to handle rename of portal from {0} to {1}

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details. Change the portal manually in Administration screens
Level: 1

Type: ERROR

Impact: Other

WCS-19457: Could not update default portal settings to handle rename of portal from {0} to {1}

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details. Change the portal manually in Administration screens
Level: 1

Type: ERROR

Impact: Other

WCS-19458: Could not update default portal settings to handle delete of portal {0}

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details. Change the portal manually in Administration screens
Level: 1

Type: ERROR

Impact: Other

WCS-19458: Could not update default portal settings to handle delete of portal {0}

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details. Change the portal manually in Administration screens
Level: 1

Type: ERROR

Impact: Other

WCS-19459: The default portal configuration is being modified by another user. Try operation after some time.

Cause: >Another admin user is updating the default portal configuration

Action: Try the operation after some time
Level: 1

Type: WARNING

Impact: Other

WCS-19459: The default portal configuration is being modified by another user. Try operation after some time.

Cause: >Another admin user is updating the default portal configuration

Action: Try the operation after some time
Level: 1

Type: WARNING

Impact: Other

WCS-19460: Could not fetch the default portal configuration from webcenter-config

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Go the Default Portal Configuration screen and change the default setting to desired values
Level: 1

Type: WARNING

Impact: Other

WCS-19460: Could not fetch the default portal configuration from webcenter-config

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Go the Default Portal Configuration screen and change the default setting to desired values
Level: 1

Type: WARNING

Impact: Other

WCS-19461: Unexpected error while fetching the default portal due to {0}

Cause: Unexpected error while fetching the default portal

Action: Unexpected error while fetching the default portal
Level: 1

Type: WARNING

Impact: Other

WCS-19461: Invalid input - unmatched quotes

Cause: A string was provided with unmatched quotes.

Action: Ensure all quotes are opened and closed.
Level: 1

Type: ERROR

Impact: Other

WCS-19462: User {0} does not have the privileges required for this operation on Portals/Portal Templates. Verify that the user has 'Create Portal' permission while performing import or deployment operation, 'Create and Manage Portal' permission while performing redeployment operation and 'Manage Portal' permission while performing export or propagation operation.

Cause: Check if the user has required permission on Portals for performing lifecycle operations.

Action: Try performing the operation as an administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19462: Unexpected error while fetching the default portal due to {0}

Cause: Unexpected error while fetching the default portal

Action: Unexpected error while fetching the default portal
Level: 1

Type: WARNING

Impact: Other

WCS-19463: Error occurred while importing the security policy as the UCM server is down.

Cause: Error occurred while importing the security policy as the UCM server is down.

Action: Start the UCM server and retry this operation
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19463: User {0} does not have the privileges required for this operation. Verify that the user has the 'Manage All' permission for Portals/Portal Templates which is required to perform this operation.

Cause: Check if the user has the 'Manage All' permission on Portals

Action: Try performing the operation as an administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19464: User {0} not authorized to view Application.

Cause: User not authorized to view Application

Action: Contact Administrator to grant more permissions.
Level: 1

Type: ERROR

Impact: Other

WCS-19464: User {0} not authorized to view Application.

Cause: User not authorized to view Application

Action: Contact Administrator to grant more permissions.
Level: 1

Type: ERROR

Impact: Other

WCS-19465: User {0} not authorized to configure Application.

Cause: User not authorized to configure Application

Action: Contact Administrator to grant more permissions.
Level: 1

Type: ERROR

Impact: Other

WCS-19465: User {0} not authorized to configure Application.

Cause: User not authorized to configure Application

Action: Contact Administrator to grant more permissions.
Level: 1

Type: ERROR

Impact: Other

WCS-19466: Error occurred in creating translated scope resource bundle {0} due to {1}.

Cause: Unexpected error while creating scope resource bundle for newely created Portal/Template.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-19466: Error occurred in creating translated scope resource bundle {0} due to {1}.

Cause: Unexpected error while creating scope resource bundle for newely created Portal/Template.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-19467: Error occurred while parsing document name due to {0}.

Cause: Unexpected error while parsing scope resource bundle file name.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-19467: Error occurred while parsing document name due to {0}.

Cause: Unexpected error while parsing scope resource bundle file name.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-19468: Unexpected error occurred while adding Business Role Page for Impersonation due to {0}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19468: Unexpected error occurred while adding Business Role Page for Impersonation due to {0}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19469: Error occurred while adding Impersonation page:{0} to pages:{1} due to {2}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19469: Error occurred while adding Impersonation page:{0} to pages:{1} due to {2}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19470: Error occurred while granting navigation permissions for role {0} for the scope {1} due to {2}

Cause: An unexpected error occurred while granting the user permission

Action: Contact the WebCenter Portal administrator
Level: 1

Type: WARNING

Impact: Other

WCS-19470: Error occurred while granting navigation permissions for role {0} for the scope {1} due to {2}

Cause: An unexpected error occurred while granting the user permission

Action: Contact the WebCenter Portal administrator
Level: 1

Type: WARNING

Impact: Other

WCS-19471: Error occurred while deleting the list of tabs to persistence store

Cause: An unexpected error occurred while deleting the list of pages.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19472: Unexpected error occurred while fetching current device group due to {0}

Cause: Unexpected error occurred while fetching current device group due to {0}

Action: Contact Administrator for more details
Level: 1

Type: ERROR

Impact: Other

WCS-19473: Get GUID call for LibOVDUser {0} returned null, which caused NullPointerException.

Cause: Misconfiguration found in jps-config.xml.

Action: Please contact the WebCenter Portal administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19474: There are no Portal Server URL connections set.

Cause: There are no Portal Server URL connections set for deploying the portals.

Action: Please create a Portal Server URL Connection.
Level: 1

Type: ERROR

Impact: Other

WCS-19475: Failed to update application ready status

Cause: Status update to indicate application readiness with ReadyApp failed. There may be issues with registering or configuring the application.

Action: Examine WebLogic Server debug logs for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-19476: Failed to update application not ready status

Cause: Status update to indicate application non-readiness with ReadyApp failed. There may be issues with registering or configuring the application.

Action: Examine WebLogic Server debug logs for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-19477: Creation of seeded role is not supported for scope {0}

Cause: Currently the creation of seeded role is not supported.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19478: Unable to grant permissions to {0} role in the policy store

Cause: An attempt to grant permissions failed due to unexpected errors.

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-20001: Error while creating the blog {0}.

Cause: Error while creating the blog.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20002: Error while deleting the blog {0}.

Cause: Error while deleting the blog.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20003: Error while creating the blog entry {0}.

Cause: Error while creating the blog entry.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20004: Error while deleting the blog entry {0}.

Cause: Error while deleting the blog entry.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20005: Error while deleting the blog container {0}.

Cause: Error while deleting the blog container.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20006: Error while creating the blog container {0}.

Cause: Error while creating the blog container.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20007: Error while editing the blog entry {0}.

Cause: Error while editing the blog entry.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20010: No Blog Selected

Cause: No blog was seleced! Hence couldnot complete operation

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20011: No Container Selected

Cause: No container was seleced! Hence couldn't complete operation

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20013: No Blog Entry Selected

Cause: No entry was selected! Hence couldn't complete the operation

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20014: Error while listing the blogs.

Cause: Error while listing the blogs.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20015: Error while listing the blog container.

Cause: Error while listing the blog container.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20016: Error while listing the blog entries.

Cause: Error while listing the blog entries.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20017: No Blog Container Found.

Cause: No Blog Container Found

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20018: {0} not accessible.

Cause: Contact your administrator for access.

Action: Check if data exist or check for appropriate permissions.
Level: 1

Type: WARNING

Impact: Other

WCS-20020: Error while listing the recent blogs.

Cause: Error while listing the recent blogs.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20021: Error while listing the popular blogs.

Cause: Error while listing the popular blogs.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20022: Error while listing the favourite blogs.

Cause: Error while listing the popular blogs.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-23001: unexpected error has occurred

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26001: Search Configuration Error: {0}

Cause: A configuration error has been encountered.

Action: Refer to the error details and the documentation for how to debug this.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-26041: General Search Execution Error

Cause: A general execution error has been encountered.

Action: Query execution error is dependent on the service running it. Refer to the Query in the log and the documentation for the service involved to debug this.
Level: 1

Type: ERROR

Impact: Other

WCS-26042: The execution of the query does not complete within the execution time limit

Cause: The search query does not complete within the time limit.

Action: Re-try the search query again later.
Level: 1

Type: ERROR

Impact: Other

WCS-26042: The execution of the query does not complete within the execution time limit

Cause: The search query does not complete within the time limit.

Action: Re-try the search query again later.
Level: 1

Type: ERROR

Impact: Other

WCS-26061: General Search Response Error

Cause: A general response error has been encountered.

Action: Query execution response error is dependent on the service running it. Refer to the Query in the log and the documentation for the service involved to debug this.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-26143: Failed to commit changes to Search preferences, encountering {0}.

Cause: Some underlying MDS issues with the Preferences implementation is causing the failure.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26144: An error occurred while parsing the default full crawl interval "{0}".

Cause: An internal error occurred while trying to instantiate a DatatypeFactory for parsing Duration values.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-26144: An error occurred while parsing the default full crawl interval "{0}".

Cause: An internal error occurred while trying to instantiate a DatatypeFactory for parsing Duration values.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-26145: An invalid full crawl interval "{0}" was specified in adf-config.xml.

Cause: The fullCrawlInterval attribute of the crawl-properties element in adf-config.xml may not be well-formed or valid.

Action: Make sure that the fullCrawlInterval attribute value is in the duration format as defined in the W3C XML Schema 1.0.
Level: 1

Type: WARNING

Impact: Other

WCS-26145: An invalid full crawl interval "{0}" was specified in adf-config.xml.

Cause: The fullCrawlInterval attribute of the crawl-properties element in adf-config.xml may not be well-formed or valid.

Action: Make sure that the fullCrawlInterval attribute value is in the duration format as defined in the W3C XML Schema 1.0.
Level: 1

Type: WARNING

Impact: Other

WCS-26146: An invalid full crawl interval "{0}" was specified for service {1}.

Cause: The fullCrawlInterval attribute of a service-crawl-properties element in adf-config.xml may not be well-formed or valid.

Action: Make sure that the fullCrawlInterval attribute value is in the duration format as defined in the W3C XML Schema 1.0.
Level: 1

Type: WARNING

Impact: Other

WCS-26146: An invalid full crawl interval "{0}" was specified for service {1}.

Cause: The fullCrawlInterval attribute of a service-crawl-properties element in adf-config.xml may not be well-formed or valid.

Action: Make sure that the fullCrawlInterval attribute value is in the duration format as defined in the W3C XML Schema 1.0.
Level: 1

Type: WARNING

Impact: Other

WCS-26147: An error occurred while parsing the crawl-properties element in adf-config.xml.

Cause: An internal error occurred while trying to parse the crawl-properties element in adf-config.xml.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-26147: An error occurred while parsing the crawl-properties element in adf-config.xml.

Cause: An internal error occurred while trying to parse the crawl-properties element in adf-config.xml.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-26161: Encountered a message from MDS indicating unsupported operation while deleting a Saved Search with ID "{0}", MO Reference name "{1}", and MO Absolute Name "{2}".

Cause: The deletion of a Saved Search triggered some MDS operation that is not supported on said Saved Search document.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-26185: Encountered an MDS exception "{0}" with message "{1}" while creating default service list in MDS.

Cause: An underlying MDS exception occurred during the creation of the service list in the Search UI Metadata.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26186: Encountered an MDS exception "{1}" with message "{2}" while updating UI Metadata Object in MDS with Metadata Object absolute name "{0}".

Cause: An underlying MDS exception occurred during the update of the Search UI Metadata.

Action: The update by this user will be lost. Refresh the page and continue.
Level: 1

Type: ERROR

Impact: Other

WCS-26186: Encountered an MDS exception "{1}" with message "{2}" while updating UI Metadata Object in MDS with Metadata Object absolute name "{0}".

Cause: An underlying MDS exception occurred during the update of the Search UI Metadata.

Action: The update by this user will be lost. Refresh the page and continue.
Level: 1

Type: ERROR

Impact: Other

WCS-26201: Encountered "{2}" with message "{3}" when loading QueryManager Class "{0}" for service "{1}" in Extension Handler.

Cause: Any one of the possible exceptions resulting from loading a class using reflection occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-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-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-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-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-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-26207: Oracle Secure Enterprise Search (SES) is not configured. Search query cannot be executed.

Cause: Oracle Secure Enterprise Search (SES) is not configured.

Action: Oracle Secure Enterprise Search (SES) must be configured before search query can be executed.
Level: 1

Type: ERROR

Impact: Other

WCS-26221: Search execution was interrupted because of "{0}" with message "{1}".

Cause: The service search execution was interrupted because of a timeout or a failure.

Action: Examine the log to determine the root cause and take appropriate debugging steps.
Level: 1

Type: ERROR

Impact: Other

WCS-26221: Search execution was interrupted because of "{0}" with message "{1}".

Cause: The service search execution was interrupted because of a timeout or a failure.

Action: Examine the log to determine the root cause and take appropriate debugging steps.
Level: 1

Type: ERROR

Impact: Other

WCS-26222: Search execution failure for service "{0}", encountering "{1}" with message "{2}".

Cause: An exception occurred while executing search.

Action: Examine the log to determine the root cause and take appropriate debugging steps.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-26224: Query Handler creation of {0} was interrupted.

Cause: The Query Handler named took too long to be created and was timed out.

Action: Increase your prepareTimeoutMs value in the search-config section of the adf-config.xml file
Level: 1

Type: WARNING

Impact: Other

WCS-26225: {0} occurred during Search result transfer of service with identifier "{1}" with message "{2}"

Cause: An unexpected exception occurred when transferring search results after execution.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26225: {0} occurred during Search result transfer of service with identifier "{1}" with message "{2}"

Cause: An unexpected exception occurred when transferring search results after execution.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26226: Failed to extract Refiners from executor {0}.

Cause: Failure occurred when extracting refiners from the execution results of an executor.

Action: Inspect the failure message and fix accordingly.
Level: 1

Type: WARNING

Impact: Other

WCS-26226: Failed to extract Refiners from executor {0}.

Cause: Failure occurred when extracting refiners from the execution results of an executor.

Action: Inspect the failure message and fix accordingly.
Level: 1

Type: WARNING

Impact: Other

WCS-26227: Column not found for {0}

Cause: When formulating an query with a condition based on an attribute, the attribute is not found.

Action: Inspect your input and make sure that the values for the attributes are one of "name", "title", "description", "creator", "created", "modifier", "modified", and "tags".
Level: 1

Type: WARNING

Impact: Other

WCS-26227: Column not found for {0}

Cause: When formulating an query with a condition based on an attribute, the attribute is not found.

Action: Inspect your input and make sure that the values for the attributes are one of "name", "title", "description", "creator", "created", "modifier", "modified", and "tags".
Level: 1

Type: WARNING

Impact: Other

WCS-26228: Parsing of date operand "{0}" failed

Cause: When formulating an query with a condition based on a date attribute, the date value specified fails to be parsed.

Action: Inspect your date attribute and make sure that it follows the format: "yyyy-MM-dd"
Level: 1

Type: WARNING

Impact: Other

WCS-26228: Parsing of date operand "{0}" failed

Cause: When formulating an query with a condition based on a date attribute, the date value specified fails to be parsed.

Action: Inspect your date attribute and make sure that it follows the format: "yyyy-MM-dd"
Level: 1

Type: WARNING

Impact: Other

WCS-26229: Search query execution timed out for service "{0}".

Cause: The search query does not complete within the time limit.

Action: Re-try the search query again later.
Level: 1

Type: WARNING

Impact: Other

WCS-26229: Search query execution timed out for service "{0}".

Cause: The search query does not complete within the time limit.

Action: Re-try the search query again later.
Level: 1

Type: WARNING

Impact: Other

WCS-26281: getSessionVersion failed with Exception {0}

Cause: Operation to get Sessions Version from SES failed.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26282: getAllFacets failed with Exception {0}

Cause: Operation to fetch allfacets from SES failed.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26283: getAllAttributes failed with Exception {0}

Cause: Operation to fetch allattributes from SES failed.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26284: getAllAttributes failed with Exception {0}

Cause: Operation to fetch all attributes from SES failed.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26322: Skipping consumption of a Date ComplexPredicate with 1 child because its type {0} is not AttributePredicate<Calendar> as expected.

Cause: A Date ComplexPredicate was passed down from the query that contains the wrong type for its single child.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-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-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-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-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-26327: Query execution failed for {0}.

Cause: Query execution failed.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26328: Search failure: time out error

Cause: Search execution timed out.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26328: Search failure: time out error

Cause: Search execution timed out.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26329: Search failure: problem preparing search executor

Cause: Unable to create a search executor.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26329: Search failure: problem preparing search executor

Cause: Unable to create a search executor.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26330: Search failure: problem with execution

Cause: Search execution problem.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26330: Search failure: problem with execution

Cause: Search execution problem.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26331: Search failure: problem with adding refiner

Cause: Unable to add refiner.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26331: Search failure: problem with adding refiner

Cause: Unable to add refiner.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26332: Search failure: problem with removing refiner

Cause: Unable to remove refiner.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26332: Search failure: problem with removing refiner

Cause: Unable to remove refiner.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26333: Search failure: problem with updating refiner

Cause: Unable to update the refiner.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26333: Search failure: problem with updating refiner

Cause: Unable to update the refiner.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26341: Search UI Metadata Lookup Failed: {0}

Cause: The UI Metadata document necessary for rendering Search views could not be found.

Action: Refer to the error messages presented in the dialog box and act accordingly.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-26393: Failed to get attributes of resource "{0}"

Cause: Failed to get attributes of a given resource.

Action: Examine the log for the root cause and take appropriate debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26396: Search Box Size not a number - "{0}". Using Default size instead.

Cause: taskflow parameter passed to this component not an integer.

Action: Examine the taskflow parameter and replace value with a number.
Level: 1

Type: WARNING

Impact: Other

WCS-26396: Search Box Size not a number - "{0}". Using Default size instead.

Cause: taskflow parameter passed to this component not an integer.

Action: Examine the taskflow parameter and replace value with a number.
Level: 1

Type: WARNING

Impact: Other

WCS-26397: Search Taskflow ID does not correspond to a valid taskflow. Using Default taskflow instead.

Cause: taskflow parameter passed to this component not a valid taskflow id.

Action: Examine the taskflow parameter and replace with appropriate value.
Level: 1

Type: WARNING

Impact: Other

WCS-26397: Search Taskflow ID does not correspond to a valid taskflow. Using Default taskflow instead.

Cause: taskflow parameter passed to this component not a valid taskflow id.

Action: Examine the taskflow parameter and replace with appropriate value.
Level: 1

Type: WARNING

Impact: Other

WCS-26398: Search Scope ID parameter value is not a Scope object - "{0}".

Cause: taskflow parameter EL or value is not a Scope object

Action: Examine the taskflow parameter and replace value with a valid Scope object.
Level: 1

Type: WARNING

Impact: Other

WCS-26398: Search Scope ID parameter value is not a Scope object - "{0}".

Cause: taskflow parameter EL or value is not a Scope object

Action: Examine the taskflow parameter and replace value with a valid Scope object.
Level: 1

Type: WARNING

Impact: Other

WCS-26399: Service with service ID: "{0}" is not registered and cannot be included in Categories list.

Cause: Service Id is not a registered service.

Action: Have an administrator remove service from Services to be included list.
Level: 1

Type: WARNING

Impact: Other

WCS-26400: Locale or Service Registry not found.

Cause: Taskflow is not in an appropriate application or adf context was lost.

Action: Refresh page or place taskflow in appropriate template.
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-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-26402: Received status "{0}" during proxy login with application entity "{1}" to Oracle SES at [{2}], as search user "{3}". Defaulting to public.

Cause: The application entity may not have been provisioned in the identity management system used by SES, or its password may have been expired.

Action: Log on to the Oracle SES administration tool and make sure that the application entity has been provisioned. Then make sure that the account is enabled on the identity management system and has not expired.
Level: 1

Type: WARNING

Impact: Other

WCS-26403: Federation Trusted Entity parameters not configured. Search as public user on Oracle SES.

Cause: Federation Trusted Entity parameters not configured.

Action: Configure Federation Trusted Entity parameters.
Level: 1

Type: WARNING

Impact: Other

WCS-26403: Federation Trusted Entity parameters not configured. Search as public user on Oracle SES.

Cause: Federation Trusted Entity parameters not configured.

Action: Configure Federation Trusted Entity parameters.
Level: 1

Type: WARNING

Impact: Other

WCS-26421: Failed to initialize data group ID from {0} in {1}, encountering {2}

Cause: Either the group ID in question does not exist or SES is down.

Action: Make sure that SES is up and check the group IDs present on SES.
Level: 1

Type: WARNING

Impact: Other

WCS-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-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-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-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-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-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-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-26444: Invalid value for addrType attribute in "{1}" entry. Expected value is "{0}"

Cause: Incorrect value for addrType attribute found in connections.xml

Action: Update connections.xml with the correct value for addrType attribute
Level: 1

Type: ERROR

Impact: Other

WCS-26451: Failed to create an instance of class "{0}"

Cause: Failed creating an instance of the XML object representing an SES admin object.

Action: A RuntimeException would have been thrown to propagate the underlying Exception causing this. Please inspect the log to see what else can be done to fix the issue.
Level: 1

Type: WARNING

Impact: Other

WCS-26451: Failed to create an instance of class "{0}"

Cause: Failed creating an instance of the XML object representing an SES admin object.

Action: A RuntimeException would have been thrown to propagate the underlying Exception causing this. Please inspect the log to see what else can be done to fix the issue.
Level: 1

Type: WARNING

Impact: Other

WCS-26461: Failed to marshal SES Filter for Advanced Search due to JAXB issues - {0}

Cause: A JAXB problem has caused the marshalling of an SES filter before sending it to SES for execution.

Action: Examine the log to look at the XML structure to verify validity.
Level: 1

Type: WARNING

Impact: Other

WCS-26461: Failed to marshal SES Filter for Advanced Search due to JAXB issues - {0}

Cause: A JAXB problem has caused the marshalling of an SES filter before sending it to SES for execution.

Action: Examine the log to look at the XML structure to verify validity.
Level: 1

Type: WARNING

Impact: Other

WCS-26462: SES Search Execution failed, encountering "{0}" with message "{1}".

Cause: The cause is embedded in the Exception and can be SES-specific.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: ERROR

Impact: Other

WCS-26462: SES Search Execution failed, encountering "{0}" with message "{1}".

Cause: The cause is embedded in the Exception and can be SES-specific.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: ERROR

Impact: Other

WCS-26463: Can not convert SES Result Element value from {0} to {1}

Cause: Conversion from SES Result Element value failed.

Action: No action is needed. The conversion will default to using String
Level: 1

Type: WARNING

Impact: Other

WCS-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-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-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-26466: Failed to unmarshal byte stream into Cluster

Cause: Unmarshalling failed because a JAXBContext instance could not be obtained.

Action: Make sure that the required files can be found in the specified package and that the required classes can be loaded from the classpath.
Level: 1

Type: WARNING

Impact: Other

WCS-26467: SES search query execution timed out - "{0}" with message "{1}".

Cause: The search query does not complete within the time limit.

Action: Re-try the search query again later.
Level: 1

Type: WARNING

Impact: Other

WCS-26467: SES search query execution timed out - "{0}" with message "{1}".

Cause: The search query does not complete within the time limit.

Action: Re-try the search query again later.
Level: 1

Type: WARNING

Impact: Other

WCS-26481: SearchCrawlExtension class is not found for service {0}

Cause: Portal crawler failed to introspect a Crawlable SPI implementation for the involved service, specified by a URL parameter indicating a crawler's intent to crawl said service. This theoretically should never happen because the URL that crawlers would use are all generated by the Search framework code when crawlers access the root feed that we provide. But if a crawler explicitly starts with a particular service, bypassing our root feed, this warning may result.

Action: Please check the potential crawling SES instances to make sure that there isn't a source that directly targets a service which has no Crawlable implementation.
Level: 1

Type: WARNING

Impact: Other

WCS-26481: SearchCrawlExtension class is not found for service {0}

Cause: Portal crawler failed to introspect a Crawlable SPI implementation for the involved service, specified by a URL parameter indicating a crawler's intent to crawl said service. This theoretically should never happen because the URL that crawlers would use are all generated by the Search framework code when crawlers access the root feed that we provide. But if a crawler explicitly starts with a particular service, bypassing our root feed, this warning may result.

Action: Please check the potential crawling SES instances to make sure that there isn't a source that directly targets a service which has no Crawlable implementation.
Level: 1

Type: WARNING

Impact: Other

WCS-26491: The processing and preparing of the control feed for service {0} failed

Cause: The processing and preparing of the control feed for service {0} failed. This could mean that there is a fundamental error in the writing the feed content to the output stream which is to be returned to the caller of the URL.

Action: Most likely there is a network issue which may well be temporary. Restart the crawl again and see if the problem persists.
Level: 1

Type: ERROR

Impact: Other

WCS-26491: The processing and preparing of the control feed for service {0} failed

Cause: The processing and preparing of the control feed for service {0} failed. This could mean that there is a fundamental error in the writing the feed content to the output stream which is to be returned to the caller of the URL.

Action: Most likely there is a network issue which may well be temporary. Restart the crawl again and see if the problem persists.
Level: 1

Type: ERROR

Impact: Other

WCS-26492: The processing and preparing of the data feed for service {0} failed

Cause: The processing and preparing of the data feed for service {0} failed. This could mean that there is a fundamental error in the writing the feed content to the output stream which is to be returned to the caller of the URL.

Action: Most likely there is a network issue which may well be temporary. Restart the crawl again and see if the problem persists.
Level: 1

Type: ERROR

Impact: Other

WCS-26492: The processing and preparing of the data feed for service {0} failed

Cause: The processing and preparing of the data feed for service {0} failed. This could mean that there is a fundamental error in the writing the feed content to the output stream which is to be returned to the caller of the URL.

Action: Most likely there is a network issue which may well be temporary. Restart the crawl again and see if the problem persists.
Level: 1

Type: ERROR

Impact: Other

WCS-26501: Creation of the Tags service failed.

Cause: The Tags service is loaded by reflection. Something may have happened to cause that to fail.

Action: Check whether the class name logged is accessible through the class path of the WebCenter Web application.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-26539: findUpdatedResources failed because of invalid arguments passed in to the method: serviceId ({0}), date ({1})).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26540: getTags failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1})).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26540: getTags failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1})).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26541: Error encountered while publishing to activity stream due to {0}.

Cause: Error caused by Activity Stream

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26541: Error encountered while publishing to activity stream due to {0}.

Cause: Error caused by Activity Stream

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26542: Error encountered while retrieving user profile due to {0}.

Cause: Error caused by Profile server

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26542: Error encountered while retrieving user profile due to {0}.

Cause: Error caused by Profile server

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26543: Error encountered while renaming personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26543: Error encountered while renaming personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26544: Error encountered while deleting personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26544: Error encountered while deleting personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26545: Error encountered while finding personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26545: Error encountered while finding personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26546: Error encountered while finding personal resources.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26546: Error encountered while finding personal resources.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26547: saveBookmark callback failed for service {0}.

Cause: The specified service encountered an internal error.

Action: Make sure that the service is configured correctly and that arguments passed in are all valid.
Level: 1

Type: WARNING

Impact: Other

WCS-26547: saveBookmark callback failed for service {0}.

Cause: The specified service encountered an internal error.

Action: Make sure that the service is configured correctly and that arguments passed in are all valid.
Level: 1

Type: WARNING

Impact: Other

WCS-26548: service-definition.xml requires a resource-type element and one or more object-type elements.

Cause: The service-definition.xml does not have the appropriate components.

Action: Add a resource-type and an object type to the service-definition.xml
Level: 1

Type: WARNING

Impact: Other

WCS-26548: service-definition.xml requires a resource-type element and one or more object-type elements.

Cause: The service-definition.xml does not have the appropriate components.

Action: Add a resource-type and an object type to the service-definition.xml
Level: 1

Type: WARNING

Impact: Other

WCS-26601: No service ID or resource ID - cannot perform {0}.

Cause: The consumption of the EditBookmarkBean from the view layer did not pass in the service or the resource IDs necessary.

Action: Check the view layer to make sure that the resourceId and the serviceId parameters are passed into the page flow scope.
Level: 1

Type: ERROR

Impact: Other

WCS-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-26602: Cannot create a recommended list because the Tags service cannot be created.

Cause: The creation of the Tags service was unsuccessful, so the recommended list could not be created.

Action: Check for /META-INF/tagging-class-config.properties and verify that a correct accessible class is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-26603: Bookmark cannot be loaded because Tags service cannot be created.

Cause: The creation of the Tags service was unsuccessful, so the bookmark object could not be created.

Action: Check for /META-INF/tagging-class-config.properties and verify that a correct accessible class is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-26603: Bookmark cannot be loaded because Tags service cannot be created.

Cause: The creation of the Tags service was unsuccessful, so the bookmark object could not be created.

Action: Check for /META-INF/tagging-class-config.properties and verify that a correct accessible class is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-26604: Bookmark saving failed because a Tags service cannot be created.

Cause: The creation of the Tags service was unsuccessful, so the bookmark could not be saved.

Action: Check for /META-INF/tagging-class-config.properties and verify that a correct accessible class is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-26612: The tagging component "{0}" was not rendered because the underlying Tags service was not available.

Cause: The underlying Tags service was not available.

Action: Look for the errors causing the underlying Tags service to not be available and fix them.
Level: 1

Type: WARNING

Impact: Other

WCS-26613: Error encountered while renaming personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26613: Error encountered while renaming personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26614: Error encountered while deleting personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26614: Error encountered while deleting personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26615: Error encountered while finding personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26615: Error encountered while finding personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26616: Error encountered while finding personal resources.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26616: Error encountered while finding personal resources.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26617: Error encountered while updating resource with serviceId: {0} resourceId:{1} and resourceName:{2}.

Cause: There was a problem saving the updated resource.

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26617: Error encountered while updating resource with serviceId: {0} resourceId:{1} and resourceName:{2}.

Cause: There was a problem saving the updated resource.

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26618: This item has been deleted by another user while being tagged. Refresh this page.

Cause: Resource was deleted while being tagged.

Action: Retry the action.
Level: 1

Type: WARNING

Impact: Other

WCS-26618: This item has been deleted by another user while being tagged. Refresh this page.

Cause: Resource was deleted while being tagged.

Action: Retry the action.
Level: 1

Type: WARNING

Impact: Other

WCS-26621: EncodeBegin error for TaggingPopup tag

Cause: Catastrophic error

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-26623: Component {0} does not support client listeners.

Cause: Tried to add a client listener to a component that does not support client listeners.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-30001: Error while creating the wiki.

Cause: Error while creating the wiki.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30003: Error while getting the wiki parent.

Cause: Error while getting the wiki parent

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30004: Error while getting wiki.

Cause: Error while getting wiki

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30005: Error while moving to wiki page.

Cause: Error while moving to wiki page

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30006: Error while getting child wikis size.

Cause: Error while getting child wikis size

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30007: Error while deleting wiki.

Cause: Error while deleting wiki

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30008: Error while initializing ContainerWikiBean.

Cause: Error while initializing ContainerWikiBean

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30009: Error while getting wiki list.

Cause: Error while getting wiki list

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30010: Error while getting child wiki list.

Cause: Error while getting wiki list

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30011: Error while moving to wiki page.

Cause: Error while moving to wiki page

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30012: Error while getting wikiContainer.

Cause: Error while getting wikiContainer

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30014: Error while setting containerId.

Cause: Error while setting containerId

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30015: Error while getting crumbsList.

Cause: Error while getting crumbsList

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30016: Error while getting different versions for wiki.

Cause: Error while getting different versions for wiki.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30017: Error while creating container.

Cause: Error while creating container.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30018: Error while deleting container.

Cause: Error while deleting container.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30019: Error while editing container.

Cause: Error while editing container.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30020: Error while getting the wiki hierarchy.

Cause: Error while getting the wiki hierarchy.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30021: {0} not accessible.

Cause: Contact your administrator for access.

Action: Check if data exist or check for appropriate permissions.
Level: 1

Type: WARNING

Impact: Other

WCS-30022: Error while getting the root wiki.

Cause: Error while getting the root wiki.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30023: Error while getting the tree model.

Cause: Error while getting the tree model.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-32003: Unable to load WebCenter Worklist configuration

Cause: Connections context could not be acquired.

Action: Ensure that the connections.xml file is available and valid.
Level: 1

Type: WARNING

Impact: Other

WCS-32004: Worklist Connection ''{0}'' is an invalid WebCenter Worklist connection.

Cause: The BPEL Worklist connection is invalid.

Action: Verify the specified Worklist connection is to a valid, accessible BPEL Workflow instance.
Level: 1

Type: ERROR

Impact: Other

WCS-32005: The adf-config.xml element associated with the BPEL connection to be used by the To-Dos and Group Tasks service was not present.

Cause: The application's adf-config.xml file was missing the adf-task-config element containing a BPELConnection name.

Action: Add the adf-config.xml entry associated with the To-Dos and Group Tasks service's BPEL connection using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32006: The adf-config.xml element associated with the BPEL connection to be used by the Worklist service was not present.

Cause: The application's adf-config.xml file was missing the adf-worklist-config element containing one or more BPELConnection names.

Action: Add the adf-config.xml entry associated with the Worklist service BPEL connection using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32007: The BPEL Connection named ''{0}'' was not present in the connections.xml file. This will prevent the To-Dos and Group Tasks service from being able to function as a BPEL connection is required.

Cause: The BPEL Connection matching the name specified in the adf-config.xml segment for the To-Dos and Group Tasks service requires adding to connections.xml.

Action: Add the BPEL Connection entry associated with the To-Dos and Group Tasks service adf-config.xml entry to connections.xml using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32008: The BPEL Connection named ''{0}'' was not present in the connections.xml file. This will prevent the Worklist service from being able to interact with the required this BPEL connection.

Cause: The BPEL Connection matching the name specified in the adf-config.xml segment for the Worklist service requires adding to connections.xml.

Action: Add the BPEL Connection entry associated with the Worklist service adf-config.xml entry to connections.xml using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32009: The Worklist service does not have a ConnectionName configuration entry in adf-config.xml that maps to a BPELConnection in connections.xml, therefore the Worklist service was not configured for this application.

Cause: There was no Worklist service ConnectionName entry in adf-config.xml that maps to a corresponding BPELConnection name in connections.xml.

Action: Make sure there is a ConnectionName configuration entry in adf-config.xml in the adf-worklist-config element that maps to a BPELConnection entry in connections.xml using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32010: The To-Dos and Group Tasks service does not have an entry in adf-config.xml that maps to a BPELConnection in connections.xml, therefore the To-Dos and Group Tasks service was not configured for this application.

Cause: There was no To-Dos and Group Tasks service ConnectionName entry in adf-config.xml that maps to a corresponding BPELConnection name in connections.xml.

Action: Make sure there is a ConnectionName configuration entry in adf-config.xml in the adf-task-config element that maps to a BPELConnection entry in connections.xml using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32011: The connection associated with connection name ''{0}'' was not of type BPELConnection. This will prevent the To-Dos and Group Tasks service from being able to use this connection.

Cause: The To-Dos and Group Tasks service ConnectionName entry in adf-config.xml was not mapped to a corresponding BPELConnection name in connections.xml.

Action: Either recreate the connection to one of connection type BPELConnection in connections.xml, or update the To-Dos and Group Tasks service's adf-task-config adf-config.xml entry to refer to a BPELConnection.
Level: 1

Type: WARNING

Impact: Other

WCS-32012: The connection associated with connection name ''{0}'' was not of type BPELConnection. This will prevent the Worklist service from being able to use this connection.

Cause: The Worklist service ConnectionName entry in adf-config.xml was not mapped to a corresponding BPELConnection name in connections.xml.

Action: Either recreate the connection to one of connection type BPELConnection in connections.xml, or update the Worklist service's adf-worklist-config adf-config.xml entry to refer to a BPELConnection.
Level: 1

Type: WARNING

Impact: Other

WCS-32013: Unable to interact with the BPEL client APIs.

Cause: The Worklist service was unable to interact with the BPEL client APIs.

Action: See the exception in the associated notification.
Level: 1

Type: ERROR

Impact: Other

WCS-32100: The WebCenter Worklist has queried the BPEL Worklist connection named ''{0}'', and encountered a WebCenter Executor error. Please see related exception for details. If the WebCenter Worklist is running in an Application Server, check to see if the wsm-pm application is up and running.

Cause: Either, there is an issue with the BPEL Worklist instance being queried or, (if the WebCenter application is running in an Application Server) the wsm-pm application required by the Worklist is down.

Action: Validate the BPEL Worklist connection details in connections.xml, and check that the wsm-pm application process is up and running (if the WebCenter application is running in an Application Server).
Level: 1

Type: ERROR

Impact: Other

WCS-32101: Cache not available.

Cause: Cache is not initialized.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-32102: Could not operate on cache object.

Cause: Examine the associated Cache related exceptions that have been logged.

Action: Contact system administrator, if unable to resolve through examination of related logged Cache exception.
Level: 1

Type: ERROR

Impact: Other

WCS-32103: Unable to query BPEL repository.

Cause: The Worklist service was unable to connect to the BPEL repository, as an exception occurred while querying the BPEL Client APIs.

Action: See the exception in the associated notification.
Level: 1

Type: ERROR

Impact: Other

WCS-33001: Exception while executing Query for Recent Activities "{0}" : "{1}".

Cause: The execution of the search query for recent activities failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-33002: Unable to find any services to query.

Cause: The Service Framework has not provided any services to query.

Action: Add services to application that can be searched for recent activity.
Level: 1

Type: ERROR

Impact: Configuration

WCS-33003: Exception while executing Search Query Thread for Recent Activities "{0}" : "{1}".

Cause: The query of a specific service for recent activity has failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-33004: Unable to retrieve user preference "{0}".

Cause: The user preferences could not be read.

Action: Check the WebCenter preference configuration and MDS settings.
Level: 1

Type: ERROR

Impact: Configuration

WCS-33005: Recency value of "{0} minutes" is too low (minimum value is 1 minute).

Cause: The number of minutes considered to be recent is too low.

Action: Increase the recency value preference to greater than or equal to 1 minute.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-33006: Search Execution API returned null.

Cause: The search API used to query for recent activity returned a null object.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

WCS-33007: Service Extension for Recent Activities was not found.

Cause: The WebCenter Service Extension for Recent Activities could not be found.

Action: Check the WebCenter configuration in adf-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

WCS-33008: View Layer API Exception: Exception {0}. Message: {1}.

Cause: Unable to render the recent activity UI.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-33009: Exception reading from Recent Activity Cache: {0} : {1}.

Cause: The data cache for recent activity for this user has failed.

Action: Clear the cache by clicking the Refresh button. If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-33010: Invalid recent activity entry returned from service {0} with title "{1}".

Cause: The service returning recent activity has responded with invalid data.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WCS-33011: Unhandled Error or Exception: {0} : {1}.

Cause: The recent activity API has caught an unhandled Exception or Error, possibly thrown in an underlying service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-33012: createExecutors timed out for all services or no services available.

Cause: All searchable services have timed out or are not available.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-33013: Results found, but failed to be processed for service : {0}.

Cause: Results from the given service are invalid and have been ignored.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-33014: Search timed out or cancelled for {0}.

Cause: The search for activity in the given service has taken too long to execute.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-33501: Unable to execute the search for recent activity. Search has not been provisioned.

Cause: The WebCenter Recent Activity Service depends on the availability of the Search service to execute the search for recent activities, but the Search service has not been provisioned for the current scope.

Action: Provision the Search service for this scope.
Level: 1

Type: ERROR

Impact: Other

WCS-33502: The value given for the groupSpace parameter is not a valid portal scope.

Cause: The task flow parameter groupSpace has been set to a scope that does not exist. If this application contains no groupSpace scopes, this parameter must be null.

Action: Edit the task flow parameter in the page definition to set the groupSpace parameter to a valid value (usually null).
Level: 1

Type: ERROR

Impact: Other

WCS-33503: Unable to obtain recent activity data.

Cause: The search may have timed out, failed, or been unable to find anything to search.

Action: Refresh the Recent Activity component using the refresh icon.
Level: 1

Type: ERROR

Impact: Other

WCS-33504: Recent Activity in the Home Portal requires a groupSpace taskflow parameter value to use for the search.

Cause: Recent Activity cannot search the Home Portal.

Action: Edit the Recent Activities taskflow properties and specify a portal taskflow parameter.
Level: 1

Type: ERROR

Impact: Other

WCS-34002: Item not found.

Cause: Item did not exist in repository.

Action: Do not reference items that do not exist.
Level: 1

Type: WARNING

Impact: Other

WCS-34003: Item not found, ancestor depth is not valid.

Cause: The depth of the ancestor was not valid.

Action: Check the depth of the node first.
Level: 1

Type: WARNING

Impact: Other

WCS-34004: This node is not in sync with the file system.

Cause: The session contains stale file system information.

Action: Invoke refresh() or save() to synchronize the session with the file system.
Level: 1

Type: WARNING

Impact: Other

WCS-34005: This node does not have a primary item.

Cause: Folders do not have primary items.

Action: Do not invoke getPrimaryItem() on a folder node.
Level: 1

Type: WARNING

Impact: Other

WCS-34007: Path not found: {0}.

Cause: The method was invoked with an invalid path.

Action: Invoke the method with a valid path.
Level: 1

Type: WARNING

Impact: Other

WCS-34008: Unsupported repository operation.

Cause: A method has been invoked that is not supported.

Action: Any code calling this method should be removed or skipped.
Level: 1

Type: WARNING

Impact: Other

WCS-34013: Invalid file system adapter repository reference.

Cause: The Reference provided to initialize the repository does not describe a file system connection or has incorrect parameters.

Action: Invoke the FSRepository constructor with a valid Reference constructed from FSRepository.getReference.
Level: 1

Type: WARNING

Impact: Other

WCS-34014: {0} is not a valid file system mount point.

Cause: The mount point is not a valid file system directory.

Action: Invoke the repository constructor with a valid root directory.
Level: 1

Type: WARNING

Impact: Other

WCS-34015: {0} is not a known workspace in this repository

Cause: Could not access the workspace, as the file system adapter does not support workspaces.

Action: Invoke login() with a null or empty workspace name.
Level: 1

Type: WARNING

Impact: Other

WCS-34016: The file system adapter does not accept login credentials

Cause: Could not login as the file system adapter does not accept login credentials.

Action: Invoke login() with null credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-34017: Impersonation is not allowed.

Cause: Could not execute the impersonate method as the file system adapter does not support impersonation.

Action: Do not invoke the impersonate() method.
Level: 1

Type: WARNING

Impact: Other

WCS-34018: Cannot complete the delete operation.

Cause: An unexpected file system error occurred during the delete operation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-34019: Cannot complete the move operation.

Cause: An unexpected file system error occurred during the move operation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-34021: Cannot access the file system.

Cause: There was an error reading a file.

Action: See the chained IOException for more details on this error.
Level: 1

Type: ERROR

Impact: Other

WCS-34022: This property is not a REFERENCE.

Cause: This property is not a REFERENCE.

Action: Do not invoke getNode() on this property.
Level: 1

Type: WARNING

Impact: Other

WCS-34023: Illegal single value access: property is multi valued.

Cause: Accessed a single value property on a multi valued property.

Action: Do not access a single value property on a multi valued property.
Level: 1

Type: WARNING

Impact: Other

WCS-34024: Illegal multi value access: property is single valued.

Cause: Accessed a multi value property on a single value property.

Action: Do not access a multi value property on a single value property.
Level: 1

Type: WARNING

Impact: Other

WCS-34025: XPath error

Cause: Error occurred while processing XPath.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-34026: Invalid XPath query

Cause: The XPath query was invalid.

Action: Correct the XPath query.
Level: 1

Type: WARNING

Impact: Other

WCS-34028: Invalid call to setProperty: the target type is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34029: Invalid call to setProperty: this property cannot be set or the value is not compatible

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34030: Cannot move a file or folder to a file.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34031: Save cannot include only the source or the destination of a move.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34032: Cannot specify an index on move destination.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34034: Cannot move a property.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34035: An item with the same name already exists at the destination.

Cause: An attempt was made to overwrite an existing item.

Action: Specify the overwrite option, or remove the item before attempting this operation.
Level: 1

Type: WARNING

Impact: Other

WCS-34036: Move prevented by constraint violation.

Cause: Could not perform the requested move operation as it violates the constraints defined in the JCR specification.

Action: Verify that the target node is a valid parent and/or this node can be renamed.
Level: 1

Type: WARNING

Impact: Other

WCS-34037: Access denied

Cause: Could not perform the specified action as it is not allowed on the path specified.

Action: Contact the system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-34038: The session has pending changes.

Cause: The operation could not proceed as there are pending changes in the session.

Action: Invoke save() or refresh() before performing the operation.
Level: 1

Type: WARNING

Impact: Other

WCS-34047: Invalid parameter

Cause: Could not parse a parameter to this call as it is invalid.

Action: Check and correct the parameters for this call.
Level: 1

Type: WARNING

Impact: Other

WCS-34306: Error while executing a search.

Cause: An unexpected error occurred while executing a search.

Action: Check the search criteria is valid and verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34307: Invalid node type : {0}

Cause: An invalid node type was specified for the search.

Action: Verify that the search query is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34308: Cannot determine the node type for the search.

Cause: An unexpected error occurred while determining the node type for the search.

Action: Check the search query is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34310: Invalid search query.

Cause: The XPath specified for the search was invalid.

Action: Ensure that the search query is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34311: An error occurred while building the search.

Cause: An error occurred while building the search query.

Action: Ensure the search query is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34320: Property cannot be created for {0} as the data type, {1}, is invalid. Path: {2}; node ID: {3}; node site ID: {4}.

Cause: The data type for the requested property was invalid.

Action: Specify a valid data type for the property, and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-34321: Primary item name for node type, {0}, cannot be returned. NodeTypeID: {1}; NodeTypeSiteID: {2}.

Cause: The node type was invalid.

Action: Check if the requested node type exists in the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34322: Property definitions of node type, {0}, cannot be determined.

Cause: An error occurred while creating the property definitions.

Action: Check if the requested node type exists in the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34323: Super types of node type, {0}, cannot be determined.

Cause: An error occurred while creating the super types.

Action: Check the node type is valid and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-34324: Primary item name for node type, {0}, cannot be determined.

Cause: The node type was not found.

Action: Check the node type is valid and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-34325: Node definitions for node type, {0}, cannot be determined.

Cause: Node definition could not be created.

Action: Check the node type is valid and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-34326: Super types of node type, {0}, cannot be determined. NodeTypeID: {1}; NodeTypeSiteID: {2}.

Cause: The node type was not found.

Action: Verify that the requested node type exists in the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34327: Invalid credentials.

Cause: Session could not be created for the user.

Action: Verify that the credentials passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34328: Database connection could not be obtained.

Cause: Could not access the database, which may be down.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34329: Insufficient privileges to perform the operation.

Cause: You did not have the sufficient privilege to perform this operation.

Action: Contact the Portal administrator to check your privileges.
Level: 1

Type: WARNING

Impact: Other

WCS-34330: The requested node type, {0}, does not exist.

Cause: Could not locate the requested node type as it does not exist.

Action: Verify that the node type exists in the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34331: Property definitions of node type, {0}, cannot be returned. NodeTypeID: {1}; NodeTypeSiteID: {2}.

Cause: An error occurred while creating the property definitions.

Action: Check the node type is valid, verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34332: Property, {0}, cannot be set for node type, {1}. NodeTypeID: {2}; NodeTypeSiteID: {3}.

Cause: Property value was invalid.

Action: Provide a property value that is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34333: Oracle data-source, {0}, cannot be looked up.

Cause: The data-source was not available.

Action: Verify that the data-source is created correctly and is available.
Level: 1

Type: ERROR

Impact: Other

WCS-34335: The root nodes of the Portal repository cannot be obtained.

Cause: An error occurred while listing the root nodes.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34336: Statement/Connection objects cannot be closed.

Cause: An error occurred while closing the statement or connection objects.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34337: The child nodes of folder, {2}, cannot be obtained. Parent folder ID: {0}; folder site ID: {1}.

Cause: A SQL exception occurred while trying to list the child nodes.

Action: Verify the folder ID, folder page group ID and path are valid, verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34338: Property, {0}, is a single-valued property.

Cause: The property was a single valued property.

Action: Verify the value for the property is a single value.
Level: 1

Type: ERROR

Impact: Other

WCS-34339: Unable to check if the session is live.

Cause: An error occurred while checking whether the session is live.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34340: The Portal session cannot be logged out.

Cause: An error occurred while logging out of the Portal session; it is possible the Portal instance is no longer available.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34341: Cannot determine UUID for node, {0}.

Cause: An error occurred while determining the UUID of context node.

Action: Verify that the path is correct and that the node is referenceable.
Level: 1

Type: ERROR

Impact: Other

WCS-34342: Cannot get the node, {0}.

Cause: An error occurred while getting the requested node.

Action: Verify that the path is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34343: Cannot get the node for the given UUID, {0}.

Cause: Error getting the requested node.

Action: Verify that the UUID is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34344: Cannot determine if item exists at given path, {0}.

Cause: An error occurred while determining if the requested item exists.

Action: Verify that the path is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34346: Property definitions of node type cannot be determined. NodeTypeID: {0}; NodeTypeSiteID: {1}.

Cause: An error occurred while creating the property definitions.

Action: Verify that the node type exists in the Portal repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34347: Property, {0}, cannot be set for node type. NodeTypeID: {1}; NodeTypeSiteID: {2}.

Cause: Property value was invalid.

Action: Provide a property value that is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34348: Cannot retrieve all the node types from the Portal repository.

Cause: An error occurred while retrieving the Portal node types.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34349: Cannot get the properties for node with ID: {0}, site ID: {1}.

Cause: An error occurred while obtaining the properties of the node from the repository.

Action: Verify that the node and node type are valid, and verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34350: Cannot get the references for the requested node. Node ID: {0}; node site ID: {1}.

Cause: An error occurred while obtaining the references for the requested node.

Action: Verify the node is valid, and verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34351: Cannot get binary property value for property, {0}, that belongs to node, {1}.

Cause: An error occurred while fetching the binary property of node.

Action: Verify that the path is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-34352: Cannot get Portal property name for property ID: {0}.

Cause: An error occurred while getting the Portal property name.

Action: Verify that the requested property is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34354: The Portal session could not be logged out.

Cause: A SQL error occurred when attempting to log out.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34355: Cannot determine the length of the given input stream.

Cause: An error occurred while determining the length of the input stream.

Action: Verify that the input stream is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34356: Current operation is not supported for the single-valued property, {0}.

Cause: The current operation could not be performed on a single property as single-valued properties are not supported by such an operation.

Action: This API cannot be invoked on a single-valued property.
Level: 1

Type: ERROR

Impact: Other

WCS-34357: This node, {0}, cannot be referenced and hence, does not have a UUID property.

Cause: The context node does not have a UUID property.

Action: Make this request on a referenceable node.
Level: 1

Type: ERROR

Impact: Other

WCS-34358: Current operation is not supported for the multi-valued property, {0}.

Cause: The current operation could not be performed on a multi-valued property as multi-valued properties are not supported by such an operation.

Action: This API cannot be invoked on a multi-valued property.
Level: 1

Type: ERROR

Impact: Other

WCS-34359: This operation is not supported by the Portal repository.

Cause: An error occurred while performing this action as the operation is not supported by the underlying Portal repository.

Action: Check the operation being attempted is a valid operation for the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34360: The Portal repository has only 1 workspace, so this request is invalid.

Cause: The underlying Portal repository has only one workspace.

Action: This is an invalid request since the repository is a single workspace repository. Retry with a valid request.
Level: 1

Type: ERROR

Impact: Other

WCS-34361: Cannot convert length of property, {0}, to long.

Cause: An error occurred while converting the length to the long data type.

Action: Verify the value of the property is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34362: Cannot parse the date value for property, {0}.

Cause: An error occurred while parsing the date value.

Action: Verify the value of the property is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34363: The requested property cannot be found. Path of context node: {0}; Relative Path: {1}.

Cause: The property was not found.

Action: Verify that the requested property is valid and that the path is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34364: The requested item, {0}, cannot found.

Cause: An error occurred while getting the requested item.

Action: Verify that the item exists in the Portal repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34365: The property, {0}, cannot be converted to a reference.

Cause: The property could not be converted to a reference or was a multi-valued property.

Action: Verify that the property can be converted to a reference.
Level: 1

Type: ERROR

Impact: Other

WCS-34366: {0} is a folder and hence, it does not have a primary item.

Cause: The request could not be performed because folders cannot have primary items.

Action: This is an invalid request.
Level: 1

Type: ERROR

Impact: Other

WCS-34367: The requested node was not found. Path of context node: {0}; Relative Path: {1}.

Cause: The node was not found.

Action: Verify that the requested node is valid and that the path is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34368: The given path, {0}, is invalid.

Cause: The specified path was invalid.

Action: Provide a valid path.
Level: 1

Type: WARNING

Impact: Other

WCS-34416: Error determining if child node, {0}, could be added.

Cause: An error occurred while determining whether the child node could be added.

Action: Verify the node is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34417: Error determining if child node, {0}, based on type, {1}, could be added.

Cause: An error occurred while determining whether a child node based on the given type could be added.

Action: Verify the node and type are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34418: Error removing the child item, {0}, for node type, {1}.

Cause: An error occurred while removing the child item.

Action: Verify item and node type are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34419: Error removing the property, {0}, for node type, {1}.

Cause: An error occurred while removing the property.

Action: Verify the node type and property are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34421: The connection cannot be closed.

Cause: The system encountered an unexpected error while trying to close a database connection.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34422: The node types array object could not be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node types object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34423: The "all node types" node type iterator could not be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node type iterator in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34424: The Portal node types linked list object could not be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the Portal node types linked list object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34425: The cache region, {0}, has already been defined.

Cause: The cache region has already been defined.

Action: No action is required as this is just indicating that the cache region has already been defined.
Level: 1

Type: WARNING

Impact: Other

WCS-34428: Generic cache exception when trying to retrieve object from cache.

Cause: A cache exception occurred when trying to retrieve the object from the cache.

Action: Contact the WebCenter administrator to check the status of the Cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34429: Object cannot be stored in cache as the cache is full.

Cause: The object could not be stored in cache because the cache was full.

Action: Contact the WebCenter administrator to check the status of the Cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34430: The root node does not have a parent node.

Cause: The parent node was requested for a root node.

Action: Request the parent node of any node except the parent node.
Level: 1

Type: ERROR

Impact: Other

WCS-34431: The node type iterator object cannot be removed from the cache.

Cause: The node type iterator object could not be removed from the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34432: The node type name cannot be returned from the qualified name.

Cause: The namespace could not be resolved.

Action: Verify the specified node type name is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34433: The property name cannot be returned from the qualified name.

Cause: The namespace could not be resolved.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-34434: The property definition name cannot be returned from the qualified name.

Cause: The namespace could not be resolved.

Action: Verify the property type is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34435: The item at the requested depth, {0}, cannot be found.

Cause: An error occurred while getting the requested item.

Action: Verify that the depth is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34436: The root node does not have a parent.

Cause: Could not request the parent node as root nodes do not have parent nodes.

Action: Verify that the context node is not the root node.
Level: 1

Type: ERROR

Impact: Other

WCS-34437: The Portal session cannot be restored.

Cause: A SQL error occurred when attempting to restore the session for the user.

Action: Verify that the user has been authenticated.
Level: 1

Type: ERROR

Impact: Other

WCS-34438: The declared property definition array object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the declared property definition array object in cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34440: The property definition array object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the property definition array object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34441: The property iterator object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the property iterator object in the cache.

Action: Contact the WebCenter administrator to check the status of the Cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34442: The property object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the property object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34443: The node iterator object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node iterator object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34444: The node object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34446: The node type object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node type object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34447: The "primary node types" node type iterator cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node type iterator in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34448: The "mixin node types" node type iterator cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node type iterator in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34449: The "super types" node type array cannot be stored in cache.

Cause: The system encountered an unexpected exception when trying to store the node type array in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34450: The child node definitions of the node type cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the child node definitions of the node type in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34451: The property definitions of the node type cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the property definitions of the node type in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34452: The boolean object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the boolean object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34453: The requested child node definition of the node type cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the child node definition of the node type in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34454: The requested property definition of the node type cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the property definition of the node type in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34456: The repository property objects cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the repository property objects in cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34457: The repository property definition objects cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the repository property definition objects in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34458: One of the cache regions could not be destroyed.

Cause: The system encountered an unexpected exception when trying to destroy one of the cache regions.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34459: The cache could not be initialized.

Cause: The system encountered an unexpected exception when trying to initialize the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34460: The cache configuration file could not be read.

Cause: The system encountered an IO exception when trying to read the cache configuration file.

Action: Verify that the configuration file exists.
Level: 1

Type: ERROR

Impact: Other

WCS-34461: The repository node type objects could not be stored in cache.

Cause: The system encountered an unexpected exception when trying to store the repository node type objects in cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34462: Cannot get the super types for node type: {0}.

Cause: An error occurred while fetching the super types of the given node type.

Action: Verify that the requested node type exists in the Portal repository and is a custom type.
Level: 1

Type: ERROR

Impact: Other

WCS-34463: The cache region, {0}, cannot be found.

Cause: Could not find the requested region, as it has not been defined in Java Object Cache (JOC).

Action: Verify that the region name is valid and is expected to exist in this hierarchy.
Level: 1

Type: ERROR

Impact: Other

WCS-34464: Oracle Text search is unable to run.

Cause: An error occurred with Oracle Text while running a search.

Action: Check with the Administrator of the Portal you are trying to search that Oracle Text is valid. Additional information as to the cause of the error may be in the portal diagnostics log.
Level: 1

Type: ERROR

Impact: Other

WCS-34465: A root search can not be performed as the base languages of the page groups are different.

Cause: The search could not be performed because the base language of the page groups to be searched are not the same.

Action: Only perform searches which search a single page group.
Level: 1

Type: ERROR

Impact: Other

WCS-34466: Cannot look up the database connection with the name {0} from connections.xml.

Cause: An error occurred while attempting to look up the database connection; the named database connection may not exist in connections.xml.

Action: Make sure the database connection is created in connections.xml.
Level: 1

Type: ERROR

Impact: Other

WCS-35006: cannot load metadata from XML node

Cause: The content of the data-control file (.dcx) might be invalid.

Action: Verify that the content in the data-control file (.dcx) is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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 runtime data-control object returned null.

Cause: The ADF framework did not set the data-control definition within the runtime data control.

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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-35514: This feature is only available in a design environment.

Cause: A call to a design time only feature was made from run time.

Action: Do not call this method from run time code.
Level: 1

Type: ERROR

Impact: Other

WCS-35515: Error getting information for connection {0}. The connection will be skipped in the resource catalog.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35515: Error getting information for connection {0}. The connection will be skipped in the resource catalog.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35516: This factory cannot be used at design time.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35516: This factory cannot be used at design time.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35517: Not a valid content URL: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35517: Not a valid content URL: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35518: Error getting information for node ID {0}. This node will be skipped in the resource catalog.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35518: Error getting information for node ID {0}. This node will be skipped in the resource catalog.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35900: Illegal value state, cannot read a value previously streamed.

Cause: The application mixed calls to getStream() and other get* accessors on the same value object.

Action: Verify your application code.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-36314: Unable to create a page for now because another page is being created.

Cause: Another page is being created and all page metadata is locked.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

WCS-36315: The page style is no longer available.

Cause: The page style is deleted or hidden.

Action: Choose another page style.
Level: 1

Type: ERROR

Impact: Other

WCS-36315: The page style is no longer available.

Cause: The page style is deleted or hidden.

Action: Choose another page style.
Level: 1

Type: ERROR

Impact: Other

WCS-36316: Cannot perform the requested operation.

Cause: You do not have sufficient privileges to perform the requested operations.

Action: Ask your administrator to grant you the appropriate privileges and then try again.
Level: 1

Type: ERROR

Impact: Other

WCS-36316: Cannot perform the requested operation.

Cause: You do not have sufficient privileges to perform the requested operations.

Action: Ask your administrator to grant you the appropriate privileges and then try again.
Level: 1

Type: ERROR

Impact: Other

WCS-36701: Failed to redirect because the page is not specified.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-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-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-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-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-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-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-36707: Failed to save the changes because another page operation was in progress.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36708: Failed to instantiate DocSecurityBean.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36708: Failed to instantiate DocSecurityBean.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36709: Failed to instantiate PageSecurityManager.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36709: Failed to instantiate PageSecurityManager.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36801: Failed to change page permission to "{0}".

Cause: An unexpected error occurred when changing page permission.

Action: Check error stack for details.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-36804: Failed to change page security to default mode.

Cause: An unexpected error occurred when changing page security mode.

Action: Check error stack for details.
Level: 1

Type: ERROR

Impact: Other

WCS-36805: A page named {0} already exists.

Cause: A page with the specified name exists.

Action: Specify a unique name for the page.
Level: 1

Type: ERROR

Impact: Other

WCS-36805: A page named {0} already exists.

Cause: A page with the specified name exists.

Action: Specify a unique name for the page.
Level: 1

Type: ERROR

Impact: Other

WCS-37001: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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: Check the configuration of the service that is being accessed and fix up the external application reference.
Level: 1

Type: WARNING

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: Ensure you haven't run the credential provisioning page in a standalone mode. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: 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: 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-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: WARNING

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: WARNING

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: 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: 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: resourceInfoPopup jsp inclusion missing from the page.

Cause: The jspx or jsff page containing the rah:resourceActionBehavior tag does not include the inline popup fragment: /oracle/webcenter/framework/service/view/jsf/fragments/resourceInfoPopup.jsff that is required to show resource mini-views.

Action: If this is a custom usage of rah:resourceActionBehavior, add a jsp:include to the page and a reference to the resourceMiniViewPopup page in the page definition. If this is not a custom usage of rah:resourceActionBehavior, contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-43023: Could not find component : {0}.

Cause: The specified component is missing from the current page.

Action: If this is a customized jsff or jspx page, verify that the component is included at the correct location.
Level: 1

Type: WARNING

Impact: Other

WCS-43024: The ADF Faces application to be used for WebCenter RAH requests has already been specified as {0} in another web.xml.

Cause: Multiple web.xml files in the application ear have been marked as being the web application to use for RAH requests.

Action: Examine the web.xml files from each war file and remove from all but the web application to be used for handling RAH requests.
Level: 1

Type: WARNING

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 the message key {0} in the resource bundle "{1}" (from original bundle: {2} ).

Cause: The string identified by the given key is not found in the resource bundle.

Action: If this is a custom resource bundle, add a message with the given key to the resource bundle, otherwise contact Oracle Support Services.
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 occurred reading the Connections Context.

Cause: This indicates an error with reading the Connection Context.

Action: Refer to exception detail. If insufficient details to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-43050: An error occurred reading a service's configuration.

Cause: This indicates an error with reading a service's configuration.

Action: Refer to exception detail. If insufficient 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 occurred 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 occurred 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 destroy userprofile region in Java Object Cache.

Cause: An exception occurred while removing userprofile region from Java object cache.

Action: Review the exception thrown for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-43054: An error occurred while trying to lookup connection {0}.

Cause: The name may not have been pointing to a valid connection, or some other error occurred when trying to retrieve the connection object.

Action: Ensure that the connection defined in connections.xml is valid and that the necessary classes can be loaded.
Level: 1

Type: WARNING

Impact: Other

WCS-43055: 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-43056: Database type {0} is not recognized.

Cause: WebCenter has been configured with a database platform that is not recognized.

Action: Ensure that the database platform type is set correctly.
Level: 1

Type: WARNING

Impact: Other

WCS-43057: Error closing entity manager factory

Cause: An unexpected exception occurred while closing the entity manager factory.

Action: Review the exception thrown for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-43058: Could not load LifecycleListener class for "{0}" from the service definition.

Cause: An unexpected exception occurred while attempting to access the LifecycleListener.

Action: Review the exception thrown for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-43059: The WebCenterConfig will be reinitialized. Expected class "{0}", class loader "{1}", parent class loader "{2}". Actual class "{3}", class loader "{4}", parent classLoader "{5}".

Cause: This indicates an recoverable error with retrieving the WebCenterConfig.

Action: No action required.
Level: 1

Type: WARNING

Impact: Other

WCS-43060: The connection named "{0}" cannot be found.

Cause: The connection name may be incorrect.

Action: Ensure that the name matches a connection defined for the application.
Level: 1

Type: WARNING

Impact: Other

WCS-43061: Unable to find the WebCenter data source

Cause: The data source may not have been configured or cannot be read.

Action: Check the configuration of the WebCenter data source.
Level: 1

Type: ERROR

Impact: Other

WCS-43062: Unable to parse link

Cause: The link URL or network connection is wrong.

Action: Check the network connection, proxy setting and the link URL.
Level: 1

Type: WARNING

Impact: Other

WCS-43063: Error retrieving enterprise ID/prefix from ADF Context.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-43064: The version ({0}) of WebCenter Framework Design Time used to create the Portal application is not the same as the version ({1}) of WebCenter Framework Runtime.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-43065: The build label ({0}) of WebCenter Framework Design Time used to create the Portal application is not the same as the build label ({1}) of WebCenter Framework Runtime.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-43067: Error "{1}" getting service with ID "{0}".

Cause: An unexpected error occurred getting a service by ID.

Action: Check the configuration of the WebCenter data source.
Level: 1

Type: ERROR

Impact: Other

WCS-43068: Error "{0}" reading service category configuration.

Cause: An unexpected error occurred reading the service category configuration.

Action: Review the exception thrown for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-43069: WebCenterUserNotFoundWarning: Unable to find user {0}.

Cause: User with the given name, unique identifier or distinguished name does not exist in the identity store.

Action: Ensure the user name, unique identifier or distinguished name is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-43070: Unable to find enterprise role {0}.

Cause: Role with the given name does not exist in the identity store.

Action: Ensure the role name is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-43071: Could not obtain display name for user {0} in locale {1}, will resort to default display name

Cause: There was an error trying to fetch locale specific display name from identity store.

Action: Turn on logging and check the logs for the cause of the exception
Level: 1

Type: WARNING

Impact: Other

WCS-43072: cannot access Coherence Cache

Cause: An exception occurred while accessing Coherence cache.

Action: Review the exception thrown for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-43073: cannot destroy userprofile region in Coherence Cache.

Cause: An exception occurred while removing userprofile region from Coherence cache.

Action: Review the exception thrown for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-43075: Unexpected error occurred while encoding the URL {0} due to {1}.

Cause: Unexpected error occurred while encoding the URL.

Action: Review the exception thrown for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-43076: Unexpected error occurred while decoding the URL {0} due to {1}.

Cause: Unexpected error occurred while decoding the URL.

Action: Review the exception thrown for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-43077: Unexpected error occurred while renaming the document {0} to {1} due to {2}.

Cause: Unexpected error occurred while renaming the document.

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-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-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-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 occurred while retrieving information from the Application Policy Store.

Cause: Review the underlying exception in the logs to determine the cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44004: An internal JPS error has occurred while retrieving role-mapping information from the Application Policy Store.

Cause: Review the underlying exception in the logs to determine the cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44005: cannot find security extension in Service Registry for service ID: {0}

Cause: No security extension was registered for the given service. Perhaps the service library was not available in the classpath.

Action: Check the service library is available in the classpath. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44005: cannot find security extension in Service Registry for service ID: {0}

Cause: No security extension was registered for the given service. Perhaps the service library was not available in the classpath.

Action: Check the service library is available in the classpath. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44006: There is no mapped service role for the WebCenter Portal role {1} to which the user {0} is assigned.

Cause: A user was assigned to a WebCenter Portal role that was not yet mapped to any service role.

Action: Ensure that the WebCenter Portal role is mapped to a service role.
Level: 1

Type: WARNING

Impact: Security

WCS-44006: There is no mapped service role for the WebCenter Portal role {1} to which the user {0} is assigned.

Cause: A user was assigned to a WebCenter Portal role that was not yet mapped to any service role.

Action: Ensure that the WebCenter Portal role is mapped to a service role.
Level: 1

Type: WARNING

Impact: Security

WCS-44007: An internal JPS error occurred while initializing the Application Policy Store.

Cause: The Application Policy Store (jps-config.xml) was probably not configured correctly.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44007: An internal JPS error occurred while initializing the Application Policy Store.

Cause: The Application Policy Store (jps-config.xml) was probably not configured correctly.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44009: Error obtaining JPS Service instance: {0}.

Cause: The value returned for the JPS Service instance was null. This may be caused by configuration error in jps-config.xml.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44009: Error obtaining JPS Service instance: {0}.

Cause: The value returned for the JPS Service instance was null. This may be caused by configuration error in jps-config.xml.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44010: A JPS error occurred while deleting users from the service ID/service role: {0} / {1}.

Cause: The error was caused while accessing the application policy store for deleting users. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44010: A JPS error occurred while deleting users from the service ID/service role: {0} / {1}.

Cause: The error was caused while accessing the application policy store for deleting users. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44011: Error getting handle to application policy for application {0}.

Cause: Either the application policy is not available or policy store is not configured correctly. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44011: Error getting handle to application policy for application {0}.

Cause: Either the application policy is not available or policy store is not configured correctly. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44012: Error getting handle to default policy store.

Cause: Either the policy store is not accessible or not configured correctly. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44012: Error getting handle to default policy store.

Cause: Either the policy store is not accessible or not configured correctly. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44101: Invalid PeoplePicker Scope {0} passed.

Cause: The scope is not of the valid type. It can be GLOBAL or SUB_SCOPED

Action: Pass a valid scope
Level: 1

Type: WARNING

Impact: Configuration

WCS-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-44102: Invalid PeoplePicker Scope ID {0} passed.

Cause: An invalid Scope ID has been passed.

Action: Ensure a valid scope/community ID is passed.
Level: 1

Type: WARNING

Impact: Configuration

WCS-44103: Unknown error encountered while selecting user(s) in people picker.

Cause: Review the root cause of the exception for more details.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44103: Unknown error encountered while selecting user(s) in people picker.

Cause: Review the root cause of the exception for more details.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44104: Scope Id is a required parameter for scoped people search.

Cause: Scope Id not provided.

Action: Provide Scope Id.
Level: 1

Type: WARNING

Impact: Security

WCS-44104: Scope Id is a required parameter for scoped people search.

Cause: Scope Id not provided.

Action: Provide Scope Id.
Level: 1

Type: WARNING

Impact: Security

WCS-44105: And unknown error occurred while trying to validate if user {0} exists

Cause: Review the root cause of the exception for more details.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44105: And unknown error occurred while trying to validate if user {0} exists

Cause: Review the root cause of the exception for more details.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44106: Unknown error encountered while selecting group(s) in group picker.

Cause: Review the root cause of the exception for more details.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44106: Unknown error encountered while selecting group(s) in group picker.

Cause: Review the root cause of the exception for more details.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44107: And unknown error occurred while trying to validate if group {0} exists

Cause: Review the root cause of the exception for more details.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44107: And unknown error occurred while trying to validate if group {0} exists

Cause: Review the root cause of the exception for more details.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44108: The search exceeded the time limit. Check the identity store connection details or refine your search criterion.

Cause: The underlying identity store and policy store could be down.

Action: Check that underlying repositories are accessible. Check logs and contact Oracle Support
Level: 1

Type: WARNING

Impact: Security

WCS-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-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-44110: An unexpected error occurred while searching for users/roles. Check logs for further details.

Cause: An unexpected error occurred while searching for identities. Consult the underlying cause.

Action: If the underlying cause does not provide any action, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Security

WCS-44151: An error occurred while retrieving the Identity Store.

Cause: This is caused when the Identity Store configured in jps-config.xml is not accessible or is not running. Review the underlying exception in the logs to determine the exact cause.

Action: Ensure that the Identity Store is configured correctly in jps-config.xml and is running. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44151: An error occurred while retrieving the Identity Store.

Cause: This is caused when the Identity Store configured in jps-config.xml is not accessible or is not running. Review the underlying exception in the logs to determine the exact cause.

Action: Ensure that the Identity Store is configured correctly in jps-config.xml and is running. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44152: An error occurred while sending an e-mail.

Cause: The error occurred because the e-mail account or the e-mail service was not configured correctly or the e-mail server was not running.

Action: Ensure that your e-mail account and the e-mail service are configured properly and the e-mail server is running.
Level: 1

Type: ERROR

Impact: Security

WCS-44152: An error occurred while sending an e-mail.

Cause: The error occurred because the e-mail account or the e-mail service was not configured correctly or the e-mail server was not running.

Action: Ensure that your e-mail account and the e-mail service are configured properly and the e-mail server is running.
Level: 1

Type: ERROR

Impact: Security

WCS-44153: An error occurred while generating the HMAC token.

Cause: The JVM did not support MessageDigest algorithms, such as MD5 or SHA, or the UTF8 encoding.

Action: Ensure the JVM supports UTF8 encoding and MD5/SHA message digest algorithms. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44153: An error occurred while generating the HMAC token.

Cause: The JVM did not support MessageDigest algorithms, such as MD5 or SHA, or the UTF8 encoding.

Action: Ensure the JVM supports UTF8 encoding and MD5/SHA message digest algorithms. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44154: An error occurred while getting the scope roles for scope ID {0}.

Cause: Either the policy store was configured incorrectly or was inaccessible or the scope ID passed was invalid.

Action: Ensure that the policy store is configured correctly and is running. Also, ensure that the scope ID passed is valid.
Level: 1

Type: ERROR

Impact: Security

WCS-44154: An error occurred while getting the scope roles for scope ID {0}.

Cause: Either the policy store was configured incorrectly or was inaccessible or the scope ID passed was invalid.

Action: Ensure that the policy store is configured correctly and is running. Also, ensure that the scope ID passed is valid.
Level: 1

Type: ERROR

Impact: Security

WCS-44155: The permission class is null for the service ID: {0}.

Cause: The permission class was not defined in the service-definition.xml file.

Action: Ensure that the permission class is defined in the service-definition.xml file for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-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-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-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-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-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-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-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-44162: Security Extension is not defined for the service ID: {0}.

Cause: The Security Extension (security-definition node) was not defined in the service-definition.xml file of the service.

Action: Ensure that the Security Extension (security-definition node) is properly defined in the service-definition.xml file.
Level: 1

Type: ERROR

Impact: Security

WCS-44163: An error occurred while retrieving service extension definition(service-definition.xml).

Cause: The service jars are not correctly packaged or the jars are corrupt.

Action: Ensure that webcenter framework shared library is correctly defined and the library jars are not corrupt.
Level: 1

Type: ERROR

Impact: Security

WCS-44163: An error occurred while retrieving service extension definition(service-definition.xml).

Cause: The service jars are not correctly packaged or the jars are corrupt.

Action: Ensure that webcenter framework shared library is correctly defined and the library jars are not corrupt.
Level: 1

Type: ERROR

Impact: Security

WCS-44164: An error occurred while retrieving the spi file .

Cause: The are multiple spi files.

Action: Ensure that only spi file with the name oracle.webcenter.security.selfregistration.custom.SelfRegActionHandlerSpi.properties exists.
Level: 1

Type: ERROR

Impact: Security

WCS-44164: An error occurred while retrieving the spi file .

Cause: The are multiple spi files.

Action: Ensure that only spi file with the name oracle.webcenter.security.selfregistration.custom.SelfRegActionHandlerSpi.properties exists.
Level: 1

Type: ERROR

Impact: Security

WCS-44165: The principal is not of type JpsRole

Cause: The principal object passed to the api is not of type JpsRole.

Action: Ensure that the parameter passed to the api is of type JpsRole.
Level: 1

Type: WARNING

Impact: Security

WCS-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-44166: Application Policy for {0} does not exist. Creating a new application policy.

Cause: The application did not package any policies.

Action: None as a new policy has been created. However ensure that application did not indeed package any policies and this was not a case of policies not being migrated. Contact Oracle Support in that case.
Level: 1

Type: WARNING

Impact: Security

WCS-44167: Public registration is not enabled for this site.

Cause: The public registration option is not enabled.

Action: Ensure that public registration is enabled in the general tab of Webcenter administration.
Level: 1

Type: WARNING

Impact: Security

WCS-44167: Public registration is not enabled for this site.

Cause: The public registration option is not enabled.

Action: Ensure that public registration is enabled in the general tab of Webcenter administration.
Level: 1

Type: WARNING

Impact: Security

WCS-44168: The principal argument is null

Cause: The principal object passed to the api is null.

Action: Ensure that the parameter passed to the api is not null.
Level: 1

Type: WARNING

Impact: Security

WCS-44168: The principal argument is null

Cause: The principal object passed to the api is null.

Action: Ensure that the parameter passed to the api is not null.
Level: 1

Type: WARNING

Impact: Security

WCS-44169: Error while determining security attributes for user {0}

Cause: The user {0} passed to determine security attributes does not exist in the underlying identity store.

Action: Ensure the user name is valid.
Level: 1

Type: WARNING

Impact: Security

WCS-44169: Error while determining security attributes for user {0}

Cause: The user {0} passed to determine security attributes does not exist in the underlying identity store.

Action: Ensure the user name is valid.
Level: 1

Type: WARNING

Impact: Security

WCS-44170: Error occurred while retrieving the security attributes of user {0}

Cause: An error occurred while querying the identity store or the policy store to determine the user's security attributes. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44170: Error occurred while retrieving the security attributes of user {0}

Cause: An error occurred while querying the identity store or the policy store to determine the user's security attributes. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44171: Error occurred while determining security attributes for service {0}

Cause: An error occurred while querying the policy store to determine the principals that were granted view access for the given service. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44171: Error occurred while determining security attributes for service {0}

Cause: An error occurred while querying the policy store to determine the principals that were granted view access for the given service. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44172: Error occurred while determining security attributes for service {0} in scope {1}

Cause: An error occurred while querying the policy store to determine the principals that were granted view access for the given service and scope. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44172: Error occurred while determining security attributes for service {0} in scope {1}

Cause: An error occurred while querying the policy store to determine the principals that were granted view access for the given service and scope. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44173: Error occurred while determining security attributes for artifact {0} belonging to service {1}

Cause: An error occurred while querying the policy store to determine the principals that were granted view access for the given service and artifact. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44173: Error occurred while determining security attributes for artifact {0} belonging to service {1}

Cause: An error occurred while querying the policy store to determine the principals that were granted view access for the given service and artifact. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44174: Error encountered while getting the HMAC initial key from the credential store

Cause: There is a problem while accessing the credential store. Review the underlying exception in the logs to determine the exact cause.

Action: Ensure the credential store is setup properly. Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44174: Error encountered while getting the HMAC initial key from the credential store

Cause: There is a problem while accessing the credential store. Review the underlying exception in the logs to determine the exact cause.

Action: Ensure the credential store is setup properly. Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44175: Error occurred while obtaining mapped service {0} roles for WebCenter Portal role {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44175: Error occurred while obtaining mapped service {0} roles for WebCenter Portal role {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44176: Error occurred while obtaining mapped application roles for service {0} and service role with ID {1} in scope {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44176: Error occurred while obtaining mapped application roles for service {0} and service role with ID {1} in scope {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44177: Error occurred while adding role mapping entry for service {0} and service role {1} to webcenter role {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services. This error can be ignored if upgrade is being re-run.
Level: 1

Type: ERROR

Impact: Security

WCS-44177: Error occurred while adding role mapping entry for service {0} and service role {1} to webcenter role {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services. This error can be ignored if upgrade is being re-run.
Level: 1

Type: ERROR

Impact: Security

WCS-44178: Error occurred while removing role mapping entry for service {0} and service role {1} from WebCenter Portal role {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44178: Error occurred while removing role mapping entry for service {0} and service role {1} from WebCenter Portal role {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44179: Error occurred while removing role mapping entries for service {0} in scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44179: Error occurred while removing role mapping entries for service {0} in scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44180: Error occurred while removing role mapping entries for scope {0}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44180: Error occurred while removing role mapping entries for scope {0}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44181: Error occurred while fetching role mapping metadata for scope {0}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44181: Error occurred while fetching role mapping metadata for scope {0}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44182: Error occurred while adding role mapping metadata to scope {0}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44182: Error occurred while adding role mapping metadata to scope {0}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44183: Cannot copy role mapping metadata for scope {0} as the metadata already exists

Cause: Role mapping metadata already existed for the given scope.

Action: Remove the role mapping metadata for the scope and then perform this operation again. Alternatively, you can pass a different scope for which the role mapping metadata does not already exist.
Level: 1

Type: ERROR

Impact: Security

WCS-44183: Cannot copy role mapping metadata for scope {0} as the metadata already exists

Cause: Role mapping metadata already existed for the given scope.

Action: Remove the role mapping metadata for the scope and then perform this operation again. Alternatively, you can pass a different scope for which the role mapping metadata does not already exist.
Level: 1

Type: ERROR

Impact: Security

WCS-44184: Error occurred while fetching role mapping metadata for service {0} in scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44184: Error occurred while fetching role mapping metadata for service {0} in scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44185: Error occurred while adding role mapping metadata for service {0} in scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44185: Error occurred while adding role mapping metadata for service {0} in scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44186: Unable to obtain service {0} role mapping metadata for scope {1}

Cause: The query to obtain role mapping metadata for the scope returned a path for which the metadata did not exist.

Action: Ensure the service role mapping metadata exists for the scope.
Level: 1

Type: WARNING

Impact: Security

WCS-44186: Unable to obtain service {0} role mapping metadata for scope {1}

Cause: The query to obtain role mapping metadata for the scope returned a path for which the metadata did not exist.

Action: Ensure the service role mapping metadata exists for the scope.
Level: 1

Type: WARNING

Impact: Security

WCS-44187: The role mapping metadata for service {0} in scope {1} is being modified by another user. Try the operation again after some time.

Cause: Another user acquired the write lock on the service role mapping metadata.

Action: Try the operation after some time.
Level: 1

Type: WARNING

Impact: Security

WCS-44187: The role mapping metadata for service {0} in scope {1} is being modified by another user. Try the operation again after some time.

Cause: Another user acquired the write lock on the service role mapping metadata.

Action: Try the operation after some time.
Level: 1

Type: WARNING

Impact: Security

WCS-44188: Cannot copy the role mapping metadata for service {0} in scope {1}

Cause: The service role mapping metadata for the scope already existed.

Action: Remove the service role mapping for the scope and then perform the operation again. Alternatively, you can pass a different service and scope for which the role mapping metadata does not already exist.
Level: 1

Type: ERROR

Impact: Security

WCS-44188: Cannot copy the role mapping metadata for service {0} in scope {1}

Cause: The service role mapping metadata for the scope already existed.

Action: Remove the service role mapping for the scope and then perform the operation again. Alternatively, you can pass a different service and scope for which the role mapping metadata does not already exist.
Level: 1

Type: ERROR

Impact: Security

WCS-44189: Cannot find the WebCenter Portal application role {0}

Cause: The WebCenter Portal application role passed to Role Manager did not exist.

Action: Ensure that a valid application role is passed to Role Manager.
Level: 1

Type: ERROR

Impact: Security

WCS-44189: Cannot find the WebCenter Portal application role {0}

Cause: The WebCenter Portal application role passed to Role Manager did not exist.

Action: Ensure that a valid application role is passed to Role Manager.
Level: 1

Type: ERROR

Impact: Security

WCS-44190: Error copying role mapping metadata from role {0} to role {1} in scope {2}

Cause: Role mapping metadata could not be copied. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. To perform role mapping, use the Roles tab in the portal settings.
Level: 1

Type: ERROR

Impact: Security

WCS-44190: Error copying role mapping metadata from role {0} to role {1} in scope {2}

Cause: Role mapping metadata could not be copied. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. To perform role mapping, use the Roles tab in the portal settings.
Level: 1

Type: ERROR

Impact: Security

WCS-44191: Error deleting role mapping metadata from role {0} in scope {1}

Cause: The role mapping metadata could not be deleted. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44191: Error deleting role mapping metadata from role {0} in scope {1}

Cause: The role mapping metadata could not be deleted. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44192: Error while determining enterprise role mapping support. Enterprise groups, and not the individual group members, will be added directly as members.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: If a service configured does not support enterprise role mapping, then take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44192: Error while determining enterprise role mapping support. Enterprise groups, and not the individual group members, will be added directly as members.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: If a service configured does not support enterprise role mapping, then take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44193: The permission action is invalid for the service ID: {0}.

Cause: Either permission action name or icon was not specified in the service-definition.xml file.

Action: Ensure that the permission action name and icon is defined correctly in the service-definition.xml file for the service. The permission action should be specified as <permission-action name="view" icon="/adf/webcenter/view_qualifier.png"/>
Level: 1

Type: ERROR

Impact: Security

WCS-44193: The permission action is invalid for the service ID: {0}.

Cause: Either permission action name or icon was not specified in the service-definition.xml file.

Action: Ensure that the permission action name and icon is defined correctly in the service-definition.xml file for the service. The permission action should be specified as <permission-action name="view" icon="/adf/webcenter/view_qualifier.png"/>
Level: 1

Type: ERROR

Impact: Security

WCS-44194: The application level permission class is null for the service ID: {0}.

Cause: The application permission class was not defined in the service-definition.xml file.

Action: Ensure that the application permission class is defined in the service-definition.xml file for the service. The application permission class should be specified as <application-permission-impl>permission class</application-permission-impl> in <application-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44194: The application level permission class is null for the service ID: {0}.

Cause: The application permission class was not defined in the service-definition.xml file.

Action: Ensure that the application permission class is defined in the service-definition.xml file for the service. The application permission class should be specified as <application-permission-impl>permission class</application-permission-impl> in <application-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44195: The application level permission target is not defined for the service ID: {0}.

Cause: The application permission target was not defined in the service-definition.xml file.

Action: Ensure that the application permission target is defined in the service-definition.xml file for the service. The application permission target should be specified as <application-permission-target-id>permission target</application-permission-target-id> in <application-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44195: The application level permission target is not defined for the service ID: {0}.

Cause: The application permission target was not defined in the service-definition.xml file.

Action: Ensure that the application permission target is defined in the service-definition.xml file for the service. The application permission target should be specified as <application-permission-target-id>permission target</application-permission-target-id> in <application-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44196: The application level permission actions is not defined for the service ID: {0}.

Cause: The application permission actions list was not defined in the service-definition.xml file.

Action: Ensure that the application permission actions list is defined in the service-definition.xml file for the service. The application permission actions should be specified as <application-permission-action-list>permission actions</application-permission-action-list> in <application-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44196: The application level permission actions is not defined for the service ID: {0}.

Cause: The application permission actions list was not defined in the service-definition.xml file.

Action: Ensure that the application permission actions list is defined in the service-definition.xml file for the service. The application permission actions should be specified as <application-permission-action-list>permission actions</application-permission-action-list> in <application-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44197: The scope level permission class is not defined for the service ID: {0}.

Cause: The scope permission class was not defined in the service-definition.xml file.

Action: Ensure that the scope permission class is defined in the service-definition.xml file for the service. The scope permission class should be specified as <scope-permission-impl>permission class</scope-permission-impl> in <scope-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44197: The scope level permission class is not defined for the service ID: {0}.

Cause: The scope permission class was not defined in the service-definition.xml file.

Action: Ensure that the scope permission class is defined in the service-definition.xml file for the service. The scope permission class should be specified as <scope-permission-impl>permission class</scope-permission-impl> in <scope-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44198: The scope level permission target is not defined for the service ID: {0}.

Cause: The scope permission target was not defined in the service-definition.xml file.

Action: Ensure that the scope permission target is defined in the service-definition.xml file for the service. The scope permission target should be specified as <scope-permission-target-id>permission target</scope-permission-target-id> in <scope-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44198: The scope level permission target is not defined for the service ID: {0}.

Cause: The scope permission target was not defined in the service-definition.xml file.

Action: Ensure that the scope permission target is defined in the service-definition.xml file for the service. The scope permission target should be specified as <scope-permission-target-id>permission target</scope-permission-target-id> in <scope-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44199: The scope level permission actions is not defined for the service ID: {0}.

Cause: The scope permission actions list was not defined in the service-definition.xml file.

Action: Ensure that the scope permission actions list is defined in the service-definition.xml file for the service. The scope permission actions should be specified as <scope-permission-action-list>permission actions</scope-permission-action-list> in <scope-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44199: The scope level permission actions is not defined for the service ID: {0}.

Cause: The scope permission actions list was not defined in the service-definition.xml file.

Action: Ensure that the scope permission actions list is defined in the service-definition.xml file for the service. The scope permission actions should be specified as <scope-permission-action-list>permission actions</scope-permission-action-list> in <scope-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44200: The resource level permission class is not defined for the service ID: {0}.

Cause: The resource permission class was not defined in the service-definition.xml file.

Action: Ensure that the resource permission class is defined in the service-definition.xml file for the service. The resource permission class should be specified as <resource-permission-impl>permission class</resource-permission-impl> in <resource-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44200: The resource level permission class is not defined for the service ID: {0}.

Cause: The resource permission class was not defined in the service-definition.xml file.

Action: Ensure that the resource permission class is defined in the service-definition.xml file for the service. The resource permission class should be specified as <resource-permission-impl>permission class</resource-permission-impl> in <resource-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44201: The resource level permission target is not defined for the service ID: {0}.

Cause: The resource permission target was not defined in the service-definition.xml file.

Action: Ensure that the resource permission target is defined in the service-definition.xml file for the service. The resource permission target should be specified as <resource-permission-target-id>permission target</resource-permission-target-id> in <resource-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44201: The resource level permission target is not defined for the service ID: {0}.

Cause: The resource permission target was not defined in the service-definition.xml file.

Action: Ensure that the resource permission target is defined in the service-definition.xml file for the service. The resource permission target should be specified as <resource-permission-target-id>permission target</resource-permission-target-id> in <resource-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44202: The resource level permission actions is not defined for the service ID: {0}.

Cause: The resource permission actions list was not defined in the service-definition.xml file.

Action: Ensure that the resource permission actions list is defined in the service-definition.xml file for the service. The resource permission actions should be specified as <resource-permission-action-list>permission actions</resource-permission-action-list> in <resource-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44202: The resource level permission actions is not defined for the service ID: {0}.

Cause: The resource permission actions list was not defined in the service-definition.xml file.

Action: Ensure that the resource permission actions list is defined in the service-definition.xml file for the service. The resource permission actions should be specified as <resource-permission-action-list>permission actions</resource-permission-action-list> in <resource-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44203: The application role operations list is not specified at the application level for the service ID: {0}.

Cause: The application role operations list is not specified at the application level. It was not defined in the service-definition.xml file.

Action: Ensure that the application role operations list is defined at the application level in the service-definition.xml file for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44203: The application role operations list is not specified at the application level for the service ID: {0}.

Cause: The application role operations list is not specified at the application level. It was not defined in the service-definition.xml file.

Action: Ensure that the application role operations list is defined at the application level in the service-definition.xml file for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44204: The application role operations list is not specified at the scope level for the service ID: {0}.

Cause: The application role operations list is not specified at the scope level was not defined in the service-definition.xml file.

Action: Ensure that the application role operations list is defined at the scope level in the service-definition.xml file for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44204: The application role operations list is not specified at the scope level for the service ID: {0}.

Cause: The application role operations list is not specified at the scope level was not defined in the service-definition.xml file.

Action: Ensure that the application role operations list is defined at the scope level in the service-definition.xml file for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44205: The application role operations list is not specified at the resource level for the service ID: {0}.

Cause: The application role operations list is not specified at the resource level was not defined in the service-definition.xml file.

Action: Ensure that the application role operations list is defined at the resource level in the service-definition.xml file for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44205: The application role operations list is not specified at the resource level for the service ID: {0}.

Cause: The application role operations list is not specified at the resource level was not defined in the service-definition.xml file.

Action: Ensure that the application role operations list is defined at the resource level in the service-definition.xml file for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44206: The application role operation specified is invalid for the service ID: {0}.

Cause: Operation name or application role or icon has not been specified correctly for the application role operation in service-definition.xml

Action: Ensure that the application role operation is specified correctly with operation name, application role and icon in the service-definition.xml file for the service. An application role operation entry looks like this - <application-operation name="manage" approle="AppConnectionManager" icon="/adf/webcenter/manage.png"/>
Level: 1

Type: ERROR

Impact: Security

WCS-44206: The application role operation specified is invalid for the service ID: {0}.

Cause: Operation name or application role or icon has not been specified correctly for the application role operation in service-definition.xml

Action: Ensure that the application role operation is specified correctly with operation name, application role and icon in the service-definition.xml file for the service. An application role operation entry looks like this - <application-operation name="manage" approle="AppConnectionManager" icon="/adf/webcenter/manage.png"/>
Level: 1

Type: ERROR

Impact: Security

WCS-44207: Error occurred while adding resource {0} security override entry for service {1} in scope {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44207: Error occurred while adding resource {0} security override entry for service {1} in scope {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44208: Error occurred while removing resource {0} security override entry for service {1} in scope {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44208: Error occurred while removing resource {0} security override entry for service {1} in scope {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44209: Error occurred while checking if resource {0} override security for service {1} in scope {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44209: Error occurred while checking if resource {0} override security for service {1} in scope {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44210: Error occurred while removing security override entries for scope {0}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44210: Error occurred while removing security override entries for scope {0}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44211: Error occurred while removing security override entries for service {0} in scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44211: Error occurred while removing security override entries for service {0} in scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44212: The security override metadata for service {0} in scope {1} is being modified by another user. Try the operation again after some time.

Cause: Another user acquired the write lock on the service security override metadata.

Action: Try the operation after some time.
Level: 1

Type: WARNING

Impact: Security

WCS-44212: The security override metadata for service {0} in scope {1} is being modified by another user. Try the operation again after some time.

Cause: Another user acquired the write lock on the service security override metadata.

Action: Try the operation after some time.
Level: 1

Type: WARNING

Impact: Security

WCS-44213: Invalid Security Handler for service {0}. Expected Type: {1} Actual Type: {2}.

Cause: Security Handler defined in service-definition was of incorrect type

Action: Define the correct security handler in the service-definition as specified
Level: 1

Type: ERROR

Impact: Security

WCS-44213: Invalid Security Handler for service {0}. Expected Type: {1} Actual Type: {2}.

Cause: Security Handler defined in service-definition was of incorrect type

Action: Define the correct security handler in the service-definition as specified
Level: 1

Type: ERROR

Impact: Security

WCS-44214: Security Extension not found for service {0}.

Cause: Security Extension not defined in service-definition.

Action: Define the security extension appropriately in the service-definition.
Level: 1

Type: ERROR

Impact: Security

WCS-44214: Security Extension not found for service {0}.

Cause: Security Extension not defined in service-definition.

Action: Define the security extension appropriately in the service-definition.
Level: 1

Type: ERROR

Impact: Security

WCS-44215: Security Handler not found for service {0}.

Cause: Security Handler specified in the security extension is either undefined or could not be found.

Action: Ensure the correct security handler class is defined in the security extension of service-definition.
Level: 1

Type: ERROR

Impact: Security

WCS-44215: Security Handler not found for service {0}.

Cause: Security Handler specified in the security extension is either undefined or could not be found.

Action: Ensure the correct security handler class is defined in the security extension of service-definition.
Level: 1

Type: ERROR

Impact: Security

WCS-44216: Could not determine security authorization type for service {0}. It needs to be one of the following - PERMISSION, APPLICATION_ROLE or ROLEMAPPING.

Cause: The security extension either does not contain any authorization model or contains more than one.

Action: Depending on the authorization model, security extension must be updated to specify the appropriate security model.
Level: 1

Type: ERROR

Impact: Security

WCS-44216: Could not determine security authorization type for service {0}. It needs to be one of the following - PERMISSION, APPLICATION_ROLE or ROLEMAPPING.

Cause: The security extension either does not contain any authorization model or contains more than one.

Action: Depending on the authorization model, security extension must be updated to specify the appropriate security model.
Level: 1

Type: ERROR

Impact: Security

WCS-44217: Permission security model not defined at {0} level for service {1}.

Cause: Permission check or provisioning is being attempted at specified level where as the security extension in the service-definition does not define given level permission security model

Action: Either define specified level permission security metadata or do not attempt security provisioning or check at given level for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44217: Permission security model not defined at {0} level for service {1}.

Cause: Permission check or provisioning is being attempted at specified level where as the security extension in the service-definition does not define given level permission security model

Action: Either define specified level permission security metadata or do not attempt security provisioning or check at given level for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44218: Application Roles security model not defined at {0} level for service {1}.

Cause: Security check or provisioning is being attempted at specified level where as the security extension in the service-definition does not define given level application role security model

Action: Either define specified level application role security metadata or do not attempt security provisioning or check at given level for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44218: Application Roles security model not defined at {0} level for service {1}.

Cause: Security check or provisioning is being attempted at specified level where as the security extension in the service-definition does not define given level application role security model

Action: Either define specified level application role security metadata or do not attempt security provisioning or check at given level for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44219: Error occurred revoking permissions for {0} service resource {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44219: Error occurred revoking permissions for {0} service resource {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44220: Application Role not defined for {0} service action {1} at {2} level.

Cause: Application Role for the given service action and level not defined in security extension of service-definition.

Action: Define the application role mapping for the given service action at the given level else do not attempt security provisioning or check for the service at given level.
Level: 1

Type: ERROR

Impact: Security

WCS-44220: Application Role not defined for {0} service action {1} at {2} level.

Cause: Application Role for the given service action and level not defined in security extension of service-definition.

Action: Define the application role mapping for the given service action at the given level else do not attempt security provisioning or check for the service at given level.
Level: 1

Type: ERROR

Impact: Security

WCS-44221: Error occurred checking {0} action for {1} service at {2} level.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44221: Error occurred checking {0} action for {1} service at {2} level.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44222: An error occurred while retrieving the policies or permissions.

Cause: This is caused when the policy store is not accessible or is not running or the service definition is not defined properly.

Action: Ensure that the policy store and service definition is configured properly and is running.
Level: 1

Type: ERROR

Impact: Security

WCS-44222: An error occurred while retrieving the policies or permissions.

Cause: This is caused when the policy store is not accessible or is not running or the service definition is not defined properly.

Action: Ensure that the policy store and service definition is configured properly and is running.
Level: 1

Type: ERROR

Impact: Security

WCS-44223: An error occurred while saving the permissions.

Cause: This is caused when the policy store is not accessible or is not running or the service definition is not defined properly.

Action: Ensure that the policy store and service definition is configured properly and is running.
Level: 1

Type: ERROR

Impact: Security

WCS-44223: An error occurred while saving the permissions.

Cause: This is caused when the policy store is not accessible or is not running or the service definition is not defined properly.

Action: Ensure that the policy store and service definition is configured properly and is running.
Level: 1

Type: ERROR

Impact: Security

WCS-44224: An error occurred while saving the permissions.

Cause: This is caused when the service definition is not defined properly.

Action: Ensure that the service definition is configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44224: An error occurred while saving the permissions.

Cause: This is caused when the service definition is not defined properly.

Action: Ensure that the service definition is configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44225: An error occurred while setting service id.

Cause: This is caused when the service definition is not defined properly.

Action: Ensure that the service definition is configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44225: An error occurred while setting service id.

Cause: This is caused when the service definition is not defined properly.

Action: Ensure that the service definition is configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44226: Error while accessing data from OPSS Policy Store.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44226: Error while accessing data from OPSS Policy Store.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44227: An error occurred while getting portal assets and WebCenter Portal services

Cause: This is caused when the service definition is not defined properly.

Action: Ensure that the service definition is configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44227: An error occurred while getting portal assets and WebCenter Portal services

Cause: This is caused when the service definition is not defined properly.

Action: Ensure that the service definition is configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44228: An error occurred while determining list of portal assets that override security for service {0} in scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44228: An error occurred while determining list of portal assets that override security for service {0} in scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44229: An error encountered while getting mapped action.

Cause: This is caused when the service definition is not defined properly.

Action: Ensure that the service definition is configured properly.
Level: 1

Type: WARNING

Impact: Security

WCS-44229: An error encountered while getting mapped action.

Cause: This is caused when the service definition is not defined properly.

Action: Ensure that the service definition is configured properly.
Level: 1

Type: WARNING

Impact: Security

WCS-44230: An error encountered while trying to retrieve {0} service policies at {1} level for scope {2} and asset {3}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44230: An error encountered while trying to retrieve {0} service policies at {1} level for scope {2} and asset {3}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44231: An error encountered while trying to grant {0} service policies at {1} level for scope {2} and asset {3}.

Cause: Review the underlying exception in the logs to determine the exact cause. The grant could already exist.

Action: Take action based on the underlying exception details. If the grant already exists, revoke the grant using WLST and perform operation again.
Level: 1

Type: ERROR

Impact: Security

WCS-44231: An error encountered while trying to grant {0} service policies at {1} level for scope {2} and asset {3}.

Cause: Review the underlying exception in the logs to determine the exact cause. The grant could already exist.

Action: Take action based on the underlying exception details. If the grant already exists, revoke the grant using WLST and perform operation again.
Level: 1

Type: ERROR

Impact: Security

WCS-44232: An error encountered while trying to revoke {0} service policies at {1} level for scope {2} and asset {3}.

Cause: Review the underlying exception in the logs to determine the exact cause. The grant being revoked probably does not exist.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44232: An error encountered while trying to revoke {0} service policies at {1} level for scope {2} and asset {3}.

Cause: Review the underlying exception in the logs to determine the exact cause. The grant being revoked probably does not exist.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44233: An error encountered while trying to obtain subject for user {0}, returning anonymous user subject instead.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44233: An error encountered while trying to obtain subject for user {0}, returning anonymous user subject instead.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44234: An error encountered while trying to create role {0}.

Cause: Review the underlying exception in the logs to determine the exact cause. The role may be already exists or there is a problem with policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44234: An error encountered while trying to create role {0}.

Cause: Review the underlying exception in the logs to determine the exact cause. The role may be already exists or there is a problem with policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44235: An error encountered while trying to get application roles.

Cause: Review the underlying exception in the logs to determine the exact cause. The roles may not exists or there is an issue with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44235: An error encountered while trying to get application roles.

Cause: Review the underlying exception in the logs to determine the exact cause. The roles may not exists or there is an issue with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44236: An error encountered while trying to create role {0}.

Cause: Review the underlying exception in the logs to determine the exact cause. The role may be already exists or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44236: An error encountered while trying to create role {0}.

Cause: Review the underlying exception in the logs to determine the exact cause. The role may be already exists or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44237: An error encountered while trying to get members.

Cause: Review the underlying exception in the logs to determine the exact cause. The members may not exist or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44237: An error encountered while trying to get members.

Cause: Review the underlying exception in the logs to determine the exact cause. The members may not exist or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44238: An error encountered while trying to get members.

Cause: Review the underlying exception in the logs to determine the exact cause. The member may not exist or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44238: An error encountered while trying to get members.

Cause: Review the underlying exception in the logs to determine the exact cause. The member may not exist or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44239: An error encountered while trying to delete members.

Cause: Review the underlying exception in the logs to determine the exact cause. The member may already exist or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44239: An error encountered while trying to delete members.

Cause: Review the underlying exception in the logs to determine the exact cause. The member may already exist or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44240: Cannot access the resource

Cause: The service was not defined properly.

Action: Ensure that the service definition is configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44240: Cannot access the resource

Cause: The service was not defined properly.

Action: Ensure that the service definition is configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44241: Failed to issue token.

Cause: Trust Service Token Manager failed to issue the token.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44241: Failed to issue token.

Cause: Trust Service Token Manager failed to issue the token.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44242: TrustService instance is null.

Cause: Failed to get TrustService instance from the JPS context.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44242: TrustService instance is null.

Cause: Failed to get TrustService instance from the JPS context.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44243: TokenManager instance is null.

Cause: Failed to get TokenManager instance from the TrustService.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44243: TokenManager instance is null.

Cause: Failed to get TokenManager instance from the TrustService.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44244: Could not execute search

Cause: The identity store is not up or is not configured properly.

Action: Ensure that the identity store is up and configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44244: Could not execute search

Cause: The identity store is not up or is not configured properly.

Action: Ensure that the identity store is up and configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44245: Could not add to role

Cause: The policy object already exists or the policy store is not configured properly.

Action: Ensure that the policy is not already added and policy store is configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44245: Could not add to role

Cause: The policy object already exists or the policy store is not configured properly.

Action: Ensure that the policy is not already added and policy store is configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44246: An internal JPS error occurred while exporting / importing application roles.

Cause: This may have been caused when retrieving information from the Application Policy Store or while granting permissions to roles.

Action: Review the exception to determine exact cause.
Level: 1

Type: WARNING

Impact: Security

WCS-44246: An internal JPS error occurred while exporting / importing application roles.

Cause: This may have been caused when retrieving information from the Application Policy Store or while granting permissions to roles.

Action: Review the exception to determine exact cause.
Level: 1

Type: WARNING

Impact: Security

WCS-44247: Could not delete application role {0}.

Cause: This may have been caused because the role to be deleted does not exist any more.

Action: Review the exception to determine exact cause.
Level: 1

Type: WARNING

Impact: Security

WCS-44247: Could not delete application role {0}.

Cause: This may have been caused because the role to be deleted does not exist any more.

Action: Review the exception to determine exact cause.
Level: 1

Type: WARNING

Impact: Security

WCS-44248: The documents role mapping failed during import for portal : {0} and application role {1}.

Cause: This is caused by an error experienced by service-specific Role Mapping provider.

Action: Inspect the server logs and rectify the problem encountered by the service Role Mapping provider.
Level: 1

Type: ERROR

Impact: Security

WCS-44248: The documents role mapping failed during import for portal : {0} and application role {1}.

Cause: This is caused by an error experienced by service-specific Role Mapping provider.

Action: Inspect the server logs and rectify the problem encountered by the service Role Mapping provider.
Level: 1

Type: ERROR

Impact: Security

WCS-44249: No application role found for scope : {0}.

Cause: This may be due to an error that could have occurred during Portal creation or import due to which the roles were not created.

Action: Inspect the logs to confirm which Portal is this error being thrown for and try manually accessing the Portal. If the Portal is inaccessible, re try import or, re create the Portal.
Level: 1

Type: WARNING

Impact: Security

WCS-44249: No application role found for scope : {0}.

Cause: This may be due to an error that could have occurred during Portal creation or import due to which the roles were not created.

Action: Inspect the logs to confirm which Portal is this error being thrown for and try manually accessing the Portal. If the Portal is inaccessible, re try import or, re create the Portal.
Level: 1

Type: WARNING

Impact: Security

WCS-44250: Unable to obtain MDSSession to initialize {0} store.

Cause: This is caused by an underlying MDS Configuration exception while trying to initialize the customization config.

Action: Review the exception to determine exact cause.
Level: 1

Type: ERROR

Impact: Security

WCS-44250: Unable to obtain MDSSession to initialize {0} store.

Cause: This is caused by an underlying MDS Configuration exception while trying to initialize the customization config.

Action: Review the exception to determine exact cause.
Level: 1

Type: ERROR

Impact: Security

WCS-44251: Start time {0} specified for an impersonation grant cannot be after end time {1}

Cause: Start time for impersonation grant is after end time

Action: Ensure start time specified for an impersonation grant is before end time
Level: 1

Type: WARNING

Impact: Security

WCS-44251: Start time {0} specified for an impersonation grant cannot be after end time {1}

Cause: Start time for impersonation grant is after end time

Action: Ensure start time specified for an impersonation grant is before end time
Level: 1

Type: WARNING

Impact: Security

WCS-44252: You cannot add, update, or remove yourself as an impersonator

Cause: Adding, updating, or removing oneself as an impersonator is not allowed

Action: Ensure impersonator being added, updated or removed is a valid impersonator
Level: 1

Type: WARNING

Impact: Security

WCS-44252: You cannot add, update, or remove yourself as an impersonator

Cause: Adding, updating, or removing oneself as an impersonator is not allowed

Action: Ensure impersonator being added, updated or removed is a valid impersonator
Level: 1

Type: WARNING

Impact: Security

WCS-44253: Impersonator {0} already added for user {1}

Cause: You can add an impersonator only once for a user

Action: Ensure you add an impersonator only once for a user. To specify a different time duration, edit the existing grant
Level: 1

Type: WARNING

Impact: Security

WCS-44253: Impersonator {0} already added for user {1}

Cause: You can add an impersonator only once for a user

Action: Ensure you add an impersonator only once for a user. To specify a different time duration, edit the existing grant
Level: 1

Type: WARNING

Impact: Security

WCS-44254: Impersonatee {0} already added for user {1}

Cause: You can add an impersonator only once for a user

Action: Ensure you add an impersonator only once for a user. To specify a different time duration, edit the existing grant
Level: 1

Type: WARNING

Impact: Security

WCS-44254: Impersonatee {0} already added for user {1}

Cause: You can add an impersonator only once for a user

Action: Ensure you add an impersonator only once for a user. To specify a different time duration, edit the existing grant
Level: 1

Type: WARNING

Impact: Security

WCS-44255: Cannot update or delete impersonator {0} for user {1} as impersonator not yet added

Cause: The impersonator being updated or deleted has not been added yet

Action: Ensure the impersonator has been added before trying to update or remove the impersonation grant
Level: 1

Type: WARNING

Impact: Security

WCS-44255: Cannot update or delete impersonator {0} for user {1} as impersonator not yet added

Cause: The impersonator being updated or deleted has not been added yet

Action: Ensure the impersonator has been added before trying to update or remove the impersonation grant
Level: 1

Type: WARNING

Impact: Security

WCS-44256: Cannot update or delete impersonatee {0} for user {1} as impersonatee not yet added

Cause: The impersonator being updated or deleted has not been added yet

Action: Ensure the impersonator has been added before trying to update or remove the impersonation grant
Level: 1

Type: WARNING

Impact: Security

WCS-44256: Cannot update or delete impersonatee {0} for user {1} as impersonatee not yet added

Cause: The impersonator being updated or deleted has not been added yet

Action: Ensure the impersonator has been added before trying to update or remove the impersonation grant
Level: 1

Type: WARNING

Impact: Security

WCS-44257: Impersonator user {0} could not be found

Cause: The impersonator specified is not a valid user

Action: Ensure you specify a valid impersonator
Level: 1

Type: WARNING

Impact: Security

WCS-44257: Impersonator user {0} could not be found

Cause: The impersonator specified is not a valid user

Action: Ensure you specify a valid impersonator
Level: 1

Type: WARNING

Impact: Security

WCS-44258: Impersonatee user {0} could not be found

Cause: The impersonatee specified is not a valid user

Action: Ensure you specify a valid impersonatee
Level: 1

Type: WARNING

Impact: Security

WCS-44258: Impersonatee user {0} could not be found

Cause: The impersonatee specified is not a valid user

Action: Ensure you specify a valid impersonatee
Level: 1

Type: WARNING

Impact: Security

WCS-44259: Fetching Impersonator user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44259: Fetching Impersonator user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44260: Fetching Impersonatee user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44260: Fetching Impersonatee user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44261: Adding impersonator {0} for user {1} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44261: Adding impersonator {0} for user {1} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44262: Updating impersonator {0} for user {1} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44262: Updating impersonator {0} for user {1} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44263: Removing impersonator {0} for user {1} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44263: Removing impersonator {0} for user {1} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44264: Getting impersonators for user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44264: Getting impersonators for user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44265: Getting impersonatees for user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44265: Getting impersonatees for user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44266: Removing expired impersonation grants for user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44266: Removing expired impersonation grants for user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44267: Starting impersonation session for user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44267: Starting impersonation session for user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44268: Terminating impersonation session for current user failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44268: Terminating impersonation session for current user failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44269: User {0} is not a valid impersonator

Cause: The user specified as impersonator does not belong to webcenter#-#impersonators role.

Action: Ensure you specify a user that belongs to webcenter#-#impersontors role.
Level: 1

Type: WARNING

Impact: Security

WCS-44269: User {0} is not a valid impersonator

Cause: The user specified as impersonator does not belong to webcenter#-#impersonators role.

Action: Ensure you specify a user that belongs to webcenter#-#impersontors role.
Level: 1

Type: WARNING

Impact: Security

WCS-44270: Determining if user {0} is a valid impersonator failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44270: Determining if user {0} is a valid impersonator failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44271: Adding or updating impersonator {0} for user {1} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44271: Adding or updating impersonator {0} for user {1} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44272: Searching for impersonators matching pattern {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44272: Searching for impersonators matching pattern {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44273: Impersonation Time delta {0} specified is in invalid format

Cause: Time delta specified was not a valid integer

Action: Check documentation to understand the format in which this delta needs to be specified. It needs to be a valid integer
Level: 1

Type: WARNING

Impact: Security

WCS-44273: Impersonation Time delta {0} specified is in invalid format

Cause: Time delta specified was not a valid integer

Action: Check documentation to understand the format in which this delta needs to be specified. It needs to be a valid integer
Level: 1

Type: WARNING

Impact: Security

WCS-44274: Impersonation configuration check failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44274: Impersonation configuration check failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44275: End time {0} cannot be before current time.

Cause: End time for impersonation grant is before current time

Action: Ensure end time is not before current time
Level: 1

Type: WARNING

Impact: Security

WCS-44300: An error encountered while granting permissions

Cause: Review the underlying exception in the logs to determine the exact cause. The policy may already have been granted or the identity may not exist or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44300: An error encountered while granting permissions

Cause: Review the underlying exception in the logs to determine the exact cause. The policy may already have been granted or the identity may not exist or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44301: An error encountered while revoking permissions

Cause: Review the underlying exception in the logs to determine the exact cause. The policy may not exist or the identity may not exist or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44301: An error encountered while revoking permissions

Cause: Review the underlying exception in the logs to determine the exact cause. The policy may not exist or the identity may not exist or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44302: An OPSS error occurred while locating the audit service.

Cause: The error would be caused when Audit Service is not configured. Review the jps-config.xml configuration file in conjunction with the stack trace if Audit Service needs to be enabled for WebCenter Portal.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Security

WCS-44302: An OPSS error occurred while locating the audit service.

Cause: The error would be caused when Audit Service is not configured. Review the jps-config.xml configuration file in conjunction with the stack trace if Audit Service needs to be enabled for WebCenter Portal.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Security

WCS-44304: Invalid security attribute {0} obtained for artifact {1} in service {2}

Cause: The security attribute returned by the service does not comply to the list of expected security attributes

Action: Ensure the security attribute is one of the expected values i.e. user, group, application role, authenticated and anonymous roles
Level: 1

Type: ERROR

Impact: Security

WCS-44304: Invalid security attribute {0} obtained for artifact {1} in service {2}

Cause: The security attribute returned by the service does not comply to the list of expected security attributes

Action: Ensure the security attribute is one of the expected values i.e. user, group, application role, authenticated and anonymous roles
Level: 1

Type: ERROR

Impact: Security

WCS-44305: An error occurred while upgrading portal role {0}

Cause: Review the underlying exception in the logs to determine the exact cause. The role may already have been upgraded.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44306: An error occurred while upgrading portal roles

Cause: Review the underlying exception in the logs to determine the exact cause. The role may already have been upgraded.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-47201: An unexpected error occurred in the Activity Stream sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-47201: An unexpected error occurred in the Activity Stream sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-47202: The publish activity failed because invalid arguments were passed to the method: activity ({0}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47202: The publish activity failed because invalid arguments were passed to the method: activity ({0}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47203: The retrieve activities failed because invalid arguments were passed to the method: privateAndUpActorIds ({0}), sharedAndUpActorIds ({1}), publicActorIds ({2}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47203: The retrieve activities failed because invalid arguments were passed to the method: privateAndUpActorIds ({0}), sharedAndUpActorIds ({1}), publicActorIds ({2}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47205: Cannot establish connections. A connections exception was thrown.

Cause: A connections exception has been thrown.

Action: Check the exception's details to see why it was thrown.
Level: 1

Type: ERROR

Impact: Other

WCS-47205: Cannot establish connections. A connections exception was thrown.

Cause: A connections exception has been thrown.

Action: Check the exception's details to see why it was thrown.
Level: 1

Type: ERROR

Impact: Other

WCS-47206: A Service Framework exception was thrown.

Cause: A Service Framework exception has been thrown.

Action: Check the exception's details to see why it was thrown.
Level: 1

Type: ERROR

Impact: Other

WCS-47206: A Service Framework exception was thrown.

Cause: A Service Framework exception has been thrown.

Action: Check the exception's details to see why it was thrown.
Level: 1

Type: ERROR

Impact: Other

WCS-47207: A Settings exception was thrown.

Cause: A Settings exception was thrown.

Action: Check the exception's details to see why it was thrown.
Level: 1

Type: ERROR

Impact: Other

WCS-47207: A Settings exception was thrown.

Cause: A Settings exception was thrown.

Action: Check the exception's details to see why it was thrown.
Level: 1

Type: ERROR

Impact: Other

WCS-47208: The retrieve activities failed because invalid arguments were passed to the method: applicationId ({0}), servivceId ({1}), activityType ({2}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47208: The retrieve activities failed because invalid arguments were passed to the method: applicationId ({0}), servivceId ({1}), activityType ({2}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47209: The retrieve activities failed because invalid arguments were passed to the method: applicationId ({0}), servivceId ({1}), activityType ({2}), sinceDate ({3}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47209: The retrieve activities failed because invalid arguments were passed to the method: applicationId ({0}), servivceId ({1}), activityType ({2}), sinceDate ({3}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47210: A database exception occurred in the Activity Stream Toplink module.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47210: A database exception occurred in the Activity Stream Toplink module.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47211: A query exception occurred in the Activity Stream Toplink module.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47211: A query exception occurred in the Activity Stream Toplink module.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47212: Create Actor failed because an invalid argument was passed to the method: guid ({0}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47212: Create Actor failed because an invalid argument was passed to the method: guid ({0}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47213: Create Object failed because an invalid argument was passed to the method: guid ({0}), type ({1}), displayName ({2}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47213: Create Object failed because an invalid argument was passed to the method: guid ({0}), type ({1}), displayName ({2}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47214: Create Activity Element failed because an invalid argument was passed to the method: applicationID ({0}), scope ({1}), serviceID ({2}), activityType ({3}), actors ({4}), permission ({5}), activityTime ({6}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47214: Create Activity Element failed because an invalid argument was passed to the method: applicationID ({0}), scope ({1}), serviceID ({2}), activityType ({3}), actors ({4}), permission ({5}), activityTime ({6}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47215: Create Activity Type failed because an invalid argument was passed to the method: id ({0}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47215: Create Activity Type failed because an invalid argument was passed to the method: id ({0}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47216: Create Object Type failed because an invalid argument was passed to the method: id ({0}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47216: Create Object Type failed because an invalid argument was passed to the method: id ({0}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47217: Create Activity Element failed because an invalid argument was passed to the method: applicationID ({0}), activityType ({1}), actors ({2}), permission ({3}), activityTime ({4}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47217: Create Activity Element failed because an invalid argument was passed to the method: applicationID ({0}), activityType ({1}), actors ({2}), permission ({3}), activityTime ({4}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47218: Publish activity {0} failed due to {1}.

Cause: An unexpected error during the publishing activity.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47218: Publish activity {0} failed due to {1}.

Cause: An unexpected error during the publishing activity.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47219: An error occurred due to {0}.

Cause: An exception occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47219: An error occurred due to {0}.

Cause: An exception occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47220: An unexpected error occurred resolving property ''{0}'':''{1}'' for an Analytics event of type {2}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47220: An unexpected error occurred resolving property ''{0}'':''{1}'' for an Analytics event of type {2}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47221: Unable to publish the Analytics event (of type {0}).

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47221: Unable to publish the Analytics event (of type {0}).

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47222: This operation is not supported.

Cause: This operation not supported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47222: This operation is not supported.

Cause: This operation not supported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47223: Skipping profile information for user {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-47223: Skipping profile information for user {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-47224: For user {0}, the last accessed page couldn''t be found due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-47224: For user {0}, the last accessed page couldn''t be found due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-47225: Check for valid repository failed.

Cause: Either the database is down or the WebCenter repository is not installed.

Action: Check the exception's details to why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WCS-47225: Check for valid repository failed.

Cause: Either the database is down or the WebCenter repository is not installed.

Action: Check the exception's details to why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WCS-47226: For user {0}, couldn''t retrieve the list of pages last accessed due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-47226: For user {0}, couldn''t retrieve the list of pages last accessed due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-47227: For user {0}, couldn''t retrieve the last accessed page in {1} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-47227: For user {0}, couldn''t retrieve the last accessed page in {1} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-47228: For user {0}, couldn''t clean the last accessed page due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-47228: For user {0}, couldn''t clean the last accessed page due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-47229: The task flow instance was not specified.

Cause: The supplied taskflow instance ID was null or blank.

Action: Specify a valid taskflow instance ID that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-47229: The task flow instance was not specified.

Cause: The supplied taskflow instance ID was null or blank.

Action: Specify a valid taskflow instance ID that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-47230: An activity exception was encountered during the bulk publish operation.

Cause: One or more activities threw an exception.

Action: Check the individual activity exception.
Level: 1

Type: ERROR

Impact: Other

WCS-47230: An activity exception was encountered during the bulk publish operation.

Cause: One or more activities threw an exception.

Action: Check the individual activity exception.
Level: 1

Type: ERROR

Impact: Other

WCS-47231: Create Cust Attr failed because an invalid argument was passed to the method: name ({0}), value ({1}), url ({2}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47231: Create Cust Attr failed because an invalid argument was passed to the method: name ({0}), value ({1}), url ({2}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47232: An unexpected error occurred while setting up the Comments service.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47232: An unexpected error occurred while setting up the Comments service.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47233: An unexpected error occurred while retrieving comments.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47233: An unexpected error occurred while retrieving comments.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47234: An unexpected error occurred while posting a comment.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47234: An unexpected error occurred while posting a comment.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47235: An unexpected error occurred while preparing a comments summary.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47235: An unexpected error occurred while preparing a comments summary.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47236: An unexpected error occurred while preparing comments.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47236: An unexpected error occurred while preparing comments.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47237: Comment text cannot be empty.

Cause: The supplied text for the comment is null or blank.

Action: Specify a non-empty text for the comment.
Level: 1

Type: ERROR

Impact: Other

WCS-47237: Comment text cannot be empty.

Cause: The supplied text for the comment is null or blank.

Action: Specify a non-empty text for the comment.
Level: 1

Type: ERROR

Impact: Other

WCS-47238: An object was not specified.

Cause: The supplied object identifier is null.

Action: Specify a non-null object identifier.
Level: 1

Type: ERROR

Impact: Other

WCS-47238: An object was not specified.

Cause: The supplied object identifier is null.

Action: Specify a non-null object identifier.
Level: 1

Type: ERROR

Impact: Other

WCS-47239: An object ID is not present for the specified object.

Cause: The ID of the specified object is null.

Action: Specify an object with a valid ID.
Level: 1

Type: ERROR

Impact: Other

WCS-47239: An object ID is not present for the specified object.

Cause: The ID of the specified object is null.

Action: Specify an object with a valid ID.
Level: 1

Type: ERROR

Impact: Other

WCS-47240: A service ID is not present for the specified object.

Cause: The service ID for the specified object is null.

Action: Specify an object with a valid service ID.
Level: 1

Type: ERROR

Impact: Other

WCS-47240: A service ID is not present for the specified object.

Cause: The service ID for the specified object is null.

Action: Specify an object with a valid service ID.
Level: 1

Type: ERROR

Impact: Other

WCS-47241: An object type is not present for the specified object.

Cause: The object type for the specified object is null.

Action: Specify an object with a valid object type.
Level: 1

Type: ERROR

Impact: Other

WCS-47241: An object type is not present for the specified object.

Cause: The object type for the specified object is null.

Action: Specify an object with a valid object type.
Level: 1

Type: ERROR

Impact: Other

WCS-47242: An unexpected error while expanding comments.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47242: An unexpected error while expanding comments.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47243: An unexpected error occurred while collapsing comments.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47243: An unexpected error occurred while collapsing comments.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47244: An unexpected error occurred while setting up the Likes service.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47244: An unexpected error occurred while setting up the Likes service.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47245: An unexpected error occurred while retrieving Likes.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47245: An unexpected error occurred while retrieving Likes.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47246: An unexpected error occurred while retrieving Likes.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47246: An unexpected error occurred while retrieving Likes.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47247: An unexpected error occurred while posting a Like.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47247: An unexpected error occurred while posting a Like.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47248: A comment ID not specified.

Cause: The supplied comment ID was null or blank.

Action: Specify a valid comment ID that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-47248: A comment ID not specified.

Cause: The supplied comment ID was null or blank.

Action: Specify a valid comment ID that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-47249: An unexpected error occurred while deleting a comment.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47249: An unexpected error occurred while deleting a comment.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47250: An unexpected error occurred while initializing the scope.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47250: An unexpected error occurred while initializing the scope.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47252: The follow object failed because an invalid arguments was passed to the method: actor ({0}), object ({1}), object service id ({2}).

Cause: One of the input arguments is invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47252: The followed object failed because an invalid arguments was passed to the method: actor ({0}), object ({1}), object service id ({2}).

Cause: One of the input arguments is invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47253: Can''t archive due to an invalid argument: date ({0}).

Cause: One of the input arguments is invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47253: Can''t archive due to an invalid argument: date ({0}).

Cause: One of the input arguments is invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47254: An unexpected error occurred while archiving.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47254: An unexpected error occurred while archiving.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47255: Failed to register application management beans.

Cause: Application management beans(MBean) registration failed. Either there are issues with WebLogic or the application was not packaged properly.

Action: Restart WebLogic or examine WebLogic log files for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-47255: Failed to register application management beans.

Cause: Application management beans(MBean) registration failed. Either there are issues with WebLogic or the application was not packaged properly.

Action: Restart WebLogic or examine WebLogic log files for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-47256: Failed to unregister application management beans.

Cause: Application management beans(MBean) unregistration failed. Either the Mbeans were not registered or the Mbeans were already unregistered.

Action: Examine the WebLogic log files for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-47256: Failed to unregister application management beans.

Cause: Application management beans(MBean) unregistration failed. Either the Mbeans were not registered or the Mbeans were already unregistered.

Action: Examine the WebLogic log files for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-47257: An unexpected error occurred while deleting service data corresponding to the activity.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47257: An unexpected error occurred while deleting service data corresponding to the activity.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47258: The advanced query parameter contains invalid or unsupported constructs.

Cause: There are invalid or unsupported SQL constructs specified in the Advanced Query filter parameter.

Action: Correct the Advanced Query filter parameter.
Level: 1

Type: ERROR

Impact: Other

WCS-47258: The advanced query parameter contains invalid or unsupported constructs.

Cause: There are invalid or unsupported SQL constructs specified in the Advanced Query filter parameter.

Action: Correct the Advanced Query filter parameter.
Level: 1

Type: ERROR

Impact: Other

WCS-47259: An unexpected error occurred in setting up the JMS queue {0}.

Cause: The AQ JMS ConnectionFactory or Queue lookup failed.

Action: Correct JMS Modules in Admin Console.
Level: 1

Type: ERROR

Impact: Other

WCS-47259: An unexpected error occurred in setting up the JMS queue {0}.

Cause: The AQ JMS ConnectionFactory or Queue lookup failed.

Action: Correct JMS Modules in Admin Console.
Level: 1

Type: ERROR

Impact: Other

WCS-47260: An unexpected error occurred while send message to the JMS queue.

Cause: The JMS Queue found, but enqueue failed.

Action: Examine the Weblogic log files for exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-47260: An unexpected error occurred while send message to the JMS queue.

Cause: The JMS Queue found, but enqueue failed.

Action: Examine the Weblogic log files for exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-47261: Fail to get Resource URI for published Activity.

Cause: The ResourceActionUtils.getUrl() failed for input Activity.

Action: Examine the Weblogic log files for exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-47261: Fail to get Resource URI for published Activity.

Cause: The ResourceActionUtils.getUrl() failed for input Activity.

Action: Examine the Weblogic log files for exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-47262: Fail to get Activity message for message key {0} in bundle {1}.

Cause: The getMessage() failed for input Activity.

Action: Examine the Weblogic log files for exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-47262: Fail to get Activity message for message key {0} in bundle {1}.

Cause: The getMessage() failed for input Activity.

Action: Examine the Weblogic log files for exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-47263: Failed to unfollow objects due to {0}.

Cause: An unexpected error occurred during the unfollowing objects.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47263: Failed to unfollow objects due to {0}.

Cause: An unexpected error occurred during the unfollowing objects.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47264: The unfollowed object failed because an invalid arguments was passed to the method: actor ({0}), object ({1}).

Cause: One of the input arguments is invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47264: The unfollowed object failed because an invalid arguments was passed to the method: actor ({0}), object ({1}).

Cause: One of the input arguments is invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47265: Failed to initialize context for asynchronous activity listeners processing.

Cause: Failed to initialize context for asynchronous activity listeners processing.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-47265: Failed to initialize context for asynchronous activity listeners processing.

Cause: Failed to initialize context for asynchronous activity listeners processing.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-47266: Failed to parse the activity definition file {0} due to {1}

Cause: Validate the activity-definition.xml file..

Action: Examine the Weblogic log files for exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-47266: Failed to parse the actitvity definition file {0} due to {1}

Cause: Validate the activity-definition.xml file..

Action: Examine the Weblogic log files for exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-47267: Failed to lookup connection for name {0}.

Cause: Invalid OSN connection name.

Action: Contact Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-47267: Failed to lookup connection for name {0}.

Cause: Invalid OSN connection name.

Action: Contact Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-47268: Could not load extension handler due to {0}.

Cause: Could not load extension handler.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47268: Could not load extension handler due to {0}.

Cause: Could not load extension handler.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47269: Can not close transaction due to {0}.

Cause: Can not close transaction.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47269: Can not close transaction due to {0}.

Cause: Can not close transaction.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47270: Can not close statement due to {0}.

Cause: Can not close statement.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47270: Can not close statement due to {0}.

Cause: Can not close statement.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47271: Can not get result set due to {0}.

Cause: Can not get result set.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47271: Can not get result set due to {0}.

Cause: Can not get result set.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47272: Can not rollback transaction due to {0}.

Cause: Can not rollback transaction.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47272: Can not rollback transaction due to {0}.

Cause: Can not rollback transaction.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47273: Can not load XML actor detail data due to {0}.

Cause: Can not load XML actor detail data.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47273: Can not load XML actor detail data due to {0}.

Cause: Can not load XML actor detail data.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47274: Can not insert new actor details due to {0}.

Cause: Can not insert new actor details.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47274: Can not insert new actor details due to {0}.

Cause: Can not insert new actor details.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47275: Error occurs when processing activity {0} for activity listener{1} due to {2}.

Cause: Could not call activity listener's onsActivity method.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47275: Error occurs when processing activity {0} for activity listener{1} due to {2}.

Cause: Could not call activity listener's onsActivity method.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47276: Failed while retrieving activity listeners due to {0}

Cause: Failed while retrieving activity listeners.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47276: Failed while retrieving activity listeners due to {0}

Cause: Failed while retrieving activity listeners.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47277: Failed to initialize due to {0}

Cause: Failed to initialize.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47277: Failed to initialize due to {0}

Cause: Failed to initialize.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47278: Cannot get service registry due to {0}.

Cause: Error to get service registry.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47278: Cannot get service registry due to {0}.

Cause: Error to get service registry.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47279: Error closing entity manager factory due to {0}

Cause: An unexpected exception occurred while closing the entity manager factory.

Action: Review the exception thrown for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47279: Error closing entity manager factory due to {0}

Cause: An unexpected exception occured while closing the entity manager factory.

Action: Review the exception thrown for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47280: No default value found for key {0}.

Cause: No default value found for key {0}.

Action: Ensure default value for key {0} is valid.
Level: 1

Type: WARNING

Impact: Other

WCS-47280: No default value found for key {0}.

Cause: No default value found for key {0}.

Action: Ensure default value for key {0} is valid.
Level: 1

Type: WARNING

Impact: Other

WCS-47281: Cannot get activity services list due to {0}.

Cause: Cannot get activity services list.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47281: Cannot get activity services list due to {0}.

Cause: Cannot get activity services list.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47282: Resource bundle not found. bundle = {0}, key = {1} .

Cause: Resource bundle not found.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47282: Resource bundle not found. bundle = {0}, key = {1} .

Cause: Resource bundle not found.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47283: Key not found. bundle = {0}, key = {1} .

Cause: Key not found.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47283: Key not found. bundle = {0}, key = {1} .

Cause: Key not found.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47284: Service category {0} is invalid, title key not found, ignoring.

Cause: Service category is invalid, therefore title key not found.

Action: Examine the WebCenter log files for exception details
Level: 1

Type: WARNING

Impact: Other

WCS-47284: Service category {0} is invalid, title key not found, ignoring.

Cause: Service category is invalid, therefore title key not found.

Action: Examine the WebCenter log files for exception details
Level: 1

Type: WARNING

Impact: Other

WCS-47285: Unable to compare Service Settings due to {0}.

Cause: Unable to compare Service Settings.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47285: Unable to compare Service Settings due to {0}.

Cause: Unable to compare Service Settings.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47286: Cannot parse to date due to {0}.

Cause: Cannot parse to date.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47286: Cannot parse to date due to {0}.

Cause: Cannot parse to date.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47287: Cannot parse from date due to {0}.

Cause: Cannot parse from date.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47287: Cannot parse from date due to {0}.

Cause: Cannot parse from date.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47288: Cannot set access control configurable due to {0}.

Cause: Cannot set access control configurable.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47288: Cannot set access control configurable due to {0}.

Cause: Cannot set access control configurable.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47289: Cannot set configurable service category settings due to {0}.

Cause: Cannot set configurable service category settings.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47289: Cannot set configurable service category settings due to {0}.

Cause: Cannot set configurable service category settings.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47290: Can not process activity {0} due to {1}.

Cause: >Can not process activity.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47290: Can not process activity {0} due to {1}.

Cause: >Can not process activity.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47291: Failed to get profile guid {0} due to {1}.

Cause: Failed to get profile guid.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47291: Failed to get profile guid {0} due to {1}.

Cause: Failed to get profile guid.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47292: Failed to get profile id {0} due to {1}.

Cause: Failed to get profile guid.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47292: Failed to get profile id {0} due to {1}.

Cause: Failed to get profile guid.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47293: Cannot summarize activities due to activity list is null.

Cause: Cannot summarize activities due mActivities is null.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47293: Cannot summarize activities due to activity list is null.

Cause: Cannot summarize activities due mActivities is null.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47294: Cannot get object type display name due to {0}.

Cause: Cannot get object type display name.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47294: Cannot get object type display name due to {0}.

Cause: Cannot get object type display name.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47295: Could not publish activity even after retry due to {0}.

Cause: Could not publish activity even after retry.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47295: Could not publish activity even after retry due to {0}.

Cause: Could not publish activity even after retry.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47296: Error while retrieving activities due to {0}.

Cause: Error while retrieving activities.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47296: Error while retrieving activities due to {0}.

Cause: Error while retrieving activities.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47297: Error while processing personal criteria due to {0}.

Cause: Error while processing personal criteria.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47297: Error while processing personal criteria due to {0}.

Cause: Error while processing personal criteria.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47298: Error while processing portals criteria due to {0}.

Cause: Error while processing portals criteria.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47298: Error while processing portals criteria due to {0}.

Cause: Error while processing portals criteria.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47299: Error while processing service id criteria due to {0}.

Cause: Error while processing service id criteria .

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47299: Error while processing service id criteria due to {0}.

Cause: Error while processing service id criteria .

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47300: Error while processing activity type criteria due to {0}.

Cause: Error while processing activity type criteria.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47300: Error while processing activity type criteria due to {0}.

Cause: Error while processing activity type criteria.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47302: Error while processing enterprise id criteria due to {0}.

Cause: Error while processing enterprise id criteria.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47302: Error while processing enterprise id criteria due to {0}.

Cause: Error while processing enterprise id criteria.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47303: Error while processing date criteria due to {0}.

Cause: Error while processing date criteria.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47303: Error while processing date criteria due to {0}.

Cause: Error while processing date criteria.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47304: Skipping rendering activity {0} due to {1}.

Cause: Skipping rendering activity.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47304: Skipping rendering activity {0} due to {1}.

Cause: Skipping rendering activity.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47305: Cannot get profile due to {0}.

Cause: Cannot get profile.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47305: Cannot get profile due to {0}.

Cause: Cannot get profile.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47306: Failed to get activity type icon url due to {0}.

Cause: Failed to get activity type icon url.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47306: Failed to get activity type icon url due to {0}.

Cause: Failed to get activity type icon url.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47307: Failed to get activity type due to {0}.

Cause: Failed to get activity type.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47307: Failed to get activity type due to {0}.

Cause: Failed to get activity type.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47308: Failed to get activity type category due to {0}.

Cause: Failed to get activity type category.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47308: Failed to get activity type category due to {0}.

Cause: Failed to get activity type category.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47309: Failed to get inline preview due to {0}.

Cause: Failed to get inline preview.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47309: Failed to get inline preview due to {0}.

Cause: Failed to get inline preview.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47310: Failed to get object type due to {0}.

Cause: Failed to get object type.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47310: Failed to get object type due to {0}.

Cause: Failed to get object type.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47311: Client listener not supported {0}.

Cause: Client listener not supported.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47311: Client listener not supported {0}.

Cause: Client listener not supported.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47312: Cannot convert user guid {0} to id due to {1}.

Cause: Cannot convert user guid to id.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47312: Cannot convert user guid {0} to id due to {1}.

Cause: Cannot convert user guid to id.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47313: Could not publish activity due to {0}.

Cause: Could not publish activity.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47313: Could not publish activity due to {0}.

Cause: Could not publish activity.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47314: Cannot get preference maps due to {0}.

Cause: Cannot get preference maps .

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47314: Cannot get preference maps due to {0}.

Cause: Cannot get preference maps .

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47315: Cannot obtain scope {0} due to {1}.

Cause: Cannot obtain scope.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47315: Cannot obtain scope {0} due to {1}.

Cause: Cannot obtain scope.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47316: Failed to publish Activity. Activity Detail: {0}.

Cause: Could not publish activity.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47316: Failed to publish Activity. Activity Detail: {0}.

Cause: Could not publish activity.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47317: Failed to publish Activity. Actor Detail: {0}.

Cause: Could not publish activity.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47317: Failed to publish Activity. Actor Detail: {0}.

Cause: Could not publish activity.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47318: During creating of UI components, can not get the object type.

Cause: During creating of UI components, can not get the object type.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47318: Cannot summarize activities due to {0}.

Cause: Cannot summarize activities.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47319: Failed to initialize activity stream settings due to {0}

Cause: Fail to initialize activity stream settings.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47319: Cannot get service {0} due to {1}.

Cause: Error to get service.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47320: Cannot summarize activities due to {0}.

Cause: Cannot summarize activities.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47320: During creating of UI components, can not get the object type.

Cause: During creating of UI components, can not get the object type.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47321: Cannot get service {0} due to {1}.

Cause: Error to get service.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47321: Failed to initialize activity stream settings due to {0}

Cause: Fail to initialize activity stream settings.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47322: An unexpected error occurred while saving settings.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47323: An unexpected error occurred while preparing the activity record.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47324: An unexpected error occurred while refreshing preference settings.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47325: An unexpected error occurred while removing the activity record.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47326: An unexpected error occurred while hiding the popup.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47327: An unexpected error occurred while preparing the activity view or components.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47328: An unexpected error occurred while fetching service IDs.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47329: An unexpected error occurred while initializing activity stream settings.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47330: An unexpected error occurred while saving or hiding preferences.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47331: An unexpected error occurred while fetching the portals.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47332: An unexpected error occurred while retrieving the activities.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47333: An unexpected error occurred while retrieving the summary activities.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47334: An unexpected error occurred while retrieving activities data.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47335: An unexpected error occurred while saving setup options.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
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-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-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-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-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-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-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-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-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-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-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-47806: Unexpected error sending invitation to user ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47807: Invitation not found (the invitation may have been withdrawn, accepted, or declined already)

Cause: The system could not find any invitation with the specified ID.

Action: Ensure that the specified invitation ID is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47807: Invitation not found (the invitation may have been withdrawn, accepted, or declined already)

Cause: The system could not find any invitation with the specified ID.

Action: Ensure that the specified invitation ID is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47808: Invitation ID not specified

Cause: The supplied invitation ID was null or blank.

Action: Specify a valid invitation ID that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-47825: Unexpected error setting Connection list membership of user ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47826: Unexpected error retrieving the Connection lists to which user ''{0}'' belongs

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47826: Unexpected error retrieving the Connection lists to which user ''{0}'' belongs

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47827: Unexpected error creating a connection between users ''{0}'' and ''{1}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47827: Unexpected error creating a connection between users ''{0}'' and ''{1}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47828: Unexpected error preparing the user invitation screen

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47829: Cannot invite oneself as a connection

Cause: You have specified yourself as the invitee.

Action: Specify a username other than that of yourself.
Level: 1

Type: ERROR

Impact: Other

WCS-47829: Cannot invite oneself as a connection

Cause: You have specified yourself as the invitee.

Action: Specify a username other than that of yourself.
Level: 1

Type: ERROR

Impact: Other

WCS-47830: Cannot invite a user who has been invited already ({0})

Cause: The user you have specified has already been invited.

Action: Wait for the invited user to act on your invitation.
Level: 1

Type: ERROR

Impact: Other

WCS-47830: Cannot invite a user who has been invited already ({0})

Cause: The user you have specified has already been invited.

Action: Wait for the invited user to act on your invitation.
Level: 1

Type: ERROR

Impact: Other

WCS-47831: Cannot invite a user who has already invited you ({0})

Cause: The user you have specified has already invited you.

Action: Accept the invitation you have received from the user.
Level: 1

Type: ERROR

Impact: Other

WCS-47831: Cannot invite a user who has already invited you ({0})

Cause: The user you have specified has already invited you.

Action: Accept the invitation you have received from the user.
Level: 1

Type: ERROR

Impact: Other

WCS-47832: Cannot invite a user you are already connected with ({0})

Cause: You have specified one of your existing connections as the invitee.

Action: Specify a username other than that of your existing connections.
Level: 1

Type: ERROR

Impact: Other

WCS-47832: Cannot invite a user you are already connected with ({0})

Cause: You have specified one of your existing connections as the invitee.

Action: Specify a username other than that of your existing connections.
Level: 1

Type: ERROR

Impact: Other

WCS-47833: Unexpected error searching for users with filter pattern ({0})

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47833: Unexpected error searching for users

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47834: Cannot create a connection between users ''{0}'' and ''{1}'' who already connected

Cause: The specified users are already connected with each other.

Action: Specify users who are not yet connected.
Level: 1

Type: ERROR

Impact: Other

WCS-47834: Cannot create a connection between users ''{0}'' and ''{1}'' who already connected

Cause: The specified users are already connected with each other.

Action: Specify users who are not yet connected.
Level: 1

Type: ERROR

Impact: Other

WCS-47835: Unexpected error reading default configuration ''{0}'' or custom configuration

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47835: Unexpected error reading configuration

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47836: Unexpected error getting connections with preferences (userGuid = {0}, applicationId = {1}, scope = {2}, serviceId = {3}, settingKey = {4}, configurableSettingKey = {5})

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47836: Unexpected error getting connections with preferences (userGuid = {0}, applicationId = {1}, scope = {2}, serviceId = {3}, settingKey = {4}, configurableSettingKey = {5})

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47837: Unexpected error getting connections lists with preferences (listNames = {0}, userGuid = {1}, applicationId = {2}, scope = {3}, serviceId = {4}, settingKey = {5}, configurableSettingKey = {6})

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47837: Unexpected error getting connections lists with preferences (listNames = {0}, userGuid = {1}, applicationId = {2}, scope = {3}, serviceId = {4}, settingKey = {5}, configurableSettingKey = {6})

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47838: Cannot create a Connection list with the same name as existing one ({0})

Cause: You already have a connection list with the specified name.

Action: Specify a name other than that of your existing connection lists.
Level: 1

Type: ERROR

Impact: Other

WCS-47838: Cannot create a Connection list with the same name as existing one ({0})

Cause: You already have a connection list with the specified name.

Action: Specify a name other than that of your existing connection lists.
Level: 1

Type: ERROR

Impact: Other

WCS-47839: Unexpected error getting all connections (startIndex = {0}, itemsPerPage = {1})

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-49001: Injectable Service provider did not set list service

Cause: Injectable Service provider could not find the list service.

Action: Make sure List Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49001: Injectable Service provider did not set list service

Cause: Injectable Service provider could not find the list service.

Action: Make sure List Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49002: List id is null

Cause: List ID was not specified in request.

Action: Make sure List ID is specified in request.
Level: 1

Type: ERROR

Impact: Other

WCS-49002: List id is null

Cause: List ID was not specified in request.

Action: Make sure List ID is specified in request.
Level: 1

Type: ERROR

Impact: Other

WCS-49003: Column id is null

Cause: Column ID was not specified in request.

Action: Make sure Column ID is specified in request.
Level: 1

Type: ERROR

Impact: Other

WCS-49003: Column id is null

Cause: Column ID was not specified in request.

Action: Make sure Column ID is specified in request.
Level: 1

Type: ERROR

Impact: Other

WCS-49004: Row id is null

Cause: Row ID was not specified in request.

Action: Make sure Row ID is specified in request.
Level: 1

Type: ERROR

Impact: Other

WCS-49004: Row id is null

Cause: Row ID was not specified in request.

Action: Make sure Row ID is specified in request.
Level: 1

Type: ERROR

Impact: Other

WCS-49005: No 'column' in the request body

Cause: Column data was not found in the request body.

Action: Make sure Column data is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49005: No 'column' in the request body

Cause: Column data was not found in the request body.

Action: Make sure Column data is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49006: No 'list' in the request body

Cause: List data was not found in the request body.

Action: Make sure List data is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49006: No 'list' in the request body

Cause: List data was not found in the request body.

Action: Make sure List data is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49007: No 'row' in the request body

Cause: Row data was not found in the request body.

Action: Make sure Row data is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49007: No 'row' in the request body

Cause: Row data was not found in the request body.

Action: Make sure Row data is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49008: List could not be found for list id [{0}]

Cause: List ID was not found.

Action: Make sure List ID exists.
Level: 1

Type: ERROR

Impact: Other

WCS-49008: List could not be found for list id [{0}]

Cause: List ID was not found.

Action: Make sure List ID exists.
Level: 1

Type: ERROR

Impact: Other

WCS-49009: Column could not be found for column id [{0}]

Cause: Column ID was not found.

Action: Make sure Column ID exists.
Level: 1

Type: ERROR

Impact: Other

WCS-49009: Column could not be found for column id [{0}]

Cause: Column ID was not found.

Action: Make sure Column ID exists.
Level: 1

Type: ERROR

Impact: Other

WCS-49010: Row could not be found for row id [{0}]

Cause: Row ID was not found.

Action: Make sure Row ID exists.
Level: 1

Type: ERROR

Impact: Other

WCS-49010: Row could not be found for row id [{0}]

Cause: Row ID was not found.

Action: Make sure Row ID exists.
Level: 1

Type: ERROR

Impact: Other

WCS-49011: Unable to create list

Cause: List was not created.

Action: See logs for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-49011: Unable to create list

Cause: List was not created.

Action: See logs for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-49012: 'id' should not be supplied with a POST -- use PUT if you want to update

Cause: 'id' should not be supplied with a POST.

Action: Use PUT if you want to update.
Level: 1

Type: ERROR

Impact: Other

WCS-49012: 'id' should not be supplied with a POST -- use PUT if you want to update

Cause: 'id' should not be supplied with a POST.

Action: Use PUT if you want to update.
Level: 1

Type: ERROR

Impact: Other

WCS-49013: Search parameter must follow [column:[operator:]]value;[column:[operator:]value] syntax

Cause: Search parameter syntax not understood.

Action: Syntax must follow: [column:[operator:]]value;[column:[operator:]value]
Level: 1

Type: ERROR

Impact: Other

WCS-49013: Search parameter must follow [column:[operator:]]value;[column:[operator:]value] syntax

Cause: Search parameter syntax not understood.

Action: Syntax must follow: [column:[operator:]]value;[column:[operator:]value]
Level: 1

Type: ERROR

Impact: Other

WCS-49014: Comparator [{0}] is invalid

Cause: Invalid search comparator.

Action: Use valid search comparator.
Level: 1

Type: ERROR

Impact: Other

WCS-49014: Comparator [{0}] is invalid

Cause: Invalid search comparator.

Action: Use valid search comparator.
Level: 1

Type: ERROR

Impact: Other

WCS-49015: MetaColumn [{0}] is a required field, and cannot be set to null

Cause: Missing required field.

Action: Make sure required field is present.
Level: 1

Type: ERROR

Impact: Other

WCS-49015: MetaColumn [{0}] is a required field, and cannot be set to null

Cause: Missing required field.

Action: Make sure required field is present.
Level: 1

Type: ERROR

Impact: Other

WCS-49016: Invalid ''row'' data in the request body [{0}]

Cause: Invalid row data was found in the request body.

Action: Make sure valid row data is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49016: Invalid ''row'' data in the request body [{0}]

Cause: Invalid row data was found in the request body.

Action: Make sure valid row data is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49017: Portal name not found [{0}]

Cause: Portal name not found.

Action: Please specify a valid portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49017: Portal name not found [{0}]

Cause: Portal name not found.

Action: Please specify a valid portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49018: Portal name not found for GUID [{0}]

Cause: Portal name GUID not found.

Action: Please specify a valid portal name GUID.
Level: 1

Type: ERROR

Impact: Other

WCS-49018: Portal name not found for GUID [{0}]

Cause: Portal name GUID not found.

Action: Please specify a valid portal name GUID.
Level: 1

Type: ERROR

Impact: Other

WCS-49101: Injectable Service provider did not set forum service

Cause: Injectable Service provider could not find the forum service.

Action: Make sure Forum Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49101: Injectable Service provider did not set forum service

Cause: Injectable Service provider could not find the forum service.

Action: Make sure Forum Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49102: Can't establish Forum Session

Cause: Injectable Service provider could not establish a Forum Session.

Action: Make sure Jive Forum is configured and running and/or you have a valid user session established. Re-authenticating may help.
Level: 1

Type: ERROR

Impact: Other

WCS-49102: Can't establish Forum Session

Cause: Injectable Service provider could not establish a Forum Session.

Action: Make sure Jive Forum is configured and running and/or you have a valid user session established. Re-authenticating may help.
Level: 1

Type: ERROR

Impact: Other

WCS-49103: Forum id not found [{0}]

Cause: Forum not found.

Action: Please specify a valid forum.
Level: 1

Type: ERROR

Impact: Other

WCS-49103: Forum id not found [{0}]

Cause: Forum not found.

Action: Please specify a valid forum.
Level: 1

Type: ERROR

Impact: Other

WCS-49104: Portal name not found [{0}]

Cause: Portal name not found.

Action: Please specify a valid portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49104: Portal name not found [{0}]

Cause: Portal name not found.

Action: Please specify a valid portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49105: All resources require a name.

Cause: Resource name required.

Action: Please specify a resource name in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49105: All resources require a name.

Cause: Resource name required.

Action: Please specify a resource name in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49106: Topic id not found [{0}]

Cause: Topic not found.

Action: Please specify a valid topic.
Level: 1

Type: ERROR

Impact: Other

WCS-49106: Topic id not found [{0}]

Cause: Topic not found.

Action: Please specify a valid topic.
Level: 1

Type: ERROR

Impact: Other

WCS-49201: Injectable Service provider did not set Spaces service

Cause: Injectable Service provider could not find Space the service.

Action: Make sure Space Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49201: Injectable Service provider did not set Spaces service

Cause: Injectable Service provider could not find Space the service.

Action: Make sure Space Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49202: Portal id is null

Cause: Portal ID was not specified in request.

Action: Make sure Portal ID is specified in request.
Level: 1

Type: ERROR

Impact: Other

WCS-49202: Portal id is null

Cause: Portal ID was not specified in request.

Action: Make sure Portal ID is specified in request.
Level: 1

Type: ERROR

Impact: Other

WCS-49203: No 'document' in the request body

Cause: Portal document data was not found in the request body.

Action: Make sure Portal document is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49203: No 'document' in the request body

Cause: Portal document data was not found in the request body.

Action: Make sure Portal document is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49204: Portal name not found [{0}]

Cause: Portal name not found.

Action: Please specify a valid portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49204: Portal name not found [{0}]

Cause: Portal name not found.

Action: Please specify a valid portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49205: Members not found for portal [{0}]

Cause: No Members found.

Action: Please specify a portal with members.
Level: 1

Type: ERROR

Impact: Other

WCS-49205: Members not found for portal [{0}]

Cause: No Members found.

Action: Please specify a portal with members.
Level: 1

Type: ERROR

Impact: Other

WCS-49206: Member [{0}] not found in portal [{1}]

Cause: Member not found.

Action: Please specify a different member or portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49206: Member [{0}] not found in portal [{1}]

Cause: Member not found.

Action: Please specify a different member or portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49207: Attributes not found in portal [{0}]

Cause: Attributes not found.

Action: Please specify a different portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49207: Attributes not found in portal [{0}]

Cause: Attributes not found.

Action: Please specify a different portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49208: Attribute name [{0}] not found in portal [{1}]

Cause: Attribute name not found.

Action: Please specify a different Attribute name or portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49208: Attribute name [{0}] not found in portal [{1}]

Cause: Attribute name not found.

Action: Please specify a different Attribute name or portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49209: Portal params [{0}] and [{1}] result in exception

Cause: General exception.

Action: Please specify a different set of parameters.
Level: 1

Type: ERROR

Impact: Other

WCS-49209: Portal params [{0}] and [{1}] result in exception

Cause: General exception.

Action: Please specify a different set of parameters.
Level: 1

Type: ERROR

Impact: Other

WCS-49210: Attempted operation resulted in security exception

Cause: Insufficient authorization.

Action: Contact portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-49210: Attempted operation resulted in security exception

Cause: Insufficient authorization.

Action: Contact portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-49211: Retrieving Portal failed due to service unavailability

Cause: Service unaccessible.

Action: Contact portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-49211: Retrieving Portal failed due to service unavailability

Cause: Service unaccessible.

Action: Contact portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-49212: Failed to retrieve document repository info for portal.

Cause: Unknown document repository error.

Action: Contact portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-49212: Failed to retrieve document repository info for portal.

Cause: Unknown document repository error.

Action: Contact portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-49213: No Portal provided in body.

Cause: Portal was not provided in POST body of request.

Action: Provide Portal in POST body of request.
Level: 1

Type: ERROR

Impact: Other

WCS-49213: No Portal provided in body.

Cause: Portal was not provided in POST body of request.

Action: Provide Portal in POST body of request.
Level: 1

Type: ERROR

Impact: Other

WCS-49214: Portal template name not specified.

Cause: No portal template name was specified in POST body of request.

Action: Please specify a portal template name.
Level: 1

Type: ERROR

Impact: Other

WCS-49214: Portal template name not specified.

Cause: No portal template name was specified in POST body of request.

Action: Please specify a portal template name.
Level: 1

Type: ERROR

Impact: Other

WCS-49215: Portal name not specified.

Cause: No portal name was specified in POST body of request.

Action: Please specify a portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49215: Portal name not specified.

Cause: No portal name was specified in POST body of request.

Action: Please specify a portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49216: Unable to create Portal.

Cause: Internal error creating Portal.

Action: Contact portal administrator and/or see logs for additional errors.
Level: 1

Type: ERROR

Impact: Other

WCS-49216: Unable to create Portal.

Cause: Internal error creating Portal.

Action: Contact portal administrator and/or see logs for additional errors.
Level: 1

Type: ERROR

Impact: Other

WCS-49217: No Member provided in body.

Cause: Member was not provided in POST body of request.

Action: Provide Member in POST body of request.
Level: 1

Type: ERROR

Impact: Other

WCS-49217: No Member provided in body.

Cause: Member was not provided in POST body of request.

Action: Provide Member in POST body of request.
Level: 1

Type: ERROR

Impact: Other

WCS-49218: Member name not specified.

Cause: No member name was specified in POST body of request.

Action: Please specify a member name.
Level: 1

Type: ERROR

Impact: Other

WCS-49218: Member name not specified.

Cause: No member name was specified in POST body of request.

Action: Please specify a member name.
Level: 1

Type: ERROR

Impact: Other

WCS-49219: Role name not specified.

Cause: No role name was specified in POST body of request.

Action: Please specify a role name.
Level: 1

Type: ERROR

Impact: Other

WCS-49219: Role name not specified.

Cause: No role name was specified in POST body of request.

Action: Please specify a role name.
Level: 1

Type: ERROR

Impact: Other

WCS-49220: Retrieving Portal Assets failed due to service unavailability

Cause: Service unaccessible.

Action: Contact portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-49220: Retrieving Portal Assets failed due to service unavailability

Cause: Service unaccessible.

Action: Contact portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-49221: Injectable Service provider did not set Asset Lifecycle service

Cause: Injectable Service provider could not find Asset Lifecycle the service.

Action: Make sure Asset Lifecycle Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49222: Portal name specified for asset publishing not found : {0}

Cause: Portal name not found.

Action: Specify a valid portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49223: Archive for asset upload has not been provided

Cause: Asset archive for upload not provided.

Action: Specify an asset archive for upload.
Level: 1

Type: ERROR

Impact: Other

WCS-49224: Asset archive is invalid : {0}

Cause: Asset archive files or content is not packaged properly.

Action: Include a valid asset archive. See associated message for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-49225: Portal template not found with the name not specified.

Cause: No portal template was found corresponding to the name specified in POST body of request.

Action: Please specify an existing portal template name.
Level: 1

Type: ERROR

Impact: Other

WCS-49251: REST API Injectable Service provider did not set message board service.

Cause: REST API Injectable Service provider did not set message board service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49251: REST API Injectable Service provider did not set message board service.

Cause: REST API Injectable Service provider did not set message board service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49252: No 'message' in the request body

Cause: Message data was not found in the request body.

Action: Make sure Message data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49252: No 'message' in the request body

Cause: Message data was not found in the request body.

Action: Make sure Message data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49253: Message body not specified

Cause: No 'message' in the body when trying to create a new message.

Action: Specify a valid message body that is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49253: Message body not specified

Cause: No 'message' in the body when trying to create a new message.

Action: Specify a valid message body that is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49254: 'id' should not be supplied with a POST -- use PUT if you want to update

Cause: 'id' should not be supplied with a POST.

Action: Use PUT if you want to update.
Level: 1

Type: WARNING

Impact: Other

WCS-49254: 'id' should not be supplied with a POST -- use PUT if you want to update

Cause: 'id' should not be supplied with a POST.

Action: Use PUT if you want to update.
Level: 1

Type: WARNING

Impact: Other

WCS-49255: Error accessing profile for user with GUID {0}. Ignoring.

Cause: Error retrieving user profile.

Action: Verify that the user GUID is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49255: Error accessing profile for user with GUID {0}. Ignoring.

Cause: Error retrieving user profile.

Action: Verify that the user GUID is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49256: Permissions class called with wrong number of resource IDs. Expecting 2 or 3, but got {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49256: Permissions class called with wrong number of resource IDs. Expecting 2 or 3, but got {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49257: Error accessing user or portal message board {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49257: Error accessing user or portal message board {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49258: Error accessing message {0} from user or portal message board {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49258: Error accessing message {0} from user or portal message board {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49259: Error retrieving messages {0} to {1} from user or portal message board {2}.

Cause: Error retrieving message from user's message board.

Action: Check startIndex and itemsPerPage.
Level: 1

Type: ERROR

Impact: Other

WCS-49259: Error retrieving messages {0} to {1} from user or portal message board {2}.

Cause: Error retrieving message from user's message board.

Action: Check startIndex and itemsPerPage.
Level: 1

Type: ERROR

Impact: Other

WCS-49260: Error trying to delete message {0} from message board for user or portal {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49260: Error trying to delete message {0} from message board for user or portal {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49261: Error trying to create message on message board for user or portal {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49261: Error trying to create message on message board for user or portal {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49262: Invalid message board type. Got ''{0}'', expected ''person'' or ''space''.

Cause: Invalid message board type in URI.

Action: Verify that the message board type is either 'person' or 'space'.
Level: 1

Type: ERROR

Impact: Other

WCS-49262: Invalid message board type. Got ''{0}'', expected ''person'' or ''space''.

Cause: Invalid message board type in URI.

Action: Verify that the message board type is either 'person' or 'space'.
Level: 1

Type: ERROR

Impact: Other

WCS-49263: Invalid message type. Got ''{0}'', expected ''private'', ''public'', ''hidden'', ''private_hidden''.

Cause: Invalid message type in URI.

Action: Verify that the message type is either 'private', 'public', hidden' or 'private_hidden'.
Level: 1

Type: ERROR

Impact: Other

WCS-49263: Invalid message type. Got ''{0}'', expected ''private'' or ''public''.

Cause: Invalid message type in URI.

Action: Verify that the message type is either 'private' or 'public'.
Level: 1

Type: ERROR

Impact: Other

WCS-49264: Message type ''{0}'' not supported with message board type ''{1}''.

Cause: Invalid message type in URI.

Action: Verify that the message type is empty.
Level: 1

Type: ERROR

Impact: Other

WCS-49264: Message type ''{0}'' not supported with message board type ''{1}''.

Cause: Invalid message type in URI.

Action: Verify that the message type is empty.
Level: 1

Type: ERROR

Impact: Other

WCS-49265: Message type ''{0}'' not supported for users other than current user.

Cause: Invalid message type in URI.

Action: Verify that the message type is empty.
Level: 1

Type: ERROR

Impact: Other

WCS-49265: Message type ''{0}'' not supported for users other than current user.

Cause: Invalid message type in URI.

Action: Verify that the message type is empty.
Level: 1

Type: ERROR

Impact: Other

WCS-49301: REST API Injectable Service provider did not set profile service.

Cause: REST API Injectable Service provider did not set profile service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49301: REST API Injectable Service provider did not set profile service.

Cause: REST API Injectable Service provider did not set profile service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49302: Cannot delete a member from a list that the current user does not own.

Cause: Cannot delete a member from a list that the current user does not own.

Action: Make sure REST URL specifies the correct list and is accessing list for the current user.
Level: 1

Type: WARNING

Impact: Other

WCS-49302: Cannot delete a member from a list that the current user does not own.

Cause: Cannot delete a member from a list that the current user does not own.

Action: Make sure REST URL specifies the correct list and is accessing list for the current user.
Level: 1

Type: WARNING

Impact: Other

WCS-49303: Retrieving list names is only supported for current user. Found GUID {0}.

Cause: Retrieving list names is only supported for current user.

Action: Make sure REST URL specifies the current user GUID (or @me).
Level: 1

Type: WARNING

Impact: Other

WCS-49303: Retrieving list names is only supported for current user. Found GUID {0}.

Cause: Retrieving list names is only supported for current user.

Action: Make sure REST URL specifies the current user GUID (or @me).
Level: 1

Type: WARNING

Impact: Other

WCS-49304: Creating lists is only supported for the current user. Found GUID {0}.

Cause: Creating lists is only supported for current user.

Action: Make sure REST URL specifies the current user GUID (or @me).
Level: 1

Type: WARNING

Impact: Other

WCS-49304: Creating lists is only supported for the current user. Found GUID {0}.

Cause: Creating lists is only supported for current user.

Action: Make sure REST URL specifies the current user GUID (or @me).
Level: 1

Type: WARNING

Impact: Other

WCS-49305: No 'list' in the request body

Cause: List data was not found in the request body.

Action: Make sure List data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49305: No 'list' in the request body

Cause: List data was not found in the request body.

Action: Make sure List data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49306: List name not specified

Cause: No 'name' in the body when trying to create a new list.

Action: Specify a valid list name that is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49306: List name not specified

Cause: No 'name' in the body when trying to create a new list.

Action: Specify a valid list name that is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49307: Creating connections is only supported for the current user. Found GUID {0}.

Cause: Creating connections is only supported for current user.

Action: Make sure REST URL specifies the current user GUID (or @me).
Level: 1

Type: WARNING

Impact: Other

WCS-49307: Creating connections is only supported for the current user. Found GUID {0}.

Cause: Creating connections is only supported for current user.

Action: Make sure REST URL specifies the current user GUID (or @me).
Level: 1

Type: WARNING

Impact: Other

WCS-49308: No 'member' in the request body

Cause: Member data was not found in the request body.

Action: Make sure member data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49308: No 'member' in the request body

Cause: Member data was not found in the request body.

Action: Make sure member data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49309: Connection GUID not specified

Cause: No 'guid' in the body when trying to create a new connection.

Action: Specify a valid user GUID that is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49309: Connection GUID not specified

Cause: No 'guid' in the body when trying to create a new connection.

Action: Specify a valid user GUID that is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49310: Only connection lists can be deleted, and only by the current user. Found GUID {0} and list ID {1}.

Cause: Only connection lists can be deleted, not the current user or the intrinsic connections list. They can only be deleted by the current user.

Action: Make sure REST URL specifies the connection list ID, not @self or @connections, and is accessing the current user.
Level: 1

Type: WARNING

Impact: Other

WCS-49310: Only connection lists can be deleted, and only by the current user. Found GUID {0} and list ID {1}.

Cause: Only connection lists can be deleted, not the current user or the intrinsic connections list. They can only be deleted by the current user.

Action: Make sure REST URL specifies the connection list ID, not @self or @connections, and is accessing the current user.
Level: 1

Type: WARNING

Impact: Other

WCS-49311: Accessing status is only supported for @self id. Found selector {0}.

Cause: Accessing status is only supported for @self id.

Action: Make sure REST URL specifies the @self selector.
Level: 1

Type: WARNING

Impact: Other

WCS-49311: Accessing status is only supported for @self id. Found selector {0}.

Cause: Accessing status is only supported for @self id.

Action: Make sure REST URL specifies the @self selector.
Level: 1

Type: WARNING

Impact: Other

WCS-49312: Updating status is only supported for the current user. Found GUID {0}.

Cause: Accessing status is only supported for the current user.

Action: Make sure REST URL is accessing the current user.
Level: 1

Type: WARNING

Impact: Other

WCS-49312: Updating status is only supported for the current user. Found GUID {0}.

Cause: Accessing status is only supported for the current user.

Action: Make sure REST URL is accessing the current user.
Level: 1

Type: WARNING

Impact: Other

WCS-49313: Error trying to access profile for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49313: Error trying to access profile for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49314: Error checking for people permissions. Wrong number of arguments. Expected 1-3, but found {0} for permission {1}. Ignoring.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49314: Error checking for people permissions. Wrong number of arguments. Expected 1-3, but found {0} for permission {1}. Ignoring.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49315: Error checking for people permissions. Could not parse type {0}. Expected: person, status, lists, list, member. Ignoring.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49315: Error checking for people permissions. Could not parse type {0}. Expected: person, status, lists, list, member. Ignoring.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49316: Error trying to access connection lists for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49316: Error trying to access connection lists for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49317: Error accessing connection list {0}.

Cause: Error accessing connection list.

Action: Verify that the list ID is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49317: Error accessing connection list {0}.

Cause: Error accessing connection list.

Action: Verify that the list ID is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49318: Error accessing connection relationship of user {0} to current user {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49318: Error accessing connection relationship of user {0} to current user {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49319: Error adding/deleting user {0} for list {1} of current user.

Cause: Error adding/deleting user in connection list of current user.

Action: Verify that the list ID is correct and is not @CONNECTIONS (use invitations instead) and the user GUID is correct, and that the user is not already a member of the list when adding user.
Level: 1

Type: WARNING

Impact: Other

WCS-49319: Error adding/deleting user {0} for list {1} of current user.

Cause: Error adding/deleting user in connection list of current user.

Action: Verify that the list ID is correct and is not @CONNECTIONS (use invitations instead) and the user GUID is correct, and that the user is not already a member of the list when adding user.
Level: 1

Type: WARNING

Impact: Other

WCS-49320: "Error using Resource Action Handler to get link to user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49320: "Error using Resource Action Handler to get link to user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49321: Invalid user search query {0}. Unable to process search. Verify that the search query is of the form [loginid:equals:X] or [guid:equals:Y].

Cause: Invalid search query was passed into People REST API.

Action: Verify that the search query is of the form [loginid:equals:X] or [guid:equals:Y].
Level: 1

Type: WARNING

Impact: Other

WCS-49321: Invalid user search query {0}. Unable to process search. Verify that the search query is of the form [loginid:equals:X] or [guid:equals:Y].

Cause: Invalid search query was passed into People REST API.

Action: Verify that the search query is of the form [loginid:equals:X] or [guid:equals:Y].
Level: 1

Type: WARNING

Impact: Other

WCS-49322: Error accessing connection list {0} for user {1}.

Cause: Error accessing connection list.

Action: Verify that the list ID and GUID are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49322: Error accessing connection list {0} for user {1}.

Cause: Error accessing connection list.

Action: Verify that the list ID and GUID are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49323: Invalid invitation search query {0}. Unable to process search. Verify that the search query is either [invitor:equals:@me] or [invitee:equals:@me].

Cause: Invalid search query was passed into People Invitations REST API.

Action: Verify that the search query is either [invitor:equals:@me] or [invitee:equals:@me].
Level: 1

Type: WARNING

Impact: Other

WCS-49323: Invalid invitation search query {0}. Unable to process search. Verify that the search query is either [invitor:equals:@me] or [invitee:equals:@me].

Cause: Invalid search query was passed into People Invitations REST API.

Action: Verify that the search query is either [invitor:equals:@me] or [invitee:equals:@me].
Level: 1

Type: WARNING

Impact: Other

WCS-49324: No 'invitation' in the request body

Cause: Invitation data was not found in the request body when trying to create a new invitation.

Action: Make sure Invitation data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49324: No 'invitation' in the request body

Cause: Invitation data was not found in the request body when trying to create a new invitation.

Action: Make sure Invitation data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49325: Invitation invitee GUID not specified

Cause: No 'invitee' item or 'guid' item in 'invitee' in the body when trying to create a new invitation.

Action: Specify a valid invitee user GUID that is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49325: Invitation invitee GUID not specified

Cause: No 'invitee' item or 'guid' item in 'invitee' in the body when trying to create a new invitation.

Action: Specify a valid invitee user GUID that is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49326: Error retrieving invitations for current user.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49326: Error retrieving invitations for current user.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49327: Error inviting user {0} to be a connection of the current user

Cause: Error inviting user {0} to be a connection of the current user.

Action: Verify the invitee user GUID is correct and is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49327: Error inviting user {0} to be a connection of the current user

Cause: Error inviting user {0} to be a connection of the current user.

Action: Verify the invitee user GUID is correct and is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49328: The invitation ID in the request body ({0}) did not match the ID in the query string ({1})

Cause: The invitation ID in the request body did not match the ID in the query string when trying to update invitation status.

Action: Make sure the invitation ID specified in the request body matches the invitation ID in the query string.
Level: 1

Type: WARNING

Impact: Other

WCS-49328: The invitation ID in the request body ({0}) did not match the ID in the query string ({1})

Cause: The invitation ID in the request body did not match the ID in the query string when trying to update invitation status.

Action: Make sure the invitation ID specified in the request body matches the invitation ID in the query string.
Level: 1

Type: WARNING

Impact: Other

WCS-49329: Error deleting invitation {0}

Cause: Error deleting invitation {0}.

Action: Verify the invitation ID is correct, and that the current user has permissions to delete the invitation (i.e. created or received it).
Level: 1

Type: WARNING

Impact: Other

WCS-49329: Error deleting invitation {0}

Cause: Error deleting invitation {0}.

Action: Verify the invitation ID is correct, and that the current user has permissions to delete the invitation (i.e. created or received it).
Level: 1

Type: WARNING

Impact: Other

WCS-49330: Unable to update invitation {0} with status {1}. Verify that the invitation id is valid, the current user has permission to update the invitation, and that the status is either "accepted" or "ignored".

Cause: Unable to update invitation status.

Action: Verify that the invitation id is valid, the current user has permission to update the invitation, and that the status is either "accepted" or "ignored".
Level: 1

Type: WARNING

Impact: Other

WCS-49330: Unable to update invitation {0} with status {1}. Verify that the invitation id is valid, the current user has permission to update the invitation, and that the status is either "accepted" or "ignored".

Cause: Unable to update invitation status.

Action: Verify that the invitation id is valid, the current user has permission to update the invitation, and that the status is either "accepted" or "ignored".
Level: 1

Type: WARNING

Impact: Other

WCS-49331: Error inviting user {0} to be a connection of current user.

Cause: Error inviting user to be a connection of current user.

Action: Verify that the user GUID is correct, and that the user has not already been invited by the current user.
Level: 1

Type: WARNING

Impact: Other

WCS-49331: Error inviting user {0} to be a connection of current user.

Cause: Error inviting user to be a connection of current user.

Action: Verify that the user GUID is correct, and that the user has not already been invited by the current user.
Level: 1

Type: WARNING

Impact: Other

WCS-49332: Error accessing relationship information for connections and invitations of current user.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49332: Error accessing relationship information for connections and invitations of current user.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49333: Unable to lookup email address {0}.

Cause: Unable to lookup email address.

Action: Make sure the email address is correct, and the identity store is configure properly.
Level: 1

Type: WARNING

Impact: Other

WCS-49333: Unable to lookup email address {0}.

Cause: Unable to lookup email address.

Action: Make sure the email address is correct, and the identity store is configure properly.
Level: 1

Type: WARNING

Impact: Other

WCS-49334: Error creating connection list {0}. List already exists.

Cause: Error creating connection list. List already exists.

Action: Choose a new name for the new connection list.
Level: 1

Type: WARNING

Impact: Other

WCS-49334: Error creating connection list {0}. List already exists.

Cause: Error creating connection list. List already exists.

Action: Choose a new name for the new connection list.
Level: 1

Type: WARNING

Impact: Other

WCS-49351: REST API Injectable Service provider did not set activity service.

Cause: REST API Injectable Service provider did not set activity service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49351: REST API Injectable Service provider did not set activity service.

Cause: REST API Injectable Service provider did not set activity service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49352: No 'activity' in the request body

Cause: Activity data was not found in the request body.

Action: Make sure Activity data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49352: No 'activity' in the request body

Cause: Activity data was not found in the request body.

Action: Make sure Activity data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49353: 'id' should not be supplied with a POST -- use PUT if you want to update

Cause: 'id' should not be supplied with a POST.

Action: Use PUT if you want to update.
Level: 1

Type: WARNING

Impact: Other

WCS-49353: 'id' should not be supplied with a POST -- use PUT if you want to update

Cause: 'id' should not be supplied with a POST.

Action: Use PUT if you want to update.
Level: 1

Type: WARNING

Impact: Other

WCS-49354: Creating activities requires the service ID and activity type to be present.

Cause: Creating activities requires the service ID and activity type.

Action: Make sure the activity POST contains the service ID and activity type.
Level: 1

Type: WARNING

Impact: Other

WCS-49354: Creating activities requires the service ID and activity type to be present.

Cause: Creating activities requires the service ID and activity type.

Action: Make sure the activity POST contains the service ID and activity type.
Level: 1

Type: WARNING

Impact: Other

WCS-49355: Error accessing activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49355: Error accessing activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49356: Error accessing activities for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49356: Error accessing activities for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49357: Error accessing activities for Portal {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49357: Error accessing activities for Portal {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49358: Error trying to access profile for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49358: Error trying to access profile for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49359: Unable to retrieve object type for parameter object {0} in activity {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49359: Unable to retrieve object type for parameter object {0} in activity {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49360: Unable to retrieve object with index {0} for parameter object {1} in activity {2}, because there are only {3} objects available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49360: Unable to retrieve object with index {0} for parameter object {1} in activity {2}, because there are only {3} objects available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49361: Unable to parse key {0}, activity type {1}, service id {2}, activity id {3} for activity parameter. Should be of form ''{actor[n]''} or ''{object[n]''}.

Cause: Unable to parse key for activity parameter.

Action: Make sure key starts with actor or object and the index is numeric.
Level: 1

Type: WARNING

Impact: Other

WCS-49361: Unable to parse key {0}, activity type {1}, service id {2}, activity id {3} for activity parameter. Should be of form ''{actor[n]''} or ''{object[n]''}.

Cause: Unable to parse key for activity parameter.

Action: Make sure key starts with actor or object and the index is numeric.
Level: 1

Type: WARNING

Impact: Other

WCS-49362: Unable to find Portal scope for {0}.

Cause: Unable to find Portal scope from specified value.

Action: Make sure Portal value is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49362: Unable to find Portal scope for {0}.

Cause: Unable to find Portal scope from specified value.

Action: Make sure Portal value is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49363: Unable to publish activity for service {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49363: Unable to publish activity for service {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49364: Error accessing comments for object {2} with service id {0} and type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49364: Error accessing comments for object {2} with service id {0} and type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49365: Error creating comment for object {2} with service id {0} and type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49365: Error creating comment for object {2} with service id {0} and type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49366: Error deleting comment {0}.

Cause: Unable to delete comment.

Action: Make sure current user has permission to delete this comment.
Level: 1

Type: WARNING

Impact: Other

WCS-49366: Error deleting comment {0}.

Cause: Unable to delete comment.

Action: Make sure current user has permission to delete this comment.
Level: 1

Type: WARNING

Impact: Other

WCS-49367: Error accessing activity object with id {2} with service id {0} and type {1}.

Cause: Unable to access activity object.

Action: Make sure the service id, object type, and object id are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49367: Error accessing activity object with id {2} with service id {0} and type {1}.

Cause: Unable to access activity object.

Action: Make sure the service id, object type, and object id are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49368: Error accessing activity object details for object with id {2} with service id {0} and type {1}.

Cause: Unable to access activity object details.

Action: Make sure the service id, object type, and object id are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49368: Error accessing activity object details for object with id {2} with service id {0} and type {1}.

Cause: Unable to access activity object details.

Action: Make sure the service id, object type, and object id are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49369: Error accessing comments service.

Cause: Error accessing comments service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49369: Error accessing comments service.

Cause: Error accessing comments service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49370: REST API Injectable Service provider did not set comment service.

Cause: REST API Injectable Service provider did not set comment service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49370: REST API Injectable Service provider did not set comment service.

Cause: REST API Injectable Service provider did not set comment service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49371: No 'comment' in the request body

Cause: Comment data was not found in the request body.

Action: Make sure comment data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49371: No 'comment' in the request body

Cause: Comment data was not found in the request body.

Action: Make sure comment data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49372: Creating comments requires the comment text to be present.

Cause: Creating comments requires the comment text.

Action: Make sure the comment POST contains the comment text.
Level: 1

Type: WARNING

Impact: Other

WCS-49372: Creating comments requires the comment text to be present.

Cause: Creating comments requires the comment text.

Action: Make sure the comment POST contains the comment text.
Level: 1

Type: WARNING

Impact: Other

WCS-49373: Invalid data parameter ''{0}'' for activity. Must include ''data'', and may include ''commentsSummary'' and ''likesSummary''.

Cause: Invalid data parameter for activity.

Action: Make sure the data parameter includes 'data'. 'commentsSummary' and 'likesSummary' are optional.
Level: 1

Type: WARNING

Impact: Other

WCS-49373: Invalid data parameter ''{0}'' for activity. Must include ''data'', and may include ''commentsSummary'' and ''likesSummary''.

Cause: Invalid data parameter for activity.

Action: Make sure the data parameter includes 'data'. 'commentsSummary' and 'likesSummary' are optional.
Level: 1

Type: WARNING

Impact: Other

WCS-49374: Error accessing likes for object {2} with service id {0} and type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49374: Error accessing likes for object {2} with service id {0} and type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49375: Error creating like for object {2} with service id {0} and type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49375: Error creating like for object {2} with service id {0} and type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49376: Error deleting like {0}.

Cause: Unable to delete like.

Action: Make sure current user has permission to delete this like.
Level: 1

Type: WARNING

Impact: Other

WCS-49376: Error deleting like {0}.

Cause: Unable to delete like.

Action: Make sure current user has permission to delete this like.
Level: 1

Type: WARNING

Impact: Other

WCS-49377: Error accessing likes service.

Cause: Error accessing likes service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49377: Error accessing likes service.

Cause: Error accessing likes service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49378: REST API Injectable Service provider did not set like service.

Cause: REST API Injectable Service provider did not set like service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49378: REST API Injectable Service provider did not set like service.

Cause: REST API Injectable Service provider did not set like service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49379: No 'like' in the request body

Cause: Like data was not found in the request body.

Action: Make sure like data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49379: No 'like' in the request body

Cause: Like data was not found in the request body.

Action: Make sure like data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49380: Activity ID is null

Cause: Activity ID cannot be null.

Action: Use valid activity ID.
Level: 1

Type: WARNING

Impact: Other

WCS-49380: Activity ID is null

Cause: Activity ID cannot be null.

Action: Use valid activity ID.
Level: 1

Type: WARNING

Impact: Other

WCS-49382: Error accessing comments for activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49382: Error accessing comments for activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49383: Error creating comment for activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49383: Error creating comment for activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49384: Error creating like for activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49384: Error creating like for activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49385: Error accessing likes for activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49385: Error accessing likes for activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49386: User has insufficient permission to access object {2} with service id {0} and type {1}.

Cause: Unable to access the object due to permission settings.

Action: Make sure current user has permission to access this object.
Level: 1

Type: WARNING

Impact: Other

WCS-49386: User has insufficient permission to access object {2} with service id {0} and type {1}.

Cause: Unable to access the object due to permission settings.

Action: Make sure current user has permission to access this object.
Level: 1

Type: WARNING

Impact: Other

WCS-49387: User has insufficient permission to access activity {0}.

Cause: Unable to access the object due to permission settings.

Action: Make sure current user has permission to access this object.
Level: 1

Type: WARNING

Impact: Other

WCS-49387: User has insufficient permission to access activity {0}.

Cause: Unable to access the object due to permission settings.

Action: Make sure current user has permission to access this object.
Level: 1

Type: WARNING

Impact: Other

WCS-49388: User has insufficient permission to access object {2} with service id {0} and type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49388: User has insufficient permission to access object {2} with service id {0} and type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49389: User has insufficient permission to access activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49389: User has insufficient permission to access activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49390: Unable to parse date {0}. Make sure date format is yyyy-MM-dd.

Cause: Date format is not correct.

Action: Make sure date format is yyyy-MM-dd.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49401: REST API Injectable Service provider did not set feedback service.

Cause: REST API Injectable Service provider did not set feedback service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49401: REST API Injectable Service provider did not set feedback service.

Cause: REST API Injectable Service provider did not set feedback service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49402: No 'message' in the request body

Cause: Message data was not found in the request body.

Action: Make sure Message data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49402: No 'message' in the request body

Cause: Message data was not found in the request body.

Action: Make sure Message data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49403: Message body not specified

Cause: No 'message' in the body when trying to create a new feedback item.

Action: Specify a valid message body that is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49403: Message body not specified

Cause: No 'message' in the body when trying to create a new feedback item.

Action: Specify a valid message body that is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49404: 'id' should not be supplied with a POST -- use PUT if you want to update

Cause: 'id' should not be supplied with a POST.

Action: Use PUT if you want to update.
Level: 1

Type: WARNING

Impact: Other

WCS-49404: 'id' should not be supplied with a POST -- use PUT if you want to update

Cause: 'id' should not be supplied with a POST.

Action: Use PUT if you want to update.
Level: 1

Type: WARNING

Impact: Other

WCS-49405: Error retrieving display name from profile for user with GUID {0}. Ignoring.

Cause: Error retrieving user profile.

Action: Verify that the user GUID is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49405: Error retrieving display name from profile for user with GUID {0}. Ignoring.

Cause: Error retrieving user profile.

Action: Verify that the user GUID is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49406: Permissions class called with wrong number of resource IDs. Expecting 1 or 2, but got {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49406: Permissions class called with wrong number of resource IDs. Expecting 1 or 2, but got {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49407: Error accessing feedback for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49407: Error accessing feedback for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49408: Error accessing feedback item from user {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49408: Error accessing feedback item from user {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49409: Error retrieving received feedback items from {0} to {1} for user {2}.

Cause: Error retrieving received feedback for user.

Action: Check startIndex and itemsPerPage.
Level: 1

Type: ERROR

Impact: Other

WCS-49409: Error retrieving received feedback items from {0} to {1} for user {2}.

Cause: Error retrieving received feedback for user.

Action: Check startIndex and itemsPerPage.
Level: 1

Type: ERROR

Impact: Other

WCS-49410: Error retrieving given feedback items from user {0} for items {1} to {2}.

Cause: Error retrieving feedback for user.

Action: Check startIndex and itemsPerPage.
Level: 1

Type: ERROR

Impact: Other

WCS-49410: Error retrieving given feedback items from user {0} for items {1} to {2}.

Cause: Error retrieving feedback for user.

Action: Check startIndex and itemsPerPage.
Level: 1

Type: ERROR

Impact: Other

WCS-49411: Error trying to delete feedback {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49411: Error trying to delete feedback {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49412: Error trying to create feedback for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49412: Error trying to create feedback for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49413: Unable to find link {0} for feedback item {1}..

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49413: Unable to find link {0} for feedback item {1}..

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49414: Error trying to get feedback for user. Either unknown GUID {0} or unknown selector {1}.

Cause: Either an unknown GUID was entered, expected @me or GUID or unknown selector was entered, expected @self, @all, or valid GUID. Selector can only be a valid GUID if the {guid} value entered is @me or the GUID of the current logged in user.

Action: Double check the GUID or selector entered is valid.
Level: 1

Type: WARNING

Impact: Other

WCS-49414: Error trying to get feedback for user. Either unknown GUID {0} or unknown selector {1}.

Cause: Either an unknown GUID was entered, expected @me or GUID or unknown selector was entered, expected @self, @all, or valid GUID. Selector can only be a valid GUID if the {guid} value entered is @me or the GUID of the current logged in user.

Action: Double check the GUID or selector entered is valid.
Level: 1

Type: WARNING

Impact: Other

WCS-49415: No 'receivedUser' in the request body

Cause: The received user data was not found in the request body.

Action: Make sure the received user is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49415: No 'receivedUser' in the request body

Cause: The received user data was not found in the request body.

Action: Make sure the received user is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49416: Invalid selector for creating feedback. Expected ''@self'', but found ''{0}''.

Cause: Feedback can only be POSTed to a URI of the form {guid}/@self.

Action: Make sure the URI selector is @self.
Level: 1

Type: WARNING

Impact: Other

WCS-49416: Invalid selector for creating feedback. Expected ''@self'', but found ''{0}''.

Cause: Feedback can only be POSTed to a URI of the form {guid}/@self.

Action: Make sure the URI selector is @self.
Level: 1

Type: WARNING

Impact: Other

WCS-49417: GUID specified in URI and GUID specified in POST body do not match. URI GUID was ''{0}'', POST body received user GUID was ''{1}''.

Cause: GUID in URI and GUID specified in POST body received user GUID must match.

Action: Make sure the URI GUID and POST body received user GUID match.
Level: 1

Type: WARNING

Impact: Other

WCS-49417: GUID specified in URI and GUID specified in POST body do not match. URI GUID was ''{0}'', POST body received user GUID was ''{1}''.

Cause: GUID in URI and GUID specified in POST body received user GUID must match.

Action: Make sure the URI GUID and POST body received user GUID match.
Level: 1

Type: WARNING

Impact: Other

WCS-49451: Error trying to access profile for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49451: Error trying to access profile for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49452: The current DB version does not support this REST API. Expected version 11.1.1.2.0 or greater.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49452: The current DB version does not support this REST API. Expected version 11.1.1.2.0 or greater.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49453: Unable to use Resource Action Handler to get link to object with type {0} from service {1} and ID {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49453: Unable to use Resource Action Handler to get link to object with type {0} from service {1} and ID {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49454: The ''{0}'' parameter was not found in the query string, or was empty.

Cause: The query string was missing a required parameter.

Action: Make sure the specified parameter is present in the query string and is not empty.
Level: 1

Type: WARNING

Impact: Other

WCS-49454: The ''{0}'' parameter was not found in the query string, or was empty.

Cause: The query string was missing a required parameter.

Action: Make sure the specified parameter is present in the query string and is not empty.
Level: 1

Type: WARNING

Impact: Other

WCS-49455: The ''{0}'' date time parameter could not be parsed: ''{1}''

Cause: The query string date time parameter was not formatted correctly.

Action: Make sure the specified date time parameter is formatted according to the XSD spec: YYYY-MM-DD with optional time and timezone components hh:mm:ss, +HH:mm, -HH:mm, or Z. The time component may include milliseconds, but they will not be used.
Level: 1

Type: WARNING

Impact: Other

WCS-49455: The ''{0}'' date time parameter could not be parsed: ''{1}''

Cause: The query string date time parameter was not formatted correctly.

Action: Make sure the specified date time parameter is formatted according to the XSD spec: YYYY-MM-DD with optional time and timezone components Thh:mm:ss, +HH:mm, -HH:mm, or Z. The time component may include milliseconds, but they will not be used.
Level: 1

Type: WARNING

Impact: Other

WCS-49456: Unable to encode data for use in URI.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49456: Unable to encode data for use in URI.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49457: Unable to decode data from URI: {0}.

Cause: Unable to decode data from URI.

Action: Make sure the specified data is correctly URL encoded before being passed to the server.
Level: 1

Type: WARNING

Impact: Other

WCS-49457: Unable to decode data from URI: {0}.

Cause: Unable to decode data from URI.

Action: Make sure the specified data is correctly URL encoded before being passed to the server.
Level: 1

Type: WARNING

Impact: Other

WCS-49458: A query string parameter was set to the default value of ''{0}'', which is a default template parameter, not a valid value.

Cause: A query string parameter was set to a default template parameter value with a starting '{ and ending '}, which is not a valid value.

Action: Make sure the query string parameter is either set to a valid value, or removed.
Level: 1

Type: WARNING

Impact: Other

WCS-49458: A query string parameter was set to the default value of ''{0}'', which is a default template parameter, not a valid value.

Cause: A query string parameter was set to a default template parameter value with a starting '{ and ending '}, which is not a valid value.

Action: Make sure the query string parameter is either set to a valid value, or removed.
Level: 1

Type: WARNING

Impact: Other

WCS-49459: Secure Enterprise Search is not configured.

Cause: SES Crawl is not enabled for this instance

Action: Make sure crawl is enabled for Documents, Forums, and Portals sources
Level: 1

Type: WARNING

Impact: Other

WCS-49459: Secure Enterprise Search is not configured.

Cause: SES Crawl is not enabled for this instance

Action: Make sure crawl is enabled for Documents, Forums, and Portals sources
Level: 1

Type: WARNING

Impact: Other

WCS-49460: This Secure Enterprise Search version is not supporting facets.

Cause: SES Version is not supporting faceted queries

Action: Make sure to use the SES version that supports faceted serch
Level: 1

Type: WARNING

Impact: Other

WCS-49460: This Secure Enterprise Search version is not supporting facets.

Cause: SES Version is not supporting faceted queries

Action: Make sure to use the SES version that supports faceted serch
Level: 1

Type: WARNING

Impact: Other

WCS-49461: No UriService is available for the REST resource {0}.

Cause: No UriService is available for the REST resource.

Action: Make sure the REST resource is correctly configured and annotated.
Level: 1

Type: ERROR

Impact: Other

WCS-49501: Injectable Service provider did not set search service

Cause: Injectable Service provider could not find the search service.

Action: Make sure Search Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49501: Injectable Service provider did not set search service

Cause: Injectable Service provider could not find the search service.

Action: Make sure Search Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49509: Column could not be found for column id [{0}]

Cause: Column ID was not found.

Action: Make sure Column ID exists.
Level: 1

Type: ERROR

Impact: Other

WCS-49509: Column could not be found for column id [{0}]

Cause: Column ID was not found.

Action: Make sure Column ID exists.
Level: 1

Type: ERROR

Impact: Other

WCS-49513: Search parameter must follow [column:[operator:]]value;[column:[operator:]value] syntax

Cause: Search parameter syntax not understood.

Action: Syntax must follow: [column:[operator:]]value;[column:[operator:]value]
Level: 1

Type: ERROR

Impact: Other

WCS-49513: Search parameter must follow [column:[operator:]]value;[column:[operator:]value] syntax

Cause: Search parameter syntax not understood.

Action: Syntax must follow: [column:[operator:]]value;[column:[operator:]value]
Level: 1

Type: ERROR

Impact: Other

WCS-49514: Search parameter must follow [column:[operator:]]value;[column:[operator:]value] syntax

Cause: Search parameter syntax not understood.

Action: Syntax must follow: [column:[operator:]]value;[column:[operator:]value]
Level: 1

Type: ERROR

Impact: Other

WCS-49514: Search parameter must follow [column:[operator:]]value;[column:[operator:]value] syntax

Cause: Search parameter syntax not understood.

Action: Syntax must follow: [column:[operator:]]value;[column:[operator:]value]
Level: 1

Type: ERROR

Impact: Other

WCS-49515: Comparator [{0}] is invalid

Cause: Invalid search comparator.

Action: Use valid search comparator.
Level: 1

Type: ERROR

Impact: Other

WCS-49515: Comparator [{0}] is invalid

Cause: Invalid search comparator.

Action: Use valid search comparator.
Level: 1

Type: ERROR

Impact: Other

WCS-49516: Invalid argument: [{0}]

Cause: Invalid search argument.

Action: Use valid search argument.
Level: 1

Type: ERROR

Impact: Other

WCS-49516: Invalid argument: [{0}]

Cause: Invalid search argument.

Action: Use valid search argument.
Level: 1

Type: ERROR

Impact: Other

WCS-49517: Internal Search Error: [{0}]

Cause: Internal search error.

Action: Please see error on server console.
Level: 1

Type: ERROR

Impact: Other

WCS-49517: Internal Search Error: [{0}]

Cause: Internal search error.

Action: Please see error on server console.
Level: 1

Type: ERROR

Impact: Other

WCS-49551: REST API Injectable Service provider did not set event service.

Cause: REST API Injectable Service provider did not set event service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49551: REST API Injectable Service provider did not set event service.

Cause: REST API Injectable Service provider did not set event service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49552: Unable to find Portal scope for {0}.

Cause: Unable to find Portal scope from specified value.

Action: Make sure Portal value is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49552: Unable to find Portal scope for {0}.

Cause: Unable to find Portal scope from specified value.

Action: Make sure Portal value is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49553: Unable to access calendar for scope {0}.

Cause: Unable to access requested calendar.

Action: Make sure the scope value is a valid Portal GUID.
Level: 1

Type: WARNING

Impact: Other

WCS-49553: Unable to access calendar for scope {0}.

Cause: Unable to access requested calendar.

Action: Make sure the scope value is a valid Portal GUID.
Level: 1

Type: WARNING

Impact: Other

WCS-49554: Unable to access event {0} in Portal scope {1}.

Cause: Unable to access Portal event.

Action: Make sure Portal and event ID values are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49554: Unable to access event {0} in Portal scope {1}.

Cause: Unable to access Portal event.

Action: Make sure Portal and event ID values are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49555: Unable to create event in Portal scope {1}.

Cause: Unable to create Portal event.

Action: Make sure the Portal ID is correct and the current user has permission to create an event in that Portal.
Level: 1

Type: WARNING

Impact: Other

WCS-49555: Unable to create event in Portal scope {1}.

Cause: Unable to create Portal event.

Action: Make sure the Portal ID is correct and the current user has permission to create an event in that Portal.
Level: 1

Type: WARNING

Impact: Other

WCS-49556: Unable to update event {0} in Portal scope {1}.

Cause: Unable to update Portal event.

Action: Make sure Portal and event ID values are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49556: Unable to update event {0} in Portal scope {1}.

Cause: Unable to update Portal event.

Action: Make sure Portal and event ID values are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49557: Unable to delete event {0} in Portal scope {1}.

Cause: Unable to delete Portal event.

Action: Make sure Portal and event ID values are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49557: Unable to delete event {0} in Portal scope {1}.

Cause: Unable to delete Portal event.

Action: Make sure Portal and event ID values are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49558: No 'event' in the request body.

Cause: Event data was not found in the request body.

Action: Make sure Event data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49558: No 'event' in the request body.

Cause: Event data was not found in the request body.

Action: Make sure Event data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49559: Event POST or PUT request bodies cannot contain the ID, author, created date, modifier, modified date, or duration.

Cause: Event POST or PUT request bodies cannot contain the ID, author, created date, modifier, modified date, or duration.

Action: Make sure Event data does not contain the ID, author, created date, modifier, modified date, or duration in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49559: Event POST or PUT request bodies cannot contain the ID, author, created date, modifier, modified date, or duration.

Cause: Event POST or PUT request bodies cannot contain the ID, author, created date, modifier, modified date, or duration.

Action: Make sure Event data does not contain the ID, author, created date, modifier, modified date, or duration in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49560: The event object was missing required data. Events are required to have summary, startTime, and endTime data.

Cause: The event object was missing required data.

Action: Make sure Event summary, startTime, and endTime data are specified in the event object.
Level: 1

Type: WARNING

Impact: Other

WCS-49560: The event object was missing required data. Events are required to have summary, startTime, and endTime data.

Cause: The event object was missing required data.

Action: Make sure Event summary, startTime, and endTime data are specified in the event object.
Level: 1

Type: WARNING

Impact: Other

WCS-49561: Invalid portal GUID {0}.

Cause: This GUID does not refer to a valid portal.

Action: Make sure the portal GUID is not null or empty, and refers to a valid portal. Home Portal cannot be used for portal events.
Level: 1

Type: WARNING

Impact: Other

WCS-49561: Invalid portal GUID {0}.

Cause: This GUID does not refer to a valid portal.

Action: Make sure the portal GUID is not null or empty, and refers to a valid portal. Home Portal cannot be used for portal events.
Level: 1

Type: WARNING

Impact: Other

WCS-49562: Invalid time sequence: startTime {0} must be before endTime {1}..

Cause: The startTime must be before the endTime.

Action: Make sure the startTime is before the endTime.
Level: 1

Type: WARNING

Impact: Other

WCS-49562: Invalid time sequence: startTime {0} must be before endTime {1}..

Cause: The startTime must be before the endTime.

Action: Make sure the startTime is before the endTime.
Level: 1

Type: WARNING

Impact: Other

WCS-49563: Unable to access event categories for Portal scope {0}.

Cause: Unable to access Portal event categories.

Action: Make sure Portal guid is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49563: Unable to access event categories for Portal scope {0}.

Cause: Unable to access Portal event categories.

Action: Make sure Portal guid is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49564: Unable to create event category {0} in Portal scope {1}.

Cause: Unable to create Portal event category.

Action: Make sure the Portal ID is correct and the current user has permission to create an event category in that Portal.
Level: 1

Type: WARNING

Impact: Other

WCS-49564: Unable to create event category {0} in Portal scope {1}.

Cause: Unable to create Portal event category.

Action: Make sure the Portal ID is correct and the current user has permission to create an event category in that Portal.
Level: 1

Type: WARNING

Impact: Other

WCS-49565: Unable to delete event category {0} in Portal scope {1}.

Cause: Unable to delete Portal event category.

Action: Make sure Portal and event category name values are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49565: Unable to delete event category {0} in Portal scope {1}.

Cause: Unable to delete Portal event category.

Action: Make sure Portal and event category name values are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49601: Injectable Service provider did not set tagging service

Cause: Injectable Service provider could not find the tagging service.

Action: Make sure Tagging Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49601: Injectable Service provider did not set tagging service

Cause: Injectable Service provider could not find the tagging service.

Action: Make sure Tagging Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49613: Required query Parameter "{0}" was not found.

Cause: Query parameter "{0}" omitted or null.

Action: Query parameter "{0}" required. Please try again with a non-null value for this parameter
Level: 1

Type: ERROR

Impact: Other

WCS-49613: Required query Parameter "{0}" was not found.

Cause: Query parameter "{0}" ommmited or null.

Action: Query parameter "{0}" required. Please try again with a non-null value for this parameter
Level: 1

Type: ERROR

Impact: Other

WCS-49614: {1} Body must include "{0}" as a field. Could not complete POST Request.

Cause: {1} Body must include "{0}" as a field.

Action: Provide a complete {1} Object as the body for this request
Level: 1

Type: ERROR

Impact: Other

WCS-49614: {1} Body must include "{0}" as a field. Could not complete POST Request.

Cause: {1} Body must include "{0}" as a field.

Action: Provide a complete {1} Object as the body for this request
Level: 1

Type: ERROR

Impact: Other

WCS-49615: Tag {0} could not be deleted.

Cause: There was an error while deleting this item

Action: Please check if item exists and if you have the appropriate permissions to delete this item.
Level: 1

Type: ERROR

Impact: Other

WCS-49615: Tag {0} could not be deleted.

Cause: There was an error while deleting this item

Action: Please check if item exists and if you have the appropriate permissions to delete this item.
Level: 1

Type: ERROR

Impact: Other

WCS-49616: Item with service Id: {0} and resource id: {1} could not be deleted.

Cause: There was an error while deleting this item

Action: Please check if item exists and if you have the appropriate permissions to delete this item.
Level: 1

Type: ERROR

Impact: Other

WCS-49616: Item with service Id: {0} and resource id: {1} could not be deleted.

Cause: There was an error while deleting this item

Action: Please check if item exists and if you have the appropriate permissions to delete this item.
Level: 1

Type: ERROR

Impact: Other

WCS-49617: Item with service id: {0} and resource id: {1} is already tagged by you

Cause: There was an error while tagging this item

Action: Please check if item exists and if you have the appropriate permissions to tag this item.
Level: 1

Type: ERROR

Impact: Other

WCS-49617: Item with service id: {0} and resource id: {1} is already tagged by you

Cause: There was an error while tagging this item

Action: Please check if item exists and if you have the appropriate permissions to tag this item.
Level: 1

Type: ERROR

Impact: Other

WCS-49618: Item with service id: {0} and resource id: {1} was not found

Cause: There was an error while finding this item

Action: Please check if item exists and if you have the appropriate permissions to tag this item.
Level: 1

Type: ERROR

Impact: Other

WCS-49618: Item with service id: {0} and resource id: {1} was not found

Cause: There was an error while finding this item

Action: Please check if item exists and if you have the appropriate permissions to tag this item.
Level: 1

Type: ERROR

Impact: Other

WCS-49619: Tag {0} could not be found.

Cause: There was an error while finding this tag

Action: Please check if item exists and if you have the appropriate permissions to tag this item.
Level: 1

Type: ERROR

Impact: Other

WCS-49619: Tag {0} could not be found.

Cause: There was an error while finding this tag

Action: Please check if item exists and if you have the appropriate permissions to tag this item.
Level: 1

Type: ERROR

Impact: Other

WCS-49620: Required query Parameter "{0}" was not valid.

Cause: Query parameter "{0}" not valid.

Action: Query parameter "{0}" required. Please try again with a valid value for this parameter
Level: 1

Type: ERROR

Impact: Other

WCS-49620: Required query Parameter "{0}" was not valid.

Cause: Query parameter "{0}" not valid.

Action: Query parameter "{0}" required. Please try again with a valid value for this parameter
Level: 1

Type: ERROR

Impact: Other

WCS-49651: REST API Injectable Service provider did not set links service.

Cause: REST API Injectable Service provider did not set links service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49651: REST API Injectable Service provider did not set links service.

Cause: REST API Injectable Service provider did not set links service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49652: No 'source' in the request body

Cause: Links source object was not found in the request body.

Action: Make sure source object is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49652: No 'source' in the request body

Cause: Links source object was not found in the request body.

Action: Make sure source object is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49653: No 'target' in the request body

Cause: Links target object was not found in the request body.

Action: Make sure target object is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49653: No 'target' in the request body

Cause: Links target object was not found in the request body.

Action: Make sure target object is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49654: Error trying to create links.

Cause: Error trying to create links

Action: Make sure webcenter repository is available.
Level: 1

Type: ERROR

Impact: Other

WCS-49654: Error trying to create links.

Cause: Error trying to create links

Action: Make sure webcenter repository is available.
Level: 1

Type: ERROR

Impact: Other

WCS-49655: No 'link' in the request body

Cause: Link data was not found in the request body.

Action: Make sure Link data is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49655: No 'link' in the request body

Cause: Link data was not found in the request body.

Action: Make sure Link data is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49656: Unable to create link

Cause: Link was not created.

Action: See logs for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-49656: Unable to create link

Cause: Link was not created.

Action: See logs for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-49657: Source "serviceid" or "resourceid" not specified

Cause: No source "serviceid" or "resourceid" when trying to create a link.

Action: Specify valid "serviceid" and "resourceid" that are not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-49657: Source "serviceid" or "resourceid" not specified

Cause: No source "serviceid" or "resourceid" when trying to create a link.

Action: Specify valid "serviceid" and "resourceid" that are not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-49658: Target "serviceid" or "resourceid" not specified

Cause: No target "serviceid" or "resourceid" when trying to create a link.

Action: Specify valid "serviceid" and "resourceid" that are not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-49658: Target "serviceid" or "resourceid" not specified

Cause: No target "serviceid" or "resourceid" when trying to create a link.

Action: Specify valid "serviceid" and "resourceid" that are not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-49659: Attempted operation resulted in security exception

Cause: Insufficient authorization.

Action: Contact portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-49659: Attempted operation resulted in security exception

Cause: Insufficient authorization.

Action: Contact portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-49701: Injectable Service provider did not set recommendation service

Cause: Injectable Service provider could not find the recommendation service.

Action: Make sure the Activity Graph Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49701: Injectable Service provider did not set recommendation service

Cause: Injectable Service provider could not find the recommendation service.

Action: Make sure the Activity Graph Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49702: A database exception occured when connecting to the recommendation service

Cause: A database exception occured when connecting to the recommendation service

Action: Make sure the Activities data source is correctly configured and that the database server is working.
Level: 1

Type: ERROR

Impact: Other

WCS-49702: A database exception occured when connecting to the recommendation service

Cause: A database exception occured when connecting to the recommendation service

Action: Make sure the Activities data source is correctly configured and that the database server is working.
Level: 1

Type: ERROR

Impact: Other

WCS-49703: The Activity Graph engines have not been run yet; there is no data to query. Please contact your administrator to configure and run the Activity Graph engines.

Cause: The Activity Graph engines have not been run yet and there is no data to query.

Action: Please contact your administrator to configure and run the Activity Graph engines.
Level: 1

Type: WARNING

Impact: Other

WCS-49703: The Activity Graph engines have not been run yet; there is no data to query. Please contact your administrator to configure and run the Activity Graph engines.

Cause: The Activity Graph engines have not been run yet and there is no data to query.

Action: Please contact your administrator to configure and run the Activity Graph engines.
Level: 1

Type: WARNING

Impact: Other

WCS-49704: An exception occured when connecting to the recommendation service

Cause: An exception occured when connecting to the recommendation service

Action: Make sure the Activity Graph server is correctly configured and is working.
Level: 1

Type: WARNING

Impact: Other

WCS-49704: An exception occured when connecting to the recommendation service

Cause: An exception occured when connecting to the recommendation service

Action: Make sure the Activity Graph server is correctly configured and is working.
Level: 1

Type: WARNING

Impact: Other

WCS-49705: The item class urn and object urns in the request body ({0}, {1}) did not match the values in the path ({2}, {3})

Cause: The item class urn and object urns in the request body did not match the values in the path when trying to update item status.

Action: Make sure the item class urn and object urn specified in the request body matches the values in the uri path.
Level: 1

Type: WARNING

Impact: Other

WCS-49705: The item class urn and object urns in the request body ({0}, {1}) did not match the values in the path ({2}, {3})

Cause: The item class urn and object urns in the request body did not match the values in the path when trying to update item status.

Action: Make sure the item class urn and object urn specified in the request body matches the values in the uri path.
Level: 1

Type: WARNING

Impact: Other

WCS-49706: Unable to update item {0}, {1} with status {2}. Verify that the item''s class URN and object URN are valid, that the current user has permission to update the item, and that the status is either "interested" or "not interested".

Cause: Unable to update the item's status.

Action: Verify that the item's class URN and object URN are valid, that the current user has permission to update the item, and that the status is either "interested" or "not interested".
Level: 1

Type: WARNING

Impact: Other

WCS-49706: Unable to update item {0}, {1} with status {2}. Verify that the item''s class URN and object URN are valid, that the current user has permission to update the item, and that the status is either "interested" or "not interested".

Cause: Unable to update the item's status.

Action: Verify that the item's class URN and object URN are valid, that the current user has permission to update the item, and that the status is either "interested" or "not interested".
Level: 1

Type: WARNING

Impact: Other

WCS-49707: Unable to update item. Verify that the item's class URN and object URN are valid.

Cause: The item's class URN and object URN must be specified

Action: Verify that the item's class URN and object URN are valid and specified
Level: 1

Type: ERROR

Impact: Other

WCS-49707: Unable to update item. Verify that the item's class URN and object URN are valid.

Cause: The item's class URN and object URN must be specified

Action: Verify that the item's class URN and object URN are valid and specified
Level: 1

Type: ERROR

Impact: Other

WCS-49708: Unable to query for common items. Verify that the required parameters are valid and specified.

Cause: One or more mandatory query parameters have not been specified.

Action: Verify that the required parameters are valid and specified.
Level: 1

Type: WARNING

Impact: Other

WCS-49708: Unable to query for common items. Verify that the required parameters are valid and specified.

Cause: One or more mandatory query paramters have not been specified.

Action: Verify that the required parameters are valid and specified.
Level: 1

Type: WARNING

Impact: Other

WCS-49709: Unable to query for recommendations. Verify that the required parameters are valid and specified. You need to provide a recipe, an objectURN and either a classURN or serviceId parameters.

Cause: One or more mandatory query parameters have not been specified.

Action: Verify that the required parameters are valid and specified. You need to provide a recipe, an objectURN and either a classURN or serviceId parameters.
Level: 1

Type: WARNING

Impact: Other

WCS-49709: Unable to query for recommendations. Verify that the required parameters are valid and specified. You need to provide a recipe, an objectURN and either a classURN or serviceId parameters.

Cause: One or more mandatory query paramters have not been specified.

Action: Verify that the required parameters are valid and specified. You need to provide a recipe, an objectURN and either a classURN or serviceId parameters.
Level: 1

Type: WARNING

Impact: Other

WCS-49710: One of the query arguments is invalid. Verify that all arguments are correct, and that recipe and similarity URNs match the specified object types.

Cause: One or more query parameters is invalid.

Action: Verify that all arguments are correct, and that recipe and similarity URNs match the specified object types.
Level: 1

Type: WARNING

Impact: Other

WCS-49710: One of the query arguments is invalid. Verify that all arguments are correct, and that recipe and similarity URNs match the specified object types.

Cause: One or more query paramters is invalid.

Action: Verify that all arguments are correct, and that recipe and similarity URNs match the specified object types.
Level: 1

Type: WARNING

Impact: Other

WCS-49711: The following recipe is invalid: {0}. Verify that all similarity URNs are correct, that each URN has a positive weight, and that the recipe is formatted like this: item-edit:100;item-tag:10.

Cause: The recipe is invalid.

Action: Verify that all similarity URNs are correct, that each URN has a positive weight, and that the recipe is formatted like this: item-edit:100;item-tag:10.
Level: 1

Type: WARNING

Impact: Other

WCS-49711: The following recipe is invalid: {0}. Verify that all similarity URNs are correct, that each URN has a positive weight, and that the recipe is formatted like this: item-edit:100;item-tag:10.

Cause: The recipe is invalid.

Action: Verify that all similarity URNs are correct, that each URN has a positive weight, and that the recipe is formatted like this: item-edit:100;item-tag:10.
Level: 1

Type: WARNING

Impact: Other

WCS-49712: The Activity Graph service is not present in this installation. It has either not been installed or not been configured correctly. Please contact your administrator to install and configure the Activity Graph service.

Cause: The Activity Graph service is not present in this installation. It has either not been installed or not been configured correctly.

Action: Please contact your administrator to install and configure the Activity Graph service.
Level: 1

Type: WARNING

Impact: Other

WCS-49712: The Activity Graph service is not present in this installation. It has either not been installed or not been configured correctly. Please contact your administrator to install and configure the Activity Graph service.

Cause: The Activity Graph service is not present in this installation. It has either not been installed or not been configured correctly.

Action: Please contact your administrator to install and configure the Activity Graph service.
Level: 1

Type: WARNING

Impact: Other

WCS-49713: Unable to query for top items. Verify that the required parameters are valid and specified.

Cause: One or more mandatory query parameters have not been specified.

Action: Verify that the required parameters are valid and specified.
Level: 1

Type: WARNING

Impact: Other

WCS-49713: Unable to query for top items. Verify that the required parameters are valid and specified.

Cause: One or more mandatory query paramters have not been specified.

Action: Verify that the required parameters are valid and specified.
Level: 1

Type: WARNING

Impact: Other

WCS-49714: Unable to query for autocompletions because the query string or index URNs are empty or missing. Verify that the required query string and index URN arguments are present and not empty.

Cause: The autocomplete query string or index URNs are missing.

Action: Verify that the autocomplete query string and index URN arguments are present and not empty.
Level: 1

Type: WARNING

Impact: Other

WCS-49714: Unable to query for autocompletions because the query string or index URNs are empty or missing. Verify that the required query string and index URN arguments are present and not empty.

Cause: The autocomplete query string or index URNs are missing.

Action: Verify that the autocomplete query string and index URN arguments are present and not empty.
Level: 1

Type: WARNING

Impact: Other

WCS-49715: The Activity Graph autocomplete engine has not been run yet; there is no data to query. Please contact your administrator to configure and run the Activity Graph engines.

Cause: The Activity Graph autocomplete engine has not been run yet and there is no data to query.

Action: Please contact your administrator to configure and run the Activity Graph engines.
Level: 1

Type: WARNING

Impact: Other

WCS-49715: The Activity Graph autocomplete engine has not been run yet; there is no data to query. Please contact your administrator to configure and run the Activity Graph engines.

Cause: The Activity Graph autocomplete engine has not been run yet and there is no data to query.

Action: Please contact your administrator to configure and run the Activity Graph engines.
Level: 1

Type: WARNING

Impact: Other

WCS-49716: An exception occured when connecting to the autocomplete service

Cause: An exception occured when connecting to the autocomplete service

Action: Make sure the Activity Graph server is correctly configured and is working.
Level: 1

Type: WARNING

Impact: Other

WCS-49716: An exception occured when connecting to the autocomplete service

Cause: An exception occured when connecting to the autocomplete service

Action: Make sure the Activity Graph server is correctly configured and is working.
Level: 1

Type: WARNING

Impact: Other

WCS-49751: REST API Injectable Service provider did not set resource catalogs service.

Cause: REST API Injectable Service provider did not set resource catalogs service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49752: Catalog ID is not valid: {0}.

Cause: The given catalog ID is not valid to access Resource Catalog REST.

Action: Valid value for Catalog ID is: @BI. Passing any other value is not yet supported.
Level: 1

Type: WARNING

Impact: Other

WCS-49753: Catalog path not found when trying to access: {0}.

Cause: The given path is not valid to access a Resource Catalog.

Action: Verify the given path and make sure to pass a valid path.
Level: 1

Type: WARNING

Impact: Other

WCS-49754: Oracle Business Inteligence (BI) Server is not responding. Connection name: {0}

Cause: The Oracle BI server configured for this connection is not responding.

Action: Please contact your administrator to verify the connection to Oracle BI server.
Level: 1

Type: ERROR

Impact: Other

WCS-49801: Invalid ID

Cause: ID provided in the URL or query parameters is incorrect.

Action: Make sure provided IDs in path or parameters are correct.
Level: 1

Type: ERROR

Impact: Other

WCS-49802: Portal Not Found

Cause: Portal does not exist.

Action: Make sure you specify the correct portal ID is provided and that this portal has not been deleted.
Level: 1

Type: ERROR

Impact: Other

WCS-49803: Could not create object.

Cause: Could not create object based on provided PropertyBean.

Action: Make sure valid paramters were passed for object creation.
Level: 1

Type: ERROR

Impact: Other

WCS-49804: Invalid Query or OrderBy Parameter {0}.

Cause: Query or OrderBy param provided in the URL is incorrect.

Action: Verify that the query name and query parameters you specified are correct. For more information, refer to the PortalQuery API documentation.
Level: 1

Type: ERROR

Impact: Other

WCS-49805: Portal specified with short ID {0} not found.

Cause: Portal not found.

Action: Specify a valid portal short id.
Level: 1

Type: ERROR

Impact: Other

WCS-49806: Portal archive for import has not been provided. Specify the portal archive against the control name {0}.

Cause: Portal archive for import not provided.

Action: Specify a portal archive for import archive against the control name fileName.
Level: 1

Type: ERROR

Impact: Other

WCS-49807: Failed to create temporary directory within 5 attempts.

Cause: Failed to create temporary directory.

Action: Make sure you have read and write permissions on the temporary locations on the server.
Level: 1

Type: ERROR

Impact: Other

WCS-49808: Asset specified for download operation with short ID {0} not found.

Cause: Asset not found.

Action: Specify a valid asset short id.
Level: 1

Type: ERROR

Impact: Other

WCS-49809: Asset specified for download operation with short ID {0} does not belong to the portal {1}.

Cause: Asset specified for download operation does not belong to the specified portal.

Action: Specify a valid asset short id which belongs to the specified portal.
Level: 1

Type: ERROR

Impact: Other

WCS-49810: Asset archive for upload has not been provided. Specify the asset archive against the control name {0}.

Cause: Asset archive for upload not provided.

Action: Specify an asset archive for upload archive against the control name fileName.
Level: 1

Type: ERROR

Impact: Other

WCS-49811: Invalid limit ({0}) or offset ({1}) value for REST query.

Cause: Invalid limit or offset value for REST query.

Action: Make sure the limit is greater than zero and the offset is greater than or equal to zero.
Level: 1

Type: ERROR

Impact: Other

WCS-49812: The portal archive specified is invalid. Specify a valid archive that exists on the file system, and try again.

Cause: The portal archive specified is invalid.

Action: Specify a valid portal archive for upload against the fileName attribute.
Level: 1

Type: ERROR

Impact: Other

WCS-49813: The asset archive specified is invalid. Specify a valid archive that exists on the file system, and try again.

Cause: The asset archive specified is invalid.

Action: Specify a valid asset archive for upload against the fileName attribute.
Level: 1

Type: ERROR

Impact: Other

WCS-50001: An unexpected error occurred in the notification sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50001: An unexpected error occurred in the notification sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50002: Error in Notification Button tag usage - component {0} has attribute {1} whose value is {2}.

Cause: The attribute mentioned in the error cannot be null, but no value was found for this attribute.

Action: Correct your tag usage.
Level: 1

Type: WARNING

Impact: Other

WCS-50002: Error in Notification Button tag usage - component {0} has attribute {1} whose value is {2}.

Cause: The attribute mentioned in the error cannot be null, but no value was found for this attribute.

Action: Correct your tag usage.
Level: 1

Type: WARNING

Impact: Other

WCS-50003: Component {0} does not support client listeners.

Cause: Tried to add a client listener to a component that does not support client listeners.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-50003: Component {0} does not support client listeners.

Cause: Tried to add a client listener to a component that does not support client listeners.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-50004: Mandatory parameter {0} not provided in parameters

Cause: The caller did not provide the required parameter to generate notification

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50004: Mandatory parameter {0} not provided in parameters

Cause: The caller did not provide the required parameter to generate notification

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50005: Notification template {0} not found

Cause: The service failed to read the notification template. The template is not available

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50005: Notification template {0} not found

Cause: The service failed to read the notification template. The template is not available

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50006: Could not create notification contents based on default template {0}

Cause: The service failed to process the default notification template.

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50006: Could not create notification contents based on default template {0}

Cause: The service failed to process the default notification template.

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50007: Invalid child element {0} found for parent {1}

Cause: The template contains invalid child elements.

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50007: Invalid child element {0} found for parent {1}

Cause: The template contains invalid child elements.

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50008: End tag {0} not found in CDATA section corresponding to the tag at index {2}

Cause: The CDATA section of the template contains a notification tag without corresponding end tag.

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50008: End tag {0} not found in CDATA section corresponding to the tag at index {2}

Cause: The CDATA section of the template contains a notification tag without corresponding end tag.

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50009: Value for the token {0} not found in parameters

Cause: The value for the token is not provided in the list of parameter values

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50009: Value for the token {0} not found in parameters

Cause: The value for the token is not provided in the list of parameter values

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50010: Message key {0} not defined in resource bundle of service {1}

Cause: The message key used in the template does not exist in the service resource bundle

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50010: Message key {0} not defined in resource bundle of service {1}

Cause: The message key used in the template does not exist in the service resource bundle

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50011: Error occurred in parsing message {0} in resource bundle of service {1}

Cause: The message has invalid syntax

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50011: Error occurred in parsing message {0} in resource bundle of service {1}

Cause: The message has invalid syntax

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50012: An unexpected error occurred in the notification sub-system.

Cause: An unexpected error occurred.

Action: Contact your system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-50012: An unexpected error occurred in the notification sub-system.

Cause: An unexpected error occurred.

Action: Contact your system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-50013: Failed to add subscription.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50013: Failed to add subscription.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50014: Failed to remove subscription.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50014: Failed to remove subscription.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50015: Failed to query subscription.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50015: Failed to query subscription.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50016: Failed to update subscription.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50016: Failed to update subscription.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50017: Failed to save subscription.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50017: Failed to save subscription.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50018: Failed to remove subscription.

Cause: Subscription does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-50018: Failed to remove subscription.

Cause: Subscription does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-50019: Subscription cannot be added.

Cause: Subscription content is empty

Action: Provide a non empty description
Level: 1

Type: ERROR

Impact: Other

WCS-50019: Subscription cannot be added.

Cause: Subscription content is empty

Action: Provide a non empty description
Level: 1

Type: ERROR

Impact: Other

WCS-50020: Error occurred in initializing the notification sender

Cause: Failed initialize notification sender

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50020: Error occurred in initializing the notification sender

Cause: Failed initialize notification sender

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50021: Error occurred in sending notification

Cause: Failed to send notification

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50021: Error occurred in sending notification

Cause: Failed to send notification

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50022: Fail to get UMS instance url.

Cause: An unexpected error occurred.

Action: Contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-50022: Fail to get UMS instance url.

Cause: An unexpected error occurred.

Action: Contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-50023: Error occurred in saving user preference settings

Cause: Failed to save user preference settings

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50023: Error occurred in saving user preference settings

Cause: Failed to save user preference settings

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50024: The settings document is invalid

Cause: Contents of the settings document are invalid

Action: Verify and correct the settings document
Level: 1

Type: ERROR

Impact: Other

WCS-50024: The settings document is invalid

Cause: Contents of the settings document are invalid

Action: Verify and correct the settings document
Level: 1

Type: ERROR

Impact: Other

WCS-50025: Fail to get user preference settings for the service {0}

Cause: Fail to get user preference settings for the service

Action: Verify and correct the service
Level: 1

Type: ERROR

Impact: Other

WCS-50025: Fail to get user preference settings for the service {0}

Cause: Fail to get user preference settings for the service

Action: Verify and correct the service
Level: 1

Type: ERROR

Impact: Other

WCS-50026: Service Framework Exception is thrown.

Cause: Service Framework exception thrown.

Action: Check the exception's detail to see the reason why the exception is thrown.
Level: 1

Type: ERROR

Impact: Other

WCS-50026: Service Framework Exception is thrown.

Cause: Service Framework exception thrown.

Action: Check the exception's detail to see the reason why the exception is thrown.
Level: 1

Type: ERROR

Impact: Other

WCS-50027: Notification sender is not configured

Cause: Notification sender is not configured

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50027: Notification sender is not configured

Cause: Notification sender is not configured

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50028: Error in parsing notification configuration

Cause: Error in parsing notification configuration

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50028: Error in parsing notification configuration

Cause: Error in parsing notification configuration

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50029: Error processing activity for notifications

Cause: Error in processing activity for notification

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50029: Error processing activity for notifications

Cause: Error in processing activity for notification

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50030: Failed to initialize context for asynchronous processingError processing

Cause: Failed to initialize context for asynchronous processingError processing

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50030: Failed to initialize context for asynchronous processingError processing

Cause: Failed to initialize context for asynchronous processingError processing

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50031: Unexpected error occurred, please retry the unsubscribe operation

Cause: An internal error occurred

Action: Retry the unsubscribe operation. Contact Oracle Support Services if the issue persists.
Level: 1

Type: ERROR

Impact: Other

WCS-50031: Unexpected error occurred, please retry the unsubscribe operation

Cause: An internal error occurred

Action: Retry the unsubscribe operation. Contact Oracle Support Services if the issue persists.
Level: 1

Type: ERROR

Impact: Other

WCS-50032: Can not find scope for the given name

Cause: The given scope name is invalid

Action: Verify and correct the scope name
Level: 1

Type: ERROR

Impact: Other

WCS-50032: Can not find scope for the given name

Cause: The given scope name is invalid

Action: Verify and correct the scope name
Level: 1

Type: ERROR

Impact: Other

WCS-50033: An unexpected error occurred while retrieving configuration document.

Cause: Failed to get configuration document.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-50034: An unexpected error occurred while retrieving service name for service id {0}.

Cause: Failed to get service name.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-50035: An unexpected error occurred while retrieving subscription object type.

Cause: Failed to get subscription object type.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-50036: An unexpected error occurred while sending UMS notification message.

Cause: Failed to send UMS notification message.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-51001: Document {0} cannot be checked out as it is locked by user {1}.

Cause: Another user has checked out the document.

Action: Contact the other user, or wait until they have checked in the document.
Level: 1

Type: ERROR

Impact: Files

WCS-51002: Unspecified Error

Cause: See underlying error.final

Action: See underlying error
Level: 1

Type: ERROR

Impact: Other

WCS-51003: Document {0} does not exist.

Cause: File may have been deleted, or the current user no longer has access to it.

Action: Check if file exists in the space.
Level: 1

Type: ERROR

Impact: Files

WCS-51004: Document {0} cannot be checked in as it is not checked out.

Cause: File is not checked out.

Action: Check out the file before attempting to check it in.
Level: 1

Type: ERROR

Impact: Files

WCS-51005: User {0} does not have the rights to access document {1}.

Cause: User does not have rights to access documents.

Action: Check user rights to document.
Level: 1

Type: ERROR

Impact: Files

WCS-51006: Folder {0} already exists in this parent folder.

Cause: Folder already exists.

Action: type the name of a folder that does not already exist.
Level: 1

Type: ERROR

Impact: Files

WCS-52002: error obtaining content repository connection

Cause: A JNDI naming exception occurred while attempting to obtain the content repository connection.

Action: Verify that connections.xml contains a valid entry for the content repository connection.
Level: 1

Type: WARNING

Impact: Other

WCS-52002: error obtaining content repository connection

Cause: A JNDI naming exception occurred while attempting to obtain the content repository connection.

Action: Verify that connections.xml contains a valid entry for the content repository connection.
Level: 1

Type: WARNING

Impact: Other

WCS-52003: error obtaining blog folder for the page

Cause: The blog folder for the page cannot be found or created.

Action: Check the server logs for details on this exception.
Level: 1

Type: WARNING

Impact: Other

WCS-52003: error obtaining blog folder for the page

Cause: The blog folder for the page cannot be found or created.

Action: Check the server logs for details on this exception.
Level: 1

Type: WARNING

Impact: Other

WCS-52004: After fail-over, failed to get the item {0} from the repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-52004: After fail-over, failed to get the item {0} from the repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-52005: error obtaining blog entry for the page

Cause: The blog entry for the page cannot be found.

Action: Check the server logs for details on this exception.
Level: 1

Type: WARNING

Impact: Other

WCS-52005: error obtaining blog entry for the page

Cause: The blog entry for the page cannot be found.

Action: Check the server logs for details on this exception.
Level: 1

Type: WARNING

Impact: Other

WCS-60001: Unable to fetch category listing

Cause: Failed to retrieve category list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60002: Unable to fetch category with id {0}

Cause: Failed to retrieve category information from the data store.

Action: Ensure that valid category id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60003: Unable to create category with name {0}

Cause: Failed to create a new category.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60004: Unable to delete category with id {0}

Cause: Failed to delete category.

Action: Ensure that valid category id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60005: Unable to fetch list of top contributors

Cause: Failed to get list of top contributors in the current category.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60006: Unable to edit category with id {0}

Cause: Failed to edit category information in the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60007: Unable to fetch forum with id {0}

Cause: Failed to retrieve forum information from the data store.

Action: Ensure that valid forum id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60008: Unable to create forum with name {0}

Cause: Failed to create a new forum.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60009: Unable to delete forum with id {0}

Cause: Failed to delete forum.

Action: Ensure that valid forum id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60010: Unable to fetch list of forums for category with id {0}

Cause: Failed to retrieve forum list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60011: Unable to edit forum with id {0}

Cause: Failed to edit forum information in the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60012: Unable to fetch list of topics for forum with id {0}

Cause: Failed to retrieve topic list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60013: Unable to fetch topic with id {0}

Cause: Failed to retrieve topic information from the data store.

Action: Ensure that valid topic id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60014: Unable to delete topic with id {0}

Cause: Failed to delete topic.

Action: Ensure that valid topic id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60015: Unable to lock forum with id {0}

Cause: Failed to lock forum to prevent updates.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60016: Unable to unlock forum with id {0}

Cause: Failed to unlock forum to allow updates.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60017: Unable to create topic with title "{0}"

Cause: Failed to create a new topic.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60018: Unable to edit topic with id {0}

Cause: Failed to edit topic information in the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60019: Unable to fetch list of messages for topic with id {0}

Cause: Failed to retrieve message list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60020: Unable to fetch message with id {0}

Cause: Failed to retrieve message information from the data store.

Action: Ensure that valid message id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60021: Unable to delete message with id {0}

Cause: Failed to delete message.

Action: Ensure that valid message id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60022: Unable to lock topic with id {0}

Cause: Failed to lock topic to prevent updates.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60023: Unable to unlock topic with id {0}

Cause: Failed to unlock topic to allow updates.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60024: Unable to check if the topic with id {0} is answered or not

Cause: Failed to check the answered status of the topic.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60025: Unable to fetch number of messages in topic with id {0}

Cause: Failed to fetch the message count in the topic.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60026: Unable to create message

Cause: Failed to create a new message.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60027: Unable to fetch list of answers for topic with id {0}

Cause: Failed to retrieve answer list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60028: Unable to edit message with id {0}

Cause: Failed to edit message information in the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60029: Unable to fetch list of sub messages for message with id {0}

Cause: Failed to retrieve message list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60030: Unable to like message with id {0}

Cause: Failed to like message.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60031: Unable to unlike message with id {0}

Cause: Failed to unlike message.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60032: Unable to mark message with id {0} as the answer

Cause: Failed to mark message as the answer.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60033: Unable to unmark message with id {0} as the answer

Cause: Failed to unmark message as the answer.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60034: Unable to check if the message with id {0} is an answer or not

Cause: Failed to check if the message is an answer.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60035: Unable to create a sub message to message with id {0}

Cause: Failed to create a sub message.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60036: Unable to fetch number of topics in forum with id {0}

Cause: Failed to retrieve topic count from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60037: Unable to fetch number of answered topics in forum with id {0}

Cause: Failed to retrieve topic count from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60038: Unable to fetch number of unanswered topics in forum with id {0}

Cause: Failed to retrieve topic count from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60039: Unable to fetch list of recent topics for category with id {0}

Cause: Failed to retrieve topic list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60040: Unable to instantiate forum factory class {0}

Cause: Failed to reinstantiate factory class.

Action: Ensure that the correct factory class name has been supplied.
Level: 1

Type: WARNING

Impact: Other

WCS-60041: Unable to perform operation, since forum/topic is locked

Cause: Unable to perform operation.

Action: Ensure the forum/topic is not locked.
Level: 1

Type: WARNING

Impact: Other

WCS-60042: Unable to fetch list of recent topics for forum with id {0}

Cause: Failed to retrieve topic list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60043: Unable to fetch list of popular topics for forum with id {0}

Cause: Failed to retrieve topic list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60044: Unable to fetch OSN connection details

Cause: Failed to retrieve OSN Connection.

Action: Ensure that the OSN Connection is created via WLST/EM.
Level: 1

Type: WARNING

Impact: Other

WCS-62001: Unexpected error occurred while saving translations for {0},{1}.

Cause: Unexpected error getting translations.

Action: Contact Oracle support services.
Level: 1

Type: ERROR

Impact: Other

WCS-62002: Unexpected error loading translations into WebCenter Portal.

Cause: Unexpected error loading translations.

Action: Contact Oracle support services.
Level: 1

Type: ERROR

Impact: Other

WCS-62003: The MDS Root location for loading translations cannot be null.

Cause: Null MDS root provided for loading translations.

Action: Please specify a valid MDS root location.
Level: 1

Type: ERROR

Impact: Other

WCS-63001: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63001: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63002: An object of type {0} with this id ({1}) already exits.

Cause: An attempt was made to create an object with an id that is already in use.

Action: Specify a unique id.
Level: 1

Type: ERROR

Impact: Other

WCS-63002: An object of type {0} with this id ({1}) already exits.

Cause: An attempt was made to create an object with an id that is already in use.

Action: Specify a unique id.
Level: 1

Type: ERROR

Impact: Other

WCS-63003: The name ({0}) is not valid.

Cause: The specified name is not valid.

Action: Specify a valid name.
Level: 1

Type: ERROR

Impact: Other

WCS-63003: The name ({0}) is not valid.

Cause: The specified name is not valid.

Action: Specify a valid name.
Level: 1

Type: ERROR

Impact: Other

WCS-63004: Object has been changed by another user.

Cause: The object has been changed by another user.

Action: Reload the object and try the operation again.
Level: 1

Type: ERROR

Impact: Other

WCS-63004: Object has been changed by another user.

Cause: The object has been changed by another user.

Action: Reload the object and try the operation again.
Level: 1

Type: ERROR

Impact: Other

WCS-63005: An Object of type {0} with id={1} could not be found.

Cause: The specified object could not be found. This may be due to the object being deleted by another user.

Action: Specify a valid id.
Level: 1

Type: ERROR

Impact: Other

WCS-63005: An Object of type {0} with id={1} could not be found.

Cause: The specified object could not be found. This may be due to the object being deleted by another user.

Action: Specify a valid id.
Level: 1

Type: ERROR

Impact: Other

WCS-63006: Object ({0}) is immutable.

Cause: An attempt to change this object was made, but this object is currently immutable.

Action: Retrieve mutable object to make changes.
Level: 1

Type: ERROR

Impact: Other

WCS-63006: Object ({0}) is immutable.

Cause: An attempt to change this object was made, but this object is currently immutable.

Action: Retrieve mutable object to make changes.
Level: 1

Type: ERROR

Impact: Other

WCS-63007: {0} is not a valid reference name to MDS.

Cause: The name is not a valid MDS reference name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63007: {0} is not a valid reference name to MDS.

Cause: The name is not a valid MDS reference name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63008: The MDS session does not support updates.

Cause: MDS was not configured correctly to support updates.

Action: Configure the MDS store to support updates.
Level: 1

Type: ERROR

Impact: Other

WCS-63008: The MDS session does not support updates.

Cause: MDS was not configured correctly to support updates.

Action: Configure the MDS store to support updates.
Level: 1

Type: ERROR

Impact: Other

WCS-63009: An IO error occurred when accessing metadata.

Cause: An IO error occurred in MDS.

Action: See the log for more details on the specific IO error to correct the problem.
Level: 1

Type: ERROR

Impact: Other

WCS-63009: An IO error occurred when accessing metadata.

Cause: An IO error occurred in MDS.

Action: See the log for more details on the specific IO error to correct the problem.
Level: 1

Type: ERROR

Impact: Other

WCS-63010: The object is not valid.

Cause: The metadata for the object does not pass validation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63010: The object is not valid.

Cause: The metadata for the object does not pass validation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63011: Failed to construct attribute set for list [{0}].

Cause: Failed to construct attribute set for list.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63011: Failed to construct attribute set for list [{0}].

Cause: Failed to construct attribute set for list.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63012: Failed to add data flavor to ListTransferable. List=[{0}] DataFlavor=[{1}]

Cause: Failed to add data flavor to ListTransferable.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63012: Failed to add data flavor to ListTransferable. List=[{0}] DataFlavor=[{1}]

Cause: Failed to add data flavor to ListTransferable.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63013: The query attribute predicate {0}{1}{2} was ignored because the column does not exist or the comparator is not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-63013: The query attribute predicate {0}{1}{2} was ignored because the column does not exist or the comparator is not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-63014: An error occurred when deleting metadata.

Cause: An error occurred in MDS while deleting metadata.

Action: See the log for more details on the specific error to correct the problem.
Level: 1

Type: ERROR

Impact: Other

WCS-63014: An error occurred when deleting metadata.

Cause: An error occurred in MDS while deleting metadata.

Action: See the log for more details on the specific error to correct the problem.
Level: 1

Type: ERROR

Impact: Other

WCS-63015: A column with the name ({0}) already exists.

Cause: A column was created or renamed with the name of an existing column in the list.

Action: Specify a unique column name within the list.
Level: 1

Type: ERROR

Impact: Other

WCS-63015: A column with the name ({0}) already exists.

Cause: A column was created or renamed with the name of an existing column in the list.

Action: Specify a unique column name within the list.
Level: 1

Type: ERROR

Impact: Other

WCS-63016: A list with the name ({0}) already exists.

Cause: A list was created or renamed with the name of an existing list.

Action: Specify a unique list name.
Level: 1

Type: ERROR

Impact: Other

WCS-63016: A list with the name ({0}) already exists.

Cause: A list was created or renamed with the name of an existing list.

Action: Specify a unique list name.
Level: 1

Type: ERROR

Impact: Other

WCS-63017: The maximum number of columns for this list has been exceeded.

Cause: A list was created or modified with more than 30 columns.

Action: Do not add more than 30 columns to a list.
Level: 1

Type: ERROR

Impact: Other

WCS-63017: The maximum number of columns for this list has been exceeded.

Cause: A list was created or modified with more than 30 columns.

Action: Do not add more than 30 columns to a list.
Level: 1

Type: ERROR

Impact: Other

WCS-63019: The Lists service is not provisioned for scope {0}.

Cause: The Lists service is not provisioned for the specified scope.

Action: Provision the Lists service for the specified scope.
Level: 1

Type: ERROR

Impact: Other

WCS-63019: The Lists service is not provisioned for scope {0}.

Cause: The Lists service is not provisioned for the specified scope.

Action: Provision the Lists service for the specified scope.
Level: 1

Type: ERROR

Impact: Other

WCS-63020: The value is the wrong data type. The data type expected is {0}.

Cause: The value is the wrong data type.

Action: Use the value with the correct data type.
Level: 1

Type: ERROR

Impact: Other

WCS-63020: The value is the wrong data type. The data type expected is {0}.

Cause: The value is the wrong data type.

Action: Use the value with the correct data type.
Level: 1

Type: ERROR

Impact: Other

WCS-63021: The WebCenter repository is not available.

Cause: An error occurred accessing the repository.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-63021: The WebCenter repository is not available.

Cause: An error occurred accessing the repository.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-63022: An error occurred accessing the WebCenter metadata repository.

Cause: An error occurred accessing the repository.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-63022: An error occurred accessing the WebCenter metadata repository.

Cause: An error occurred accessing the repository.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-63023: List column values were converted or deleted based on list column changes during import: scope={0}, list={1}, column={2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-63023: List column values were converted or deleted based on list column changes during import: scope={0}, list={1}, column={2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-64001: JAXRS framework encryption service threw exception with message {0}.

Cause: JAXRS framework encryption service not initialized correctly.

Action: Ensure JAXRS framework encryption service is initialized.
Level: 1

Type: ERROR

Impact: Other

WCS-64001: JAXRS framework encryption service threw exception with message {0}.

Cause: JAXRS framework encryption service not initialized correctly.

Action: Ensure JAXRS framework encryption service is initialized.
Level: 1

Type: ERROR

Impact: Other

WCS-64002: JAXRS framework encryption service set up required. Key generator algorithm not set up in credential store framework.

Cause: Key generator algorithm not set up in credential store framework.

Action: Set up key generator algorithm in credential store framework.
Level: 1

Type: WARNING

Impact: Other

WCS-64002: JAXRS framework encryption service set up required. Key generator algorithm not set up in credential store framework.

Cause: Key generator algorithm not set up in credential store framework.

Action: Set up key generator algorithm in credential store framework.
Level: 1

Type: WARNING

Impact: Other

WCS-64003: JAXRS framework encryption service set up required. Cipher transformation not set up in credential store framework.

Cause: Cipher transformation not set up in credential store framework.

Action: Set up cipher transformation in credential store framework.
Level: 1

Type: WARNING

Impact: Other

WCS-64003: JAXRS framework encryption service set up required. Cipher transformation not set up in credential store framework.

Cause: Cipher transformation not set up in credential store framework.

Action: Set up cipher transformation in credential store framework.
Level: 1

Type: WARNING

Impact: Other

WCS-64005: The ResourceType element named \"{0}\" is missing its \"{1}\" element.

Cause: The specified element is required by ResourceType element and cannot be empty.

Action: Correct the ResourceType by setting the specified element to a non-empty value.
Level: 1

Type: ERROR

Impact: Other

WCS-64006: ResourceType maps require the key element to be of type String.

Cause: The ResourceType map key should be of type String.

Action: Correct the ResourceType by setting the specified map key to a String.
Level: 1

Type: ERROR

Impact: Other

WCS-64007: The ResourceType element \"resourceTypeUrn\" requires a urn value.

Cause: The specified element value is required by ResourceType.

Action: Correct the ResourceType by setting the specified element to a non-empty value.
Level: 1

Type: ERROR

Impact: Other

WCS-64008: The ResourceType element named \"{0}\" must match the end of the resourceType urn name, \"{1}\".

Cause: The end of the resourceType urn name must match the element's name.

Action: Correct the ResourceType by setting the specified element's name to the end of the resourceType urn string.
Level: 1

Type: ERROR

Impact: Other

WCS-64010: The resource config provider cannot be instantiated.

Cause: The resource config provider for Jersey servlet is not configured properly.

Action: Check web.xml to make sure the resource config provider is configured correctly.
Level: 1

Type: ERROR

Impact: Other

WCS-64011: The TokenManager is not initialized.

Cause: The Token Manager is not configured correctly and cannot be initialized.

Action: Check web.xml to make sure the Token Manager is configured correctly.
Level: 1

Type: ERROR

Impact: Other

WCS-64012: Failed to set capabilities for REST resource type {0} due to exception {1}.

Cause: Failed to set capabilities for REST resource.

Action: Make sure REST resource is annotated correctly.
Level: 1

Type: WARNING

Impact: Other

WCS-64013: Null injectee in REST injection resolver class {0}.

Cause: Null injectee in REST injection resolver class.

Action: Make sure REST servlet and resources are configured correctly.
Level: 1

Type: WARNING

Impact: Other

WCS-64014: Missing WebCenter resource registration class.

Cause: The WebCenter resource registration class is missing.

Action: Make sure a WebCenter resource registration class is implemented and registered in the web.xml file and mapped to the oracle.jaxrs.config.registration context parameter.
Level: 1

Type: ERROR

Impact: Other

WCS-64015: The WebCenter resoruce registration class {0} is incorrectly implemented.

Cause: The WebCenter resource registration class does not implement the WebCenterResourceRegistration interface.

Action: Make sure the WebCenter resource registration class implements the WebCenterResourceRegistration interface and is correctly registered in the web.xml file.
Level: 1

Type: ERROR

Impact: Other

WCS-64016: Failed to invoke the WebCenter resoruce registration class {0} due to exception {1} with message {2}.

Cause: Failed to invoke the WebCenter resource registration class at runtime.

Action: Make sure the WebCenter resource registration class is correctly implemented and registered in the web.xml file.
Level: 1

Type: ERROR

Impact: Other

WCS-65001: Web service data control creation failed. Check the WSDL and re-create the data control

Cause: WSDL may be inaccessible or the WSDL file may be incorrect.

Action: Make sure the WSDL is accessible and correct, then re-create the data control.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-65002: An unexpected error occurred while creating visualization.

Cause: Parameter form not generated.

Action: Check the logs for exception.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-69251: {0} of {1} is out-of-bounds

Cause: Page is not responding within configured limits

Action: Check the regions on the page to identify which region is problematic, or general system health
Level: 1

Type: WARNING

Impact: Other

WCS-69252: {0} of {1} is out-of-bounds

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-69253: {0} of {1} is out-of-bounds.

Cause: Portlet is not responding within configured limits

Action: Check the backend Producer or the network connectivity to it, or general system health
Level: 1

Type: WARNING

Impact: Other

WCS-69254: {0} of {1} is out-of-bounds

Cause: Document Library Upload service is not responding within configured limits

Action: Check the Content Server or the network connectivity to it, or general system health
Level: 1

Type: WARNING

Impact: Other

WCS-69255: {0} of {1} is out-of-bounds

Cause: Document Library Download service is not responding within configured limits

Action: Check the Content Server or the network connectivity to it, or general system health
Level: 1

Type: WARNING

Impact: Other

WCS-70001: Invalid value "{1}" supplied for argument "{0}"

Cause: Argument value is empty or invalid.

Action: Please provide appropriate value to the argument.
Level: 1

Type: WARNING

Impact: Other

WCS-70002: Resource of type "{0}" with id {1} not found

Cause: The resource with supplied id could not be found.

Action: Please provide valid resource id.
Level: 1

Type: WARNING

Impact: Other

WCS-70003: Operation {0} is not supported by the resource of type "{0}" with id {1}

Cause: The operation is not supported by the resource.

Action: Please ensure that the operation invoked on the resource is supported by the backend.
Level: 1

Type: WARNING

Impact: Other

WCS-72001: Missing @PersistProperty, @PersistText, @PersistCollection or @PersistReference annotation on method: {0}.

Cause: @PersistProperty, @PersistText, @PersistCollection or @PersistReference annotation is required on the accessors corresponding to persistence methods to enable access through the Portal Core Persistence Layer.

Action: Add the @PersistProperty, @PersistText, @PersistCollection or @PersistReference annotation to the accessor as defined in the Portal Core Persistence Layer's integration documentation.
Level: 1

Type: ERROR

Impact: Other

WCS-72002: PersistenceManager does not support method: {0}.

Cause: An attempt was made to use a method that is not supported by the Portal Core Persistence Layer.

Action: Add the required method to the class.
Level: 1

Type: ERROR

Impact: Other

WCS-72003: Invalid value passed to reference operation ''{0}'' for reference ''{1}''. Expected {2}, received {3}.

Cause: A value passed to a reference mutator could not be converted to the required type.

Action: Modify calling code to ensure references are only updated with valid types.
Level: 1

Type: ERROR

Impact: Other

WCS-72004: Cannot instantiate object using abstract PortalEntity interface: {0}

Cause: An attempt was made to create a PortalEntity object using an interface that is marked as abstract.

Action: Supply a non-abstract type or remove the @AbstractEntity annotation from this interface.
Level: 1

Type: ERROR

Impact: Other

WCS-72005: Unable to delete null {0}.

Cause: A null PortalEntity or PortalEntityObject was supplied.

Action: Supply a non-null PortalEntity or PortalEntityObject.
Level: 1

Type: WARNING

Impact: Other

WCS-72006: Unable to delete PortalEntity. A PortalEntity in portal ''{0}'' and namespace ''{1}'' with name ''{2}'' was not found.

Cause: An attempt was made to delete a PortalEntity object that does not exist.

Action: Ensure that the supplied portal, namespace and name values are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-72007: Unable to delete PortalEntity. A PortalEntity with ID ''{0}'' was not found.

Cause: An attempt was made to delete a PortalEntity object that does not exist.

Action: Ensure that the supplied ID is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-72008: PortalEntity in portal ''{0}'' and namespace ''{1}'' with name ''{2}'' was found but is not of the requested type. Type requested = {3}, type found = {4}.

Cause: The type of PortalEntity object found in the persistence store was not as expected.

Action: Ensure that the supplied portal, namespace, name and type parameters are correct.
Level: 1

Type: ERROR

Impact: Other

WCS-72009: PortalEntity object with ID ''{0}'' was found but is not of the requested type. Type requested = {1}, type found = {2}.

Cause: The type of PortalEntity object found in the persistence store was not as expected.

Action: Ensure that the supplied ID and type parameters are correct.
Level: 1

Type: ERROR

Impact: Other

WCS-72010: An error occurred while starting a transaction.

Cause: An error occurred while starting a transaction.

Action: Check the root cause of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-72011: An error occurred while committing a transaction.

Cause: An error occurred while committing a transaction.

Action: Check the root cause of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-72012: An error occurred while rolling-back a transaction.

Cause: An error occurred while rolling-back a transaction.

Action: Check the root cause of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-72013: An error occurred while checking the status of a transaction.

Cause: An error occurred while checking the status of a transaction.

Action: Check the root cause of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-72014: Unable to read the value of property ''{0}'' of PortalEntity ''{1}'' using method ''{2}''.

Cause: An error occurred while trying to read a property of a PortalEntity object.

Action: Use the associated exception to determine why the property could not be read.
Level: 1

Type: ERROR

Impact: Other

WCS-72015: Unable to create XML document.

Cause: An error occurred while using JAXB to create an XML document.

Action: Use the associated exception to determine why JAXB serialization failed.
Level: 1

Type: ERROR

Impact: Other

WCS-72018: Unable to read XML document.

Cause: An error occurred while using JAXB to read an XML document.

Action: Use the associated exception to determine why JAXB deserialization failed.
Level: 1

Type: ERROR

Impact: Other

WCS-72019: Unable to set the value of property ''{0}'' for PortalEntity ''{1}'' using method ''{2}''.

Cause: An error occurred while trying to set a property of a PortalEntity object.

Action: Use the associated exception to determine why the property could not be set.
Level: 1

Type: ERROR

Impact: Other

WCS-72020: Unable to find set method for property ''{0}'' of PortalEntity ''{1}''.

Cause: An error occurred while trying to set a property of a PortalEntity object.

Action: Unable to find set method for the property.
Level: 1

Type: ERROR

Impact: Other

WCS-72021: Unable to set references for ''{0}'' of property ''{1}'' for PortalEntity ''{2}''.

Cause: An error occurred while trying to set a reference property of a PortalEntity object.

Action: Use the associated exception to determine why the property could not be set.
Level: 1

Type: ERROR

Impact: Other

WCS-72022: Unsupported data type: {0}.

Cause: A data type has been used for a persisted property of an object which is not supported by the Portal Core Persistence Layer.

Action: Use a data type specified by the oracle.webcenter.portal.persistence.PersistedDataType enum.
Level: 1

Type: ERROR

Impact: Other

WCS-72023: Invalid offset {0} for data type {1}

Cause: The offset used for a persisted property is not valid.

Action: Try using a smaller offset value, if possible.
Level: 1

Type: ERROR

Impact: Other

WCS-72024: PortalEntity object with short ID ''{0}'' was found but is not of the requested type. Type requested = {1}, type found = {2}.

Cause: The type of PortalEntity object found in the persistence store was not as expected.

Action: Ensure that the supplied short ID and type parameters are correct.
Level: 1

Type: ERROR

Impact: Other

WCS-72025: Unable to delete PortalEntity. A PortalEntity with short ID ''{0}'' was not found.

Cause: An attempt was made to delete a PortalEntity object that does not exist.

Action: Ensure that the supplied short ID is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-72026: A PortalEntity object with ID ''{0}'' and name ''{1}'' was found but is not of the expected type. Type expected = {2}, type found = {3}.

Cause: The type of a PortalEntity object found in the persistence store was not as expected.

Action: Ensure that the type requested in the query is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-72027: Invalid pagination requested in query: Row limit {0}, first row {1}.

Cause: Invalid criteria specified for query pagination.

Action: Ensure that the row limit is greater than zero, and the first row index is greater than or equal to zero.
Level: 1

Type: ERROR

Impact: Other

WCS-72028: Permission class ''{0}'' cannot be used with actions ''{1}''.

Cause: The permission class name and actions specified via an @Authorization annotation on a PortalEntity class cannot be used with the current security manager.

Action: Correct the permission class name or actions.
Level: 1

Type: ERROR

Impact: Other

WCS-72029: Could not find permission class named: ''{0}''.

Cause: A permission class specified by the permissionClassName element of an @Authorization annotation could not be loaded.

Action: Ensure that the name of the class is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-72030: Type ''{0}'' is not valid. More than one property has datatype {1} and offset {2}, see methods: {3} and {4}.

Cause: A type makes incorrect use of the @PersistProperty annotation.

Action: Use a different offset for one of the methods named in the error message.
Level: 1

Type: ERROR

Impact: Other

WCS-72031: Could not find the persistence object with ID {0} and type {1} in the persistent store.

Cause: A PortalEntity was passed to the PersistenceManager but does not correspond to an entity in the persistent store.

Action: Requery the PortalEntity and try the operation again.
Level: 1

Type: ERROR

Impact: Other

WCS-72032: Invalid from-clause for the query. You must specify one or more types.

Cause: The Query.from(Class... types) method was called with either a null or empty list of types.

Action: Update the code to pass one or more types to the Query.from(Class... types) method.
Level: 1

Type: ERROR

Impact: Other

WCS-72033: The query contains an invalid reference to property {0}.

Cause: An invalid property name has been specified in the query.

Action: Update the query to correct the error.
Level: 1

Type: ERROR

Impact: Other

WCS-72034: The property {0} cannot be used for a property comparsion in a query.

Cause: The property type does not implement the Comparable interface and so cannot be used in with an operation that requires a Comparable interface.

Action: Update the query to correct the error.
Level: 1

Type: ERROR

Impact: Other

WCS-72035: The property {0} is not indexed and so cannot be used in a query without enabling the unindexed property mode.

Cause: The property maps to a column that was not marked as indexed and the unindexed property mode is not enabled.

Action: Either use a different property in the query or enable the unindexed property mode for the query.
Level: 1

Type: ERROR

Impact: Other

WCS-72036: The property {0} cannot be used in the order-by clause of the query.

Cause: An invalid property was used in an order-by clause.

Action: Update the query to use a valid property for the order-by clause.
Level: 1

Type: ERROR

Impact: Other

WCS-72037: Could not set the value of the long text field because the CLOB has not been created.

Cause: There has been an attempt to set the value of the long text field before the CLOB has been created.

Action: Update the calling code to create the CLOB before setting the long text field.
Level: 1

Type: ERROR

Impact: Other

WCS-72038: Cannot import ''{1}'' resource ''{0}'' as the target portal is not set and the source portal is not part of the export set

Cause: Resource import failed because the portal ID associated with the resource did not match any portal in the target portal server, or the specified portal was not part of the export set, or the target portal was not set on the importXML() method.

Action: Update the importXML() method to specify a valid portal on the target.
Level: 1

Type: ERROR

Impact: Other

WCS-72039: The target portal for the import does not exist on the portal server.

Cause: Import failed as the target portal does not exist on the portal server.

Action: Update the importXML() method to specify a valid portal on the target.
Level: 1

Type: ERROR

Impact: Other

WCS-72040: The text property getter method {0} has an invalid return type {1}.

Cause: The getter method for the text property has a return type that is neither String nor java.io.Reader.

Action: Update the method to return either String or java.io.Reader.
Level: 1

Type: ERROR

Impact: Other

WCS-72041: The text property setter method {0} has an invalid parameter {1}.

Cause: The first parameter of the setter method for the text property is neither String nor java.io.Reader.

Action: Update the method so that the first parameter is a String or java.io.Reader.
Level: 1

Type: ERROR

Impact: Other

WCS-72042: An attempt was made to create a PortalEntity object named ''{0}'' and type ''{1}'' with a null Portal property.

Cause: PortalEntities must specify a Portal on creation, unless the type of PortalEntity is a Portal.

Action: Ensure that a Portal is set on the PortalEntity object prior to creation.
Level: 1

Type: ERROR

Impact: Other

WCS-72043: An attempt was made to set a PortalEntity object named ''{0}'' and type ''{1}'' with a null Portal property.

Cause: PortalEntities must not specify null as the Portal property on a set operation, unless the type of PortalEntity is a Portal.

Action: Ensure that a null is not set on the PortalEntity, unless the type of PortalEntity is a Portal.
Level: 1

Type: ERROR

Impact: Other

WCS-72044: Failed to set collection ''{0}'' of type ''{1}'' for PortalEntity object of type ''{2}'' on import.

Cause: Collections of this type are not supported.

Action: Ensure that the data being imported is compatible with this version of the portal server.
Level: 1

Type: ERROR

Impact: Other

WCS-72045: While importing object ''{0}'' with ID ''{1}'', could not find referenced object with ID ''{2}'' (reference name ''{3}'').

Cause: An object referenced by an object in the export set could not be found on the target server.

Action: If required, transfer the referenced object from the source server to the target server.
Level: 1

Type: WARNING

Impact: Other

WCS-72046: While importing object ''{0}'' with ID ''{1}'', could not find referencing object with ID ''{2}'' and type ''{3}'' (reference name ''{4}'').

Cause: An object referencing an object in the export set could not be found on the target server.

Action: If required, transfer the referencing object from the source server to the target server.
Level: 1

Type: WARNING

Impact: Other

WCS-72047: Unable to copy a Portal because a Portal with the name ''{0}'' already exists.

Cause: An attempt was made to copy a Portal with the name of an existing Portal.

Action: Ensure that the supplied Portal name is unique.
Level: 1

Type: WARNING

Impact: Other

WCS-72048: The targetPortal parameter must be null when copying a Portal.

Cause: An attempt was made to copy a Portal with the targetPortal parameter set to a none-null value.

Action: Ensure that the targetPortal parameter is set to null.
Level: 1

Type: ERROR

Impact: Other

WCS-72049: The current user is not authorized to perform action ''{2}'' on object {0} ({1}).

Cause: The current user does not have permission to perform an action on an object.

Action: Ensure that the user is granted appropriate permissions.
Level: 1

Type: ERROR

Impact: Other

WCS-72050: A conflict has occurred with your edit, it will be necessary to resubmit the changes using the updated resource.

Cause: An optimitistic locking exception was raised by the persistence store, due to an earliuer update on the resource by another transaction.

Action: Re-try your edits using the updated resource.
Level: 1

Type: ERROR

Impact: Other

WCS-72051: Attempted to apply a security ID {0} on an entity {1} with no Authorization annotation (type {2})

Cause: Either setSecurityId() or setSecurityEntity() was called on this entity with a non-null value, but the type of this entity has no Authorization annotation defined.

Action: Modify the type definition to add the Authorization annotation, or avoid securing this entity type.
Level: 1

Type: ERROR

Impact: Other

WCS-72052: The current user is not authorized to create an object of type ''{0}'' in portal with ID ''{1}''..

Cause: The current user does not have permission to create objects of the specified type.

Action: Ensure that the user is granted appropriate permissions.
Level: 1

Type: ERROR

Impact: Other

WCS-72053: Permission class ''{0}'' cannot be used with actions ''{1}'' in @CreateAuthorization annotation.

Cause: The permission class name and actions specified via a @CreateAuthorization annotation on a PortalEntity class cannot be used with the current security manager.

Action: Correct the permission class name or actions.
Level: 1

Type: ERROR

Impact: Other

WCS-72054: An error occurred while setting the timeout of a transaction.

Cause: An error occurred while setting the timeout of a transaction.

Action: Check the root cause of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-72055: The user is not authorized to perform this operation.

Cause: The user was not authorized to perform the operation.

Action: Check the root cause of the exception for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-72056: A PortalEntity could not be created from PortalEntityObject {0} because no type factories could be found.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-72057: None of the available type factories were able to create a PortalEntity from PortalEntityObject {0}.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-72058: The EntityManager's transaction is already active.

Cause: An error occurred initializing the TransactionManager.

Action: Modify calling code to remove direct acces to the Portal EntityManager's transaction.
Level: 1

Type: ERROR

Impact: Other

WCS-72059: The EntityManager is configured for JPA.

Cause: An error occurred initializing the TransactionManager.

Action: The Portal EntityManager must be configured for resource local transactions.
Level: 1

Type: ERROR

Impact: Other

WCS-72060: The TransactionManager has uncommitted changes which have been rolled back.

Cause: The TransactionManager's context is ending and the uncommitted changes have been rolled back.

Action: Contact your Oracle Support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-72061: The TransactionManager has uncommitted changes which cannot be rolled back.

Cause: The TransactionManager's context is ending and rollback of its uncommitted changes has failed.

Action: Check the root cause of the exception and contact your Oracle Support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-72062: The TransactionManager cannot begin the transaction as the EntityManager's transaction is already active.

Cause: The EntityManager's transaction is already active.

Action: Ensure that no calling code is directly accessing the Portal EntityManager's transaction.
Level: 1

Type: ERROR

Impact: Other

WCS-72063: The TransactionManager must fully rollback.

Cause: All outstanding transactions must be rolled-back.

Action: Rollback all outstanding transactions.
Level: 1

Type: ERROR

Impact: Other

WCS-72064: An error occurred executing a transactional method.

Cause: An error occurred executing a transactional method.

Action: Check the root cause of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-72065: Transactions cannot be commited out of order.

Cause: The calling code is attempting to commit transactions out of order.

Action: The calling code must commit transactions in the same order as they were begun.
Level: 1

Type: ERROR

Impact: Other

WCS-72067: Failed to set translation ''{0}'' for Locale ''{1}'' on PortalEntity object of type ''{2}'' on import.

Cause: An error occurred while trying to set a property of a PortalEntity object.

Action: Use the associated exception to determine why the property could not be set.
Level: 1

Type: ERROR

Impact: Other

WCS-72401: Cannot determine the ID of the current page. The current page will not be available via the Portal Request Context.

Cause: The Portal Runtime Framework was unable to obtain the ID of the current page using JSF.

Action: Ensure that the application is running in a JSF environment.
Level: 1

Type: WARNING

Impact: Other

WCS-72402: Cannot find a page with ID ''{0}''. The current page will not be available via the Portal Request Context.

Cause: The current page with the given ID could not be found in the Portal's persistent store.

Action: Ensure that the page with the given ID is present in the Portal's persistent store.
Level: 1

Type: WARNING

Impact: Other

WCS-72403: The AdfPortalController Failed to redirect to URL ''{0}''.

Cause: An internal error occurred whilst attempting to perform a redirect of the portal.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-72501: Unable to find the CDI bean for type: {0}.

Cause: No beans of the given type are available for injection.

Action: Make sure that an injectable implementation of the given type is on the classpath.
Level: 1

Type: ERROR

Impact: Other

WCS-72551: Method ''{0}'' cannot be called when the current transaction is active.

Cause: A method with a Transactional annotation whose propagation element was set to NEVER was called when a transaction was active.

Action: Make sure the transaction is not active when the method is called.
Level: 1

Type: ERROR

Impact: Other

WCS-72552: Method ''{0}'' must be called when the current transaction is active.

Cause: A method with a Transactional annotation whose propagation element was set to MANDATORY was called when a transaction was not active.

Action: Make sure the transaction is active when the method is called.
Level: 1

Type: ERROR

Impact: Other

WCS-72571: Cache name ''{0}'' is invalid.

Cause: An invalid cache name has been used.

Action: Make sure the cache name is of the form ''oracle.webcenter.*''.
Level: 1

Type: ERROR

Impact: Other

WCS-72601: Failed to create a document with Metadata Object absolute name "{0}".

Cause: An underlying MDS exception caused this.

Action: See related log entries.
Level: 1

Type: ERROR

Impact: Other

WCS-72602: Metadata Object absolute name "{0}" already exists.

Cause: Metadata already exists.

Action: Check the metadata to be created.
Level: 1

Type: ERROR

Impact: Other

WCS-72603: Pattern syntax error in name "{0}".

Cause: Pattern syntax error in name.

Action: Check name.
Level: 1

Type: ERROR

Impact: Other

WCS-72604: Metadata Object absolute name "{0}" not found.

Cause: Metadata not found.

Action: Check the metadata to be found.
Level: 1

Type: ERROR

Impact: Other

WCS-72605: Encountered an MDS exception "{0}" with message "{1}".

Cause: An underlying MDS exception caused this.

Action: Check underlying exception.
Level: 1

Type: ERROR

Impact: Other

WCS-72608: Failed to update a Portal object.

Cause: An underlying exception caused this.

Action: Check underlying exception.
Level: 1

Type: ERROR

Impact: Other

WCS-72609: Failed to delete a Portal object.

Cause: An underlying exception caused this.

Action: Check underlying exception.
Level: 1

Type: ERROR

Impact: Other

WCS-72610: Required parameter {0} not specified.

Cause: Required parameter is not specified.

Action: Ensure that the required parameter is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-72611: Required parameters {0} and/or {1} not specified.

Cause: Required parameters are not specified.

Action: Ensure that the required parameters are specified.
Level: 1

Type: ERROR

Impact: Other

WCS-72612: File type is required for paramter {0}

Cause: File type is not specified in the parameter.

Action: Ensure that the file type is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-72613: A version conflict was detected when updating the portal object. {0}

Cause: The supplied PropertyBean has a non-null currentVersionId property, and it does not match the current version ID of the object it was applied to.

Action: Requery the portal object properties and apply the update again if appropriate.
Level: 1

Type: ERROR

Impact: Other

WCS-72615: PropertyBean create validation failed: {0}

Cause: The supplied PropertyBean violates the validation constraints that are enforced for creation with this type of PropertyBean.

Action: Review the error message for details of the constraint violations.
Level: 1

Type: ERROR

Impact: Other

WCS-72616: PropertyBean update validation failed: {0}

Cause: The supplied PropertyBean violates the validation constraints that are enforced for update with this type of PropertyBean.

Action: Review the error message for details of the constraint violations.
Level: 1

Type: ERROR

Impact: Other

WCS-72620: ValidationFrame not populated.

Cause: The ValidationFrame providing context for PropertyBean validation did not contain state that was expected to be present.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-72621: FrameAwareValidator invoked outside of a ValidationFrame.

Cause: The ValidationFrame providing context for PropertyBean validation was not found.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-72622: Error getting bean value.

Cause: Inspect the cause exception to determine the underlying cause.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-72624: An error occurred while attempting to copy the portlets.

Cause: An exception was thrown while attempting to copy the portlets for a page.

Action: Check the root cause of the exception.
Level: 1

Type: WARNING

Impact: Other

WCS-72625: An error occurred while trying to instantiate the query manager or named query via reflection.

Cause: An exception was thrown while attempting to load query classes via reflection.

Action: Check that the classes requested are valid for this operation.
Level: 1

Type: ERROR

Impact: Other

WCS-72627: The asset of the given Id {0} is not found.

Cause: The asset is not found.

Action: Check that the asset with the given Id value exists.
Level: 1

Type: ERROR

Impact: Other

WCS-72628: Duplicate name: {0}.

Cause: An attempt was made to create an object with a name that has already been used.

Action: Use a different name.
Level: 1

Type: ERROR

Impact: Other

WCS-72629: Duplicate portal name: {0}.

Cause: An attempt was made to create a portal with a name that has already been used for a portal.

Action: Use a different name for the portal.
Level: 1

Type: ERROR

Impact: Other

WCS-72632: Device Operation {0} not allowed.

Cause: Devices and Device Groups cannot be created, modified or deleted in a custom portal

Action: Ensure that the operations are performed at the portal server
Level: 1

Type: ERROR

Impact: Other

WCS-72633: Device group {0} being customized in {1} portal does not exist at the portal server

Cause: Device group being customized at the portal level does not exist

Action: Ensure that device group being customized exists in the portal server
Level: 1

Type: ERROR

Impact: Other

WCS-72637: Authorization failure when trying to delete {0} type object "{1}" with ID: {2}

Cause: The current user is not authorized to delete the object

Action: Ensure that the user is granted the appropriate permissions
Level: 1

Type: ERROR

Impact: Other

WCS-72638: Authorization failure when trying to update {0} type object "{1}" with ID: {2}

Cause: The current user is not authorized to update the object

Action: Ensure that the user is granted the appropriate permissions
Level: 1

Type: ERROR

Impact: Other

WCS-72639: The Portal API object is not attached.

Cause: The Portal API object has a null id. This means it is not attached to any underlying persistence object.

Action: The Portal API client should attach the object or obtain a new object with a valid id from the PortalObjectRepository. The object can become unattached if it has been deleted.
Level: 1

Type: ERROR

Impact: Other

WCS-72640: The persistence resource with ID "{0}" associated with the ManagedPortalObject could not be found.

Cause: The Portal API ManagedPortalObject object is attached to an underlying persistence resouce that is no longer available.

Action: The Portal API client should take appropriate action to account for the deleted Portal API object.
Level: 1

Type: ERROR

Impact: Other

WCS-72641: There was a failure adding member ''{0}'' to portal ''{1}''

Cause: A failure occurred adding a member to a portal.

Action: Examine the logged exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-72642: There was a failure removing member ''{0}'' from portal ''{1}''

Cause: A failure occurred removing a member from a portal.

Action: Examine the logged exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-72643: There was a failure removing members for role ''{0}'' from portal ''{1}''

Cause: A failure occurred removing all members with a role from a portal.

Action: Examine the logged exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-72646: Duplicate portal display name: {0}.

Cause: An attempt was made to create a portal with a display name that has already been used for a portal.

Action: Use a different display name for the portal.
Level: 1

Type: ERROR

Impact: Other

WCS-72647: Null portal name.

Cause: An attempt was made to create a portal with a null name.

Action: Use a non-null name for this portal.
Level: 1

Type: ERROR

Impact: Other

WCS-72648: Null portal display name.

Cause: An attempt was made to create a portal with a null display name.

Action: Use a non-null display name for this portal.
Level: 1

Type: ERROR

Impact: Other

WCS-72649: Operation forbidden without authorization to perform action {0} on {1} (type {2}, id {3})

Cause: An attempt was made to perform an unauthorized action.

Action: Ensure user is authorized to perform this action and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-72650: Invalid name: {0}.

Cause: An attempt was made to create an object with a invalid name.

Action: Use a different valid name.
Level: 1

Type: ERROR

Impact: Other

WCS-72651: Invalid portal name: {0}.

Cause: An attempt was made to create a portal with a invalid name.

Action: Use a name containing only letters and digits.
Level: 1

Type: ERROR

Impact: Other

WCS-72652: Invalid portal template name: {0}.

Cause: An attempt was made to create a portal template with a invalid name.

Action: Use a name containing only letters and digits.
Level: 1

Type: ERROR

Impact: Other

WCS-72653: Failed to rename a Portal object.

Cause: An underlying exception caused this.

Action: Check underlying exception.
Level: 1

Type: ERROR

Impact: Other

WCS-72654: Unable to cleanup properly after failed creation of {0}.

Cause: An underlying exception caused this.

Action: Check underlying exception.
Level: 1

Type: WARNING

Impact: Other

WCS-72655: Some properties have violated their constraints.

Cause: Constrainst have been violated on setting or updating the properties.

Action: Check that the properties values are correct.
Level: 1

Type: ERROR

Impact: Other

WCS-72656: The combination of (isDiscoverable=false and isPublic=true) is not allowed.

Cause: The Access Level setting constraint has been violated.

Action: Check that the properties values are correct.
Level: 1

Type: ERROR

Impact: Other

WCS-72701: Error in checking if the service ${0} is provisioned for portal ${1}.

Cause: Unable to discover the service's provisioning status.

Action: Examine the exception for further information.
Level: 1

Type: ERROR

Impact: Other

WCS-72702: Error in checking which services are configured.

Cause: Unable to discover which services are configured.

Action: Examine the exception for further information.
Level: 1

Type: ERROR

Impact: Other

WCS-72703: Error in provisioning service ${0} for portal ${1}.

Cause: Unable to provision the service for the portal.

Action: Examine the exception for further information.
Level: 1

Type: ERROR

Impact: Other

WCS-72704: Error in unprovisioning service ${0} for portal ${1}.

Cause: Unable to unprovision the service for the portal.

Action: Examine the exception for further information.
Level: 1

Type: ERROR

Impact: Other

WCS-72705: Error in retrieving the ScopeAPI for the ${0} service.

Cause: Unable to get the ScopeAPI for the service.

Action: Examine the exception for further information.
Level: 1

Type: ERROR

Impact: Other

WCS-72706: Error getting group info for user ${0}.

Cause: Unable to get group info for a user.

Action: Examine the exception for further information.
Level: 1

Type: ERROR

Impact: Other

WCS-72707: Error in copying service ${0} from portal ${1} to portal {2}.

Cause: Unable to unprovision the service for the portal.

Action: Examine the exception for further information.
Level: 1

Type: ERROR

Impact: Other

WCS-72801: Error publishing activity to the activity stream

Cause: Unable to publish an activity to the activity stream.

Action: Examine the exception for further information.
Level: 1

Type: WARNING

Impact: Other

WCS-72802: The {2} role has already been granted for user {1} in portal {0}

Cause: Unable to grant the role because it has already been granted.

Action: Examine the exception for further information.
Level: 1

Type: ERROR

Impact: Other

WCS-72803: Failed to grant the {2} role for user {1} in portal {0}

Cause: Unable to grant the role due to an exception.

Action: Examine the exception for further information.
Level: 1

Type: ERROR

Impact: Other

WCS-72804: Failed to revoke the {2} role for user {1} in portal {0}

Cause: Unable to revoke the role due to an exception.

Action: Examine the exception for further information.
Level: 1

Type: ERROR

Impact: Other

WCS-72805: Failed to set permissions for portal {0}

Cause: Unable to set permissions due to an exception.

Action: Examine the exception for further information.
Level: 1

Type: ERROR

Impact: Other

WCS-72806: Failed to drop role {0} for portal {1}

Cause: Unable to drop role due to an exception.

Action: Examine the exception for further information.
Level: 1

Type: ERROR

Impact: Other

WCS-73000: Muffling exception.

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-73001: Unable to instantiate upgrade handler {0}.

Cause: Review the underlying exception in the logs to determine the cause.

Action: Make sure that handler implementation is on the classpath.
Level: 1

Type: ERROR

Impact: Other

WCS-73002: Unable to instantiate upgrade manager.

Cause: Review the underlying exception in the logs to determine the cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73003: Upgrade failed for portal {0}.

Cause: Review the underlying exception in the logs to determine the cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73004: Upgrade clean up failed for portal {0}.

Cause: Review the underlying exception in the logs to determine the cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73005: Upgrade initialization failed for handler {0}.

Cause: Review the underlying exception in the logs to determine the cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73006: Upgrade validation failed for {0}:{1} in scope {2}.

Cause: Review the underlying exception in the logs to determine the cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73007: Upgrade validation failed for {0}:{1} in scope {2} due to {3}.

Cause: Validation failed for the said 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: Other

WCS-73008: Upgrade phase failed for {0}:{1} in scope {2}.

Cause: Review the underlying exception in the logs to determine the cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73009: Upgrade clean up failed for {0}:{1} in scope {2}.

Cause: Review the underlying exception in the logs to determine the cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73010: Post upgrade failed for {0}:{1} in scope {2}.

Cause: Review the underlying exception in the logs to determine the cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73011: Portal {0} with id {1} not found in the repository.

Cause: Either the portal upgrade has not happened or there is some data corruption.

Action: Check logs for related error. Re-run upgrade. If you still continue to see the issue, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73012: Default portal upgrade failed therefore halting the upgrade.

Cause: Review the related exception in the logs to determine the cause.

Action: Re-run upgrade. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73013: Exception while resolving the reference for {0} , message: {1}.

Cause: Review the related exception in the logs to determine the cause.

Action: Re-run upgrade. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73014: Exception while getting a list of scopes for upgrade, message: {0}.

Cause: Review the related exception in the logs to determine the cause.

Action: Re-run upgrade. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73015: Exception while getting a list of scopes for clean up, message: {0}.

Cause: Review the related exception in the logs to determine the cause.

Action: Re-run upgrade. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73016: Exception while persisting the information related to upgrade scope failure, message: {0}.

Cause: Review the related exception in the logs to determine the cause.

Action: Re-run upgrade. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73017: An error occurred while trying to audit portal server using MDS root {0}.

Cause: Review the related exception in the logs to determine the cause.

Action: Re-run audit. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73018: An error occurred while trying to generate audit report for portal server in report directory {0}.

Cause: Review the related exception in the logs to determine the cause.

Action: Re-run audit. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73019: An error occurred while trying to audit portals {0} using MDS root {1}.

Cause: Review the related exception in the logs to determine the cause.

Action: Re-run audit. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73020: An error occurred while trying to generate audit report for portals {0} in report directory {1}.

Cause: Review the related exception in the logs to determine the cause.

Action: Re-run audit. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73021: An error occurred while trying to initialize mbeans to audit deprecated connection usage.

Cause: Review the related exception in the logs to determine the cause.

Action: Re-run audit. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73022: An error occurred while trying to audit deprecated connection usage.

Cause: Review the related exception in the logs to determine the cause.

Action: Re-run audit. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73023: An error occurred while trying to audit deprecated usage of type {0} in scopes {1}.

Cause: Review the related exception in the logs to determine the cause.

Action: Re-run audit. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73024: Exception while getting a list of scopes for post upgrade, message: {0}.

Cause: Review the related exception in the logs to determine the cause.

Action: Re-run upgrade. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73025: Post upgrade failed for portal {0}.

Cause: Review the underlying exception in the logs to determine the cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73026: Unable to instantiate Upgrade Context for scope {0}.

Cause: Review the underlying exception in the logs to determine the cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-73027: An error occurred while upgrade.

Cause: Review the underlying exception in the logs to determine the cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-80001: The blog is locked. You cannot create new entries

Cause: The blog has been locked.

Action: Unlock the block to enable creating new entries.
Level: 1

Type: WARNING

Impact: Other

WCS-89001: An unexpected error occurred in the activity stream sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-89001: An unexpected error occurred in the activity stream sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-89002: WSRP Connection Name {0} already exists.

Cause: Connection Name used already exists.

Action: Use a different name for the connection.
Level: 1

Type: ERROR

Impact: Other

WCS-89002: WSRP Connection Name {0} already exists.

Cause: Connection Name used already exists.

Action: Use a different name for the connection.
Level: 1

Type: ERROR

Impact: Other

WCS-89003: Web Service Connection Name {0} already exists. WSRP connection {1} cannot be created.

Cause: Connection Name used already exists.

Action: Use a different name for the connection.
Level: 1

Type: ERROR

Impact: Other

WCS-89003: Web Service Connection Name {0} already exists. WSRP connection {1} cannot be created.

Cause: Connection Name used already exists.

Action: Use a different name for the connection.
Level: 1

Type: ERROR

Impact: Other

WCS-89004: Cannot register the producer due to connectivity issues.

Cause: Failed to connect to the producer. Either the connection details specified were invalid or there was a network problem.

Action: Verify that the producer connection details are correct, and then check to see if a firewall or some other network issue is blocking the connection.
Level: 1

Type: ERROR

Impact: Other

WCS-89004: Cannot register the producer due to connectivity issues.

Cause: Failed to connect to the producer. Either the connection details specified were invalid or there was a network problem.

Action: Verify that the producer connection details are correct, and then check to see if a firewall or some other network issue is blocking the connection.
Level: 1

Type: ERROR

Impact: Other

WCS-89005: Unable to register the producer due to an invalid WSDL URL.

Cause: The WSDL URL specified for the WSRP producer was invalid.

Action: Specify a valid WSDL URL, and then try again.
Level: 1

Type: ERROR

Impact: Other

WCS-89005: Unable to register the producer due to an invalid WSDL URL.

Cause: The WSDL URL specified for the WSRP producer was invalid.

Action: Specify a valid WSDL URL, and then try again.
Level: 1

Type: ERROR

Impact: Other

WCS-89006: URL Connection Name {0} already exists.

Cause: Connection Name used already exists.

Action: Use a different name for the connection.
Level: 1

Type: ERROR

Impact: Other

WCS-89006: URL Connection Name {0} already exists.

Cause: Connection Name used already exists.

Action: Use a different name for the connection.
Level: 1

Type: ERROR

Impact: Other

WCS-89007: Web Producer Name {0} already exists.

Cause: Web Producer Name used already exists.

Action: Use a different name for the Web producer.
Level: 1

Type: ERROR

Impact: Other

WCS-89007: Web Producer Name {0} already exists.

Cause: Web Producer Name used already exists.

Action: Use a different name for the Web producer.
Level: 1

Type: ERROR

Impact: Other

WCS-89008: Unable to register the producer due to exception {0}. Contact your administrator.

Cause: Error occurred registering the producer.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89008: Unable to register the producer due to exception {0}. Contact your administrator.

Cause: Error occurred registering the producer.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89009: Unable to unregister the producer due to exception {0}. Contact your administrator.

Cause: Error occurred deregistering the producer.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89009: Unable to unregister the producer due to exception {0}. Contact your administrator.

Cause: Error occurred deregistering the producer.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89010: Unable to get producer connections due to exception {0}. Contact your administrator.

Cause: Error occurred retrieving the list of producers.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89010: Unable to get producer connections due to exception {0}. Contact your administrator.

Cause: Error occurred retrieving the list of producers.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89011: Unable to register the WSRP producer due to exception {0}. Contact your administrator.

Cause: Error occurred registering the WSRP producer.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89011: Unable to register the WSRP producer due to exception {0}. Contact your administrator.

Cause: Error occurred registering the WSRP producer.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89012: Unable to register the JPDK producer due to exception {0}. Contact your administrator.

Cause: Encountered an exception when registering the JPDK producer.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89012: Unable to register the JPDK producer due to exception {0}. Contact your administrator.

Cause: Encountered an exception when registering the JPDK producer.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89013: Unable to create the WSRP producer connection due to exception {0}. Contact your administrator.

Cause: Error occurred creating the WSRP producer connection.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89013: Unable to create the WSRP producer connection due to exception {0}. Contact your administrator.

Cause: Error occurred creating the WSRP producer connection.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89014: Unable to refresh the producer connections due to exception {0}

Cause: Error occurred refreshing the list of producers.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89014: Unable to refresh the producer connections due to exception {0}

Cause: Error occurred refreshing the list of producers.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89015: Failed to clean up producer registration due to exception {0}. Contact your administrator.

Cause: Error occurred cleaning up the producer registration.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89015: Failed to clean up producer registration due to exception {0}. Contact your administrator.

Cause: Error occurred cleaning up the producer registration.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89016: The operation failed due to an exception. Contact your administrator.

Cause: Error occurred performing the operation.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89016: The operation failed due to an exception. Contact your administrator.

Cause: Error occurred performing the operation.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89017: Error parsing policy XML ({0}) from PolicyApplication mbean with message {1}

Cause: Error parsing policy XML from PolicyApplication mbean.

Action: Make sure the policy XML in the PolicyApplication mbean is set correctly.
Level: 1

Type: ERROR

Impact: Other

WCS-89501: An unexpected error occurred in the activity stream sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-89501: An unexpected error occurred in the activity stream sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-89502: External Application Connection Name {0} already exists.

Cause: Connection Name used already exists.

Action: Use a different name for Connection.
Level: 1

Type: ERROR

Impact: Other

WCS-89502: External Application Connection Name {0} already exists.

Cause: Connection Name used already exists.

Action: Use a different name for Connection.
Level: 1

Type: ERROR

Impact: Other

WCS-89503: No connection selected for this operation.

Cause: No External Application connection selected for this operation.

Action: Select a External Application connection from the table listing the available connections.
Level: 1

Type: ERROR

Impact: Other

WCS-89503: No connection selected for this operation.

Cause: No External Application connection selected for this operation.

Action: Select a External Application connection from the table listing the available connections.
Level: 1

Type: ERROR

Impact: Other

WCS-90100: No moveplan.xml file available.

Cause: moveplan.xml file missing.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-90100: No moveplan.xml file available.

Cause: moveplan.xml file missing.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-90200: Error in validating the source environment.

Cause: Invalid source environment.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-90200: Error in validating the source environment.

Cause: Invalid source environment.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

57 WLS-WSEE-CORE-00001 to WLS-WSEE-CORE-00007

WLS-WSEE-CORE-00001: An unexpected error occurred: {0}

Cause: Unknown

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-CORE-00002: 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

WLS-WSEE-CORE-00006: 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

WLS-WSEE-CORE-00007: Error while invoking endpoint {0} from client; ServiceName: {1} ; PortName: {2} ; Client side features: {3}; Client side policies: {4}

Cause: Unknown.

Action: Check the error mesage and stack trace for more info.
Level: 1

Type: SEVERE

Impact: WebService

58 WLS-WSEE-MC-00001 to WLS-WSEE-MC-00016

WLS-WSEE-MC-00001: {0}: {1}

Cause: An unexpected exception has occurred.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-MC-00002: Exception reading SOAP body of message

Cause: An error occurred reading the message's SOAP body.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-MC-00003: No SOAP body in message

Cause: There is no SOAP body in the message.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-MC-00004: Exception reading MakeConnection message

Cause: An error occurred reading a MakeConnection message.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-MC-00005: Policy requires mandatory MakeConnection anonymous URIs

Cause: Either or both of the replyTo and faultTo addresses are not MakeConnection anonymous URIs.

Action: Correct the replyTo and/or faultTo addresses.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-MC-00006: replyTo address {0} is a malformed MakeConnection anonymous URI.

Cause: The supplied replyTo address is not a legal MakeConnection anonymous URI.

Action: Correct the replyTo address.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-MC-00007: The Malformed faultTo MakeConnection anonymous URI: {0}

Cause: The format of the faultTo address is not that of a MakeConnection anonymous URI.

Action: Correct the faultTo address.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-MC-00008: Failed to find pending list for {0}

Cause: There is no pending message list corresponding to the received MakeConnection anonymous URI.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-MC-00009: Cannot concurrently use MakeConnection and Async Client Transport.

Cause: Both the Make Connection and Async Client Transport features have been specified; however, they are mutually exclusive.

Action: Correct the list of features used.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-MC-00010: {0} is an illegal poll id.

Cause: Poll id cannot be null or a null string.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-MC-00011: {0} is an illegal poll state for attempted operation.

Cause: Operation cannot be attempted when poll is in its current state.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-MC-00012: Cannot reset poll expiration timer.

Cause: The timer for the sending of MakeConnection messages cannot be reset.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-MC-00013: Unexpected response received on poll, id: {0}, state {1}

Cause: MakeConnection initiator not in a state where a response was expected.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-MC-00014: Address is not set in MakeConnection message.

Cause: MakeConnection messages must specify an Address element containing a MakeConnection anonymous URI

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-MC-00015: Could not build header of type {0}: {1}

Cause: An unexpected exception occurred during building of header.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-MC-00016: ClientIdentityFeature not enabled or clientId not specified on this port/stub. This is required for WS-MC polling by this client.

Cause: A Port/Dispatch instance was created without specifying an 'identity' via the ClientIdentityFeature JAX-WS feature when WS-MC requires such an identity.

Action: Add a ClientIdentityFeature when creating your Port/Dispatch stub instance, and make sure that feature has its clientId field set to a unique, repeatable client ID.
Level: 1

Type: SEVERE

Impact: WebService

59 WLS-WSEE-00002 to WLS-WSEE-00116

WLS-WSEE-00002: 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: SEVERE

Impact: WebService

WLS-WSEE-00003: 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: SEVERE

Impact: WebService

WLS-WSEE-00004: 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: SEVERE

Impact: WebService

WLS-WSEE-00005: 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: SEVERE

Impact: WebService

WLS-WSEE-00006: 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: SEVERE

Impact: WebService

WLS-WSEE-00007: 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: SEVERE

Impact: WebService

WLS-WSEE-00008: 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: SEVERE

Impact: WebService

WLS-WSEE-00009: 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: SEVERE

Impact: WebService

WLS-WSEE-00010: 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: SEVERE

Impact: WebService

WLS-WSEE-00011: 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: SEVERE

Impact: WebService

WLS-WSEE-00012: 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

WLS-WSEE-00013: 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: SEVERE

Impact: WebService

WLS-WSEE-00014: 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: SEVERE

Impact: WebService

WLS-WSEE-00015: 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: SEVERE

Impact: WebService

WLS-WSEE-00016: 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: SEVERE

Impact: WebService

WLS-WSEE-00017: The start element was not found.

Cause: The XML stream is corrupted.

Action: Correct the XML stream and retry the task.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-00018: 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: SEVERE

Impact: WebService

WLS-WSEE-00031: Failed to create Web services reliable agents. {0}.

Cause: There is a configuration error Administration Server failure.

Action: Check the configuration.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-00033: 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: SEVERE

Impact: WebService

WLS-WSEE-00034: Failed to access the store for reliable delivery. {0}.

Cause: There was a failure accessing JMS.

Action: Contact My Oracle Support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-00100: 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

WLS-WSEE-00101: 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: SEVERE

Impact: WebService

WLS-WSEE-00102: 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: SEVERE

Impact: WebService

WLS-WSEE-00105: 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

WLS-WSEE-00106: 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: SEVERE

Impact: WebService

WLS-WSEE-00107: An unexpected error occurred: {0}

Cause: Unknown

Action: Contact Oracle support
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-00108: 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

WLS-WSEE-00112: 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

WLS-WSEE-00113: 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

WLS-WSEE-00114: 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

WLS-WSEE-00115: JMS onMessage exception {0} {1}

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: WARNING

Impact: WebService

WLS-WSEE-00116: Can't find injection @WebServiceRef target {0} in class {1} of application {2}

Cause: An invalid @WebServiceRef or missing injection target in a client class.

Action: Correct or remove this invalid or unsupported client class.
Level: 1

Type: SEVERE

Impact: WebService

60 WLS-WSEE-PERSIST-00001 to WLS-WSEE-PERSIST-00007

WLS-WSEE-PERSIST-00001: An unexpected error occurred: {0}

Cause: Unknown

Action: Contact Oracle support
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-PERSIST-00002: No store name provided, and persistence strategy is not LOCAL_ACCESS_ONLY. The SendingService cannot be created.

Cause: When requesting a network-available persistent store, the name of this store must be given when attempting to create a SendingService instance.

Action: Set up the store, and provide its name when creating the SendingService, or request a store that uses LOCAL_ACCESS_ONLY so the service can create the store for you.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-PERSIST-00003: The store associated with the given store name ({0}) is slated for use across the network but is not an XA-capable store. Please specify another store name or configure this store to be location independent (e.g. JDBC-based, etc.)

Cause: In order to use a store across the network, that store must support the XA transaction protocol. Without this, only local changed can be made.

Action: Set up the store, and provide its name when creating the SendingService, or request a store that uses LOCAL_ACCESS_ONLY so the service can create the store for you.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-PERSIST-00004: A store instance with persistent store name {0} and connection name {1} already exists.

Cause: Some component has attempted to create a store instance without first checking for an existing one. Please contact Oracle Tech Support to file an issue.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-PERSIST-00005: Logical store {0} not defined.

Cause: You have configured web services to use a named logical store but have not defined that logical store on this server.

Action: Change the name of the logical store to be used for this web service (or web service client) or define a logical store with the given name (using WLST, WLS console, etc.)
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-PERSIST-00006: You cannot reset the ID on a ClientIdentityFeature. Existing ID {0} attempted new ID {1}

Cause: You called ClientIdentityFeature.setClientId() but thid ID has already been set. You cannot reset the ID.

Action: Check the ID on the ClientIdentityFeature before trying to set it, or create a new client instance (Port/Dispatch instance) and set a new ClientIdentityFeature on that instance.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-PERSIST-00007: Improper buffering queue type {0} with JNDI name {1} configured on logical store {2}. You must use Uniform Distributed Queues or simple Queues with web services.

Cause: You configured an invalid type of queue for a logical store (via the RequestBufferingQueueJndiName or ResponseBufferingQueueJndiName properties). You must use Uniform Distributed Queues (recommended) or plain Queues. If you wish to take advantage of migration features of web services in a cluster, you must use Uniform Distributed Queues. Note, when using configuration wizard or WLST to apply the wls_webservice_jaxws.jar extension template, you must explicitly request the creation of Uniform Distributed Queues as described in the web services documentation. By default, the configuration wizard and WLST create Weighted Distributed Queues in a cluster.

Action: Configure a Uniform Distributed Queue (or Queue) and provide this queue's JNDI name to the logical store configuration (via the RequestBufferingQueueJndiName or ResponseBufferingQueueJndiName properties). Note, you can do this from the configuration wizard or WLST when applying the wls_webservice_jaxws.jar extension template, and the proper type and number of queues will be created automatically for you. See the web services documentation for more information on requesting Uniform Distributed Queues when using the template.
Level: 1

Type: SEVERE

Impact: WebService

61 WLS-WSEE-SENDER-00001 to WLS-WSEE-SENDER-00006

WLS-WSEE-SENDER-00001: An unexpected error occurred: {0}

Cause: Unknown

Action: Contact Oracle support
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-SENDER-00002: The conversation with the given name ({0}) already exists, and cannot be added again.

Cause: You've tried to create two or more conversation instances with the same name.

Action: Pick a different conversation name, or look for an existing conversation before trying to create one.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-SENDER-00003: The conversation with the given name ({0}) could not be found.

Cause: You've asked for a conversation with an unknown name.

Action: Pick a different conversation name, or create/add it before trying to look it up.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-SENDER-00004: The request with the given message ID ({0}) could not be found.

Cause: You've asked for a request with an unknown message ID.

Action: Pick a different message ID, or create/add it before trying to look it up.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-SENDER-00005: The request with the given conversation name ({0}) and sequence number ({1}) could not be found.

Cause: You've asked for a request with an unknown conversation name and sequence number combination.

Action: Pick a different conversation/sequence number, or create/add it before trying to look it up.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-SENDER-00006: The conversation ({0}) has been cancelled.

Cause: The conversation with the given name has been cancelled. This can occur if the conversation has timed out or has encountered some type of fatal error.

Action: Look at and resolve the underlying exceptions that may be keeping this conversation from proceeding, or if the conversation seems to be proceeding normally, consider increasing the conversation or idle timeout values.
Level: 1

Type: SEVERE

Impact: WebService

62 WLS-WSEE-WSAT-00001 to WLS-WSEE-WSAT-00117

WLS-WSEE-WSAT-00001: Error persisting branch record for branch {0}: {1}

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00002: Error deleting branch record for branch {0}: {1}

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00007: SystemException while registering WS-AT XAResource {0}

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00008: SystemException while registering WS-AT XAResource {0}

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00024: replayOperation Xid: {0} resulted in SOAPException: {1}

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00033: Unexpected failed status {0} during WS-AT Synchronization beforeCompletion for Address {1} and Xid {2} . Marking transaction for rollback.

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00034: InterruptedException {0} during beforeCompletion for Address {1} and Xid {2}

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00035: Exception {0} during beforeCompletion for Address {1} and Xid {2}

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00045: Failed state of {0} during WS-AT XAResource prepare for Address {1} and Xid {2} . This may be due to a timeout waiting for a response.

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00052: Failed state of {0} during WS-AT XAResource commit for Address {1} and Xid {2} . This may be due to a timeout waiting for a response.

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00053: InterruptedException {0} during WS-AT XAResource commit for Address {1} and Xid {2}

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00059: Failed state of {0} during WS-AT XAResource rollback for Address {1} and Xid {2} . This may be due to a timeout waiting for a response.

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00060: InterruptedException {0} during WS-AT XAResource rollback for Address {1} and Xid {2}

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00063: Enter client-side handleFault {0}

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00064: Exit client-side handleFault with {0} {1}

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00073: InvalidTransactionException {0} while attempting to resume suspended transaction {1} on thread {2} . Resume will be forced and transaction marked for rollback.

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00074: SystemException {0} while attempting to resume suspended transaction {1} on thread {2} . Resume will be forced and transaction marked for rollback.

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00077: SOAPException {0} while creating coordinator context for transaction {1} on thread {2}

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00080: SystemException {0} during suspend for transaction {1} on thread {2}

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00081: Unknown participant protocol identifier in WS-AT context {0}

Cause: Refer to the exception in the log message and SOAP message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00115: txid does not exist in header in WebServiceContext {0} while calling getWSATTidFromWebServiceContextHeaderList

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

WLS-WSEE-WSAT-00117: Error Enlisting EndpointReferencetype {0} with Xid {1}: {2}

Cause: Refer to the exception in the log message.

Action: Contact Oracle support.
Level: 1

Type: SEVERE

Impact: WebService

63 WSEE-RM-00001 to WSEE-RM-00019

WSEE-RM-00001: Conversation {0} was specified/retained directly by the client, but has expired or has been terminated or destroyed. Please use a new service or dispatch instance.

Cause: A service or Dispatch instance was reused after a reliable sequence was created and completed on it. You should use a new service/Dispatch instance to avoid using the same saved sequence ID for a new sequence.

Action: Use a new service/Dispatch instance before invoking more reliable operations after a prior sequence of invocations.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00002: SourceSequence not ready to send sequence messages. Retry after CreateSequenceResponse and Sequence.getState() == CREATED.

Cause: An attempt was made to use or modify a sequence from the RM source side before that sequence has completed the RM handshake process (when the CreateSequenceResponse message arrives and is processed).

Action: Retry the operation after the RM sequence has been properly initialized, and the CreateSequenceResponse message for the sequence has been processed.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00003: Protocol exception, detected a response to a response on the client side. Since there is no protocol-specific back-channel on a client-side response, we attempted to send the secondary response via a new outbound connection, and this failed. This response cannot be delivered. Response was: {0} Send error was: {1}

Cause: Runtime code attempted to send a response after processing a response on the client-side protocol-specific back-channel. The back-channel can only support one message delivery, so we attempted, and failed, to send this secondary response via a new outbound connection. Because of this failure, the secondary response cannot be delivered.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00004: Client-side couldn't determine if we have RM policy on target service/port

Cause: Runtime code on the client or sending side of an RM sequence couldn't retrieve a policy.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00005: Server-side couldn't determine if we have RM policy on target service/port

Cause: Runtime code on the service or receiving side of an RM sequence couldn't retrieve a policy.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00006: No {0} header found on CreateSequenceResponse. Cannot identify sequence to handle this message

Cause: A protocol violation has occurred, and RM cannot identify the message ID of the CreateSequence message by looking at the CreateSequenceResponse message.

Action: Contact the vendor that supplied the RM destination implementation (receiver of CreateSequence message) and indicate a protocol violation.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00007: Got CreateSequenceResponse/Accept when no offer was made on sequence with destination-side ID: {0}

Cause: A CreateSequenceResponse message in response to a CreateSequence message that does not contain an Offer element must not itself contain an Accept element.

Action: Contact the vendor that supplied the RM destination implementation (receiver of CreateSequence message) and indicate a protocol violation.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00008: Null sequence ID specified/found

Cause: A null value was passed to some internal method taking a sequence identifier where that method does not accept null values.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00009: Null message ID specified/found

Cause: A null value was passed to some internal method taking a message identifier where that method does not accept null values.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00010: Attempt to add a sequence that is null or has already been added: {0}

Cause: A null sequence (or a sequence that already has been added to the list of valid sequences) has been detected.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00011: Attempt to update a sequence that is null or has not been added via addSequence: {0}

Cause: A null sequence (or a sequence that never has been added to the list of valid sequences) has been referenced in an update operation.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00012: Cannot accept/process this request, and can't assume async response is forthcoming because ReplyTo is anonymous. Cannot continue.

Cause: An incoming request to the RM destination has failed a quality-of-service check (e.g. duplicate or out-of-order) and there is no ReplyTo address to which we can send a fault. Thus, we'll completely abort the processing of this request in order to indicate the failure to the sender.

Action: Send requests according to the quality-of-service requirements of the service.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00013: Could not find sequence {0} on {1} side

Cause: No sequence with the given identifier exists on the given side of the RM message exchange.

Action: Specify a different sequence identifier in the protocol message or contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00014: WsrmClient feature not enabled on this port/stub

Cause: A Port/Dispatch instance was used as if it referenced a reliable service, but the service is in fact not reliable (no WS-RM policy attached to it).

Action: Make the target service reliable (by attaching WS-RM policy to it) or pick a different target service.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00015: Cannot call {0} on a sequence that has not yet been fully initialized (no destination sequence ID or CreateSequenceResponse received yet). Source sequence ID: {1}

Cause: You've called a WsrmClient method to interact with the sequence before calling (or getting a true result) from WsrmClient.isInitialized().

Action: Please wait until you have completed a synchronous reliable invocation or have gotten true from WsrmClient.isInitialized before calling such a method.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00016: Got a message using the wrong WS-RM version for action {0}. Expected {1} but got {2}.

Cause: An RM sequence was negotiated using one version of the RM protocol, and a subsequent message was received indicating a different version.

Action: Make sure all messages related to a given sequence use the same RM protocol version.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00017: An unexpected error occurred: {0}

Cause: An unexpected exception has occurred.

Action: Contact technical support.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00018: ClientIdentityFeature not enabled or clientId not specified on this port/stub. This is required for WS-RM to track requests and responses for this client.

Cause: A Port/Dispatch instance was created without specifying an 'identity' via the ClientIdentityFeature JAX-WS feature when RM requires such an identity.

Action: Add a ClientIdentityFeature when creating your Port/Dispatch stub instance, and make sure that feature has its clientId field set to a unique, repeatable client ID.
Level: 1

Type: SEVERE

Impact: WebService

WSEE-RM-00019: No ReliabilityErrorListener provided via WsrmClient for a Port/Dispatch instance {0}. The sequence started on the Port/Dispatch instance encountered the following error: {1}

Cause: A Port/Dispatch instance was created without specifying an 'error listener' via the WsrmClient interface. Subsequently, a WS-RM sequence being managed on that Port/Dispatch instance encountered an error and could not notify the client of this error directly.

Action: Add a ReliabilityErrorListener on the Port/Dispatch instance by calling WsrmClient.setErrorListener().
Level: 1

Type: WARNING

Impact: WebService

64 WSM-00001 to WSM-09029

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 unmarshalled 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: Login Exception: {0}.

Cause: Login Exception at OPSS.

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-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: Message is not compliant with timestamp requirement of the policy. Timestamp element is required by policy but it is not present in the message.

Cause: Policy compliance failed due to timestamp. Timestamp element is required by policy but it is not present in the message.

Action: Check the message and make sure message is compliant with timestamp requirement of the service policy.
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 message.

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 retrieve 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. Ensure that the above key exists in the credential store. 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 in request. 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 initializing 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. Check your keystore configurations.

Cause: Keystore was not properly configured.

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. It is missing the Created time.

Cause: Valid timestamp was not present in the message. It was missing the Created time.

Action: Ensure the timestamp element conforms to the specifications.
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 WSM configuration system for the configured value of 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 WSM configuration system for the configured values of clock skew and 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 the domain level 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 domain level configuration or through policy configuration override.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00146: Keystore type {0} defined using keystore.type property in the domain level 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 the domain level 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 WSM configuration system.
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 WSM configuration system.
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 : {0}.

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 values 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: Invalid 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: Asymmetric 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 algorithm 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 asymmetric proof 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 wsm configuration system .

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 the domain level configuration

Cause: Keystore name property value was not set through the domain level configuration.

Action: Make sure that the value is provided for keystore name through the domain level configuration.
Level: 1

Type: ERROR

Impact: Security

WSM-00237: KSS keystore with URI {0} can not be loaded due to {1}.

Cause: The following KSS keystore-related configuration properties may not be valid:keystore.type, location. 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 KSS keystore. Grant necessary permission to read KSS keystore with URI {0}

Cause: KKS keystore may have not been initialized or necessary permissions are not granted.

Action: Ensure that necessary permission to read KSS keystore is granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00239: KSS trust store can not be loaded, ensure that necessary permissions are granted.

Cause: KSS trust store can not be loaded, probably necessary permissions are not granted.

Action: Ensure that necessary permission to read KSS trust store is granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00240: KSS trust store is NULL, ensure that KSS system trust store exist.

Cause: KSS trust store is NULL, may be it doesn't exists or probably necessary permissions are not granted.

Action: Ensure that KSS trust store exists in system stripe and permissions are granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00241: Failure retrieving KSS trust store aliases.

Cause: KSS 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 KSS keystore. Grant necessary permission to read alias {1} from KSS keystore with URI {0}

Cause: Unable to read key from KSS keystore. KSS 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 KSS keystore. Grant necessary permission to read certificate alias {1} from KSS keystore with URI {0}

Cause: Unable to read certificate from KSS keystore. KSS 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 KSS key store aliases.

Cause: Unable to list alias from KSS 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 message is expired. Check the timestamp element in the message. 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 {4} seconds, configured clock skew is {3} seconds. The acceptable time range is "{1}" to "{2}". The incoming message is outside the valid range as allowed by clock skew and expiry times.

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 maps that are used to retrieve property are:- "{1}". The properties found in the JPS config are <PropertyName: Value>:- {2}

Cause: The property value is null.

Action: Make sure that the value provided either through policy configuration override, policy binding, or domain level 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-00267: Authentication token specified in the policy for re-authenticate in secure conversation is not supported. Only SAML token is supported currently.

Cause: Authentication token specified in the policy for re-authenticate in secure conversation is not supported.

Action: Only SAML token is supported as of now.
Level: 1

Type: ERROR

Impact: Configuration

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 supported.

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-00280: Caching of STS client executor failed which is required for secure conversation.

Cause: Caching of STS client executor failed which is required for se cure conversation.

Action: Check error logs for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-00281: Failed to calculate session id for user {0}, due to {1}

Cause: Failed to calculate session id for user.

Action: Check error logs for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-00282: Failed to calculate session id for user {0} because required credential "{1}" is NULL.

Cause: Failed to calculate session id because required credential is NULL.

Action: Make sure that all required credentials are set.
Level: 1

Type: ERROR

Impact: Security

WSM-00283: Failed to create token context required for secure conversation due to {0}

Cause: Failed to create token context which is required for secure conversation.

Action: Check logs for finding out exact reason of failure.
Level: 1

Type: ERROR

Impact: Security

WSM-00284: Failed to send secure conversation bootstrap request.

Cause: Failure occurred while trying to send secure conversation bootstrap request message, possibly due to a failure in security code.

Action: Check logs for finding out exact reason of failure.
Level: 1

Type: ERROR

Impact: Security

WSM-00285: Failed to issue secure conversation token due to : {0}.

Cause: Failed to issue secure conversation token.

Action: Check logs for finding out exact reason of failure.
Level: 1

Type: ERROR

Impact: Security

WSM-00286: Failed to renew secure conversation token.

Cause: Failed to renew secure conversation token.

Action: Check logs for finding out exact reason of failure.
Level: 1

Type: ERROR

Impact: Security

WSM-00287: Failed to cancel secure conversation token.

Cause: Failed to cancel secure conversation token.

Action: Check logs for finding out exact reason of failure.
Level: 1

Type: ERROR

Impact: Security

WSM-00288: SecurityContextToken required for secure conversation not found. You might have not enabled secure conversation on other side.

Cause: SecurityContextToken required for secure conversation not found.

Action: Make sure that valid SCT is used for signing and encryption of message. You might have not enabled secure conversation on other side.
Level: 1

Type: ERROR

Impact: Security

WSM-00289: SecurityContextToken version used for secure conversation is not matching with expected version. Expected : {0} but found namespace: {1}

Cause: SecurityContextToken version used for secure conversation is not matching with expected version.

Action: Check documentation for supported WS Secure conversation version.
Level: 1

Type: ERROR

Impact: Security

WSM-00290: SecurityContextToken version "{0}" used for secure conversation is not supported.

Cause: SecurityContextToken version used for secure conversation is not supported.

Action: Check documentation for supported WS Secure conversation version.
Level: 1

Type: ERROR

Impact: Security

WSM-00291: Failed to add addressing header to the secure conversation bootstrap message.

Cause: Failed to add addressing headers when creating secure conversation bootstrap message.

Action: Check logs for finding out exact reason of failure.
Level: 1

Type: ERROR

Impact: Security

WSM-00292: sc.lifetime property value given in secure conversation policy is not valid.

Cause: sc.lifetime property value "{0}" given in secure conversation policy is not valid.

Action: sc.lifetime should have valid integer value.
Level: 1

Type: ERROR

Impact: Security

WSM-00293: sc.lifetime property value given in domain configuration is not valid.

Cause: sc.lifetime property value "{0}" given in domain configuration is not valid.

Action: sc.lifetime should have valid integer value.
Level: 1

Type: ERROR

Impact: Security

WSM-00294: Secure Conversation token inclusion mechanism is not supported: {0}

Cause: Secure Conversation token inclusion mechanism is not supported.

Action: Make sure to use supported token inclusion mechanism.
Level: 1

Type: ERROR

Impact: Security

WSM-00295: Secure Conversation session has expired for SCT ID: {0}

Cause: Secure Conversation session has expired for SCT ID.

Action: Renew session.
Level: 1

Type: ERROR

Impact: Security

WSM-00296: Secure Conversation session not found in session manager for SCT ID: {0}

Cause: Secure Conversation session not found in session manager for SCT ID.

Action: Check logs for the exact reason.
Level: 1

Type: ERROR

Impact: Security

WSM-00297: Security Context Token in RSTR is null

Cause: Security Context Token in RSTR is null.

Action: Check logs for the exact reason.
Level: 1

Type: ERROR

Impact: Security

WSM-00298: Policy Reference URI(s) passed to dispatcher is empty.

Cause: Policy Reference URI(s) passed to dispatcher is empty.

Action: Check logs for the exact reason.
Level: 1

Type: ERROR

Impact: Security

WSM-00299: Exception is thrown by the Session Manager

Cause: Exception is thrown by the Session Manager.

Action: Check logs for the exact reason.
Level: 1

Type: ERROR

Impact: Security

WSM-00300: Invalid input to the Session Manager on {0}.

Cause: Invalid input to Session Manager.

Action: Check logs for the exact reason.
Level: 1

Type: ERROR

Impact: Security

WSM-00301: Error in creating session id since the reference resource pattern is null

Cause: Error in creating session id since the reference resource pattern is null

Action: Check logs for the exact reason.
Level: 1

Type: ERROR

Impact: Security

WSM-00302: Error in creating session id since the service URL in message context is null

Cause: Error in creating session id since the service URL in the message context is null

Action: Check logs for the exact reason.
Level: 1

Type: ERROR

Impact: Security

WSM-00303: Secure conversation is unsupported for the assertion {0}. The policy file should be checked to not have secure conversation "on" for this assertion.

Cause: Secure conversation is unsupported for this assertion.

Action: Check your policy
Level: 1

Type: ERROR

Impact: Security

WSM-00304: Message does not contain client entropy which is required by service policy.

Cause: Message does not contain client entropy while server policy requires it.

Action: Check your client policy and make sure require-client-entropy is enabled on it.
Level: 1

Type: ERROR

Impact: Security

WSM-00305: Session ID "{0}" removed from session manager because BadContextToken received. This happens because SecurityContextToken sent from client is not accepted by service which can be due to the time difference between client and service being more than configured clock skew and it can also happen if service is not using session persistence while client is.

Cause: BadContextToken fault received which is due to invalid or expired SecurityContextToken (SCT). This happens because SCT sent from client is not accepted by service which can be due to the time difference between client and service being more than configured clock skew and it can also happen if service is not using session persistence while client is.

Action: Replay message again which will go through fine because dead session has been cleaned. Make sure that client and server clocks are synchronized properly or set correct clock skew. Also make sure that server and client are both configured with compatible session manager providers.
Level: 1

Type: ERROR

Impact: Security

WSM-00306: The derived keys security token could not be obtained from the message.

Cause: The Derived keys could not be located

Action: Either turn off the use-derived-keys flag or provide the derived keys in the message.
Level: 1

Type: ERROR

Impact: Security

WSM-00307: Client Credential did not get delegated to the Service.

Cause: Client Credential did not get delegated to the Service.

Action: Make sure the Kerberos configuration file on the client supports credential delegation.
Level: 1

Type: ERROR

Impact: Security

WSM-00308: Conflicting client credential available from Config-Override and Credential Delegation.

Cause: Conflicting client credential available from Config-Override and Credential Delegation.

Action: Either remove the client side config-overrides for Caller Principal Name and Keytab location or disable credential delegation.
Level: 1

Type: ERROR

Impact: Security

WSM-00309: HTTP SPNEGO Authorization Header is missing in the request.

Cause: HTTP SPNEGO Authorization Header is missing in the request.

Action: Client must provide a valid Authorization header for SPNEGO.
Level: 1

Type: ERROR

Impact: Security

WSM-00310: Client Credential not available.

Cause: Client Credential not available.

Action: Either provide caller principal name and keytab location or enable credential delegation if appropriate.
Level: 1

Type: ERROR

Impact: Security

WSM-00311: SAML over HTTP authentication failure.

Cause: Failure occurred in SAML over HTTP authentication.

Action: Use the appropriate GZIP and Base64 encoded combination of a valid SAML.
Level: 1

Type: ERROR

Impact: Security

WSM-00312: 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-00313: Could not obtain the certificate for the corresponding thumbprint

Cause: The certificate for the corresponding SKI could not be obtained

Action: Add the certificate to the Keystore.
Level: 1

Type: NOTIFICATION

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 key {1} is 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-00317: Required OES resource string is incomplete: application: {0}, resource_type: {1}, resource_name: {2}

Cause: Required OES resource string is incomplete.

Action: Ensure that all components of resource string is available either dynamially or using config overrides.
Level: 1

Type: ERROR

Impact: Security

WSM-00318: Required OES resource string is null because required resource pattern is null.

Cause: Required OES resource string is null because resource patterns is null.

Action: Ensure that resource pattern is available which is passed from web service stack.
Level: 1

Type: ERROR

Impact: Security

WSM-00319: Error while populating attributes for OES authorization. Actual error message is: {0}

Cause: Error occured while populating attributes for OES authorization.

Action: Check logs for actual cause of error.
Level: 1

Type: ERROR

Impact: Security

WSM-00320: PEPException has occurred while making authorization call to PDP using PEP API.

Cause: Error occured while invoking OES's authorization engine using PEP API.

Action: Check logs for actual cause of PEP APIs failure.
Level: 1

Type: ERROR

Impact: Security

WSM-00321: XPath attributes configured for fine-grained authorization will be ignored because no valid XML message found in current payload.

Cause: XPath attributes are being ignored because no SOAP message or XML msg found in current payload.

Action: SOAP message should have valid envelope or if its SOA then XML request message should be available.
Level: 1

Type: WARNING

Impact: Security

WSM-00322: Error occurred while evaluating XPath query. XPath query will be ignored. Specific error is: {0}

Cause: Error while evaluating XPath query. Query is being ignored.

Action: Check logs if there is any error or XPath query may not be valid for current XML payload.
Level: 1

Type: WARNING

Impact: Security

WSM-00323: STS {0} obtained from WSDL is {1}. Local STS configuration is also not available.

Cause: STS (issuer) uri is not available in the WSDL or client side STS configuration.

Action: Ensure that STS trust config policy is attached to either the client or the service.
Level: 1

Type: ERROR

Impact: Security

WSM-00324: Automatic (Client) Policy Configuration failed to determine a compatible client side policy to communicate with the STS at {0}.

Cause: Automatic (Client) Policy Configuration failed to determine compatible client side policy to communicate with STS.

Action: Ensure that STS trust config service policy is attached and is configured with the correct issuer uri.
Level: 1

Type: ERROR

Impact: Security

WSM-00325: The protocol "{0}" set in the token configuration for the token to be cached is not recognized. If the problem persists, contact Oracle Support Services.

Cause: The protocol set in the token configuration for the token to be cached is not recognized.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WSM-00326: The client clock skew value should not be negative

Cause: Invalid client clock skew value.

Action: Change client clock skew to a positive value.
Level: 1

Type: ERROR

Impact: Security

WSM-00327: Incoming request did not have a valid authentication token. Service will send a 401 Challenge in response to the client with WWW-Authenticate header.

Cause: Incoming request did not have a valid authentication token.

Action: Service will send a 401 Challenge in response to the client. Client should understand the authentication scheme and re-send the request with required token.
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00328: The XPath expression {0} is not valid.

Cause: The XPATH expression could not be evaluated for the SOAP/XML Message. It could be because the xpath is not following xpath syntax.

Action: THe XPATH expression is not valid, correct the XPATH and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00329: The PII for the xpath {0} to be encrypted is already encrypted.

Cause: The PII Node to be encrypted is already encrypted. It could be because the same XPATH is being used twice or the message already had PII encrypted

Action: Check if the same XPATH is being used again. There is some place where the PII policy should have been attached but was not attached properly.
Level: 1

Type: ERROR

Impact: Security

WSM-00330: The XPATH {0} used to configure the PII does not result in TEXT_NODE.

Cause: The PII Xpath did not return a TEXT_NODE. If the Xpath does not return a TEXT_NODE then it is not a Supported XPATH

Action: Rectify the XPATH configured for the PII so that it returns a TEXT_NODE.
Level: 1

Type: ERROR

Impact: Security

WSM-00331: The key used to encrypt/decrypt PII could not derived.

Cause: The Secret Key for PII could not be derived. The policy is not configured properly

Action: Rectify the PII configuration so that the secret key can be generated.
Level: 1

Type: ERROR

Impact: Security

WSM-00332: The resource pattern is not configured properly.

Cause: The Resource Pattern is null.

Action: The ResourcePattern should be properly configured.
Level: 1

Type: ERROR

Impact: Security

WSM-00333: The PII policy is not supported on the SubjectType: {0}

Cause: PII Policy not supported on this SubjectType.

Action: Dettach the PII policy from this subject as it is not supported here.
Level: 1

Type: ERROR

Impact: Security

WSM-00334: The PII denoted by xpath {0} was encrypted in {1}, but was being decrypted in {2}, which is not allowed.

Cause: PII encrypted in one entity and decrypted in a different entity.

Action: Attach the decrypt policy in the earlier entity, so that PII gets decrypted in the same entity where it was encrypted.
Level: 1

Type: ERROR

Impact: Security

WSM-00335: Anonymous user found in the SAML assertion so anonymous subject has been created. Trusted issuers validation, DN list validation and other validations related to SAML token will be skipped. Subject: {0}

Cause: Anonymous user found in the SAML assertion so anonymous subject has been created. Trusted issuers validation, DN list validation and other validations related to SAML token will be skipped.

Action: If anonymous user was not expected in token then check client's configuration.
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00336: Anonymous user is being propagated as subject is {0}.

Cause: Anonymous user is being propagated as subject is either NULL or anonymous.

Action: Check client's configuration if anonymous user should not be propagated.
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00338: Error creating OPSS subject from username and policy context.

Cause: A failure occurred while creating OPSS subject from username and policy context.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00339: Error creating anonymous subject.

Cause: A failure occurred while creating anonymous subject.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00340: The key for the alias {0} not found in the KSS Keystore {1}. The following aliases are found in the Keystore: {2}

Cause: Key does not exist in the KSS keystore.

Action: Ensure that alias exists in keystore and necessary permission to read key alias is granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00341: SAML assertion signature digest verification failed

Cause: SAML assertion signature verification failed.

Action: Ensure that SAML assertion signature is valid.
Level: 1

Type: ERROR

Impact: Security

WSM-00342: Certificate/Key with subject DN "{0}" has expired.

Cause: Certificate/Key has expired.

Action: Get a new certificate/key.
Level: 1

Type: WARNING

Impact: Security

WSM-00343: Could not get new Kerberos TGT and current TGT has expired.

Cause: Could not get new Kerberos TGT and current TGT has expired.

Action: Check logs for the reason of failure. Principal and password (for example using keytab) must be available for login.
Level: 1

Type: ERROR

Impact: Security

WSM-00344: Failed to authorize user request for {0}. {1}

Cause: Failed to authorize user request.

Action: Check logs for the reason of failure and also check if required premission is granted.
Level: 1

Type: ERROR

Impact: Security

WSM-00345: Failed to decrypt the encrypted key at client side due to {0}. Ensure that the client is configured with sign key as crypt key.

Cause: An error occurred while decrypting the encrypted key at client side.

Action: Ensure that the client is configured with the sign key as crypt key.
Level: 1

Type: ERROR

Impact: Security

WSM-00346: There is no matching assertion found in the service side policy which can process the incoming message. Ensure that there is a compatible policy attached at the client side. Tokens found in the security header are:- {0}. Authentication mechanism found in the HTTP header:- {1}. The assertions found in the service side policy are:- {2}.

Cause: No matching assertion found in the service side policy which can process the incoming message.

Action: Ensure that a compatible client policy is attached and enabled at the client side.
Level: 1

Type: ERROR

Impact: Security

WSM-00347: The request message contains the Derived Keys but service side policy is not configured to use Derived Keys for message decryption. Ensure that the service side policy is configured to use Derived Keys.

Cause: The request message contains the Derived Keys but service side policy is not configured to use Derived Keys for message decryption.

Action: Ensure that the service side policy is configured to use Derived Keys.
Level: 1

Type: ERROR

Impact: Security

WSM-00348: EncrytpedData element found inside the ReferenceParameters element. This might result in security vulnerabilities, so removing its data reference "{0}" from the reference list to avoid decryption of any EncrytpedData element inside the ReferenceParameters element. Ensure that the entire ReferenceParameters element is either encrypted or without any EncrytpedData element.

Cause: EncrytpedData element found inside the ReferenceParameters element. This might result in security vulnerabilities.

Action: Ensure that the entire ReferenceParameters element is either encrypted or without any EncrytpedData element.
Level: 1

Type: WARNING

Impact: Security

WSM-00349: The HTTP header is missing in the incoming client request message. Service will send back a 401 Challenge to the client with response header {0}: {1}.

Cause: Incoming request did not have any authentication token in the HTTP header.

Action: Service will send back a 401 Challenge to the client. Client should understand one of the authentication schemes and re-send the request with one of the supported authentication token.
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00350: The name attribute for the token issuer trust document is not found.

Cause: The name attribute for the token issuer trust document is not found.

Action: Make sure the name is provided when creating a token issuer trust document.
Level: 1

Type: ERROR

Impact: Security

WSM-00351: The tokentype attribute "{0}" for the Issuer in token issuer trust document is not supported.

Cause: The tokentype attribute for the Issuer in the token issuer trust document is not supported.

Action: Change it to a supported token type when creating the Issuer in token issuer trust document.
Level: 1

Type: ERROR

Impact: Security

WSM-00352: The keytype attribute "{0}" for a trusted key for an Issuer in the token issuer trust document is not supported.

Cause: The keytype attribute for a trusted key for an Issuer in the token issuer trust document is not supported.

Action: Change it to a supported key type when creating the trusted key for the Issuer in token issuer trust document.
Level: 1

Type: ERROR

Impact: Security

WSM-00353: The valuetype attribute "{0}" for a trusted key for an Issuer in the token issuer trust document is not supported.

Cause: The valuetype attribute for a trusted key for an Issuer in the token issuer trust document is not supported.

Action: Change it to a supported key valuetype when creating the trusted key for the Issuer in token issuer trust document.
Level: 1

Type: ERROR

Impact: Security

WSM-00354: The attribute "{0}" for which the filter is configured in a token attribute rule is not supported.

Cause: The attribute for which the filter is configured in a token attribute rule is not supported.

Action: Set the filter only for supported attributes in a token attribute rule.
Level: 1

Type: ERROR

Impact: Security

WSM-00355: Name Id "{0}" in the token is not allowed by the token attribute rule for the DN "{1}".

Cause: Token Name ID validation for the DN failed.

Action: Name ID value is not allowed for the DN of token signing certificate. Make sure a valid user is sent.
Level: 1

Type: ERROR

Impact: Security

WSM-00356: Failed to enforce token attribute rule "{0}" configured for the DN "{1}" of the signing certificate.

Cause: Token attribute rule configured for the DN of the signing certificate failed.

Action: Check logs for the details. Either rule is not configured properly or token does not has required details to enforce it.
Level: 1

Type: ERROR

Impact: Security

WSM-00357: Token attribute rule identifier "{0}" is not associated with any trusted key of a trusted token issuer.

Cause: Token attribute rule identifier "{0}" is not assocoated with any trusted key of a trusted token issuer.

Action: Check the identifier to make sure it matches the key identifier value of a trusted key for an trusted issuer configured.
Level: 1

Type: ERROR

Impact: Security

WSM-00358: SAML assertion signature reference is pointing to invalid URI

Cause: SAML assertion signature reference is pointing to invalid URI .

Action: Ensure that SAML assertion signature is valid
Level: 1

Type: ERROR

Impact: Security

WSM-00359: Instance tenancy is not available but used as property value: "{0}"

Cause: Instance tenancy is not available.

Action: Make sure that instance tenancy is available or don't use that property if not required.
Level: 1

Type: ERROR

Impact: Security

WSM-00360: Tenant name set in configuration property "{0}" does not match with tenancy: "{1}" of current subject.

Cause: Tenant name set in configuration property does not match with current subject's tenancy.

Action: Make sure that tenant name set as configuration property matches with current subject's tenant name.
Level: 1

Type: ERROR

Impact: Security

WSM-00361: The SAML HOK token found in the incoming message does not contain the KeyInfo element. Make sure that the incoming message contains a valid SAML HOK assertion and contains the KeyInfo element.

Cause: The SAML HOK assertion found in the incoming message does not contain the KeyInfo element.

Action: Insert valid SAML HOK assertion containing the KeyInfo element and resend the request.
Level: 1

Type: ERROR

Impact: Security

WSM-00362: The SAML HOK token found in the incoming message does not contain the KeyValue element. Make sure that the incoming message contains a valid SAML HOK assertion and contains the KeyValue element.

Cause: The SAML HOK token found in the incoming message does not contain the KeyValue element.

Action: Insert valid SAML HOK token containing the KeyValue element and resend the request.
Level: 1

Type: ERROR

Impact: Security

WSM-00363: The SAML token found in the incoming message is not valid. Both AttributeStatement and AuthenticationStatement elements are missing from the SAML assertion.

Cause: The SAML token found in the incoming message is not valid. Both AttributeStatement and AuthenticationStatement elements are missing from the SAML assertion.

Action: Insert valid SAML token and resend the request.
Level: 1

Type: ERROR

Impact: Security

WSM-00364: JWT token has expired

Cause: JWT token received after the token has expired.

Action: Fix the expiry claim and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00365: JWT token issuer - "{0}" is not trusted. Configured trusted issuers are "{1}"

Cause: JWT token issuer is not trusted.

Action: Fix the issuer claim and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00366: JWT symmetric key "{0}" is not trusted

Cause: JWT key id is not trusted.

Action: Fix the symmetric key and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00367: JWT certificate DN "{0}" is not trusted

Cause: JWT certificate DN is not trusted.

Action: Fix the JWT certificate and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00368: JWT x5t claim is invalid

Cause: Cannot find certificate matching the JWT x5t claim.

Action: Fix the JWT x5t claim and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00369: JWT signature csf key is not configured

Cause: Cannot find JWT signature csf key.

Action: Fix the JWT signature csf key and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00370: JWT token is not signed

Cause: JWT token is not signed.

Action: Sign the JWT token and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00371: JWT signature algorithm mismatch, expecting "{0}", found "{1}"

Cause: JWT signature algorithm does not match policy.

Action: Fix the JWT signature algorithm and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00372: Unsupported signature algorithm specified

Cause: An unsupported signature algorithm was provided.

Action: Consult the documentation for the supported signature algorithms and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00373: JWT audience claim - "{0}" is invalid. Correct value is "{1}"

Cause: JWT audience claim is invalid

Action: Fix the audience claim to match the resource and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00374: JWT issued time claim is invalid

Cause: JWT token received before the issued time.

Action: Fix the issued time claim and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00375: Unable to determine user tenant name in multi-tenant environment

Cause: Unable to determine user tenant name in multi-tenant environment.

Action: Ensure that the user tenant name is set.
Level: 1

Type: ERROR

Impact: Security

WSM-00376: SAML token authentication failed for issuer "{0}"

Cause: SAML token based authentication failed.

Action: SAML token based authentication failed. Check logs for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-00377: {0}. This error is most likely due to secure conversation not enabled at the service side policy

Cause: Secure conversation is not enabled at the service side policy.

Action: Disable secure conversation at the client side policy and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00378: Incoming Kerberos token has an invalid/unsupported Value Type: {0} : {1}

Cause: The value type of the incoming Kerberos token did not match the expected type at service side.

Action: Make sure client sends the Kerberos token of value type as expected by service policy.
Level: 1

Type: ERROR

Impact: Security

WSM-00379: There are no Xpath transformations allowed inside CipherReference in EncryptedKey. To allow all the Xpath transformations, set the property {0} to true.

Cause: No Xpath transformations are supported inside CipherReference in EncryptedKey which are present in the incoming SOAP message.

Action: Do not include any XPATH transformations inside CipherReference
Level: 1

Type: ERROR

Impact: Security

WSM-00380: An Exception was thrown while retreiving the keystore password from the credential store.

Cause: The Keystore password was not retrieved

Action: Check if the keystore password is configured correctly.
Level: 1

Type: ERROR

Impact: Security

WSM-00381: Alias "{0}" is not valid for the keystore entry.

Cause: Alias doesn't point to any trusted certificate or a private key entry.

Action: Ensure that alias either points to any trusted certificate or a private key entry and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00382: An Exception was thrown while loading the keystore, only JKS type keystores are supported by the oracle.wsm.security.store.jks.mgmt.KeystoreMBean.

Cause: Keystore MBean only support JKS type keystore.

Action: Consult the oracle documentation to ensure that keystore.type that is configured is of type JKS for the oracle.wsm.security.store.jks.mgmt.KeystoreMBean.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00383: Failed to initialize JKS Mbean auditor.

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: Security

WSM-00384: Alias "{0}" points to a certificate which is not a trusted certificate.

Cause: Alias already exists but does not identify an entry containing a trusted certificate.

Action: Check that a trusted certificate already exists for the given alias and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00385: Alias "{0}" does not point to a valid private key entry in the keystore.

Cause: Alias doesn't point to a private key entry.

Action: Ensure that alias points to a private key entry in the keystore.
Level: 1

Type: ERROR

Impact: Security

WSM-00386: Invalid type argument "{0}". Valid values are "Certificate" and "PKCS7".

Cause: Invalid type argument. Valid values are "Certificate" for single certificate and "PKCS7" for certificate chain.

Action: Ensure that either "Certificate" or "PKCS7" is passed as type argument.
Level: 1

Type: ERROR

Impact: Security

WSM-00387: No trusted certificate identified by alias "{0}".

Cause: No trusted certificate entry identified by the alias.

Action: Ensure that alias points to a trusted certificate and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00388: Certificate deletion failed for "{0}" alias(es).

Cause: An error occurred while deleting the alias.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WSM-00389: Public key entry of the certificate to be imported does not match the existing public key entry in the keystore for alias "{0}".

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: ERROR

Impact: Security

WSM-00390: Failed to retrieve Private key entry for alias "{0}" due to invalid password.

Cause: Failed to retrieve private key entry due to invalid password.

Action: Ensure that correct password is used to import/set the certificate.
Level: 1

Type: ERROR

Impact: Security

WSM-00391: Creating certificate from base64 encoded string failed for alias "{0}".

Cause: Encountered error while creating certificate from base64 encoded string.

Action: Must provide valid certificate in valid base64 encoded string.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00392: Failed to store keystore to the file system.

Cause: Encountered error while storing the keystore to the file system.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00393: Permission "{0}" required to access the application specific CSF map "{1}" is not granted to the resource "{2}". Underlying exception message : "{3}"

Cause: Permission required to access application specific credential map is not granted.

Action: Grant permission for accessing application specific credential map to the codesource and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00394: The given name "{0}" for permission "{1}" with action "{2}" is not supported target format. If action is "assert", supported target format is resource={RESOURCENAME}. If action is "getKey", supported target format is resource={RESOURCENAME},mapName={CSF_MAP_NAME}.

Cause: The target format of the specified WSIdentityPermission is not supported.

Action: Correct the supported target terms for WSIdentityPermission and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00395: The action "{0}" is not supported for permission "{1}".

Cause: The action of the specified WSIdentityPermission is not supported.

Action: Correct the supported actions for WSIdentityPermission and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00396: JKS "{0}" audit operation failed.

Cause: Encountered error while auditing JKS operation.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00397: JKS Mbean registration failed.

Cause: JKS Mbean registration failed.

Action: Check logs for actual cause of Mbean registration failure.
Level: 1

Type: ERROR

Impact: Security

WSM-00398: The OAuth2 policy configuration property token-uri has an invalid value of "{0}". The value must point to a valid Oauth token endpoint and should be specified in the form "http(s)://host:port/tokens"; it should not be a null or empty string.

Cause: OAuth2 config attribute token-uri is either null, empty or not in the format of "http(s)://host:port/tokens".

Action: Provide valid attribute value for Oauth token endpoint which is in the format of "http(s)://host:port/tokens".
Level: 1

Type: ERROR

Impact: Configuration

WSM-00399: OAuth2 request sent to OAuth2 server failed with Message : "{0}". Please check OAuth2 server logs for more details.

Cause: OAuth2 token request failed

Action: Check the OAuth2 Server logs and exception stack trace to determine why the request failed.
Level: 1

Type: ERROR

Impact: Security

WSM-00400: OAuth2 server responded with status : "{0} {1}", error : "{2}". Please check OAuth2 server logs for more details.

Cause: OAuth2 server responded with error message and bad request

Action: Check the error message returned by OAuth2 server to determine why the request was rejected.
Level: 1

Type: ERROR

Impact: Security

WSM-00401: JWT signature verification failed.

Cause: JWT Signature verification failed

Action: Fix the JWT token or import the right trusted issuer certificate and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00402: JWT kid "{0}" claim is not valid. Certificate mathcing the kid claim does not exist in OWSM trust store.

Cause: Cannot find certificate matching the JWT kid claim.

Action: Fix the JWT kid claim or import the certificate in OWSM trust store and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00403: oauth2_config_client_policy is not found. Attach it using GPA or LPA.

Cause: The oauth2_config_client_policy is not attached.

Action: Check the configuration and attach oauth2_config_client_policy using GPA or LPA.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00404: Provide valid value for oauth2.client.csf.key config override.

Cause: oauth2.client.csf.key config override is missing.

Action: Provide valid value for oauth2.client.csf.key after adding entry in CSF.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00405: Add a CSF entry with client id

Cause: oauth2.client.csf.key config override does not point to a valid entry

Action: Add an entry in CSF corresponding to oauth2.client.csf.key.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00406: Configure redirect.uri for 3-legged OAuth

Cause: redirect.uri config override does not point to a valid value

Action: Configure redirect.uri in the config override
Level: 1

Type: ERROR

Impact: Configuration

WSM-00407: Invalid policy alternatives found inside XOR policy operator. It contains two or more message protection assertions ({0}, {1}) which have same authentication token type.

Cause: Invalid policy alternatives found inside XOR policy operator. It contains two or more message protection assertions which have same authentication token type.

Action: Ensure that you have only one message protection assertion with same authentication token type in the XOR policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00408: Invalid policy alternatives found inside XOR policy operator. It contains two or more non message protection or SSL assertions ({0}, {1}) which have same authentication token type.

Cause: Invalid policy alternatives found inside XOR policy operator. It contains two or more non message protection or SSL assertions which have same authentication token type.

Action: Ensure that you have only one non message protection assertion with same authentication token type in the XOR policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00409: Invalid policy alternatives found inside XOR policy operator. It contains more than one of x509, anonymous or custom authentication token type ({0}, {1}).

Cause: Invalid policy alternatives found inside XOR policy operator. It contains more than one of x509, anonymous or custom authentication token type.

Action: Ensure that you have only one of either x509, anonymous or custom authentication token types in the XOR policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00410: Invalid policy alternatives found inside XOR policy operator. It contains two or more secure conversation enabled message protection assertions ({0}, {1}) which have same authentication token type.

Cause: Invalid policy alternatives found inside XOR policy operator. It contains two or more secure conversation enabled message protection assertions which have same authentication token type.

Action: Ensure that you have only one secure conversation enabled message protection assertion with same authentication token type in the XOR policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00411: Invalid policy alternatives found inside XOR policy operator. It contains two or more secure conversation enabled SSL assertions ({0}, {1}) which have same authentication token type.

Cause: Invalid policy alternatives found inside XOR policy operator. It contains two or more secure conversation enabled SSL assertions which have same authentication token type.

Action: Ensure that you have only one secure conversation enabled SSL assertion with same authentication token type in the XOR policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00412: Invalid policy alternatives found inside XOR policy operator. It contains more than one secure conversation enabled assertion with either x509, anonymous or custom authentication token types ({0}, {1}).

Cause: Invalid policy alternatives found inside XOR policy operator. It contains more than one secure conversation enabled assertion with x509, anonymous or custom authentication token type.

Action: Ensure that you have only one secure conversation enabled assertion with either x509, anonymous or custom authentication token types in the XOR policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00413: Invalid policy alternatives found inside XOR policy operator. It contains two or more message protection assertions which have different values for keystore.enc.csf.key ({0}, {1}).

Cause: Invalid policy alternatives found inside XOR policy operator. It contains two or more message protection assertions which have different values for keystore.enc.csf.key property.

Action: Ensure that you have same value for keystore.enc.csf.key for all message protetcion assertions
Level: 1

Type: ERROR

Impact: Configuration

WSM-00414: DMS string not available in ClientConfig properties. Setting dummy value for OWSM agent initialization. Monitoring will not work for subject identified by {0}

Cause: DMS string not available in ClientConfig properties.

Action: Set the WSMExecutionConstants.AGENT_TOPOLOGYNODE_PATH proeprty with a String value in the ClientConfig object of the Jersey Client.
Level: 1

Type: WARNING

Impact: Security

WSM-00415: The value of algorithm suite,"{0}" used in the JWT assertion is not valid. The only valid value to be used is "{1}".

Cause: The algorithm suite specified in the policy is not supported by JWT policies. Only Asymmetric key signature is supported at this time.

Action: Make sure that a valid value of algorithm-suite is provided in the JWT assertion.
Level: 1

Type: ERROR

Impact: Security

WSM-00416: The current server time is "{0}", incoming message creation time is "{1}", incoming message expiry time is "{2}" , configured clock skew is "{3}" seconds. The acceptable time range is "{4}" to "{5}". The incoming token is outside the valid range as allowed by clock skew and expiry times.

Cause: The incoming message is outside the valid range as allowed by clock skew and expiry times.

Action: Make sure the token is not expired. Check the allowed clock skew and configure them as required.
Level: 1

Type: ERROR

Impact: Security

WSM-00417: Alias "{0}" already exists in the Keystore.

Cause: Alias already points to trusted certificate or a private key entry.

Action: Ensure that alias do not already exist in the Keystore and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00418: Subject Name Identifier is missing in the SAML token. Check if the user identifier is properly set up to be included in the SAML assertion.

Cause: Subject Name Identifier is missing in the SAML token.

Action: Check if the user identifier is properly set up to be included in the SAML assertion.
Level: 1

Type: ERROR

Impact: Security

WSM-00419: Keystore properties updation failed due to {0}

Cause: Check nested error for failure

Action: Check nested error for fixing the issue
Level: 1

Type: ERROR

Impact: Security

WSM-00420: The key, {0}, is not retrieved due to exception "{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: 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-00421: The claim "{0}" contains null or empty value in the JWT token "{1}".

Cause: The claim contains empty or null value in the incoming JWT token.

Action: Make sure that the claim is present in the incoming JWT token.
Level: 1

Type: ERROR

Impact: Security

WSM-00422: Message is not compliant with timestamp requirement of the policy. Policy indicates that the timestamp element should not be present, but it is found in the message.

Cause: Timestamp policy compliance failed. Policy indicates that the timestamp element should not be present, but it is found in the message.

Action: Check the message and make sure message is compliant with timestamp requirement of the service policy.
Level: 1

Type: ERROR

Impact: Security

WSM-00423: Web service authentication failed.

Cause: Web Service Authentication failed at the server end.

Action: Resend valid credentials.
Level: 1

Type: ERROR

Impact: Security

WSM-00424: The init-param named servlet-name not found in the deployment descriptor. Skipping SecurityFilter initialization. OWSM SecurityFilter will not be enforced.

Cause: servlet-name init param for the OWSM security filter definition was missing from the application's web.xml.

Action: User must provide a value for the servlet-name init param of the filter definition in the web.xml for the OWSM Security Filter to be initialized.
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00425: The security header is missing in request. Ensure that there is a valid security policy attached at the client side, and the policy is enabled. And make sure timestamp is present in the security header.

Cause: Security header was expected but was not found.

Action: Security header is missing in request. It could be that client side policy has not been applied. Resend request with appropriate Security header. And make sure timestamp is present in the security header.
Level: 1

Type: ERROR

Impact: Security

WSM-00426: The security header is missing in response. Ensure that response message is compliant with security requirement of the client policy. And make sure timestamp is present in the security header.

Cause: Security header was expected but was not found.

Action: Security header is missing in response. The response message is not compliant with security requirement of the client policy. Check the response message sent by service. And make sure timestamp is present in the security header.
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 due to {0}.

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 overridden.

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, one or more PolicySets resource pattern are not same as that of the base, baseResourcePattern={0}, invalid input PolicySets= {1}

Cause: While validating the input PolicySet array to be merged, found policyset resourcepattern that is different than that of the base.

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: The ResourcePattern of the base runtime PolicySet for merging is null, basePolicySet={0}, input PolicySet array={1}. All PolicySet in the array should be either null, or has the same resource pattern as that of the base policy set and all callback policy sets should have the same resource pattern.

Cause: The ResourcePattern of the base runtime Policy Set for merging is null, possibly the base runtime Policy Set is constructed using empty Policyset() constructor.

Action: Make sure runtime PolicySet is created with not-null ResourcePattern.
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-01701: Cannot perform changes to the DOM document provided to the storage provider since its a read-only document.

Cause: WSM Assembly document could not be fetched for write operation.

Action: The WSM Assembly document provided to the storage provider does not support update. Provide a writeable DOM document and retry the operation.
Level: 1

Type: ERROR

Impact: Other

WSM-01702: A null WSM Assembly object cannot be marshalled.

Cause: An attempt was made to marshall a null WsmAssembly object.

Action: Provide a non-null WsmAssembly object.
Level: 1

Type: ERROR

Impact: Other

WSM-01703: Failed to retrieve descriptor identified by "{0}" in storage provider due to an exception

Cause: WSM descriptor document could not be fetched due to IOException.

Action: Check with logging for detail, and retry, if problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Other

WSM-01704: While advertising policies under subject "{0}", the specified web service with QName "{1}" does not exist in the wsdl; it may not be valid, make sure that namespace and local name of the service are correct.

Cause: The QName of the web service specified does not exist in the wsdl

Action: Verify the namespace and local name and make sure there are valid
Level: 1

Type: ERROR

Impact: Other

WSM-01705: While advertising policies under subject "{0}", the specified port name "{1}" does not exist under the service "{2}" in wsdl.

Cause: The port name specified does not exist in the servie of wsdl

Action: Verify the port name and make sure it is valid
Level: 1

Type: ERROR

Impact: Other

WSM-01706: A null node cannot be unmarshalled into an Intent object.

Cause: An attempt was made to unmarshall an intent from a null node.

Action: Provide a node that contains a marshalled intent.
Level: 1

Type: ERROR

Impact: Data

WSM-01707: A null node cannot be unmarshalled into an assertion metadata object.

Cause: An attempt was made to unmarshall assertion metadata from a null node.

Action: Provide a node that contains a marshalled assertion metadata.
Level: 1

Type: ERROR

Impact: Data

WSM-01708: Advertisement expression "{0}" for portable expression "{1}" is not valid.

Cause: The advertisment expression probably is not set correctly.

Action: Check the log and verify it is not null and confirm to the format.
Level: 1

Type: ERROR

Impact: Data

WSM-01709: The Runtime PolicySet cannot be advertised due to validation errors. PolicySet "{0}" validation errors: "{1}" .

Cause: Runtime PolicySet cannot be advertised due to validation errors.

Action: Check the logs and correct errors in the PolicySet.
Level: 1

Type: ERROR

Impact: Other

WSM-01710: The Policy "{0}" has following validation errors= "{1}".

Cause: Policy has validation errors.

Action: Check the logs and correct errors in the Policy.
Level: 1

Type: WARNING

Impact: Other

WSM-01711: One or more Callback PolicySets ResourcePattern are not the same. baseResourcePattern={0}, callbackPolicySetsHaveDifferentResourcePatterns= {1}. All PolicySet in the array should be either null, or has the same resource pattern as that of the base policy set and all callback policy sets should have the same resource pattern.

Cause: Found invalid PolicySet in the input PolicySet array to be merged.

Action: Make sure all PolicySet resource pattern in the array should be either null, or has the same resource pattern as that of the base policy set and all callback policy sets should have the same resource pattern.
Level: 1

Type: ERROR

Impact: Other

WSM-01712: While validating the input PolicySet array to be merged, input resource pattern subject type={0} is incompatible with that of base={1}, input policySet={2}.

Cause: While validating the input PolicySet array to be merged, input callback subject type is not compatible with that of the base.

Action: Input resource pattern should be either null, same as base, or a compatible callback type
Level: 1

Type: ERROR

Impact: Other

WSM-01713: A null node cannot be unmarshalled into a TimestampInfo object.

Cause: An attempt was made to unmarshall a TimestampInfo from a null node.

Action: Check the log and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-01714: A null TimestampInfo object cannot be marshalled.

Cause: An attempt was made to marshall a null TimestampInfo object.

Action: Check the log and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-01715: The current thread context class loaders "{0}" are unable to locate the OWSM seed policy JAR "{1}". URLs that have the searched resource "{2}" are "{3}".

Cause: The current thread classpath does not include the path to the wsm-seed-policies.jar.

Action: Check the log for detail info.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-01716: The current thread context class loader is unable to locate the OWSM seed policy JAR "{0}" by searching resource "{1}".

Cause: The current thread classpath does not include the path to the wsm-seed-policies.jar.

Action: Check the log and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01717: A null node cannot be unmarshalled into an PolicyReference object.

Cause: An attempt was made to unmarshal PolicyReference from a null node.

Action: Provide a node that contains a valid policy reference.
Level: 1

Type: ERROR

Impact: Data

WSM-01718: A null PolicyReference object cannot be marshalled.

Cause: An attempt was made to marshal a null PolicyReference object.

Action: Provide a non-null PolicyReference object.
Level: 1

Type: ERROR

Impact: Data

WSM-01719: Error while getting input stream for entry "{0}" from seed jar located at "{1}".

Cause: Error in reading jar entry from seed jar.

Action: Check the jar file and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-01720: Error while parsing entry "{0}" from seed jar located at "{1}".

Cause: Error in parsing file in seed jar.

Action: Remove the invalid file and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-01751: The name of an assertion property is empty.

Cause: The name of an assertion property was empty.

Action: Make sure that you specify a name for all assertion properties.
Level: 1

Type: ERROR

Impact: Data

WSM-01752: The data type of the value does not match the data type of property {0}. The expected data type is "string".

Cause: The datatype of the property value entered was not of type "string".

Action: Make sure that the data type for the property value is of type "string".
Level: 1

Type: ERROR

Impact: Data

WSM-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 make connection(WSMC) policies is not supported. Only one WSMC 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 is not supported for "{0}" type of Documents. Only a Policy, AssertionTemplate or PolicySet can be validated.

Cause: Validation is not supported for the type of Documents.

Action: Ensure that the document is either a Policy or a PolicySet or AssertionTemplate.
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-01787: The policy name {0} contains invalid characters.

Cause: The policy name contains invalid characters.

Action: Make sure that policy name contains valid characters.
Level: 1

Type: ERROR

Impact: Data

WSM-01788: The assertion template name {0} contains invalid characters.

Cause: The assertion template name contains invalid characters.

Action: Specify a valid value for the assertion template name.
Level: 1

Type: ERROR

Impact: Data

WSM-01789: Attaching multiple web service transaction(WSTX) policies is not supported. Only one WSTX policy can be attached to a policy subject.

Cause: More than one WSMC policy was attached to a policy subject.

Action: Make sure that only one make connection policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01790: 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 WSTX policy was attached to a policy subject.

Action: Make sure that only one reliable WSTX 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-01793: The OR group contains no assertions. Edit the OR group to include one or more assertions.

Cause: The OR group contains no assertions.

Action: Edit the OR group to include one or more assertions.
Level: 1

Type: ERROR

Impact: Data

WSM-01794: Combination of an oauth2-config policy and a non oauth2 client policy is not valid.

Cause: oauth2-config policy and non oauth2 policy was attached to a policy subject.

Action: Make sure that an oauth2-config policy and a non oauth2 config policy are not attached together to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01795: Attachment of an oauth2 config policy without any oauth2 client policy is invalid. Ensure you attach a valid oauth2 policy either via Direct Policy Attachment or via Global Policy Attachment along with an oauth2 config policy.

Cause: Oauth2 config policy was attached without oauth2 client policy to a policy subject.

Action: Make sure that an oauth2 config policy is attached together with a oauth2 policy to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01796: Attaching multiple Oauth2-Config policies is not supported. Only one Oauth2-Config policy can be attached to a policy subject.

Cause: More than one oauth2-config policy was attached to a policy subject.

Action: Make sure that only one oauth2-config policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01797: Attachment of an oauth2 client policy without oauth2 config policy is invalid. Ensure you attach a valid oauth2 config policy either via Direct Policy Attachment or via Global Policy Attachment along with an oauth2 client policy.

Cause: Oauth2 client policy was attached without oauth2-config policy to a policy subject.

Action: Make sure that a oauth2 config policy is attached together with a oauth2 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 or malformed. A function requires a non-empty, quoted value.

Cause: The argument for a function was missing, empty, or malformed.

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: The policy set name is empty.

Cause: The policy set name was empty.

Action: Make sure that the policy set name is specified.
Level: 1

Type: ERROR

Impact: Data

WSM-01824: The policy set name {0} contains invalid characters.

Cause: The policy set name contains invalid characters.

Action: Make sure that policy set name contains valid characters.
Level: 1

Type: ERROR

Impact: Data

WSM-01825: Secure conversation is enabled in assertion to which it does not currently apply.

Cause: Secure conversation is enabled in assertion to which it does not currently apply.

Action: Make sure that secure conversation is enabled only in supported assertions.
Level: 1

Type: ERROR

Impact: Data

WSM-01826: Secure conversation re-authenticate feature is not supported in this assertion.

Cause: Secure conversation re-authenticate feature is not supported in this assertion.

Action: Make sure that secure conversation re-authenticate feature is enabled only in supported assertions.
Level: 1

Type: ERROR

Impact: Data

WSM-01827: 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-01828: 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-01829: 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-01830: The policy binding value "{0}" is not valid.

Cause: The policy binding value provided for the PolicySubject is invalid.

Action: Verify that the SubjectType arguemt is correct.
Level: 1

Type: ERROR

Impact: Security

WSM-01831: PII assertions cannot be combined with other assertions in a policy. This policy includes PII and non PII assertions which is not valid.

Cause: The policy contains PII assertion as well as other assertions. PII Assertion cannot be combined with other assertions in a policy.

Action: Remove other assertions from this policy or remove the PII assertion.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01832: PII Policy {0} is not supported on the Resource {1} , as the PII policy is not supported on SubjectType : {2}

Cause: The PII Policy is not applicable on this SubjectType.

Action: Detach the PII policy from the Subject.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01833: PII Policy {0} has local optimization turned ON, it should always be turned OFF.

Cause: Local optimization cannot be ON for PII Policy.

Action: Turn local optimization off in PII policy.
Level: 1

Type: ERROR

Impact: Security

WSM-01834: Policy: {0} contains assertion(s) that are not supported for the REST endpoint with Resource Pattern: {1}

Cause: Policy Set validation failed because the attached policy contains assertions that are not supported for REST endpoints.

Action: Make sure the assertion(s) included in the policy are supported for REST endpoints.
Level: 1

Type: ERROR

Impact: Security

WSM-01835: Policy: {0} contains assertion(s) that are not supported for the virtual endpoint with Resource Pattern: {1}, Subject type: {2}. If SubjectType is VS_SERVICE, policy must have VS_SERVICE intent and policy references must have SOAP_HTTP intent. If SubjectType is VS_REST_RESOURCE, policy must have VS_REST_RESOURCE intent and policy references must have REST_HTTP intent. If SubjectType is VS_URL_RESOURCE, policy must have VS_URL_RESOURCE intent and policy references must have URL intent.

Cause: Policy Set validation failed because the attached policy contains assertions that are not supported for virtual endpoints.

Action: Make sure the assertion(s) included in the policy are supported for virtual endpoints. Check log for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-01844: The data type of the value does not match the data type of property {0}. The expected data type is "long".

Cause: The data type of the property value entered was not of type "long".

Action: Make sure that the data type for the property value is of type "long".
Level: 1

Type: ERROR

Impact: Data

WSM-01845: The value specified for the policy attachTo attribute {0}, is invalid for the assertion category: {1}.

Cause: The value specified for the policy attachTo attribute is invalid for the category.

Action: Specify a valid value for the attachTo attribute. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01846: The policy "{0}" having category "{1}" is not valid for resource pattern "{2}" of subject type "{3}".

Cause: Policy of this category is not applicable to the subject type.

Action: Detach the policy from the subject.
Level: 1

Type: ERROR

Impact: Security

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 committed 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}" cannot be deleted 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-04700: cannot delete read-only resources {0}

Cause: The document is read-only and cannot be deleted.

Action: Choose document(s) that are not read-only for modification.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04701: A connection provider is required to connect to a database-based MDS repository.

Cause: A null connection provider was provided when attempting to create an MDS instance for a database-based repository.

Action: Provide a valid connection provider and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04702: Timestamp information cannot be marshalled due to underlying parser error "{2}"

Cause: The timestamp information object could not be marshalled into a DOM document.

Action: Retry the operation and if problem persists, contact Oracle Support Services for assistance.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04703: Repository timestamp 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-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-06156: The policy referenced by URI "{0}" could not be retrieved since the URI is invalid.

Cause: The policy URI is missing, empty or contains invalid characters.

Action: Provide a valid URI for a policy in the repository or remove the reference.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06157: The policy referenced by URI "{0}" could not be retrieved due to incorrect repository configuration.

Cause: The repository database is not configured correctly or not running.

Action: Verify that the repository database is configured correctly according to the user documentation and is running.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06158: The policy referenced by URI "{0}" does not exist in the repository.

Cause: The referenced policy does not exist in the repository.

Action: Provide the URI for a policy in the repository or load the desired policy into the repository.
Level: 1

Type: ERROR

Impact: Data

WSM-06159: The policy referenced by URI "{0}" could not be retrieved due to invalid credential "{1}" being used to connect to the Policy Manager.

Cause: Cannot connect to the policy manager due to credential issue.

Action: Verify that credentials are correctly specified, if not using the default principal, and that the principal is authorized to access the policy manager application.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06160: The policy referenced by URI "{0}" could not be retrieved since Policy Manager is either not deployed or not in active state.

Cause: The policy manager application has not been deployed or is not running.

Action: Verify that the policy manager application is deployed and configured correctly and in an active state.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06161: The policy referenced by URI "{0}" could not be retrieved since Policy Manager is not deployed.

Cause: The policy manager application has not been deployed.

Action: Verify that the policy manager application is deployed.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06162: The policy referenced by URI "{0}" could not be retrieved as connection to Policy Manager cannot be established at "{1}" due to invalid configuration or inactive state.

Cause: The policy manager application is not running or is not configured correctly.

Action: Verify that the policy manager application is configured correctly and is in an active state. Provide correct configuration for URL of policy manager, setting its listen address if using auto-discovery, and ensure that any required SSL certificate is valid.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06163: The policy referenced by URI "{0}" could not be retrieved as connection to Policy Manager cannot be established due to invalid certificate configuration.

Cause: Cannot connect to the policy manager due to certificate issue.

Action: Verify that credential store and trust store location are correctly specified, and ensure that the certificate entry is valid.
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-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-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-06226: An instance of the {0} bean was obtained for accessing the local repository at path "{1}".

Cause: A bean instance was obtained by the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06227: An instance of the {0} bean was obtained for accessing the remote repository.

Cause: A bean instance was obtained by the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06228: Unable to retrieve "ENTERPRISE" model via classpath accessor during configuration initialization.

Cause: The seed ENTERPRISE model cannot be retrieved via ClasspathAccessor during configuration manager startup.

Action: Verify the availability of seed documents jar witin the classpath.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06229: Unable to retrieve "default" resource via classpath accessor during configuration initialization.

Cause: The seed default resource cannot be retrieved via ClasspathAccessor during configuration manager startup.

Action: Verify the availability of seed documents jar witin the classpath.
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-06401: The assembly referenced by "{0}" is not registered with the application.

Cause: The assembly is not registered with the application.

Action: Retry the operation after registering the assembly with the application.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-06402: The resource pattern identifying the metadata model is not provided.

Cause: The resource pattern identifying the metadata is not provided.

Action: Ensure that a valid resource pattern is passed for identifying the metadata.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-06403: Valid instance of StorageProvider must be provided for accessing the assembly file.

Cause: A storage provider is required for extracting metadata information from assembly file.

Action: Retry the operation with valid instance of storage provider.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-06404: The resource pattern "{0}" does not uniquely identify the subject.

Cause: The resource pattern identifying the subject is invalid.

Action: Retry the operation with valid value for subject resource pattern.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-06405: The subject referenced by "{0}" is not registered with the assembly.

Cause: The subject is not registered with the assembly.

Action: Retry the operation after registering the subject with the assembly.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-06406: Valid PolicySubjectDefinition must be provided for retrieving the effective policy set.

Cause: The subject definition is not provided for creating policy set.

Action: Provide valid value for subject definition for creating policy set.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-06407: Attempted to register the listener "{0}" to a policy subject "{1}" which was already previously registered with listener "{2}".

Cause: Attempt to reregistering a listener for a policy subject.

Action: Make sure that a policy subject registers a listener only once.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-06408: The local policy attachment data for policy subject "{0}" is not available due to underlying IO exception "{1}".

Cause: The policy assembly containing the policy subject's metadata cannot be accessed.

Action: Correct the underlying condition and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-06409: The local policy attachment data for policy subject "{0}" is not available due to underlying JAXB exception "{1}".

Cause: The policy assembly containing the policy subject's metadata is corrupt.

Action: Correct the underlying condition and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-06410: JMX APIs are not available in this environment, verify environment configuration for JMX.

Cause: JMX api's are not available in this environment, so not initializing PolicyApplicationMBean

Action: Verify environment configuration for JMX.
Level: 1

Type: WARNING

Impact: Data

WSM-06411: A task scheduler was not available for configuring the repository accessor due to undelying error "{0}".

Cause: OWSM Configuration Manager not able to set the task scheduler.

Action: Provide a task scheduler to the configuration framework.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06412: The partition aware scheduler fetch failed due to underlying Naming exception "{0}".

Cause: The partition aware scheduler cannot be fetched.

Action: Correct the underlying condition and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-06413: The value of term "{0}" from resource pattern terms "{1}" is not provided and cannot be resolved by platform support API either, hence will be set to default "{2}", please verify the cause.

Cause: PlatformSupport API returned unexpected null value in J2EE environment.

Action: Check the log for more info and possible cause.
Level: 1

Type: WARNING

Impact: Data

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-07510: JAX-RS Filter is already initialized for policy subject with Resource Pattern "{0}". It can not be passed another PolicySubjectDefintion with Resource Patter "{1}". {2}

Cause: The JAX-RS Filter was already initialized with a PolicySubjectDefinition. It can not be passed any more PolicySubjectDefinition objects.

Action: Do not Initialize the JAX-RS Filter multiple times.
Level: 1

Type: ERROR

Impact: Data

WSM-07511: Failed to initialize JAX-RS Filter. The PolicySubjectDefinition array is either null, empty or has length > 1

Cause: JAX-RS Filter not initialized with an array of PolicySubjectDefinition objects whose length is exactly 1. The filter supports a single PolicySubjectDefinition at any time.

Action: Create a PolicySubjectDefinition array with a single object and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-07512: PolicySubjectDefinition could not be created for the JAX-RS resource. The JAX-RS resource object passed to create PolicySubjectDefinition was null.

Cause: PolicySubjectDefinition could not be created for the JAX-RS resource. The JAX-RS resource object passed to create PolicySubjectDefinition was null.

Action: Pass a valid, non-null resource class object.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-07513: A resource filter could not be created for the JAX-RS resource. Either the HttpServletRequest [{0}] or the HttpServletResponse [{1}] passed to the constructor was null.

Cause: RESTResourceFilter could not be instantiated. Either of the servlet request or response objects passed by the RESTResourceFilterFactory was null.

Action: Make sure the HttpServletRequest/Response objects were injected in the filter factory.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-07514: OWSM Security Filter failed to initialize. The param-value of "oracle.wsm.metadata.policySet" init-param can not be parsed.

Cause: The XML value configured as CDATA for "oracle.wsm.metadata.policySet" init-param in the application's web.xml was not parsed successfully.

Action: Make sure that the value of "oracle.wsm.metadata.policySet" init-param is well-formed XML enclosed as CDATA.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07515: OWSM Security Filter failed to initialize. The filter was unable to create a valid ResourcePattern object for this servlet: {0}.

Cause: The servlet may be under the default (root) context path.

Action: Make sure that the servlet to be protected is not under the default (root) context path.
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 Weblogic 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-07622: The agent instance for enforcement cannot be null for scope "{0}". Check logs for details.

Cause: The agent instance for enforcement is null.

Action: Check server logs for more details.
Level: 1

Type: WARNING

Impact: Data

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

WSM-09025: Unable to initialize WSM Coherence cache service, Defaulting to local Coherence cache. {0}

Cause: Unable to initialize Coherence cache service.

Action: Make sure that the Coherence is properly configured for the cluster environment.
Level: 1

Type: WARNING

Impact: Logging

WSM-09027: Resource bundle {0} is missing.

Cause: Resource bundle is missing.

Action: Add the resource bundle and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-09028: Failed to get server log directory due to error {0}.

Cause: Failed to get server Log directory.

Action: See logs for details.
Level: 1

Type: WARNING

Impact: Other

WSM-09029: Diagnostic logging handler creation failed due to error {0}.

Cause: Failed to create handler for diagnosis logs.

Action: See logs for details.
Level: 1

Type: WARNING

Impact: Other

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2018, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.