- CWWBI0001E: Unknown extension of class ''{0}'' encountered: ''{1}''.
- Explanation: An unknown extension of the DMA schema was encountered.
- User Action: Use only published extensions.
- CWWBI0002E: Could not delete INTO part from SELECT INTO/VALUES INTO statement: ''{0}''.
- Explanation: An internal error occurred.
- User Action: Report this error or change your SELECT INTO/VALUES INTO statement.
- CWWBI0003E: Actual number of columns (''{0}'') does not match number of output parameters (''{1}'') of SELECT INTO statement: ''{2}''.
- Explanation: The result of the query has a different number of columns than indicated by the output parameters.
- User Action: Make sure your SELECT INTO statement returns the same number of columns as indicated by the output parameters.
- CWWBI0004E: The result of a SELECT INTO statement ''{0}'' contains no rows.
- Explanation: The result of the query is empty so the output parameter(s) cannot be filled.
- User Action: Make sure your SELECT INTO statement returns exactly one row.
- 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 executed does not return a single row.
- User Action: Make sure your statement does return only a single row.
- CWWBI0006W: SQLException occurred during executing cleanup statements.
- Explanation: A SQL exception occurred during the execution of the defined cleanup statements. It will be ignored.
- User Action: Check if this is serious problem or acceptable.
- CWWBI0007W: SQLException occurred while closing JDBC connection.
- Explanation: A SQL exception occurred while closing the connection of the DMA. It will be ignored.
- User Action: Check if this is a serious problem or acceptable.
- CWWBI0008E: There are ''{0}'' underspecified input set references.
- Explanation: While processing a SQL statement, a number of input set references which should be prepared and/or cleaned up was encountered but which so not contain prepare and/or cleanup statements.
- User Action: Make sure the used set references contain prepare and/or cleanup statements or change their lifecycle attributes.
- CWWBI0009W: SQLException occurred during preparation of a DMA.
- Explanation: A SQL exception occurred during preparing a DMA. It will be ignored.
- User Action: Check if this is a serious problem or acceptable.
- CWWBI0010E: JNDI name of set reference data source (''{0}'') does not match JNDI name of DMA data source (''{1}'').
- Explanation: The data source of a statement and all involved set references must be equal.
- User Action: Make sure that all used data sources in one DMA are the same.
- CWWBI0011E: Exception occurred during processing a DMA.
- Explanation: An exception occurred during processing a DMA.
- User Action: Fix reported error.
- CWWBI0012E: Throwing BPEL fault (QName: ''{0}'', message: ''{1}'', SQL error code: ''{2}'', SQL state: ''{3}'').
- Explanation: A BPEL fault was thrown as a result of an exception.
- User Action: Fix reported error.
- CWWBI0013E: Unknown extension found in mixed content of SQL statement definition (feature map entry: ''{0}'', ''{1}'').
- Explanation: An unknown extension of the mixed content of a SQL statement was found
- User Action: Fix statement definition.
- CWWBI0014E: An internal error occurred.
- Explanation: An internal error occurred.
- User Action: Report this error.
- CWWBI0016E: SELECT INTO and VALUES INTO statement ''{0}'' should 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.
- CWWBI0018E: nested exception is:
- Explanation: TBD
- User Action: TBD/None.
- CWWBI0019W: No cleanup statement for table ''{0}'' are executed because preparation is set to ''ifNeeded'' and table already existed.
- Explanation: A set reference has its cleanup attribute set to ''yes'' but they will not be executed since its preparation attribute is set to ''ifNeeded'' and the table already existed.
- User Action: Check if this is a serious problem.
- CWWBI0020W: Cannot find result set reference for position ''{0}''. Skipping this result set.
- Explanation: No result set reference was defined for the position.
- User Action: Check if this is correct.
- CWWBI0021W: DMA extension with namespace ''{0}'' and xsi:type ''{1}'' cannot be converted to a Java class name.
- Explanation: No executable extension of the XML extension could not be properly converted to a Java class name.
- User Action: Check the XML extension.
- CWWBI0022W: DataObject with namespace ''{0}'' and type ''{1}'' could not be created.
- Explanation: A DataObject could not be created.
- User Action: Check SDO configuration.
- CWWBI0023E: A set reference is about to be retrieved or persisted during activity ''{0}'' for which no primary keys are defined.
- Explanation: Only set references with a primary key can be correctly retrieved or persisted.
- User Action: Add a comma separated list of column names as the set property ''setPrimaryKeyColumns'' to the set reference definition.
- CWWBI0024E: The part of variable ''{0}'' in the parameter specification does not exist.
- Explanation: The variable part does not exist.
- User Action: Ensure that the variable contains a valid value.
- CWWBI0025E: Variable ''{0}'' does not contain a valid set reference.
- Explanation: The variable part does not exist.
- User Action: Ensure that the variable contains a valid set reference value.
- CWWBI0100E: Unknown SQL body type ''{0}''found.
- Explanation: An unknown extension was encountered in the SQL body.
- User Action: Fix the reported error.
- CWWBI0101E: Unknown extension found in mixed content of SQL statement definition (feature map entry: ''{0}'', ''{1}'').
- Explanation: An unknown extension of the mixed content of a SQL statement was found
- User Action: Fix statement definition.
- CWWBI0102E: The specified SQL statement is empty.
- Explanation: The specified SQL statement is empty.
- User Action: Add a non-empty statement
- CWWBI0103I: DMA successfully validated.
- Explanation: DMA successfully validated.
- User Action: None
- CWWBI0104E: Attribute ''position'' on multiple result set references not present.
- Explanation: If multiple result sets are specified, the ''position'' attribute is mandatory.
- User Action: Add ''position'' attribute to every result set reference.
- CWWBI0105E: Negative position ''{0}'' is not possible for result set reference.
- Explanation: A negative position for a result set reference is not possible.
- User Action: Specify non-negative number as position.
- CWWBI0106E: Position ''{0}'' of result set refence is bigger than number of actual result sets - 1 (''{1}'').
- Explanation: The position of a result set reference must be between 0 and number of actual result sets - 1
- User Action: Specify correct position
- CWWBI0107E: Duplicate position ''{0}'' for result set reference.
- Explanation: Two result set references must not have the same position.
- User Action: Change position attribute.
- CWWBI0108E: There is no position ''{0}'' in result set references.
- Explanation: A result set reference with the given position is missing.
- User Action: Add result set reference with this position.
- CWWBI0109E: The statement has no data source specified.
- Explanation: A statement must have a data source specified where it is executed.
- User Action: Add a data source specification.
- CWWBI0110E: The data source specification of the statement does neither contain a variable attribute nor an inline data source definition.
- Explanation: A data source specification must either refer to a variable or contain an inline definition.
- User Action: Add a correct data source specification.
- 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.
- CWWBI0112W: The data source specification contains a variable attribute but no part attribute. This does not work if the variable contains a WSDL message.
- Explanation: For variables typed with WSDL messages a part attribute is required.
- User Action: None.
- CWWBI0113E: Schema name can only be provided if ''generate'' attribute is set to ''no''.
- Explanation: Schema name can only be provided if ''generate'' attribute is set to ''no''.
- User Action: Set the ''generate'' attribute to ''no'' or delete schema name.
- CWWBI0114E: Table name can only be provided if ''generate'' attribute is set to ''no''.
- Explanation: Table name can only be provided if ''generate'' attribute is set to ''no''.
- User Action: Set the ''generate'' attribute to ''no'' or delete table name.
- CWWBI0115E: The set reference specification of the statement does neither contain 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.
- CWWBI0117E: The set reference specification contains a variable attribute but no part attribute. This does not work if the variable contains a WSDL message.
- Explanation: For variables typed with WSDL messages a part attribute is required.
- User Action: None.
- CWWBI0118E: The parameter specification element has to contain either a property or a query attribute.
- Explanation: The parameter specification is incomplete.
- User Action: Add query or property attribute
- CWWBI0119E: The specified variable does not exist: ''{0}''.
- Explanation: The specified variable does not exist.
- User Action: Create a variable with the given name or change variable name.
- CWWBI0120E: Variable ''{0}'' does not contain part ''{1}''.
- Explanation: The type of the variable is not an appropriate WSDL message.
- User Action: Change message type of variable or specify a different variable.
- CWWBI0121I: Validation info: ''{0}''.
- Explanation: None.
- User Action: None.
- CWWBI0122W: Validation warning: ''{0}''.
- Explanation: None.
- User Action: None.
- CWWBI0123E: Validation error: ''{0}''.
- Explanation: None.
- User Action: None.