Pending updates and data distribution errors are collected and displayed in the Shared Data Updates forms of the local element where you initiated the Start Sharing operation. Check these forms frequently to
view the status of pending updates
identify any updates that were made on the local element that have failed to be distributed to the other elements in the network or cluster.
Pending updates are updates that have not been applied to the destination element's database yet. Data Distribution errors are updates that could not be applied to the destination elements.
Notes:
In the SDS Shared Data Updates forms, click Data Refresh frequently to reload the latest update records from the database.
It is recommended that you provision all data sharing from one master element in the network or cluster. If you provision data sharing from a master element, you can monitor distribution errors from that one master element. However, if data sharing is provisioned from multiple elements, then you must log in separately to each element and check for distribution errors.
You should not use an AX controller as the master element. It does not have enough storage space to maintain a large number of data distribution updates and errors.
The pending updates and data distribution errors that are listed in the SDS Shared Data Updates forms do not show fields that are considered to be private to the end user. For example, set keys that are assigned to private speed calls are not displayed.
To view pending updates and data distribution errors
Access the desired Shared Data Updates form:
SDS Shared Data Updates - All
SDS Shared Data Updates - User
SDS Shared Data Updates - System
Notes:
The system displays the total number of data sharing errors on the upper, right-hand side of the Shared Data Updates - All form.
The system generates a minor alarm after the number of updates in the SDS Shared Data Updates form exceeds 200, and a major alarm after the number exceeds 10000. See SDS Usage Alarm for details.
To view a subset of records, select first or last, select the desired number of records, and then click Retrieve. The main frame of the window lists the pending updates and the failed updates.
Action ID: number assigned to the update transaction (unique within admin session)
Date/Time: date and time that the update was initiated
To: name of the destination element
Action: type of operation -- Add, Delete, or Modify
Form Name: name of the sharable form that is being modified
Reason: update status or in the case of failure, the reason for the failure, for example:
"pending"
"retrying"
"cannot connect to network element"
To sort the records by type, click on the field heading, for example Action ID. An down arrow located next to the field label indicates that the records are sorted by that field.
Click on a record in the main frame. The details for the record are shown in the lower frame:
Last Retried: date and time that the failed update was last retried
Form Name: name of the form on the destination element where the update failed. For pending updates, this field may be blank until the update is processed
Detail: first three fields of the of the record. For example, if the update action was changed, the key fields of the old record and the first three fields of the new record are displayed.
Click More to view the remaining updated fields.
Click Close to exit the details window.
Proceed to Resolving Pending Updates or Errors.
