Attribute Length Set Incorrectly for Operation and Load Arguments

Problem: Due to JDBC driver metadata retrieval related API limitations, Unwired WorkSpace does not always set the correct attribute length, especially for operation arguments and load arguments. For STRING and BINARY types, if the lengths are unknown, Unwired WorkSpace sets them to STRING(300) and BINARY(32767) by default, and gives a warning to adjust the length to avoid wasting device database space, and/or getting runtime data truncation.

Solution: Examine the EIS database metadata and adjust the attribute length, the types and lengths of operation arguments, and the load arguments in Unwired WorkSpace to avoid run-time errors.

Related concepts
AutoCommit Option for JDBC MBOs Using an ASE Data Source
Troubleshoot Code Generation
Related tasks
Unwired WorkSpace Crashes When Previewing or Test Executing Large Amounts of Data
Cannot Start Unwired WorkSpace After Modifying Plugins
Cannot Access Sample Database After Switching Network Types
Data Source Connection Fails After Installing to a New Directory
Related reference
JDBC Connection Errors
Mobile Business Object Errors
Preview Errors for a Web Service Mobile Business Object with date/time Types
Deployment and Code Generation Errors For MBOs That Use Large Datatypes
Deploying to Unwired Server Fails
Deploying to Unwired Server in a Cluster Fails
Input Parameters Fail to Generate for Complex Data Sources