33 ESS-00001 to ESS-09004

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

Type: WARNING

Impact: Other

ESS-00002: Constraint error for property {0} with value {1}.: Cause: An attempt was made to change the value of an object thatis read-only; Action: Retry the operation without changing the value of the object.
Level: 1

Type: WARNING

Impact: Other

ESS-00003: Failed to find resource {0}. {1}: Cause: A JNDI lookup of the given resource caused an error; Action: TODO: action
Level: 1

Type: ERROR

Impact: Other

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

Type: WARNING

Impact: Programmatic

ESS-00005: SQL bind operation not supported for parameter data type: {0}: Cause: A value being used for an SQL bind parameter has a data type that is not suitable for the SQL Statement.; Action: Specify a parameter value having an appropriate data type.
Level: 1

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

ESS-00007: Operation intended for group, {0}. Configured group is {1}.: Cause: An Enterprise Scheduler instance received an event, message, or other data that was intended for an instance of a different group.; Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

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

Type: ERROR

Impact: Installation

ESS-00101: Global data source, {0}, could not be created: Cause: The global data source could not be created; Action: TODO
Level: 1

Type: ERROR

Impact: Installation

ESS-00102: Dependent component, {0}, has not been deployed: Cause: A dependent component of this component has not been deployed. An error may have occurred when deploying dependent component; Action: Check log for errors in deploying dependent component
Level: 1

Type: ERROR

Impact: Installation

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

Type: WARNING

Impact: Installation

ESS-00120: Invalid value for dispatcher poll interval: Cause: Attempted to configure an invalid value for the dispatcher minimum or maximum poll interval.; Action: Retry the operation with a non-negative numeric value.
Level: 1

Type: WARNING

Impact: Other

ESS-00121: Dispatcher poll interval minimum value cannot exceed maximum value: Cause: Attempted to configure a value for the dispatcher maximum poll interval that is less than the minimum value.; Action: Retry the operation with a value that is equal to or greater than the minimum value.
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

ESS-00300: Invalid value ({0}) for {1} argument.: Cause: The value specified for an argument is not valid.; Action: Retry the operation using a valid value.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00301: TopologyNodeType, {0}, is not supported for this operation.: Cause: The operation is not supported on the specified topology node type.; Action: Retry the operation on OC4JComponent or Group.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00310: Work assignment, {0}, already exists.: Cause: Attempted an operation using a work assignment that already exists.; Action: Retry the operation with an assignment that does not exist.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00311: Work assignment, {0}, does not exist.: Cause: Attempted an operation using a work assignment that does not exist.; Action: Retry the operation with an assignment that exists.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00312: Group, {0}, does not exist.: Cause: Attempted an operation using a group that does not exist.; Action: Retry the operation with a group that exists.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00313: Failed to read the configuration document.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00314: Failed to write the configuration document.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00315: Invalid Wait Queue polling interval; minimum ({0}) > maximum ({1}): Cause: TODO: cause; Action: TODO: action
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00316: Invalid minimum Wait Queue polling interval ({0}).: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00317: Invalid maximum Wait Queue polling interval ({0}).: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00318: Invalid threshold ({0}) for processing low priority jobs.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00319: Invalid value ({0}) for threads to be available for request processing.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00400: Insufficent information to execute the command: Cause: A valid command was specified but the supplied information was not adequate to execute the command, possibly due to missing command switches or keywords.; Action: Review the help and syntax for the command. Retry the operation with additional information.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00401: Error attempting to execute the "{0}" operation. {1}: Cause: Encountered an error while trying to execute the specified operation.; Action: Review the error information to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00402: Invalid work assignment mode ({0}): Cause: Value specified for a work assignment mode is not valid.; Action: Retry the operation with a valid value; "primary" or "secondary".
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00403: Work assignment is required: Cause: A work assignment is required for the operation but none was specified.; Action: Retry the operation with at least one work assignment.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00404: Invalid topoNode "{0}": Cause: Invalid topoNode; Action: Provide a valid topoNode value and make usre the Config MBean is registered with ESSAPP
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00405: The Config MBean "{0}" is not registered with the ESSAPP: Cause: Config MBean is not registered with the ESSAPP; Action: Make sure the Config MBean is registered with ESSAPP and then retry
Level: 1

Type: ERROR

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Programmatic

