WebSphere Process Server messages     Operating Systems: All supported
CWWBI0001E: An unknown extension of class ''{0}'' was encountered: ''{1}.''
Explanation: An internal error occurred.
User Action: Check the log for more details.

 

CWWBI0002E: The INTO portion of the SELECT INTO/VALUES INTO statement could not be deleted: ''{0}.''
Explanation: The statement is syntactically incorrect.
User Action: Make sure that the SELECT INTO/VALUES INTO statement is syntactically correct. It must be of the form ''SELECT INTO #outparam_1#, ..., #outparam_n# FROM ...''

 

CWWBI0003E: The actual number of columns (''{0}'') does not match the number of output parameters (''{1}'') of the SELECT INTO statement: ''{2}.''
Explanation: The result of the query has a different number of columns than the number indicated by the output parameters.
User Action: Make sure that your SELECT INTO statement returns the same number of columns as there are output parameters.

 

CWWBI0004W: The result of a SELECT INTO statement ''{0}'' contains no rows. Output parameters will not be filled.
Explanation: The result of the query is empty, so the output parameter or parameters cannot be filled.
User Action: None.

 

CWWBI0005E: The result of a scalar fullselect, SELECT INTO statement, or VALUES INTO statement is more than one row. The statement affected is ''{0}.''
Explanation: The statement that was run does not return a single row.
User Action: Make sure your statement only returns one row.

 

CWWBI0006W: An SQLException exception occurred while running the cleanup statements.
Explanation: An SQL exception occurred during the execution of the cleanup statements. The exception will be ignored.
User Action: Check the details of the SQL error message to decide whether the issue is a serious problem that must be fixed or whether it can be ignored.

 

CWWBI0007W: An SQLException exception occurred when the database connection was being closed.
Explanation: An SQL exception occurred while a database connection was being closed. The exception will be ignored.
User Action: Check the details of the SQL error message to decide whether the issue is a serious problem that must be fixed or whether it can be ignored.

 

CWWBI0008E: There are ''{0}'' too few input set references specified.
Explanation: An internal error occurred.
User Action: Check the log for more details.

 

CWWBI0010E: The JNDI name of the set reference data source (''{0}'') does not match the JNDI name of the data source of the SQL snippet (''{1}'').
Explanation: The data source for a statement and all involved set references must be the same.
User Action: Make sure that all data sources used in the SQL snippet are the same.

 

CWWBI0011E: An exception occurred while processing an activity. A fault will be thrown.
Explanation: The exception will be mapped to a BPEL fault which can be caught in a fault handler.
User Action: Check the error message to determine whether this issue is a serious problem. If not, create a fault handler in the business process.

 

CWWBI0012E: A fault will be thrown (QName: ''{0}'', message: ''{1}'', SQL error code: ''{2}'', SQL state: ''{3}'').
Explanation: A fault was generated as a result of an exception. See the previous log message.
User Action: Check the error message to determine whether this issue is a serious problem. If not, create a fault handler in the business process.

 

CWWBI0013E: An unknown extension was found in the mixed content of an SQL statement definition (feature map entry: ''{0}'', ''{1}'').
Explanation: An internal error occurred.
User Action: Check the log for more details.

 

CWWBI0014E: An internal error occurred.
Explanation: An internal error occurred.
User Action: See the log for more details.

 

CWWBI0016E: SELECT INTO and VALUES INTO statement ''{0}'' must have at least one output parameter.
Explanation: A SELECT INTO or VALUES INTO statement needs at least one output parameter where the result is stored.
User Action: Change the SELECT INTO/VALUES INTO statement.

 

CWWBI0019I: The cleanup statements for table ''{0}'' were not run.
Explanation: The preparation settings for the set reference are set to ''Create table only if it does not exist yet'' but the cleanup settings are set to ''Drop table at end of process instance'' or ''Drop table at end of activity''. Because the table already exists it will not be cleaned up.
User Action: None.

 

CWWBI0020W: The result set reference for position ''{0}'' cannot be found. This result set is being skipped.
Explanation: No result set reference was defined for the position.
User Action: Ensure that a result set reference exists for every position.

 

CWWBI0021W: The model extension with namespace ''{0}'' and xsi:type ''{1}'' cannot be converted to a Java class name.
Explanation: An internal error occurred.
User Action: Check the log for more details.

 

CWWBI0025E: Variable ''{0}'' does not contain a valid set reference.
Explanation: The variable value might be null.
User Action: Ensure that the variable contains a valid set reference value, for example, by providing an initial value for the variable.

 

