ESS-00001 to ESS-09422

9 ESS-00001 to ESS-09422

ESS-00001: Internal error. {0}
Category:: Other
Cause:: Internal error occurred.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-00002: Constraint error for property {0} with value {1}.
Category:: Other
Cause:: An attempt was made to create an object that already exists. An attempt was made to change the value of an object thatis read-only.
Action:: Specifiy an identifier for the object that is not currently in use. Retry the operation without changing the value of the object.

ESS-00003: Failed to find resource {0}. {1}
Category:: Other
Cause:: A JNDI lookup of the given resource failed.
Action:: Ensure the resource is deployed properly and is available via jndi lookup.

ESS-00004: Incorrect timestamp format: {0}. {1}
Category:: Programmatic
Cause:: An invalid value was specified for a timestamp.
Action:: Specify a correct value for the parameter.

ESS-00005: SQL bind operation not supported for parameter data type: {0}
Category:: Programmatic
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.

ESS-00006: Enterprise Scheduler configuration is not initialized.
Category:: Programmatic
Cause:: An operation attempted to access Enterprise Scheduler configuration information before the configuration was initialized.
Action:: Re-try the operation at a later time.

ESS-00007: Operation intended for group, {0}. Configured group is {1}.
Category:: Other
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.

ESS-00100: Install plan is not present for application {0}.
Category:: Installation
Cause:: The install plan is not present for the application being deployed.
Action:: Contact Oracle Support Services.

ESS-00101: Global data source, {0}, could not be created.
Category:: Installation
Cause:: The global data source could not be created.
Action:: Check the underlying cause for details.

ESS-00102: Dependent component, {0}, has not been deployed.
Category:: Installation
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.

ESS-00103: Error finding application {0}.
Category:: Installation
Cause:: An error occurred while attempting to find the specified application.
Action:: Perform the action specified in the chained exception.

ESS-00104: Cannot find object {0} for archive {1}.
Category:: Other
Cause:: The attempt to access the specified object failed.
Action:: None

ESS-00120: Invalid value for dispatcher poll interval.
Category:: Other
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.

ESS-00121: Dispatcher poll interval minimum value cannot exceed maximum value.
Category:: Other
Cause:: Attempted to configure a value for the dispatcher minimum poll interval that is greater than the maximum value. 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 less than or equal to the maximum value. Retry the operation with a value that is equal to or greater than the minimum value.

ESS-00122: Invalid value for processor threads.
Category:: Other
Cause:: Attempted to configure an invalid value for the processor maximum threads.
Action:: Retry the operation with a non-negative numeric value.

ESS-00123: Invalid value for processor starvation threshold.
Category:: Other
Cause:: Attempted to configure an invalid value for the processor starvation threshold.
Action:: Retry the operation with a non-negative numeric value.

ESS-00124: Unable to validate metadata for work assignment {0}.
Category:: Other
Cause:: Attempted to add or remove bindings for an work assignment.
Action:: Retry the operation with a valid work assignment name.

ESS-00500: Failed to create metadata service handle.
Category:: Other
Cause:: An error occurred while starting a Metadata session.
Action:: See the base exception for details.

ESS-00501: Failed to close metadata service handle.
Category:: Other
Cause:: An error occurred while closing a Metadata session.
Action:: See the base exception for details.

ESS-00502: The metadata object type must be specified
Category:: Other
Cause:: The metadata type was not specified when creating the metadata object
Action:: Specify a valid value for the metadata object type

ESS-00503: MetadataServiceHandle is null.
Category:: Programmatic
Cause:: The ESS metadata service handle is null.
Action:: Specify a valid ESS metadata service handle.

ESS-00800: Error attempting notification for SQL job request {0}.
Category:: Other
Cause:: Failed to create notification that SQL job executable completed.
Action:: Review the log file to determine the nature of the problem.

ESS-01000: Failed to open runtime service. {0}
Category:: Programmatic
Cause:: An error occurred opening the RuntimeService handle
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01001: Failed to close runtime service handle. {0}
Category:: Programmatic
Cause:: An error occurred closing the RuntimeService handle
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01002: Illegal attempt to validate request, {0}, when current state, {1}, is not PENDING_VALIDATION.
Category:: Other
Cause:: A request is in an illegal state for validation.
Action:: None

ESS-01003: Illegal operation for an unvalidated request {0}.
Category:: Programmatic
Cause:: The operation is not supported for an unvalidated request.
Action:: Do not attempt this operation unless the request is validated.

ESS-01004: Illegal attempt to set state of request, {0}, to VALIDATION_FAILED when current state, {1}, is not PENDING_VALIDATION.
Category:: Other
Cause:: An internal error occurred.
Action:: None

ESS-01005: Parameter {0} does not exist for request {1}.
Category:: Programmatic
Cause:: The given parameter name does not exist for this request.
Action:: Specify an existing parameter.

ESS-01006: RuntimeServiceHandle is marked for rollback only.
Category:: Programmatic
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.

ESS-01007: RuntimeServiceHandle is null.
Category:: Programmatic
Cause:: The ESS runtime service handle is null.
Action:: Specify a valid ESS runtime service handle.

ESS-01008: Value for parameter, {0}, has an invalid data type: {1}.
Category:: Programmatic
Cause:: The value for a parameter has an unsupported data type.
Action:: Specify a value which has a supported data type for the parameter.

ESS-01009: Value for parameter, {0}, is not valid.
Category:: Programmatic
Cause:: The value for a parameter is not valid.
Action:: Specify a valid value for the parameter.

ESS-01010: Value for parameter, {0}, must not be null.
Category:: Programmatic
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.

ESS-01011: Parameter, {0}, is required but was not specified.
Category:: Programmatic
Cause:: The given parameter is required but was not specified.
Action:: Specify the required parameter.

ESS-01012: Request {0} not found.
Category:: Programmatic
Cause:: A request that was the target of a RuntimeService operation was not found in the runtime store.
Action:: Specify a valid request identifier.

ESS-01013: Failed to lock request {0}. Request not found.
Category:: Programmatic
Cause:: Attemped to lock a request that was not found in the runtime store.
Action:: Specify a valid request identifier.

ESS-01014: Error occurred attempting to lock request {0}.
Category:: Other
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.

ESS-01015: Failed to generate a request identifier.
Category:: Other
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.

ESS-01016: Failed to generate a request handle.
Category:: Other
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.

ESS-01017: Error attempting to access information for request {0}.
Category:: Other
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.

ESS-01018: Error attempting to update information for request {0}.
Category:: Other
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.

ESS-01019: Request {0} is not in {1} state. Current state is {2}.
Category:: Programmatic
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.

ESS-01021: Failed to create DMS context for new request.
Category:: Programmatic
Cause:: Failed to create a DMS context for a new request.
Action:: Review any linked exceptions to identify the root cause of the error.

ESS-01022: Error occurred retrieving summary data. {0}
Category:: Other
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.

ESS-01023: Parameter {0} for request {1} is read-only.
Category:: Programmatic
Cause:: Attempted to modify the value for a request parameter that is read-only.
Action:: None

ESS-01024: This operation is illegal for this request. {0}
Category:: Programmatic
Cause:: The invoked operation is not legal for this request.
Action:: None

ESS-01025: The request does not have a schedule. {0}
Category:: Programmatic
Cause:: This operation can only be applied to a request with a schedule.
Action:: None

ESS-01026: Schedule for request {0} cannot be changed when in state {1}
Category:: Programmatic
Cause:: The schedule for this request cannot be replaced in the current state.
Action:: None

ESS-01027: Failed to convert schedule to string
Category:: Programmatic
Cause:: The schedule cannot be converted to a string.
Action:: None

ESS-01028: Request submission or validation failed. {0}
Category:: Programmatic
Cause:: An error occurred during request submission or validation.
Action:: None

ESS-01029: Failed to create child request for parent request {0}.
Category:: Programmatic
Cause:: An error occurred while attempting to create a child request for a parent that was submitted with a Schedule or Trigger.
Action:: None

ESS-01030: Failed to create JobSet step request for parent request {0}, step {1}.
Category:: Programmatic
Cause:: An error occurred while attempting to create a request for a JobSet step.
Action:: None

ESS-01031: Application {0} was not found.
Category:: Programmatic
Cause:: Attempted to submit a request for an application associated with a logical name but no such application was found.
Action:: Deploy the application

ESS-01032: Application {0} was found in more than one process group.
Category:: Programmatic
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.

ESS-01033: Application {0} was not found for process group {1}.
Category:: Programmatic
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.

ESS-01034: Unable to determine the deployed application name for logical application {0}.
Category:: Programmatic
Cause:: Unable to determine the name of the deployed application for the specified logical name.
Action:: Check for deployment errors.

ESS-01035: Unable to determine a logical application name for new request.
Category:: Programmatic
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.

ESS-01036: Unable to determine a process group for new request.
Category:: Programmatic
Cause:: Unable to determine the process group that should be used for a submitted request.
Action:: None

ESS-01037: Job definition is required for a non-Adhoc request submission.
Category:: Programmatic
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.

ESS-01038: Read-Only violation for request parameter {0}.
Category:: Programmatic
Cause:: The given parameter is marked as read-only and was specified as a request parameter.
Action:: Retry the operation without the parameter.

ESS-01039: Parameter, {0}, is not allowed in request submission parameters.
Category:: Programmatic
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.

ESS-01040: Invalid parameter {0}. Scoped parameters are only supported for JobSet.
Category:: Programmatic
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.

ESS-01041: Parameter, {0}, is not allowed as a scoped request parameter for JobSet step {1}.
Category:: Programmatic
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.

ESS-01042: Metadata type, {0}, is not supported for a sub-request.Only JobDefinition is supported.
Category:: Programmatic
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.

ESS-01043: Failed to get XML for an adhoc Schedule.
Category:: Programmatic
Cause:: Error occurred creating XML representation of an adhoc Schedule.
Action:: Fix the adhoc Schedule and retry the operation.

ESS-01046: Start time must be before the end time.
Category:: Programmatic
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.

ESS-01047: End time must be after the current time.
Category:: Programmatic
Cause:: Attempted to submit a request where the end time is before the current time.
Action:: Retry the operation with value end time.

ESS-01048: Schedule has expired and no executions are possible.
Category:: Programmatic
Cause:: Attempted to submit a request with a Schedule that has expired.
Action:: Retry the operation with a different Schedule.

ESS-01049: No executions are possible before the given end date.
Category:: Programmatic
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.

ESS-01050: One or more requests are currently pending for definition: {0}
Category:: Programmatic
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

ESS-01051: Incompatible with parent request {0} due to Incompatibility definition: {1}
Category:: Programmatic
Cause:: Attempted to submit a sub-request that is incompatible with its parent request due to an Incompatibility definition
Action:: None

ESS-01052: Request handle is not valid for the current execution context of parent request {0}.
Category:: Programmatic
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

ESS-01053: Cannot cancel request {0}. Current state is {1}.
Category:: Programmatic
Cause:: Attempted to cancel a request whose current state does not allow the operation to be performed.
Action:: None

ESS-01054: Cannot hold request {0}. Current state is {1}.
Category:: Programmatic
Cause:: Attempted to hold a request whose current state does not allow the operation to be performed.
Action:: None

ESS-01055: Cannot release request {0}. Current state is {1}.
Category:: Programmatic
Cause:: Attempted to release a request whose current state does not allow the operation to be performed.
Action:: None

ESS-01056: Cannot delete request {0}. Current state is {1}, process phase is {2}.
Category:: Programmatic
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.

ESS-01057: Cannot purge request {0}. Current state is {1}, process phase is {2}.
Category:: Programmatic
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.

ESS-01058: Cannot change priority for request {0}. Current state is {1}.
Category:: Programmatic
Cause:: Attempted to change the priority for a request whose current state does not allow the operation to be performed.
Action:: None

ESS-01059: Delete failed for request {0}. This operation is not supported for a sub-request or JobSet step.
Category:: Programmatic
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

ESS-01060: Purge failed for request {0}. This operation not supported for a sub-request or JobSet step.
Category:: Programmatic
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

ESS-01061: Failed to purge request {0}.
Category:: Programmatic
Cause:: An error occurred attempting to purge a request.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01062: Invalid priority value. Valid range is {0} to {1}.
Category:: Programmatic
Cause:: An invalid value for request priority is specified.
Action:: Specify a value in the indicated range.

ESS-01063: Failed to retrieve Schedule for request {0}.
Category:: Programmatic
Cause:: Failed to retrieve the Schedule associated with the given request.
Action:: None

ESS-01065: Cannot recover request {0} with incomplete child requests.
Category:: Programmatic
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.

ESS-01066: Request state {0} not allowed for manual recovery. State should be canceling or terminal. {1}
Category:: Programmatic
Cause:: An attempt was made to manually recover a request that was in an illegal state.
Action:: Cancel the request.

ESS-01067: Error occurred mapping Filter to CompositeData.
Category:: Programmatic
Cause:: Error occurred mapping Filter to CompositeData.
Action:: Correct the invalid CompositeData instance.

ESS-01068: Unexpected type, {0}, for Filter value {1}.
Category:: Programmatic
Cause:: Unexpected Filter type for Filter value.
Action:: Correct the invalid Filter type.

ESS-01069: Invalid Null input for a Filter {0}.
Category:: Programmatic
Cause:: Unexpected null input for a filter.
Action:: Provider a non null value.

ESS-01070: Cannot change start time or end time for request of type {0}
Category:: Programmatic
Cause:: The start and end times cannot be updated for a request this type.
Action:: None

ESS-01071: Schedule for request {0} cannot be for a retry attempt
Category:: Programmatic
Cause:: The schedule for this request cannot be replaced during a retry.
Action:: None

ESS-01072: Metadata schedule and adhoc schedule were specified. Only one schedule can be used.
Category:: Programmatic
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

ESS-01073: Failed to open runtime service: {0}. {1}
Category:: Programmatic
Cause:: An error occurred opening the RuntimeService handle
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01074: Failed to open runtime service due to resource error. {0}
Category:: Programmatic
Cause:: A resource error occurred opening the RuntimeService handle.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01075: Cannot delete execution group, {0}, because active instances exist.
Category:: Programmatic
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.

ESS-01076: Execution group {0} is already being deleted.
Category:: Programmatic
Cause:: The execution group is already being deleted.
Action:: Wait for first deletion to complete.

ESS-01077: Failed to get async request information for message {0}.
Category:: Other
Cause:: Failed to retrieve information for web service asynchronous callback.
Action:: Check the logs.

ESS-01078: Request {0} is required to be asynchronous for this operation.
Category:: Other
Cause:: This operation cannot be executed on a synchronous request.
Action:: Do not invoke the operation on this request.

ESS-01079: Error attempting to access request information.
Category:: Other
Cause:: An error occurred attempting to access request information.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01080: Failed to persist request information.
Category:: Other
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.

ESS-01081: Failed to persist request parameter {0}, scope {1}.
Category:: Other
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.

ESS-01082: Failed to persist read-only constraint for parameter {0}.
Category:: Other
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.

ESS-01083: Error attempting to retrieve parameters for request {0}.
Category:: Other
Cause:: An error occurred attempting to retrieve request parameters.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01084: Error attempting to update parameter, {0}, for request {1}.
Category:: Other
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.

ESS-01085: Failed to add parameter {0}, scope {1}, for request {2}.
Category:: Other
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.

ESS-01086: Operation not supported for scoped parameter, {0}.
Category:: Programmatic
Cause:: A scoped parameter was specified for an operation that is not supported for scoped parameter.
Action:: None

ESS-01087: Failed to convert Document to byte sequence.
Category:: Other
Cause:: An error occurred converting a Document to byte sequence.
Action:: None

ESS-01088: Failed to convert byte sequence to Document.
Category:: Other
Cause:: An error occurred converting a byte sequence to a Document.
Action:: None

ESS-01089: Failed to get storable value for parameter, {0}.
Category:: Other
Cause:: An error occurred converting a parameter value to its stored representation.
Action:: None

ESS-01090: Failed to get typed value for parameter, {0}, data type, {1}.
Category:: Other
Cause:: An error occurred converting a parameter value from its stored representation to a typed value.
Action:: None

ESS-01091: Unable to obtain incompatibility value for property, {0}.
Category:: Programmatic
Cause:: Unable to materialize an incompatibility value for the specified property.
Action:: Review the causeBy exception chain to determine the specific failure.

ESS-01092: Incompatibility conflict detected between request {0} and parent request {1} for incompatibility {2}.
Category:: Other
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

