Running Control DB Validation Utility

Use this procedure to run the Control DB Validation utility to validate the expensemap database.

Before you begin

You must configure the Control DB Validation utility. To configure the Control DB Validation utility, see Configuration of Control DB Validation Utility.

To run the Control DB Validation utility, complete the following steps:

Run the Control DB Validation utility by using the command prompt on Windows machine or by using the terminal on Linux machine.
Open the command prompt or terminal and change the directory to the ControldbValidation folder.
Use the following command on the Linux machine to run the script:
```
chmod +x controldbValidation.sh
```
In the command prompt, enter the following command with the user name and password of the database that is to be validated.
```
 controldbValidation <userName> <password>
```
The utility generates the invalidData file and the controldbdeletequery_<timestamp>.sql file. The controldbdeletequery_<timestamp>.sql file contains all SQL commands that are to be run on the Controldb Validation folder. The utility displays a message if you want to run SQL commands from the controldbdeletequery_<timestamp>.sql file.
Click Yes to run the delete file that deletes the data that is listed in the controldbdeletequery_<timestamp>.sql file or click No to manually run the SQL queries on the database.

After you run the utility, an OUTPUT folder is created that contains the following files:

The controldbinvalidData_<timestamp>.log file contains all the unreferenced or obsolete data that is found in the Controldb Validation folder.
The controldbinvalidData_<timestamp>.log file contains the data in the following columns:
- ID: Populates row ID that is retrieved from the Controldb Validation folder.
- Type: Displays the type of object that is invalid.
- Name: Displays the name of object that is invalid.
- User: Displays the name of the user who has created the object.
- Reason: Reason for the data to be invalid.
The controldbvalidation.log file contains the execution logs for the utility. It also displays the number of records that are deleted for each query if you select Yes to delete records.