38 ESS-00001 to ESS-09408

ESS-00001: Internal error. {0}

Cause: Internal error occurred.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-00002: Constraint error for property {0} with value {1}.

Cause: An attempt was made to create an object that already exists.

Action: Specifiy an identifier for the object that is not currently in use.

Level: 1

Type: ERROR

Impact: Other

Cause: An attempt was made to change the value of an object thatis read-only.

Action: Retry the operation without changing the value of the object.

ESS-00003: Failed to find resource {0}. {1}

Cause: A JNDI lookup of the given resource failed.

Action: Ensure the resource is deployed properly and is available via jndi lookup.

Level: 1

Type: ERROR

Impact: Other

ESS-00004: Incorrect timestamp format: {0}. {1}

Cause: An invalid value was specified for a timestamp.

Action: Specify a correct value for the parameter.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00005: SQL bind operation not supported for parameter data type: {0}

Cause: A value being used for an SQL bind parameter has a data type that is not suitable for the SQL Statement.

Action: Specify a parameter value having an appropriate data type.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00006: Enterprise Scheduler configuration is not initialized.

Cause: An operation attempted to access Enterprise Scheduler configuration information before the configuration was initialized.

Action: Re-try the operation at a later time.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00007: Operation intended for group, {0}. Configured group is {1}.

Cause: An Enterprise Scheduler instance received an event, message, or other data that was intended for an instance of a different group.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

ESS-00100: Install plan is not present for application {0}.

Cause: The install plan is not present for the application being deployed.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Installation

ESS-00101: Global data source, {0}, could not be created.

Cause: The global data source could not be created.

Action: Check the underlying cause for details.

Level: 1

Type: ERROR

Impact: Installation

ESS-00102: Dependent component, {0}, has not been deployed.

Cause: A dependent component of this component has not been deployed. An error may have occurred when deploying dependent component.

Action: Check log for errors in deploying dependent component.

Level: 1

Type: ERROR

Impact: Installation

ESS-00103: Error finding application {0}.

Cause: An error occurred while attempting to find the specified application.

Action: Perform the action specified in the chained exception.

Level: 1

Type: WARNING

Impact: Installation

ESS-00104: Cannot find object {0} for archive {1}.

Cause: The attempt to access the specified object failed.

Action: None

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-00120: Invalid value for dispatcher poll interval.

Cause: Attempted to configure an invalid value for the dispatcher minimum or maximum poll interval.

Action: Retry the operation with a non-negative numeric value.

Level: 1

Type: ERROR

Impact: Other

ESS-00121: Dispatcher poll interval minimum value cannot exceed maximum value.

Cause: Attempted to configure a value for the dispatcher minimum poll interval that is greater than the maximum value.

Action: Retry the operation with a value that is less than or equal to the maximum value.

Level: 1

Type: ERROR

Impact: Other

Cause: Attempted to configure a value for the dispatcher maximum poll interval that is less than the minimum value.

Action: Retry the operation with a value that is equal to or greater than the minimum value.

ESS-00122: Invalid value for processor threads.

Cause: Attempted to configure an invalid value for the processor maximum threads.

Action: Retry the operation with a non-negative numeric value.

Level: 1

Type: ERROR

Impact: Other

ESS-00123: Invalid value for processor starvation threshold.

Cause: Attempted to configure an invalid value for the processor starvation threshold.

Action: Retry the operation with a non-negative numeric value.

Level: 1

Type: ERROR

Impact: Other

ESS-00124: Unable to validate metadata for work assignment {0}.

Cause: Attempted to add or remove bindings for an work assignment.

Action: Retry the operation with a valid work assignment name.

Level: 1

Type: ERROR

Impact: Other

ESS-00300: Invalid value ({0}) for {1} argument.

Cause: The value specified for an argument is not valid.

Action: Retry the operation using a valid value.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00301: TopologyNodeType, {0}, is not supported for this operation.

Cause: The operation is not supported on the specified topology node type.

Action: Retry the operation on OC4JComponent or Group.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00310: Work assignment, {0}, already exists.

Cause: Attempted an operation using a work assignment that already exists.

Action: Retry the operation with an assignment that does not exist.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00311: Work assignment, {0}, does not exist.

Cause: Attempted an operation using a work assignment that does not exist.

Action: Retry the operation with an assignment that exists.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00312: Group, {0}, does not exist.

Cause: Attempted an operation using a group that does not exist.

Action: Retry the operation with a group that exists.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00313: Failed to read the configuration document.

Cause: Failed to read the configuration document.

Action: Check the underlying cause for details.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00314: Failed to write the configuration document.

Cause: Failed to write the configuration document.

Action: Check the underlying cause for details.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00315: Invalid Wait Queue polling interval; minimum ({0}) > maximum ({1}).

Cause: Invalid Wait Queue polling interval.

Action: Provide a valid polling interval.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00316: Invalid minimum Wait Queue polling interval ({0}).

Cause: Invalid minimum Wait Queue polling interval.

Action: Provide a valid polling interval.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00317: Invalid maximum Wait Queue polling interval ({0}).

Cause: Invalid maximum Wait Queue polling interval.

Action: Provide a valid polling interval.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00318: Invalid threshold ({0}) for processing low priority jobs.

Cause: Threshold is invalid.

Action: Correct the threshold value.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00319: Invalid value ({0}) for threads to be available for request processing.

Cause: Threads used for request processing are invalid.

Action: Call Oracle Support.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00400: Insufficient information to execute the command.

Cause: A valid command was specified but the supplied information was not adequate to execute the command, possibly due to missing command switches or keywords.

Action: Review the help and syntax for the command. Retry the operation with additional information.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00401: Error attempting to execute the "{0}" operation. {1}

Cause: Encountered an error while trying to execute the specified operation.

Action: Review the error information to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00402: Invalid work assignment mode ({0}).

Cause: Value specified for a work assignment mode is not valid.

Action: Retry the operation with a valid value; "primary" or "secondary".

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00403: Work assignment is required.

Cause: A work assignment is required for the operation but none was specified.

Action: Retry the operation with at least one work assignment.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00404: Invalid topoNode "{0}".

Cause: Invalid topoNode

Action: Provide a valid topoNode value and make usre the Config MBean is registered with ESSAPP

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00405: The Config MBean "{0}" is not registered with the ESSAPP.

Cause: Config MBean is not registered with the ESSAPP

Action: Make sure the Config MBean is registered with ESSAPP and then retry

Level: 1

Type: ERROR

Impact: Programmatic

ESS-00500: Failed to create metadata service handle.

Cause: An error occurred while starting a Metadata session.

Action: See the base exception for details.

Level: 1

Type: WARNING

Impact: Other

ESS-00501: Failed to close metadata service handle.

Cause: An error occurred while closing a Metadata session.

Action: See the base exception for details.

Level: 1

Type: WARNING

Impact: Other

ESS-00502: The metadata object type must be specified

Cause: The metadata type was not specified when creating the metadata object

Action: Specify a valid value for the metadata object type

Level: 1

Type: WARNING

Impact: Other

ESS-01000: Failed to open runtime service. {0}

Cause: An error occurred opening the RuntimeService handle

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01001: Failed to close runtime service handle. {0}

Cause: An error occurred closing the RuntimeService handle

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01002: Illegal attempt to validate request, {0}, when current state, {1}, is not PENDING_VALIDATION.

Cause: A request is in an illegal state for validation.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-01003: Illegal operation for an unvalidated request {0}.

Cause: The operation is not supported for an unvalidated request.

Action: Do not attempt this operation unless the request is validated.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01004: Illegal attempt to set state of request, {0}, to VALIDATION_FAILED when current state, {1}, is not PENDING_VALIDATION.

Cause: An internal error occurred.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-01005: Parameter {0} does not exist for request {1}.

Cause: The given parameter name does not exist for this request.

Action: Specify an existing parameter.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01006: RuntimeServiceHandle is marked for rollback only.

Cause: The ESS runtime service handle has been marked for rollback only.

Action: Close the ESS runtime service session. Another session may be created for further operations.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01007: RuntimeServiceHandle is null.

Cause: The ESS runtime service handle is null.

Action: Specify a valid ESS runtime service handle.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01008: Value for parameter, {0}, has an invalid data type: {1}.

Cause: The value for a parameter has an unsupported data type.

Action: Specify a value which has a supported data type for the parameter.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01009: Value for parameter, {0}, is not valid.

Cause: The value for a parameter is not valid.

Action: Specify a valid value for the parameter.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01010: Value for parameter, {0}, must not be null.

Cause: The given parameter does not support a null value, or empty string for string parameter.

Action: Specify a non-null value for the parameter.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01011: Parameter, {0}, is required but was not specified.

Cause: The given parameter is required but was not specified.

Action: Specify the required parameter.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01012: Request {0} not found.

Cause: A request that was the target of a RuntimeService operation was not found in the runtime store.

Action: Specify a valid request identifier.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01013: Failed to lock request {0}. Request not found.

Cause: Attemped to lock a request that was not found in the runtime store.

Action: Specify a valid request identifier.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01014: Error occurred attempting to lock request {0}.

Cause: An error occurred attempting to lock a request in the runtime store.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01015: Failed to generate a request identifier.

Cause: An error occurred attempting to generate a new request identifier.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01016: Failed to generate a request handle.

Cause: An error occurred attempting to generate a new request handle.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01017: Error attempting to access information for request {0}.

Cause: An error occurred attempting to access information for a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01018: Error attempting to update information for request {0}.

Cause: An error occurred attempting to update information for a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01019: Request {0} is not in {1} state. Current state is {2}.

Cause: An operation was attempted when the request was not in an expected state.

Action: Retry the operation when the request is the correct state.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01022: Error occurred retrieving summary data. {0}

Cause: An error occurred attempting to retrieve request or application summary information.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01023: Parameter {0} for request {1} is read-only.

Cause: Attempted to modify the value for a request parameter that is read-only.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01024: This operation is illegal for this request. {0}

Cause: The invoked operation is not legal for this request.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01025: The request does not have a schedule. {0}

Cause: This operation can only be applied to a request with a schedule.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01026: Schedule for request {0} cannot be changed when in state {1}

Cause: The schedule for this request cannot be replaced in the current state.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01027: Failed to convert schedule to string

Cause: The schedule cannot be converted to a string.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01028: Request submission or validation failed. {0}

Cause: An error occurred during request submission or validation.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01029: Failed to create child request for parent request {0}.

Cause: An error occurred while attempting to create a child request for a parent that was submitted with a Schedule or Trigger.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01030: Failed to create JobSet step request for parent request {0}, step {1}.

Cause: An error occurred while attempting to create a request for a JobSet step.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01031: Application {0} was not found.

Cause: Attempted to submit a request for an application associated with a logical name but no such application was found.

Action: Deploy the application

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01032: Application {0} was found in more than one process group.

Cause: Attempted to submit a request for an application that is deployed to multiple process groups. Unable to determine correct group to use.

Action: Application should be deployed to only one group.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01033: Application {0} was not found for process group {1}.

Cause: Attempted to submit a request for an application that is deployed to multiple process groups. Unable to determine correct group to use.

Action: Application should be deployed to only one group.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01034: Unable to determine the deployed application name for logical application {0}.

Cause: Unable to determine the name of the deployed application for the specified logical name.

Action: Check for deployment errors.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01035: Unable to determine a logical application name for new request.

Cause: Unable to determine the logical application that should be used for a submitted request.

Action: Specify a value for the SystemProperty.EFFECTIVE_APPLICATION parameter in the metatadata for the JobDefinition or JobSet.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01036: Unable to determine a process group for new request.

Cause: Unable to determine the process group that should be used for a submitted request.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01037: Job definition is required for a non-Adhoc request submission.

Cause: A submit operation was attempted for a non-adhoc job but no metadata id for a JobDefinition or JobSet was given.

Action: Retry the submit operation and specify a job defintion.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01038: Read-Only violation for request parameter {0}.

