Cisco Cisco Prime Service Catalog 10.0 Installation Guide

Proceed to the 

 section below.

Skip this section and proceed to the 

 section if you are 

already familiar with the database validation process during the Cisco Prime Service Catalog upgrade. 
You can always come back to review this section when the Validate Schema and Validate Data steps 
return any error. 

The functions on the Validation page verify the integrity of your existing schema and database. The 
results for all validation scripts are stored in a table called SchValidationLog in the database. See the 

 for instructions to view this log file. All possible 

validation entry ErrorLevels and their descriptions are shown in 

 below.

inform

The validation test results in an anomaly that is deemed harmless for the upgrade process, as well as for 
the application. For example, the validation detects a table that does not belong to the database schema. 
The existence of this table will not cause the upgrade to fail, nor will it have any ill effect on the 
application. 

These unrecognized objects that do not interact with Service Catalog tables are flagged with a status of 
“inform” in the SchValidationLog table. The following objects (if they exist) are reported only: tables, 
columns, sequences, stored procedures, functions, indexes and constraints that do not interact with Service 
Catalog tables. These objects are reported only, and are left alone.

All validation entries with ErrorLevel= “inform” will be ignored. 

No action is required on your part to address these entries.

inform: 
auto-repairable

The data validation test results in a data error that is deemed to be harmful. However, this type of error can 
be safely and programmatically fixed by the Repair Database function. 

Most errors of this type are the result of internal inconsistencies, possibly introduced by previous upgrades 
or import utilities, and the repair typically consists of restoring referential or data integrity.

The RepairScript column in the SchValidationLog table shows the SQL statement that is used to repair the 
error. 

No action is required on your part.

inform: 
auto-repaired

The Repair Database function executes the sql statement documented in the RepairScript column to fix 
the error that was reported as “inform: auto-repairable” above.

All validation entries with ErrorLevel= “inform:auto-repaired” are shown in the SchValidationLog table, 
and in the Validation Errors table when you click View Errors for the Repair Database function.

No action is required on your part.

inform: 
pending-repair

The validation test results in an anomaly that is deemed to be harmful to the upgrade process, but one that 
will be programmatically repaired during the upgrade process.

Missing or modified objects are flagged with a status of “inform: pending-repair” in the SchValidationLog 
table. An example of this type of anomaly is a missing index or a missing primary key constraint. The 
missing index or primary key constraint will be created correctly, if it does not exist.

No action is required on your part.