This example validates the cq_schema.mdb schema repository against all rules in the rules.xml rules file. Unless you specify the –rulegroup or –rulename option, the ClearQuest Diagnostics utility processes all rules in the rules file. You must edit the cqdiagnostics.pl script to specify which subcommand to run and which parameters to use; then run the script.
The –logfile and –resultsfile options identify the names of the log file and results file, respectively. The results file contains the information that the utility prints to the console as it processes the command. Part of the results file for this example is shown below. If you do not specify the –resultsfile option, the utility creates one with the name result_timestamp.txt in the directory where you invoke the command. The log file contains more detailed information, which is useful for diagnosing and repairing problems.
Use the –dbinfoschemarepo option to identify the schema repository's name, location, and vendor database.
validatedb -rulefile configuration\rules.xml -logfile testlog.txt -resultsfile testresults.txt -dbinfoschemarepo MS_ACCESS C:\cq_schema.mdb
Aug 26, 2005 11:02:54 AM
INPUT SUMMARY
Rule File : configuration\rules.xml
Results File : testresults.txt
Log File : testlog.txt
Master Database Information : MS_ACCESS C:\cq_schema.mdb null null null
Validating database connection parameters.
Database connection parameters validated.
Validating Rules File.....
Rule file validation completed.
Aug 26, 2005 11:02:56 AM
Executing Rule : m_action_def_master_usage_rule ( 1 of 248 )
Completed
.
.
.
Summary of Results
Total Rules :248
Rules Executed :247
Rules Completed : 245
Total rules with Information : 0
Total rules with Warning(s) : 1
Total rules with Error(s) : 12
Total rules with Recommendation(s) : 1
Fatal Error Occured in rule : 0
The following example uses the –rulegroups option to direct the utility to validate the schema repository against only the rules that belong to the performance rule group. The performance rule group contains rules that check for conditions known to adversely affect the schema repository's performance.
validatedb -rulefile configuration\rules.xml -logfile testlog.txt -resultsfile testresults.txt -rulegroups performance -dbinfoschemarepo MS_ACCESS C:\cq_schema.mdb