LO90194: STALE SECURITY RECORD INFORMATION FROM SYSTEM DUMP/TELL COMMANDS REQUIRING DEVICE RE-APPROVAL.
Direct links to fixes
Closed as program error.
If a "tell traveler security allstatus" or systemdump with the security option included (security is not included by default) is executed, all of the security records from the Traveler database are loaded into the Security Record Store which functions as the cache for users bound to the current server. By loading all of the records for the command output, the records for the users not bound to this server are loaded. When a user is bound to this server later (because of Traveler load balancing, server restarts, etc.), the cache is not updated for the user, so any updates made on other servers may not be in the Security Record Store cache and cause actions to have to be redone (such as device approval, device not approved, wipe, lock, etc.) until Traveler is restated which would force the data to be loaded from the Traveler database and be accurate again.
Restart the Traveler server to force the Security Record Store (which functions as the in memory cache of security records) to reload.
Not a common scenario, but a user could require device approval a second time when load balancing accross servers or after a device reset.
The IBM Traveler server has been updated to ensure the cached security policy data for the user is accurate.
This fix will be included in IBM Traveler 22.214.171.124 and later releases. For the lastest available Traveler Server release see this technote: 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
Translate this page: