BPEL Data Source Exceptions ORABPEL 04000 - 04142
BPEL Data Source Exceptions ORABPEL 04000 - 04142
Data Source Exceptions 04000 - 04142
ORABPEL-04000
severity: 10
type: error
name: Cannot count instances
description: The process domain was unable to count the number of instances. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04001
severity: 10
type: error
name: Cannot count instances
description: The process domain was unable to count the number of instances for the process \"{0}\" (revision \"{1}\"). The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04002
severity: 10
type: error
name: Cannot find instances
description: An attempt to fetch the instances using the where condition \"{0}\" from the datastore has failed. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04003
severity: 10
type: error
name: Cannot find work items
description: An attempt to fetch the work items using the where condition \"{0}\" from the datastore has failed. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04004
severity: 10
type: error
name: Cannot insert audit trail
description: The process domain was unable to insert the current log entries for the instance \"{0}\" to the audit trail table. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04005
severity: 10
type: error
name: Cannot insert audit details
description: The process domain was unable to insert the current audit trail detail entries for the instance \"{0}\" to the audit details table. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04006
severity: 10
type: error
name: Cannot insert sync work items
description: The process domain was unable to store the work items for the synchronous instance \"{0}\" to the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04007
severity: 10
type: error
name: Cannot insert sync audit trail
description: The process domain was unable to store the audit trail for the synchronous instance \"{0}\" to the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04008
severity: 10
type: error
name: Cannot set auto commit
description: Unable to set the auto commit level for the current datastore connection. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04009
severity: 10
type: error
name: Cannot commit transaction
description: Unable to commit the current datastore transaction. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04010
severity: 10
type: error
name: Cannot delete instances
description: The process domain was unable to purge the instances from the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04011
severity: 10
type: error
name: Cannot delete document
description: The process domain was unable to delete the document \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04012
severity: 10
type: error
name: Cannot delete process instances
description: The process domain was unable to delete all the instances for the process \"{0}\" (revision \"{1}\") from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04013
severity: 10
type: error
name: Cannot find expired work items
description: The process domain was unable to fetch a list of the expired work items in the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04014
severity: 10
type: error
name: Cannot lookup instance type
description: The process domain was unable to lookup the type for instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04015
severity: 10
type: error
name: Cannot find stranded scope activation messages
description: The process domain was unable to fetch a list of the stranded scope activation messages from the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04016
severity: 10
type: error
name: Cannot find stranded work items
description: The process domain was unable to fetch a list of the stranded work items in the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04017
severity: 10
type: error
name: Cannot find work items
description: The process domain was unable to find the work items for instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04018
severity: 10
type: error
name: Cannot find audit trail
description: The process domain was unable to find the audit trail entry for instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04019
severity: 10
type: error
name: Cannot find sync work items
description: The process domain was unable to find the work items for the synchronous instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04020
severity: 10
type: error
name: Cannot find sync audit trail
description: The process domain was unable to find the audit trail for the synchronous instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04021
severity: 10
type: error
name: Cannot find stranded transaction messages
description: The process domain was unable to fetch a list of stranded transaction messages from the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04022
severity: 10
type: error
name: Cannot delete transaction data
description: The process domain was unable to delete the data for transaction \"{0}\" from the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04023
severity: 10
type: error
name: Cannot load transaction data
description: The process domain was unable to load the data for transaction \"{0}\" from the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04024
severity: 10
type: error
name: Cannot store transaction data
description: The process domain was unable to insert/update the data for transaction \"{0}\" in the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04025
severity: 10
type: error
name: Cannot decode properties
description: The process domain was unable to decode the properties for message guid {0}, which are stored in column {1}; the exception reported is: {2}
ORABPEL-04026
severity: 10
type: error
name: Cannot find pending callback messages
description: The process domain was unable to find any pending callback messages in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04027
severity: 10
type: error
name: Cannot find pending invoke messages
description: The process domain was unable to find any pending invoke messages in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04028
severity: 10
type: error
name: Cannot find pending subscriptions
description: The process domain was unable to find any pending subscriptions in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04029
severity: 10
type: error
name: Cannot mark process as stale
description: The process domain was unable to mark all instances (and activites) with process GUID \"{0}\" as stale. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04030
severity: 10
type: error
name: Cannot find audit details
description: An attempt to fetch the audit details for instance \"{0}\" (detail id \"{1}\") from datastore has failed. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04031
severity: 10
type: error
name: Cannot find audit details
description: An attempt to fetch the audit details for instance \"{0}\" from datastore has failed. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04032
severity: 10
type: error
name: Cannot read lob column
description: The process domain was unable to read the lob column \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04033
severity: 10
type: error
name: Cannot fetch document
description: The process domain was unable to fetch the document \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04034
severity: 10
type: error
name: Cannot find closed instance
description: The process domain was unable to find the closed instances for the domain \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04035
severity: 10
type: error
name: Cannot fetch instance
description: The process domain was unable to fetch the instance \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04036
severity: 10
type: error
name: Cannot fetch scope activation message
description: The process domain was unable to fetch the scope activation message with key \"{0}\" from the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04037
severity: 10
type: error
name: Cannot fetch work item
description: The process domain was unable to fetch the work item \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04038
severity: 10
type: error
name: Cannot update document
description: The process domain was unable to update/insert the document \"{0}\" into the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04039
severity: 10
type: error
name: Cannot update key range
description: The process domain was unable to update the key table \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04040
severity: 10
type: error
name: Cannot update lob column
description: The process domain was unable to update the lob column \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04041
severity: 10
type: error
name: Cannot update instance
description: The process domain was unable to update/insert the instance \"{0}\" into the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04042
severity: 10
type: error
name: Cannot update scope
description: The process domain was unable to update/insert the serialized scope for instance \"{0}\" into the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04043
severity: 10
type: error
name: Cannot delete/insert scope activation message
description: The process domain was unable to delete/insert the scope activation message with key \"{0}\" from the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04044
severity: 10
type: error
name: Cannot update work item
description: The process domain was unable to update/insert the work item \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04045
severity: 10
type: error
name: Cannot batch update work items
description: The process domain was unable to batch update/insert the work items for instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04046
severity: 10
type: error
name: Cannot batch insert sync work items
description: The process domain was unable to batch insert a series of synchronous work items in the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04047
severity: 10
type: error
name: Cannot select delivery subscription
description: The process domain was unable to select the delivery data for processId \"{0}\" and operationName \"{1}\" from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04048
severity: 10
type: error
name: Cannot insert delivery subscription
description: The process domain was unable to insert the delivery data for conversation \"{0} \", subscriber \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04049
severity: 10
type: error
name: Cannot select delivery subscription
description: The process domain was unable to select the delivery data for conversation \"{0}\" (subscriber \"{1}\") from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04050
severity: 10
type: error
name: Cannot select delivery subscription
description: The process domain was unable to select the delivery data for conversation \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04051
severity: 10
type: error
name: Cannot select delivery subscription
description: The process domain was unable to select the delivery data for conversation type \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04052
severity: 10
type: error
name: Cannot select delivery subscription
description: The process domain was unable to select the delivery data for subscriber \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04053
severity: 10
type: error
name: Cannot update delivery subscription
description: The process domain was unable to update the state of the delivery subscription \"{1}\" for conversation \"{0}\". The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04054
severity: 10
type: error
name: Cannot update delivery subscription
description: The process domain was unable to update the state of the delivery subscription \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04055
severity: 10
type: error
name: Cannot delete handled subscriptions
description: The process domain \"{0}\" was unable to delete handled delivery subscriptions. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04056
severity: 10
type: error
name: Cannot insert delivery message
description: The process domain was unable to insert the delivery data for message \"{0}\", operation \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04057
severity: 10
type: error
name: Cannot delete delivery message
description: The process domain was unable to delete the delivery data for message \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04058
severity: 10
type: error
name: Cannot delete handled messages
description: The process domain \"{0}\" was unable to delete the handled delivery data from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04059
severity: 10
type: error
name: Cannot select delivery message
description: The process domain was unable to select the delivery data for message \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04060
severity: 10
type: error
name: Cannot select delivery message
description: The process domain was unable to select the delivery data for message \"{0}\", operation \"{1}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04061
severity: 10
type: error
name: Cannot update delivery message
description: The process domain was unable to update the state of the delivery message \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04062
severity: 10
type: error
name: Cannot delete invoke message
description: The process domain was unable to delete the invocation data for message \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04063
severity: 10
type: error
name: Cannot delete handled messages
description: The process domain \"{0}\" was unable to delete the handled invocation data from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04064
severity: 10
type: error
name: Cannot select invoke message
description: The process domain was unable to select the invocation data for message \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04065
severity: 10
type: error
name: Cannot select invoke message
description: The process domain was unable to select the invocation data for process \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04066
severity: 10
type: error
name: Cannot insert invoke message
description: The process domain was unable to insert the invocation data for message \"{0}\", operation \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04067
severity: 10
type: error
name: Cannot update invoke message
description: The process domain was unable to update the state of the invocation message \"{0} \". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04069
severity: 10
type: error
name: Cannot find stale instances
description: The process domain was unable to fetch a list of the stale instances belonging to process \"{0}\" (revision \"{1}\"). The exception reported is: {2}
ORABPEL-04075
severity: 10
type: error
name: Cannot update task
description: The process domain was unable to update the data for task \"{0}\" in the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04076
severity: 10
type: error
name: Cannot lookup jdbc datasource
description: The process domain was unable to lookup the TX datasource \"{0}\".
fix: Please check that the machine hosting the datasource is physically connected to the network. Additionally check that the connection pool properties as defined in the application server startup properties are valid.
ORABPEL-04077
severity: 10
type: error
name: Cannot fetch a datasource connection
description: The process domain was unable to establish a connection with the datasource with the connection URL \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04078
severity: 10
type: error
name: Cannot close datasource connection
description: The process domain was unable to release its datasource connection. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04079
severity: 10
type: error
name: Cannot read blob stream
description: Cannot read blob stream from datastore with key \"{0}\"; exception is {1}
ORABPEL-04080
severity: 10
type: error
name: Data stream not found
description: The data stream for the instance/activity object \"{0}\" was not found in the datastore.
fix: Please check that the instance/activity key \"{0}\" refers to a valid instance/activity that has been started and not removed from the process domain.
ORABPEL-04081
severity: 10
type: error
name: Cannot write stream length
description: Cannot write binary stream length to serializer for instance \"{0}\"; exception is {1}
ORABPEL-04082
severity: 10
type: error
name: Cannot delete instance
description: The process domain was unable to delete the instance \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04083
severity: 10
type: error
name: Cannot update work item exception
description: The process domain was unable to insert/update the exception entry for the activity \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04084
severity: 10
type: error
name: Cannot delete work item exception
description: The process domain was unable to delete the exception entry for the activity \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04085
severity: 10
type: error
name: Cannot find work item exception
description: The process domain was unable to find the activity in the domain \"{0}\" with custom key \"{1}\"; the exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04087
severity: 10
type: error
name: Cannot find schedulable activities
description: Failed to find schedulable activities for domain \"{0}\"; exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04088
severity: 10
type: error
name: Cannot find tasks
description: Failed to find the tasks for domain \"{0}\" with the where condition \"{1}\"; the exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04089
severity: 10
type: error
name: Cannot update task
description: The process domain was unable to insert the data for task \"{0}\" in the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04090
severity: 10
type: error
name: Cannot select scope
description: The process domain was unable to read the serialized scope for instance \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04091
severity: 10
type: error
name: Cannot select instance indexes
description: The process domain was unable to read the indexes for instance \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04092
severity: 10
type: error
name: Cannot update instance indexes
description: The process domain was unable to update/insert the indexes for instance \"{0}\" into the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04093
severity: 10
type: error
name: Cannot select process metadata
description: The process domain was unable to select the metadata for process \"{0}\" with revision tag \"{1}\" from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04095
severity: 10
type: error
name: Cannot delete process metadata
description: The process domain was unable to delete the metadata for process \"{0}\" with revision tag \"{1}\" from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04096
severity: 10
type: error
name: Cannot update process metadata
description: The process domain was unable to insert/update the process metadata for process \"{0}\" with revision tag \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04097
severity: 10
type: error
name: Cannot find process revision
description: The process domain was unable to find the process revision record for process \"{0}\" with revision tag \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04098
severity: 10
type: error
name: Cannot flush jboss datasource
description: The process domain was unable to flush the datasource \"{0}\". The exception reported is: {1}
fix: Please try manually flushing the datasource from the jboss jmx-console.
ORABPEL-04099
severity: 10
type: error
name: Cannot find instances
description: The process domain was unable to find instances with root id \"{0}\" in the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04100
severity: 10
type: error
name: Cannot find invoke metadata
description: The process domain was unable to find any invoke messages with the specified where condition in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04101
severity: 10
type: error
name: Cannot find callback metadata
description: The process domain was unable to find any callback messages with the specified where condition in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04102
severity: 10
type: error
name: Cannot insert process event
description: The process domain was unable to insert the process event for process \"{0}\" (revision \"{1}\") in the datasource. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04103
severity: 10
type: error
name: Cannot find process events
description: The process domain was unable to find any process events with the specified where condition in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04104
severity: 10
type: error
name: Cannot find default revisions
description: The process domain was unable to find the default process revisions in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04105
severity: 10
type: error
name: Cannot update default revision
description: The process domain was unable to set the default revision for process \"{0}\", revision tag \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04106
severity: 10
type: error
name: Cannot delete default revision
description: The process domain was unable to delete the default revision for process \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04107
severity: 10
type: error
name: Cannot update lob column
description: The process domain was unable to update the lob column \"{0}\" in the datastore, for cube instance \"{1}\". The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04108
severity: 10
type: error
name: Cannot select attachment
description: The process domain was unable to select the attachent by the key \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04109
severity: 10
type: error
name: Cannot delete attachment
description: The process domain was unable to delete the attachent by the key \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04110
severity: 10
type: error
name: Cannot insert attachment
description: The process domain was unable to insert attachent into the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04111
severity: 10
type: error
name: Cannot fetch attachment reference
description: The process domain was unable to seelct the attachment reference \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04112
severity: 10
type: error
name: Cannot insert attachment reference
description: The process domain was unable to insert attachent reference into the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04113
severity: 10
type: error
name: Cannot delete attachment reference
description: The process domain was unable to remove attachent reference of instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04121
severity: 10
type: error
name: Cannot find test details
description: An attempt to fetch the test details using the where condition \"{0}\" from the datastore has failed. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04122
severity: 10
type: error
name: Cannot update test details
description: The process domain was unable to insert/update test details for instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04123
severity: 10
type: error
name: Cannot update delivery message batch
description: The process domain was unable to update the state of the following delivery messages \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04124
severity: 10
type: error
name: Cannot update delivery subscription batch
description: The process domain was unable to update the state of the following delivery subscriptions \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04125
severity: 10
type: error
name: Cannot select detail instances
description: The process domain was unable to select the number of detail instances for master instance specified by the conversation id \"{0}\".
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04126
severity: 10
type: error
name: Cannot select document reference key
description: The process domain was unable to select document references for instance id \"{0} \". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04127
severity: 10
type: error
name: Cannot select insert reference key
description: The process domain was unable to insert document references for instance id \"{0} \". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04128
severity: 10
type: error
name: Cannot select document reference key
description: The process domain was unable to select document references for delivery message guid \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04129
severity: 10
type: error
name: Cannot select insert reference key
description: The process domain was unable to insert document references for delivery message guid \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04130
severity: 10
type: error
name: Cannot select process descriptor
description: The process domain was unable to select the descriptor for process \"{0}\", revision \"{1}\" from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04131
severity: 10
type: error
name: Cannot insert/update process descriptor
description: The process domain was unable to insert/update the descriptor for process \"{0}\", revision \"{1}\" into the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04132
severity: 10
type: error
name: Cannot read clob stream
description: Cannot read clob stream from datastore with key \"{0}\"; exception is {1}
ORABPEL-04133
severity: 10
type: error
name: Cannot select process suitcase
description: The process domain was unable to select the bytes for suitcase \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04134
severity: 10
type: error
name: Cannot insert/update process suitcase
description: The process domain was unable to insert/update the process suitcase \"{0}\" into the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04135
severity: 10
type: error
name: Cannot delete process suitcase
description: The process domain was unable to delete the process suitcase \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04136
severity: 10
type: error
name: Cannot count suitcase processes
description: The process domain was unable to count the number of deployed suitcase processes. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04137
severity: 10
type: error
name: Cannot find test definition
description: An attempt to fetch the test definition for process \"{0}\", revision \"{1}\", test suite \"{2}\", location \"{3}\" from the datastore has failed. The exception reported is: {4}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04138
severity: 10
type: error
name: Cannot store test definition
description: The process domain was unable to store the test definition for process \"{0}\", revision \"{1}\", test suite \"{2}\", location \"{3}\" in the datastore. The exception reported is: {4}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04139
severity: 10
type: error
name: Cannot delete test definition
description: The process domain was unable to delete the test definition for process \"{0}\", revision \"{1}\", test suite \"{2}\", location \"{3}\" in the datastore. The exception reported is: {4}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04140
severity: 10
type: error
name: Cannot delete test definitions
description: The process domain was unable to delete test definitions for process \"{0}\", revision \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04141
severity: 10
type: error
name: Cannot delete process events
description: The process domain was unable to delete the events logged for process \"{0}\", revision \"{1}\" from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04142
severity: 10
type: error
name: Cannot delete process events
description: The process domain was unable to delete the events logged for in the domain. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
Data Source Exceptions 04000 - 04142
ORABPEL-04000
severity: 10
type: error
name: Cannot count instances
description: The process domain was unable to count the number of instances. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04001
severity: 10
type: error
name: Cannot count instances
description: The process domain was unable to count the number of instances for the process \"{0}\" (revision \"{1}\"). The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04002
severity: 10
type: error
name: Cannot find instances
description: An attempt to fetch the instances using the where condition \"{0}\" from the datastore has failed. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04003
severity: 10
type: error
name: Cannot find work items
description: An attempt to fetch the work items using the where condition \"{0}\" from the datastore has failed. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04004
severity: 10
type: error
name: Cannot insert audit trail
description: The process domain was unable to insert the current log entries for the instance \"{0}\" to the audit trail table. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04005
severity: 10
type: error
name: Cannot insert audit details
description: The process domain was unable to insert the current audit trail detail entries for the instance \"{0}\" to the audit details table. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04006
severity: 10
type: error
name: Cannot insert sync work items
description: The process domain was unable to store the work items for the synchronous instance \"{0}\" to the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04007
severity: 10
type: error
name: Cannot insert sync audit trail
description: The process domain was unable to store the audit trail for the synchronous instance \"{0}\" to the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04008
severity: 10
type: error
name: Cannot set auto commit
description: Unable to set the auto commit level for the current datastore connection. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04009
severity: 10
type: error
name: Cannot commit transaction
description: Unable to commit the current datastore transaction. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04010
severity: 10
type: error
name: Cannot delete instances
description: The process domain was unable to purge the instances from the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04011
severity: 10
type: error
name: Cannot delete document
description: The process domain was unable to delete the document \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04012
severity: 10
type: error
name: Cannot delete process instances
description: The process domain was unable to delete all the instances for the process \"{0}\" (revision \"{1}\") from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04013
severity: 10
type: error
name: Cannot find expired work items
description: The process domain was unable to fetch a list of the expired work items in the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04014
severity: 10
type: error
name: Cannot lookup instance type
description: The process domain was unable to lookup the type for instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04015
severity: 10
type: error
name: Cannot find stranded scope activation messages
description: The process domain was unable to fetch a list of the stranded scope activation messages from the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04016
severity: 10
type: error
name: Cannot find stranded work items
description: The process domain was unable to fetch a list of the stranded work items in the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04017
severity: 10
type: error
name: Cannot find work items
description: The process domain was unable to find the work items for instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04018
severity: 10
type: error
name: Cannot find audit trail
description: The process domain was unable to find the audit trail entry for instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04019
severity: 10
type: error
name: Cannot find sync work items
description: The process domain was unable to find the work items for the synchronous instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04020
severity: 10
type: error
name: Cannot find sync audit trail
description: The process domain was unable to find the audit trail for the synchronous instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04021
severity: 10
type: error
name: Cannot find stranded transaction messages
description: The process domain was unable to fetch a list of stranded transaction messages from the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04022
severity: 10
type: error
name: Cannot delete transaction data
description: The process domain was unable to delete the data for transaction \"{0}\" from the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04023
severity: 10
type: error
name: Cannot load transaction data
description: The process domain was unable to load the data for transaction \"{0}\" from the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04024
severity: 10
type: error
name: Cannot store transaction data
description: The process domain was unable to insert/update the data for transaction \"{0}\" in the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04025
severity: 10
type: error
name: Cannot decode properties
description: The process domain was unable to decode the properties for message guid {0}, which are stored in column {1}; the exception reported is: {2}
ORABPEL-04026
severity: 10
type: error
name: Cannot find pending callback messages
description: The process domain was unable to find any pending callback messages in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04027
severity: 10
type: error
name: Cannot find pending invoke messages
description: The process domain was unable to find any pending invoke messages in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04028
severity: 10
type: error
name: Cannot find pending subscriptions
description: The process domain was unable to find any pending subscriptions in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04029
severity: 10
type: error
name: Cannot mark process as stale
description: The process domain was unable to mark all instances (and activites) with process GUID \"{0}\" as stale. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04030
severity: 10
type: error
name: Cannot find audit details
description: An attempt to fetch the audit details for instance \"{0}\" (detail id \"{1}\") from datastore has failed. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04031
severity: 10
type: error
name: Cannot find audit details
description: An attempt to fetch the audit details for instance \"{0}\" from datastore has failed. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04032
severity: 10
type: error
name: Cannot read lob column
description: The process domain was unable to read the lob column \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04033
severity: 10
type: error
name: Cannot fetch document
description: The process domain was unable to fetch the document \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04034
severity: 10
type: error
name: Cannot find closed instance
description: The process domain was unable to find the closed instances for the domain \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04035
severity: 10
type: error
name: Cannot fetch instance
description: The process domain was unable to fetch the instance \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04036
severity: 10
type: error
name: Cannot fetch scope activation message
description: The process domain was unable to fetch the scope activation message with key \"{0}\" from the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04037
severity: 10
type: error
name: Cannot fetch work item
description: The process domain was unable to fetch the work item \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04038
severity: 10
type: error
name: Cannot update document
description: The process domain was unable to update/insert the document \"{0}\" into the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04039
severity: 10
type: error
name: Cannot update key range
description: The process domain was unable to update the key table \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04040
severity: 10
type: error
name: Cannot update lob column
description: The process domain was unable to update the lob column \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04041
severity: 10
type: error
name: Cannot update instance
description: The process domain was unable to update/insert the instance \"{0}\" into the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04042
severity: 10
type: error
name: Cannot update scope
description: The process domain was unable to update/insert the serialized scope for instance \"{0}\" into the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04043
severity: 10
type: error
name: Cannot delete/insert scope activation message
description: The process domain was unable to delete/insert the scope activation message with key \"{0}\" from the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04044
severity: 10
type: error
name: Cannot update work item
description: The process domain was unable to update/insert the work item \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04045
severity: 10
type: error
name: Cannot batch update work items
description: The process domain was unable to batch update/insert the work items for instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04046
severity: 10
type: error
name: Cannot batch insert sync work items
description: The process domain was unable to batch insert a series of synchronous work items in the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04047
severity: 10
type: error
name: Cannot select delivery subscription
description: The process domain was unable to select the delivery data for processId \"{0}\" and operationName \"{1}\" from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04048
severity: 10
type: error
name: Cannot insert delivery subscription
description: The process domain was unable to insert the delivery data for conversation \"{0} \", subscriber \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04049
severity: 10
type: error
name: Cannot select delivery subscription
description: The process domain was unable to select the delivery data for conversation \"{0}\" (subscriber \"{1}\") from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04050
severity: 10
type: error
name: Cannot select delivery subscription
description: The process domain was unable to select the delivery data for conversation \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04051
severity: 10
type: error
name: Cannot select delivery subscription
description: The process domain was unable to select the delivery data for conversation type \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04052
severity: 10
type: error
name: Cannot select delivery subscription
description: The process domain was unable to select the delivery data for subscriber \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04053
severity: 10
type: error
name: Cannot update delivery subscription
description: The process domain was unable to update the state of the delivery subscription \"{1}\" for conversation \"{0}\". The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04054
severity: 10
type: error
name: Cannot update delivery subscription
description: The process domain was unable to update the state of the delivery subscription \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04055
severity: 10
type: error
name: Cannot delete handled subscriptions
description: The process domain \"{0}\" was unable to delete handled delivery subscriptions. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04056
severity: 10
type: error
name: Cannot insert delivery message
description: The process domain was unable to insert the delivery data for message \"{0}\", operation \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04057
severity: 10
type: error
name: Cannot delete delivery message
description: The process domain was unable to delete the delivery data for message \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04058
severity: 10
type: error
name: Cannot delete handled messages
description: The process domain \"{0}\" was unable to delete the handled delivery data from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04059
severity: 10
type: error
name: Cannot select delivery message
description: The process domain was unable to select the delivery data for message \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04060
severity: 10
type: error
name: Cannot select delivery message
description: The process domain was unable to select the delivery data for message \"{0}\", operation \"{1}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04061
severity: 10
type: error
name: Cannot update delivery message
description: The process domain was unable to update the state of the delivery message \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04062
severity: 10
type: error
name: Cannot delete invoke message
description: The process domain was unable to delete the invocation data for message \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04063
severity: 10
type: error
name: Cannot delete handled messages
description: The process domain \"{0}\" was unable to delete the handled invocation data from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04064
severity: 10
type: error
name: Cannot select invoke message
description: The process domain was unable to select the invocation data for message \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04065
severity: 10
type: error
name: Cannot select invoke message
description: The process domain was unable to select the invocation data for process \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04066
severity: 10
type: error
name: Cannot insert invoke message
description: The process domain was unable to insert the invocation data for message \"{0}\", operation \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04067
severity: 10
type: error
name: Cannot update invoke message
description: The process domain was unable to update the state of the invocation message \"{0} \". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04069
severity: 10
type: error
name: Cannot find stale instances
description: The process domain was unable to fetch a list of the stale instances belonging to process \"{0}\" (revision \"{1}\"). The exception reported is: {2}
ORABPEL-04075
severity: 10
type: error
name: Cannot update task
description: The process domain was unable to update the data for task \"{0}\" in the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04076
severity: 10
type: error
name: Cannot lookup jdbc datasource
description: The process domain was unable to lookup the TX datasource \"{0}\".
fix: Please check that the machine hosting the datasource is physically connected to the network. Additionally check that the connection pool properties as defined in the application server startup properties are valid.
ORABPEL-04077
severity: 10
type: error
name: Cannot fetch a datasource connection
description: The process domain was unable to establish a connection with the datasource with the connection URL \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04078
severity: 10
type: error
name: Cannot close datasource connection
description: The process domain was unable to release its datasource connection. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04079
severity: 10
type: error
name: Cannot read blob stream
description: Cannot read blob stream from datastore with key \"{0}\"; exception is {1}
ORABPEL-04080
severity: 10
type: error
name: Data stream not found
description: The data stream for the instance/activity object \"{0}\" was not found in the datastore.
fix: Please check that the instance/activity key \"{0}\" refers to a valid instance/activity that has been started and not removed from the process domain.
ORABPEL-04081
severity: 10
type: error
name: Cannot write stream length
description: Cannot write binary stream length to serializer for instance \"{0}\"; exception is {1}
ORABPEL-04082
severity: 10
type: error
name: Cannot delete instance
description: The process domain was unable to delete the instance \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04083
severity: 10
type: error
name: Cannot update work item exception
description: The process domain was unable to insert/update the exception entry for the activity \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04084
severity: 10
type: error
name: Cannot delete work item exception
description: The process domain was unable to delete the exception entry for the activity \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04085
severity: 10
type: error
name: Cannot find work item exception
description: The process domain was unable to find the activity in the domain \"{0}\" with custom key \"{1}\"; the exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04087
severity: 10
type: error
name: Cannot find schedulable activities
description: Failed to find schedulable activities for domain \"{0}\"; exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04088
severity: 10
type: error
name: Cannot find tasks
description: Failed to find the tasks for domain \"{0}\" with the where condition \"{1}\"; the exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04089
severity: 10
type: error
name: Cannot update task
description: The process domain was unable to insert the data for task \"{0}\" in the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04090
severity: 10
type: error
name: Cannot select scope
description: The process domain was unable to read the serialized scope for instance \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04091
severity: 10
type: error
name: Cannot select instance indexes
description: The process domain was unable to read the indexes for instance \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04092
severity: 10
type: error
name: Cannot update instance indexes
description: The process domain was unable to update/insert the indexes for instance \"{0}\" into the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04093
severity: 10
type: error
name: Cannot select process metadata
description: The process domain was unable to select the metadata for process \"{0}\" with revision tag \"{1}\" from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04095
severity: 10
type: error
name: Cannot delete process metadata
description: The process domain was unable to delete the metadata for process \"{0}\" with revision tag \"{1}\" from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04096
severity: 10
type: error
name: Cannot update process metadata
description: The process domain was unable to insert/update the process metadata for process \"{0}\" with revision tag \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04097
severity: 10
type: error
name: Cannot find process revision
description: The process domain was unable to find the process revision record for process \"{0}\" with revision tag \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04098
severity: 10
type: error
name: Cannot flush jboss datasource
description: The process domain was unable to flush the datasource \"{0}\". The exception reported is: {1}
fix: Please try manually flushing the datasource from the jboss jmx-console.
ORABPEL-04099
severity: 10
type: error
name: Cannot find instances
description: The process domain was unable to find instances with root id \"{0}\" in the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04100
severity: 10
type: error
name: Cannot find invoke metadata
description: The process domain was unable to find any invoke messages with the specified where condition in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04101
severity: 10
type: error
name: Cannot find callback metadata
description: The process domain was unable to find any callback messages with the specified where condition in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04102
severity: 10
type: error
name: Cannot insert process event
description: The process domain was unable to insert the process event for process \"{0}\" (revision \"{1}\") in the datasource. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04103
severity: 10
type: error
name: Cannot find process events
description: The process domain was unable to find any process events with the specified where condition in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04104
severity: 10
type: error
name: Cannot find default revisions
description: The process domain was unable to find the default process revisions in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04105
severity: 10
type: error
name: Cannot update default revision
description: The process domain was unable to set the default revision for process \"{0}\", revision tag \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04106
severity: 10
type: error
name: Cannot delete default revision
description: The process domain was unable to delete the default revision for process \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04107
severity: 10
type: error
name: Cannot update lob column
description: The process domain was unable to update the lob column \"{0}\" in the datastore, for cube instance \"{1}\". The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04108
severity: 10
type: error
name: Cannot select attachment
description: The process domain was unable to select the attachent by the key \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04109
severity: 10
type: error
name: Cannot delete attachment
description: The process domain was unable to delete the attachent by the key \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04110
severity: 10
type: error
name: Cannot insert attachment
description: The process domain was unable to insert attachent into the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04111
severity: 10
type: error
name: Cannot fetch attachment reference
description: The process domain was unable to seelct the attachment reference \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04112
severity: 10
type: error
name: Cannot insert attachment reference
description: The process domain was unable to insert attachent reference into the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04113
severity: 10
type: error
name: Cannot delete attachment reference
description: The process domain was unable to remove attachent reference of instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04121
severity: 10
type: error
name: Cannot find test details
description: An attempt to fetch the test details using the where condition \"{0}\" from the datastore has failed. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04122
severity: 10
type: error
name: Cannot update test details
description: The process domain was unable to insert/update test details for instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04123
severity: 10
type: error
name: Cannot update delivery message batch
description: The process domain was unable to update the state of the following delivery messages \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04124
severity: 10
type: error
name: Cannot update delivery subscription batch
description: The process domain was unable to update the state of the following delivery subscriptions \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04125
severity: 10
type: error
name: Cannot select detail instances
description: The process domain was unable to select the number of detail instances for master instance specified by the conversation id \"{0}\".
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04126
severity: 10
type: error
name: Cannot select document reference key
description: The process domain was unable to select document references for instance id \"{0} \". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04127
severity: 10
type: error
name: Cannot select insert reference key
description: The process domain was unable to insert document references for instance id \"{0} \". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04128
severity: 10
type: error
name: Cannot select document reference key
description: The process domain was unable to select document references for delivery message guid \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04129
severity: 10
type: error
name: Cannot select insert reference key
description: The process domain was unable to insert document references for delivery message guid \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04130
severity: 10
type: error
name: Cannot select process descriptor
description: The process domain was unable to select the descriptor for process \"{0}\", revision \"{1}\" from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04131
severity: 10
type: error
name: Cannot insert/update process descriptor
description: The process domain was unable to insert/update the descriptor for process \"{0}\", revision \"{1}\" into the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04132
severity: 10
type: error
name: Cannot read clob stream
description: Cannot read clob stream from datastore with key \"{0}\"; exception is {1}
ORABPEL-04133
severity: 10
type: error
name: Cannot select process suitcase
description: The process domain was unable to select the bytes for suitcase \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04134
severity: 10
type: error
name: Cannot insert/update process suitcase
description: The process domain was unable to insert/update the process suitcase \"{0}\" into the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04135
severity: 10
type: error
name: Cannot delete process suitcase
description: The process domain was unable to delete the process suitcase \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04136
severity: 10
type: error
name: Cannot count suitcase processes
description: The process domain was unable to count the number of deployed suitcase processes. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04137
severity: 10
type: error
name: Cannot find test definition
description: An attempt to fetch the test definition for process \"{0}\", revision \"{1}\", test suite \"{2}\", location \"{3}\" from the datastore has failed. The exception reported is: {4}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04138
severity: 10
type: error
name: Cannot store test definition
description: The process domain was unable to store the test definition for process \"{0}\", revision \"{1}\", test suite \"{2}\", location \"{3}\" in the datastore. The exception reported is: {4}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04139
severity: 10
type: error
name: Cannot delete test definition
description: The process domain was unable to delete the test definition for process \"{0}\", revision \"{1}\", test suite \"{2}\", location \"{3}\" in the datastore. The exception reported is: {4}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04140
severity: 10
type: error
name: Cannot delete test definitions
description: The process domain was unable to delete test definitions for process \"{0}\", revision \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04141
severity: 10
type: error
name: Cannot delete process events
description: The process domain was unable to delete the events logged for process \"{0}\", revision \"{1}\" from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
ORABPEL-04142
severity: 10
type: error
name: Cannot delete process events
description: The process domain was unable to delete the events logged for in the domain. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
Comments