These instructions apply changes to how CMDB processes the Organizational Hierarchy to help resolve performance issues caused by a large number of Organizational Views or Groups, especially in regards to issues seen by Asset/Contract-related functions. In step 8, the user manually reviews their Organizational Views and Groups. They must make a determination if any are unnecessary; Symantec Technical Support is unfortunately unable to make that determination for the user. The user may also want to review Manage > Organizational Views and Groups for more information in the Symantec Management Platform Console, such as looking through Assets by Cost Center. Clicking on individual ones may show that there are no assigned assets. This may indicate an unused and cost center that can be removed. Once user has determined which Organizational Views or Groups are unnecessary, these are then set to be purged (step 10).

IMPORTANT NOTE: The following steps require direct database interaction.  Please ensure a complete backup of the database exists or create one before moving forward.

1. In the Symantec Management Platform Console, click on Settings button > All Settings > Service and Asset Management > CMDB Solution > Organizational Hierarchy Settings.
2. Click to uncheck and disable "Enable automatic updating of Organizational Hierarchies" if it is enabled.
3. Click on the "Save changes" button.
4. Click on the Manage button > Jobs and Tasks > Service and Asset Management > CMDB > Update Organizational Hierarchy.
5. In the Default Task Parameters section, add any Organizational Hierarchies to be updated, such as Users by Location, etc.
6. Click to uncheck and disable "Only update resource membership" if it is enabled.
7. Click on the "Save changes" button.
8. Run the following SQL query on the SQL Server in SQL Server Management Studio to get a list of the guids to be used in the next queries.
   
   USE Symantec_CMDB
   SELECT DISTINCT i2.Name, i2.Guid
   FROM ScopeCollection sc
   JOIN Item i2 ON i2.Guid = sc.ScopeSetGuid
   ORDER BY i2.Name
    
9. Run the next query as many times as needed to replace the existing guid with the one found from the query in step 8. Note: This will change the security of the items so that they can be deleted.
   
   UPDATE Item SET Attributes = 0
   WHERE Guid in (SELECT ScopeCollectionGuid FROM ScopeCollection WHERE ScopeSetGuid = '<guid>')
   
   Where "<guid>" is to be replaced by the guid found from the query from step 8.
    
10. Run the final query as many times as needed to replace the existing guid with the one found from the query in step 8. Note: This will put the items in a table that will cause them to be deleted in a more automated fashion. This does not take effect immediately, necessarily and so some time may occur before these are purged.
    
    INSERT INTO ItemToDelete (Guid, DeleteDate)
    SELECT ScopeCollectionGuid, GETDATE () from ScopeCollection where ScopeSetGuid = '<guid>' 
    
    Where "<guid>" is to be replaced by the guid found from the query from step 8.

Related Article

Asset Contract reports take a long time to open or time out
http://www.symantec.com/business/support/index?page=content&id=TECH203764