CPU usage on the DC when migrations are running is high and Linkresolver.log contains warnings similar to the following:
6-1-2012 12:46:07 3896 2264 Warning: matching attribute extensionAttribute15 of class user is not indexed. Links resolving performance will be significantly reduced.
6-1-2012 12:46:11 3896 2264 Warning: matching attribute extensionAttribute15 of class group is not indexed. Links resolving performance will be significantly reduced.
6-1-2012 12:46:13 3896 2264 Warning: matching attribute extensionAttribute15 of class contact is not indexed. Links resolving performance will be significantly reduced.
6-1-2012 12:46:15 3896 2264 Warning: matching attribute extensionAttribute15 of class inetOrgPerson is not indexed. Links resolving performance will be significantly reduced.
6-1-2012 12:46:19 3896 2264 Warning: matching attribute extensionAttribute15 of class computer is not indexed. Links resolving performance will be significantly reduced.
Quest Migration Manager Best Practices advises to index the service attributes in the schema but it doesn't explain how to do this.
How can this be performed? How can I index an attribute?
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center