Troubleshooting guide

Troubleshooting Guide
164
Data Sharing status for the
element is not consistent with all
the other SDS elements in the
data sharing network even after
you perform a sync operation.
That is, the other elements
indicate in their Network Element
Assignment forms that they are
sharing with the element, but data
is not actually being shared.
You restored an old database
that had SDS disabled.
To resolve this issue:
1. At the element at which SDS is off
(element A). Turn SDS on and then
back off again.
2. Perform a Start Sharing operation
from another SDS element (element
B) in the data sharing community with
element A.
3. Perform a Sync operation from
element B to element A to update any
data that may be out of sync on
element A.
You disabled SDS while the
element was disconnected from
the network.
To resolve this issue:
1. At the element at which SDS is off
(element A), turn SDS on again.
2. Perform a Sync operation from
another SDS element (element B) in
the data sharing community with
element A. Do not share any forms.
Unexpected transport errors are
being generated at the local
element.
The network connection
between the elements is down
resulting in transport errors.
Fix network issue and retry update
errors.
Data Sharing Mismatch errors are
being generated at the local
element in the SDS Distribution
Errors form.
A record has been updated on
local element and sent to a
remote (slave) element. The
slave element has rejected the
update because the slave's
sharing status is out of sync with
the local element (that is, the
slave does not recognize that it
should be sharing with the local
element).
If you want the slave element to accept
updates from the local element, perform
a sync operation from the local element
with the slave.
If you want to stop sharing data with the
slave element, perform a sync operation
from the local element with the slave and
then disable SDS at the slave element.
Unexpected Concurrent Change
Rejected errors are being
generated at the local element in
the SDS Distribution Errors form.
Concurrent Change Rejected
errors were created because
during a network outage
changes were made on
individual elements.
Fix network issue and retry update
errors.
The shared data has different
default settings because the
system Country variants (set in
the License and Option
Selection form) are different on
the master and remote
elements.
Accept the values using the Force
Change option, or do not share this data.
Table 56: Troubleshooting Sharing Operations
Symptom Possible Cause Corrective Action
Page 3 of 5