Cause: The given parameter is marked as read-only and was specified as a request parameter.

Action: Retry the operation without the parameter.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01039: Parameter, {0}, is not allowed in request submission parameters.

Cause: The given parameter is not allowed to be included as a request parameter for a submit operation. Usually such paramters can be set only via a metadata parameter.

Action: Retry the operation without the given parameter.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01040: Invalid parameter {0}. Scoped parameters are only supported for JobSet.

Cause: A scoped parameter was included in the request parameters specified for the request submisssion of a JobDefinition. Scoped parameters are supported only for a JobSet.

Action: Retry the submit operation without the scoped parameter.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01041: Parameter, {0}, is not allowed as a scoped request parameter for JobSet step {1}.

Cause: The request parameters for a JobSet submission include a scoped parameter that is not allowed to be specified as a scoped parameter for a JobSet step.

Action: Retry the submit operation without the scoped parameter.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01042: Metadata type, {0}, is not supported for a sub-request.Only JobDefinition is supported.

Cause: Attempted to submit a sub-request for an unsupported definition type. Subrequest supported only for a JobDefinition.

Action: Retry the operation using a valid defintion type.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01043: Failed to get XML for an adhoc Schedule.

Cause: Error occurred creating XML representation of an adhoc Schedule.

Action: Fix the adhoc Schedule and retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01044: Failed to get XML for an adhoc Trigger.

Cause: Error occurred creating XML representation of an adhoc Trigger.

Action: Fix the adhoc Trigger and retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01045: Failed to validate Trigger expression against the schema.

Cause: Error occurred validating the XML for a Trigger expression.

Action: Fix the Trigger expression and retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01046: Start time must be before the end time.

Cause: Attempted to submit a request where the start time is after the end time.

Action: Retry the operation with valid start and end times.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01047: End time must be after the current time.

Cause: Attempted to submit a request where the end time is before the current time.

Action: Retry the operation with value end time.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01048: Schedule has expired and no executions are possible.

Cause: Attempted to submit a request with a Schedule that has expired.

Action: Retry the operation with a different Schedule.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01049: No executions are possible before the given end date.

Cause: Attempted to submit a request with a Schedule for which there no executions prior to the end date.

Action: Retry the operation with a different Schedule.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01050: One or more requests are currently pending for definition: {0}

Cause: The SystemProperty.ALLOW_MULT_PENDING property is disabled for the request being submitted. Execution is already pending for one or more requests with the same job definition.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01051: Incompatible with parent request {0} due to Incompatibility definition: {1}

Cause: Attempted to submit a sub-request that is incompatible with its parent request due to an Incompatibility definition

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01052: Request handle is not valid for the current execution context of parent request {0}.

Cause: The SystemProperty.ALLOW_MULT_PENDING property is disabled for the request being submitted. Execution is already pending for one or more requests with the same job definition.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01053: Cannot cancel request {0}. Current state is {1}.

Cause: Attempted to cancel a request whose current state does not allow the operation to be performed.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01054: Cannot hold request {0}. Current state is {1}.

Cause: Attempted to hold a request whose current state does not allow the operation to be performed.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01055: Cannot release request {0}. Current state is {1}.

Cause: Attempted to release a request whose current state does not allow the operation to be performed.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01056: Cannot delete request {0}. Current state is {1}, process phase is {2}.

Cause: Attempted to delete a request whose current state or process phase does not allow the operation to be performed.

Action: Retry the operation at a later time.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01057: Cannot purge request {0}. Current state is {1}, process phase is {2}.

Cause: Attempted to purge a request whose current state or process phase does not allow the operation to be performed.

Action: Retry the operation at a later time.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01058: Cannot change priority for request {0}. Current state is {1}.

Cause: Attempted to change the priority for a request whose current state does not allow the operation to be performed.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01059: Delete failed for request {0}. This operation is not supported for a sub-request or JobSet step.

Cause: Attempted to perform a delete operation on a child request. Only an absolute parent or instance parent can be the target of a delete operation.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01060: Purge failed for request {0}. This operation not supported for a sub-request or JobSet step.

Cause: Attempted to perform a purge operation on a child request. Only an absolute parent or instance parent can be the target of a purge operation.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01061: Failed to purge request {0}.

Cause: An error occurred attempting to purge a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01062: Invalid priority value. Valid range is {0} to {1}.

Cause: An invalid value for request priority is specified.

Action: Specify a value in the indicated range.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01063: Failed to retrieve Schedule for request {0}.

Cause: Failed to retrieve the Schedule associated with the given request.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01064: Failed to retrieve Trigger for request {0}.

Cause: Failed to retrieve the Trigger associated with the given request.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01065: Cannot recover request {0} with incomplete child requests.

Cause: An attempt was made to manually recover a request with at least one child not in ProcessPhase.Complete.

Action: Wait for the incomplete child to complete or recover.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01066: Request state {0} not allowed for manual recovery. State should be canceling or terminal. {1}

Cause: An attempt was made to manually recover a request that was in an illegal state.

Action: Cancel the request.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01067: Error occurred mapping Filter to CompositeData.

Cause: Error occurred mapping Filter to CompositeData.

Action: Correct the invalid CompositeData instance.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01068: Unexpected type, {0}, for Filter value {1}.

Cause: Unexpected Filter type for Filter value.

Action: Correct the invalid Filter type.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01069: Invalid Null input for a Filter {0}.

Cause: Unexpected null input for a filter.

Action: Provider a non null value.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01070: Cannot change start time or end time for request of type {0}

Cause: The start and end times cannot be updated for a request this type.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01071: Schedule for request {0} cannot be for a retry attempt

Cause: The schedule for this request cannot be replaced during a retry.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01072: Metadata schedule and adhoc schedule were specified. Only one schedule can be used.

Cause: A metadata schedule and an adhoc schedule were specified for an operation. Only one schedule should be specified.

Action: Retry the operation with only one schedule

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01073: Failed to open runtime service: {0}. {1}

Cause: An error occurred opening the RuntimeService handle

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01074: Failed to open runtime service due to resource error. {0}

Cause: A resource error occurred opening the RuntimeService handle.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01075: Cannot delete execution group, {0}, because active instances exist.

Cause: A execution group must not be deleted when active instances exist in its cluster.

Action: Use only when the cluster associated with the execution group no longer exists.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01076: Execution group {0} is already being deleted.

Cause: The execution group is already being deleted.

Action: Wait for first deletion to complete.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01077: Failed to get async request information for message {0}.

Cause: Failed to retrieve information for web service asynchronous callback.

Action: Check the logs.

Level: 1

Type: WARNING

Impact: Other

ESS-01078: Request {0} is required to be asynchronous for this operation.

Cause: This operation cannot be executed on a synchronous request.

Action: Do not invoke the operation on this request.

Level: 1

Type: WARNING

Impact: Other

ESS-01079: Error attempting to access request information.

Cause: An error occurred attempting to access request information.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01080: Failed to persist request information.

Cause: An error occurred attempting to persist request information to the runtime store.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01081: Failed to persist request parameter {0}, scope {1}.

Cause: An error occurred attempting to store a request parameter.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01082: Failed to persist read-only constraint for parameter {0}.

Cause: An error occurred attempting to store parameter read-only constraint.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01083: Error attempting to retrieve parameters for request {0}.

Cause: An error occurred attempting to retrieve request parameters.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01084: Error attempting to update parameter, {0}, for request {1}.

Cause: An error occurred attempting to update a request parameter.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01085: Failed to add parameter {0}, scope {1}, for request {2}.

Cause: An error occurred attempting to add a request parameter.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01086: Operation not supported for scoped parameter, {0}.

Cause: A scoped parameter was specified for an operation that is not supported for scoped parameter.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01087: Failed to convert Document to byte sequence.

Cause: An error occurred converting a Document to byte sequence.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-01088: Failed to convert byte sequence to Document.

Cause: An error occurred converting a byte sequence to a Document.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-01089: Failed to get storable value for parameter, {0}.

Cause: An error occurred converting a parameter value to its stored representation.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-01090: Failed to get typed value for parameter, {0}, data type, {1}.

Cause: An error occurred converting a parameter value from its stored representation to a typed value.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-01091: Unable to obtain incompatibility value for property, {0}.

Cause: Unable to materialize an incompatibility value for the specified property.

Action: Review the causeBy exception chain to determine the specific failure.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01092: Incompatibility conflict detected between request {0} and parent request {1} for incompatibility {2}.

Cause: Incompatibility conflict detected between a JobSet step request and a JobSet request of its parent chain. An incompatibility lock for that incompatibility will not be acquired for the step request.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-01093: Number of acquired request incompatibilities ({0}) does not match number of incompatibility locks ({1}) for request {2}.

Cause: Runtime service system failure.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-01094: Error attempting to process getCompletionStatus call since another getCompletionStatus call with message id {0} is pending for reply.

Cause: An error occured attempting to process getCompletionStatus call since another getCompletionStatus call with messageid {0} is pending for reply.

Action: Attach different ws message id or wait for the previous call finished before submit getCompletionStatus call.

Level: 1

Type: ERROR

Impact: Other

ESS-01095: Unable to find ess hosting app with logical application name {0}.

Cause: Unable to find ess hosting app with logical application name {0}.

Action: Specify a correct parameter of application or deploy the ess hosting app with expected logical application name.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01096: Query result handle is null.

Cause: The value of the query result handle argument is null.

Action: Specify an argument value that is not null.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01097: Request, {0}, is not of expected type, {1}.

Cause: The request was found in ESS runtime storage but was not of the expected execution type.

Action: Specify a request identifier for a request of the correct execution type.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01098: No request is found for id {0} {1}

Cause: A request was not found in ESS runtime storage corresponding to the indicated request identifier.

Action: Specify a request identifier for an existing request.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01099: An error occured invoking the RuntimeService MBean. {0}

Cause: An error occurred invoking the RuntimeService MBean.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01100: Error retrieving details about Oracle Scheduler job {0} for request {1}.

Cause: An error occurred while trying to retrieve details about the Oracle Scheduler job associated with an ESS request identifier.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01101: Error retrieving the OUTPUT_LIST for parallel children of request {0}.

Cause: An error occurred while trying to retrieve the OUTPUT_LIST for parallel child requests for an ESS request identifier.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01102: Failed to register application, {0}, with instance {1}. {2}

Cause: Application registration failed with ESS.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

ESS-01103: Failed to unregister all applications for instance {0}. {1}

Cause: Application deregistration failed with ESS.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

ESS-01104: Failed to unregister application, {0}, for instance {1}. {2}

Cause: Application deregistration failed with ESS.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

ESS-01105: Failed to check in instance {0}. {1}

Cause: Registration update of ESS instance failed.

Action: Check that database is running and data source is correct.

Level: 1

Type: ERROR

Impact: Other

ESS-01106: Failed to clear checkin entry for instance {0}. {1}

Cause: Unregistration of ESS instance failed.

Action: Check that database is running and data source is correct.

Level: 1

Type: ERROR

Impact: Other

ESS-01107: Failed to remove timed out instance registrations. {0}

Cause: Unregistration of ESS timed-out instances failed.

Action: Check that database is running and data source is correct.

Level: 1

Type: ERROR

Impact: Other

ESS-01108: Failed to fetch elements from wait queue. {0}.

Cause: An error occurred attempting to fetch elements from the wait queue.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01109: Failed to access wait queue element for request {0}. {1}

Cause: An error occurred attempting to access a wait queue element.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01110: Failed to lock wait queue element for request {0}. {1}

Cause: Failed to obtain a lock on the wait queue element for a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01111: Failed to insert wait queue element for request {0}. {1}

Cause: An error occurred while attempting to add an element to the wait queue.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01112: Failed to delete wait queue element for request {0}. {1}

Cause: An error occurred while attempting to remove an element from the wait queue.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01113: Failed to hold wait queue element for request {0}. {1}

