Migration errors in TPAM 2.5.910; "Current Status" incorrect after migration; purging Release Logs. (4211413)

-After Migrating data into 2.5.910, the "Current Status" of an account could show an incorrect user name as knowing the current password.

-Migration of data into TPAM 2.5.910 which contains both a RequestID and an ISA ReleaseID can cause migrated rows in the password and file Release Logs to be purged by the first post-migration Daily Maintenance run.

WORKAROUND: Appling Hotfix 6006 is the only workaround.

STATUS: BFER 5999 and BFER 6006 are corrected in Hotfix_6006.

BFER 5999: Fixed migration issue where the Current Status of an account could show an incorrect user name as knowing the current password. Note that this only applies to a new migration - it does not fix already-migrated data.

BFER 6006: Fix the migration of data which contains both a RequestID and an ISA ReleaseID. Migrated rows in the password and file Release Logs were being purged by the first post-migration Daily Maintenance run. Note that this will not restore the purged log rows.

Note that this Hotfix is expected to be included within a future release of the Product.