ESS-01093: Number of acquired request incompatibilities ({0}) does not match number of incompatibility locks ({1}) for request {2}.
Category:: Other
Cause:: Runtime service system failure.
Action:: Review the log file for underlying causes.

ESS-01094: Error attempting to process getCompletionStatus call since another getCompletionStatus call with message id {0} is pending for reply.
Category:: Other
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.

ESS-01095: Unable to find ess hosting app with logical application name {0}.
Category:: Programmatic
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.

ESS-01096: Query result handle is null.
Category:: Programmatic
Cause:: The value of the query result handle argument is null.
Action:: Specify an argument value that is not null.

ESS-01097: Request, {0}, is not of expected type, {1}.
Category:: Programmatic
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.

ESS-01098: No request is found for id {0} {1}
Category:: Programmatic
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.

ESS-01099: An error occurred invoking the RuntimeService MBean. {0}
Category:: Programmatic
Cause:: An error occurred invoking the RuntimeService MBean.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01100: Error retrieving details about Oracle Scheduler job {0} for request {1}.
Category:: Programmatic
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.

ESS-01101: Error retrieving the OUTPUT_LIST for parallel children of request {0}.
Category:: Programmatic
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.

ESS-01102: Failed to register application, {0}, with instance {1}. {2}
Category:: Other
Cause:: Application registration failed with ESS.
Action:: Contact Oracle Support Services.

ESS-01103: Failed to unregister all applications for instance {0}. {1}
Category:: Other
Cause:: Application deregistration failed with ESS.
Action:: Contact Oracle Support Services.

ESS-01104: Failed to unregister application, {0}, for instance {1}. {2}
Category:: Other
Cause:: Application deregistration failed with ESS.
Action:: Contact Oracle Support Services.

ESS-01105: Failed to check in instance {0}. {1}
Category:: Other
Cause:: Registration update of ESS instance failed.
Action:: Check that database is running and data source is correct.

ESS-01106: Failed to clear checkin entry for instance {0}. {1}
Category:: Other
Cause:: Unregistration of ESS instance failed.
Action:: Check that database is running and data source is correct.

ESS-01107: Failed to remove timed out instance registrations. {0}
Category:: Other
Cause:: Unregistration of ESS timed-out instances failed.
Action:: Check that database is running and data source is correct.

ESS-01108: Failed to fetch elements from wait queue. {0}.
Category:: Other
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.

ESS-01109: Failed to access wait queue element for request {0}. {1}
Category:: Other
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.

ESS-01110: Failed to lock wait queue element for request {0}. {1}
Category:: Other
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.

ESS-01111: Failed to insert wait queue element for request {0}. {1}
Category:: Other
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.

ESS-01112: Failed to delete wait queue element for request {0}. {1}
Category:: Other
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.

ESS-01113: Failed to hold wait queue element for request {0}. {1}
Category:: Other
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.

ESS-01114: Failed to release wait queue element for request {0}. {1}
Category:: Other
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.

ESS-01115: Failed to undefer wait queue element for request {0}. {1}
Category:: Other
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.

ESS-01116: Query field name, {0}, is not a valid name.
Category:: Programmatic
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.

ESS-01117: Value for query field, {0}, has an unsupported data type: {1}
Category:: Programmatic
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.

ESS-01118: Query field, {0}, has a null value which is not supported for the {1} operator.
Category:: Programmatic
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.

ESS-01119: Query field, {0}, has a value with a data type, {1}, that is not supported for the {2} comparator.
Category:: Programmatic
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.

ESS-01120: Query field, {0}, does not support the {1} comparator.
Category:: Programmatic
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.

ESS-01121: Failed to retrieve field {0}.
Category:: Programmatic
Cause:: A failure occurred while retrieving the specified field.
Action:: Check that database is running and data source is correct.

ESS-01122: Error attempting to access information for incompatibility {0} for request {1}.
Category:: Programmatic
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.

ESS-01123: Error attempting to update information for incompatibility {0} for request {1}.
Category:: Programmatic
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.

ESS-01124: Error attempting to add information for incompatibility {0} for request {1}.
Category:: Programmatic
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.

ESS-01125: Size of request parameter {0} used for incompatibility {1} is too large.
Category:: Programmatic
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.

ESS-01126: Application {0} is active in more than one group.
Category:: Programmatic
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.

ESS-01127: Application {0} is not active in any ESS instance.
Category:: Programmatic
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.

ESS-01128: Application with deployed name {0} exists with multiple logical names.
Category:: Programmatic
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.

ESS-01129: Application with logical name {0} was not found.
Category:: Programmatic
Cause:: The application is not a member of this ESS group.
Action:: Ensure the application is deployed and running in the correct ESS group.

ESS-01130: Application with logical name {0} exists with multiple deployed names.
Category:: Programmatic
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.

ESS-01131: Application with deployed name {0} was not found.
Category:: Programmatic
Cause:: The application is not a member of this ESS group.
Action:: Ensure the application is deployed and running in the correct ESS group.

ESS-01132: Unable to access processor bindings. {0}
Category:: Other
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.

ESS-01133: Processor binding {0} could not be found.
Category:: Other
Cause:: Processor binding could not be found.
Action:: Check that you specified the correct binding name.

ESS-01134: Processor binding {0} already exists.
Category:: Other
Cause:: Processor binding already exists.
Action:: Change the name of the binding.

ESS-01135: Unable to notify server of processor bindings change. {0}
Category:: Other
Cause:: Unable to notify server of bindings change.
Action:: Check that database is running and data source is correct.

ESS-01136: Unable to access processor bindings change notification. {0}
Category:: Other
Cause:: Unable to access bindings change notification.
Action:: Check that database is running and data source is correct.

ESS-01137: Unable to notify server to refresh selector. {0}
Category:: Other
Cause:: Unable to notify server to refresh selector.
Action:: Check that database is running and data source is correct.

ESS-01138: Unable to access refresh selector notification. {0}
Category:: Other
Cause:: Unable to access refresh selector notification.
Action:: Check that database is running and data source is correct.

ESS-01139: Value, {1}, for query field, {0}, is invalid.
Category:: Programmatic
Cause:: A query filter was specified in which the value for a query field was invalid.
Action:: Specify a valid query value.

ESS-01140: Error accessing async throttle information for ({0}, {1}). {2}
Category:: Other
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.

ESS-01141: Async throttle already exists for Workshift = {0}. {1}
Category:: Other
Cause:: The throttle is already configured for the Workshift.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01142: Async throttle not found for Workshift = {0}.
Category:: Other
Cause:: The throttle was not found for the Workshift.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01143: Failed to process filter {0}.
Category:: Programmatic
Cause:: Filter evaluation failed.
Action:: Correct the invalid Filter.

ESS-01144: Failed to retrieve timed out instance registrations. {0}
Category:: Other
Cause:: Query of ESS timed out registrationsinstance failed.
Action:: Check that database is running and data source is correct.

ESS-01145: Failed to lock instance {0}. {1}
Category:: Other
Cause:: Locking the ESS instance registration failed.
Action:: Check that database is running and data source is correct.

ESS-01146: Error accessing runtime async throttle information. {0}
Category:: Other
Cause:: An error occurred while accessing the throttle configuration.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01147: Failed to get DiagnosticState for instance {0}. {1}
Category:: Other
Cause:: Failed to get DiagnosticState for the instance.
Action:: None

ESS-01148: Failed to clear registrations for execution group {0}, isolation group {1}. {2}
Category:: Other
Cause:: Failed to clear registrations for execution group.
Action:: None. Registrations will be automatically retried

ESS-01149: Error accessing unthrottled work assignments ({0}). {1}
Category:: Other
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.

ESS-01150: Unable to delete workshift with outstanding async workers: {0}
Category:: Other
Cause:: A workshift that has outstanding async workers not be deleted.
Action:: Wait until all async workers have completed and then delete the workshift.

ESS-01151: Error accessing async limit information for workshift = {0}. {1}
Category:: Other
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.

ESS-01152: Error accessing async allocation information for work assignment = {0}. {2}
Category:: Other
Cause:: An error occurred accessing runtime async allocation information.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01153: Failed to add incompatibility lock {0}.
Category:: Programmatic
Cause:: An error occurred attempting to add incompatibility lock information.
Action:: Review the causeBy exception chain to determine the specific failure.

ESS-01154: Failed to delete incompatibility lock {0}.
Category:: Programmatic
Cause:: An error occurred attempting to delete incompatibility lock information.
Action:: Review the causeBy exception chain to determine the specific failure.

ESS-01155: Failed to lock incompatibility lock {0}.
Category:: Programmatic
Cause:: An error occurred attempting to delete incompatibility lock information.
Action:: Review the causeBy exception chain to determine the specific failure.

ESS-01156: Failed to update reference count for incompatibility lock {0}.
Category:: Programmatic
Cause:: An error occurred attempting to delete incompatibility lock information.
Action:: Review the causeBy exception chain to determine the specific failure.

ESS-01157: Failed to retrieve incompatibility locks for request {0}.
Category:: Programmatic
Cause:: An error occurred attempting to retrieve incompatibility locks held by a request.
Action:: Review the causeBy exception chain to determine the specific failure.

ESS-01158: Failed to lock incompatibility locks for request {0}.
Category:: Programmatic
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.

ESS-01159: Failed to retrieve request incompatibility for request {0}.
Category:: Programmatic
Cause:: An error occurred attempting to retrieve request incompatibility information.
Action:: Review the causeBy exception chain to determine the specific failure.

ESS-01160: Failed to lock request incompatibility for request {0}.
Category:: Programmatic
Cause:: An error occurred attempting to lock request incompatibility information.
Action:: Review the causeBy exception chain to determine the specific failure.

ESS-01161: Failed to retrieve request incompatibility.
Category:: Programmatic
Cause:: An error occurred attempting to retrieve request incompatibility information.
Action:: Review the causeBy exception chain to determine the specific failure.

ESS-01162: Failed to lock request incompatibility.
Category:: Programmatic
Cause:: An error occurred attempting to lock request incompatibility information.
Action:: Review the causeBy exception chain to determine the specific failure.

ESS-01163: Failed to add reference for incompatibility {0}, job definition {1}, request {2}.
Category:: Programmatic
Cause:: An error occurred attempting to add job incompatibility reference.
Action:: Review the causeBy exception chain to determine the specific failure.

ESS-01164: Reference already exists for incompatibility {0}, job definition {1}, request {2}.
Category:: Programmatic
Cause:: Job incompatibility reference already exists.
Action:: None

ESS-01165: Failed to retrieve incompatibility metadata from runtime store for job definition {0}, request {1}.
Category:: Programmatic
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.

ESS-01166: Query for application registration information failed.
Category:: Other
Cause:: An error occurred while querying the application registration table.
Action:: Contact Oracle Support Services

ESS-01167: Failed to cache metadata in runtime store for request {0}, metadata {1}.
Category:: Other
Cause:: An error occurred while saving metadata in the ESS runtime store.
Action:: Review the log file to determine the nature of the problem.

ESS-01168: Binding mode conflict for {0}
Category:: Other
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.

ESS-01169: Workshift does not exist {0}
Category:: Other
Cause:: The workshift does not exist.
Action:: Ensure you are using the correct workshift name, and that the workshift exists.

ESS-01170: Failed to retrieve runtime store information.
Category:: Other
Cause:: An error occurred attempting to retrieve runtime store information.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01171: Runtime store compatibility information is not available.
Category:: Other
Cause:: Unable to retrieve Enterprise Scheduler Service runtime store compatibility information.
Action:: Contact Oracle Support Services.

ESS-01172: Runtime store compatibility check failed; mid-tier check version: {0}, runtime store version: {1}, schema name: {2}
Category:: Other
Cause:: The Enterprise Scheduler Service mid-tier is not compatible with the database runtime store.
Action:: Upgrade database schema or mid-tier to be compatible

ESS-01173: Runtime store status check failed; runtime store status: {0}, schema name: {1}
Category:: Other
Cause:: The Enterprise Scheduler Service runtime store is not valid.
Action:: Contact Oracle Support Services.

ESS-01174: Runtime store compatibility check failed; mid-tier check version: {0}, runtime store version: {1}, schema name: {2}. Check disabled, allowing operation to continue.
Category:: Other
Cause:: The Enterprise Scheduler Service mid-tier is not compatible with the database runtime store.
Action:: Upgrade database schema or mid-tier to be compatible.

ESS-01175: Runtime store status check failed; runtime store status: {0}, schema name: {1}. Check disabled, allowing operation to continue.
Category:: Other
Cause:: The Enterprise Scheduler Service runtime store is not valid.
Action:: Contact Oracle Support Services.

ESS-01176: Triggers are not supported.
Category:: Programmatic
Cause:: A trigger was specified to the metadata service or when submitting a request.
Action:: Do not create triggers and specify a null value for any trigger parameter.

ESS-01177: Failed to delete job incompatibility references for request {0} from runtime store.
Category:: Programmatic
Cause:: An error occurred attempting to remove job incompatibility references.
Action:: Review the causeBy exception chain to determine the specific failure.

ESS-01178: Query for server coordination information failed.
Category:: Other
Cause:: An error occurred while querying the server coordination table.
Action:: Check that database is running and data source is correct.

ESS-01179: Schedule includes explicit times that are before the start time.
Category:: Programmatic
Cause:: Attempted to submit a reuqest with Adhoc schedule that contains time that are before the current time.
Action:: Retry the operation after modifying the times in Adhoc Schedule.

ESS-01180: Unable to determine database type.
Category:: Other
Cause:: Unable to determine the database type being used for the runtime store.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01181: Failed to delete information for request {0}.
Category:: Other
Cause:: An error occurred attempting to remove request information from the runtime store.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01182: Failed to update wait queue element for request {0}.
Category:: Other
Cause:: An error occurred attempting to update the wait queue element for a request.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01183: Wait queue operation failed.
Category:: Other
Cause:: An error occurred attempting a wait queue operation.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01184: Update of server coordination information failed.
Category:: Other
Cause:: An error occurred attempting to update the server coordination table.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01185: Failed to get async request information for request {0}.
Category:: Other
Cause:: Failed to retrieve information for web service asynchronous callback.
Action:: Check the logs.

ESS-01186: Failed to update async request information for message {0}.
Category:: Other
Cause:: Failed to update information for web service asynchronous callback.
Action:: Check the logs.

ESS-01187: Failed to add or modify attribute {0} of namespace {1} for request {2}.
Category:: Other
Cause:: An error occurred attempting to modify request attribute information.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01188: Failed to access attribute {0} of namespace {1} for request {2}.
Category:: Other
Cause:: An error occurred attempting to access request attribute information.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01189: Failed to delete attribute {0} of namespace {1} for request {2}.
Category:: Other
Cause:: An error occurred attempting to remove request attribute information.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01190: Value for attribute {0} of namespace {1} has an invalid data type: {2}.
Category:: Other
Cause:: The value for a request attribute has an unsupported data type.
Action:: Specify a value which has a supported data type for the attribute.

ESS-01191: Failed to get storable value for attribute {0} of namespace {1}.
Category:: Other
Cause:: An error occurred converting a request attribute value to its stored representation.
Action:: None

ESS-01192: Failed to get typed value for attribute {0} of namespace {1} for data type {2}.
Category:: Other
Cause:: An error occurred converting a request attribute value from its stored representation to a typed value.
Action:: None

ESS-01193: Value for attribute {0} of namespace {1} has data type {2} instead of the expected data type {3}
Category:: Other
Cause:: Data type for request attribute value does not match the type already estabished for that attribute.
Action:: None

ESS-01194: An unknown or unsupported request detail type was specified: {0}.
Category:: Other
Cause:: An unknown or unsupported request detail type was specified.
Action:: Provide a valid request detail type.

ESS-01195: Error attempting to access parameter, {0}, for request {1}.
Category:: Other
Cause:: An error occurred attempting to access request parameter information.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01196: Unable to get the current time from the database.
Category:: Programmatic
Cause:: Unable to get the current time from the database.
Action:: Review the log file for possible underlying causes.

ESS-01197: Unable to release incompatibility locks for request {0}.
Category:: Programmatic
Cause:: Unable to release one or more incompatibility locks for the request at this time.
Action:: Review the log file for possible underlying causes.

ESS-01198: Unable to obtain configuration information for application {0}.
Category:: Programmatic
Cause:: Unable to retrieve configuration information for application.
Action:: None

ESS-01199: JobSet steps would have mixed request modes: {0}
Category:: Programmatic
Cause:: The steps for a JobSet are not homogeneous in regard to the resolved request mode.
Action:: None

