Synchronization Fails With OutOfMemory Error

Problem: The device application seems to hang for 15 or 20 minutes, then synchronization fails with a java.lang.OutOfMemoryError or OutOfMemoryError message.

Explanation 1: The load and synchronization parameters may not be set correctly to eliminate extraneous data. The volume of synchronized data, both from the enterprise information system (EIS) to the consolidated database, and from the consolidated database to the device client is causing the out of memory error.

Solution: Redesign the mobile business object (MBO) to take better advantage of both the load and synchronization parameters. See Sybase Unwired WorkSpace - Mobile Business Object Development > Develop > Working with Mobile Business Objects > Mobile Business Object Mobility Properties > Load Parameters > Combining Load and Synchronization Parameters.

Explanation 2: The device database page size may be too small.

Solution 1: Increase the page size for the device:

Use Device Application Designer, if you used it to generate the client application. See Sybase Unwired WorkSpace - Device Application Development > Developing a Device Application Using the Designer > Developing a Device Application Using the Device Application Designer > Designing the Screen for Device Applications > Screen Design Page Properties (the Device subsection).
Use the Sybase Unwired WorkSpace code generation wizard, if you used code generation to generate the client application. See Sybase Unwired WorkSpace - Device Application Development > Develop a Device Application > Using Object API to Develop a Device Application > Generating Object API Code.