Cause: An error occurred attempting to hold the wait queue element for a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01114: Failed to release wait queue element for request {0}. {1}

Cause: An error occurred attempting to release the wait queue element for a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01115: Failed to undefer wait queue element for request {0}. {1}

Cause: An error occurred attempting to undefer the wait queue element for a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01116: Query field name, {0}, is not a valid name.

Cause: A query filter was specified with an unknown query field.

Action: Remove that query field from the filter, or specify a known name for the query field.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01117: Value for query field, {0}, has an unsupported data type: {1}

Cause: A query filter was specified in which the value for a query field has an unsupported data type.

Action: Specify a query value whose data type is a supported type.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01118: Query field, {0}, has a null value which is not supported for the {1} operator.

Cause: A query filter was specified with a field that has a null value and a comparator that does not support a null value. A null query value requires an EQUALS or NOT_EQUALS comparator.

Action: Specify a non-null value for that query field, or specify an EQUALS or NOT_EQUALS comparator.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01119: Query field, {0}, has a value with a data type, {1}, that is not supported for the {2} comparator.

Cause: A query filter was specified with a field that has a value whose data type is not supported for the specified comparator.

Action: Specify a query value whose data type is supported by the comparator being used.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01120: Query field, {0}, does not support the {1} comparator.

Cause: A query filter was specified with a field that does not support the specified comparator.

Action: Specify a comparator that is supported by that query field.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01121: Failed to retrieve field {0}.

Cause: A failure occurred while retrieving the specified field.

Action: Check that database is running and data source is correct.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01122: Error attempting to access information for incompatibility {0} for request {1}.

Cause: An error occurred attempting to access request incompatibility information.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01123: Error attempting to update information for incompatibility {0} for request {1}.

Cause: An error occurred attempting to update request incompatibility information.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01124: Error attempting to add information for incompatibility {0} for request {1}.

Cause: An error occurred attempting to add request incompatibility information.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01125: Size of request parameter {0} used for incompatibility {1} is too large.

Cause: The value for a request parameter that would be used for an Incompatibility is too large.

Action: Use a smaller value for the parameter value.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01126: Application {0} is active in more than one group.

Cause: An application with the same name is already a member of another ESS group.

Action: Redeploy the current application with a unique deployment name.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01127: Application {0} is not active in any ESS instance.

Cause: The application could not be found in the current ESS group.

Action: Ensure the application is deployed and running in the correct ESS group.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01128: Application with deployed name {0} exists with multiple logical names.

Cause: An application with the same deployment name but different logical name is already a member of this ESS group.

Action: Redploy this application with a unique deployment name. If this application is the same application as the conflicting app, then change the logical name to match.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01129: Application with logical name {0} was not found.

Cause: The application is not a member of this ESS group.

Action: Ensure the application is deployed and running in the correct ESS group.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01130: Application with logical name {0} exists with multiple deployed names.

Cause: An application with the same logical name but different deployment name is already a member of this ESS group.

Action: Redploy this application with a unique logical application name. If this application is the same application as the conflicting app, then change the deployment name to match.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01131: Application with deployed name {0} was not found.

Cause: The application is not a member of this ESS group.

Action: Ensure the application is deployed and running in the correct ESS group.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01132: Unable to access processor bindings. {0}

Cause: Processor bindings in the runtime store could not be accessed.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01133: Processor binding {0} could not be found.

Cause: Processor binding could not be found.

Action: Check that you specified the correct binding name.

Level: 1

Type: ERROR

Impact: Other

ESS-01134: Processor binding {0} already exists.

Cause: Processor binding already exists.

Action: Change the name of the binding.

Level: 1

Type: ERROR

Impact: Other

ESS-01135: Unable to notify server of processor bindings change. {0}

Cause: Unable to notify server of bindings change.

Action: Check that database is running and data source is correct.

Level: 1

Type: ERROR

Impact: Other

ESS-01136: Unable to access processor bindings change notification. {0}

Cause: Unable to access bindings change notification.

Action: Check that database is running and data source is correct.

Level: 1

Type: ERROR

Impact: Other

ESS-01137: Unable to notify server to refresh selector. {0}

Cause: Unable to notify server to refresh selector.

Action: Check that database is running and data source is correct.

Level: 1

Type: ERROR

Impact: Other

ESS-01138: Unable to access refresh selector notification. {0}

Cause: Unable to access refresh selector notification.

Action: Check that database is running and data source is correct.

Level: 1

Type: ERROR

Impact: Other

ESS-01139: Value, {1}, for query field, {0}, is invalid.

Cause: A query filter was specified in which the value for a query field was invalid.

Action: Specify a valid query value.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01140: Error accessing async throttle information for ({0}, {1}). {2}

Cause: An error occurred while accessing runtime async throttle information.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01141: Async throttle already exists for Workshift = {0}. {1}

Cause: The throttle is already configured for the Workshift.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01142: Async throttle not found for Workshift = {0}.

Cause: The throttle was not found for the Workshift.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01143: Failed to process filter {0}.

Cause: Filter evaluation failed.

Action: Correct the invalid Filter.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01144: Failed to retrieve timed out instance registrations. {0}

Cause: Query of ESS timed out registrationsinstance failed.

Action: Check that database is running and data source is correct.

Level: 1

Type: WARNING

Impact: Other

ESS-01145: Failed to lock instance {0}. {1}

Cause: Locking the ESS instance registration failed.

Action: Check that database is running and data source is correct.

Level: 1

Type: WARNING

Impact: Other

ESS-01146: Error accessing runtime async throttle information. {0}

Cause: An error occurred while accessing the throttle configuration.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01147: Failed to get DiagnosticState for instance {0}. {1}

Cause: Failed to get DiagnosticState for the instance.

Action: None

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01148: Failed to clear registrations for execution group {0}, isolation group {1}. {2}

Cause: Failed to clear registrations for execution group.

Action: None. Registrations will be automatically retried

Level: 1

Type: WARNING

Impact: Other

ESS-01149: Error accessing unthrottled work assignments ({0}). {1}

Cause: An error occurred while accessing the unthrottled work assignments.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01150: Unable to delete workshift with outstanding async workers: {0}

Cause: A workshift that has outstanding async workers not be deleted.

Action: Wait until all async workers have completed and then delete the workshift.

Level: 1

Type: WARNING

Impact: Other

ESS-01151: Error accessing async limit information for workshift = {0}. {1}

Cause: An error occurred while accessing runtime async limit information.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01152: Error accessing async allocation information for work assignment = {0}. {2}

Cause: An error occurred accessing runtime async allocation information.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01153: Failed to add incompatibility lock {0}.

Cause: An error occurred attempting to add incompatibility lock information.

Action: Review the causeBy exception chain to determine the specific failure.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01154: Failed to delete incompatibility lock {0}.

Cause: An error occurred attempting to delete incompatibility lock information.

Action: Review the causeBy exception chain to determine the specific failure.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01155: Failed to lock incompatibility lock {0}.

Cause: An error occurred attempting to delete incompatibility lock information.

Action: Review the causeBy exception chain to determine the specific failure.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01156: Failed to update reference count for incompatibility lock {0}.

Cause: An error occurred attempting to delete incompatibility lock information.

Action: Review the causeBy exception chain to determine the specific failure.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01157: Failed to retrieve incompatibility locks for request {0}.

Cause: An error occurred attempting to retrieve incompatibility locks held by a request.

Action: Review the causeBy exception chain to determine the specific failure.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01158: Failed to lock incompatibility locks for request {0}.

Cause: An error occurred attempting to lock any incompatibility locks held by a request.

Action: Review the causeBy exception chain to determine the specific failure.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01159: Failed to retrieve request incompatibility for request {0}.

Cause: An error occurred attempting to retrieve request incompatibility information.

Action: Review the causeBy exception chain to determine the specific failure.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01160: Failed to lock request incompatibility for request {0}.

Cause: An error occurred attempting to lock request incompatibility information.

Action: Review the causeBy exception chain to determine the specific failure.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01161: Failed to retrieve request incompatibility.

Cause: An error occurred attempting to retrieve request incompatibility information.

Action: Review the causeBy exception chain to determine the specific failure.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01162: Failed to lock request incompatibility.

Cause: An error occurred attempting to lock request incompatibility information.

Action: Review the causeBy exception chain to determine the specific failure.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01163: Failed to add reference for incompatibility {0}, job definition {1}, request {2}.

Cause: An error occurred attempting to add job incompatibility reference.

Action: Review the causeBy exception chain to determine the specific failure.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01164: Reference already exists for incompatibility {0}, job definition {1}, request {2}.

Cause: Job incompatibility reference already exists.

Action: None

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01165: Failed to retrieve incompatibility metadata from runtime store for job definition {0}, request {1}.

Cause: An error occurred attempting to retrieve incompatibility metadata from runtime store for a job definition.

Action: Review the causeBy exception chain to determine the specific failure.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01166: Failed to query registration table.

Cause: An error occurred while querying the registration table.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

ESS-01167: Failed to cache metadata in runtime store for request {0}. {1}.

Cause: An error occurred while saving metadata in the ESS runtime store.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01168: Binding mode conflict for {0}

Cause: Binding mode conflict. Work assignment may be bound in either standard or exclusive mode, but not in both modes on two different servers in the same processing group.

Action: Use the correct binding mode.

Level: 1

Type: WARNING

Impact: Other

ESS-01169: Workshift does not exist {0}

Cause: The workshift does not exist.

Action: Ensure you are using the correct workshift name, and that the workshift exists.

Level: 1

Type: WARNING

Impact: Other

ESS-01196: Unable to get the current time from the database.

Cause: Unable to get the current time from the database.

Action: Review the log file for possible underlying causes.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01197: Unable to release incompatibility locks for request {0}.

Cause: Unable to release one or more incompatibility locks for the request at this time.

Action: Review the log file for possible underlying causes.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-01198: Unable to obtain configuration information for application {0}.

Cause: Unable to retrieve configuration information for application.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01199: JobSet steps would have mixed request modes: {0}

Cause: The steps for a JobSet are not homogeneous in regard to the resolved request mode.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01200: Error attempting to insert {0} work unit for request {1}.

Cause: An error occurred inserting a work unit into the persistent store.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01201: Error attempting to insert {0} work unit.

Cause: An error occurred inserting a work unit into the persistent store.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01202: Failed to update work stage for work {0}.

Cause: An error occurred updating the work stage of a work unit.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01203: Failed to delete work for request {0}.

Cause: An error occurred deleting work units.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01204: Failed to delete work {0} for request {1}.

Cause: An error occurred deleting work units.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01205: Failed to delete work unit {0}.

Cause: An error occurred deleting work units.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01206: Failed to check in work unit {0} for request {1}.

Cause: An error occurred checking in work units.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01207: Failed to check in work unit {0}.

Cause: An error occurred checking in work units.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01208: Failed to undefer DeleteProcessGroup work for execution group {0}.

Cause: An error occurred undeferring a DeleteProcessGroupEvent.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01209: Failed to update information for work {0} for request {1}.

Cause: An error occurred updating a work unit.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01210: Failed to undefer work for request {0}.

Cause: An error occurred undeferring a work unit.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01211: Failed to check in work for instance {0}.

Cause: An error occurred checking in all the work units for an ESS instance.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01212: Error retrieving available work units.

Cause: Error occurred while retrieving work units to process.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01213: Failed to retrieve work unit {0}.

Cause: Error occurred while retrieving a work unit to process.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01214: Failed to determine if work {0} is checked out to instance {1}.

Cause: Failed to determine if the work is checked out to this instance.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01215: Error occurred querying check out work units for instance {0}.

Cause: Failed to determine the work units checked out to the instance.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01216: Failed to access work unit {0}.

Cause: Error occurred attempting to access work unit.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01217: Error waiting for work.

Cause: Error occurred while waiting for new work.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01218: Error waiting for work. Operation returned: {0}.

Cause: Operation used to work for new work returned the specified result.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01219: Work unit {0} is not checked out to instance {1}.