ESS-01200: Error attempting to insert {0} work unit for request {1}.
Category:: Other
Cause:: An error occurred inserting a work unit into the persistent store.
Action:: Review the log file to determine the nature of the problem.

ESS-01201: Error attempting to insert {0} work unit.
Category:: Other
Cause:: An error occurred inserting a work unit into the persistent store.
Action:: Review the log file to determine the nature of the problem.

ESS-01202: Failed to update work stage for work {0}.
Category:: Other
Cause:: An error occurred updating the work stage of a work unit.
Action:: Review the log file to determine the nature of the problem.

ESS-01203: Failed to delete work for request {0}.
Category:: Other
Cause:: An error occurred deleting work units.
Action:: Review the log file to determine the nature of the problem.

ESS-01204: Failed to delete work {0} for request {1}.
Category:: Other
Cause:: An error occurred deleting work units.
Action:: Review the log file to determine the nature of the problem.

ESS-01205: Failed to delete work unit {0}.
Category:: Other
Cause:: An error occurred deleting work units.
Action:: Review the log file to determine the nature of the problem.

ESS-01206: Failed to check in work unit {0} for request {1}.
Category:: Other
Cause:: An error occurred checking in work units.
Action:: Review the log file to determine the nature of the problem.

ESS-01207: Failed to check in work unit {0}.
Category:: Other
Cause:: An error occurred checking in work units.
Action:: Review the log file to determine the nature of the problem.

ESS-01208: Failed to undefer DeleteProcessGroup work for execution group {0}.
Category:: Other
Cause:: An error occurred undeferring a DeleteProcessGroupEvent.
Action:: Review the log file to determine the nature of the problem.

ESS-01209: Failed to update information for work {0} for request {1}.
Category:: Other
Cause:: An error occurred updating a work unit.
Action:: Review the log file to determine the nature of the problem.

ESS-01210: Failed to undefer work for request {0}.
Category:: Other
Cause:: An error occurred undeferring a work unit.
Action:: Review the log file to determine the nature of the problem.

ESS-01211: Failed to check in work for instance {0}.
Category:: Other
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.

ESS-01212: Error retrieving available work units.
Category:: Other
Cause:: Error occurred while retrieving work units to process.
Action:: Review the log file for runtime cause.

ESS-01213: Failed to retrieve work unit {0}.
Category:: Other
Cause:: Error occurred while retrieving a work unit to process.
Action:: Review the log file for runtime cause.

ESS-01214: Failed to determine if work {0} is checked out to instance {1}.
Category:: Other
Cause:: Failed to determine if the work is checked out to this instance.
Action:: Review the log file for runtime cause.

ESS-01215: Error occurred querying check out work units for instance {0}.
Category:: Other
Cause:: Failed to determine the work units checked out to the instance.
Action:: Review the log file for runtime cause.

ESS-01216: Failed to access work unit {0}.
Category:: Other
Cause:: Error occurred attempting to access work unit.
Action:: Review the log file for runtime cause.

ESS-01217: Error waiting for work.
Category:: Other
Cause:: Error occurred while waiting for new work.
Action:: Review the log file for runtime cause.

ESS-01218: Error waiting for work. Operation returned: {0}.
Category:: Other
Cause:: Operation used to work for new work returned the specified result.
Action:: Review the log file for runtime cause.

ESS-01219: Work unit {0} is not checked out to instance {1}.
Category:: Other
Cause:: The work unit is not checked out to the specified instance.
Action:: None

ESS-01220: Failed to lock work unit {0} by instance {1}.
Category:: Other
Cause:: Failed to lock the work unit by the specified instance.
Action:: None

ESS-01221: Requests {0} can not be cancelled. Please check server logs for more details.
Category:: Programmatic
Cause:: Requests can not be cancelled as there may be errors in cancelling the requests.
Action:: Please check server logs for more details

ESS-01222: Number of requests that needs to be cancelled in one go, should not exceed max limit of 100 records.
Category:: Programmatic
Cause:: Number of requests that needs to be cancelled in one go, should not exceed max limit of 100 records
Action:: Please provide requests less than 100 records.

ESS-01223: Filter with null value is not supported.Please provide valid filter which includes requests with non-terminal states.
Category:: Programmatic
Cause:: Filter with null value is not supported.
Action:: Please provide valid filters which includes requests with non-terminal states.

ESS-01250: Error retrieving available event work.
Category:: Other
Cause:: Error occurred while retrieving event work to process.
Action:: Review the log file for runtime cause.

ESS-01251: Failed to access event work {0}.
Category:: Other
Cause:: Error occurred attempting to access event work.
Action:: Review the log file for runtime cause.

ESS-01252: Failed to update event work {0}.
Category:: Other
Cause:: Error occurred attempting to update event work.
Action:: Review the log file for runtime cause.

ESS-01253: Failed to delete event work {0}.
Category:: Other
Cause:: Error occurred attempting to delete event work.
Action:: Review the log file for runtime cause.

ESS-01254: Failed to delete event work for request {0}.
Category:: Other
Cause:: Error occurred attempting to delete event work for a request.
Action:: Review the log file for runtime cause.

ESS-01255: Failed to check in event work {0}.
Category:: Other
Cause:: Error occurred attempting to check in event work.
Action:: Review the log file for runtime cause.

ESS-01256: Failed to check in event work for instance {0}.
Category:: Other
Cause:: Error occurred attempting to check in event work for an instance.
Action:: Review the log file for runtime cause.

ESS-01257: Failed to add event. Event name: {0}, request: {1}.
Category:: Other
Cause:: Error occurred attempting to insert event work.
Action:: Review the log file for runtime cause.

ESS-01258: Event work not found: {0}.
Category:: Other
Cause:: The specified event work was not found.
Action:: None

ESS-01259: Error waiting for event work.
Category:: Other
Cause:: Error occurred while waiting for new event work.
Action:: Review the log file for runtime cause.

ESS-01260: Error waiting for event work. Operation returned: {0}.
Category:: Other
Cause:: Operation used to work for new event work returned the specified result.
Action:: Review the log file for runtime cause.

ESS-01262: Event work {0} is not checked out to instance {1}.
Category:: Other
Cause:: The event work is not checked out to a specific instance.
Action:: None

ESS-01263: Invalid event listener class, {0}.
Category:: Other
Cause:: The class name configured for the request listener is not a valid event listener class.
Action:: None

ESS-01264: Unable to instantiate event listener for class, {0}.
Category:: Other
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.

ESS-01265: Unable to retrieve information needed to dispatch an event for request {0}.
Category:: Other
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.

ESS-01266: Failed to lock event work {0} by instance {1}.
Category:: Other
Cause:: Failed to lock the event work by the specified instance.
Action:: None

ESS-01290: Invalid logical cluster name value {0}.
Category:: Other
Cause:: An invalid logical cluster name was specified.
Action:: Specify a valid logical cluster name.

ESS-01291: A logical cluster name is not allowed to contain the character '.'.
Category:: Other
Cause:: An invalid logical cluster name was specified.
Action:: Specify a valid logical cluster name.

ESS-01300: Unable to access content store for request {0}, file {1}. {2}.
Category:: Other
Cause:: Failed to access the content store.
Action:: Review the log file for runtime cause.

ESS-01301: Failed to create content for request {0}, content name {1}. {2}.
Category:: Other
Cause:: Failed to create content for the request.
Action:: Review the log file for runtime cause.

ESS-01302: Failed to update content for request {0}, content name {1}. {2}.
Category:: Other
Cause:: Failed to update content for the request.
Action:: Review the log file for runtime cause.

ESS-01303: Failed to import file to content store for request {0}, file {1}. {2}.
Category:: Other
Cause:: Failed to import file to the content store for the request.
Action:: Review the log file for runtime cause.

ESS-01304: Failed to export content for request {0}, content name {1}. {2}.
Category:: Other
Cause:: Failed to export content for the request.
Action:: Review the log file for runtime cause.

ESS-01305: Failed to delete content for request {0}, content name {1}. {2}.
Category:: Other
Cause:: Failed to delete content for the request.
Action:: Review the log file for runtime cause.

ESS-01306: Failed to delete all content for request {0}. {1}.
Category:: Other
Cause:: Failed to delete all content for the request.
Action:: Review the log file for runtime cause.

ESS-01307: Invalid write to output content for request {0}, content name {1}.
Category:: Other
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.

ESS-01308: The content does not exist for request {0}, content name {1}.
Category:: Other
Cause:: The content does not exist for the request.
Action:: Ensure you are using the correct content name.

ESS-01309: Invalid content handle.
Category:: Other
Cause:: The content handle is invalid.
Action:: Re-open the content and use the valid handle.

ESS-01310: The file does not exist for request {0}, file name {1}.
Category:: Other
Cause:: The file does not exist for the request.
Action:: Ensure you are using the correct file name.

ESS-01312: Failed to close the output file for request {0}, file name {1}. {2}.
Category:: Other
Cause:: Failed to close the output file for the request.
Action:: Review the log file for runtime cause.

ESS-01313: Invalid directory for request {0}, directory {1}.
Category:: Other
Cause:: The directory is invalid for the request.
Action:: Ensure you are using the correct file name.

ESS-01314: Incompatible content operation for request {0}, content name {1}.
Category:: Other
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.

ESS-01315: Error creating directory for request {0}, directory {1}.
Category:: Other
Cause:: Failed to create the request directory.
Action:: Ensure that RequestFileDirectory is configured correctly for the application and that the directory is writeable.

ESS-01316: Error exporting output content for request {0}, status {1}.
Category:: Other
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.

ESS-01317: Error importing output content for request {0}, status {1}, directory {2}. {3}
Category:: Other
Cause:: Failed to import output files from the request output directory.
Action:: Check the log for errors.

ESS-01318: Failed to import the log for request {0}, log file {1}. {2}.
Category:: Other
Cause:: Failed to import the request log.
Action:: Review the log file for runtime cause.

ESS-01319: Invalid content handle mode for request {0}, content {1}.
Category:: Other
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.

ESS-01320: Invalid RequestFileDirectory {0} for application {1}.
Category:: Other
Cause:: The application has an invalid RequestFileDirectory configured.
Action:: Configure a valid RequestFileDirectory for the application.

ESS-01321: Error deleting files for request {0}, directory {1}.
Category:: Other
Cause:: Failed to delete files from the request work directory.
Action:: Manually delete the files from the file system.

ESS-01322: Error preserving log or output files for request {0}. {1}
Category:: Other
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.

ESS-01323: Invalid content open options for request {0} content category {1}, content name {2}.
Category:: Other
Cause:: The content open options are invalid.
Action:: Ensure that the content open options contain a single operation, and if applicable, options that are consistent with that operation.

ESS-01500: Dispatcher cannot be started while in {0} state.
Category:: Other
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.

ESS-01501: Dispatcher cannot be stopped while in {0} state.
Category:: Other
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.

ESS-01502: Processor cannot be started while in {0} state.
Category:: Other
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.

ESS-01503: Processor cannot be stopped while in {0} state.
Category:: Other
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.

ESS-01504: Cannot add endpoint {0} for application {1} because endpoint {2} already exists for application {3}.
Category:: Deployment
Cause:: The endpoint to add conflicts with an already existing endpoint.
Action:: Modify the endpoint name.

ESS-01505: Failed to retrieve information for request {0}.
Category:: Other
Cause:: Failed to retrieve runtime information for a request.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01506: Unable to create diagnostic incident. {0}
Category:: Other
Cause:: Failed to create diagnostic incident.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01507: Unable to register diagnostic dumps or rules. {0}
Category:: Other
Cause:: Failed to register diagnostic dumps or rules.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01508: Unable to unregister diagnostic dumps or rules. {0}
Category:: Other
Cause:: Failed to unregister diagnostic dumps or rules.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01509: Unable to create the diagnostic dump {0}. {1}
Category:: Other
Cause:: Failed to create the diagnostic dump.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01601: JobSet request {0} completed with an invalid final state {1}.
Category:: Other
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.

ESS-01602: First step is not defined in serial JobSet: {0}.
Category:: Other
Cause:: Cannot process a JobSet request due to invalid JobSet definition. The first step of a serial JobSet is not defined.
Action:: None

ESS-01603: Error dispatching subrequests for parent request {0}.
Category:: Other
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.

ESS-01604: Failed to create {0} work unit for request {1}.
Category:: Other
Cause:: Unable to create the specified work unit for a request.
Action:: Review the log file to determine the nature of the problem.

ESS-01605: Failed to create event, {0}, for request {1}.
Category:: Other
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.

ESS-01606: Failed to mark request {0} as completed.
Category:: Other
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.

ESS-01607: Request {0} cannot be marked complete. State is {1}, process phase is {2}.
Category:: Other
Cause:: The request state and/or process phase prevents a request from being completed.
Action:: None

ESS-01608: Error occurred while processing request {0} by request dispatcher.
Category:: Other
Cause:: Failed to perform dispatch proccessing for the specified request.
Action:: Review the log file to determine the nature of the problem.

ESS-01700: Unrecognized request type : {0}.
Category:: Programmatic
Cause:: The job type used for the request is not supported.
Action:: Correct the job type definition.

ESS-01701: Unable to instantiate executable wrapper for execution type {0}.
Category:: Installation
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.

ESS-01702: Unable to instantiate pre-process callback handler for request {0} using class name, {1}.
Category:: Programmatic
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.

ESS-01703: Unable to instantiate post-process callback handler for request {0} using class name, {1}.
Category:: Programmatic
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.

ESS-01704: Error occurred at initiate stage during execution of request {0}. {1}
Category:: Programmatic
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.

ESS-01705: Error occurred at finalize stage during execution of request {0}. {1}
Category:: Programmatic
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.

ESS-01706: Invalid execution result code, {0}, for request {1}.
Category:: Programmatic
Cause:: A REQUEST_FINALIZATION event contained an unknown result code.
Action:: This indicates an internal error. Contact Oracle Support Services.

ESS-01707: Unable to instantiate Executable for Java request {0} using class name, {1}.
Category:: Programmatic
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.

ESS-01708: Database job for request {0} ended with error: {1}.
Category:: Programmatic
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.

ESS-01709: Database job for request {0} ended with warning: {1}.
Category:: Programmatic
Cause:: Execution of a SQL request has ended with a warning.
Action:: None.

ESS-01710: Database job for request {0} was cancelled.
Category:: Programmatic
Cause:: Execution of a SQL request has been cancelled.
Action:: None.

ESS-01711: Database job for request {0} was paused. Paused state value: {1}.
Category:: Programmatic
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.

ESS-01712: Failed to create database job for request {0}.
Category:: Other
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.

ESS-01713: Error cancelling database job for request {0}.
Category:: Other
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.

ESS-01714: Database job for request {0} ended with business error: {1}.
Category:: Programmatic
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.

ESS-01715: Failed to create database job for request {0} using Oracle Scheduler job class {1}.
Category:: Other
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.

ESS-01716: Unable to process JobSet request {0}. JobSet definition has no steps: {1}
Category:: Programmatic
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.

ESS-01900: Error constructing ESS command {0}. {1}
Category:: Other
Cause:: An error is present in the command format.
Action:: Contact Oracle Support Services.

ESS-01901: Unsupported value, {0}, for attribute {1}.
Category:: Programmatic
Cause:: An unknown value was specified for a parameter.
Action:: Specify a valid attribute value.

ESS-01903: Unknown command type {0}. {1}
Category:: Other
Cause:: An unknown command type was submitted.
Action:: None

ESS-01904: Document is not valid for work {0}.
Category:: Other
Cause:: The command document is invalid for this Enterprise Scheduler server
Action:: None. The command will be deferred.

ESS-01905: Attribute {0} value {1} from command document does not match value {2} from command creation.
Category:: Other
Cause:: The internal command state is inconsistent for the given attribute.
Action:: Contact administrator.

ESS-01906: Error retrieving available command work.
Category:: Other
Cause:: Error occurred while retrieving command work to process.
Action:: Review the log file for runtime cause.

ESS-01907: Failed to access command work {0}.
Category:: Other
Cause:: Error occurred attempting to access command work.
Action:: Review the log file for runtime cause.

ESS-01908: Failed to update command work {0}.
Category:: Other
Cause:: Error occurred attempting to update command work.
Action:: Review the log file for runtime cause.

ESS-01909: Failed to delete command work {0}.
Category:: Other
Cause:: Error occurred attempting to delete command work.
Action:: Review the log file for runtime cause.

