CWYDB0102E: An error occurred while the metadata for business object {0} was being retrieved.
Explanation: There is a syntax error in the business object metadata portion of the XSD file.
User Action: Verify the syntax of the XSD file.
CWYDB0104W: Stored procedure type {0} is already defined.
Explanation: More than one definition of the specified stored procedure type exists in the XSD file.
User Action: Correct the XSD file to retain only one definition for each stored procedure type.
CWYDB0201E: The adapter could not establish a connection to the database for the following reason: {0}.
Explanation: 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.
User Action: Analyze the reason for the failure to establish a connection, and fix the related setup problems.
CWYDB0202E: The adapter could not 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: Ensure that the JDBC driver classes are in the class path.
CWYDB0301E: An operation on the database failed with an SQL exception for the following reason: {0}.
Explanation: The adapter could not perform a database operation. The problem might be in the driver, the database, or the business object data. The SQL exception can help you identify the problem.
User Action: Analyze the reason for the failure, and fix the related setup problems.
CWYDB0302E: An operation on the database failed with a generic exception for the following reason: {0}.
Explanation: The adapter could not perform 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.
User Action: Analyze the reason for the failure of the database operation, and fix the related setup problems.
CWYDB0303E: An operation on the database failed with a generic exception for the following reason: {0}
Explanation: The adapter could not perform 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.
User Action: Analyze the reason for the failure of the database operation, and fix the related setup problems.
CWYDB0304E: While the date value was being parsed, an error occurred for the following reason: {0}.
Explanation: The adapter could not 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 that it does not have correct values.
User Action: Analyze the reason for the failure, and fix the date value.
CWYDB0305E: The following unknown SQL type was encountered: {0}.
Explanation: The adapter encountered an unknown SQL type. There might be a problem with the JDBC driver. Analyze the driver type and check the documentation for it.
User Action: Provide a valid SQL type.
CWYDB0306E: An unknown SDO type was encountered: {0}.
Explanation: The adapter encountered an unknown data type in the business object.
User Action: Analyze the detailed exception in the trace file for the failure. This data type is not supported by the adapter.
CWYDB0307E: The execute Retrieve SQL call failed.
Explanation: The adapter could not perform a database operation. The problem might be in the driver, the database, or the business object data being used.
User Action: Analyze the reason for the failure of the database operation and fix any related setup issues. Check the exception reported in the trace file, and try to address the issue.
CWYDB0401E: An error occurred while application-specific information was being retrieved for the {0} business object.
Explanation: The adapter cannot parse the application-specific information for the business object.
User Action: Ensure that the Namespace of the application-specific information is correct and that the business object XSD file is in the class path. Also verify the syntax of the XSD file according to the detailed exception in the trace file.
CWYDB0402E: An error occurred while the maximum length of property {0} was being retrieved in the {1} business object.
Explanation: The maximum length of the property could not be obtained from the business object.
User Action: Verify that the maximum length for the property is defined in the XSD file.
CWYDB0403E: The type of property {0} in the {1} business object should be of type String, because FixedChar ASI is set to true.
Explanation: If an element has FixedChar ASI set to true, it must be of type String.
User Action: Update the type of the property that is defined in the XSD file to type String.
CWYDB0501E: The commit operation on the transaction could not be completed for the following reason: {0}.
Explanation: The adapter could not commit the changes to the database.
User Action: Refer to the SQL exceptions in the trace file located in the server log directory. Also ensure that a database connection can be made.
CWYDB0502E: The Rollback operation on the transaction could not be completed for the following reason: {0}.
Explanation: The adapter could not roll back the changes made in the database.
User Action: Refer to the SQL exception in the trace file located in the server log directory. Also ensure that a database connection can be made.
CWYDB0603I: The value specified for the poll quantity is not valid; it is being set to 1.
Explanation: When a value specified for PollQuantity in the ActivationSpec property is not valid, the default value of 1 is used.
User Action: Provide a value greater than 0 in the ActivationSpec property for PollQuantity.
CWYDB0604I: No events are being polled because the poll quantity is 0.
Explanation: To poll, the adapter requires a value greater than 0.
User Action: Provide a value greater than 0 in the ActivationSpec property for PollQuantity.
CWYDB0605E: 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: Ensure that object keys exist in database event table. Ensure that the key-value pairs are set correctly in the event store.
CWYDB0606E: An operation on the database could not be completed for the following reason: {0}.
Explanation: The adapter could not perform a database operation. Check the SQL exception reported and address the issue.
User Action: Analyze the reason for the failure, and fix the related setup problems.
CWYDB0607E: Polled events were not retrieved.
Explanation: The adapter cannot retrieve events for polling.
User Action: Check the data store in the database for existing events. If some events exist, check the event status column to see if the events are set with the correct status values.
CWYDB0608E: The event status cannot be updated for event ID {0}.
Explanation: The status of the event in the event distribution table cannot be updated.
User Action: Check for an SQL exception in the trace file. Ensure that the event distribution table in the database can be updated.
CWYDB0609E: Event ID {0} cannot be deleted.
Explanation: The event records cannot be deleted from the event distribution table.
User Action: Check for an SQL exception in the trace file. Ensure that the event distribution table in the database can be updated.
CWYDB0610E: The adapter could not 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.
CWYDB0611E: The adapter could not establish a connection to the database for the following reason: {0}.
Explanation: 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.
User Action: Analyze the reason for the failure to establish a connection, and fix the related setup problems.
CWYDB0612E: An operation on the database could not be performed, and a generic exception has been generated: {0}.
Explanation: The problem might be in the driver, the database, or the business object data being used.
User Action: Examine the exception for the reason for the failure and correct any related setup issues.
CWYDB0613E: The XID cannot be updated for event ID {0}.
Explanation: The XID column of the event record in the event distribution table cannot be updated.
User Action: Check for an SQL exception in the trace file. Ensure that the event distribution table in the database can be updated.
CWYDB0614E: Pending transactions were not retrieved.
Explanation: The adapter cannot retrieve pending transactions for polling.
User Action: No action is required.
CWYDB0615E: The SPBeforePoll stored procedure could not be performed.
Explanation: The adapter could not run the stored procedure specified in the SPBeforePoll ActivationSpec property.
User Action: Check the trace file for an SQL exception. Verify that the specific stored procedure is valid.
CWYDB0616E: The SPAfterPoll stored procedure could not be run.
Explanation: The adapter could not run the stored procedure specified in the SPAfterPoll ActivationSpec property.
User Action: Check the trace file for an SQL exception. Verify that the stored procedure is valid.
CWYDB0617E: The custom event could not be inserted in the event table for event ID {0}.
Explanation: The standard event table is needed for custom queries when the AssuredOnceDelivery property is set to true.
User Action: Verify that the event table exists.
CWYDB0618E: The inbound connection could not be closed due to the following reason: {0}.
Explanation: The adapter could not close the inbound connection.
User Action: Check the details in the exception logged in the trace file in the server log directory and fix any issues reported.
CWYDB0619E: 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 cannot establish a connection to the database.
User Action: Provide a proper value for the UserName and Password properties in the ActivationSpec, or if the Authentication Alias is specified, ensure that the values for the UserName and Password properties are not blank.
CWYDB0801E: The Retrieve operation could not be performed.
Explanation: The adapter could not perform the Retrieve operation. The detailed exception is located in the trace file in the server log directory.
User Action: Check the trace file for an SQL exception. Analyze the reason for the failure of the Retrieve operation and fix any issues reported.
CWYDB0804E: 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: View the data in the database tables and ensure that there is only one row for the given key value or values.
CWYDB0805E: The Retrieve operation found no matches in the database for the {0} top-level business object 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: View the data in the database tables and ensure that there is a row for the given key value or values.
CWYDB0806W: The Retrieve operation found no matches in the database for the {0} child business object 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: You can typically ignore this warning; 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.
CWYDB0901E: The Delete operation could not be performed on the {0} business object.
Explanation: The adapter could not perform the Delete operation.
User Action: Check the trace file for an SQL exception. Analyze the reason for the failure of the Delete operation and fix any issues reported.
CWYDB0902E: The Delete operation could not be performed because no primary or foreign keys were specified for the {0} business object.
Explanation: The adapter could not perform the Delete operation because no primary and foreign keys were specified for the business object.
User Action: Define the appropriate primary or foreign key values, or both, for the business object.
CWYDB1001E: The Update operation could not be performed on the {0} business object.
Explanation: The adapter could not perform the Update operation.
User Action: Check the trace file for an SQL exception. Analyze the reason for the failure of the Update operation and fix any issues reported.
CWYDB1002E: The Update operation could not be performed because no primary or foreign keys were specified for the {0} business object.
Explanation: The adapter could not perform the Update Operation because no primary and foreign keys were specified for the business object.
User Action: Define the appropriate primary or foreign key values, or both, for the business object.
CWYDB1003E: The NO OWNERSHIP child business object {0} does not exist in the database.
Explanation: The adapter could not perform 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.
CWYDB1004E: An error occurred while retrieving the NO OWNERSHIP child business object {0} from the database.
Explanation: The adapter could not retrieve the specified NO OWNERSHIP child from the database.
User Action: Check the exception and perform corrective action.
CWYDB1101E: The RetrieveAll operation could not be performed on the {0} business object.
Explanation: The adapter could not perform the RetrieveAll operation.
User Action: Check the trace file for an SQL exception. Analyze the reason for the failure of the RetrieveAll operation and fix any issues reported.
CWYDB1103E: No result set is associated with the stored procedure for the RetrieveAll operation.
Explanation: The adapter could not get a result set when the stored procedure was run.
User Action: Check the trace file for an SQL exception and perform corrective action. Also check the actual values in the returned business object.
CWYDB1104E: 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 enterprise information system (EIS) exceeds the configured maximum record count in the InteractionSpec. 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 InteractionSpec.
CWYDB1301E: An error occurred while retrieving the application-specific information for the {0} business object.
Explanation: The adapter could not retrieve application-specific information for the specified business object.
User Action: Check the trace file for an SQL exception. Analyze the reason for the failure of the application-specific information retrieval and fix any issues reported.
CWYDB1302E: An error occurred while loading the oracle.jdbc.driver.OracleTypes class.
Explanation: There was an error loading the class from the Oracle driver JAR file. This may be because an improper version of the Oracle driver is loaded.
User Action: Verify that the class exists in the Oracle driver JAR file.
CWYDB1401E: An exception occurred while processing bidi data: {0}.
Explanation: The adapter encountered an error while processing bidi data.
User Action: Analyze the reason for the bidi exception and fix any issues reported.
CWYDB1402E: Bidi Transformation Error: An error occurred while creating the bidi context for the \'{0}\' property.
Explanation: The bidi context for the property cannot be created.
User Action: Check the log and trace files in the server log directory and correct any error indicated in the files.
CWYDB1403E: Bidi Transformation Error: An error occurred while transforming the business object \'{0}\'.
Explanation: A business object cannot be transformed.
User Action: Check the log and trace files, and correct any error indicated in the files.
CWYDB1404E: Bidi Transformation Error: An error occurred while transforming the metadata property \'{0}\' for the business object.
Explanation: 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.
CWYDB1405E: Bidi Transformation Error: An error occurred while transforming metadata property for attribute \'{0}\' for the business object.
Explanation: 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.
CWYDB1406E: Bidi Transformation Error: An error occurred while transforming the metadata configuration property \'{0}\'.
Explanation: A metadata configuration property cannot be transformed.
User Action: Check the log and trace files, and correct any error indicated in the files.
CWYDB1407E: Bidi Validation Error: An error occurred while validating bidi properties for the metadata configuration property.
Explanation: 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.