LO85260: WHEN FIRST ENABLING TRASH SYNC, START WITH TODAY AND FORWARD FOR ENHANCED PERFORMANCE.
Direct links to fixes
Closed as program error.
Some customers found a temporary performance issue when upgrading to 220.127.116.11 and later releases due to Trash folder syncing being enabled. The issue is that some users have a very large number of documents in the Trash folder that will all sync after the upgrade. To mitigate this, starting with this fix which will be delivered in Traveler 18.104.22.168, when upgrade a pre 22.214.171.124 server to 126.96.36.199, when Trash first is enabled it will only sync trash folder entries for today and future. It will not sync trash folder entries prior to the date of upgrade.
The performance hit is temporary, once all Trash items sync'd performance will return to normal.
To improve performance of initial upgrade from a pre 188.8.131.52 server to a post 184.108.40.206 server, during initial enablement of Trash sync, users will only see today's trash entries. Any new trash folder entries will sync to the device without issue. The server will not discover "older" trash entries during the initial enablement. This was done since some users were found to have tens of thousands of old trash documents which would impact performance.
The Traveler server has been updated starting with 220.127.116.11.
This fix will be included in IBM Traveler 18.104.22.168 and later releases. For latest maintenance information see this technote: http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
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