ESS-01004: Illegal attempt to set state of request, {0}, to VALIDATION_FAILED when current state, {1}, is not PENDING_VALIDATION: Cause: Internal error; Action: None
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Programmatic

ESS-01006: RuntimeServiceHandle is marked for rollback only: Cause: The ESS runtime service handle has been marked for rollback only; Action: Close the ESS runtime service session. Another session may be created for further operations.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01007: RuntimeServiceHandle is null: Cause: The ESS runtime service handle is null.; Action: Specify a valid ESS runtime service handle.
Level: 1

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

ESS-01010: Value for parameter, {0}, must not be null.: Cause: The given parameter does not support a null value.; Action: Specify a non-null value for the parameter.
Level: 1

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

ESS-01014: Error occurred attempting to lock request {0}.: Cause: An error occurred attempting to lock a request in the runtime store.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01015: Failed to generate a request identifer.: Cause: An error occurred attempting to generate a new request identifier.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01016: Failed to generate a request handle.: Cause: An error occurred attempting to generate a new request handle.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01017: Error attempting to access information for request {0}.: Cause: An error occurred attempting to access information for a request.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01018: Error attempting to update information for request {0}.: Cause: An error occurred attempting to update information for a request.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01019: Request {0} is not in {1} state. Current state is {2}.: Cause: An operation was attempted when the request was not in an expected state.; Action: Retry the operation when the request is the correct state.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01021: Error occurred processing system purge request {0}. {1}: Cause: An error occurred while proccessing system purge job.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01022: Error occurred retrieving summary data. {0}: Cause: An error occurred attempting to retrieve request or application summary information.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

ESS-01027: Failed to convert schedule to string: Cause: The schedule cannot be converted to a string; Action: None
Level: 1

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

ESS-01097: Request, {0}, is not of expected type, {1}.: Cause: The request was found in ESS runtime storage but was not of the expected execution type; Action: Specify a request identifier for a request of the correct execution type
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01098: No request found for the given id {0} {1}: Cause: A request was not found in ESS runtime storage corresponding to the indicated request identifier; Action: Specify a request identifier for an existing request
Level: 1

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

ESS-01100: Error retrieving details about Oracle Scheduler job {0} for request {1}.: Cause: An error occurred while trying to retrieve details about the Oracle Scheduler job associated with an ESS request identifier.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01101: Error retrieving the OUTPUT_LIST for parallel children of request {0}.: Cause: An error occurred while trying to retrieve the OUTPUT_LIST for parallel child requests for an ESS request identifier.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

ESS-01108: Failed to fetch elements from wait queue. {0}: Cause: An error occurred attempting to fetch elements from the wait queue.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01109: Failed to access wait queue element for request {0}. {1}: Cause: An error occurred attempting to access a wait queue element.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01110: Failed to lock wait queue element for request {0}. {1}: Cause: Failed to obtain a lock on the wait queue element for a request.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01111: Failed to insert wait queue element for request {0}. {1}: Cause: An error occurred while attempting to add an element to the wait queue.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01112: Failed to delete wait queue element for request {0}. {1}: Cause: An error occurred while attempting to remove an element from the wait queue.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01113: Failed to hold wait queue element for request {0}. {1}: Cause: An error occurred attempting to hold the wait queue element for a request.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01114: Failed to release wait queue element for request {0}. {1}: Cause: An error occurred attempting to release the wait queue element for a request.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01115: Failed to undefer wait queue element for request {0}. {1}: Cause: An error occurred attempting to undefer the wait queue element for a request.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01116: Query field name, {0}, is not a valid name.: Cause: A query filter was specified with an unknown query field.; Action: Remove that query field from the filter, or specify a known name for the query field.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01117: Value for query field, {0}, has an unsupported data type: {1}: Cause: A query filter was specified in which the value for a query field has an unsupported data type.; Action: Specify a query value whose data type is a supported type.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01118: Query field, {0}, has a null value which is not supported for the {1} operator.: Cause: A query filter was specified with a field that has a null value and a comparator that does not support a null value. A null query value requires an EQUALS or NOT_EQUALS comparator.; Action: Specify a non-null value for that query field, or specify an EQUALS or NOT_EQUALS comparator.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01119: Query field, {0}, has a value with a data type, {1}, that is not supported for the {2} comparator.: Cause: A query filter was specified with a field that has a value whose data type is not supported for the specified comparator.; Action: Specify a query value whose data type is supported by the comparator being used.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01120: Query field, {0}, does not support the {1} comparator.: Cause: A query filter was specified with a field that does not support the specified comparator.; Action: Specify a comparator that is supported by that query field.
Level: 1

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

