Describes the consolidated database cache process flow, and options available for diagnosing problems at each step of the process.
Process flow
This diagram shows a logical view of the cache process flow on Sybase Unwired Platform.
The cache refresh process is either scheduled (repeated at certain intervals) or on-demand when the client initiates a request. The cache can also be updated by incoming Data Change Notification (DCN) requests. A mobile business object (MBO) operation marked as an Invalidate the cache operation forces cache contents to be refreshed.
![SUP Debug all [and MBS, Cache]](../image/penmqu1263497255390_21-mqu1273192675167.image)
Troubleshooting options
This section describes the options available for diagnosing consolidated database cache processing flow problems.
- In Sybase Control Center, enable data services (DS) subsystem logging by setting its log level. The output is written in the server log.
- Review subsystem messages for information about getting data and sending transactions.
- For cache activities, you can enable monitoring on the package and then use Sybase Control Center to review cache statistics captured for the period monitoring is enabled.
In Sybase Control Center, check cache group properties such as schedule, and cache interval. Cache updates are propagated to the client based on a combination of settings for Synchronization group change detection interval, push related device settings (MBS), and notification threshold for subscriptions (RBS). You can view all those properties in the Sybase Control Center .
You can also use monitoring to trace the cache refresh timestamp, notification generation timestamp, data import message generation (MBS), or sync request from the client for local database update. See System Administration for further details on cache.
- If you like to troubleshoot at the system-level (which will record all domains and packages activities), you can enable MMS logging by setting the log level in Sybase Control Center. The output is written in the server log.
- Select the desired application package, and enable monitoring. The captured data appears in Sybase Control Center. Use package-level logging to review data in the domain log.
- For low-level debugging and diagnostics, you may enable "Sync Tracing" for the package in Sybase Control Center. The output is written in the server log.
- For quick troubleshooting to locate system errors, you can check the package-level client log and MBO/Operation history in the Sybase Control Center.
- View the MBO/Operation history in Sybase Control Center for errors during back-end interaction with the EIS.
- On Unwired Server, review the errorlog.txt for any consolidated database system errors: <UnwiredPlatform_InstallDir\UnwiredPlatform\Servers\UnwiredServer\errorlog.txt.