ESS-01910: Failed to delete command work for request {0}.
Category:: Other
Cause:: Error occurred attempting to delete command work for a request.
Action:: Review the log file for runtime cause.

ESS-01911: Failed to check in command work {0}.
Category:: Other
Cause:: Error occurred attempting to check in command work.
Action:: Review the log file for runtime cause.

ESS-01912: Failed to check in command work for instance {0}.
Category:: Other
Cause:: Error occurred attempting to check in command work for an instance.
Action:: Review the log file for runtime cause.

ESS-01913: Command work not found: {0}.
Category:: Other
Cause:: The specified command work was not found.
Action:: None

ESS-01914: Command work {0} is not checked out to instance {1}.
Category:: Other
Cause:: The command work is not checked out to a specific instance.
Action:: None

ESS-01915: Failed to lock command work {0} by instance {1}.
Category:: Other
Cause:: Failed to lock the command work by the specified instance.
Action:: None

ESS-01970: Error during request purge processing.
Category:: Other
Cause:: An error was encountered during purge of request data.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01971: Error while purging request data from table {0} for request {1}.
Category:: Other
Cause:: An error was encountered during purge of request data from the specified table.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01972: Error during request purge processing for session {0}.
Category:: Other
Cause:: An error was encountered during purge of request data.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01973: Error while purging request data from table {0} for session {1}.
Category:: Other
Cause:: An error was encountered during purge of request data from the specified table.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01974: Error while purging request data from table {0} for request {1}, session {2}.
Category:: Other
Cause:: An error was encountered during purge of request data from the specified table.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01980: Batch delete initialization failed.
Category:: Other
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.

ESS-01981: Failed to delete request {0}. Reason: {1}
Category:: Other
Cause:: An error occurred attempting to delete a request.
Action:: None

ESS-01982: Insufficient privileges to delete request {0}.
Category:: Other
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

ESS-01983: Error determining requests for batch delete.
Category:: Other
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.

ESS-01984: Error occurred while executing batch delete request {0}. Cause: {1}
Category:: Other
Cause:: An error occurred during request execution.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01985: Execution of request {0} was cancelled.
Category:: Other
Cause:: Request execution was canceled.
Action:: None

ESS-01987: Runtime store error during batch delete.
Category:: Other
Cause:: Runtime store error occurred during batch delete operation.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01988: Failed to lock request for batch delete.
Category:: Other
Cause:: Unable to lock one or more requests during batch delete operation
Action:: None

ESS-01989: Batch delete request {0} failed to delete request {1}. Reason: {2}
Category:: Other
Cause:: Batch delete job failed to delete the specified request.
Action:: Review log file to determine the reason.

ESS-01995: Failed to create delete session.
Category:: Other
Cause:: Failed to initialize delete session used for request data delete or purge.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01996: Failed to lock delete session table.
Category:: Other
Cause:: Failed to lock delete session table used for request data delete or purge.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01997: Failed to access delete session information.
Category:: Other
Cause:: Failed to access delete session information used for request data delete or purge.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-01998: Runtime store operation failed for delete session {0}.
Category:: Other
Cause:: Runtime store error occurred during delete session operation.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-02001: User {0} does not have execute permission on metadata object {1}. Request {2} execution is aborted.
Category:: Other
Cause:: User {0} does not have execute permission on metadata object {1}. Request {2} execution is aborted.
Action:: Check the policy assignment..

ESS-02002: User {0} does not have sufficient privilege to perform operation {1}.
Category:: Other
Cause:: User {0} does not have sufficient privilege to perform operation {1}.
Action:: Grant the policy to the user {0}..

ESS-02003: User {0} does not have sufficient privilege to perform operation {1} on request {2}.
Category:: Other
Cause:: User {0} does not have sufficient privilege to perform operation {1} on request {2}.
Action:: Grant the policy to the user {0}..

ESS-02004: User or appid {0} is not a valid entry in the identity store.
Category:: Other
Cause:: {0} can not be authenticated.
Action:: Check the user settting.

ESS-02005: User {0} does not have {1} privilege on metadata object {2}. Request {3} validation failed.
Category:: Other
Cause:: User {0} does not have {1} privilege on metadata object {2}. Request {3} validation failed.
Action:: Check the policy assignment..

ESS-02006: User {0} does not have sufficient privilege to perform operation {1} on job set {2}, failed steps are {3}.
Category:: Other
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}..

ESS-02007: User or appid {0} that job {1} runs as is not a valid entry in the identity store.
Category:: Other
Cause:: The user or appid {0} is not a valid identity or can not be authenticated.
Action:: Check your metadata definition.

ESS-02008: Invalid value {0} specified for FADataSecurityPolicyOverrides property in ess-config. Continuing permission checks using default FND policy.
Category:: Other
Cause:: Invalid value specified for FADataSecurityPolicyOverrides property in ess-config
Action:: Use a supported value.

ESS-02200: Mismatched request handles for request {0}.
Category:: Other
Cause:: The request may have been retried.
Action:: Update with request execution context from new execution if desired.

ESS-02220: Failed to deliver web service callback for message {0} for request {1}.
Category:: Other
Cause:: The web service asynchronous callback message could not be delivered.
Action:: The action may be retried. Check the log files.

ESS-02221: Invalid web service request message {0} for getCompletionStatus operation.
Category:: Other
Cause:: The web service request to getCompletionStatus was invalid.
Action:: Check the attached exceptions and fix the web service request.

ESS-03000: Metadata name cannot contain character '/'
Category:: Other
Cause:: Invalid metdata type name
Action:: Provide a valid metadata name

ESS-03001: Both explicit date and recurrence cannot be null.
Category:: Other
Cause:: Both explicit date and recurrence cannot be null.
Action:: Provide explicit date or recurrence.

ESS-03002: ExclusionDefinition must contain at least one exclusion
Category:: Other
Cause:: ExclusionDefinition is empty
Action:: Include atleast one exclusion in ExclusionDefinition.

ESS-03003: Incompatibility already has an entity for job definition:{0}
Category:: Other
Cause:: Incompatibility already has the corresponding job definition.
Action:: Don't add the job definition to the Incompatibility.

ESS-03004: Incompatibility defined for a single entity must be self-incompatible on that entity.
Category:: Other
Cause:: Incompatibility defined for a single entity must be self-incompatible on that entity
Action:: A valid incompatibility definition must have at least two entities or one self-incompatible entity

ESS-03005: Identifier not specified for incompatibility entity.
Category:: Other
Cause:: Identifier not specified for incompatibility entity.
Action:: Specify identifier for incompatibility entity.

ESS-03006: Property not specified for an entity of a {0} incompatibility
Category:: Other
Cause:: Property not specified for Incompatibility entity.
Action:: Specify property for Incompatibility entity.

ESS-03007: Property {0} is defined as read-only in the JobType definition.
Category:: Other
Cause:: Read-only property is defined in JobType definition
Action:: Make sure that no read-only property is specified for Jobtype Definition.

ESS-03008: Unable to convert steps to XML Document
Category:: Other
Cause:: Conversion of JobSet's JobSetStep objects to an XML Document failed
Action:: Internal error

ESS-03009: Failed to validate Jobset/JobsetSteps document against the schema :{0}
Category:: Other
Cause:: Failed to validate Jobset/JobsetSteps document against the schema
Action:: Internal error

ESS-03010: Unable to convert XML steps to objects
Category:: Other
Cause:: Unable to convert XML steps to objects
Action:: Internal error

ESS-03011: First step must be defined for serial job set.
Category:: Other
Cause:: Jobset has steps, but the first step is not defined.
Action:: First step must be defined for serial jobset.

ESS-03012: First step id does not specify a defined step:{0}
Category:: Other
Cause:: First step id of Jobset does not specify a defined step
Action:: First step must be a defined one for serial jobset.

ESS-03013: Invalid link step id for {0}
Category:: Other
Cause:: Invalid link step id
Action:: Check that step links are valid step ids..

ESS-03014: Jobset has no steps.
Category:: Other
Cause:: Jobset has no steps
Action:: Ensure Jobset have steps

ESS-03015: Invalid Serial JobSet:loops are not allowed. See step {0}
Category:: Other
Cause:: Invalid Serial JobSet:loops are not allowed
Action:: Avoid loops in serial Jobset

ESS-03016: Step already exists:{0}
Category:: Other
Cause:: Step already exists in Jobset
Action:: Avoid adding duplicate step

ESS-03017: Can''t define Procedure Name, or CmdLine for a Java JobType definition
Category:: Other
Cause:: Cannot define Procedure Name, or CmdLine for a Java JobType definition
Action:: Java job type cannot have properties of SQL or PROCESS Job Type.

ESS-03018: Can''t define Class Name, CmdLine, or for a SQL JobType definition
Category:: Other
Cause:: Cannot define Class Name, CmdLine for a SQL JobType definition
Action:: Procedure name can be defined for SQL JobType.

ESS-03019: Can''t define Class Name or Procedure name for a Binary JobType definition
Category:: Other
Cause:: Cannot define Class Name or Procedure name for a Process JobType definition
Action:: CmdLine supported for Process JobType.

ESS-03020: Both FREQUENCY and ICAL Expression cannot be null
Category:: Other
Cause:: Both FREQUENCY and ICAL Expression cannot be null
Action:: Specify either Frequency or Ical expression.

ESS-03021: Cannot have start date after end date
Category:: Other
Cause:: Cannot have start date after end date
Action:: Correct the start or end date

ESS-03022: Cannot specify Recurrence Fields WEEK_OF_MONTH without DAY_OF_WEEK
Category:: Other
Cause:: Cannot specify recurrence fields WEEK_OF_MONTH without DAY_OF_WEEK
Action:: Given weeks of month, days of week is must.

ESS-03023: Cannot specify MONTH_OF_YEAR for MONTHLY frequency. MONTH_OF_YEAR can be specified for YEARLY frequency.
Category:: Other
Cause:: Cannot specify recurrence fields MONTH_OF_YEAR for MONTHLY frequency.
Action:: Month of year can be specified for yearly frequency.

ESS-03024: Cannot specify MONTH_OF_YEAR, WEEK_OF_MONTH or DAY_OF_MONTH for WEEKLY frequency
Category:: Other
Cause:: Cannot specify recurrence fields MONTH_OF_YEAR, WEEK_OF_MONTH or DAY_OF_MONTH for WEEKLY frequency
Action:: Other fields cannot have bigger scope then frequency

ESS-03025: Only TIME_OF_DAY field can be specified with DAILY frequency
Category:: Other
Cause:: Only time of day field can be specified with daily frequency.
Action:: Only time of day field can be specified with daily frequency.

ESS-03026: RecurrenceFields cannot be specified with 'HOURLY', 'MINUTELY' or 'SECONDLY' frequency
Category:: Other
Cause:: Recurrence fields cannot be specified with HOURLY, MINUTELY or SECONDLY frequency
Action:: Recurrence fields cannot be specified with HOURLY, MINUTELY or SECONDLY frequency

ESS-03027: RecurrenceFields have invalid Month, Date combinations.
Category:: Other
Cause:: Recurrence fields have invalid Month, Date combinations.
Action:: Specify correct month, date combinations.

ESS-03028: RecurrenceSet can''t have more than {0} recurrences
Category:: Other
Cause:: RecurrenceSet cannot have more than 5 recurrences
Action:: Reduce the number of recurrences

ESS-03029: Event filters should have no more than one operator
Category:: Other
Cause:: Event filters have more than one operator.
Action:: Correct Event filters to have no more than one operator.

ESS-03030: {0} and {1} are the only supported fields for event filters
Category:: Other
Cause:: EventType and EventName are the only supported fields for event filters.
Action:: EventType and EventName are the only supported fields for event filters.

ESS-03031: Work Assignment must specify at least one Workshift
Category:: Other
Cause:: Work Assignment has no Workshift.
Action:: Work Assignment must specify at least one Workshift.

ESS-03033: Illegal value provided for Actions in parameter
Category:: Other
Cause:: Illegal value provided for Metadata permission actions in parameter.
Action:: Illegal value provided for Metadata permission actions in parameter.

ESS-03034: MetadataPermissionStrings parameter cannot be null.
Category:: Other
Cause:: MetadataPermissionStrings parameter cannot be null or empty.
Action:: Specify non-empty metadata permission strings

ESS-03035: Actions parameter cannot be null.
Category:: Other
Cause:: Actions parameter cannot be null or empty.
Action:: Actions parameter cannot be null or empty.

ESS-03036: Failed to commit changes and close service handle. Referential Integrity violation detected. Referencing objects exist for the object(s) being deleted.
Category:: Other
Cause:: Deletion of object not possible as it is referenced by some other object
Action:: Check the dependent objects before deletion.

ESS-03037: Invalid options due to missing operation: {0}
Category:: Other
Cause:: Invalid options.
Action:: Provide valid options.

ESS-03038: Invalid options for Read operation: {0}
Category:: Other
Cause:: Invalid options for Read operation.
Action:: Specify correct options for read operation.

ESS-03039: Invalid options for Write operation: {0}
Category:: Other
Cause:: Invalid options for Write operation.
Action:: Specify correct options for write operation.

ESS-03040: Invalid options for Import operation: {0}
Category:: Other
Cause:: Invalid options for Import operation.
Action:: Specify correct options for import operation

ESS-03041: Invalid options for Log content: {0}
Category:: Other
Cause:: Invalid options for Log content.
Action:: Specify correct options for log content.

ESS-03042: Definition is required
Category:: Other
Cause:: Job or jobset definition Id is missing
Action:: Job or jobset definition Id is required

ESS-03043: Incompatibility definition, {0}, from runtime store is {1} incompatibility type. Expected type is {2}
Category:: Other
Cause:: Incompatibility type mismatch between metadata store and runtime store for the request
Action:: There should be no mismatch. Internal error

ESS-03044: Incompatibility definition, {0},from runtime store does not contain an entity for {1}
Category:: Other
Cause:: Incompatibility definition from runtime store does not contain an entity for Job/Jobset
Action:: Entity must be present in Incompatibility definition. Internal error.

ESS-03045: Map parameter cannot be null.
Category:: Other
Cause:: Config properties map is null
Action:: Config properties map cannot be null

ESS-03046: Application parameter cannot be null.
Category:: Other
Cause:: Application parameter provided to fetch config properties is null
Action:: Provide non null application name.

ESS-03047: PropertyType enum cannot be null.
Category:: Other
Cause:: PropertyType enum is null.
Action:: PropertyType enum cannot be null.

ESS-03048: PropertyName parameter cannot be null.
Category:: Other
Cause:: PropertyName parameter is null.
Action:: PropertyName parameter cannot be null.

ESS-03049: PropertyValue parameter cannot be null.
Category:: Other
Cause:: PropertyValue parameter is null.
Action:: PropertyValue parameter cannot be null.

ESS-03050: Trigger definition cannot be null.
Category:: Other
Cause:: Trigger definition is null.
Action:: Trigger definition cannot be null.

ESS-03051: No specialization in configured bindings for {0}
Category:: Other
Cause:: No specialization in configured bindings.
Action:: Specify specialization in configured bindings.

ESS-03052: {0} is not bound on this instance
Category:: Other
Cause:: Work Assignment not bound on this instance.
Action:: Work Assignment not bound on this instance.

ESS-03053: Request parameters cannot be null.
Category:: Other
Cause:: Request parameters are null.
Action:: Request parameters cannot be null.

ESS-03054: Illegal value provided for Actions in parameter.
Category:: Other
Cause:: Illegal value provided for Actions in parameter.
Action:: Provide proper values for Actions in parameter.

ESS-03055: Invalid binding mode: name={0},exclusiveMode={1}
Category:: Other
Cause:: Invalid binding mode.
Action:: Invalid binding mode.

ESS-03056: Filter parameters with DATETIME datatype are not supported
Category:: Other
Cause:: Filter parameters with DATETIME datatype are not supported.
Action:: DATETIME datatype cannot be used with Filter parameters

ESS-03058: Value of deltaStart or deltaEnd cannot be negative
Category:: Other
Cause:: Value of deltaStart or deltaEnd is negative.
Action:: Value of deltaStart or deltaEnd cannot be negative

ESS-03059: Datatype is not supported for a parameter value:{0}
Category:: Other
Cause:: Unsupported datatype for parameter.
Action:: Unsupported datatype for parameter.

ESS-03060: Failed to convert parameter value to data type:{0}
Category:: Other
Cause:: Failed to convert parameter value to data type.
Action:: Failed to convert parameter value to data type.