ESS-01122: Error attempting to access information for incompatibility {0} for request {1}.: Cause: An error occurred attempting to access request incompatibility information.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01123: Error attempting to update information for incompatibility {0} for request {1}.: Cause: An error occurred attempting to update request incompatibility information.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01124: Error attempting to add information for incompatibility {0} for request {1}.: Cause: An error occurred attempting to add request incompatibility information.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01125: Size of request parameter {0} used for incompatibility {1} is too large.: Cause: The value for a request parameter that would be used for an Incompatibility is too large.; Action: Use a smaller value for the parameter value.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01126: Application {0} is active in more than one group.: Cause: An application with the same name is already a member of another ESS group.; Action: Redeploy the current application with a unique deployment name.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01127: Application {0} is not active in any ESS instance.: Cause: The application could not be found in the current ESS group.; Action: Ensure the application is deployed and running in the correct ESS group.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01128: Application with deployed name {0} exists with multiple logical names.: Cause: An application with the same deployment name but different logical name is already a member of this ESS group.; Action: Redploy this application with a unique deployment name. If this application is the same application as the conflicting app, then change the logical name to match.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01129: No application with deployed name {0} found.: Cause: The application is not a member of this ESS group.; Action: Ensure the application is deployed and running in the correct ESS group.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01130: Application with logical name {0} exists with multiple deployed names.: Cause: An application with the same logical name but different deployment name is already a member of this ESS group.; Action: Redploy this application with a unique logical application name. If this application is the same application as the conflicting app, then change the deployment name to match.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01131: No application with logical name {0} found.: Cause: The application is not a member of this ESS group.; Action: Ensure the application is deployed and running in the correct ESS group.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01132: Unable to access processor bindings. {0}: Cause: Processor bindings in the runtime store could not be accessed.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

ESS-01134: Processor binding {0} already exists.: Cause: Processor binding already exists.; Action: Change the name of the binding.
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

ESS-01500: Dispatcher cannot be started while in {0} state.: Cause: Attempted to start the dispatcher when it is in a state for which the operation is not allowed.; Action: Retry the operation when the dispatcher state is STOPPED.
Level: 1

Type: WARNING

Impact: Other

ESS-01501: Dispatcher cannot be stopped while in {0} state.: Cause: Attempted to stop the dispatcher when it is in a state for which the operation is not allowed.; Action: Retry the operation when the dispatcher state is STARTING or RUNNING.
Level: 1

Type: WARNING

Impact: Other

ESS-01502: Processer cannot be started while in {0} state.: Cause: Attempted to start the processor when it is in a state for which the operation is not allowed.; Action: Retry the operation when the processor state is STOPPED.
Level: 1

Type: WARNING

Impact: Other

ESS-01503: Processor cannot be stopped while in {0} state.: Cause: Attempted to stop the processor when it is in a state for which the operation is not allowed.; Action: Retry the operation when the processor state is STARTING or RUNNING.
Level: 1

Type: WARNING

Impact: Other

ESS-01504: Cannot add endpoint {0} for application {1} because endpoint {2} already exists for application {3}.: Cause: The endpoint to add conflicts with an already existing endpoint.; Action: TODO: action
Level: 1

Type: ERROR

Impact: Deployment

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

Type: WARNING

Impact: Other

ESS-01600: JobSet request {0} indicated completed, but is in a non-terminal state, {1}.: Cause: A JobSet request has been marked as completed, but is in an unexpected, non-terminal state.; Action: Review the log file for an errors pertaining to the request.
Level: 1

Type: WARNING

Impact: Other

ESS-01700: Unrecognized request type : {0}: Cause: The job type used for the request is unsupported.; Action: TODO: action: Q: Is this possible?
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01701: Unable to instantiate executable wrapper for class {0}: Cause: Unable to instantiate wrapper class used to process the request.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Installation

