LO87442: USERS MAY RE-SYNC DATA WHEN SYNCING IN MIXED MODE ENVIRONMENT.
Direct links to fixes
Closed as program error.
This issue is seen when upgrading an older HA Environmnet pre 220.127.116.11 to a later HA Environment such as 18.104.22.168. The Scenario only happens for users syncing against the new server while the old server is still running the old level of code. The problem is also not severe, in that no data is lost. All users effected simply resync data to their device and the problem is not seen again.
Rapid upgrade of all servers to current level is best way to prevent. Working on fix for next delivery.
Somewhat rare scenario, but if upgrading from an HA pool from 22.214.171.124 to a newer level such as 126.96.36.199 and you run servers at both the 188.8.131.52 level and at the 184.108.40.206 level for some amount of time you may see users get issued a new account which will force a resync of data for that user.
This issue has been resolved in 220.127.116.11 and customers should not see issues upgrading from 18.104.22.168 to 22.214.171.124 even if running in mixed mode for a while.
This fix will be included in IBM Traveler 126.96.36.199 and all later releases. See this technote for the latest release information. http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
LOTUS NOTES TRA
Fixed component ID
Applicable component levels