ESS-03061: Value of parameter {0} has data type {1} instead of the expected data type {2}
Category:: Other
Cause:: Parameter value datatype mismatch.
Action:: Parameter value datatype mismatch.

ESS-03062: Step must be JobDefinition or JobSet
Category:: Other
Cause:: Invalid step type.
Action:: Step must be JobDefinition or JobSet.

ESS-03063: Unknown data type for parameter {0}
Category:: Other
Cause:: Unknown datatype for parameter.
Action:: Unknown datatype for parameter.

ESS-03064: Operation not supported for scoped parameter {0}
Category:: Other
Cause:: Operation not supported for scoped parameter.
Action:: Operation not supported for scoped parameter.

ESS-03065: RecurrenceSet must contain at least one recurrence
Category:: Other
Cause:: RecurrenceSet is empty.
Action:: RecurrenceSet must contain atleast one recurrence.

ESS-03066: Unable to delete workshift {0} that is referenced by a work assignment.
Category:: Other
Cause:: Wokshift deletion failed as it is referenced by a work assignment
Action:: Ensure that workshift is not referenced in a work assignment before deletion

ESS-03067: Unable to delete schedule {0} that is referenced by a workshift.
Category:: Other
Cause:: Schedule deletion failed as it is referenced by a work shift
Action:: Ensure that schedule is not referenced by a work shift before deletion

ESS-05000: Error occurred. {0}
Category:: Other
Cause:: Enterprise Scheduler Service encountered an error.
Action:: Review the log file for indications of the problem.

ESS-05010: Request {0} not found.
Category:: Other
Cause:: Request with the given request id can not be found in the database.
Action:: None

ESS-05011: Request {0} set to {1} state.
Category:: Other
Cause:
Action:

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

ESS-05013: Request {0}. Process phase {1} not in valid phases {2}.
Category:: Other
Cause:: The process phase of the request is inconsistent with its current status.
Action:: None

ESS-05015: Oracle Enterprise Scheduler. Release Version: {0}, Build: {1}
Category:: Other
Cause:: Information about release version and build label of Oracle Enterprise Scheduler.
Action:: No action is necessary.

ESS-05016: Oracle Enterprise Scheduler runtime store. Schema Name: {0}, Version: {1}, Status: {2}
Category:: Other
Cause:: Information about the runtime store used by Oracle Enterprise Scheduler.
Action:: No action is necessary.

ESS-05021: Failed to begin transaction.
Category:: Other
Cause:: Being of a user transaction failed.
Action:: Review the log file for runtime cause.

ESS-05022: Failed to commit transaction.
Category:: Other
Cause:: Failed to commit the transaction.
Action:: Review the log file for runtime cause.

ESS-05023: Failed to rollback transaction.
Category:: Other
Cause:: Failed to rollback the transaction.
Action:: Review the log file for runtime cause.

ESS-05024: Failed to set transaction timeout.
Category:: Other
Cause:: Failed to set transaction timeout.
Action:: Review the log file for runtime cause.

ESS-05025: Error in transaction processing. The transaction is eligible to be retried.
Category:: Other
Cause:: A recoverable SQL error was encountered
Action:: None

ESS-05038: Failed to find JNDI resource for {0}.
Category:: Configuration
Cause:: Failed to perform a JNDI lookup for a given resource name.
Action:: Verify the configuration for the resource.

ESS-05039: Error occurred closing JNDI naming context.
Category:: Other
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.

ESS-05043: Failed to commit SQL transaction.
Category:: Other
Cause:: An error occurred trying to commit database transaction.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-05044: Failed to rollback SQL transaction.
Category:: Other
Cause:: An error occurred trying to rollback database transaction.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-05045: Error using SQL ResultSet. {0}
Category:: Other
Cause:: An error occurred while using an SQL ResultSet.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-05046: Failed to close an SQL ResultSet.
Category:: Other
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.

ESS-05047: Failed to close an SQL Statement.
Category:: Other
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.

ESS-05048: Failed to obtain a database connection.
Category:: Other
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.

ESS-05049: Failed to close a database connection.
Category:: Other
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.

ESS-05053: Failed to map object of type {0} to CompositeData.
Category:: Other
Cause:: An error occurred converting an ESS object to a javax.management.openmbean.CompositeData object
Action:: Contact Oracle Support Services

ESS-05054: Failed to map CompositeData object to {0}.
Category:: Other
Cause:: An error occurred converting a javax.management.openmbean.CompositeData object to an ESS object
Action:: Contact Oracle Support Services

ESS-05055: Illegal state transition from {0} to {1} for request {2}.
Category:: Other
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.

ESS-05100: Operator {1} is invalid with query field {0}. Valid operators are: {2}.
Category:: Other
Cause:: Operator is invalid for the given query field.
Action:: Use a valid operator.

ESS-05101: Comparator {1} is invalid with query field {0}. Valid comparators are: {2}.
Category:: Other
Cause:: Comparator is invalid for the given query field.
Action:: Use a valid comparator.

ESS-05102: Value of type {1} is invalid with query field {0}. Valid value types are: {2}.
Category:: Other
Cause:: Value type is invalid for the given query field.
Action:: Use a valid value type.

ESS-05103: Value of type null is invalid with query field {0}.
Category:: Other
Cause:: Null value type is invalid for the given query field.
Action:: Use a valid non-null value type.

ESS-05104: Failed to check in {0} work unit {1} for request {2}. {3}
Category:: Other
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.

ESS-05105: Metadata of type {0} cannot be customized. Only metadata of the following types can be customized: {1}.
Category:: Other
Cause:: An invalid metadata type was provided.
Action:: Provide a valid customizable metadata type.

ESS-05106: Property {0} cannot be assigned a value of type {1}. Values for property {0} can only have the following types: {2}.
Category:: Other
Cause:: The data type of the provided property is not valid.
Action:: Provide a value with the correct data type.

ESS-05107: An error occurred while parsing the metadata object id string: {0}
Category:: Other
Cause:: An error occurred while parsing a metadata object id string.
Action:: See base exception for detailed underlying cause.

ESS-05108: The user provided metadata type of {0} does not match the metadata type of {1} in the metadata object id string
Category:: Other
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.

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.
Category:: Other
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.

ESS-05110: An error occurred while retrieving the metadata object with name {0} of type {1}.
Category:: Other
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.

ESS-05111: Bulk metadata customization input file {0} does not exist or is not readable.
Category:: Other
Cause:: Invalid XML input file specified for bulk customization.
Action:: Provide the correct input XML file for bulk customization.

ESS-05112: Bulk metadata customization output file {0} is not writable.
Category:: Other
Cause:: Invalid XML output file specified for bulk customization.
Action:: Provide the correct output XML file absolute pathname.

ESS-05113: Argument type is not supported: {0}
Category:: Other
Cause:: The type of argument is unsupported.
Action:: Use a supported argument type.

ESS-05114: Failed to check in {0} work unit {1}. {2}
Category:: Other
Cause:: The work unit could not be checked in or deleted.
Action:: The work unit operation should be automatically retried, so no action is necessary.

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

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

ESS-05204: NamingException looking up EssConnection {0}.
Category:: Other
Cause:: NamingException looking up EssConnection.
Action:: Review the log file for attached exceptions to determine the cause.

ESS-05205: Error reading EssConnection Tokens from adf-domain-config.
Category:: Other
Cause:: Error reading EssConnection Tokens from adf-domain-config.
Action:: Review the log file for attached exceptions to determine the cause.

ESS-05206: Error writing EssConnection Tokens to adf-domain-config.
Category:: Other
Cause:: Error writing EssConnection Tokens to adf-domain-config.
Action:: Review the log file for attached exceptions to determine the cause.

ESS-05490: Service MBeans registration failed.
Category:: Other
Cause:: Service MBeans registration failed.
Action:: Review the log file for underlying causes.

ESS-05700: Failed to obtain a metadata service instance. {0}
Category:: Other
Cause:: Failed to obtain a metadata service instance.
Action:: Review the log file for underlying causes.

ESS-05704: An error occurred invoking the MetadataService MBean. {0}
Category:: Programmatic
Cause:: An error occurred invoking the RuntimeService MBean.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-05705: Failed to save the {0} with name {1} in application {2}.
Category:: Programmatic
Cause:: Failed to save the metadata object.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-05706: {0} with name {1} does not exist in application {2}.
Category:: Programmatic
Cause:: Unable to find the metadata object.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-05707: {0} with name {1} already exists in application {2}.
Category:: Programmatic
Cause:: The metadata object already exists.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-05708: Failed to delete the {0} with name {1} in application {2}.
Category:: Programmatic
Cause:: Unable to delete the metadata object
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-05709: Metadata parameter {0} starts with {1} which is a reserved parameter keyword.
Category:: Programmatic
Cause:: A property defined by the metadata object contains a reserved keyword.
Action:: Remove the reserved keyword from the property name.

ESS-05710: A validation error occurred while validating JobSet step {0}.
Category:: Programmatic
Cause:: A JobSet step failed validation.
Action:: See the base validation exception for the original validation error.

ESS-05711: A null value cannot be used when querying the {0} field.
Category:: Other
Cause:: A value of null was used as the query value.
Action:: Provide a non-null argument.

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.
Category:: Programmatic
Cause:: The metadata object to be deleted resides in a read-only package.
Action:: This metadata object cannot be deleted by end users.

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.
Category:: Programmatic
Cause:: The metadata object to be updated resides in a read-only package.
Action:: This metadata object cannot be updated by end users.

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.
Category:: Programmatic
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.

ESS-05715: Metadata parameter {0} cannot have value {1} because {1} is a reserved value.
Category:: Programmatic
Cause:: The value of a property defined by the metadata object contains a reserved keyword.
Action:: Change the value of the property.

ESS-05716: Metadata parameter {0} cannot have an empty or null value.
Category:: Programmatic
Cause:: The value of a property defined by the metadata object was empty or null.
Action:: Change the value of the property.

ESS-06000: Failed to obtain a runtime service instance. {0}
Category:: Other
Cause:: Failed to obtain a runtime service instance.
Action:: Review log file for underlying cause.

ESS-06002: Failed to close runtime service handle. {0}
Category:: Other
Cause:: Failed to close runtime service handle.
Action:: Review the log file for underlying causes.

ESS-06003: Runtime service system failure. {0}
Category:: Other
Cause:: Runtime service system failure.
Action:: Review the log file for underlying causes.

ESS-06100: No request found for the given id {0}.
Category:: Programmatic
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.

ESS-06102: An error occurred invoking the RuntimeService MBean.
Category:: Other
Cause:: An error occurred invoking the RuntimeService MBean.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06500: Starting ESS resource adapter.
Category:: Other
Cause:
Action:

ESS-06501: Stopping ESS resource adapter.
Category:: Other
Cause:
Action:

ESS-06502: Endpoint activation for {0}.
Category:: Other
Cause:
Action:

ESS-06503: Endpoint deactivation for {0}.
Category:: Other
Cause:
Action:

ESS-06510: Registering application, {0}, via ClassLoader: {1}
Category:: Other
Cause:
Action:

ESS-06511: Registered application: {0} adfConfigUrl: {1} connUrl: {2}
Category:: Other
Cause:
Action:

ESS-06512: Removed registered configuration for application {0}.
Category:: Other
Cause:
Action:

ESS-06514: Application {0} is already registered.
Category:: Other
Cause:
Action:

ESS-06515: The logical name of this application, {0}, is already in use by the following deployed applications (possibly in different domains): {1}.
Category:: Other
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.

ESS-06516: The deployed name of this application, {0}, is already in use by the following logical applications (possibly in different domains): {1}.
Category:: Other
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.

ESS-06517: Logical application name {0} is a reserved keyword.
Category:: Other
Cause:: The specified logical application name is a reserved keyword.
Action:: Change the name of the logical application.

ESS-06521: Failed to start request dispatcher.
Category:: Other
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.

ESS-06522: Failed to start request processor.
Category:: Other
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.

ESS-06523: Failed to start system event service.
Category:: Other
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.

ESS-06524: Failed to start application event service.
Category:: Other
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.

ESS-06525: Failed to start heartbeat monitor.
Category:: Other
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.

ESS-06526: Failed to update configuration information.
Category:: Other
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.

ESS-06527: Failed to start deferred monitor.
Category:: Other
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.

ESS-06528: Failed to start work unit worker.
Category:: Other
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.

ESS-06529: Failed to start change event service.
Category:: Other
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.

ESS-06530: Dispatcher cannot be started when it is in the {0} state.
Category:: Other
Cause:: Dispatcher cannot be started when it is in the specified state.
Action:: Start the dispatcher when it is in STOPPED state.

ESS-06531: Dispatcher cannot be stopped when it is in the {0} state.
Category:: Other
Cause:: Dispatcher cannot be stopped when it is in the specified state.
Action:: Stop the dispatcher when it is in STARTING or RUNNING state.

ESS-06532: Processor cannot be started when it is in the {0} state.
Category:: Other
Cause:: Processor cannot be started when it is in the specified state.
Action:: Start the processor when it is in STOPPED state.

ESS-06533: Processor cannot be stopped when it is in the {0} state.
Category:: Other
Cause:: Processor cannot be stopped when it is in the specified state.
Action:: Stop the processor when it is in STARTING or RUNNING state.

ESS-06534: {0} is an unversioned ESS hosting application. Unversioned hosting applications are deprecated and will not be supported in subsequent releases. Some features are only supported for versioned applications.
Category:: Other
Cause:: The ESS hosting application does is not versioned.
Action:: Make the application versioned or expect certain features not to work.

ESS-06538: No endpoint is available for {0}.
Category:: Other
Cause:: An application using the specified endpoint application name is not deployed.
Action:: Review the log file for underlying causes.

ESS-06539: Could not create endpoint for {0}.
Category:: Other
Cause:: An error occurred creating an application endpoint.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06540: Failed to get an endpoint to run dispatcher for application {0}.
Category:: Other
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.

ESS-06541: Error during dispatch for application {0}.
Category:: Other
Cause:: Error during dispatch for application.
Action:: Review the log for underlying causes.

ESS-06542: Error getting applications to dispatch.
Category:: Other
Cause:: Error getting applications for dispatch.
Action:: Review the log for underlying causes.

ESS-06543: Failed to deactivate endpoint for application {0}.
Category:: Other
Cause:: An error occurred while removing an application endpoint.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06557: Failed to start heartbeat worker {0}.
Category:: Other
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.

ESS-06558: Failed to get an endpoint to run a heartbeat for application {0}.
Category:: Other
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.

ESS-06560: Error encountered by event worker.
Category:: Other
Cause:: Error encountered by event worker.
Action:: Review the log for underlying causes.

ESS-06570: Failed to get metadata for work assignment {0}.
Category:: Other
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.

ESS-06571: Failed to get workshift metadata ({0}) for work assignment {1}.
Category:: Other
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.

ESS-06572: Failed to get schedule metadata ({0}) for work assignment {1}.
Category:: Other
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.

ESS-06573: Failed to start work assignment {0}.
Category:: Other
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.

ESS-06574: Failed to start starvation thread for work assignment {0}.
Category:: Other
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.

ESS-06575: Skipping inactive work assignment {0}.
Category:: Other
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.

ESS-06576: Binding default work assignment.
Category:: Other
Cause:: The default work assignment is being bound because no user-defined work assignments were bound.
Action:: No action is necessary.

ESS-06577: Skipping inactive workshift {0} for work assignment {1}.
Category:: Other
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.

ESS-06578: Started work assignment {0}.
Category:: Other
Cause:: Started the work assignment.
Action:: No action is necessary.

ESS-06579: Stopped work assignment {0}.
Category:: Other
Cause:: Stopped the work assignment.
Action:: No action is necessary.

ESS-06580: Skipping invalid work assignment {0}.
Category:: Other
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.

ESS-06581: Skipping invalid work assignment binding {0}.
Category:: Other
Cause:: The work assignment is being ignored because the binding is invalid.
Action:: Check the work assignment binding mode and correct the problem.

ESS-06582: Skipping completed work assignment {0}.
Category:: Other
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.

ESS-06583: Cannot delete bound work assignment {0}.
Category:: Other
Cause:: A work assignment that is bound may not be deleted.
Action:: Unbind the work assignment and then delete it.

ESS-06584: Reloading metadata for work assignment {0}.
Category:: Other
Cause:: Reloaded the work assignment metadata.
Action:: No action is necessary.

ESS-06585: Unable to bind work assignment {0} due to invalid workshift {1}.
Category:: Other
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.

ESS-06586: Work assignment must include at least one workshift to be bound, {0}.
Category:: Other
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.