ESS-01702: Unable to instantiate pre-process callback handler for request {0} using class name, {1}.: Cause: Failed to instantiate an object for the pre-process callback handler class associated with a request.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01703: Unable to instantiate post-process callback handler for request {0} using class name, {1}.: Cause: Failed to instantiate an object for the post-process callback handler class associated with a request.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01704: Error occurred at initiate stage during execution of request {0}. {1}: Cause: An error occurred during the initiate stage of a request execution.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01705: Error occurred at finalize stage during execution of request {0}. {1}: Cause: An error occurred during the finalize stage of a request execution.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Programmatic

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

Type: ERROR

Impact: Programmatic

ESS-01707: Unable to instantiate Executable for Java request {0} using class name, {1}.: Cause: Failed to instantiate Executable object for a Java request.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01708: Database job for request {0} ended with error: {1}: Cause: Execution of a SQL request has ended with a error.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

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

Type: NOTIFICATION

Impact: Programmatic

ESS-01711: Database job for request {0} was paused. Paused state value: {1}: Cause: Execution of a SQL job request has been paused to allow one or more sub-requests to execute.; Action: None. The execution of the paused request will be resumed once the sub-requests have completed.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

ESS-01712: Failed to create database job for request {0}. {1}: Cause: An error occurred trying to create an Oracle Scheduler job used to execute a SQL job request.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01713: Error cancelling database job for request {0}. {1}: Cause: An error occurred during post-execution clean tasks for an Oracle Scheduler job used to execute a SQL job request.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Programmatic

ESS-01902: Error undeferring command message. {0}: Cause: An error occurred deferring a command until application endpoint is activated; Action: None
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

ESS-02000: Failed to obtain principal for anonymous user. {0}: Cause: Invalid user; Action: Check the user settting.
Level: 1

Type: WARNING

Impact: Other

ESS-02001: User {0} does not execute permission on metadata object {1} before executing.: Cause: User {0} does not execute permission on metadata object {1} before executing.; Action: Check the policy assignment..
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: NOTIFICATION

Impact: Other

ESS-05010: Request {0} not found.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-05020: Failed to get a transaction.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-05021: Failed to begin transaction.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-05022: Failed to commit transaction.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-05023: Failed to rollback transaction.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-05024: Failed to set transaction timeout.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-05030: Method, {0}, not found for class {1}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

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

Type: ERROR

Impact: Configuration

ESS-05039: Error occurred closing JNDI naming context.: Cause: An error occurred while trying to close a JNDI naming context.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-05040: Error occurred closing JMS {0}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-05041: Error occurred committing JMS Session.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-05042: Error occurred during JMS Session rollback.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

ESS-05046: Failed to close an SQL ResultSet.: Cause: An error occurred trying to close an SQL ResultSet.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-05047: Failed to close an SQL Statement.: Cause: An error occurred trying to close an SQL Statement.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-05048: Failed to obtain a database connection.: Cause: An error occurred trying to obtain a database connection.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-05049: Failed to close a database connection.: Cause: An error occurred trying to close a database connection.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

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

Type: INCIDENT_ERROR

Impact: Other

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

Type: INCIDENT_ERROR

Impact: Other

ESS-05055: Illegal state transition from {0} to {1} for request {2}: Cause: An update event's timing may have tried to change the state after the request has begun a transition to a terminal state.; Action: Ignore the warning
Level: 1

Type: WARNING

Impact: Other

ESS-05200: Scheduler configuration file not found: {0}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-05201: Error parsing scheduler configuration, using defaults: {0}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-05490: Service MBeans registration failed.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-05491: Enterprise Scheduler WSDL file could not be found at {0}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-05700: Failed to obtain a metadata service instance. {0}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-05701: Failed to open metadata service. {0}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-05702: Failed to close metadata service handle. {0}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-05703: Metadata service system failure. {0}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Programmatic

ESS-05705: Failed to save the {0} with name {1}.: Cause: Failed to save the metadata object; Action: TODO: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

ESS-05707: {0} with name {1} already exists.: Cause: The metadata object already exists; Action: TODO: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-05708: Failed to delete the {0} with name {1}.: Cause: Unable to delete the metadata object; Action: TODO: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Other

ESS-06000: Failed to obtain a runtime service instance. {0}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06001: Failed to open runtime service. {0}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06002: Failed to close runtime service handle. {0}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06003: Runtime service system failure. {0}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06100: No request found for the given id {0}: Cause: A request was not found in ESS runtime storage corresponding to the indicated request identifier; Action: Specify a request identifier for an existing request
Level: 1

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Other

