73 ORABPEL-00006 to ORABPEL-20511

ORABPEL-00006: failure to load the JCE cipher "{0}"

Cause: The environment may not have been set correctly.

Action: JCE library files must be installed in the JRE installation as an extension. Copy the jar files from "{1}\install\java\jce1.2.2" directory to "(jdk_path)\jre\lib\ext" directory (where jdk_path is JDK installation directory).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00007: failure to decrypt cipher text with transformation "{0}"; exception reported is: {1}

Cause: This was an internal error. It may have been caused by an incorrect cipher state or an invalid padding size being specified.

Action: Contact Oracle Support Services. Provide the error message and the process that appeared to cause the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00008: failure to encrypt plain text with transformation "{0}"; exception reported is: {1}

Cause: This was an internal error. It may have been caused by an incorrect cipher state or an invalid padding size being specified.

Action: Contact Oracle Support Services. Provide the error message and the process that appeared to cause the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00015: failure to create jar file {0}

Cause: The Sun tools.jar may not have been installed on the local machine or included in the class path.

Action: Verify that tools.jar is installed on this machine and is included in the class path.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00016: failure to execute javac compiler on file(s) "{0}"; exception reported is: {1}

Cause: The Sun tools.jar may not have been installed on the local machine or included in the class path.

Action: Verify that tools.jar is installed on this machine and is included in the class path.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00017: failure to compile file(s) "{0}"; exception reported is: {1}

Cause: The generated Java class(es) had errors and/or all the required libraries to compile the class(es) were not available.

Action: Verify that the file named in the error message is valid Java file and that all required libraries are included in the class path.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00018: cannot find the Java source directory "{0}"

Cause: The specified Java source directory did not exist or it could not be written to.

Action: Create the source directory named in the error message and set the write permission accordingly.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00019: cannot create the Java destination directory "{0}"

Cause: The parent directory permissions prevented the creation of this directory.

Action: Verify that the parent directory for the directory named in the error message is writable.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00020: failure to write the Javadoc argument file "{0}"; exception reported is: "{2}"

Cause: The Javadoc file named in the error message was not written to the directory "{1}".

Action: Verify that the directory "{1}" can be written to.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00021: failure to execute Javadoc with the argument file "{0}"

Cause: The Javadoc executable was not found in the system path or was not executed.

Action: Verify that Javadoc is installed on this machine in the <JDK>\bin directory and that this directory is included in the machine system path.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00024: failure to schedule the "{0}" agent with the scheduler; exception reported is: {1}

Cause: The Quartz scheduler did not schedule the job named in the error message. This is typically an internal scheduler error.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00025: failure to unschedule the "{0}" agent with the scheduler; exception reported is: {1}

Cause: The Quartz scheduler did not unschedule the job named in the error message. This is typically an internal scheduler error.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00026: error while attempting to execute the job "{0}" for agent "{1}"; exception reported is: {2}

Cause: This error was a wrapper for an internal exception thrown by the underlying scheduler job.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00201: cannot return system authentication token for caller "{0}"

Cause: This was an internal error. The agent "{0}" was not added to the allowed callers list for the system token.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00209: The domain identifier "{0}" is not registered with the server.

Cause: All domain identifiers were kept in the domain table; this table may have been modified incorrectly.

Action: Restart the application server; if the domain directory is present, the identifier will be automatically registered again.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00210: domain ref "{0}" is not registered with the server.

Cause: All domain identifiers were kept in the domain table; this table may have been modified incorrectly.

Action: Restart the application server; if the domain directory is present, the identifier will be automatically registered again.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00214: The OraBPEL server has not finished initializing yet; the initialization process may be complete in a few moments.

Cause: A request was sent to the server before it finished initializing.

Action: Resubmit the request. If this does not solve the problem, check the logs (with logging level set to debug mode) for error messages.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00215: error while attempting to instantiate the JDK adapter class "{0}" for run-time version "{1}"; exception reported is: {2}

Cause: The JDK adapter class named in the error message was not in the system class path or there was an incompatibility with the JDK used to the compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00216: JDK adapter class "{0}" for run-time version "{1}" does not implement the IJDKAdapter interface

Cause: This was an internal error. All JDK adapters registered with the system must conform to the IJDKAdapter interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00217: JDK version "{0}" is not supported by the OraBPEL run-time; currently only JDK versions 1.4 and 1.5 are supported

Cause: A JDK adapter was not specified for the JVM version with which the container was started.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00219: cannot instantiate an instance for the class "{0}"

Cause: The class "{1}" was not granted sufficient permissions by the JVM to instantiate the class "{0}".

Action: Verify that the OraBPEL run-time class "{1}" has the necessary security permissions to access the class specified in the error message.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00220: class "{0}" (for the platform adapter for platform "{1}") does not implement the IPlatformAdaptor interface

Cause: This was an internal error. All platform adapters registered with the system must conform to the IPlatformAdaptor interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00221: error while attempting to instantiate the class "{0}" as the adapter for platform "{1}"; exception reported is: {2}

Cause: The platform adapter class "{0}" was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00222: class for platform adapter "{0}" (platform "{1}") cannot be found

Cause: The platform adapter class "{0}" was not in the system class path.

Action: Ensure that Oracle BPEL libraries are set correctly in the system class path.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00227: class "{0}" (for the database adapter for "{1}") does not implement the IDatabaseAdaptor interface

Cause: This was an internal error. All database adapters registered with the system must conform to the IDatabaseAdaptor interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00228: error while attempting to instantiate the class "{0}" as the database adapter, data source "{1}"; exception reported is: {3}

Cause: The database adapter class "{0}" was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00229: database adapter class name for data source "{0}" has not been specified

Cause: The database adapter class "{0}" was not in the system class path.

Action: Ensure that the Oracle BPEL libraries are set correctly in the system class path. If the libraries are configured correctly, the adapter configuration files may have been modified incorrectly.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00230: adapter resource file "{0}" cannot be found in the current class path

Cause: The resource file named in the error message contained all the JNDI mappings required for the BPEL process domain to initialize.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00231: error while attempting to instantiate the class "{0}" as the adapter manifest for "{1}", data source "{2}"; exception reported is: {3}

Cause: The adapter manifest class "{0}" was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00232: class "{0}" (for the adapter manifest for "{1}", data source "{2}") does not implement the IServerAdaptorManifest interface; all adapter manifests used by the OraBPEL server must implement this interface

Cause: This was an internal error. All adapter manifests registered with the system must conform to the IServerAdaptorManifest interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00233: adapter manifest class name for "{0}", data source "{1}" is not specified.

Cause: The adapter manifest class "{0}" was not in the system class path.

Action: Ensure that the Oracle BPEL libraries are set correctly in the system class path. If the libraries are configured correctly, the adapter configuration files may have been modified incorrectly.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00235: The component identifier "{0}" has not been registered with the server.

Cause: All component identifiers were kept in the "component" table; this table may have been modified incorrectly.

Action: Restart the application server; when the component is loaded, the identifier will be automatically registered again.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00236: The component reference "{0}" is not registered with the server.

Cause: All component references were kept in the "component" table; this table may have been modified incorrectly.

Action: Restart the application server; when the component is loaded, the reference will be automatically registered again.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00237: failure to create the component reference for "{0}"

Cause: The maximum number of components ({1}) were reached.

Action: Contact Oracle Support Services. At the current time, the maximum number of components has been set to 32767.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00238: exception while reading the component index from the data source; the exception reported is: {0}

Cause: There was a problem with connecting to the data source where the component index is stored.

Action: There are three things to verify. Verify that the machine hosting the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for the OraBPEL server has been installed in the data source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00239: exception while writing the component index (application_name "{0}", composite_name"{1}", revision "{2}", label "{3}", component_name "{4}") to the data source; the exception reported is: {5}

Cause: There was a problem with connecting to the data source where the component index is stored.

Action: There are three things to verify. Verify that the machine hosting the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for the OraBPEL server has been installed in the data source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00240: exception occurs while removing the component index (dn "{0}", ref "{1}") from the data source; the exception reported is: {2}

Cause: There was a problem with connecting to the data source where the component index is stored.

Action: There are three things to verify. Verify that the machine hosting the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for the OraBPEL server has been installed in the data source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01005: failure to compile the generated BPEL classes for BPEL process "{0}" of composite "{1}"

Cause: The class path setting is incorrect.

Action: Ensure that the class path is set correctly. If this happens on the server side, verify that the custom classes or jars which this BPEL process is depending on are deployed correctly. Also verify that the run time is using the same release/version.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01007: build directory "{0}" for the BPEL process "{1}" of composite "{2}" cannot be found or accessed

Cause: The compiler could not find or create the directory "{0}".

Action: Ensure that the parent directory of "{0}" is a valid directory and that it is not read-only.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01010: failure to generate the BPEL process file "{0}".

Cause: Could not generate named BPEL process file. The exception reported was "{1}".

Action: Ensure that the file "{0}" is a valid file to be generated.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-01027: trying to manipulate the nonexistent part "{1}" in a message of type "{0}"

Cause: An invalid request was made to manipulate the invalid part "{1}".

Action: Ensure that the client request is correct.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01028: cannot find propertyAlias definition that associates the BPEL correlation "{0}" of correlationSet "{1}" to messageType "{2}"

Cause: A propertyAlias must be defined to associate the BPEL correlation to a correlationSet. The run time could not find it.

Action: Ensure that the mentioned propertyAlias is in one of the WSDL files that are referenced by the composite. Redeploy the composite.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01029: cannot find property definition for "{0}" in any of the WSDL files

