Synchronization Report

This report returns the results of data synchronization processes run on the deployment.

Note: For more information about the Data Synchronization feature, see "Data Synchronization" on page 1.
To generate a Synchronization Report:
  1. Log in as a Company Administrator, and click the Reports tab.
  2. On the Reports menu, click Synchronization Report.
    1. The report is automatically generated.
  3. Click the link of a specific data synchronization run to display success/failure summaries for each table.
  1. If failures are displayed, you can click the related Synchronizer Name link to display the Synchronization Failure Summary for that row entry in the table.

Interpreting the Synchronization Report

The following sections explain how to interpret the results returned in the Report.

A SUCCESS result in the Final Status column of the Synchronization Report indicates that the Synchronization ran successfully, but does not preclude the failure of individual objects. A FAILURE result indicates one of the following errors:

Similarly, a SUCCESS result in a Synchronization Table Report does not mean that there were no failures of individual objects, while a FAILURE result indicates one of the following errors:

Failure Counts

The Failure Count result indicates the number of rows (objects) that failed to synchronize with xMatters; click the link in the Synchronizer Name column to view more details on a failure.

Failure counts may be incremented by the following errors:

  1. Missing a value for a required field.
    1. For example, if IS_EXTERNALLY_OWNED is null (or not Y or N for an Add or Update operation), SITENAME is null for DS_SITES, or WEB_LOGIN_TYPE is null for DS_USERS
  1. Attempting to remove objects that could not be removed.
    1. For example, attempting to remove the last supervisor of a Group, or removing the last active Device that is marked as the default Device for a User. (These rules are the same as those enforced in the web user interface.)
  2. Attempting to add objects to a missing or invalid parent.
    1. For example, if the User referenced by DS_USER_CUSTOM_VALUES is missing, or if the Event Domain referenced by DS_EVENT_DOMAIN_PREDICATE is invalid.
  3. Adding or updating an object to have a duplicated name or ID.
    1. For example, if the SITENAME in DS_SITES, the USER_ID if DS_USERS, or the DEVICE_NAME in any of the DS_%_DEVICES already exists in xMatters.
  4. Adding or updating an object to have a property that is invalid or references something that does not exist.
    1. For example, if the GROUP_KEY in DS_TEAMS does not reference an existing Group, or if the SITE_LANGUAGE or SITE_TIMEZONE in DS_SITES does not reference existing values in xMatters.
  5. Attempting to update a Custom Field from one type to another.
  6. Using an invalid format for the date, time, and day of week.
  7. Using an invalid value for WEB_LOGIN_TYPE in DS_USERS.
  8. Using an invalid value for PREDICATE_TYPE in DS_EVENT_DOMAIN_PREDICATES.
  9. Using an invalid MEMBER_SUB_TYPE in DS_TEAM_MEMBERSHIPS.
  10. Using an invalid CUSTOM_FIELD_TYPE in DS_CUSTOM_FIELDS.
  11. Using an invalid DT_OWNING_DEVICE in DS_DEVICE_TIMEFRAMES.
  12. Using an invalid COUNTRY_CODE in DS_TEXT_PHONE_DEVICES.
  13. Attempting to export a Dynamic Team.

Note that removing a non-existant object is considered a success; this includes the removal of Person Supervisors for a non-existant User.

Partial Failure Counts

The Partial Failure Count indicates that an object may have synchronized successfully, but a property of the object has encountered an error.

Partial failures may be caused by the following:

  1. Including an invalid element in a comma-delimited list.
    1. For example, if a User specified in the SUPERVISOR_LIST field in DS_GROUPS is missing or has an ineligible Role, or if a Role specified in the OBSERVER_LIST does not exist in xMatters.
  2. Including an invalid element in a joined table.
    1. For example, if an attribute in the DS_USER_JOIN_ATTRIBUTES table or an attribute in the DS_CUSTOM_FIELD_JOIN_VALUES table does not exist in xMatters.
  3. Including a team member in the DS_TEAM_MEMBERSHIPS table who does not exist in xMatters.