Cause: The work unit is not checked out to the specified instance.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-01220: Failed to lock work unit {0} by instance {1}.

Cause: Failed to lock the work unit by the specified instance.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-01250: Error retrieving available event work.

Cause: Error occurred while retrieving event work to process.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01251: Failed to access event work {0}.

Cause: Error occurred attempting to access event work.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01252: Failed to update event work {0}.

Cause: Error occurred attempting to update event work.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01253: Failed to delete event work {0}.

Cause: Error occurred attempting to delete event work.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01254: Failed to delete event work for request {0}.

Cause: Error occurred attempting to delete event work for a request.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01255: Failed to check in event work {0}.

Cause: Error occurred attempting to check in event work.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01256: Failed to check in event work for instance {0}.

Cause: Error occurred attempting to check in event work for an instance.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01257: Failed to add event. Event name: {0}, request: {1}.

Cause: Error occurred attempting to insert event work.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01258: Event work not found: {0}.

Cause: The specified event work was not found.

Action: None

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01259: Error waiting for event work.

Cause: Error occurred while waiting for new event work.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01260: Error waiting for event work. Operation returned: {0}.

Cause: Operation used to work for new event work returned the specified result.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01262: Event work {0} is not checked out to instance {1}.

Cause: The event work is not checked out to a specific instance.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-01263: Invalid event listener class, {0}.

Cause: The class name configured for the request listener is not a valid event listener class.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-01264: Unable to instantiate event listener for class, {0}.

Cause: Unable to instantiate an instance of an event listener class name.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01265: Unable to retrieve information needed to dispatch an event for request {0}.

Cause: Failed to retrieve information needed to dispatch an event.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01266: Failed to lock event work {0} by instance {1}.

Cause: Failed to lock the event work by the specified instance.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-01300: Unable to access content store for request {0}, file {1}. {2}.

Cause: Failed to access the content store.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01301: Failed to create content for request {0}, content name {1}. {2}.

Cause: Failed to create content for the request.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01302: Failed to update content for request {0}, content name {1}. {2}.

Cause: Failed to update content for the request.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01303: Failed to import file to content store for request {0}, file {1}. {2}.

Cause: Failed to import file to the content store for the request.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01304: Failed to export content for request {0}, content name {1}. {2}.

Cause: Failed to export content for the request.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01305: Failed to delete content for request {0}, content name {1}. {2}.

Cause: Failed to delete content for the request.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01306: Failed to delete all content for request {0}. {1}.

Cause: Failed to delete all content for the request.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01307: Invalid write to output content for request {0}, content name {1}.

Cause: Invalid write to content due to incorrect content type.

Action: Ensure the type of data you are writing is compatible with the content type.

Level: 1

Type: WARNING

Impact: Other

ESS-01308: The content does not exist for request {0}, content name {1}.

Cause: The content does not exist for the request.

Action: Ensure you are using the correct content name.

Level: 1

Type: WARNING

Impact: Other

ESS-01309: Invalid content handle.

Cause: The content handle is invalid.

Action: Re-open the content and use the valid handle.

Level: 1

Type: WARNING

Impact: Other

ESS-01310: The file does not exist for request {0}, file name {1}.

Cause: The file does not exist for the request.

Action: Ensure you are using the correct file name.

Level: 1

Type: WARNING

Impact: Other

ESS-01312: Failed to close the output file for request {0}, file name {1}. {2}.

Cause: Failed to close the output file for the request.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01313: Invalid directory for request {0}, directory {1}.

Cause: The directory is invalid for the request.

Action: Ensure you are using the correct file name.

Level: 1

Type: WARNING

Impact: Other

ESS-01314: Incompatible content operation for request {0}, content name {1}.

Cause: The operation is incompatible with the existing content type.

Action: It is not allowed to export output content that was not imported. Updating existing output content using the API requires using the same content type.

Level: 1

Type: WARNING

Impact: Other

ESS-01315: Error creating directory for request {0}, directory {1}.

Cause: Failed to create the request directory.

Action: Ensure that RequestFileDirectory is configured correctly for the application and that the directory is writeable.

Level: 1

Type: WARNING

Impact: Other

ESS-01316: Error exporting output content for request {0}, status {1}.

Cause: Failed to export output content to the request output directory.

Action: Ensure that RequestFileDirectory is configured correctly for the application and that the directory is writeable. Check the log for errors.

Level: 1

Type: WARNING

Impact: Other

ESS-01317: Error importing output content for request {0}, status {1}, directory {2}. {3}

Cause: Failed to import output files from the request output directory.

Action: Check the log for errors.

Level: 1

Type: WARNING

Impact: Other

ESS-01318: Failed to import the log for request {0}, log file {1}. {2}.

Cause: Failed to import the request log.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01319: Invalid content handle mode for request {0}, content {1}.

Cause: The content handle is opened in the wrong mode for the operation being performed. The content must be opened in read for fetching and write for importing.

Action: Re-open the content in the correct mode for the operation being performed.

Level: 1

Type: WARNING

Impact: Other

ESS-01320: Invalid RequestFileDirectory {0} for application {1}.

Cause: The application has an invalid RequestFileDirectory configured.

Action: Configure a valid RequestFileDirectory for the application.

Level: 1

Type: ERROR

Impact: Other

ESS-01321: Error deleting files for request {0}, directory {1}.

Cause: Failed to delete files from the request work directory.

Action: Manually delete the files from the file system.

Level: 1

Type: WARNING

Impact: Other

ESS-01322: Error preserving log or output files for request {0}. {1}

Cause: Failed to preserve log or output files from the request work directory. This may be due to a problem with the directory or a previous version of the output file may already exist.

Action: No action. The files have been removed.

Level: 1

Type: WARNING

Impact: Other

ESS-01500: Dispatcher cannot be started while in {0} state.

Cause: Attempted to start the dispatcher when it is in a state for which the operation is not allowed.

Action: Retry the operation when the dispatcher state is STOPPED.

Level: 1

Type: ERROR

Impact: Other

ESS-01501: Dispatcher cannot be stopped while in {0} state.

Cause: Attempted to stop the dispatcher when it is in a state for which the operation is not allowed.

Action: Retry the operation when the dispatcher state is STARTING or RUNNING.

Level: 1

Type: ERROR

Impact: Other

ESS-01502: Processor cannot be started while in {0} state.

Cause: Attempted to start the processor when it is in a state for which the operation is not allowed.

Action: Retry the operation when the processor state is STOPPED.

Level: 1

Type: ERROR

Impact: Other

ESS-01503: Processor cannot be stopped while in {0} state.

Cause: Attempted to stop the processor when it is in a state for which the operation is not allowed.

Action: Retry the operation when the processor state is STARTING or RUNNING.

Level: 1

Type: ERROR

Impact: Other

ESS-01504: Cannot add endpoint {0} for application {1} because endpoint {2} already exists for application {3}.

Cause: The endpoint to add conflicts with an already existing endpoint.

Action: Modify the endpoint name.

Level: 1

Type: ERROR

Impact: Deployment

ESS-01505: Failed to retrieve information for request {0}.

Cause: Failed to retrieve runtime information for a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01506: Unable to create diagnostic incident. {0}

Cause: Failed to create diagnostic incident.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01507: Unable to register diagnostic dumps or rules. {0}

Cause: Failed to register diagnostic dumps or rules.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01508: Unable to unregister diagnostic dumps or rules. {0}

Cause: Failed to unregister diagnostic dumps or rules.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01509: Unable to create the diagnostic dump {0}. {1}

Cause: Failed to create the diagnostic dump.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01601: JobSet request {0} completed with an invalid final state {1}.

Cause: A JobSet request has been marked as completed, but has an unexpected final state.

Action: Review the log file for errors pertaining to the request.

Level: 1

Type: ERROR

Impact: Other

ESS-01602: First step is not defined in serial JobSet: {0}.

Cause: Cannot process a JobSet request due to invalid JobSet definition. The first step of a serial JobSet is not defined.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-01603: Error dispatching subrequests for parent request {0}.

Cause: An error occurred while attempting to dispatch subrequests for a parent request in PAUSED state.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01604: Failed to create {0} work unit for request {1}.

Cause: Unable to create the specified work unit for a request.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01605: Failed to create event, {0}, for request {1}.

Cause: An error occurred while attempting to create an event for a request.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01606: Failed to mark request {0} as completed.

Cause: An error prevented the request from being marked completed

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01607: Request {0} cannot be marked complete. State is {1}, process phase is {2}.

Cause: The request state and/or process phase prevents a request from being completed.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-01700: Unrecognized request type : {0}.

Cause: The job type used for the request is not supported.

Action: Correct the job type definition.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01701: Unable to instantiate executable wrapper for execution type {0}.

Cause: Unable to instantiate wrapper class used to process the request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Installation

ESS-01702: Unable to instantiate pre-process callback handler for request {0} using class name, {1}.

Cause: Failed to instantiate an object for the pre-process callback handler class associated with a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01703: Unable to instantiate post-process callback handler for request {0} using class name, {1}.

Cause: Failed to instantiate an object for the post-process callback handler class associated with a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01704: Error occurred at initiate stage during execution of request {0}. {1}

Cause: An error occurred during the initiate stage of a request execution.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01705: Error occurred at finalize stage during execution of request {0}. {1}

Cause: An error occurred during the finalize stage of a request execution.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01706: Invalid execution result code, {0}, for request {1}.

Cause: A REQUEST_FINALIZATION event contained an unknown result code.

Action: This indicates an internal error. Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01707: Unable to instantiate Executable for Java request {0} using class name, {1}.

Cause: Failed to instantiate Executable object for a Java request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01708: Database job for request {0} ended with error: {1}.

Cause: Execution of a SQL request has ended with a error.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01709: Database job for request {0} ended with warning: {1}.

Cause: Execution of a SQL request has ended with a warning.

Action: None.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01710: Database job for request {0} was cancelled.

Cause: Execution of a SQL request has been cancelled.

Action: None.

Level: 1

Type: NOTIFICATION

Impact: Programmatic

ESS-01711: Database job for request {0} was paused. Paused state value: {1}.

Cause: Execution of a SQL job request has been paused to allow one or more sub-requests to execute.

Action: None. The execution of the paused request will be resumed once the sub-requests have completed.

Level: 1

Type: NOTIFICATION

Impact: Programmatic

ESS-01712: Failed to create database job for request {0}.

Cause: An error occurred trying to create an Oracle Scheduler job used to execute a SQL job request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01713: Error cancelling database job for request {0}.

Cause: An error occurred during post-execution clean tasks for an Oracle Scheduler job used to execute a SQL job request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01714: Database job for request {0} ended with business error: {1}.

Cause: Execution of a SQL request has ended with a biz error.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01715: Failed to create database job for request {0} using Oracle Scheduler job class {1}.

Cause: An error occurred trying to create an Oracle Scheduler job used to execute a SQL job request with the given Oracle Scheduler job class.

Action: Verify the EXECUTE privilege on the Oracle Scheduler job class has been granted to the ESS schema user. Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-01716: Unable to process JobSet request {0}. JobSet definition has no steps: {1}

Cause: The JobSet definition associated with a JobSet request has no steps.

Action: Review the metadata of the JobSet definition for the specified metadata id.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01900: Error constructing ESS command {0}. {1}

Cause: An error is present in the command format.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

ESS-01901: Unsupported value, {0}, for attribute {1}.

Cause: An unknown value was specified for a parameter.

Action: Specify a valid attribute value.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-01903: Unknown command type {0}. {1}

Cause: An unknown command type was submitted.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-01904: Document is not valid for work {0}.

Cause: The command document is invalid for this Enterprise Scheduler server

Action: None. The command will be deferred.

Level: 1

Type: WARNING

Impact: Other

ESS-01905: Attribute {0} value {1} from command document does not match value {2} from command creation.

Cause: The internal command state is inconsistent for the given attribute.

Action: Contact administrator.