Cause: The BPEL correlation property needs to be defined. But the run time could not find it.

Action: Define the mentioned BPEL property in one of the WSDL files referenced by the composite.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01030: cannot generate debug model file "{0}"

Cause: The named BPEL debug model file was not generated. The exception reported was: "{1}".

Action: Correct the error reported by the error message.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01032: specified process ID "{0}" is invalid

Cause: The specified process identifier did not follow the naming constraints.

Action: Valid process identifiers might start with a letter, a ''$'' or ''_'' character; process characters (other than the first character) include a letter, a digit, a ''$'', a ''_'' or ''-'' character. The max length permitted is 100. Ensure that the component name specified in the composite descriptor conforms to the above mentioned constraints.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02000: The class "{0}" for the block element "{1}" does not implement the ICubeBlock interface.

Cause: This was an internal error. All block elements contained within the process domain must implement this interface.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02001: error while attempting to instantiate the class "{1}" for the block element "{0}"; exception reported is: {2}

Cause: This was an internal error. The block class "{0}" was not in the composite class path, or there was an incompatibility with the JDK used to the compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02002: block element "{0}" missing its class name; this element cannot be created without its class name

Cause: This was an internal error. The block element class "{0}" was not in the composite class path.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02003: A Cube element is missing its "ID" property. Every Cube element in the process domain is uniquely identified by its "ID" property.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02005: The parent block element "{0}" specified by node or block element "{1}" is not defined in the service class map. All nodes or blocks contained in the map must be bound to a valid parent block element.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02006: The node or block element "{0}" is missing a parent block identifier. All nodes or blocks contained in the service class map must be bound to a parent block element.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02007: Multiple method block elements are specified in the service class map. A valid map can only contain one method block element.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02008: No block elements are specified in the service class map. All valid maps must contain at least one block element (the root block).

Cause: This was an internal error. The block map was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02009: No node elements are specified in the service class map. All valid maps must contain at least one node element.

Cause: This was an internal error. The block map was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02010: No method block element is specified for the service class map. All valid maps must contain one method block element.

Cause: This was an internal error. The block map was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02011: The class "{0}" for the node element "{1}" does not implement the ICubeNode interface.

Cause: This was an internal error. All node elements contained within the process domain must implement this interface.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02012: error while attempting to instantiate the class "{1}" for the node element "{0}"; the exception reported is: {2}

Cause: This was an internal error. The node class "{0}" was not in the composite class path or there was an incompatibility with the JDK used to the compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02013: The class "{0}" cannot be found in the current class path.

Cause: This was an internal error. The node element class "{0}" was not in the composite class path.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02014: The node element "{0}" is missing its class name; this element cannot be created without its class name.

Cause: This was an internal error. The node class name should be generated by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02015: The BPEL process "{0}" (revision "{1}") has been compiled with an older version of SCAC; current BPEL process domain cannot execute this process.

Cause: An attempt to deploy a process that was compiled with an older version of SCAC failed.

Action: Recompile the BPEL process using the SCAC tool bundled with the current process domain.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02016: The process "{0}" is not initializing because of the error: "{1}".

Cause: This error contained the exceptions thrown by the underlying process loading module.

Action: Check for possible cause in the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02017: cannot compress the data stream with GZIP algorithm; exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying compression layer.

Action: Check for possible cause in the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02018: cannot uncompress the data stream with GZIP algorithm; exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying compression layer.

Action: Check for possible cause in the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02019: cannot compute the md5 checksum; exception reported is: {0}

Cause: This error contained exceptions thrown by the underlying digest layer.

Action: Check for possible cause in the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02020: failure to serialize the audit trail for instance "{0}" to its binary representation; exception reported is: {1}

Cause: This was an internal error. This error contained the exceptions thrown by the underlying XML marshalling module.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02022: The value "{0}" for the tag "{1}" in the XML serialized text for the audit trail for instance "{2}" is not a numeric value.

Cause: The tag "{1}" did not contain a numeric value.

Action: Ensure that the value for tag "{1}" conforms to the expected numeric format.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02023: failure to activate the block "{0}" for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02024: failure to invoke the method "until" on the block "{0}" for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02025: failure of the block "{0}" to handle a business exception for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02026: failure to invoke the canActivate method on the block "{0}" for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02027: failure to deserialize the instance "{0}" from binary format; exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02028: failure to serialize the instance "{0}" to binary format; exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02029: The process domain cannot create the bean "{0}"; this bean is responsible for generating a unique key for a new instance. The exception reported is: "{1}".

Cause: The SOA application or class path was not configured correctly.

Action: Verify that the instance key generator bean has been properly deployed to the server and can be properly mounted from a java class.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02030: failure to marshall the instance "{0}" to XML format; exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02031: The instance "{0}" is created from the domain "{1}"; the current domain is "{2}". A process can be loaded only from the domain from which it was created.

Cause: The instance was not accessed because it was created in a different domain.

Action: If this instance is being accessed from the API, try looking up the instance "{0}" from the "{1}" domain (change the domain ID parameter to the Locator initializer).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02032: The instance "{0}" is created with process guid "{1}"; the current guid for the process "{2}" (revision "{3}") is "{4}".

Cause: Whenever a process is deployed on top of an existing process with the same process ID and revision tag, all instances created from the previous process are marked as stale.

Action: If this instance is being accessed from the console, the browser may be referring to an out-of-date page; click the Instances tab to get the current list of active instances.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02033: failure to construct a valid instance key from the string "{0}"; exception reported is: {2}

Cause: The instance did not consist of a single integer value.

Action: If the instance key has not been constructed by the process domain, ensure that the key format is valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02037: exception while trying to create a context object; the exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying JNDI environment.

Action: Verify that the directory service on the application server has been configured correctly.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02038: The process domain is unable to look up the context object using the bind name "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying JNDI environment.

Action: Verify that the JNDI identifier is valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02040: exception while trying to destroy a context object; the exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying JNDI environment.

Action: Verify that the directory service on the application server has been configured correctly.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02041: The action "{0}" cannot be performed on the instance "{1}" because of its current state ("{2}").

Cause: The current instance state did not allow the requested action to be performed.

Action: Consult the product documentation for a list of all the permissible actions that can be performed on an instance when it is in the "{2}" state.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02042: The action "{0}" cannot be performed on the work item "{1}" because of its current state ("{2}").

Cause: The current work item state did not allow the requested action to be performed.

Action: Consult the product documentation for a list of all the permissible actions that can be performed on a work item when it is in the "{2}" state.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02043: The action "{0}" cannot be performed on the scope "{1}" because of its current state ("{2}").

Cause: The current scope state did not allow the requested action to be performed.

Action: Consult the product documentation for a list of all the permissible actions that can be performed on a scope when it is in the "{2}" state.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02044: The process domain is failing to write the audit trail for instance "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying persistence framework.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02046: The process domain is failing to write the debug trace for instance "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization layer.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02047: The process domain is failing to write the instance trace for instance "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization layer.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02048: The process domain is unable to handle the work item "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying process execution layer.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02050: The invocation for method "{0}" on the instance "{1}", process "{2}" (revision "{3}") is cancelled. The return value for this method cannot be determined in this case.

Cause: The instance "{1}" was cancelled or aborted.

Action: Check the audit trail for instance "{1}" for more information.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02051: The invocation for method "{0}" on the instance "{1}", process "{2}" (revision "{3}") is not complete. The return value for this method cannot be fetched until the method has completed.

Cause: The instance "{1}" was not complete yet.

Action: Resubmit this request after several minutes. Note that the method may contain some asynchronous interactions that could take an indeterminate amount of time to complete.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02052: The BPEL domain "{0}" is missing.

Cause: The BPEL domain "{0}" may not have initialized properly.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02053: The BPEL domain "{0}" is not finished initializing yet.

Cause: The domain initialization procedure was not finished yet.

Action: Resubmit the request in few minutes. The initialization progress can be monitored in the server log; set the logging level to debug mode.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02054: The BPEL domain "{0}" is currently uninitializing; the domain may not be accessed.

Cause: The domain was uninitializing.