CWWBI0026E: The data management activity will not be processed because an error occurred when starting the process. The exception message is: ''{0}.''
Explanation: A preparation SQL statement might have failed.
User Action: Check the log for more details.

 

CWWBI0027E: The data type of variable ''{0}'' in query ''{1}'' cannot be inferred.
Explanation: The variable value might be null.
User Action: Set the variable to a dummy value.

 

CWWBI0028E: The value of variable ''{0}'' in query ''{1}'' is not a simple type. The actual type is ''{2}.''
Explanation: Parameters to SQL snippets must be of a simple type.
User Action: Change either the variable type, the variable name, or the query of the parameter.

 

CWWBI0029E: An exception occurred when starting the process instance. The business process will not run.
Explanation: A preparation SQL statement might have failed.
User Action: Check the log for more details.

 

CWWBI0030W: An exception occurred when the process instance cleanup statement ''{0}'' was run. The exception will be ignored.
Explanation: The cleanup statement failed when stopping the process instance.
User Action: Check the log for more details.

 

CWWBI0031W: An exception occurred while opening a connection for the data source using the JNDI name ''{0}.'' The process instance cleanup statement ''{1}'' will be ignored. A stack trace will follow.
Explanation: A connection for the data source could not be opened.
User Action: Check the log for more details.

 

CWWBI0032E: An exception occurred during the installation of the process template.
Explanation: A preparation statement for the process installation might have failed.
User Action: Check the log for more details.

 

CWWBI0033W: An exception occurred while uninstalling the process template. The exception will be ignored.
Explanation: A cleanup statement for the process installation might have failed.
User Action: Check the log for more details.

 

CWWBI0034E: The value for the SQL parameter ''{0}'' in the variable ''{1}'' is null.
Explanation: An input parameter for an SQL statement does not have a value.
User Action: Make sure that the variable has a value.

 

CWWBI0036E: A set reference with cleanup settings to ''Drop table at end of activity'' was not prepared in the same activity.
Explanation: A cleanup for a set reference is only valid if it is prepared in the same activity.
User Action: Make sure that the set reference is prepared in the activity.

 

CWWBI0037E: An exception occurred while opening the enterprise archive (EAR) file.
Explanation: The EAR file could not be opened when trying to install the application.
User Action: Make sure that the EAR file is valid.

 

CWWBI0038W: An exception occurred while processing an AtomicSQLSnippetSequence operation, rollback will be triggered.
Explanation: Any exceptions during AtomicSQLSnippetSequences trigger a rollback and result in a runtime fault.
User Action: Check the log for a more detailed error message to determine whether this issue is a serious problem. If not, create a fault handler in the business process to catch a runtimeFailure fault.

 

CWWBI0039W: The value of InvokeInformationService parameter ''{0}'' is null.
Explanation: The variable to which the parameter is mapped is empty.
User Action: Make sure that the mapped variable contains a value, for example, by checking the process design.

 

CWWBI0100E: The unknown SQL body type {0} was found.
Explanation: An internal error occurred.
User Action: Check the log for details.

 

CWWBI0101E: An unknown extension was found in mixed content of the SQL statement definition (feature map entry: ''{0}'', ''{1}'').
Explanation: An internal error occurred.
User Action: Check the log for more details.

 

CWWBI0102E: The specified SQL statement is empty.
Explanation: An empty string is not a valid SQL statement.
User Action: Add a valid SQL statement.

 

CWWBI0104E: The attribute ''position'' on multiple result set references is not present.
Explanation: If multiple result sets are specified, the ''position'' attribute is mandatory.
User Action: Add a ''position'' attribute to every result set reference.

 

CWWBI0105E: Negative position ''{0}'' is not valid for a result set reference.
Explanation: You cannot use a negative position for a result set reference.
User Action: Specify a positive number as a position.

 

CWWBI0106E: Position ''{0}'' of the result set reference is larger than the number of actual result sets minus 1 (''{1}'').
Explanation: The position of a result set reference must be between 0 and the number of actual result sets minus 1.
User Action: Specify a position that is equal to or smaller than the number of actual result sets minus 1.

 

CWWBI0107E: The result set reference contains a duplicate position, ''{0}.''
Explanation: Result set references cannot have the same position.
User Action: Change one of the position attributes.

 

CWWBI0108E: There is no position ''{0}'' in the result set references.
Explanation: A result set reference with the given position is missing.
User Action: Add a result set reference with this position.

 