Level: 1

Type: WARNING

Impact: Other

ESS-01906: Error retrieving available command work.

Cause: Error occurred while retrieving command work to process.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01907: Failed to access command work {0}.

Cause: Error occurred attempting to access command work.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01908: Failed to update command work {0}.

Cause: Error occurred attempting to update command work.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01909: Failed to delete command work {0}.

Cause: Error occurred attempting to delete command work.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01910: Failed to delete command work for request {0}.

Cause: Error occurred attempting to delete command work for a request.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01911: Failed to check in command work {0}.

Cause: Error occurred attempting to check in command work.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01912: Failed to check in command work for instance {0}.

Cause: Error occurred attempting to check in command work for an instance.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-01913: Command work not found: {0}.

Cause: The specified command work was not found.

Action: None

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01914: Command work {0} is not checked out to instance {1}.

Cause: The command work is not checked out to a specific instance.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-01915: Failed to lock command work {0} by instance {1}.

Cause: Failed to lock the command work by the specified instance.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-01980: Batch delete initialization failed.

Cause: An error occurred during initialization of batch delete support.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01981: Failed to delete request {0}. Reason: {1}

Cause: An error occurred attempting to delete a request.

Action: None

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01982: Insufficient privileges to delete request {0}.

Cause: Execution user of a batch delete job does not have sufficient privileges to delete the request.

Action: Batch delete job should be submitted only by ESS administrator

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01983: Error determining requests for batch delete.

Cause: An error occurred attempting to determine requests to delete.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01984: Error occurred while executing batch delete request {0}. Cause: {1}

Cause: An error occurred during request execution.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-01985: Execution of request {0} was cancelled.

Cause: Request execution was canceled.

Action: None

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01987: Runtime store error during batch delete.

Cause: Runtime store error occurred during batch delete opearation.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01988: Failed to lock request for batch delete.

Cause: Unable to lock one or more requests during batch delete operation

Action: None

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01989: Batch delete request {0} failed to delete request {1}. Reason: {2}

Cause: Batch delete job failed to delete the specified request.

Action: Review log file to determine the reason.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-02001: User {0} does not have execute permission on metadata object {1}. Request {2} execution is aborted.

Cause: User {0} does not have execute permission on metadata object {1}. Request {2} execution is aborted.

Action: Check the policy assignment..

Level: 1

Type: ERROR

Impact: Other

ESS-02002: User {0} does not have sufficient privilege to perform operation {1}.

Cause: User {0} does not have sufficient privilege to perform operation {1}.

Action: Grant the policy to the user {0}..

Level: 1

Type: ERROR

Impact: Other

ESS-02003: User {0} does not have sufficient privilege to perform operation {1} on request {2}.

Cause: User {0} does not have sufficient privilege to perform operation {1} on request {2}.

Action: Grant the policy to the user {0}..

Level: 1

Type: ERROR

Impact: Other

ESS-02004: User or appid {0} is not a valid entry in the idstore configured in jps-config.xml.

Cause: {0} can not be authenticated.

Action: Check the user settting.

Level: 1

Type: ERROR

Impact: Other

ESS-02005: User {0} does not have {1} privilege on metadata object {2}. Request {3} validation failed.

Cause: User {0} does not have {1} privilege on metadata object {2}. Request {3} validation failed.

Action: Check the policy assignment..

Level: 1

Type: ERROR

Impact: Other

ESS-02006: User {0} does not have sufficient privilege to perform operation {1} on job set {2}, failed steps are {3}.

Cause: User {0} does not have sufficient privilege to perform operation {1} on jobset {2}, failed steps are {3}.

Action: Grant the policy to the user {0}..

Level: 1

Type: ERROR

Impact: Other

ESS-02007: User or appid {0} whom job {1} runs is not a valid entry in the idstore configured in jps-config.xml.

Cause: The user or appid {0} is not a valid identity or can not be authenticated.

Action: Check your metadata definition.

Level: 1

Type: ERROR

Impact: Other

ESS-02200: Mismatched request handles for request {0}.

Cause: The request may have been retried.

Action: Update with request execution context from new execution if desired.

Level: 1

Type: ERROR

Impact: Other

ESS-02220: Failed to deliver web service callback for message {0} for request {1}.

Cause: The web service asynchronous callback message could not be delivered.

Action: The action may be retried. Check the log files.

Level: 1

Type: WARNING

Impact: Other

ESS-05000: Error occurred. {0}

Cause: Enterprise Scheduler Service encountered an error.

Action: Review the log file for indications of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-05010: Request {0} not found.

Cause: Request with the given request id can not be found in the database.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-05011: Request {0} set to {1} state.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-05012: Request {0} set to {2} state. Previous state was {1}.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-05013: Request {0}. Process phase {1} not in valid phases {2}.

Cause: The process phase of the request is inconsistent with its current status.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-05021: Failed to begin transaction.

Cause: Being of a user transaction failed.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-05022: Failed to commit transaction.

Cause: Failed to commit the transaction.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-05023: Failed to rollback transaction.

Cause: Failed to rollback the transaction.

Action: Review the log file for runtime cause.

Level: 1

Type: ERROR

Impact: Other

ESS-05024: Failed to set transaction timeout.

Cause: Failed to set transaction timeout.

Action: Review the log file for runtime cause.

Level: 1

Type: WARNING

Impact: Other

ESS-05038: Failed to find JNDI resource for {0}.

Cause: Failed to perform a JNDI lookup for a given resource name.

Action: Verify the configuration for the resource.

Level: 1

Type: ERROR

Impact: Configuration

ESS-05039: Error occurred closing JNDI naming context.

Cause: An error occurred while trying to close a JNDI naming context.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-05043: Failed to commit SQL transaction.

Cause: An error occurred trying to commit database transaction.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-05044: Failed to rollback SQL transaction.

Cause: An error occurred trying to rollback database transaction.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-05045: Error using SQL ResultSet. {0}

Cause: An error occurred while using an SQL ResultSet.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-05046: Failed to close an SQL ResultSet.

Cause: An error occurred trying to close an SQL ResultSet.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-05047: Failed to close an SQL Statement.

Cause: An error occurred trying to close an SQL Statement.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-05048: Failed to obtain a database connection.

Cause: An error occurred trying to obtain a database connection.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-05049: Failed to close a database connection.

Cause: An error occurred trying to close a database connection.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-05053: Failed to map object of type {0} to CompositeData.

Cause: An error occurred converting an ESS object to a javax.management.openmbean.CompositeData object

Action: Contact Oracle Support Services

Level: 32

Type: INCIDENT_ERROR

Impact: Other

ESS-05054: Failed to map CompositeData object to {0}.

Cause: An error occurred converting a javax.management.openmbean.CompositeData object to an ESS object

Action: Contact Oracle Support Services

Level: 32

Type: INCIDENT_ERROR

Impact: Other

ESS-05055: Illegal state transition from {0} to {1} for request {2}.

Cause: An update event's timing may have tried to change the state after the request has begun a transition to a terminal state.

Action: This warning can be ignored.

Level: 1

Type: ERROR

Impact: Other

ESS-05100: Operator {1} is invalid with query field {0}. Valid operators are: {2}.

Cause: Operator is invalid for the given query field.

Action: Use a valid operator.

Level: 1

Type: WARNING

Impact: Other

ESS-05101: Comparator {1} is invalid with query field {0}. Valid comparators are: {2}.

Cause: Comparator is invalid for the given query field.

Action: Use a valid comparator.

Level: 1

Type: WARNING

Impact: Other

ESS-05102: Value of type {1} is invalid with query field {0}. Valid value types are: {2}.

Cause: Value type is invalid for the given query field.

Action: Use a valid value type.

Level: 1

Type: WARNING

Impact: Other

ESS-05103: Value of type null is invalid with query field {0}.

Cause: Null value type is invalid for the given query field.

Action: Use a valid non-null value type.

Level: 1

Type: WARNING

Impact: Other

ESS-05104: Failed to check in {0} work unit {1} for request {2}. {3}

Cause: The work unit for the given request could not be checked in or deleted.

Action: The work unit operation should be automatically retried, so no action is necessary.

Level: 1

Type: WARNING

Impact: Other

ESS-05105: Metadata of type {0} cannot be customized. Only metadata of the following types can be customized: {1}.

Cause: An invalid metadata type was provided.

Action: Provide a valid customizable metadata type.

Level: 1

Type: WARNING

Impact: Other

ESS-05106: Property {0} cannot be assigned a value of type {1}. Values for property {0} can only have the following types: {2}.

Cause: The data type of the provided property is not valid.

Action: Provide a value with the correct data type.

Level: 1

Type: WARNING

Impact: Other

ESS-05107: An error occurred while parsing the metadata object id string: {0}

Cause: An error occurred while parsing a metadata object id string.

Action: See base exception for detailed underlying cause.

Level: 1

Type: WARNING

Impact: Other

ESS-05108: The user provided metadata type of {0} does not match the metadata type of {1} in the metadata object id string

Cause: The metadata type specified by the user does not match the metadata type specified by the metadata object id string.

Action: Check the metadata repository to ensure the metadata is correct or specify the correct type and try again.

Level: 1

Type: WARNING

Impact: Other

ESS-05109: While performing a metadata query, the following problem was detected with one of the query results: {1} The query will continue but exclude the piece of metadata with name {0}. This may affect the expected query results.

Cause: A problem occurred while processing a result of the metadata query.

Action: Check the piece of metadata causing the problem for any issues and check the health of the metadata respository.

Level: 1

Type: ERROR

Impact: Other

ESS-05110: An error occurred while retrieving the metadata object with name {0} of type {1}.

Cause: A problem occurred while retrieving a piece of metadata.

Action: See the base exception for the cause then check the piece of metadata causing the problem for any issues and check the health of the metadata respository.

Level: 1

Type: ERROR

Impact: Other

ESS-05202: ESS connections.xml {0} property lookup returns null. Please verify adf-domain-config for ESS is set up and configured.

Cause: ESS connections.xml property lookup returns NULL.

Action: Verify adf-domain-config for ESS is set up and configured.

Level: 1

Type: WARNING

Impact: Other

ESS-05203: ESS connections.xml {0} property lookup returns Unresolved EL Expression. Please verify adf-domain-config for ESS is set up and configured.

Cause: ESS connections.xml property lookup returns Unresolved EL Expression.

Action: Verify adf-domain-config for ESS is set up and configured.

Level: 1

Type: WARNING

Impact: Other

ESS-05204: NamingException looking up EssConnection {0}.

Cause: NamingException looking up EssConnection.

Action: Review the log file for attached exceptions to determine the cause.

Level: 1

Type: ERROR

Impact: Other

ESS-05205: Error reading EssConnection Tokens from adf-domain-config.

Cause: Error reading EssConnection Tokens from adf-domain-config.

Action: Review the log file for attached exceptions to determine the cause.

Level: 1

Type: ERROR

Impact: Other

ESS-05206: Error writing EssConnection Tokens to adf-domain-config.

Cause: Error writing EssConnection Tokens to adf-domain-config.

Action: Review the log file for attached exceptions to determine the cause.

Level: 1

Type: ERROR

Impact: Other

ESS-05490: Service MBeans registration failed.

Cause: Service MBeans registration failed.

Action: Review the log file for underlying causes.

Level: 1

Type: WARNING

Impact: Other

ESS-05700: Failed to obtain a metadata service instance. {0}

Cause: Failed to obtain a metadata service instance.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-05704: An error occured invoking the MetadataService MBean. {0}

Cause: An error occurred invoking the RuntimeService MBean.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05705: Failed to save the {0} with name {1} in application {2}.

Cause: Failed to save the metadata object.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05706: {0} with name {1} does not exist in application {2}.

Cause: Unable to find the metadata object.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05707: {0} with name {1} already exists in application {2}.

Cause: The metadata object already exists.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05708: Failed to delete the {0} with name {1} in application {2}.

