Oracle CRM On Demand Desktop Administration Guide > How Oracle CRM On Demand Desktop Synchronizes Data > How Oracle CRM On Demand Desktop Synchronizes Data with Oracle CRM On Demand >

Situations Where Local Data Might Be Lost

To prevent losing data due to a reinstallation of the data structure, Oracle CRM On Demand Desktop must use the current customization package to upload local data to the Oracle CRM On Demand server. The exception to this requirement occurs if the package is changed locally. In this situation, Oracle CRM On Demand Desktop cannot use the current, flawed package to synchronize data. Data for the user can be lost in the following situations:

• If data exists that Oracle CRM On Demand Desktop cannot upload to the Oracle CRM On Demand server because the permissions for the user have changed.
• If data exists for a user that is associated with synchronized items but is stored in fields that are not synchronized. Oracle CRM On Demand Desktop completely replaces the record in Microsoft Outlook with the record that it downloads from the Oracle CRM On Demand server. It erases any local data.

How Oracle CRM On Demand Desktop Prevents Data Loss If the User Deletes Customization Package Files

If Microsoft Outlook is open, then the user cannot delete any customization package files. For example, if the user attempts to use Windows Explorer to delete files from the following directory, then Windows Explorer does not allow the deletion:

C:\Documents and Settings\username\Application Data\Oracle\CRM OnDemand Desktop\Profile\data

If Microsoft Outlook is not running, then the user can use Windows Explorer to delete customization package files. However, if the user subsequently starts Microsoft Outlook, then Oracle CRM On Demand Desktop restores the customization package files from local storage. This local storage is a PST folder or an Exchange mailbox.

How Oracle CRM On Demand Desktop Handles Data During a Connection Failure

An internet or network-connection failure that occurs during synchronization can interrupt the synchronization. An interruption does not cause data loss or corruption. Synchronization can proceed from the last step that Oracle CRM On Demand Desktop executed successfully before the interruption.

How Oracle CRM On Demand Desktop Handles Server Busy Responses

If the client starts a synchronization process (manually or scheduled) and the Oracle CRM On Demand server returns a busy response, then the client waits an amount of time (default of 10 minutes, that is configurable in the Windows registry) before it automatically attempts to synchronize data again. The client continues to attempt synchronization until it is successful, or it reaches the retry limit. The default is 144 retries, which you can configure in the Windows registry. In addition, consider the following:

• This attempt to resynchronize applies to incremental and initial synchronizations only.
• There is no automatic retry on a local synchronization because local synchronization occurs more often and is of shorter duration. Consequently, the chances of a busy server are reduced. Additionally, if the synchronization does not complete for a day, the next incremental synchronization captures all changes.
• Users can perform a manual local synchronization if the scheduled synchronization fails.

  Depending on the number of users that attempt to synchronize at the same time, the synchronization might take some time to complete.

For more information on the Windows registry parameters that control the synchronization retry interval (SyncRetryInterval) and the synchronization retry maximum attempts (SyncRetryMaxAttempt), see Windows Registry Parameters That Affect Local Synchronization.

Related Topics

Customizing Synchronization