The error you see is the message returned by Oracle itself so there’s nothing you can do in the IS, or even in Oracle (AFAIK), that will cause more detail to be returned.
One solution is to create an IS document type that matches the input of your adapter service. In the document type, you can then specify the length of each field by choosing a “Contenty type” like “string” and then setting the maxLength attribute. In your service, you would then map the data to this document and call pub.schema:validate. If a field exceeds the maximum length, ‘validate’ will give you a more detailed error message. If no errors occur during validation, you can simply map your document straight into the adapter service.
In addition to the more detailed error message, one advantage of this approach is that it allows you to identify a problem without having to go all the way to the database. One drawback, however, is that if the size of a column changes in the database, you’d have to update your document.
#Adapters-and-E-Standards#webMethods#Integration-Server-and-ESB