Cause: Unable to delete the metadata object

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05709: Metadata parameter {0} starts with {1} which is a reserved parameter keyword.

Cause: A property defined by the metadata object contains a reserved keyword.

Action: Remove the reserved keyword from the property name.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05710: A validation error occurred while validating JobSet step {0}.

Cause: A JobSet step failed validation.

Action: See the base validation exception for the original validation error.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05711: A null value cannot be used when querying the {0} field.

Cause: A value of null was used as the query value.

Action: Provide a non-null argument.

Level: 1

Type: WARNING

Impact: Other

ESS-05712: The metadata object with id {0} cannot be deleted because it belongs to one of the following restricted packages: {1}. However, metadata in the custom namespace, {2}, can be deleted.

Cause: The metadata object to be deleted resides in a read-only package.

Action: This metadata object cannot be deleted by end users.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05713: The metadata object with id {0} cannot be updated because it belongs to one of the following restricted packages: {1}. However, metadata in the customer namespace, {2}, can be updated.

Cause: The metadata object to be updated resides in a read-only package.

Action: This metadata object cannot be updated by end users.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05714: The metadata object with id {0} cannot be customized. Only metadata in the following packages can be customized: {1}. However, metadata in the customer namespace, {2}, cannot be customized.

Cause: The metadata object to be customized does not reside in a package that allows customization.

Action: This metadata object cannot be customized by end users.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05715: Metadata parameter {0} cannot have value {1} because {1} is a reserved value.

Cause: The value of a property defined by the metadata object contains a reserved keyword.

Action: Change the value of the property.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-05716: Metadata parameter {0} cannot have an empty or null value.

Cause: The value of a property defined by the metadata object was empty or null.

Action: Change the value of the property.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-06000: Failed to obtain a runtime service instance. {0}

Cause: Failed to obtain a runtime service instance.

Action: Review log file for underlying cause.

Level: 1

Type: ERROR

Impact: Other

ESS-06002: Failed to close runtime service handle. {0}

Cause: Failed to close runtime service handle.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06003: Runtime service system failure. {0}

Cause: Runtime service system failure.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06100: No request found for the given id {0}.

Cause: A request was not found in ESS runtime storage corresponding to the indicated request identifier.

Action: Specify a request identifier for an existing request.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-06102: An error occured invoking the RuntimeService MBean.

Cause: An error occurred invoking the RuntimeService MBean.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06500: Starting ESS resource adapter.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06501: Stopping ESS resource adapter.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06502: Endpoint activation for {0}.

Cause:

Action:

Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06503: Endpoint deactivation for {0}.

Cause:

Action:

Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06510: Registering application, {0}, via ClassLoader: {1}

Cause:

Action:

Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06511: Registered application: {0} adfConfigUrl: {1} connUrl: {2}

Cause:

Action:

Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06512: Removed registered configuration for application {0}.

Cause:

Action:

Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06514: Application {0} is already registered.

Cause:

Action:

Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06515: The logical name of this application, {0}, is already in use by the following deployed applications (possibly in different domains): {1}.

Cause: The logical name of this application is already in use by other applications using a different deployed name as this application.

Action: If this is the same application as one of the above applications then its deployed name should be changed to match. Otherwise, select a unique logical name for this application.

Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06516: The deployed name of this application, {0}, is already in use by the following logical applications (possibly in different domains): {1}.

Cause: The deployed name of the application is already in use by other applications using a different logical name as this application.

Action: If this is the same application as one of the above applications then its logical name should be changed to match. Otherwise, select a unique deployed name for this application.

Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06517: Logical application name {0} is a reserved keyword.

Cause: The specified logical application name is a reserved keyword.

Action: Change the name of the logical application.

Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06521: Failed to start request dispatcher.

Cause: An error occurred while trying to start the request dispatcher.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06522: Failed to start request processor.

Cause: An error occurred while trying to start the request processor.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06523: Failed to start system event service.

Cause: An error occurred while trying to start the system event service.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06524: Failed to start application event service.

Cause: An error occurred while trying to start the application event service.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06525: Failed to start heartbeat monitor.

Cause: An error occurred while trying to start the heartbeat monitor.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06526: Failed to update configuration information.

Cause: An error occurred while trying to update configuration information.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06527: Failed to start deferred monitor.

Cause: An error occurred while trying to start the deferred monitor.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06528: Failed to start work unit worker.

Cause: An error occurred while trying to start the work unit worker.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06529: Failed to start change event service.

Cause: An error occurred while trying to start the change event service.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06530: Dispatcher cannot be started when it is in the {0} state.

Cause: Dispatcher cannot be started when it is in the specified state.

Action: Start the dispatcher when it is in STOPPED state.

Level: 1

Type: WARNING

Impact: Other

ESS-06531: Dispatcher cannot be stopped when it is in the {0} state.

Cause: Dispatcher cannot be stopped when it is in the specified state.

Action: Stop the dispatcher when it is in STARTING or RUNNING state.

Level: 1

Type: WARNING

Impact: Other

ESS-06532: Processor cannot be started when it is in the {0} state.

Cause: Processor cannot be started when it is in the specified state.

Action: Start the processor when it is in STOPPED state.

Level: 1

Type: WARNING

Impact: Other

ESS-06533: Processor cannot be stopped when it is in the {0} state.

Cause: Processor cannot be stopped when it is in the specified state.

Action: Stop the processor when it is in STARTING or RUNNING state.

Level: 1

Type: WARNING

Impact: Other

ESS-06538: No endpoint is available for {0}.

Cause: An application using the specified endpoint application name is not deployed.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06539: Could not create endpoint for {0}.

Cause: An error occurred creating an application endpoint.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06540: Failed to get an endpoint to run dispatcher for application {0}.

Cause: Dispatch monitor was unable to obtain an application endpoint. This may happen when the system is busy and does not necessary indicate a problem.

Action: Review the log file for indications of a problem if this persists.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06541: Error during dispatch for application {0}.

Cause: Error during dispatch for application.

Action: Review the log for underlying causes.

Level: 1

Type: WARNING

Impact: Other

ESS-06542: Error getting applications to dispatch.

Cause: Error getting applications for dispatch.

Action: Review the log for underlying causes.

Level: 1

Type: WARNING

Impact: Other

ESS-06543: Failed to deactivate endpoint for application {0}.

Cause: An error occurred while removing an application endpoint.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06551: Failed processing trigger for {0} event.

Cause: Failed processing event trigger.

Action: Review the log for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06552: Failed processing trigger for {0} event for request {1}.

Cause: Failed processing event trigger.

Action: Review the log for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06553: Failed processing lifecycle for {0} event for request {1}.

Cause: Failed processing lifecycle event for a request.

Action: Review the log for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06557: Failed to start heartbeat worker {0}.

Cause: ESS heart beat monitor failed to start due to a system failure.

Action: Check the causeBy clause of this exception to find more details.

Level: 1

Type: WARNING

Impact: Other

ESS-06558: Failed to get an endpoint to run a heartbeat for application {0}.

Cause: Heartbeat monitor was unable to obtain an application endpoint. This may happen when the system is busy and does not necessary indicate a problem.

Action: Review the log file for indications of a problem if this persists.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06560: Error encountered by event worker.

Cause: Error encountered by event worker.

Action: Review the log for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06570: Failed to get metadata for work assignment {0}.

Cause: Unable to retrieve work assignment metadata when analyzing work assignment bindings. The work assignment is ignored.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06571: Failed to get workshift metadata ({0}) for work assignment {1}.

Cause: Unable to retrieve workshift metadata when analyzing a work assignment binding. The work assignment processing will ignore the workshift.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06572: Failed to get schedule metadata ({0}) for work assignment {1}.

Cause: Unable to retrieve schedule metadata when analyzing a work assignment binding. The work assignment processing will ignore the workshift associated with the schedule.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06573: Failed to start work assignment {0}.

Cause: Unable to start the first worker for the work assignment. The start will be retried in a short time.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06574: Failed to start starvation thread for work assignment {0}.

Cause: Unable to start the starvation worker for the work assignment. The work assignment will be activated without the starvation worker.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06575: Skipping inactive work assignment {0}.

Cause: The work assignment is defined as inactive and is being skipped.

Action: If the work assignment should be active, change it to active and reload work assignment metadata.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06576: Binding default work assignment.

Cause: The default work assignment is being bound because no user-defined work assignments were bound.

Action: No action is necessary.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06577: Skipping inactive workshift {0} for work assignment {1}.

Cause: The workshift is being skipped because it is inactive. It may have an allocation of 0 or a duration of 0.

Action: No action is necessary.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06578: Started work assignment {0}.

Cause: Started the work assignment.

Action: No action is necessary.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06579: Stopped work assignment {0}.

Cause: Stopped the work assignment.

Action: No action is necessary.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06580: Skipping invalid work assignment {0}.

Cause: The work assignment is being ignored because it is invalid.

Action: Check the work assignment and correct the problem. Ensure the work assignment has at least one workshift defined.

Level: 1

Type: ERROR

Impact: Other

ESS-06581: Skipping invalid work assignment binding {0}.

Cause: The work assignment is being ignored because the binding is invalid.

Action: Check the work assignment binding mode and correct the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06582: Skipping completed work assignment {0}.

Cause: The work assignment has completed and will never again become active. It is being skipped.

Action: If the work assignment should not be completed, check the workshift schedules to ensure they are correct and reload work assignment metadata.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06583: Cannot delete bound work assignment {0}.

Cause: A work assignment that is bound may not be deleted.

Action: Unbind the work assignment and then delete it.

Level: 1

Type: WARNING

Impact: Other

ESS-06584: Reloading metadata for work assignment {0}.

Cause: Reloaded the work assignment metadata.

Action: No action is necessary.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06585: Unable to bind work assignment {0} due to invalid workshift {1}.

Cause: In order to bind a work assignment, each of its workshifts must have an allocation of at least one. If the workshift has a schedule, the schedule must be unexpired, and the workshift duration must be > 0.

Action: Fix the workshift and try again to bind the work assignment.

Level: 1

Type: WARNING

Impact: Other

ESS-06586: Work assignment must include at least one workshift to be bound, {0}.

Cause: To be bound, a work assignment must have at least one workshift and be active.

Action: Fix the work assignment and try again to bind it.

Level: 1

Type: WARNING

Impact: Other

ESS-06587: Invalid update of a bound work assignment {0}.

Cause: A work assignment that is bound must have at least one workshift.

Action: Add at least one workshift to the work assignment and retry the update.

Level: 1

Type: WARNING

Impact: Other

ESS-06588: Failed to bind the ESS internal work assignment. {0}.

Cause: Unable to bind the ESS internal work assignment. The server will be started without the binding, and the default work assignment will be used.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06589: Binding the ESS internal work assignment.

Cause: The ESS internal work assignment is being bound for a new server.

Action: No action is necessary.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06590: Error encountered by the worker for work assignment {0}.

Cause: Error encountered by worker for work assignment.

Action: Review the log file for underlying causes.

Level: 1

Type: WARNING

Impact: Other

ESS-06592: Error while processing request {0} for application {1}.

Cause: Error while processing request for application

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06593: Required property, {0}, is not present in message received for work assignment {1}.

Cause: Required property is not present in message received for work assignment.

Action: Add the required request property for work assignment.

Level: 1

Type: ERROR

Impact: Other

ESS-06594: Failed to schedule additional work for work assignment {0}. {1}

Cause: Failed to schedule additional work for work assignment.

Action: Review the log file for underlying causes.

Level: 1

Type: WARNING

Impact: Other

ESS-06595: Failed to update request history for request {0}.

Cause: Failed to update request history for request.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06610: Failed processing request {0}, {1} stage.

Cause: Failed processing request.

Action: Review the log file for underlying causes.

Level: 1

Type: WARNING

Impact: Other

ESS-06617: Failed to extract event information for event name {0}.

Cause: Failed to extract event information for event name.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06618: Error while dispatching event {0}, request {1}, to request listeners.

