There are two approaches to a solution;
- Contact Quest technical support for a SQL query to check the indexes, if the result indicates that the indexes are corrupt, a tool can be provided to rebuild our proprietary indexes, however, the down side is that the rebuild process duration could be extensive (several hours depending on row count) and the database is inaccessible during this time.
- Create a new database and import the Change Auditor configuration and custom searches. The database is online for about 5 minutes with this approach.
Set the previous database as an archive for searching and reporting (if possible since searching will be impacted by the corrupt index) by a database direct connection from the Change Auditor client.
Avoid running out of disk space it can cause data corruption.
How to import the Change Auditor Configuration:
- Select “Action” | “Export” from the main menu in the Administration Task tab of the Client.
- Enable the Check boxes to the left of the configurations to be exported and click “OK”.
- Save the file to an accessible location using any desired name.
How to export Custom Reports:
- Right click on any custom search/folder, select “Export” from the context menu and save to an accessible location.
How to create a new database:
- Right click on the Coordinator icon in the system tray and select “Coordinator Configuration” from the Context menu.
- Enter a new name in the “Name of the database catalog” field and click “OK” (the database should not already exist) the Coordinator will start creating the new database shorty after restarting.
How to import Change Auditor configuration:
- Select “Action” | “Import” from the main menu in the Administration Task tab of the Client.
- Browse for the path of a previously saved configuration xml file.