ESS-06587: Invalid update of a bound work assignment {0}.
Category:: Other
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.

ESS-06588: Failed to bind the ESS internal work assignment. {0}.
Category:: Other
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.

ESS-06589: Binding the ESS internal work assignment.
Category:: Other
Cause:: The ESS internal work assignment is being bound for a new server.
Action:: No action is necessary.

ESS-06590: Error encountered by the worker for work assignment {0}.
Category:: Other
Cause:: Error encountered by worker for work assignment.
Action:: Review the log file for underlying causes.

ESS-06592: Error while processing request {0} for application {1}.
Category:: Other
Cause:: Error while processing request for application
Action:: Review the log file for underlying causes.

ESS-06593: Required property, {0}, is not present in message received for work assignment {1}.
Category:: Other
Cause:: Required property is not present in message received for work assignment.
Action:: Add the required request property for work assignment.

ESS-06594: Failed to schedule additional work for work assignment {0}. {1}
Category:: Other
Cause:: Failed to schedule additional work for work assignment.
Action:: Review the log file for underlying causes.

ESS-06595: Failed to update request history for request {0}.
Category:: Other
Cause:: Failed to update request history for request.
Action:: Review the log file for underlying causes.

ESS-06610: Failed processing request {0}, {1} stage.
Category:: Other
Cause:: Failed processing request.
Action:: Review the log file for underlying causes.

ESS-06617: Failed to extract event information for event name {0}.
Category:: Other
Cause:: Failed to extract event information for event name.
Action:: Review the log file for underlying causes.

ESS-06618: Error while dispatching event {0}, request {1}, to request listeners.
Category:: Other
Cause:: Error while dispatching event to request listeners.
Action:: Review the log file for underlying causes.

ESS-06620: Failed to get an endpoint for application {0}.
Category:: Other
Cause:: Failed to get an endpoint for application. Endpoint not available for processing.
Action:: Make sure endpoint application is available for processing.

ESS-06621: Error while calling endpoint for application {0}.
Category:: Other
Cause:: Failure encountered while calling endpoint for application.
Action:: Ensure application is deployed and running.

ESS-06622: Error while calling endpoint for application {0}, method {1}.
Category:: Other
Cause:: Error occured while calling endpoint for application.
Action:: Ensure application is deployed and running.

ESS-06630: Error starting work manager work.
Category:: Other
Cause:: An error occurred starting work mananger work.
Action:: None

ESS-06631: Cannot allocate thread. The maximum number of threads has been allocated for this pool: {0}
Category:: Other
Cause:: The maximum threads for a work pool has been reached.
Action:: None

ESS-06632: Cannot allocate thread. The client maximum number of threads has been allocated for this pool: {0}
Category:: Other
Cause:: The client maximum threads for a work pool has been reached.
Action:: None

ESS-06640: Error encountered by worker.
Category:: Other
Cause:: Error encountered by worker.
Action:: Review the log file for underlying causes.

ESS-06641: Failed to schedule additional work. {0}
Category:: Other
Cause:: Failed to schedule additional work.
Action:: Review the log file for underlying causes.

ESS-06645: Specialization is incorrectly formed and invalid for work assignment {0}. {1}
Category:: Other
Cause:: The work assignment specialization is incorrectly formed and invalid.
Action:: Fix the work assignment specialization and try again.

ESS-06646: Exclusive binding requires non-empty specialization, work assignment {0}.
Category:: Other
Cause:: Exclusive binding requires the work assignment specialization is non-empty.
Action:: Define a specialization for the work assignment and try binding it again.

ESS-06647: Exclusive mode is not allowed for {1} scoped binding, work assignment {0}.
Category:: Other
Cause:: Invalid binding mode for binding with the given scope.
Action:: Either bind the work assignment in standard mode or use a different scope (standard or group).

ESS-06700: Failed to check in event work {0} for {1} event, request {2}.
Category:: Other
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.

ESS-06701: Failed to publish request listener event during processing of work {0}. Event: {1}, request: {2}.
Category:: Other
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.

ESS-06710: Unable to dispatch event {0} for request {1} to event listener.
Category:: Other
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.

ESS-06711: Error invoking event listener for request {0}. Event name: {1}, event request: {2}
Category:: Other
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.

ESS-06712: Event listener action for event {0}, request {1}. Status: [{2}], Message: [{3}]
Category:: Other
Cause:: Information from EventListenerAction returned by the listener.
Action:: None

ESS-06713: Delivery limit reached for event {0}, request {1}. No further delivery attempts will be made.
Category:: Other
Cause:: The event has been delivered to the event listener the maximum allowed times.
Action:: None

ESS-06714: Failed to authenticate user {0}. Dispatch event {1} for request {2} as an unprivileged call. Error: [{3}]
Category:: Other
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.

ESS-06750: RequestId {0} with job definition {1} from hosting application {2}, is still in RUNNING state and holding up quiescing of ESS Server!
Category:: Other
Cause:: A job is still running in 2nd stage of ESS Quiesce and holding up ESS server from quiescing.
Action:: Update job logic to ensure it checks server quiesce and exits in time.

ESS-06751: Quiesce state update in Hosting App cache failed for hosting application {0}.
Category:: Other
Cause:: Quiesce state update in Hosting App cache failed for specified hosting app.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06752: ESS instance Quiesce state initialized to retrieved persisted quiesce state = {0}.
Category:: Other
Cause:: ESS instance Quiesce state initialized to retrieved persisted quiesce state.
Action:: No action is necessary.

ESS-06753: No persisted quiesce state found for this instance.
Category:: Other
Cause:: No persisted quiesce state found for this instance.
Action:: No action is necessary.

ESS-06754: Setting instance Quiesce state to {0}.
Category:: Other
Cause:: Setting Quiesce state to specified quiesce state.
Action:: No action is necessary.

ESS-06755: ESS instance is in an incompatible state and cannot transition to {0}.
Category:: Other
Cause:: ESS instance is in an incompatible state and cannot transition to specified quiesce state.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06756: QuiesceESS operation invoked with the following arguments:
Category:: Other
Cause:: QuiesceESS operation invoked with specified args.
Action:: No action is necessary.

ESS-06757: QuiesceESS operation invoked with invalid arguments, ignoring specified quiesce operation.
Category:: Other
Cause:: QuiesceESS operation invoked with invalid argumentss.
Action:: Check quiesceESS operations arguments and correct them.

ESS-06758: Forced UnQuiesce done, as Non-idempotent quiesce operation invoked, with instance in {0} state.
Category:: Other
Cause:: Forced UnQuiesce done, as Non-idempotent quiesce operation invoked, with an active quiesce state.
Action:: No action is necessary.

ESS-06759: Non-idempotent scheduled operation invoked resulting in Quiesce schedule override.
Category:: Other
Cause:: Non-idempotent scheduled operation invoked resulting in Quiesce schedule override.
Action:: No action is necessary.

ESS-06760: UnQuiesceESS operation transitioning instance from {0} state to POST_QUIESCE state.
Category:: Other
Cause:: UnQuiesce operation transitioning instance from specified Quiesce state to POST_QUIESCE state.
Action:: No action is necessary.

ESS-06761: Runtime service exception retrieving request details in Quiesce state.
Category:: Other
Cause:: Runtime service exception encountered retrieving request details in Quiesce state.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06762: Runtime service exception querying for running {0} jobs in Quiesce state.
Category:: Other
Cause:: Runtime service exception querying for running jobs in Quiesce state.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06763: Error retrieving persisted quiesce state or schedule for this instance.
Category:: Other
Cause:: Error retrieving persisted quiesce state or schedule for this instance.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06764: Error persisting quiesce state or schedule for this instance.
Category:: Other
Cause:: Error persisting quiesce state or schedule for this instance.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06765: Error terminating running job for request {0} in second stage of quiesce state.
Category:: Other
Cause:: Error terminating running job in second stage of quiesce state.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06800: Error handling {0} event for request {1} by request dispatcher.
Category:: Other
Cause:: Error handling event for request by request dispatcher.
Action:: Review the log for underlying causes.

ESS-06802: Request {0} is in {1} state. Skipping the processing.
Category:: Other
Cause:
Action:

ESS-06803: Request {0} is in {1} state. Skipping processing and deleting from wait queue.
Category:: Other
Cause:
Action:

ESS-06804: Request {0} has EXPIRED. Skipping processing and deleting from wait queue.
Category:: Other
Cause:
Action:

ESS-06805: Request {0} is in illegal state {1} ({2}). Skipping processing and deleting from wait queue.
Category:: Other
Cause:: Request is in illegal state. Skipping processing and deleting from wait queue.
Action:: Review the log for underlying causes.

ESS-06806: Request {0} not found in runtime store. Skipping processing and deleting from wait queue.
Category:: Other
Cause:: Request not found in runtime store. Skipping processing and deleting from wait queue.
Action:: No Action is necessary.

ESS-06807: Error occurred while dispatching requests.
Category:: Other
Cause:: An error occurred while attempting to dispatch one or more requests.
Action:: Review the log file to determine the nature of the problem.

ESS-06816: Error processing request {0} by request dispatcher.
Category:: Other
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.

ESS-06817: No subrequests exist for paused request {0}. Request execution will be resumed.
Category:: Other
Cause:: No sub-requests are active for this paused request.
Action:: None

ESS-06820: Failed to retrieve Schedule for request {1}.
Category:: Other
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.

ESS-06821: Failed to update error information for request {0}. {1}
Category:: Other
Cause:: Failed to update the error information for a request.
Action:: Review the log file for to determine the nature of the problem.

ESS-06830: Error occurred processing post-execution work for request {0}. WorkId: {1}
Category:: Other
Cause:: An error occurred while processing a post-execution work unit.
Action:: Review the log file to determine the nature of the problem.

ESS-06831: Cannot process post-execution work for request {0}. State is {1}, process phase is {2}. WorkId: {3}
Category:: Other
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

ESS-06832: Failed to publish the metadata change event for {0}, appName={1}. {2}
Category:: Other
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.

ESS-06833: Unrecognized metadata change type {0}, appName={1}, metaId={2}, origServer={3}
Category:: Other
Cause:: Unrecognized metadata change type in metadata change event.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06834: Ignoring change event as metadata cannot be found: {0}, appName={1}. {2}
Category:: Other
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.

ESS-06835: Performing automatic refresh of metadata for request {0}, metadata {1}.
Category:: Other
Cause:: Metadata used by the request has changed and is being automatically refreshed.
Action:: No action is required.

ESS-06836: Changes to metadata prevent automatic refresh for request {0}, metadata {1}.
Category:: Other
Cause:: Metadata used by the request has changed but cannot be refreshed because the changes are not allowed for automatic refresh.
Action:: No action is required. For automatic refresh, only customizable parameters may have been changed.

ESS-06837: Unable to refresh job metadata at this time for request {0}.
Category:: Other
Cause:: Temporarily unable to refresh changed metadata for the request.
Action:: No action is required. The request may be refreshed in the future.

ESS-06838: Unable to access metadata in runtime store for request {0}, metadata {1}.
Category:: Other
Cause:: Unable to access cached metadata for the request.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06839: Metadata already exists in runtime store for request {0}, metadata {1}.
Category:: Other
Cause:: The metadata already exists in the cache in the runtime store for the request.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06840: Failed to insert metadata change notification for application {0}, change type {1}, metadata id {2}.
Category:: Other
Cause:: Failed to add the metadata change notification to the runtime store.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06841: Failed to insert metadata change notification for application {0}, change type {1}, metadata id {2}.
Category:: Other
Cause:: Failed to add the metadata change notification to the runtime store.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06842: Unable to access metadata change notifications.
Category:: Other
Cause:: Unable to access metadata change notifications.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-06843: Unable to determine the logical application name for deployed application ''{0}''.
Category:: Other
Cause:: Unable to determine the logical application that should be used for a metadata change notification.
Action:: Review the log file for information to determine the nature of the problem, and ensure the logical application name is defined.

ESS-06844: Failed to remove parameter {0} for request {1}.
Category:: Other
Cause:: Unable to remove the parameter for the request during a metadata refresh.
Action:: Review the log file for information to determine the nature of the problem.

ESS-06845: Failed to remove the read-only constraint for parameter {0}, request {1}.
Category:: Other
Cause:: Unable to remove the read-only constraint for the request parameter during a metadata refresh.
Action:: Review the log file for information to determine the nature of the problem.

ESS-06846: Parameter ''{0}'' is now read only for request {1}. Previous update is discarded.
Category:: Other
Cause:: Due to a metadata refresh, the parameter is now read-only. The parameter had been updated previously, and that update has been discarded.
Action:: No action is required.

ESS-06847: Failed to remove runtime metadata for request {0}.
Category:: Other
Cause:: Unable to remove cached runtime metadata for the request.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-07000: Error handling {0} event for request {1} by request processor.
Category:: Other
Cause:: Error handling event for request by request processor.
Action:: Review the log file for underlying causes.

ESS-07001: Error processing request {0}.
Category:: Other
Cause:: Error processing request.
Action:: Review the log file for underlying causes.

ESS-07002: Failed to obtain system executable wrapper for request {0}.
Category:: Installation
Cause:: Possible causes include unknown job type, user login error, classloading issues...
Action:: Review the causeBy exception clause to determine the specific failure.

ESS-07003: Execution warning for request {0}. Reason: {1}
Category:: Other
Cause:: Execution error warning for request.
Action:: Review the log file for underlying causes.

ESS-07004: Execution error for request {0}. Reason: {1}
Category:: Other
Cause:: Execution error for request.
Action:: Review the log file for underlying causes.

ESS-07005: Execution cancelled for request {0}. Reason: {1}
Category:: Other
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.

ESS-07006: Failed to cancel request {0}.
Category:: Other
Cause:: Failed to cancel request.
Action:: Review the log file for underlying causes.

ESS-07012: Invalid action ({0}) returned from pre-process callout for request {1}. Setting to {2} state.
Category:: Other
Cause:: Invalid action returned from pre-process callout for the request.
Action:: Review the log for underlying causes.

ESS-07013: Invalid action ({0}) returned from post-process callout for request {1}. Setting to {2} state.
Category:: Other
Cause:: Invalid action returned from pre-process callout for the request.
Action:: Review the log for underlying causes.

ESS-07014: Delaying processing of request {0} by {1} minutes.
Category:: Other
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.

ESS-07015: Error occurred during cleanup of database job for request {0}.
Category:: Other
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.

ESS-07016: Failed processing update event for request {0}.
Category:: Other
Cause:: An error occurred processing an update event.
Action:: Contact Oracle Support Services

ESS-07017: Cannot process update event for request {0} in state {1}.
Category:: Other
Cause:: The request is in an illegal state for an update event.
Action:: None

ESS-07018: Cannot process update event for request {0} in state {1}.
Category:: Other
Cause:: The request is in an illegal state for an update event.
Action:: None

ESS-07019: Error processing request {0}. {1}
Category:: Other
Cause:: Error processing request.
Action:: Review the log file for underlying causes.

ESS-07020: Failed get an endpoint for application {0}.
Category:: Other
Cause:: Failed get an endpoint for application.
Action:: No action is necessary.

ESS-07021: Invalid work unit action for request {0}, work unit {1}, action {2}.
Category:: Other
Cause:: Invalid work unit action for request.
Action:: Report the failure to Oracle support as it could be a bug in ESS.

ESS-07022: Invalid endpoint action for request {0}, stage {1}, action {2}.
Category:: Other
Cause:: Invalid endpoint action for request.
Action:: Report the failure to oracle support.

ESS-07023: Error processing timed out requests. {0}.
Category:: Other
Cause:: An error occurred attempting to process a timed out request.
Action:: None

ESS-07024: Rejecting update event for request {0}. {1}. Result status = {2}. Result message = {3}. Message body = {4}.
Category:: Other
Cause:: The request is in an illegal state for an update event.
Action:: None

ESS-07025: Failed to allocate an asynchronous worker for request {0}. ({1}, {2}). ExecutionType = {3}.
Category:: Other
Cause:: Failed to allocate an asynchronous worker.
Action:: None

ESS-07026: Failed to release an asynchronous worker for request {0}. ({1}, {2}). ExecutionType = {3}.
Category:: Other
Cause:: Failed to release an asynchronous worker.
Action:: None

ESS-07027: Failed to terminate request {0}.
Category:: Other
Cause:: Failed to terminate request.
Action:: Review the log file for underlying causes.n