Cause: Error while dispatching event to request listeners.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06619: Error during trigger processing of event {0}, application {1}.

Cause: Error during trigger processing of event for the application.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-06620: Failed to get an endpoint for application {0}.

Cause: Failed to get an endpoint for application. Endpoint not available for processing.

Action: Make sure endpoint application is available for processing.

Level: 1

Type: WARNING

Impact: Other

ESS-06621: Error while calling endpoint for application {0}.

Cause: Failure encountered while calling endpoint for application.

Action: Ensure application is deployed and running.

Level: 1

Type: ERROR

Impact: Other

ESS-06622: Error while calling endpoint for application {0}, method {1}.

Cause: Error occured while calling endpoint for application.

Action: Ensure application is deployed and running.

Level: 1

Type: ERROR

Impact: Other

ESS-06640: Error encountered by worker.

Cause: Error encountered by worker.

Action: Review the log file for underlying causes.

Level: 1

Type: WARNING

Impact: Other

ESS-06641: Failed to schedule additional work. {0}

Cause: Failed to schedule additional work.

Action: Review the log file for underlying causes.

Level: 1

Type: WARNING

Impact: Other

ESS-06645: Specialization is incorrectly formed and invalid for work assignment {0}. {1}

Cause: The work assignment specialization is incorrectly formed and invalid.

Action: Fix the work assignment specialization and try again.

Level: 1

Type: WARNING

Impact: Other

ESS-06646: Exclusive binding requires non-empty specialization, work assignment {0}.

Cause: Exclusive binding requires the work assignment specialization is non-empty.

Action: Define a specialization for the work assignment and try binding it again.

Level: 1

Type: WARNING

Impact: Other

ESS-06700: Failed to check in event work {0} for {1} event, request {2}.

Cause: The event work for the given event could not be checked in or deleted.

Action: The event work operation should be automatically retried, so no action is necessary.

Level: 1

Type: WARNING

Impact: Other

ESS-06701: Failed to publish request listener event during processing of work {0}. Event: {1}, request: {2}.

Cause: An error occurred during an attempt to publish an event to be sent to the event listener of a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06710: Unable to dispatch event {0} for request {1} to event listener.

Cause: The event work is not checked out to a specific instance.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06711: Error invoking event listener for request {0}. Event name: {1}, event request: {2}

Cause: Event listener was invoked and failed with an error.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06712: Event listener action for event {0}, request {1}. Status: [{2}], Message: [{3}]

Cause: Information from EventListenerAction returned by the listener.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-06713: Delivery limit reached for event {0}, request {1}. No further delivery attempts will be made.

Cause: The event has been delivered to the event listener the maximum allowed times.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-06714: Failed to authenticate user {0}. Dispatch event {1} for request {2} as an unprivileged call. Error: [{3}]

Cause: Failed to authenticate user. Event listener will be invoked in an unprivileged block.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06800: Error handling {0} event for request {1} by request dispatcher.

Cause: Error handling event for request by request dispatcher.

Action: Review the log for underlying causes.

Level: 1

Type: WARNING

Impact: Other

ESS-06802: Request {0} is in {1} state. Skipping the processing.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06803: Request {0} is in {1} state. Skipping processing and deleting from wait queue.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06804: Request {0} has EXPIRED. Skipping processing and deleting from wait queue.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06805: Request {0} is in illegal state {1} ({2}). Skipping processing and deleting from wait queue.

Cause: Request is in illegal state. Skipping processing and deleting from wait queue.

Action: Review the log for underlying causes.

Level: 1

Type: WARNING

Impact: Other

ESS-06806: Request {0} not found in runtime store. Skipping processing and deleting from wait queue.

Cause: Request not found in runtime store. Skipping processing and deleting from wait queue.

Action: No Action is necessary.

Level: 1

Type: WARNING

Impact: Other

ESS-06807: Error occurred while dispatching requests.

Cause: An error occurred while attempting to dispatch one or more requests.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06816: Error processing request {0} by request dispatcher.

Cause: An error occurred during the request dispatching process for the given request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06817: No subrequests exist for paused request {0}. Request execution will be resumed.

Cause: No sub-requests are active for this paused request.

Action: None

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06820: Failed to retrieve Schedule for request {1}.

Cause: Failed to retrieve Schedule needed to determine the next schedule execution time.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06821: Failed to update error information for request {0}. {1}

Cause: Failed to update the error information for a request.

Action: Review the log file for to determine the nature of the problem.

Level: 1

Type: ERROR

Impact: Other

ESS-06830: Error occurred processing post-execution work for request {0}. WorkId: {1}

Cause: An error occurred while processing a post-execution work unit.

Action: Review the log file to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06831: Cannot process post-execution work for request {0}. State is {1}, process phase is {2}. WorkId: {3}

Cause: The request state and/or process phase prevents a post-execution work unit for a request from being processed. The work will be discarded.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-06832: Failed to publish the metadata change event for {0}, appName={1}. {2}

Cause: Failed to publish the change event for the metadata change notification.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06833: Unrecognized metadata change type {0}, appName={1}, metaId={2}, origServer={3}

Cause: Unrecognized metadata change type in metadata change event.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-06834: Ignoring change event as metadata cannot be found: {0}, appName={1}. {2}

Cause: Received metadata change event and metadata does not exist; it may have been deleted since the change happened.

Action: Review the log file for attached exceptions to determine the nature of the problem, if any.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-07000: Error handling {0} event for request {1} by request processor.

Cause: Error handling event for request by request processor.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-07001: Error processing request {0}.

Cause: Error processing request.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-07002: Failed to obtain system executable wrapper for request {0}.

Cause: Possible causes include unknown job type, user login error, classloading issues...

Action: Review the causeBy exception clause to determine the specific failure.

Level: 1

Type: ERROR

Impact: Installation

ESS-07003: Execution warning for request {0}. Reason: {1}

Cause: Execution error warning for request.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-07004: Execution error for request {0}. Reason: {1}

Cause: Execution error for request.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-07005: Execution cancelled for request {0}. Reason: {1}

Cause: The job execution has been cancelled.

Action: Check the cause for the exception. If the cause is not given, you can adjust logging level to fine and retry it.

Level: 1

Type: WARNING

Impact: Other

ESS-07006: Failed to cancel request {0}.

Cause: Failed to cancel request.

Action: Review the log file for underlying causes.

Level: 1

Type: WARNING

Impact: Other

ESS-07012: Invalid action ({0}) returned from pre-process callout for request {1}. Setting to {2} state.

Cause: Invalid action returned from pre-process callout for the request.

Action: Review the log for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-07013: Invalid action ({0}) returned from post-process callout for request {1}. Setting to {2} state.

Cause: Invalid action returned from pre-process callout for the request.

Action: Review the log for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-07014: Delaying processing of request {0} by {1} minutes.

Cause: The pre-process callback return value indicated that request processing should be delayed.

Action: No action required. The request will be retried after the delay.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-07015: Error occurred during cleanup of database job for request {0}.

Cause: An error occurred while performing post-execution clean tasks for an Oracle Scheduler job used to execute a SQL job request.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-07016: Failed processing update event for request {0}.

Cause: An error occurred processing an update event.

Action: Contact Oracle Support Services

Level: 1

Type: WARNING

Impact: Other

ESS-07017: Cannot process update event for request {0} in state {1}.

Cause: The request is in an illegal state for an update event.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-07018: Cannot process update event for request {0} in state {1}.

Cause: The request is in an illegal state for an update event.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-07019: Error processing request {0}. {1}

Cause: Error processing request.

Action: Review the log file for underlying causes.

Level: 1

Type: ERROR

Impact: Other

ESS-07020: Failed get an endpoint for application {0}.

Cause: Failed get an endpoint for application.

Action: No action is necessary.

Level: 1

Type: WARNING

Impact: Other

ESS-07021: Invalid work unit action for request {0}, work unit {1}, action {2}.

Cause: Invalid work unit action for request.

Action: Report the failure to Oracle support as it could be a bug in ESS.

Level: 1

Type: ERROR

Impact: Other

ESS-07022: Invalid endpoint action for request {0}, stage {1}, action {2}.

Cause: Invalid endpoint action for request.

Action: Report the failure to oracle support.

Level: 1

Type: ERROR

Impact: Other

ESS-07023: Error processing timed out requests. {0}.

Cause: An error occurred attempting to process a timed out request.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-07024: Rejecting update event for request {0}. {1}. Result status = {2}. Result message = {3}. Message body = {4}.

Cause: The request is in an illegal state for an update event.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-07025: Failed to allocate an asynchronous worker for request {0}. ({1}, {2}). ExecutionType = {3}.

Cause: Failed to allocate an asynchronous worker.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-07026: Failed to release an asynchronous worker for request {0}. ({1}, {2}). ExecutionType = {3}.

Cause: Failed to release an asynchronous worker.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-07027: Failed to terminate request {0}.

Cause: Failed to terminate request.

Action: Review the log file for underlying causes.n

Level: 1

Type: WARNING

Impact: Other

ESS-07028: Error invoking or executing application endpoint for request {0}. Check application status of logical application {1}.

Cause: An error occurred invoking a method on the endpoint of this application.

Action: Check that the application is deployed and running successfully.

Level: 1

Type: ERROR

Impact: Other

ESS-07029: Asynchronous throttle configuration does not exist for Workshift = {0}.

Cause: The async throttle configuration does not exist for the workshift.

Action: Contact Oracle Support Services

Level: 1

Type: ERROR

Impact: Other

ESS-07030: Recovering update work unit {0} for request {1} that may have been executing. There is a possibility of redelivery.

Cause: An update event is being recovered from a stage where redelivery is possible.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-07031: Error in transaction processing for request {0}. The transaction is eligible to be retried

Cause: A recoverable SQL error was encountered

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-07032: Work unit execution attempt, {0}, does not match request execution attempt, {1}, for request {2}.

Cause: The current work unit is for an older request execution attempt

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-07033: Job logic indicated a system error occurred while executing an asynchronous java job for request {0}. Job error is: {1}.

Cause: The job indicated that an error occurred

Action: Examine the innermost exception, if present, for the cause

Level: 1

Type: ERROR

Impact: Other

ESS-07034: Job logic indicated a business error occurred while executing an asynchronous java job for request {0}. Job error is: {1}.

Cause: The job indicated that a business error occurred

Action: Examine the innermost exception, if present, for the cause

Level: 1

Type: ERROR

Impact: Other

ESS-07035: Job logic indicated a warning occurred while executing an asynchronous java job for request {0}. Job warning is: {1}.

Cause: The job indicated that a warning occurred

Action: Examine the innermost exception, if present, for the cause

Level: 1

Type: WARNING

Impact: Other

ESS-07036: There was a system error while processing request {0} from which it cannot be recovered. Please check the server logs. (Process phase = {1}).

Cause: The request needed to be recovered because of a system error, but cannot be recovered safely

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-07037: Error performing substitutions for request {0}

Cause: An error occurred while performing substitution in a request parameter or other user input. This may be for process type job command line or environment variable.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-07038: Failed to initialize job context extensions for request {0} at stage {1}

Cause: An error occurred while initializing job context extensions.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-07039: Failed to cleanup job context for request {0} at stage {1}

Cause: An error occurred while cleaning job context extensions.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-07040: Failed to terminate job context for request {0}

Cause: An error occurred while terminating job context extensions.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-07041: Failed to retrieve alternate environment for application {0}

Cause: An error occurred while retrieving alternate application environment properties.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-07042: Expected class {0} not available for request mode {1}

Cause: An error instantiating an extensions class.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-07043: Failed to get platform request file directory for request {0}

Cause: An error occurred discovering the platform request file directory.

Action: Review the log file for attached exceptions to determine the nature of the problem.

Level: 1

Type: WARNING

Impact: Other

ESS-07050: Refreshing runtime incompatibilities for request {0}.

Cause: Refreshing runtime incompatibilities for the request.

Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-07200: Invalid workDirectory specified for spawned job request {0}: {1} does not exist.