ESS-06520: Failed to register configuration during endpoint activation.: Cause: An error occurred registering configuration during an endpoint activation.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06521: Failed to start request dispatcher.: Cause: An error occurred while trying to start the request dispatcher.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06522: Failed to start request processor.: Cause: An error occurred while trying to start the request processor.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06523: Failed to start system event service.: Cause: An error occurred while trying to start the system event service.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06524: Failed to start application event service.: Cause: An error occurred while trying to start the application event service.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06525: Failed to start heartbeat monitor.: Cause: An error occurred while trying to start the heartbeat monitor.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06526: Failed to update configuration information.: Cause: An error occurred while trying to update configuration information.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06527: Failed to start deferred monitor.: Cause: An error occurred while trying to start the deferred monitor.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

ESS-06538: No endpoint is available for {0}.: Cause: An application using the specified endpoint application name is not deployed.; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

ESS-06540: Failed to get an endpoint to run dispatcher for application {0}.: Cause: Dispatch monitor was unable to obtain an application endpoint. This may happen when the system is busy and does not necessary indicate a problem.; Action: Review the log file for indications of a problem if this persists.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06541: Error during dispatch for application {0}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06542: Dispatcher failed to query database. SQL error: {0}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

ESS-06550: Failed retrieving event listener for {0} event for request {1}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06551: Failed processing trigger for {0} event.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06552: Failed processing trigger for {0} event for request {1}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06553: Failed processing lifecycle for {0} event for request {1}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06558: Failed to get an endpoint to run a heartbeat for application {0}.: Cause: Heartbeat monitor was unable to obtain an application endpoint. This may happen when the system is busy and does not necessary indicate a problem.; Action: Review the log file for indications of a problem if this persists.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06559: Error during heartbeat for application {0}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06560: Error encountered by event worker.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06561: Failed to get an endpoint for application {0}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06562: Failed while calling endpoint for application {0}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06563: Required property, {0}, is not present in message received by event worker.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06564: Failed to create event from message type, {0}, for event name {1}, request {2}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06565: Unable to retrieve message with context ({0}) in event worker.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06566: Discarded event message. Event: {0}, Reason: {1}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06570: Failed to get metadata for work assignment {0}.: Cause: Unable to retrieve work assignment metadata when analyzing work assignment bindings. The work assignment is ignored.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06571: Failed to get workshift metadata ({0}) for work assignment {1}.: Cause: Unable to retrieve workshift metadata when analyzing a work assignment binding. The work assignment processing will ignore the workshift.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06572: Failed to get schedule metadata ({0}) for work assignment {1}.: Cause: Unable to retrieve schedule metadata when analyzing a work assignment binding. The work assignment processing will ignore the workshift associated with the schedule.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06573: Failed to start work assignment {0}.: Cause: Unable to start the first worker for the work assignment. The start will be retried in a short time.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06574: Failed to start starvation thread for work assignment {0}.: Cause: Unable to start the starvation worker for the work assignment. The work assignment will be activated without the starvation worker.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06575: Skipping inactive work assignment {0}.: Cause: The work assignment is defined as inactive and is being skipped.; Action: If the work assignment should be active, change it to active and reload work assignment metadata.
Level: 1

Type: NOTIFICATION

Impact: Other

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

Type: NOTIFICATION

Impact: Other

ESS-06577: Skipping inactive workshift {0} for work assignment {1}.: Cause: The workshift is being skipped because it is inactive. It may have an allocation of 0 or a duration of 0.; Action: No action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06578: Started work assignment {0}.: Cause: Started the work assignment.; Action: No action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06579: Stopped work assignment {0}.: Cause: Stopped the work assignment.; Action: No action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06580: Skipping invalid work assignment {0}.: Cause: The work assignment is being ignored because it is invalid.; Action: Check the work assignment and correct the problem. Ensure the work assignment has at least one workshift defined.
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

ESS-06582: Skipping completed work assignment {0}.: Cause: The work assignment has completed and will never again become active. It is being skipped.; Action: If the work assignment should not be completed, check the workshift schedules to ensure they are correct and reload work assignment metadata.
Level: 1

Type: NOTIFICATION

Impact: Other

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

Type: WARNING

Impact: Other