ESS-07028: Error invoking or executing application endpoint for request {0}. Check application status of logical application {1}.
Category:: Other
Cause:: An error occurred invoking a method on the endpoint of this application.
Action:: Check that the application is deployed and running successfully.

ESS-07029: Asynchronous throttle configuration does not exist for Workshift = {0}.
Category:: Other
Cause:: The async throttle configuration does not exist for the workshift.
Action:: Contact Oracle Support Services

ESS-07030: Recovering update work unit {0} for request {1} that may have been executing. There is a possibility of redelivery.
Category:: Other
Cause:: An update event is being recovered from a stage where redelivery is possible.
Action:: None

ESS-07031: Error in transaction processing for request {0}. The transaction is eligible to be retried
Category:: Other
Cause:: A recoverable SQL error was encountered
Action:: None

ESS-07032: Work unit execution attempt, {0}, does not match request execution attempt, {1}, for request {2}.
Category:: Other
Cause:: The current work unit is for an older request execution attempt
Action:: None

ESS-07033: Job logic indicated a system error occurred while executing an asynchronous java job for request {0}. Job error is: {1}.
Category:: Other
Cause:: The job indicated that an error occurred
Action:: Examine the innermost exception, if present, for the cause

ESS-07034: Job logic indicated a business error occurred while executing an asynchronous java job for request {0}. Job error is: {1}.
Category:: Other
Cause:: The job indicated that a business error occurred
Action:: Examine the innermost exception, if present, for the cause

ESS-07035: Job logic indicated a warning occurred while executing an asynchronous java job for request {0}. Job warning is: {1}.
Category:: Other
Cause:: The job indicated that a warning occurred
Action:: Examine the innermost exception, if present, for the cause

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}).
Category:: Other
Cause:: The request needed to be recovered because of a system error, but cannot be recovered safely
Action:: None

ESS-07037: Error performing substitutions for request {0}
Category:: Other
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.

ESS-07038: Failed to initialize job context extensions for request {0} at stage {1}
Category:: Other
Cause:: An error occurred while initializing job context extensions.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-07039: Failed to cleanup job context for request {0} at stage {1}
Category:: Other
Cause:: An error occurred while cleaning job context extensions.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-07040: Failed to terminate job context for request {0}
Category:: Other
Cause:: An error occurred while terminating job context extensions.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-07041: Failed to retrieve alternate environment for application {0}
Category:: Other
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.

ESS-07042: Expected class {0} not available for request mode {1}
Category:: Other
Cause:: An error instantiating an extensions class.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-07043: Failed to get platform request file directory for request {0}
Category:: Other
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.

ESS-07044: Failed to instantiate EJB job request {0}
Category:: Other
Cause:: Failed to instantiate RemoteExecutable object for a EJB request.
Action:: Make sure the bean implements RemoteExecutable and the parameters JNDI_MAPPED_NAME, JNDI_PROVIDER_URL are specified in job definition.

ESS-07045: Failed to execute EJB job request {0}. Reason: {1}
Category:: Other
Cause:: Failed to execute RemoteExecutable object for a EJB request.
Action:: Review the log file for attached exceptions to determine the nature of the problem.

ESS-07046: Failed to cancel EJB job request {0}
Category:: Other
Cause:: Failed to cancel RemoteCancellableExecutable object for a EJB request.
Action:: Review the log file for attached exceptions to determine the nature of the problem. Make sure the EJB implement RemoteCancellableExecutable interface.

ESS-07047: Metadata parameter {0} not specified in job definition for request {1}.
Category:: Other
Cause:: Validation failed for EJB request. One or more mandatory parameters of EJB job not set.
Action:: Make sure the mandatory parameters are specified in job definition.

ESS-07048: Error while retrieving credentials for CSF Key {0} while processing request {1}.
Category:: Other
Cause:: Error while retrieving CSF credentials. The configuration is either null or invalid.
Action:: Make sure the CSF configuration is proper.

ESS-07049: Error while retrieving Ess Configuration for application {0} while processing request {1}.
Category:: Other
Cause:: Error while retrieving values of EssConfiguration . The configuration is either null or invalid.
Action:: Make sure the configuration is proper.

ESS-07050: Refreshing runtime incompatibilities for request {0}.
Category:: Other
Cause:: Refreshing runtime incompatibilities for the request.
Action:: No action is required.

ESS-07060: Invalid work unit action {0} for work unit {1}.
Category:: Other
Cause:: Invalid work unit action.
Action:: Report the failure to Oracle support as it could be a bug in ESS.

ESS-07061: An error occurred initiating processing of an update work unit for request {0}.The incoming asynchronous status is {1}.Error message: [{2}] {3}
Category:: Other
Cause:: The asynchronous java job callback to update the status could not be processed.
Action:: Examine error message

ESS-07200: Invalid workDirectory specified for spawned job request {0}: {1} does not exist.
Category:: Other
Cause:: Invalid workDirectory specified for spawned job request {0}: {1} does not exist.
Action:: Ensure requestFileDirectory configured and a valid workDirectory specified for request.

ESS-07201: Error launching spawnAgent for spawned job request {0}.
Category:: Other
Cause:: Error launching spawnAgent for spawned job request {0}.
Action:: Review log file for nested IOexception and resolve the issue.

ESS-07202: Error opening Output stream to spawnAgent for spawned job request {0}.
Category:: Other
Cause:: Error opening Output stream to spawnAgent for spawned job request {0}.
Action:: Review log file for nested IOexception and resolve the issue.

ESS-07203: spawnAgent terminated at launch for spawned job request {0}.
Category:: Other
Cause:: spawnAgent terminated at launch for spawned job request {0}.
Action:: Enable Agent log to find cause and resolve.

ESS-07204: spawnAgent cannot spawn process for spawned job request {0} with command line: {1}. Cause={2}
Category:: Other
Cause:: spawnAgent cannot spawn process for spawned job request {0} with cmdline: {1}. Cause={2}.
Action:: Check error cause and update spawned job definition.

ESS-07205: spawnAgent terminated before completion of spawned process for spawned job request {0} with command line: {1}.
Category:: Other
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.

ESS-07206: Error waiting for completion of spawned job request {0} with command line: {1}.
Category:: Other
Cause:: Error waiting for completion of spawned job request {0} with cmdline: {1}.
Action:: Review log file for nested IOexception and resolve the issue.

ESS-07207: Invalid Exit Code returned by spawned process for spawned job request {0} with command line: {1}.
Category:: Other
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.

ESS-07208: Error during post-completion cleanup for spawned job request {0} with command line: {1}.
Category:: Other
Cause:: Error during post-completion cleanup for spawned job request {0} with cmdline: {1}.
Action:: Review log file for nested exception and resolve.

ESS-07209: Error retrieving DomainConfigDirectory using JRF ServerPlatformSupportFactory API.
Category:: Other
Cause:: Error retrieving DomainConfigDirectory using JRF ServerPlatformSupportFactory API.
Action:: Review log file for nested exception and resolve.

ESS-07210: Error registering shutdown hook for spawned job request {0}.
Category:: Other
Cause:: Error registering shutdown hook for spawned job request {0}.
Action:: Review log file for nested exception and resolve.

ESS-07211: Error deregistering shutdown hook for spawned job request {0}.
Category:: Other
Cause:: Error deregistering shutdown hook for spawned job request {0}.
Action:: Review log file for nested exception and resolve.

ESS-07212: Error updating processId for spawned job request {0}.
Category:: Other
Cause:: Error updating processId for spawned job request {0}.
Action:: Review log file for nested exception and resolve.

ESS-07213: Using Perl SpawnAgent {1} with perl interpreter at {2} for spawned job request {0}.
Category:: Other
Cause:: Using Perl SpawnAgent {1} with perl interpreter at {2} for spawned job request {0}.
Action:: None

ESS-07214: Error locating Perl spawnAgent script for spawned job request {0}.
Category:: Other
Cause:: Error locating Perl SpawnAgent script for spawned job request {0}.
Action:: Contact Administrator.

ESS-07215: Error locating Perl interpreter for spawned job request {0}.
Category:: Other
Cause:: Error locating Perl interpreter for spawned job request {0}.
Action:: Contact Administrator.

ESS-07216: Using Java SpawnAgent from {1} for spawned job request {0}.
Category:: Other
Cause:: Using Java SpawnAgent from {1} for spawned job request {0}.
Action:: None

ESS-07217: Error retrieving SpawnAgent configuration.
Category:: Other
Cause:: Error retrieving SpawnAgent configuration.
Action:: Review log file for nested exception. Contact Administrator.

ESS-07218: Unable to locate Perl interpreter from FusionApps WebTier location.
Category:: Other
Cause:: Unable to locate Perl interpreter from FusionApps WebTier location.
Action:: None

ESS-07300: Invalid WebServiceJobDefinition for request {0}, {1} property value is invalid.
Category:: Other
Cause:: Invalid WebServiceJob Definition: identified property value is invalid.
Action:: Specify a valid value for the identified property in WebServiceJobDefinition.

ESS-07301: Post-substitution WebService INVOKE_MESSAGE for request {0}: {1}
Category:: Other
Cause:: PostSubstitution WebService Invoke Message.
Action:: None

ESS-07302: WebService INVOKE_MESSAGE Substitution Error for request {0}.
Category:: Other
Cause:: Substitution error while processing WebService INVOKE_MESSAGE.
Action:: Specify a valid xml for INVOKE_MESSAGE property in WebServiceJobDefinition.

ESS-07303: WebService WSDL URL Substitution Error for request {0}.
Category:: Other
Cause:: Substitution error while processing WebService Wsdl URL.
Action:: Review WS_WSDL_URL property value in WebServiceJobDefinition.

ESS-07304: WebService WSDL URL Retrieval Error for request {0}.
Category:: Other
Cause:: Error retrieving WebService Wsdl from substituted URL.
Action:: Review WS_WSDL_URL property value in WebServiceJobDefinition.

ESS-07305: Invalid WebService Endpoint URL for request {0} in wsdl retrieved from {1}.
Category:: Other
Cause:: Invalid WebService Endpoint URL in retrieved wsdl.
Action:: Review WS_WSDL_URL property value in JobDefinition and Endpoint URL value in specified wsdl.

ESS-07306: WS_SECURITY_OPTION property not specified OR Invalid WS_SECURITY_OPTION property value in WebServiceJob JobDefinition for request {0}.
Category:: Other
Cause:: WS_SECURITY_OPTION property not specified OR Invalid WS_SECURITY_OPTION property value in WebServiceJobDefinition.
Action:: Review WS_SECURITY_OPTION property value in JobDefinition, if specified.

ESS-07307: WS_HTTP_BASIC_AUTH_CSF_KEY not configured in JobDefinition for request {0}.
Category:: Other
Cause:: WS_HTTP_BASIC_AUTH_CSF_KEY not configured in WebServiceJob Definition.
Action:: Specify a valid CSF key for WS_HTTP_BASIC_AUTH_CSF_KEY property in WebServiceJobDefinition.

ESS-07308: Error using JRF PortConfig API to determine ESS WebService URL Prefix.
Category:: Other
Cause:: Error using JRF PortConfig API to determine ESS WebService URL Prefix.
Action:: JRF Portability issue. Contact Administrator.

ESS-07309: Computed WebService Callback URL for Async WebServiceJob: {0}.
Category:: Other
Cause:: Computed WebService Callback URL.
Action:: None

ESS-07310: Error invoking webservice operation {1} for request {0}.
Category:: Other
Cause:: Error invoking webservice operation.
Action:: Review log file for attached exception and update JobDefinition.

ESS-07311: WebService operation {1} for request {0} results in SOAPFault with FaultCode={2} and FaultString={3}.
Category:: Other
Cause:: Invoking webservice operation results in a SOAPFault.
Action:: Review SOAPFault and update WebService JobDefinition properties.

ESS-07312: Error saving WebService operation messageId for request {0}.
Category:: Other
Cause:: Error saving WebService operation messageId.
Action:: Review log file for attached exception.

ESS-07313: Error retrieving WebService operation messageId for request {0}.
Category:: Other
Cause:: Error retrieving WebService operation messageId.
Action:: Review log file for attached exception.

ESS-07314: WebService operation for request {0} cannot be cancelled as Cancel Operation properties not specified in WebServiceJobDefinition.
Category:: Other
Cause:: WebService operation for request cannot be cancelled as Cancel operation properties not specified in WebServiceJobDefinition.
Action:: Review Cancel operation properties in WebServiceJobDefinition.

ESS-07315: WebService operation for request {0} cannot be cancelled, as Cancel message specified in WebServiceJobDefinition is invalid.
Category:: Other
Cause:: WebService operation for request cannot be cancelled as Cancel message specified in WebServiceJobDefinition is invalid.
Action:: Review Cancel operation properties in WebServiceJobDefinition.

ESS-07316: WebService WS_CANCEL_MESSAGE Substitution Error for request {0}.
Category:: Other
Cause:: Substitution error while processing WebService Cancel message.
Action:: Review WS_CANCEL_MESSAGE property in WebServiceJobDefinition.

ESS-07317: Error invoking webservice Cancel operation {1} for request {0}.
Category:: Other
Cause:: Error Cancelling webservice operation.
Action:: Review log file for attached exception and update Cancel operation properties in JobDefinition.

ESS-07318: WebService Cancel operation {1} for request {0} results in SOAPFault with FaultCode={2} and FaultString={3}.
Category:: Other
Cause:: Invoking webservice Cancel operation results in a SOAPFault.
Action:: Review SOAPFault and update WebService JobDefinition properties.

ESS-07319: Error retrieving webservice SOAPResponse payload for request {0}.
Category:: Other
Cause:: Error retrieving webservice SOAPResponse payload.
Action:: Review log file for attached exception and and update WebService JobDefinition properties.

ESS-07320: Error capturing webservice response as Job Output for request {0}.
Category:: Other
Cause:: Error capturing webservice response as Job Output.
Action:: Review log file for attached exception.

ESS-07321: WebService Job Output for request {0}: {1}.
Category:: Other
Cause:: WebServiceJob Output.
Action:: None

ESS-07322: Error retrieving credentials from CredentialStore using CSF key {0}.
Category:: Other
Cause:: Error retrieving CSF Credentials from CredentialStore.
Action:: Review CSF key in WebServiceJobDefinition.

ESS-07323: No base URL is specified for relative URL {0} = {1} for request {2}.
Category:: Other
Cause:: A required base URL was not specified for the given relative URL
Action:: Specify the corresponding base URL as an ESS system property or in the application configuration.

ESS-07324: Error retrieving WebService JobDefinition for request {0}.
Category:: Other
Cause:: Error retrieving WebService JobDefinition for request {0}.
Action:: Review log file for attached exception.

ESS-07325: Error retrieving wsa:relatesTo addresssing header from callback message using DISI ServiceRequestTransport.
Category:: Other
Cause:: Error retrieving wsa:relatesTo addresssing header from callback message using DISI ServiceRequestTransport.
Action:: Review log file for attached exception.

ESS-07326: Invalid SOAP response message, error processing message by WebServiceJob Callback servlet.
Category:: Other
Cause:: Invalid SOAP response message, error processing message by WebServiceJob Callback servlet.
Action:: Review log file for attached exception. Verify async callback message is a valid SOAP response

ESS-07327: Error processing WebServiceJob callback response in ServiceResponseTransport.
Category:: Other
Cause:: Error processing WebServiceJob callback response in ServiceResponseTransport.
Action:: Review log file for attached exception.

ESS-07328: Error processing WebServiceJob callback message in ProviderRequest.
Category:: Other
Cause:: Error processing WebServiceJob callback message in ProviderRequest.
Action:: Review log file for attached exception.

ESS-07329: WebServiceJob Progress message not permitted for request {0}.
Category:: Other
Cause:: WebServiceJob Progress message not permitted for request {0}.
Action:: Review WebServiceJob progress message usage recommendations.

ESS-07332: Error registering Policy Assembly {0} with OWSM.
Category:: Other
Cause:: Error registering Policy Assembly {0} with OWSM.
Action:: Review PolicyAssembly ResourcePattern.

ESS-07360: EssPolicyManager instance lookup attempted passing a NULL PolicyContext.
Category:: Other
Cause:: EssPolicyManager instance lookup attempted passing a NULL PolicyContext
Action:: Review log file for details. Contact administrator.

ESS-07361: EssPolicyManager instance lookup attempted passing empty or NULL application name.
Category:: Other
Cause:: EssPolicyManager instance lookup attempted passing empty or NULL application name
Action:: Review log file for details. Contact administrator.

