Quantcast
Channel: Forum Microsoft Identity Manager
Viewing all articles
Browse latest Browse all 4767

Slow SQL MA and Error - Guid should contain 32 digits and 4 dashes

$
0
0

FIM 2010 R2 SP1 - Initial load. First SQL MA projected all employee data (35000 records ) in 90 minutes. When processing full synch on second SQL MA (40000 records) (joins with MV objects from first SQL MA) one record showed up under flow errors list as "unexpected-error". 

On opening the error record, it does not show any stack trace or error details on "synchronization error" tab. On lineage tab it shows up as connector and on click of "metaverse Object properties" button a message pops up as"Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)".

I tried stopped full synch and ran full import to see if it gets resolved but it did not and then tried deleting the source record but it does not go away. <<I guess this must be a corrupted record. Has anyone seen such error with MIIS/ILM/FIM ?

Second thing is second SQL MA performance, it is processing 100 records per hour. I have 2 join conditions, one as direct (unique ID ) and second as rules extension (employee id - to strip leading zeros on MV record). All the records that are joining are using the first condition. When I preview a record it is very fast but unable to figure out why it is so slow during run profile execution. <<Any suggestions to improve performance or debugging?

Attributes in join conditions are MV indexed. SQL server tempdb is resized to 1 GB. No pending exports in FIMService MA.

Thanks


Viewing all articles
Browse latest Browse all 4767

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>