Binding an MBO to a Database Fails

Problem: Failed to bind a mobile Business object (MBO) to a non-Sybase database due to a missing JDBC driver.

Solution: If you are using a IBM, DB2, Oracle, or Microsoft SQL database, you must place the corresponding JAR file into the lib folder in the associated plugin. Before you create or bind an MBO using any of these databases, select the JAR from the appropriate directory when you create the corresponding JDBC. See Configuring Your Environment to Use a JDBC Driver in Unwired WorkSpace - Mobile Business Object Development.

Related concepts
AutoCommit Option for JDBC MBOs Using an ASE Data Source
Passing an Empty String or Byte into a Required Binary Column in ASE
Related tasks
Multilevel Insert Operation Fails
Attribute Length Set Incorrectly for Operation and Load Arguments
Unable to properly update the CDB because the partition was improperly assigned
Related reference
MBO Retrieves Incorrect Data
Relationship Error
Warning Message When Creating Relationships
Troubleshooting Default Values for Adaptive ServerĀ® Anywhere uniqueidentifiers
Preview Errors for a Web Service Mobile Business Object with date/time Types
Web Service Mobile Business Object Must Be Connected to Connection Profile
Refresh Fails Due to Missing Load Argument Default Values
Input Parameters Fail to Generate for Complex Data Sources
Output Mapping Warning Message for Multilevel Insert Operations
Syntax Errors When Creating a Database Mobile Business Object
Sybase MBOs That Invalidate the Cache