- CWYBC0001I: Starting JDBC adapter.
- Explanation: Starting JDBC adapter.
- User Action: No action required.
- CWYBC0101E: An exception occurred while the business Object {0} was being created.
- Explanation: A copy of the business object cannot be created for parsing the metadata.
- User Action: Verify that the namespace is correct and that the business object xsd is in the class path. Also verify the syntax of the xsd file.
- CWYBC0102E: An error occurred while the metadata for business object {0} was being retrieved.
- Explanation: There is a syntax error in xsd file, in the business object metadata portion.
- User Action: Verify the syntax of the xsd file.
- CWYBC0103W: Stored procedure type {0} is not valid for the Verb {1}.
- Explanation: The stored procedure type defined for the specified verb is incorrect.
- User Action: Specify the stored procedure for the appropriate type for the appropriate verb.
- CWYBC0104W: Stored procedure type {0} is already defined.
- Explanation: More than one definition of the specified stored procedure type exists in the xsd.
- User Action: Correct the xsd file to retain only one definition for each stored procedure type.
- CWYBC0105W: An invalid stored procedure type has been found: {0}.
- Explanation: The stored procedure type specified in the xsd file is not valid.
- User Action: Correct the stored procedure type in the xsd file.
- CWYBC0106W: The Verb-level application-specific information does not specify a stored procedure.
- Explanation: The verb-level application-specific information is not recognized by this adapter as a stored procedure definition.
- User Action: In the xsd file, remove verb-level application-specific information that does not specify a stored procedure.
- CWYBC0107E: An error occurred during parsing of the application-specific information for the business object {0}.
- Explanation: A syntax error exists in the application-specific information in the xsd file.
- User Action: Correct the xsd file with the appropriate application-specific information.
- CWYBC0201E: The adapter failed to establish a connection to the database for the following reason: {0}.
- Explanation: The adapter failed while attempting to establish a connection to the database. The problem might be in the driver, the database, or the user credentials provided. The reason stated in the error message can help you identify the problem area.
- User Action: Analyze the reason for the failure to establish a connection, and fix the related setup problems.
- CWYBC0202E: The adapter failed to load the driver for the following reason: {0}.
- Explanation: The adapter loads the JDBC driver and then uses it to establish a connection to the database. If the driver does not exist in the class path, the adapter returns this error.
- User Action: Check that the JDBC driver classes are in the class path.
- CWYBC0203E: The adapter encountered a blank value for the URL specified for the database.
- Explanation: The URL provided was blank. Therefore, the adapter failed to establish a connection to the database.
- User Action: Provide a proper value for the URL.
- CWYBC0204E: The adapter encountered a blank value for the driver specified for the database.
- Explanation: The database driver value provided was blank. Therefore, the adapter failed to establish a connection to the database.
- User Action: Provide a proper value for the driver.
- CWYBC0205E: The adapter encountered a blank value for the XADatasourceName property.
- Explanation: The XADatasourceName value provided was blank. Therefore, the adapter failed to establish a connection to the database.
- User Action: Provide a proper value for the XADatasourceName.
- CWYBC0206E: The adapter encountered a blank value for the XADatabaseName property.
- Explanation: The XADatabaseName value provided was blank. Therefore, the adapter failed to establish a connection to the database.
- User Action: Provide a proper value for the XADatabaseName.
- CWYBC0301E: An operation on the database failed with a SQL exception for the following reason: {0}.
- Explanation: The adapter failed while attempting to execute a database operation. The problem might be in the driver, the database, or the business object data. The SQL exception reported can help you identify the problem area.
- User Action: Analyze the reason for the failure of the database operation, and fix the related setup problems.
- CWYBC0302E: An operation on the database failed with a generic exception for the following reason: {0}.
- Explanation: The adapter failed while attempting a database operation. The problem might be in the driver, the database, or the business object data. The reason stated in the error message can help you identify the problem area.
- User Action: Analyze the reason for the failure of the database operation, and fix the related setup problems.
- CWYBC0303E: An operation on the database failed with a generic exception for the following reason: {0}.
- Explanation: The adapter failed while attempting a database operation. The problem might be in the driver, the database, or the business object data. The reason stated in the error message can help you identify the problem area.
- User Action: Analyze the reason for the failure of the database operation, and fix the related setup problems.
- CWYBC0304E: An error occurred while the date value was being parsed, for the following reason: {0}.
- Explanation: The adapter failed while attempting to parse the value provided for the data type in the business object. The problem might be that the data is not in the correct format or it does not have correct values.
- User Action: Analyze the reason for the failure, and fix the date value.
- CWYBC0305E: This unknown SQL type was encountered: {0}.
- Explanation: The adapter encountered an unknown SQL type. This might be a problem with the JDBC driver. Analyze the driver type and check its documentation.
- User Action: Analyze the type and fix it.
- CWYBC0306E: An unknown SDO type was encountered.SDO Type found is {0}.
- Explanation: The adapter encountered an unknown data type in the business object.
- User Action: Analyse the reason for the failure and fix the type.
- CWYBC0307E: The execute Retrieve SQL call failed.
- Explanation: The adapter failed while attempting a database operation. The problem could be in the driver, database or the business object data being used.Please check the Exception reported and try to address the issue.
- User Action: Analyse the reason for the failure of the database operation and fix any related setup issues.
- CWYBC0401E: An error occurred during the retrieval of the application-specific information for the business object {0}.
- Explanation: Unable to parse the application-specific information for the business object.
- User Action: Check that the namespace is correct and that the business object xsd file is in the class path. Also verify the syntax of the xsd file.
- CWYBC0402E: An error occurred during the retrieval of the maximum length of property {0} in the business object {1}.
- Explanation: Unable to get max length of property from the business object.
- User Action: Verify that the maximum length for the property is defined in the xsd file.
- CWYBC0403E: The type of Property {0} in the business object {1} should be String, because FixedChar ASI is set to true.
- Explanation: If a element has FixedChar ASI set to true, it must be of type string.
- User Action: Verify the type of the property that is defined in the xsd file, Please update it to make it type string
- CWYBC0501E: Commit operation on the transaction failed.Reason {0}
- Explanation: The adapter failed to commit the changes to the database.
- User Action: Check the logs and verify if the database is ok.
- CWYBC0502E: Rollback operation on the transaction failed.Reason {0}
- Explanation: The adapter failed to rollback the changes done in the database.
- User Action: Check the logs and verify if the database is ok.
- CWYBC0601E: An error occurred while the business Object {0} was being created.
- Explanation: Unable to create business object for the event.
- User Action: Check that the namespace is correct and that the business object xsd file is in the class path. Also verify the syntax of the xsd file.
- CWYBC0602E: The primary key values on the data object were not set.
- Explanation: The adapter cannot set the primary values on the data object with the value set in the event store.
- User Action: Check the event store for the proper setting of key values in the key column.
- CWYBC0603I: An invalid value is specified for the poll quantity; setting it to 1.
- Explanation: If an invalid value was specified for PollQuantity in the activation specification property, the default value of 1 is used.
- User Action: Provide a value greater than 0 in the activation specification property for PollQuantity.
- CWYBC0604I: No events are being polled because the poll quantity is 0.
- Explanation: An invalid value or a value of 0 was specified for PollQuantity in the activation specification property.
- User Action: Provide a value greater than 0 in the activation specification property for PollQuantity. To poll, the adapter requires a value greater than 0.
- CWYBC0605E: The object keys column contains improper key value pairs.
- Explanation: The key value pairs given in the object keys column in the event store are improper.
- User Action: Check the event store for the proper setting of key value name pairs.
- CWYBC0606E: An operation on the database failed with a SQL exception for the following reason: {0}.
- Explanation: The adapter failed while attempting to execute a database operation. Check the SQL exception reported and try to address the issue.
- User Action: Analyze the reason for the failure of the database operation, and fix the related setup problems.
- CWYBC0607E: Polled events were not retrieved.
- Explanation: The adapter cannot retrieve events for polling.
- User Action: No action required.
- CWYBC0608E: The event status cannot be updated for event ID {0}.
- Explanation: Unable to update the status of the event in the event distribution table.
- User Action: Check the event distribution table.
- CWYBC0609E: Event ID {0} cannot be deleted.
- Explanation: Unable to delete the event from the event distribution table.
- User Action: Check the event distribution table.
- CWYBC0610E: The adapter failed to load the driver for the following reason: {0}.
- Explanation: The adapter loads the JDBC driver and then uses it to establish a connection to the database. If the driver does not exist in the class path, the adapter returns this error.
- User Action: Make sure that the JDBC driver classes are in the class path.
- CWYBC0611E: The adapter failed to establish a connection to the database for the following reason: {0}.
- Explanation: The adapter failed while attempting to establish a connection to the database. The problem might be in the driver, the database, or the user credentials provided. The reason stated in the error message can help you identify the problem area.
- User Action: Analyze the reason for the failure to establish a connection, and fix the related setup problems.
- CWYBC0612E: An Operation on the database failed with a Generic Exception.The failure reason is {0}.
- Explanation: The adapter failed while attempting a database operation. The problem could be in the driver, database or the business object data being used. Please check the Exception reported and try to address the issue.
- User Action: Analyse the reason for the failure of the database operation and fix any related setup issues.
- CWYBC0613E: The xid cannot be updated for event ID {0}.
- Explanation: Unable to update the xid of the event in the event distribution table.
- User Action: Check the event distribution table.
- CWYBC0614E: Pending transactions were not retrieved.
- Explanation: The adapter cannot retrieve pending transactions for polling.
- User Action: No action required.
- CWYBC0615E: The SPBeforePoll stored procedure could not be executed.
- Explanation: The adapter failed while trying to execute the stored procedure specified in the SPBeforePoll ActivationSpec property.
- User Action: Verify that the stored procedure is proper.
- CWYBC0616E: The SPAfterPoll stored procedure could not be executed.
- Explanation: The adapter failed while trying to execute the stored procedure specified in the SPAfterPoll ActivationSpec property.
- User Action: Verify that the stored procedure is proper.
- CWYBC0617E: The custom event could not be inserted in the event table for event ID {0}.
- Explanation: The adapter failed while trying to insert a custom event record in the event table.
- User Action: Verify that the event table exists. The standard event table is needed for custom queries if the AssuredOnceDelivery property is set to true.
- CWYBC0618E: Unable to close inbound connection due to the following reason: {0}.
- Explanation: The adapter could not close the inbound connection.
- User Action: No action required.
- CWYBC0619E: The adapter encountered blank values for either, or both, the Username and Password properties.
- Explanation: The values for the Username and Password properties must be correct. Otherwise, the adapter will not be able to establish a connection to the database.
- User Action: Provide a proper value for the UserName and Password properties in the Activation Spec, or if the Authentication Alias is specified, ensure that the user name and password values are not blank.
- CWYBC0701E: The Create operation failed.
- Explanation: The adapter failed while attempting to execute the Create operation.
- User Action: Analyze the reason for the failure of the Create operation and fix any issues reported.
- CWYBC0702E: The adapter failed to generate a sequence value for the attribute {0} in the business object {1} using the sequence {2}.
- Explanation: The adapter failed while attempting to generate the next sequence value for the Create operation. This error usually occurs when the sequence does not exist in the database, the sequence name metadata configured in the business object is improper, or the database connection or the driver has problems executing the SQL command.
- User Action: Check the appropriate logged SQL exception and make the necessary changes to enable the adapter to generate the sequence value.
- CWYBC0703E: The adapter failed to generate an identity value for the attribute {0} in the business object {1}.
- Explanation: The adapter failed while attempting to generate the next identity value for the Create operation. This error usually occurs when the identity does not exist in the database or the database connection or the driver has problems executing the SQL command.
- User Action: Check the appropriate logged SQL exception and make the necessary changes to enable the adapter to generate the identity value.
- CWYBC0801E: The Retrieve operation failed in the adapter.
- Explanation: The adapter failed while attempting to execute the Retrieve operation.
- User Action: Analyze the reason for the failure of the Retrieve operation and fix any issues reported.
- CWYBC0802E: The container retrieved during Retrieve operation failed in the adapter.
- Explanation: The adapter failed while attempting to execute the Retrieve operation.
- User Action: Analyze the reason for the failure of the Retrieve operation and fix any issues reported.
- CWYBC0803E: The recursive retrieve task during the Retrieve operation failed in the adapter.
- Explanation: The adapter failed while attempting to execute the Retrieve operation.
- User Action: Analyze the reason for the failure of the Retrieve operation and fix any issues reported.
- CWYBC0804E: The Retrieve operation found multiple matches in the database for the top-level business object {0} with the given key value or values.
- Explanation: The adapter expects only one row to be returned from the database for the given criteria of key values in the business object. If more than one row exists in the database, the adapter logs this error.
- User Action: Analyze the data in the database tables and ensure that there is only one row for the given key value or values.
- CWYBC0805E: The Retrieve operation found no matches in the database for the top-level business object {0} with the given key value or values.
- Explanation: The adapter expects one row to be returned from the database for the given criteria of key values in the business object. If no row exists in the database, the adapter logs this error.
- User Action: Analyze the data in the database tables and ensure that there is a row for the given key value or values.
- CWYBC0806W: The Retrieve operation found no matches in the database for the child business object {0} with the given key value or values.
- Explanation: No matching rows were detected in the database for the child business object with the given key values. This is not an error condition. The message indicates that there are no child objects matching the key values provided.
- User Action: This warning can generally be ignored. However, if you expect child objects to be retrieved, check the database rows to ensure that the keys match and that records exist in the appropriate tables.
- CWYBC0901E: The Delete operation failed on the business object {0}.
- Explanation: The adapter failed while attempting to execute the Delete operation.
- User Action: Analyze the reason for the failure of the Delete operation and fix any issues reported.
- CWYBC0902E: The Delete operation failed because no primary or foreign keys were specified for the business object {0}.
- Explanation: The adapter failed while attempting to execute the Delete operation because no primary and foreign keys were specified for the business object.
- User Action: Define appropriate primary or foreign key values, or both, for the business object.
- CWYBC1001E: The Update operation failed on the business object {0}.
- Explanation: The adapter failed while attempting to execute the Update operation.
- User Action: Analyze the reason for the failure of the Update operation and fix any issues reported.
- CWYBC1002E: The Update operation failed because no primary or foreign keys were specified for the business object {0}.
- Explanation: The adapter failed while attempting to execute the Update Operation because no primary and foreign keys were specified for the business object.
- User Action: Define appropriate primary or foreign key values, or both, for the business object.
- CWYBC1003E: The NO OWNERSHIP child business object {0} does not exist in the database.
- Explanation: The adapter failed while attempting to execute the Update operation because the specified NO OWNERSHIP child does not exist in the database and the test to verify its existence failed.
- User Action: Create the NO OWNERSHIP child in the database.
- CWYBC11001I: Unsupported JDBC Type encountered for column {0} in the table {1} in schema {2}. The column will not be added as an attribute of the business object.
- Explanation: The column is of a type which is not supported by the Adapter for JDBC.
- User Action: No action required.
- CWYBC11002F: An exception was caught {0}
- Explanation: The EMD has encountered a severe error and cannot continue.
- User Action: See the exception message for more information.
- CWYBC11003W: An exception was caught {0}
- Explanation: The EMD has encountered an error and cannot complete the current action.
- User Action: See the exception message for more information.
- CWYBC11004C: Service Type selected {0}
- Explanation: The user chose the listed Service Type from the user interface.
- User Action: None
- CWYBC11005C: Schema Filter Property {0}
- Explanation: The EMD will use the specified value to filter the database Schemas that are listed in the tree.
- User Action: None
- CWYBC11006W: Unsupported type {0} for the column {2} of Stored Procedure {1}
- Explanation: unsupported type.
- User Action: None
- CWYBC11007C: Database Object Filter Property {0}
- Explanation: The EMD will use the specified value to filter the database objects that are listed in the tree.
- User Action: None
- CWYBC11008I: Retrieving child objects for Schema {0} and Type {1}
- Explanation: The EMD will find the database objects of the specifed type in the specified Schema and add them to the tree.
- User Action: None
- CWYBC11009S: Error encountered retrieving metadata for database object {0} in schema {1}. Exception text - {2}
- Explanation: The EMD encountered an exception processing the specified database object.
- User Action: See the explanation for more information.
- CWYBC11010S: The following select statement is unsupported: {0}
- Explanation: Complex statements that include a nested select statement in the from clause cannot be supported.
- User Action: Enter a valid select statement. Ensure that the select statement does not include a nested select statement in the from clause.
- CWYBC1101E: The RetrieveAll operation failed on the business object {0}.
- Explanation: The adapter failed while attempting to execute the RetrieveAll operation.
- User Action: Check the exception and perform corrective action.
- CWYBC1102E: The container business object {0} cannot be created.
- Explanation: The adapter failed while trying to create the container business object for during the RetrieveAll operation. The exception message logged gives the reason for the failure.
- User Action: Check the exception and perform corrective action.
- CWYBC1103E: No resultset associated in the stored procedure for retrieve all.
- Explanation: The adapter failed to get a result set on execution of the stored procedure. Ensure that the associated stored procedure returns a result set for retrieve all operation.
- User Action: Please check the exception and perform corrective action.
- CWYBC1104E: The number of objects retrieved from the database is {0}. It exceeds the maximum records configured {1} for the input object {2}. The RetrieveAll operation cannot be completed.
- Explanation: The number of instances retrieved from the EIS exceeds the configured maximum record count in the interaction. The RetrieveAll operation cannot be completed.
- User Action: Increase the filtering criteria by populating more properties in the business object. If it still does not help, increase the number of maximum records allowed in the interaction spec.
- CWYBC1201E: The execute call to the interaction failed.
- Explanation: The adapter failed while performing the Execute operation on the interaction. The exception message logged gives the reason for the failure.
- User Action: Check the exception and perform corrective action.
- CWYBC1301E: Error loading Class - oracle.jdbc.driver.OracleTypes
- Explanation: There was an error loading the class from the Oracle Driver jar file.
- User Action: Verify that the class exists in Oracle Driver jar file
- CWYBC1401E: Error processing BIDI data, Exception {0}
- Explanation: The adapter encountered an error processing BIDI data.
- User Action: Analyse the reason for BIDI Exception and fix any issues reported.
- CWYBC1402E: Bidi Transformation Error: An error occurred while creating the bidi context for the \'{0}\' property.
- Explanation: Bidi Transformation Error: The bidi context for the property cannot be created.
- User Action: Check the log and trace files, and correct any error indicated in the files.
- CWYBC1403E: Bidi Transformation Error: An error occurred while transforming the business object \'{0}\'.
- Explanation: Bidi Transformation Error: A business object cannot be transformed.
- User Action: Check the log and trace files, and correct any error indicated in the files.
- CWYBC1404E: Bidi Transformation Error: An error occurred while transforming the metadata property \'{0}\' for the business object.
- Explanation: Bidi Transformation Error: A metadata property for the business object cannot be transformed.
- User Action: Check the log and trace files, and correct any error indicated in the files.
- CWYBC1405E: Bidi Transformation Error: An error occurred while transforming metadata property for attribute \'{0}\' for business object.
- Explanation: Bidi Transformation Error: A metadata property for an attribute of the business object cannot be transformed.
- User Action: Check the log and trace files, and correct any error indicated in the files.
- CWYBC1406E: Bidi Transformation Error: An error occurred while transforming the metadata configuration property \'{0}\'.
- Explanation: Bidi Transformation Error: A metadata configuration property cannot be transformed.
- User Action: Check the log and trace files, and correct any error indicated in the files.
- CWYBC1407E: Bidi Validation Error: An error occurred while validating bidi properties for metadata configuration property.
- Explanation: Bidi Validation Error: A bidi property for the metadata configuration property cannot be validated.
- User Action: Check the log and trace files, and correct any error indicated in the files.
- CWYBC11001I: Unsupported JDBC Type encountered for column {0} in the table {1} in schema {2}. The column will not be added as an attribute of the business object.
- Explanation: The column is of a type which is not supported by the Adapter for JDBC.
- User Action: No action required.
- CWYBC11002F: An exception was caught {0}
- Explanation: The EMD has encountered a severe error and cannot continue.
- User Action: See the exception message for more information.
- CWYBC11003W: An exception was caught {0}
- Explanation: The EMD has encountered an error and cannot complete the current action.
- User Action: See the exception message for more information.
- CWYBC11004C: Service Type selected {0}
- Explanation: The user chose the listed Service Type from the user interface.
- User Action: None
- CWYBC11005C: Schema Filter Property {0}
- Explanation: The EMD will use the specified value to filter the database Schemas that are listed in the tree.
- User Action: None
- CWYBC11006W: Unsupported type {0} for the column {2} of Stored Procedure {1}
- Explanation: unsupported type.
- User Action: None
- CWYBC11007C: Database Object Filter Property {0}
- Explanation: The EMD will use the specified value to filter the database objects that are listed in the tree.
- User Action: None
- CWYBC11008I: Retrieving child objects for Schema {0} and Type {1}
- Explanation: The EMD will find the database objects of the specifed type in the specified Schema and add them to the tree.
- User Action: None
- CWYBC11009S: Error encountered retrieving metadata for database object {0} in schema {1}. Exception text - {2}
- Explanation: The EMD encountered an exception processing the specified database object.
- User Action: See the explanation for more information.
- CWYBC11010S: The following select statement is unsupported: {0}
- Explanation: Complex statements that include a nested select statement in the from clause cannot be supported.
- User Action: Enter a valid select statement. Ensure that the select statement does not include a nested select statement in the from clause.