ESS-06590: Error encountered by worker for work assignment {0}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06591: Failed get an endpoint for application {0} for work assignment {1}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06592: Errror while processing request {0} for application {1}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06593: Required property, {0}, is not present in message received for work assignment {1}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06594: Failed to schedule additional work for work assignment {0}. {1}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06595: Failed to update request history for request {0}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06610: Failed processing request {0}, {1} stage.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06611: Failed raising {0} event for request {1}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06612: Failed raising application event {0} for application {1}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06613: Failed raising internal {0} event.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06614: Failed extracting ESS information from message.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06615: Failed extracting application event information for application {0}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06616: Application endpoint received an unsupported ESS message type ({0}). No action will be taken.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06800: Error handling {0} event for request {1} by request dispatcher.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06801: Request dispatcher failed to lock request {0}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06805: Request {0} is in illegal state {1} ({2}). Skipping processing and deleting from wait queue.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06806: Request {0} not found in runtime store. Skipping processing and deleting from wait queue.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06810: Failed to get schedule definition, {0}, for request {1}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06811: Failed to get Adhoc schedule definition, {0}, for request {1}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06812: Failed to add child request. Parent request {0} not found.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06813: Failed to add child request {0} for parent request {1}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06814: Parent request {0} not found in runtime store.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06815: Failed to instantiate services.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06816: Error processing request {0} by request dispatcher.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-06817: No sub requests exist for paused request {0}. Request execution will be resumed.: Cause: No sub-requests are active for this PAUSED request; Action: Do not pause a request that has not submitted a sub-request.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-07000: Error handling {0} event for request {1} by request processor.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-07001: Error processing request {0}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-07002: Failed to obtain system executable wrapper for request {0}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: ERROR

Impact: Installation

ESS-07003: Execution warning for request {0}. Reason: {1}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-07004: Execution error for request {0}. Reason: {1}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-07005: Execution cancelled for request {0}. Reason: {1}: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-07006: Failed to cancel request {0}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-07007: Failed to kill request {0}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-07008: Failed while releasing blocked requests for request {0}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-07009: Error attempting to restart request {0}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-07010: Login denied for user {0}, application {1}. Request {2} set to {3} state.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-07011: Allowing {0} to run as anonymous user for request {1}.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-07012: Invalid action ({0}) returned from pre-process callout for request {1}. Setting to {2} state.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-07013: Invalid action ({0}) returned from post-process callout for request {1}. Setting to {2} state.: Cause: TODO: cause; Action: TODO: action
Level: 1

Type: WARNING

Impact: Other

ESS-07014: Delaying processing of request {0} by {1} minutes.: Cause: The pre-process callback return value indicated that request processing should be delayed.; Action: No action required. The request will be retried after the delay.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-07015: Error occurred during cleanup of database job for request {0}. {1}: Cause: An error occurred while performing post-execution clean tasks for an Oracle Scheduler job used to execute a SQL job request.; Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

ESS-07501: Error starting command worker. {0}: Cause: An error occurred starting a command worker; Action: None
Level: 1

Type: WARNING

Impact: Other

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

Type: WARNING

Impact: Other

ESS-07503: Failed to convert command to DOM Document: {0}. {1}: Cause: Failed to convert command to DOM Document; Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-07504: Required property, {0}, is not present in message received by command processor.: Cause: A required property was not present in the message received by command processor.; Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-08000: The value of filter is null.: Cause: The value of filter is null; Action: Provide the correct privilege name.
Level: 1

Type: WARNING

Impact: Other

ESS-08001: Invalid sec filter comparator.: Cause: Invalid sec filter comparator; Action: Choose correct comparator, GRANTED
Level: 1

Type: WARNING

Impact: Other

ESS-09000: Translation service can not be performed because resource bundles {0} for Locale {1} can not be located.: Cause: Resource Bundles invalid or requested locale does not exist.; Action: Correct the bundle id, make sure it exists in the application environement.
Level: 1

Type: WARNING

Impact: Programmatic

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

Type: WARNING

Impact: Programmatic

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

Type: ERROR

Impact: Programmatic

ESS-09003: Failed to instantiate the translation service factory implmentation {0}.: Cause: Error while instantiating an instance of translation service factory.; Action: See exception details.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-09004: Failed to retrieve a valid instance of underlying oracle.javatools ResourceBundleManager. Design time metadata translation is not supported.: Cause: Error while instantiating an instance of oracle.javatools.resourcebundle.ResourceBundleManager.; Action: N/A
Level: 1

Type: ERROR

Impact: Programmatic