ESS-07362: Error publishing WsmPolicyUpdateEvent for application {0}.
Category:: Other
Cause:: Error publishing WsmPolicyUpdateEvent for application {0}.
Action:: Review log file and contact Administrator.

ESS-07364: Error deregistering Policy Assembly {0} with OWSM.
Category:: Other
Cause:: Error deregistering Policy Assembly {0} with OWSM.
Action:: Review PolicyAssembly ResourcePattern.

ESS-07365: Error creating Policy Assembly for request {0}.
Category:: Other
Cause:: Error creating Policy Assembly for request {0}.
Action:: Review log file for attached exception.

ESS-07366: Error retrieving Policy Assembly for job definition {0}.
Category:: Other
Cause:: Error retrieving Policy Assembly for job definition {0}.
Action:: Review log file for attached exception.

ESS-07367: Error validating {0} Policy Subject registration with OWSM Policy Access Point for request {1}.
Category:: Other
Cause:: Error validating {0} Policy Subject registration with OWSM Policy Access Point for request {1}.
Action:: Review log file for owsm . Contact Administrator.

ESS-07500: Error parsing attribute {0}. {1}
Category:: Other
Cause:: An error is present in a command attribute format.
Action:: Contact Oracle Support Services.

ESS-07501: Error starting command worker.
Category:: Other
Cause:: An error occurred starting a command worker.
Action:: None

ESS-07502: Failed to set request state to VALIDATION_FAILED for request {0}. {1}
Category:: Other
Cause:: An error occurred while setting the state of the request to VALIDATION_FAILED.
Action:: None

ESS-07503: Document conversion failed for command work {0}. Command type: {1}, request: {2}.
Category:: Other
Cause:: Failed converting DOC Document for command work.
Action:: None

ESS-07505: Validation of request {0} failed.
Category:: Other
Cause:: Validation of the request has failed.
Action:: Check logs and error information for details.

ESS-07506: Failed to check in command work {0} for {1} command, request {2}.
Category:: Other
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.

ESS-07507: Unknown command type, {0}, for command work {1}.
Category:: Other
Cause:: The command work has an unknown commad type.
Action:: None

ESS-07508: Error calling endpoint for application {0} during processing of {1} command for request {2}.
Category:: Other
Cause:: The command work has an unknown commad type.
Action:: None

ESS-07509: Failed to execute command {0} for request {1} for command work {2}.
Category:: Other
Cause:: An error occurred executing the command.
Action:: Review the log file for the cause.

ESS-07510: Failed to update command {0} for request {1} for command work {2}.
Category:: Other
Cause:: An error occurred updating the command.
Action:: Review the log file for the cause.

ESS-07540: Failed to complete request {0} during group cleanup for execution group {1}, isolation group {2}.
Category:: Other
Cause:: Clean up of request failed during execution group removal.
Action:: None. The action will be automatically retried.

ESS-07541: Failed to get list of incomplete requests for execution group {0}, isolation group {1}.
Category:: Other
Cause:: Retrieving requests during execution group removal failed.
Action:: None. The action will be automatically retried.

ESS-07542: Failed to remove registrations for execution group {0}, isolation group{1}.
Category:: Other
Cause:: Removing instance or application registrations failed during execution group removal.
Action:: None. The action will be automatically retried.

ESS-07543: Failed to lock recovery delete table.
Category:: Other
Cause:: Failed to lock the recovery delete table.
Action:: None. The action will be automatically retried.

ESS-07544: Failed to insert row for process group {0}, isolation group {1}, action {2}.
Category:: Other
Cause:: Failed to insert the entry into recovery delete table.
Action:: None. The action will be automatically retried.

ESS-07545: Failed to delete row for process group {0}, isolation group {1}, action {2}.
Category:: Other
Cause:: Failed to delete the entry from recovery delete table.
Action:: None. The action will be automatically retried.

ESS-07546: Failed to query row for process group {0}, isolation group {1}, action {2}.
Category:: Other
Cause:: Failed to query for the entry from recovery delete table.
Action:: None. The action will be automatically retried.

ESS-07552: Failed to insert configuration for application {0} in process group {1}.
Category:: Other
Cause:: Failed to insert the entry from essconfig table.
Action:: None.

ESS-07553: Failed to delete configuration for application {0} in process group {1}.
Category:: Other
Cause:: Failed to delete the entry from essconfig table.
Action:: None.

ESS-07554: Failed to update configuration for application {0} in process group {1}.
Category:: Other
Cause:: Failed to update the configuration for the given application.
Action:: None.

ESS-07555: Failed to query configuration for application {0} in process group {1}.
Category:: Other
Cause:: Failed to query the entry from essconfig table.
Action:: None.

ESS-07556: Failed to find configuration for application {0} in process group {1}.
Category:: Other
Cause:: The configuration for the given application could not be found
Action:: Check if the ESS logical application name is correct and that it is deployed to the current cluster.

ESS-07557: Configuration exists for application {0} in process group {1}.
Category:: Other
Cause:: Configuration is already present for the given application.
Action:: None.

ESS-07558: Failed to convert {2} for application {0} in process group {1}.
Category:: Other
Cause:: Conversion for an EssConfig or Customization object failed
Action:: None.

ESS-07559: Property {0} is immutable defined in the base application.
Category:: Other
Cause:: The given application configuration property is immutable and cannot be customized.
Action:: None.

ESS-07560: Property {0} is immutable.
Category:: Other
Cause:: The given application configuration property is immutable and cannot be customized.
Action:: None.

ESS-07561: Property name {0} is a reserved ESS property name.
Category:: Other
Cause:: The given application configuration property name is a reserved name.
Action:: None.

ESS-07562: Property {0} has been defined. An update operation should be used.
Category:: Other
Cause:: The given application configuration property has been defined.
Action:: Use update operation to customize the property.

ESS-07563: Failed to insert configuration for server {0} in process group {1}.
Category:: Other
Cause:: Failed to insert the entry into the server configuration table.
Action:: None.

ESS-07564: Failed to delete configurations in process group {0}.
Category:: Other
Cause:: Failed to delete the entry from server configuration table.
Action:: None.

ESS-07565: Failed to update configuration for server {0} in process group {1}.
Category:: Other
Cause:: Failed to update the configuration for the given server.
Action:: None.

ESS-07566: Failed to query configuration for server {0} in process group {1}.
Category:: Other
Cause:: Failed to query the entry from ess server config table.
Action:: None.

ESS-07567: Failed to find configuration for server {0} in process group {1}.
Category:: Other
Cause:: The configuration for the given server could not be found.
Action:: None.

ESS-07568: Configuration already exists for server {0} in process group {1}.
Category:: Other
Cause:: Configuration is already present for the given server name.
Action:: None.

ESS-07569: An error occurred while updating the Scheduler server configuration for server {0} in process group {1}.
Category:: Other
Cause:: An error occurred updating the ESS server configuration.
Action:: None.

ESS-07575: Error inserting wiring {0} with value {1} for group {2}.
Category:: Other
Cause:: Failed to store cross component wiring information.
Action:: None.

ESS-07576: Error retrieving wiring {0} from group {1}.
Category:: Other
Cause:: An error occurred retrieving cross component wiring information from the runtime store.
Action:: None.

ESS-07577: Error deleting all entries in wirings table.
Category:: Other
Cause:: An error occurred deleting cross component wiring information from the runtime store.
Action:: None.

ESS-07578: Failed to register listener for CCW configuration.
Category:: Other
Cause:: The cross component wiring configuration listener could not be registered.
Action:: Review the log file for the cause.

ESS-07579: Failed to unregister listener for CCW configuration.
Category:: Other
Cause:: The cross component wiring configuration listener could not be registered.
Action:: Review the log file for the cause.

ESS-07580: Cross component wiring configuration listener failed to process document change event.
Category:: Other
Cause:: An error occurred processing the notification from the ESS CCW configuration.
Action:: Review the log file for the cause.

ESS-07581: Failed to delete wirings for URNs {0} from group {1}.
Category:: Other
Cause:: An error occurred deleting cross component wiring information from the runtime store.
Action:: None.

ESS-07582: A logical cluster name must be specified for cross-component wiring enabled jobs. Parameter {0} for request {1} has substitution prefix WIRING.
Category:: Other
Cause:: The WIRING substitution prefix was used for a job without a logical cluster name.
Action:: Either specify a logical cluster name for the job or explicitly specify the property value.

ESS-07614: null
Category:: Programmatic
Cause:: Ranks are applicable only for requests of state WAIT and READY.
Action:: Specify a request in WAIT or READY state.

ESS-07701: {0} property must be positive and not null for request {1}.
Category:: Other
Cause:: Processed count or failed count property is negetive or null.
Action:: Provide valid values for Processed count or failed count property.

ESS-07702: {0} property must not be null or empty for request {1}.
Category:: Other
Cause:: Job Monitoring property is empty or null.
Action:: Provide valid values for Job monitoring property.

ESS-07703: Number of counters are limited to 5 per job for request {0}
Category:: Other
Cause:: Number of counters are limited to 5 per job.
Action:: Provide valid Counter number between 1 to 5.

ESS-07704: Counters have not been initialized for counter number {0} for request {1}.
Category:: Other
Cause:: Job Monitoring counter property are not initialized.
Action:: Job Monitoring counter property should be initialized before updating them.

ESS-07705: Counter name property can be initialized only once and have already been initialized with different value for counter number {0} for request {1}.
Category:: Other
Cause:: Counter Name property is already initialized with a different value.
Action:: Provide a valid counter name property.

ESS-07706: Total count property is not valid for counter number {0} for request {1}.
Category:: Other
Cause:: Total count property is not valid.
Action:: Provide a valid value for Total count.

ESS-07707: RuntimeService is null.
Category:: Other
Cause:: The ESS runtime service is null.
Action:: Provide a valid ESS runtime service.

ESS-07708: An unknown or unsupported state is specified: {0}.
Category:: Other
Cause:: An unknown or unsupported state is specified.
Action:: Provide a valid supported state.

ESS-07709: Job Monitoring counters cannot be initialized or updated as request {0} is already in {1} state.
Category:: Other
Cause:: Job Monitoring counter property cannot be initialized or updated as request has been cancelled.
Action:: Job Monitoring status updates not permitted when job has been cancelled.

ESS-07710: Total count property can not be updated. It has already been initialized for counter number {0} for request {1}.
Category:: Other
Cause:: Total count property is already initialized.
Action:: Total count property can't be updated once initialized.

ESS-07711: Job Monitoring message string is either with invalid format or counter information for request {0}. String Format: apiName=xxxx,counterNumber=xxxx,counterName=xxxx,totalCount=xxxx,processedCount=xxxx,failedCount=xxxx,counterKey=xxxx,enableJobCancelDetection=xxxx, where xxxx represents counter information.
Category:: Other
Cause:: Job monitor message string is either with invalid format or counter information. Format: apiName=xxxx,counterNumber=xxxx,counterName=xxxx,totalCount=xxxx,processedCount=xxxx,failedCount=xxxx, where xxxx represents counter information.
Action:: Correct the invalid job monitor message string.

ESS-07712: Job monitoring counter property {0} is not supported for this operation.
Category:: Other
Cause:: Job Monitoring Counter property is not supported for this operation.
Action:: Provide valid Job Monitoring counter property..

ESS-07713: A resource bundle is already registered and cannot be updated or reset for the request {0}.
Category:: Other
Cause:: A resource bundle is already registered for the request and cannot be updated or reset.
Action:: Resource bundle MUST be the same which is registered with this request.

ESS-08000: The value of filter is null.
Category:: Other
Cause:: The value of filter is null
Action:: Provide the correct privilege name.

ESS-08001: Invalid sec filter comparator.
Category:: Other
Cause:: Invalid sec filter comparator.
Action:: Choose correct comparator, GRANTED.

ESS-08002: Invalid value passed to ''name'' of RuntimeDataPermission: {0}. Please check the server logs.
Category:: Other
Cause:: Invalid value passed to 'name' of RuntimeDataPermission
Action:: Provide the correct permission name.

ESS-08003: Unsupported query field {0} specified in RuntimeDataPermission name Please check the server logs.
Category:: Other
Cause:: Unsupported query field name passed to 'name' of RuntimeDataPermission
Action:: Provide a valid queryField in permission name.

ESS-09000: Translation service with resource bundles {0} for Locale {1} can not be performed due to runtime error.
Category:: Programmatic
Cause:: ESS runtime encountered a failure for the given translation request.
Action:: Correct the bundle id, make sure it exists in the application environement.

ESS-09001: Message with requested key {0} is not found in the associated resource bundles.
Category:: Programmatic
Cause:: Message with the requested key is not found in the resource bundle.
Action:: Make sure the key is entered correctly.

ESS-09002: {0} is not a valid {1} implementation.
Category:: Programmatic
Cause:: The implementation class is not of expected interface type.
Action:: Make sure the implementation class implements the proper interface.

ESS-09003: Failed to instantiate the translation service factory implementation {0}.
Category:: Programmatic
Cause:: Error while instantiating an instance of translation service factory.
Action:: Check the log to find exception details.

ESS-09004: Failed to retrieve a valid instance of underlying oracle.javatools ResourceBundleManager. Design time metadata translation is not supported.
Category:: Programmatic
Cause:: Error while instantiating an instance of oracle.javatools.resourcebundle.ResourceBundleManager.
Action:: None

ESS-09005: Encountered MDS exception while performing MDS operations.
Category:: Programmatic
Cause:: Encountered MDS exception.
Action:: Check the exception for details.

ESS-09400: Encountered an execution context exception.
Category:: Programmatic
Cause:: Encountered exception while invoking DMS execution context API(s).
Action:: Check exception stack trace for details.

ESS-09402: Failed to compile recurrence expression.
Category:: Programmatic
Cause:: Failed to compile recurrence expression
Action:: Correct the invalid recurrence expression.

ESS-09403: Schedule list limit must be a non-negative integer.
Category:: Programmatic
Cause:: Schedule List limit is invalid.
Action:: List limit must be a non-negative integer.

ESS-09404: Schedule list begin date cannot be null.
Category:: Programmatic
Cause:: Invalid Null Schedule Begin date.
Action:: Provide a non-null begin date for the schedule.

ESS-09405: Schedule begin date can not be after end date.
Category:: Programmatic
Cause:: Begin Date for the schedule is after the end date.
Action:: Correct the invalid begin date or end date.

ESS-09406: Parsing exception. Only one day type recurrence field may be specified.
Category:: Programmatic
Cause:: More than one of BYDAY, BYMONTHDAY, BYYEARDAY was specified
Action:: Correct the invalid recurrence.

ESS-09407: Parsing exception. An occurrence by week number can only be used with a yearly frequency.
Category:: Programmatic
Cause:: A BYWEEKNO clause was specified with a frequency other than YEARLY
Action:: Correct the invalid recurrence.

ESS-09408: Parsing exception. An occurrence by week number cannot be used with an occurrence by month.
Category:: Programmatic
Cause:: More than one of BYWEEKNO, BYMONTH was specified
Action:: Correct the invalid recurrence.

ESS-09409: Parsing exception. Recurrence expression with {0} clause is not supported.
Category:: Programmatic
Cause:: One of the recurrence rule BYSETPOS, UNTIL, COUNT, WKST was specified
Action:: Correct the unsupported Recurrence Expression.

ESS-09410: Parsing exception. Value for {0} clause is out of range.
Category:: Programmatic
Cause:: Out of range value for recurrence rule was specified
Action:: Correct the invalid recurrence.

ESS-09411: Parsing exception. {0} clause is redundant in the recurrence expression.
Category:: Programmatic
Cause:: Redundant recurrence rule was specified
Action:: Correct the invalid recurrence.

ESS-09412: Recurrence expression is not valid. Please verify clauses and that each clause, including the last one, is followed by a semicolon.
Category:: Programmatic
Cause:: Invalid recurrence expression was specified.
Action:: Correct the invalid recurrence and verify that it should be followed by a semicolon at the end of the expression.

ESS-09420: Property {0} is not set for request {1}.
Category:: Programmatic
Cause:: A system property that should have been set has not been set.
Action:: Contact Oracle Support Services.

ESS-09421: Request {0} is not eligible to be manually recovered until {1}.
Category:: Programmatic
Cause:: The request is not yet eligible to be recovered.
Action:: Wait until the prescribed time to attempt this operation.

ESS-09422: A hard cancel must be attempted on PL/SQL request {0} before a force cancel is allowed.
Category:: Programmatic
Cause:: A hard cancel of this request must be attempted before trying a force cancel.
Action:: Cancel the request using the old-style hard cancel.