CWWBI0110E: No data source variable has been specified.
Explanation: The variable of type tDataSource specifies the data source on which the SQL snippet is issued.
User Action: Specify a data source variable for the SQL snippet.

 

CWWBI0111W: The data source specification contains both a variable attribute and an inline data source definition. The inline definition will be used.
Explanation: The data source specification is ambiguous.
User Action: None.

 

CWWBI0113E: A schema name can be provided only if the ''Generate name'' attribute is set to ''no''.
Explanation: A generated schema name does not contain the provided schema name.
User Action: Either set the ''Generate name'' attribute to ''no'' or delete the schema name.

 

CWWBI0114E: A table name can be provided only if the ''Generate name'' attribute is set to ''no.''
Explanation: A generated table name does not contain the provided table name.
User Action: Either set the ''Generate name'' attribute to ''no'' or delete the table name.

 

CWWBI0115E: The set reference specification of the statement contains neither a variable attribute nor an inline set reference definition.
Explanation: A set reference specification must either refer to a variable or contain an inline definition.
User Action: Add a correct set reference specification.

 

CWWBI0116W: The set reference specification contains both a variable attribute and an inline set reference definition. The inline definition will be used.
Explanation: The set reference specification is ambiguous.
User Action: None.

 

CWWBI0118E: The parameter specification element must contain either a property or a query attribute.
Explanation: The parameter specification is incomplete.
User Action: Add either a query or a property attribute.

 

CWWBI0119E: The specified variable does not exist: ''{0}.''
Explanation: The business process does not contain a variable with the specified name.
User Action: Either create a variable with the given name, or change the variable name.

 

CWWBI0121I: Validation created the following information message: ''{0}.''
Explanation: None.
User Action: None.

 

CWWBI0122W: A validation warning occurred: ''{0}.''
Explanation: None.
User Action: None.

 

CWWBI0123E: A validation error occurred: ''{0}.''
Explanation: None.
User Action: None.

 

CWWBI0124E: Variable ''{0}'' has the wrong type (the actual type is '''{'{1}'}'{2}'', but the expected type is '''{'{3}'}'{4}'').
Explanation: A variable of a different type is expected.
User Action: Change the type of the variable to the expected type.

 

CWWBI0125E: Parameter ''{0}'' for the query for the RetrieveSet activity can only be of kind IN.
Explanation: Output parameters cannot be used in queries for RetrieveSet.
User Action: Set the parameter type to IN.

 

CWWBI0126E: The query of the RetrieveSet activity contains other set references than the one in variable ''{0}'' defined as the source.
Explanation: The query of a RetrieveSet activity can only be used to restrict the source set reference. Other set references cannot be used.
User Action: Change the variable in the set reference to the source set reference or change the query.

 

CWWBI0127E: The preparation and cleanup attributes of input set reference ''{0}'' must be set to ''no.''
Explanation: The preparation and cleanup of input set references is not possible.
User Action: Set the preparation or cleanup attributes (or both) to ''no.''

 

CWWBI0128E: The preparation attribute for the result set reference at position ''{0}'' is set to ''no'' but the cleanup attribute is not.
Explanation: The cleanup attribute for a result set reference with the preparation attribute set to ''no'' must also be set to ''no.''
User Action: Set both the preparation and cleanup attributes to ''no.''

 

CWWBI0129E: The SQL statement seems to be a SELECT INTO or VALUES INTO statement but it has no output parameters defined.
Explanation: SELECT INTO and VALUES INTO statements must have one or more parameters of kind ''out.''
User Action: If the SQL statement is a SELECT INTO or VALUES INTO statement, make sure that it contains output parameters in the INTO clause.

 

CWWBI0130E: The SQL activity has an output parameter but the statement does not seem to be a SELECT INTO, VALUES INTO or CALL.
Explanation: Output parameters are only valid for SELECT INTO, VALUES INTO and CALL statements.
User Action: Make sure that the parameter definition matches the statement.

 

CWWBI0131E: The SQL activity has ''{0}'' result set references defined but seems to be none of the statement types ''{1}''.
Explanation: The result set reference configuration indicates that the statement is intended to be one of the types listed in the message but the statement might be of a different type.
User Action: Ensure that both the statement and the result set reference configuration is correct. If they are already correct, just ignore this message.

 

CWWBI0132E: The variable ''{0}'' is specified in the <processName>.ids file but it does not exist in the process.
Explanation: The processName.ids file contains initial values for process variables. One of the specified variables does not exist in the process.
User Action: Delete the variableEntry elements from the file that refer to variables that do not exist in the process.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009