Action: Restart the application server. If the domain uninitialized due to an exception, check the server log for the underlying exception trace (be sure to set the logging level to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02055: failure to handle a fault thrown from a scope, by any blocks in the scope chain

Cause: This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope.

Action: A top-level fault handler should be added to the flow to handle faults not caught from within the flow.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02057: The block element "{0}" is not defined in the service class map.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02058: The node element "{0}" is not defined in the service class map.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02059: The process domain is unable to fetch the work item "{0}" from the memory repository.

Cause: This was an internal error. The work item was not correctly registered from the previous transaction.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02060: failure to activate the node "{0}" for the instance "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying routing subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the instance.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02061: failure to finalize the node "{0}" for the work item "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying routing subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02062: failure to invoke the canActivate method on the node "{0}" for the instance "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying routing subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the instance.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02063: failure to deserialize the delivery callback messages for conversation "{0}", message "{1}" from the binary format; the exception reported is: {2}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02064: failure to serialize the delivery callback messages for conversation "{0}", message "{1}" to the binary format; the exception reported is: {2}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02065: failure to serialize the delivery properties for conversation "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02066: failure to deserialize the delivery properties for conversation "{0}" from the binary format; the exception reported is: {1}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02067: failure to marshall the delivery callback messages for conversation "{0}", message "{1}" to XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02068: Failure to call method "{0}" of the delivery persistence service with parameter "{1}". This operation is not supported.

Cause: This was an internal error. Delivery persistence service does not support advanced persistence features such as lazy loading. The persistence manager should not have used those related operations.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02069: The delivery service fails to load the message content from the data store; the exception reported is: {0}

Cause: This was an internal error. Either the load() method was not working properly if the object type was imported into the process, or the delivery message content might have been edited manually in the data store.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02070: The delivery service fails to store the object "{0}" of type "{1}" to the data source. The exception reported is: {2}

Cause: This was an internal error. The save() method was not working properly if the object type was imported into the process.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02071: failure to copy the object "{0}" of type "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02072: failure to release the moniker "{0}"; the exception reported is: {1}

Cause: An attempt was made to remove the last reference to a moniker before the object referred to by the moniker had been loaded.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02073: failure to delete the object "{0}" of type "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02074: The target element with ID "{0}" cannot be located in the current XML document. The node "{1}" has a reference link to this element.

Cause: The document was corrupt; it might have been edited manually.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02075: The element "{0}" does not have an "xsi:type" attribute specifying the schema type of the underlying Java object. An XML fragment cannot be properly unmarshalled to its Java representation without this information.

Cause: The document was corrupt; it might have been edited manually.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02076: failure to deserialize an object from its moniker format; the exception reported is: {0}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the deserialization failure.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02077: Assertion failure: object "{0}" has negative reference count "{1}".

Cause: This was an internal error. An object had a reference count less than zero because it fell out of scope and had its reference count decremented.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02078: failure to marshall the object "{0}" of type "{1}" to XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02079: failure to prepare the object "{0}" of type "{1}" for marshalling; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02080: failure to prepare the object "{0}" of type "{1}" for saving; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02081: failure to read an object's moniker from the deserializer stream; the exception reported is: {0}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02082: failure to save the object "{0}" of type "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02083: failure to unmarshall the object "{0}" of type "{1}" from XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02084: failure to write an object's moniker into the serializer stream; the exception reported is: {0}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02085: The metadata for object "{0}" is not registered with the persistence service.

Cause: This was an internal error. Every Java object type in the scope must be registered.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02086: The metadata for object "{0}" does not contain an embedded moniker.

Cause: This was an internal error. One or more of the linked variants in the scope did not contain an embedded moniker that contained the actual bytes defining the object.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02087: The node "{0}" is missing its reference identifier.

Cause: This was an internal error. Any element with an "href" attribute did not contain a non-empty reference ID that could be resolved to another element in the document.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02088: An instance's root scope cannot be routed.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02089: failure to construct a valid scope activation key from the string "{0}".

Cause: This was an internal error. The expected format was: "param1-param2", where the two parameters were: instance ID (integer) and scope ID (string) respectively.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02090: failure to unmarshall the metadata for the scope tree of instance "{0}"; the exception reported is: {1}

Cause: This was an internal error. A variant's metadata did not contain "guid", "class name" and "ref-count" attributes; or the "ref-count" attribute was not an integral value while it should be.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02091: failure to release an instance's root scope from the scope tree.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02092: failure to unmarshall a scope for the instance "{0}" from an XML document; the exception reported is: {1}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the instance.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02093: The tag "{0}" is missing from the serialized XML text for the scope data for the instance "{1}".

Cause: This was an internal error. The XML document for this instance did not contain a value for the tag named in the error message.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02094: The scope "{0}" is not defined in the current instance.

Cause: This was an internal error. The scope was either closed or released, and it was not reachable.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02095: The scope associated with the block element "{0}" is not defined in the current instance.

Cause: This was an internal error. The scope metadata was corrupt.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02096: The value "{0}" for the tag "{1}" in the serialized XML text for instance "{2}" is not a parseable integral value.

Cause: This was an internal error. The value for tag named in the error message did not conform to the expected format.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02097: cannot read the XML model file for process "{0}" (revision "{1}"); the exception reported is: {2}

Cause: An exception was thrown by the underlying operating system.

Action: Verify that the BPEL archive for the process named in the error message (for the cited revision) has been deployed correctly.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02100: cannot find the content file "{0}" for process "{1}" (revision "{2}").

Cause: The content file named in the error message might not have been deployed with the process named in the error message.

Action: Verify that the path named in the error message is correct, and that it refers to a file that has been included as a part of the deployment archive.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02101: cannot read the content file "{0}" for process "{1}" (revision "{2}"); the exception reported is: {3}

Cause: The content file named in the error message might not have been deployed with the process named in the erorr message.

Action: Verify that the path named in the error message is correct, and that it refers to a file that has been included as a part of the deployment archive.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02102: Method "{0}" is missing.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02103: The map for node element "{0}" is not defined in the process class.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02104: New instances cannot be created when the process "{0}" is not active; existing instances are permitted to complete as usual.

Cause: The process named in the error message was not active and therefore could not create new instances.

Action: The process life cycle can be changed to active through the EM console.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02106: The process "{0}" has not been turned on. No operations can be performed on the process or any instance belonging to the process if the process is turned off.

Cause: The process named in the error message was not turned on; therefore it did not process any requests.

Action: Consult the administrator if this process has not been turned on.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02107: The process domain is unable to fetch the scope activation message with key "{0}" from the data source.

Cause: The scope activation message with the key named in the error message was not found in the data source.

Action: This row may have been manually removed from the data source; in which case the instance should be aborted.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02108: cannot create a copy of the scope "{0}"

Cause: This was an internal error. Scopes are not cloneable.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02109: The process domain is unable to deserialize the scope data for instance "{0}" from its binary representation; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02110: failure to marshall the scope data for instance "{0}" into XML; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02111: failure to serialize the scope data for instance "{0}" into a binary byte stream; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02112: The absolute scope ID "{0}" does not conform to the expected format for a scope identifier.

Cause: This was an internal error. The expected scope ID format is (block id + relative scope id).

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02113: failure to fetch the return or header value from the root scope.

Cause: This was an internal error. Only top-level scopes can contain return or header values.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02114: The requested variant "{0}" is not a primitive variant type. Reference variants cannot be cast to a primitive type.

Cause: This was an internal error. The code accessing the variant named in the error message was assuming that that variant was a reference variant.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02115: The requested variant "{0}" is not a reference variant type. Primitive variants cannot be cast to a reference type.

Cause: This was an internal error. The code accessing the variant named in the error message was assuming that that variant was a primitive variant.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02116: The variant object associated with key "{0}" in the scope tree is neither a primitive nor a reference variant.

Cause: This was an internal error. The type of the declared variant "{0}" in the scope tree is not contained in the list of supported types (serializable and deserializable), including primitive (all Java primitive types) and reference (java.lang.String, java.util.Date, BPEL documents, EJB entity beans and one-dimensional arrays of any primitive or reference type).

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02117: A variable with key "{0}" is already declared in the current scope.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02118: The variable "{0}" is not declared in the current scope. All variables must be declared in the scope before being accessed.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02121: failure to marshall the object "{0}" of class "{1}" to XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the marshalling failure.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02122: The type class "{0}" is missing a "{1}" tag.

Cause: The XML fragment for this type was missing a required tag; the XML document might have been edited manually.

Action: Set the logging level to debug mode. Check the log for the any exception related to the type class.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02123: The value "{0}" of the tag "{1}" in the serialized XML text for the type class "{2}" is not a parseable integral value.

Cause: The value for the tag named in the error message did not conform to the expected format.

Action: Set the logging level to debug mode. Check the log for the any exception related to the type class.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02124: failure to deserialize the work item "{0}" from the binary format; the exception reported is: {1}

Cause: This error contained the exceptions thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02125: failure to serialize the work item "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02126: failure to deserialize the work items for instance "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the instance.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02127: failure to serialize the work items for instance "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the instance.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02128: failure to marshall the work item "{0}" to the XML format; the exception reported is: {1}

Cause: An exception was thrown from the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02129: cannot construct a valid work item key from the string "{0}"

Cause: The string was of wrong format to construct a valid work item key. The expected key format is: "param1-param2-param3-param4", where the parameters are: instance ID (integer), node ID (string), scope ID (string) and count ID (integer) respectively.

Action: If the work item key string has not been constructed by the process domain, ensure that the key format is valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02130: The tag "{0}" is missing from the serialized XML text for work item "{1}".

Cause: The XML document for this instance was missing a value for the tag named in the error message.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02131: The activity "{0}" is throwing a null exception.

Cause: This was an internal error. Exceptions thrown from the activity cannot be null.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02132: The value "{0}" for the tag "{1}" in the serialized XML text for work item "{2}" is not a parseable integral value.

Cause: The value for tag "{1}" was not an integer.

Action: If the work item XML has not been constructed by the process domain, ensure that the XML format is valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02133: error while attempting to expire the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02134: error while attempting to extend the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02135: error while attempting to execute the manage method on the work manager for node "{0}"; the exception reported is: "{1}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the node.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02136: error while attempting to resume the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02137: error while attempting to suspend the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02138: The method invocation "{0}" is returning an invalid number of callback arguments.

Cause: This was an internal error. More than one return value was returned. Currently, a maximum of one return value is permitted from a method invocation; the actual number of values returned for this invocation was "{1}".

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02139: The method invocation "{0}" is throwing an invalid exception object.

Cause: This was an internal error. The exception object did not extend the Throwable class. The object thrown was of class "{1}".

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02140: failure to invoke the method "{0}" on the performer "{1}"; the exception reported is: "{2}"

Cause: An exception was thrown while performing a callback to an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the performer.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02141: error while attempting to execute the cancelPerform method on the work performer for node "{0}"; the exception reported is: "{1}"

Cause: An exception was thrown while canceling an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the node.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02142: error while attempting to execute the perform method on the work performer for node "{0}"; the exception reported is: "{1}"

Cause: An exception was thrown while executing an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the node.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02143: error while attempting to throw the exception "{0}" from the activity "{1}"; the exception reported is: "{2}"

Cause: An exception is thrown while throwing an exception from an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the activity.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02149: The instance identifier "{0}" is missing its domain ID; this ID specifies the BPEL domain from which the instance is generated.

Cause: This was an internal error. The instance domain ID was not set upon creation and rehydration.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02150: The process domain is unable to fetch the activity "{0}" from the data source.

Cause: The activity key "{0}" did not refer to a valid activity, or the activity was removed from the data source.

Action: Check the work_item database table with the activity key; if the referred row cannot be found, check the audit trail for the instance.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02151: More than one activity from domain "{1}" is returned when querying with the key "{0}".

Cause: Multiple activities were bound to the custom key "{0}". Only one activity should be returned per key.

Action: If the key is a user-specified custom key, ensure that the key is unique.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02152: The process domain is unable to fetch the instance with key "{0}" from the data source.

Cause: The instance key "{0}" did not refer to a valid instance, or the instance was removed from the data source (this might have been the case if the BPEL global transaction was modified by an external source).

Action: Check the cube_instance database table with the instance key; if the referred row cannot be found, check the server logs for traces related to this instance key.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02154: Multiple instances are returned when querying with the key "{0}", while only one instance is expected.

Cause: Multiple instances of a business process were created with the key "{0}". Each instance should be uniquely identified by a key.

Action: If the key is a user-specified custom key, ensure that the key is unique.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02155: The process domain is unable to fetch the bytes for the business document "{0}" from the data source.

Cause: The document key "{0}" did not refer to a valid document, or the document was removed from the data source.

Action: Check the xml_document database table with the document key; if the referred row cannot be found, check the server logs for traces related to this document key.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02156: The process domain is unable to fetch the scope context data for the instance with key "{0}" from the data source.

Cause: The instance key "{0}" did not refer to a valid instance, or the instance was removed from the data source.

Action: Check the cube_scope database table with the instance key; if the referred row cannot be found, check the server logs for traces related to this instance key.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02157: failure to read the audit trail for instance "{0}"; the exception reported is: {1}

Cause: An exception was thrown while writing the audit trail bytes to the in-memory buffer after those bytes were read from the data store.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace related to this in-memory buffer writing problem.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02158: failure to create the scope deserializer object for instance "{0}"; the exception reported is: {1}

Cause: An exception was thrown while creating a deserializer from the scope bytes.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace related to this deserializer creation problem.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02159: The process domain is unable to fetch the invocation content for the message "{0}" from the data source.

Cause: The message key "{0}" did not refer to a valid invocation message, or the invocation message was removed from the data source (this might have been the case if the BPEL global transaction was modified by an external source).

Action: Check the invoke_message database table with the message key; if the referred row cannot be found, check the server logs for traces related to this message key.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02160: The process domain is unable to fetch the callback content for the message "{0}" from the data source.

Cause: The message key "{0}" did not refer to a valid callback message, or the callback message was removed from the data source (this might have been the case if the BPEL global transaction was modified by an external source).

Action: Check the dlv_message database table with the message key; if the referred row cannot be found, check the server logs for traces related to this message key.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02161: The process domain is unable to fetch the audit detail bytes for the instance "{0}", detail ID "{1}" from the data store.

Cause: The instance identifier "{0}" or detail identifier "{1}", or both, did not refer to a valid entry in the audit_details table; this row might have been manually removed from the table.

Action: Check the audit_details database table with the identifiers named in the error message; if the referred row cannot be found, check the server logs for traces related to these identifiers.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02162: The instance index "{0}" is not within the valid range.

Cause: The index "{0}" for instance "{1}" was out of range.

Action: Change the index value in the xpath function or the facade API call to conform to the valid index range. Try a value between 1 and {2} (inclusive).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02163: cannot access scope "{0}"; scope is already released

Cause: This was an internal error. An attempt was made to access a scope that has already been released.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02164: An unknown cache policy "{0}" is specified for property "{1}".

Cause: The cache policy "{0}" was not recognized. The list of valid cache policies is { lru, auto, soft-filo, soft-lru, hybrid }.

Action: Change the cache policy configuration property to one of the recognized values. The valid cache policies are lru, auto, soft-filo, soft-lru, and hybrid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02165: cannot initialize connection pool for connection factory "{0}"; the reason is {1}

Cause: An exception was thrown while initializing the JMS connection pool.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02166: failure to finalize the compensation node "{0}" for the second time; the exception reported is: {1}

Cause: An exception was thrown while attempting to execute a compensation activity.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02167: The process ("{1}", revision "{2}") for instance "{0}" is not loaded by the domain; the instance is marked as stale.

Cause: The archive for process "{1}" of revision "{2}" might have been deleted from the domain manually. In this case, the domain would not have been able to mark all instances that belonged to the process as being stale.

Action: Check if the process has been manually deleted from the domain.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02168: A problem occurs while reading the sensor file "{0}"; the exception reported is: {1}

Cause: An exception was thrown while trying to access the sensor file named in the error message.

Action: Ensure that the file exists. If it has been manually deleted, then redeploy the process.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02169: A problem occurs while reading the sensor action file "{0}"; the exception reported is: {1}

Cause: An exception was thrown while trying to access the sensor action file named in the error message.

Action: Ensure that the file exists. If the file has been manually deleted, then redeploy the process.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02171: A problem occurs while updating the label status "{0}" in instance "{1}".

Cause: This label was not detected during process compilation.

Action: Redeploy the process and try again. If the redeployment step does not work, then contact Oracle Support Services. Provide the error message, the composite source, and the exception trace in the server log files (with the logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02177: failure to create the data source "{0}"; the exception reported is: {1}

Cause: An exception was thrown while attempting to create a data source.

Action: Set the logging level to debug mode, check the log for the underlying exception trace related to this data source creation problem.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02178: the BPEL process "{0}" with revision "{1}" is not loaded.

Cause: The process was not initialized properly, or the process was disabled.

Action: Set the logging level to debug mode, check the log for the underlying exception trace related to this process loading problem.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02180: The current JTA transaction is aborting due to a user rollback fault being thrown.

Cause: This exception was caused by a bpelx:rollback fault being thrown or a ROLLBACK_ONLY FabricInvocationException being thrown. BPEL engine is directed to roll back the current JTA transaction.

Action: There is no action recommended.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02181: The current JTA transaction is marked as rollback-only when performing the activity "{0}".

Cause: The reason was {1}.

Action: Check on the activity which invokes a subprocess or downstream process that results in the JTA transaction being marked as rollback-only.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02182: catching unhandled fault "{0}" when processing instance "{1}" for process "{2}"

Cause: The exception was {3}.

Action: Check the error log file and the audit trail for instance "{1}" for more information. Try to use BPEL fault handlers to catch the faults in the BPEL process "{2}". If this is a system exception, please report this to the system administrator.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02183: bpel engine can not execute activities without an active transaction. please debug the invoked subsystem on why the tranasction is not in active status. the bpel instance id is "{0}".

Cause: The reason was {1}.

Action: Consult the system administrator regarding this error.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02184: The process domain was unable to serialize the activity guide milestone state data for instance "{0}" into a binary byte stream. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown from the underlying serialization sub-system.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02185: The process domain was unable to deserialize the activity guide milestone state data for instance "{0}" from its binary byte representation. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown from the underlying serialization sub-system.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02186: The process domain was unable to fetch the activity guide instance with key "{0}" from the datasource.

Cause: The instance key "{0}" does not refer to a valid activity guide instance, or the instance has been removed from the datasource (this may be case if the BPEL global transaction has been modified by an external source).

Action: Check the "ag_instance" database table; if the row cannot be found, check the server logs.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02187: Failed to load activity guide instance with key "{0}" from the datasource. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown while loading activity guide instance from the datasource.

Action: Please check the log for the underlying exception trace. Be sure to set the logging level to debug mode.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02188: Failed to insert activity guide instance with key "{0}" to the datasource. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown while inserting activity guide instance to the datasource.

Action: Please check the log for the underlying exception trace. Be sure to set the logging level to debug mode.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02189: Failed to update activity guide instance with key "{0}" in the datasource. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown while updating activity guide instance to the datasource.

Action: Please check the log for the underlying exception trace. Be sure to set the logging level to debug mode.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02190: Failed to evaluate expression "{0}" in field "{1}" in activity guide instance with key "{2}". The exception reported is: "{3}"

Cause: The expression may not have been constructed correctly.

Action: Make sure that the expression is constructed correctly.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02191: The activity guide definition at "{0}" could not be read.

Cause: The activity guide definition either is missing or invalid.

Action: Make sure that the activity guide definition is available at the specified URL and that it is a valid XML document.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02192: The activity guide definition at "{0}" does not conform to the activity guide definition XML schema definition. The errors are "{1}"

Cause: The activity guide definition does not conform to the activity guide definition XML schema.

Action: Make sure that the activity guide definition conforms to the activity guide definition XML schema definition.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02193: The activity guide definition at "{0}" could not be validated against the activity guide definition XML schema definition.

Cause: The activity guide definition is missing.

Action: Make sure that the activity guide definition is available at the specified URL and that it is a valid XML document.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02194: The milestone instance with name "{0}" cannot be found in activity guide instance with ciKey "{1}".

Cause: This is an internal error. This may have been caused by some logical errors in the program.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02195: The "{0}" operation on milestone "{1}" with status "{2}" in activity guide instance "{3}" is invalid. This operation can only be performed on milestones with status "{4}".

Cause: This is an internal error. This may have been caused by some logical errors in the program.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02196: The "{0}" operation on activity guide instance "{1}" with status "{2}" is invalid. This operation can only be performed on activity guide instances with status "{3}".

Cause: This is an internal error. This may have been caused by some logical errors in the program.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02197: The "{0}" operation on activity guide instance "{1}" for milestone "{2}" is invalid.

Cause: The milestone's expiration date is not set or milestone is configured to continue post expiration

Action: Please check configuration settings for the milestone "{2}") in BPEL designer.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02198: The current JTA transaction is aborting due to an user rollback fault being thrown. The upstream component should retry in a new JTA transaction upon catching this fault.

Cause: This exception was caused by a global retry fault being thrown from downstream component. The user had directed the BPEL engine to roll back the current JTA transaction and retry within new JTA transactions for the specified number of times and retry interval.

Action: There is no action recommended.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02199: The transaction became inactive when executing activity "{0}" for instance "{1}", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "{2}".

Cause: The reason was {3}.

Action: Consult the system administrator regarding this error.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02200: Master conversation ID is not available in context when executing work item "{0}" in component "{1}".

Cause: Master conversation ID was not supplied by the master process when initiating the call to the detail process.

Action: Make sure the master process's invoke activity to have bpelx:invokeAsDetail and bpelx:detailLabel attributes properly supplied.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02201: The process "{0}" has been suspended. No operations can be performed on the process or any instance belonging to the process if the process is suspended.

Cause: The process is suspended; therefore it did not process any requests.

Action: Consult the administrator if this process has been suspended.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02202: The process domain is unable to create Workitem for the activity "{0}"

Cause: Refer to cause

Action: Refer to cause for an action

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02203: Model.xml file not found for component "{0}"

Cause: Model.xml file was not generated for the component

Action: If component is BPEL 2.0, Model.xml file is not needed and thus does not get generated and this error is expected

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03001: The process domain is unable to determine the database type. The version table contains the vendor type for the current data source. The exception reported is: {0}

Cause: There was a problem with connecting to the data source where the version information was stored.

Action: Check all of the following to determine the location of the problem with connecting to the data source. Verify that the machine that hosts the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for OraBPEL has been installed in the data source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03002: The server is unable to look up the database schema version.The exception reported is: {0}

Cause: There was a problem with connecting to the data source where the version information is stored.

Action: Check all of the following to determine the location of the problem with connecting to the data source. Verify that the machine that hosts the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for OraBPEL has been installed in the data source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03003: The database schema version {0} from the database does not match the version {1} expected by the server.

Cause: The database schema for the SOA installation was not properly installed, or the installation was using a database schema installed for a prior release.

Action: The database schema currently in place has probably been configured for a previous release. Reinstall the database schema and start the server again.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03004: The database table "version" does not contain a data source vendor type

Cause: The database schema may have been modified by hand.

Action: Reinstall the database schema and start the process domain again.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03005: The database table "version" does not contain a version guid.

Cause: The database schema may have been modified by hand.

Action: Reinstall the database schema and start the server again.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03010: error while trying to instantiate the class {0} as the adapter manifest for {1}, data source {2}, the exception reported is: {3}

Cause: The adapter manifest class named in the error message was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03011: The class {0} (for the adapter manifest for {1}, data source {2}) does not implement the IServerAdaptorManifest interface

Cause: This was an internal error. All adapter manifests registered with the system must conform to the IServerAdaptorManifest interface, and this one does not.

Action: Contact Oracle Support Services. Be sure to provide the error message and the exception trace in the log files (with loggers set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03012: The adapter manifest class name for {0}, data source {1} is not specified

Cause: The adapter manifest class named in the error message was not in the system class path.

Action: Ensure that the Oracle BPEL libraries are set correctly in the system class path. If the libraries are configured correctly, the adapter configuration files might have been modified.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03013: cannot instantiate an instance for the class {0}

Cause: This was an internal error. Java class {0} that must be dehydrated or rehydrated within the OraBPEL server must implement the java.io.Serializable interface. And it must implement a default constructor.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03410: error while trying to instantiate the agent class {0}; The exception reported was: {1}

Cause: The agent class might have relied on a class that was not found in the class path, or it might have relied on a JDK feature that was not compatible with the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03411: invalid agent class

Cause: This was an internal error. The agent class {0} did not implement the IAgent interface. All agents managed by the system must implement this interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03800: The process domain is not able to resolve which correlation set definition to apply to the received callback message for the operation {0}.

Cause: Correlation set definitions were registered with the process domain using operation name and process ID. The callback message was most likely missing the process ID.

Action: If the callback client is external, check that the callback URL contains the process identifier. If the client is another BPEL process, check that the correlation set is defined correctly in the receiving BPEL process.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03801: The received callback message is missing the operation name parameter. The process domain cannot resolve which correlation set definition to apply to the message without this parameter.

Cause: The callback message did not pass the operation name in the SOAP action property.

Action: If the callback client is external, check that the operation name is being passed in the message correctly. If the client is another BPEL process, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03802: The correlation set definition for operation {0}, process {1}, is not registered with the server.

Cause: The correlation set was not defined in the process.

Action: Redeploy the process to the container.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03803: The process domain cannot look up the engine bean; this bean is responsible for processing the callback of a received message. The exception reported is: {0}

Cause: This was an internal error. The SOA installation was not configured properly.

Action: Check that the engine bean has been properly deployed to the server and can be properly mounted from a Java class.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03804: The synchronous polling thread is timing out waiting for a result from instance "{0}".

Cause: The callee was a durable synchronous process that had not reached its reply activity within the allotted timeout period.

Action: There may be a problem completing instance named in the error message. Check the process console for more information.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03805: The process domain is unable to find the protocol handler for the conversation type "{0}".

Cause: This was an internal error. Only the SOAP protocol handler is active by default.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03806: The process domain is unable to process the callback for received message "{0}", for conversation "{1}", and the subscriber "{2}". The exception reported is: {3}

Cause: This error contained exceptions thrown from the underlying callback handler layer.

Action: Check the exception trace in the log (with the logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03810: A similar receive activity is being declared in the same process.

Cause: Another receive activity or equivalent (currently, onMessage branch in a pick activity) has already been enabled with the partnerLink "{0}", operation name "{1}" and correlation set "{2}" (or conversation ID). Appendix A - Standard Faults in the BPEL 1.1 specification specifies a fault should be thrown under these conditions.

Action: Redeploy the process after removing the conflicting receive activities.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03811: No correlation sets are defined for operation "{0}" (process "{1}").

Cause: There were no correlation sets defined for the operation and process named in the error message. All receive operations that do not use WS-Addressing to correlate messages must define at least one correlation set.

Action: Check the BPEL source to ensure that at least one correlationSet is defined for the operation named in the error message.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03812: cannot find the property alias "{0}", message type "{1}"

Cause: The property alias named in the error message was not defined in the BPEL/WSDL source.

Action: Check the BPEL/WSDL source to ensure that the property alias named in the error message has been defined.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03813: failure to evaluate the correlationAlias query "{0}" on the element "{1}".

Cause: The property alias was not defined correctly in the BPEL/WSDL source, or the payload is not as expected.

Action: Check the BPEL/WSDL source to ensure that property alias is defined correctly.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03850: Not able to acquire lock on invoke message {0}

Cause: More than one thread is contending for this entity

Action: No action required, it is rescheduled with delay

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03851: Not able to acquire lock on delivery message {0}

Cause: More than one thread is contending for this entity

Action: No action required, it is rescheduled with delay

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03852: Not able to acquire lock on cube instance for {0} : {1}

Cause: More than one thread is contending for this entity

Action: No action required, it is rescheduled with delay

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04000: The process domain is unable to count the number of instances. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04001: The process domain is unable to count the number of instances for the process "{0}" (revision "{1}"). The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04002: An attempt to fetch the instances using the where condition "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the SQL statement was constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04003: An attempt to fetch the work items using the where condition "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04004: The process domain is unable to insert the current log entries for the instance "{0}" to the audit trail table. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04005: The process domain is unable to insert the current audit trail detail entries for the instance "{0}" to the audit details table. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04006: The process domain is unable to store the work items for the synchronous instance "{0}" to the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04007: The process domain is unable to store the audit trail for the synchronous instance "{0}" to the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04008: Unable to set the auto commit level for the current data source connection. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibit this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04009: unable to commit the current data source transaction; the exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibit this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04010: The process domain is unable to purge the instances from the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04011: The process domain is unable to delete the document "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04012: The process domain is unable to delete all the instances for the process "{0}" (revision "{1}") from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04013: The process domain is unable to fetch a list of the expired work items in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04014: The process domain is unable to look up the type for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04017: The process domain is unable to find the work items for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04018: The process domain is unable to find the audit trail entry for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04019: The process domain is unable to find the work items for the synchronous instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04020: The process domain is unable to find the audit trail for the synchronous instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04025: The process domain is unable to decode the properties for message GUID {0}, which are stored in column {1}; the exception reported is: {2}

Cause: This is an internal error. The properties have not been encoded properly.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-04026: The process domain is unable to find any pending callback messages in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04027: The process domain is unable to find any pending invoke messages in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04028: The process domain is unable to find any pending subscriptions in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04029: The process domain is unable to mark all instances (and activities) with process GUID {0} as stale. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04030: An attempt to fetch the audit details for the instance "{0}" (detail ID {1}) from the data source fails. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04031: An attempt to fetch the audit details for the instance "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04032: The process domain is unable to read the audit detail for detailId "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibit this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04033: The process domain is unable to fetch the document "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04034: The process domain is unable to find the closed instances for the domain "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04035: The process domain is unable to fetch the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04036: The process domain is unable to fetch the scope activation message with key "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04037: The process domain is unable to fetch the work item "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04038: The process domain is unable to update or insert the document "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04039: The process domain is unable to update the key table "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04040: The process domain is unable to update the LOB column "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04041: The process domain is unable to update or insert the instance "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04042: The process domain is unable to update or insert the serialized scope for the instance "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04043: The process domain is unable to delete or insert the scope activation message with key "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04044: The process domain is unable to update or insert the work item "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04045: The process domain is unable to batch update or insert the work items for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04046: The process domain is unable to batch insert a series of synchronous work items into the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04048: The process domain is unable to insert the delivery data for conversation "{0}", subscriber "{1}" in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04049: The process domain is unable to select the delivery data for conversation "{0}" (subscriber "{1}") from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04050: The process domain is unable to select the delivery data for conversation "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04052: The process domain is unable to select the delivery data for subscriber "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04053: The process domain is unable to update the state of the delivery subscription "{1}" for conversation "{0}". The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04054: The process domain is unable to update the state of the delivery subscription "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04055: The process domain {0} is unable to delete handled delivery subscriptions. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04056: The process domain is unable to insert the delivery data for the message {0} and the operation {1} in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04057: The process domain is unable to delete the delivery data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04058: The process domain "{0}" is unable to delete the handled delivery data from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04059: The process domain is unable to select the delivery data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04060: The process domain is unable to select the delivery data for the message {0} and the operation {1} from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04061: The process domain is unable to update the state of the delivery the message {0}. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04062: The process domain is unable to delete the invocation data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04063: The process domain "{0}" is unable to delete the handled invocation data from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04064: The process domain is unable to select the invocation data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04065: The process domain is unable to select the invocation data for the process "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04066: The process domain is unable to insert the invocation data for the message {0} and the operation {1} in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04067: The process domain is unable to update the state of the invocation the message {0}. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04069: The process domain is unable to fetch a list of the stale instances belonging to the process "{0}" (revision "{1}"). The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04076: The process domain is unable to look up the TX data source "{0}".

Cause: The J2EE container was not configured properly; a data source with the expected name has not been created or has been removed.

Action: Verify that the machine hosting the data source is physically connected to the network. In addition, verify that the connection pool properties, as defined in the application server startup properties, are valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04077: The process domain is unable to establish a connection with the data source with the connection URL "{0}". The exception reported is: {1}

Cause: The J2EE container was not configured properly; the connection parameters for the data source might not have been correct.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04078: The process domain is unable to release its data source connection. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the transaction has become corrupt.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04079: cannot read BLOB stream from the data source with key "{0}"; the exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibited this action.

Action: Verify that the machine hosting the data source is physically connected to the network. In addition, verify that the connection pool properties, as defined in the application server startup properties, are valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04080: The data stream for the instance or activity object "{0}" is not found in the data source.

Cause: The data stream with the instance or activity object key named in the error message was not found.

Action: Verify that the instance or activity key named in the error message refers to a valid instance or activity that has been started and not removed from the process domain.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04082: The process domain is unable to delete the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04083: The process domain is unable to insert or update the exception entry for the activity "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04084: The process domain is unable to delete the exception entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04085: The process domain is unable to find the activity in the domain "{0}" with the custom key "{1}". The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04087: failure to find schedulable activities for domain "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04090: The process domain is unable to read the serialized scope for the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04091: The process domain is unable to read the indexes for the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04092: The process domain is unable to update or insert the indexes for the instance "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04099: The process domain is unable to find instances with root ID "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04100: The process domain is unable to find any invoke messages with the specified where condition in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04101: The process domain is unable to find any callback messages with the specified where condition in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04102: The process domain is unable to insert the process event for process "{0}" (revision "{1}") in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04103: The process domain is unable to find any process events with the specified where condition in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04108: The process domain is unable to select the attachment by the key "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04109: The process domain is unable to delete the attachment by the key "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04110: The process domain is unable to insert the attachment into the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04111: The process domain is unable to select the attachment reference "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04112: The process domain is unable to insert the attachment reference into the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04113: The process domain is unable to remove the attachment reference of the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04121: An attempt to fetch the test details using the where condition "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04122: The process domain is unable to insert or update test details for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04123: The process domain is unable to update the state of the following delivery messages "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04124: The process domain is unable to update the state of the following delivery subscriptions "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04125: The process domain is unable to select the number of detail instances for the master instance specified by the conversation ID "{0}".

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04126: The process domain is unable to select document references for the instance ID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04127: The process domain is unable to insert document references for the instance ID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04128: The process domain is unable to select document references for delivery message GUID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04129: The process domain is unable to insert document references for delivery message GUID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04132: cannot read CLOB stream from the data source with the key "{0}"; the exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibited this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Additionally verify that the connection pool properties as defined in the application server startup properties are valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04138: The process domain is unable to store the test definition for process "{0}", revision "{1}", test suite "{2}", location "{3}" in the data source. The exception reported is: {4}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04139: The process domain is unable to delete the test definition for the process "{0}", revision "{1}", test suite "{2}", location "{3}" in the data source. The exception reported is: {4}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04140: The process domain is unable to delete test definitions for the process "{0}", revision "{1}" in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04141: The process domain is unable to delete the events logged for the process "{0}", revision "{1}" from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04142: The process domain is unable to delete the events logged for the domain. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04143: The process domain is unable to insert the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04144: The process domain is unable to update the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04145: The process domain is unable to find the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04146: The process domain is unable to delete the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04147: The process domain was unable to fetch the activity guide instance with key "{0}" from the datastore. The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04148: The process domain was unable to update the activity guide instance with key "{0}" in the datastore. The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource, or the data segment may be full.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04149: The process domain was unable to insert the activity guide instance with key "{0}" to the datastore. The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource, or the data segment may be full.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04150: The process domain was unable to insert the audit counter for instance "{0}". The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04151: The process domain was unable to update the audit counter for the instance "{0}". The exception reported is: {1}

Cause: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Action: There is a problem accessing the SOA datasource, or the data segment may be full.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04152: The process domain was unable to select the audit counter for the instance "{0}" from the datastore. The exception reported is: {1}

Cause: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Action: There is a problem accessing the SOA datasource.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04153: The process domain was unable to select for update on the audit counter for the instance "{0}" from the datastore. The exception reported is: {1}

Cause: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Action: There is a problem accessing the SOA datasource.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05000: failure to fetch the dispatcher trace for the engine "{0}"; the exception reported is: {1}

Cause: The dispatcher trace XML file was written to an output buffer that was not sized correctly.

Action: Contact Oracle Support Services. Provide the error message and the process that appeared to cause the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05001: The message handler for the class {0} is not registered.

Cause: This was an internal error. It occurred because the dispatcher message handler was not registered in the MessageRegistry class.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05002: error while attempting to process the message "{0}"; the reported exception is: {1}

Cause: This error contained an exception thrown by the message handler.

Action: Check the exception trace in the log (with logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05003: No message local handler is implemented for the message "{0}".

Cause: This was an internal error. It occurred when a remote message was handled locally.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05004: error while sending a batch message to the dispatch queue; the exception reported is: {0}

Cause: There was a problem with enqueuing the message to the JMS queue or the dispatcher EJB could not be found in the JNDI context.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05005: The process domain is unable to send a message to the JMS queue "{0}". The exception reported is: {1}

Cause: There was a problem with enqueuing the message to the JMS queue; the queue configuration might be incorrect.

Action: Verify that the JMS service for the application server has been configured properly.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05006: error while scheduling a batch message with the dispatcher; the exception reported is: {0}

Cause: There was a problem finding the dispatcher EJB in the current JNDI context.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05007: there is no active transaction while scheduling a message with the dispatcher

Cause: this usually happens if the underlying subsystem rollback back the transaction without bubbling up the system or transaction exception to the bpel layer

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05213: The process identifier "{0}" for the BPEL process archive "{1}" is not valid.

Cause: The process identifier for the BPEL process archive named in the message was not valid.

Action: Ensure that the deployment descriptor contained in the BPEL process archive named in the error message has a valid process ID. Process identifiers might start with a letter, a dollar sign ($) or an underscore (_); process characters (other than the first character) include a letter, a number, a dollar sign ($), an underscore (_) or a hyphen (-).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05214: The process revision tag "{0}" for the BPEL process archive "{1}" is not valid.

Cause: The process revision tag for the BPEL process archive named in the message was not valid.

Action: Ensure that the deployment descriptor contained in the BPEL process archive named in the error message has a valid revision tag. Valid revision tags may contain the following characters: a letter, a number, a dollar sign ($), an underscore (_), a hyphen (-), or a period (.).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05215: The process domain is encountering the following errors while loading the process "{0}" (composite "{1}"): {2}.

Cause: This error contained an exception thrown by the underlying process loader module.

Action: Check the exception trace in the log (with logging level set to debug mode). If there is a patch installed on the server, verify that the bpelcClasspath domain property includes the patch classes.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05216: The class {0} for the process "{1}" (revision "{2}") does not implement the ICubeProcess interface.

Cause: The current BPEL component named in the error message was probably compiled with an older version of SCAC. All process classes contained within the process domain must implement this interface.

Action: Recompile the SOA composite again.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05217: error while attempting to instantiate the class {0} for the process "{1}" (revision "{2}"); the exception reported was: {3}

Cause: This error contained an exception thrown by the underlying process loader module.

Action: Verify the exception trace in the log (with logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05222: cannot find class for type {0}

Cause: This was an internal error. The persistence manager for the type named in the error message could not be found in the class path. All required persistence managers should be registered by default.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05225: The persistence manager class {0} for the type {1} does not implement the IPersistenceManager interface.

Cause: This was an internal error. All persistence managers registered with the system must conform to the IPersistenceManager interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05226: error while attempting to instantiate the persistence manager class {0} for type {1}; the exception reported was: {2}

Cause: The persistence manager class named in the error message was not in the system class path or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05243: failure to obtain load lock for process "{0}"; the exception reported is: {1}

Cause: The lock timeout was too small for the current load or there was a large number of process modification requests.

Action: The default timeout is 120 seconds. If this is not sufficient, customize the value using the JVM system property orabpel.process.lock.timeout, which is added to the JVM start line.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05244: failure to obtain load lock for process "{0}"; timed out after {1} seconds.

Cause: The lock timeout was too small for the current load or there was a large number of process modification requests.

Action: The default timeout is 120 seconds. If this is not sufficient, customize the value using the JVM system property orabpel.process.lock.timeout, which is added to the JVM start line.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05250: error while attempting to deploy the BPEL component file "{0}"; the exception reported is: {1}

Cause: This error contained an exception thrown by the underlying deployment module.

Action: Verify the exception trace in the log (with logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05252: The bpel container could not find persistence manager {0} for type {1} in the classpath

Cause: During dehydration the bpel container would serialize all the objects in the scope, each object in the scope should have a persistence manager registered or available in the classpath, otherwise bpel container would not know how to serialize the object for the dehydration store.

Action: Please make sure the persistence manager {0} for type {1} is available in classpath. please refer the documentation on how to write a persistence manager.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05253: Cannot re-deploy a durable process "{0}" with keepInstancesOnRedeploy=true.

Cause: A durable BPEL process cannot be deployed when the flag keepInstancesOnRedeploy is set to "true".

Action: Remove the keepInstancesOnRedeploy flag and try again.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-08015: cannot find operation {0} of portType {1} in the WSDLs of composite "{2}

Cause: In the composite named in the error message, either the WSDL that defined portType named in the error message was changed, or there were multiple definitions of the same portType.

Action: Ensure that there is only one definition of portType named in the error message and redeploy the composite.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09004: cannot convert the object of the class {0} to XML text

Cause: The object of the class named in the error message was not converted to XML text because of the exception: {1}

Action: Ensure that a valid marshaller is registered for the class named in the error message and refer to the BPEL developer guide about how to create a marshaller for a JAVA type.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09006: A mismatch of a schema-generated object version cannot be used in the system.

Cause: Either the XML schema class {0} has been compiled with an older version of SCHEMAC, or the BPEL process domain to which the class is deployed could not use the helper classes that were generated for this class.

Action: Recompile XML schema using the SCHEMAC tool that is bundled with the current process domain.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09007: error while attempting to instantiate the XML marshaller class {0}

Cause: The exception reported was: {1}

Action: Ensure that marshaller is defined, and that it is available in the class path.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09008: error while marshalling the object to XML

Cause: The class {0} did not implement the com.collaxa.cube.engine.xml.IMarshaller interface.

Action: Ensure that the marshaller class {0} implements the correct interface. All XML marshallers used in the BPEL must implement this interface.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09009: The BPEL service engine is not able to instantiate the schema registry.

Cause: The class {0} (for the run-time schema registry) did not implement the ISchemaRegistry interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09010: error attempting to create the schema registry class {0}

Cause: This is an internal error. The exception reported was: {1}

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09200: When performing the assign operation, the to node {0} is invalid.

Cause: The node named in the error message was either null or an empty node set, and it was not an instance of org.w3c.Element.

Action: Verify the node value at line number {1} is not null and is an instance of org.w3c.Element.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09204: The result of from-spec is null.

Cause: Either the from node value or the xpath query in the from node value was invalid.

Action: According to BPEL4WS spec 1.1 section 14.3, the from node value should not be empty. Verify the from node value at line number {0} in the BPEL source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09205: The assign activity of the to node query is returning zero node.

Cause: Either the to node data or the xpath query in the to node was invalid.

Action: According to BPEL4WS spec 1.1 section 14.3, verify the to node value at line number {1} in the BPEL source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09207: There is an error while parsing the xml data.

Cause: The XML data was not valid; the reason was {0}.

Action: Ensure the XML data is valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09219: failure to save the element {0} during dehydration

Cause: This element was not a root element and the scope had reference to this element. The scope should have references only to root element.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09221: failure to serialize the element {0} to the binary format during dehydration

Cause: The exception reported was: {1}

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09222: failure to deserialize the document {0} from binary format during dehydration

Cause: The exception reported was: {1}

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09223: The assign activity part and query {0} are returning multiple nodes.

Cause: The assign activity part and query named in the error message returned multiple nodes. It should return single node.

Action: According to BPEL4WS specification 1.1 section 14.3, the assign activity part and query named in the error message should not return multiple nodes. Verify the part and xpath query named in the error message at line number {1} in the BPEL source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09224: cannot set a nonelement value to an element-based variable

Cause: An attempt to assign a nonelement value to an element-based variable failed.

Action: Verify the BPEL source for invalid assign activities.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09225: cannot set a nonmessage value to a message-based variable

Cause: An attempt to assign a nonmessage value to a message-based variable failed.

Action: Verify the BPEL source for invalid assign activities.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09226: cannot use a simple type variable in the setVariableData method

Cause: It was not allowed to use simple type variable in setVariableData method.

Action: Verify the BPEL JAVA exec source code for invalid assign activities.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09227: The from-spec for {2} operation must return either an attribute list or an element list.

Cause: The from-spec did not return an attribute list or an element list.

Action: Verify the assign activity for the operation named in the error message at line number {1} in the BPEL source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09228: The message part {2} of the WSDL variable {3} is not an XML element; {4} operation cannot be performed.

Cause: The operation named in the error message was not performed because the named message part of the WSDL variable named in the error message was not an XML element.

Action: Verify the message part named in the error message is a valid XML element at line number {1} in the BPEL source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09229: The to-spec does not yield any data; the {1} operation cannot be performed.

Cause: The operation named in the error message was not performed because to-spec did not yield any data.

Action: Verify the to-spec of the assign activity at line number {0} in the BPEL source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09230: The parent of the selection result {1} does not exist or is not an XML element; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the parent of the selection result named in the error message did not exist or was not an XML element.

Action: Verify the element of the assign activity at line number {0} in the BPEL source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09231: The selection result at list entry {1} does not have a parent node; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result at the list entry named in the error message did not have a parent node.

Action: Verify the list entry of the assign activity at line number {0} in the BPEL source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09232: The selection result at list entry {1} is not an XML node; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result at the list entry named in the error message was not an XML node.

Action: Verify the list entry of the assign activity at line number {0} in the BPEL source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09233: The selection result at list entry {1} is not an XML element; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result at the list entry named in the error message was not an XML element.

Action: Verify the list entry of the assign activity at line number {0} in the BPEL source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09234: The selection result of {1} is not an XML element; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result named in the error message was not an XML element.

Action: Verify the assign activity at line number {0} in the BPEL source and ensure the run-time data is valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09240: failure of the copyList assign operation

Cause: The element list specified by the to-spec used in the copyList operation was not contiguous.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09241: The copyList assign operation fails due to a type mismatch.

Cause: The from-list of copyList was element-based, while the to-list was not element-based.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09242: The copyList assign operation fails due to a type mismatch.

Cause: The from-list of the copyList operation was attribute-based, but the to-list was not attribute-based.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09243: The copyList assign operation fails.

Cause: The element returned from the to-list spec of the copyList operation did not have an element parent.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source and ensure that the run-time to-list data is valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09244: The copyList assign operation fails.

Cause: The element returned from the to-list spec of the copyList operation did not have a parent node.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source and ensure the run-time to-list data is valid

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09245: The copyList assign operation fails.

Cause: The members of the to-list spec of the copyList operation did not share the same parent node.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source and ensure the run-time to-list data is valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09248: cannot instantiate document builder {0}

Cause: The reason was: {1}

Action: Ensure that document builder class named in the error message exists in the class path.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09249: error while parsing the XML text {0}

Cause: The XML text was invalid because {1}.

Action: Verify that the XML text is valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09250: error while creating the XML document

Cause: The reason was {0}.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)

Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09251: cannot perform copy XMLNS for prefix:{0}

Cause: Namespaces conflicted: {1} and {2}

Action: Verify the from element data of the assign operation.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09500: An error occurs while processing the XPath expression; the expression is {0}.

Cause: The XPath expression failed to execute; the reason was: {1}.

Action: Check the detailed root cause described in the exception message text and verify that the XPath query is correct.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09501: An error occurs while registering the XPath function {0}.

Cause: Registering the XPath function failed; the reason was: {1}.

Action: Check the detailed root cause described in the exception message text and verify that the XPath function named in the error message is defined in the domain property file.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09502: The syntax error occurs while parsing XPath expression {0}, at position {1}.

Cause: The XPath query syntax was wrong; the exception was: {2}

Action: Check the detailed root cause described in the exception message text and verify that the XPath expression named in the error message is correct. The XPath expression is defined in the BPEL process.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09503: an error occurs while parsing XPath expression {0}

Cause: The XPath expression was invalid; the reason was: {1}.

Action: Check the detailed root cause described in the exception message text and verify that the XPath expression named in the error message is correct. The XPath expression is defined in the BPEL process.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09504: The XPath variable or expression {0} is empty at line {1}.

Cause: An attempt to read or copy data referenced or computed by the XPath expression either had invalid data, according to the XML schema, or did not contain certain optional data.

Action: Ensure that the variable or expression result named in the error message is not empty. Enable XML schema validation of related variables to ensure the run-time data is valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09505: The XPath variable or expression {0} is empty at line {1}.

Cause: An attempt to create the missing to data by the XPath expression failed. Attribute ignoreMissingToData does not apply to this expression.

Action: Make sure the expression uses only: PathExpr ::= "/"RelativePathExpr RelativePathExpr ::= ForwardStep (("/") ForwardStep)* ForwardStep ::= (ForwardAxis QName) | AbbrevForwardStep AbbrevForwardStep ::= "@"? QName ForwardAxis ::= ("child" "::") | ("attribute" "::").

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09705: An error occurs while initializing BPEL variable {0}; the schema processor cannot find the element {1} in the following schemas: {2}.

Cause: The XSD element on which the variable was based was not properly defined in XSD or the WSDL.

Action: Ensure that the element named in the error message is valid in the XSD or the WSDL.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09706: An error occurs while initializing BPEL variable {0} at line {1}; the schema processor cannot find type {2} for part {3} in the following schemas: {4}.

Cause: The XSD type on which the variable was based was not properly defined in XSD or the WSDL.

Action: Ensure that the type named in the error message is valid in the WSDL.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09707: cannot initialize variable {0} at line {2}

Cause: The reason was: {1}.

Action: Ensure that the variable named in the error message is valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09717: validation of variable {0} failed

Cause: The reason was: {1}.

Action: Pleasehandle the exception in bpel.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20300: A problem occurs while processing reports data {0}.

Cause: The DataCaptureAgency class reported an exception.

Action: Examine the log file to determine the problem.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20301: The Reporting Data Publisher {0} fails.

Cause: The data publisher reported an exception.

Action: Examine the log file for more details.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20302: A problem occurs while setting up a connection to the JMS destination {0} using the connection factory {1}.

Cause: The JMS configuration was incorrect.

Action: Verify that the JMS configuration is valid.

Level: 1

Type: WARNING

Impact: Programmatic

ORABPEL-20303: An error occurs while publishing report data to the JMS destination {0}.

Cause: The JMS configuration was incorrect.

Action: Verify that the JMS destination is valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20304: The JMS destination lookup fails. The related report data will not be published.

Cause: The JMS configuration was incorrect.

Action: Verify that the JMS destination or JNDI name {0} is valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20305: The JMS connection factory lookup fails. The related report data will not be published.

Cause: The JMS configuration was incorrect.

Action: Verify that JNDI name {0} is valid.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20306: A problem occurs while releasing the JNDI resources used to publish to the destination {0}.

Cause: The JMS configuration was incorrect.

Action: Verify that JNDI name is correct.

Level: 1

Type: WARNING

Impact: Programmatic

ORABPEL-20307: The custom data publisher class {0} cannot be loaded.

Cause: The custom data publisher class named in the error message was not found.

Action: Verify that the class file and all dependencies can be loaded from the suitcase or from the application class path.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20308: The custom data publisher class {0} cannot be initialized properly.

Cause: An attempt to create the custom data publisher class named in the error message failed.

Action: Examine the log file for a class creation exception.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20309: The sensor cannot be registered because it has no name.

Cause: The sensor name was missing.

Action: Specify the sensor name.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20310: The sensor {0} cannot be registered because a sensor with the same name is already registered.

Cause: The sensor name was a duplicated name.

Action: Specify a unique sensor name.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20311: The sensor-sensor action association for sensor {0}, action {1} cannot be created because no sensor named {2} exists in the registry.

Cause: The sensor name was missing.

Action: Specify a valid sensor name in the association.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20312: The sensor-sensor action association for sensor {0}, action {1} cannot be created because no sensor action named {2} exists in the registry.

Cause: The sensor name was missing.

Action: Register the sensor action before specifying an assocation.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20313: The sensor action cannot be registered because it has no name.

Cause: The sensor name was missing.

Action: Specify the sensor action name.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20314: The sensor action {0} cannot be registered because a sensor action with the same name is already registered.

Cause: The sensor action name was a duplicated name.

Action: Specify a unique sensor action name.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20315: An error occurs while loading sensors and sensor actions for the process {1}, revision {2} in the domain {0}.

Cause: The loading of sensors failed.

Action: Examine the log file for the exception of loading sensors.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20316: No target is specified for sensor {0}.

Cause: The target information was missing.

Action: Specify a target.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20317: The target {1} for sensor {0} is invalid.

Cause: The target information was wrong.

Action: Specify a dollar sign ($) before the variable name and ensure that the variable exists.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20318: The configuration for sensor {0} is missing.

Cause: The sensor configuration was missing.

Action: The variableConfig element must be specified for variable sensors. Complete the variable sensor definition.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20319: The sensor {0} is a variable sensor but has activity or fault configurations defined.

Cause: The sensor configuration was wrong.

Action: Remove the unnecessary configuration elements.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20320: The sensor {0} is a fault sensor but has activity or variable configurations defined.

Cause: The sensor configuration was wrong.

Action: Remove the unnecessary configuration elements.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20321: The configuration for sensor {0} is missing.

Cause: The sensor configuration was missing.

Action: The activityConfig element must be specified for activity sensors. Complete the activity sensor definition.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20322: The sensor {0} is an activity sensor but has variable or fault configurations defined.

Cause: The sensor configuration was wrong.

Action: Remove the unnecessary configuration elements.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20323: The sensor {0} is invalid because {1} is an unrecognized sensor kind.

Cause: The sensor kind was wrong.

Action: Specify a valid sensor kind.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20324: The sensor action {0} is invalid because it publishes to a JMS destination but no destination is specified.

Cause: The JMS destination was missing in the sensor action.

Action: Specify the JMS destination property in the sensor action.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20325: The sensor action {0} is invalid because it publishes to a JMS destination but no connection factory is specified.

Cause: The JMS connection factory information was wrong.

Action: Specify the JMS connection factory.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20326: The sensor action {0} is invalid because it publishes to a custom publisher but no publisher class is specified.

Cause: The custom publisher class name was wrong.

Action: Specify the fully qualified class name of the custom data publisher.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20327: The sensor action {0} is invalid because {1} is an unrecognized publish type.

Cause: The publish type was wrong.

Action: Specify a valid publish type.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20328: The sensor action {0} is invalid because the associated sensor {1} cannot be found.

Cause: The associated sensor named in the error message was missing.

Action: Ensure that sensor names used in the sensor action file match those defined in the sensor file.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20329: The sensor action {0} is invalid because the connection name is not specified.

Cause: The connection name in the sensor action named in the error message was missing.

Action: Specify the connection name property in the sensor action.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20330: The Sensor.xsd schema cannot be loaded from the class path.

Cause: The installation of Sensor.xsd was missing

Action: Ensure that the Sensor.xsd file has not been modified in any way.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20331: The JMS Adapter cannot be loaded from the class path.

Cause: The loading of the JMS adapter failed.

Action: Ensure that the JMS adapter has been properly deployed in the application server.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20501: An error occurs while loading monitor model for the process {1}, revision {2} in the domain {0}.

Cause: The loading of monitor model failed.

Action: Examine the log file for the exception of loading monitor model.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20502: An error occurs while monitor database executing command {1}, for database {0}.

Cause: The monitor database command execution failed.

Action: Examine the log file for the exception of executing a monitor database command.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20503: An error occurs while monitor buisiness indicator evaluates the xpath {0}.

Cause: The monitor business indicator xpath evaluation execution failed.

Action: Examine the log file for the exception of executing a monitor business indicator xpath evaluation.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20504: An error occurs while monitor process activity execution for activity {0} and event {1}.

Cause: The monitor process activity execution failed.

Action: Examine the log file for the exception of executing a monitor process activity.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20505: An error occurs while monitor creates the registry. This error does not interfere in the BPEL process.

Cause: The monitor files are not found or an error occurs while loading the monitor files.

Action: Examine the log file for the exception of creating a monitor registry.

Level: 1

Type: WARNING

Impact: Programmatic

ORABPEL-20506: An error occurs while monitor loads the configuration.

Cause: The monitor config load failed.

Action: Examine the log file for the exception of loading a monitor config.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20507: An error occurs while monitor pubishes data to BAM.

Cause: The monitor BAM publish failed.

Action: Examine the log file for the exception of publishing monitor data to BAM publisher.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20508: An error occurs while monitor get the activity path information.

Cause: The monitor get activity path failed.

Action: Examine the log file for the exception of getting activity path information.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20509: Composite: {0}, Process: {1}, Process Revision: {2}, Business Indicator: {3}, Metric: {4}, Activity: {5}, Evaluation Event: {6}.Skipping evaluation for all metrics in this Business Indicator/Activity/Evaluation Event. No rows will be inserted.

Cause: The XPATH Evaluation of Business Indicator failed.

Action: Check XPath expression in conjunction with process variable state.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20510: Composite: {0}, Process: {1}, Process Revision: {2}, Business Indicator: {3}, Metric: {4}, Activity: {5}, Evaluation Event: {6}.A null value will be inserted for this metric.

Cause: The Metric XPATH Evaluation of Business Indicator failed.

Action: Check Metric XPath expression in conjunction with process variable state.

Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20511: An attempt to connect BAM failed. Error Message: {0}

Cause: Either BAM adapter credentials are incorrect or SOA/BAM trusted domain configuration is missing.

Action: See "Configuring the Oracle BAM Adapter" in Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite for more information.

Level: 1

Type: ERROR

Impact: Programmatic