Troubleshooting synchronizationAdded by IBM on October 5, 2011 | Version 1 (Original)
|These questions and actions can help you troubleshoot the synchronization problems.
These questions and actions can help you troubleshoot the synchronization problems.
- How long has the problem been occurring?
If the problem occurred after a period of normal operation, did anything change in the environment?
- Is this installation a first-time installation?
- Did the feature work until some point and then start failing?
When does the problem occur? Is it occurring during the server replication or the client synchronization?
- Was the client, host, or server upgraded to a new patch level?
- Was an operating system patch applied?
- Did the network environment change? For example, was a server moved or a domain migrated?
- Did the system (client or server) crash recently?
Collecting data for synchronization problems
Parent topic: Troubleshooting DB2 Everyplace
When you encounter synchronization problems, you can collect diagnostic data to troubleshoot the problems.
If synchronization fails when the data is replicated between your mirror database and source database, use this information to troubleshoot the replication problem.
Testing the DB2 Everyplace Sync Server servlet
To ensure that the DB2 Everyplace
Sync Server can successfully communicate with clients, make sure that the DB2 Everyplace
Sync Server servlet is running. Follow these steps to make sure that the servlet is working properly.
Providing error-handling logic for user-exits
Frequently, error messages from the Mobile Devices Administration Center logs require that you act to resolve the problem indicated in the message text. To simplify day-to-day synchronization management, you might choose to add your own logic to automatically perform these actions when a particular error message is issued.
Devices are reset by Sync Server
Devices are reset by DB2 Everyplace
Hints and tips
A number of frequently used hints and tips are available to help you solve the problem.