SYMPTOM:
In Strategy ScanMD, after performing fixes, the summary page shows the fixes are done successfully, however, the errors remain in the metadata.
CAUSE:
Though the summary page shows the fixes are done successfully, due to the schema lock, it prohibits ScanMD from performing any schema related modification. To verify this problem, the user can check DSSErrors.log file right after the ScanMD fix. The user may observe the errors below:
Sample Code/Error
2010-06-29 19:57:37.261-05:00 Schema object 'Schema' with ID '6D263FCF31D9D2E2E1B30080DBDBADD7' cannot be modified because it is in use by 'Administrator' on 'TS-VM32-WIN2K3' since 6/29/2010 7:55:17 PM. Please contact your administrator for more information.
ACTION:
Release the schema lock and perform the ScanMD fix again.