Cause: Invalid workDirectory specified for spawned job request {0}: {1} does not exist.

Action: Ensure requestFileDirectory configured and a valid workDirectory specified for request.

Level: 1

Type: ERROR

Impact: Other

ESS-07201: Error launching spawnAgent for spawned job request {0}.

Cause: Error launching spawnAgent for spawned job request {0}.

Action: Review log file for nested IOexception and resolve the issue.

Level: 1

Type: ERROR

Impact: Other

ESS-07202: Error opening Output stream to spawnAgent for spawned job request {0}.

Cause: Error opening Output stream to spawnAgent for spawned job request {0}.

Action: Review log file for nested IOexception and resolve the issue.

Level: 1

Type: ERROR

Impact: Other

ESS-07203: spawnAgent terminated at launch for spawned job request {0}.

Cause: spawnAgent terminated at launch for spawned job request {0}.

Action: Enable Agent log to find cause and resolve.

Level: 1

Type: ERROR

Impact: Other

ESS-07204: spawnAgent cannot spawn process for spawned job request {0} with command line: {1}. Cause={2}

Cause: spawnAgent cannot spawn process for spawned job request {0} with cmdline: {1}. Cause={2}.

Action: Check error cause and update spawned job definition.

Level: 1

Type: ERROR

Impact: Other

ESS-07205: spawnAgent terminated before completion of spawned process for spawned job request {0} with command line: {1}.

Cause: spawnAgent terminated before completion of spawned process for spawned job request {0} with cmdline {1}.

Action: Enable Agent log to find cause and resolve.

Level: 1

Type: ERROR

Impact: Other

ESS-07206: Error waiting for completion of spawned job request {0} with command line: {1}.

Cause: Error waiting for completion of spawned job request {0} with cmdline: {1}.

Action: Review log file for nested IOexception and resolve the issue.

Level: 1

Type: ERROR

Impact: Other

ESS-07207: Invalid Exit Code returned by spawned process for spawned job request {0} with command line: {1}.

Cause: Invalid Exit Code returned by spawned process for spawned job request {0} with cmdline: {1}.

Action: Enable Agent log to find cause and resolve.

Level: 1

Type: ERROR

Impact: Other

ESS-07208: Error during post-completion cleanup for spawned job request {0} with command line: {1}.

Cause: Error during post-completion cleanup for spawned job request {0} with cmdline: {1}.

Action: Review log file for nested exception and resolve.

Level: 1

Type: ERROR

Impact: Other

ESS-07209: Error retrieving DomainConfigDirectory using JRF ServerPlatformSupportFactory API.

Cause: Error retrieving DomainConfigDirectory using JRF ServerPlatformSupportFactory API.

Action: Review log file for nested exception and resolve.

Level: 1

Type: ERROR

Impact: Other

ESS-07210: Error registering shutdown hook for spawned job request {0}.

Cause: Error registering shutdown hook for spawned job request {0}.

Action: Review log file for nested exception and resolve.

Level: 1

Type: ERROR

Impact: Other

ESS-07211: Error deregistering shutdown hook for spawned job request {0}.

Cause: Error deregistering shutdown hook for spawned job request {0}.

Action: Review log file for nested exception and resolve.

Level: 1

Type: WARNING

Impact: Other

ESS-07212: Error updating processId for spawned job request {0}.

Cause: Error updating processId for spawned job request {0}.

Action: Review log file for nested exception and resolve.

Level: 1

Type: WARNING

Impact: Other

ESS-07213: Using Perl SpawnAgent {1} with perl interpreter at {2} for spawned job request {0}.

Cause: Using Perl SpawnAgent {1} with perl interpreter at {2} for spawned job request {0}.

Action: None

Level: 1

Type: NOTIFICATION

Impact: Other

ESS-07214: Error locating Perl spawnAgent script for spawned job request {0}.

Cause: Error locating Perl SpawnAgent script for spawned job request {0}.

Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

ESS-07215: Error locating Perl interpreter for spawned job request {0}.

Cause: Error locating Perl interpreter for spawned job request {0}.

Action: Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

ESS-07217: Error retrieving SpawnAgent configuration.

Cause: Error retrieving SpawnAgent configuration.

Action: Review log file for nested exception. Contact Administrator.

Level: 1

Type: ERROR

Impact: Other

ESS-07218: Unable to locate Perl interpreter from FusionApps WebTier location.

Cause: Unable to locate Perl interpreter from FusionApps WebTier location.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-07500: Error parsing attribute {0}. {1}

Cause: An error is present in a command attribute format.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

ESS-07501: Error starting command worker. {0}

Cause: An error occurred starting a command worker.

Action: None

Level: 1

Type: WARNING

Impact: Other

ESS-07502: Failed to set request state to VALIDATION_FAILED for request {0}. {1}

Cause: An error occurred while setting the state of the request to VALIDATION_FAILED.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-07503: Document conversion failed for command work {0}. Command type: {1}, request: {2}.

Cause: Failed converting DOC Document for command work.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-07505: Validation of request {0} failed.

Cause: Validation of the request has failed.

Action: Check logs and error information for details.

Level: 1

Type: ERROR

Impact: Other

ESS-07506: Failed to check in command work {0} for {1} command, request {2}.

Cause: The work for the given command could not be checked in or deleted.

Action: The command work operation should be automatically retried, so no action is necessary.

Level: 1

Type: WARNING

Impact: Other

ESS-07507: Unknown command type, {0}, for command work {1}.

Cause: The command work has an unknown commad type.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-07508: Error calling endpoint for application {0} during processing of {1} command for request {2}.

Cause: The command work has an unknown commad type.

Action: None

Level: 1

Type: ERROR

Impact: Other

ESS-07509: Failed to execute command {0} for request {1} for command work {2}.

Cause: An error occurred executing the command.

Action: Review the log file for the cause.

Level: 1

Type: WARNING

Impact: Other

ESS-07510: Failed to update command {0} for request {1} for command work {2}.

Cause: An error occurred updating the command.

Action: Review the log file for the cause.

Level: 1

Type: WARNING

Impact: Other

ESS-07540: Failed to complete request {0} during group cleanup for execution group {1}, isolation group {2}.

Cause: Clean up of request failed during execution group removal.

Action: None. The action will be automatically retried.

Level: 1

Type: WARNING

Impact: Other

ESS-07541: Failed to get list of incomplete requests for execution group {0}, isolation group {1}.

Cause: Retrieving requests during execution group removal failed.

Action: None. The action will be automatically retried.

Level: 1

Type: WARNING

Impact: Other

ESS-07542: Failed to remove registrations for execution group {0}, isolationGroup{1}.

Cause: Removing instance or application registrations failed during execution group removal.

Action: None. The action will be automatically retried.

Level: 1

Type: WARNING

Impact: Other

ESS-07543: Failed to lock recovery delete table.

Cause: Failed to lock the recovery delete table.

Action: None. The action will be automatically retried.

Level: 1

Type: WARNING

Impact: Other

ESS-07544: Failed to insert row for process group {0}, isolationGroup {1}, action {2}.

Cause: Failed to insert the entry into recovery delete table.

Action: None. The action will be automatically retried.

Level: 1

Type: WARNING

Impact: Other

ESS-07545: Failed to delete row for process group {0}, isolationGroup {1}, action {2}.

Cause: Failed to delete the entry from recovery delete table.

Action: None. The action will be automatically retried.

Level: 1

Type: WARNING

Impact: Other

ESS-07546: Failed to query row for process group {0}, isolationGroup {1}, action {2}.

Cause: Failed to query for the entry from recovery delete table.

Action: None. The action will be automatically retried.

Level: 1

Type: WARNING

Impact: Other

ESS-07547: Failed to insert essconfig for process group {0}, isolationGroup {1}, appname {2}.

Cause: Failed to insert the entry from essconfig table.

Action: None.

Level: 1

Type: WARNING

Impact: Other

ESS-07548: Failed to delete essconfig for process group {0}, isolationGroup {1}, appname {2}.

Cause: Failed to delete the entry from essconfig table.

Action: None.

Level: 1

Type: WARNING

Impact: Other

ESS-07549: Failed to update essconfig customization for process group {0}, isolationGroup {1}, appname {2}.

Cause: Failed to update the entry from essconfig table.

Action: None.

Level: 1

Type: WARNING

Impact: Other

ESS-07550: Failed to query essconfig or customization for process group {0}, isolationGroup {1}, appname {2}.

Cause: Failed to query the entry from essconfig table.

Action: None.

Level: 1

Type: WARNING

Impact: Other

ESS-07551: Failed to find essconfig entry for process group {0}, isolationGroup {1}, appname {2}.

Cause: Could not find the entry from essconfig table.

Action: Please give correct processgroup and logical application name.

Level: 1

Type: WARNING

Impact: Other

ESS-08000: The value of filter is null.

Cause: The value of filter is null

Action: Provide the correct privilege name.

Level: 1

Type: ERROR

Impact: Other

ESS-08001: Invalid sec filter comparator.

Cause: Invalid sec filter comparator.

Action: Choose correct comparator, GRANTED.

Level: 1

Type: ERROR

Impact: Other

ESS-09000: Translation service with resource bundles {0} for Locale {1} can not be performed due to runtime error.

Cause: ESS runtime encountered a failure for the given translation request.

Action: Correct the bundle id, make sure it exists in the application environement.

Level: 1

Type: TRACE

Impact: Programmatic

ESS-09001: Message with requested key {0} is not found in the associated resource bundles.

Cause: Message with the requested key is not found in the resource bundle.

Action: Make sure the key is entered correctly.

Level: 1

Type: TRACE

Impact: Programmatic

ESS-09002: {0} is not a valid {1} implementation.

Cause: The implementation class is not of expected interface type.

Action: Make sure the implementation class implements the proper interface.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-09003: Failed to instantiate the translation service factory implementation {0}.

Cause: Error while instantiating an instance of translation service factory.

Action: Check the log to find exception details.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-09004: Failed to retrieve a valid instance of underlying oracle.javatools ResourceBundleManager. Design time metadata translation is not supported.

Cause: Error while instantiating an instance of oracle.javatools.resourcebundle.ResourceBundleManager.

Action: None

Level: 1

Type: ERROR

Impact: Programmatic

ESS-09005: Encountered MDS exception while performing MDS operations.

Cause: Encountered MDS exception.

Action: Check the exception for details.

Level: 1

Type: TRACE

Impact: Programmatic

ESS-09400: Encountered an execution context exception.

Cause: Encountered exception while invoking DMS execution context API(s).

Action: Check exception stack trace for details.

Level: 1

Type: WARNING

Impact: Programmatic

ESS-09402: Failed to compile recurrence expression.

Cause: Failed to compile recurrence expression

Action: Correct the invalid recurrence expression.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-09403: Schedule list limit must be a non-negative integer.

Cause: Schedule List limit is invalid.

Action: List limit must be a non-negative integer.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-09404: Schedule list begin date cannot be null.

Cause: Invalid Null Schedule Begin date.

Action: Provide a non-null begin date for the schedule.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-09405: Schedule begin date can not be after end date.

Cause: Begin Date for the schedule is after the end date.

Action: Correct the invalid begin date or end date.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-09406: Parsing exception. Only one day type recurrence field may be specified.

Cause: More than one of BYDAY, BYMONTHDAY, BYYEARDAY was specified

Action: Correct the invalid recurrence.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-09407: Parsing exception. An occurrence by week number can only be used with a yearly frequency.

Cause: A BYWEEKNO clause was specified with a frequency other than YEARLY

Action: Correct the invalid recurrence.

Level: 1

Type: ERROR

Impact: Programmatic

ESS-09408: Parsing exception. An occurrence by week number cannot be used with an occurrence by month.

Cause: More than one of BYWEEKNO, BYMONTH was specified

Action: Correct the invalid recurrence.

Level: 1

Type: ERROR

Impact: Programmatic