000013722 - Unable to edit associations after upgrading FIM

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 22, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000013722
Applies ToRSA Federated Identity Manger FIM 4.1
IssueUnable to edit associations after upgrading FIM
Any attempt to edit an assoication shows in the console as a "system internal error". There is no stack trace but the admin log shows the following:
[com.rsa.fim.admin.commands.myEntity.ListMyEntitiesCommand] executed with CommandResult status [ERROR]
Cause
This indicates an inconsistency in the database.  There are listings for the Associations that reference an entity ID that does not exist.
This problem may occur when importing data from FIM 2.6 using the upgrade26To40.cmd.  The upgrade script copies over all the data from FIM 2.6 but it does not fill in all the mandatory fields.  If there is a field in FIM 4.0 that has a null value for a mandatory field then the import will appear to work correctly but the entity will not actually be valid.  When a subsequent backup and restore is done the invalid entity will not be saved.  
ResolutionAfter importing the FIM 2.6 data but before doing a backup and restore, go through all of the FIM entities and save them. If there are any missing fields the FIM console will prompt you to add the missing inforamtion.  Once you have saved all the entities you can the do a backup and restore.  The backup and restore proceedure will update the FIM database from the 4.0 schema to the latest 4.1 schema.
Workaroundexecuted upgrade26to40.cmd 
executed backupconfig.cmd and restoreconfig.cmd
Legacy Article IDa55854

Attachments

    Outcomes