The case-insensitivity of the database interactions in Data Validator are dependent on the value set for the CaseInsensitiveOracle property in the Settings node for a site in Server Manager. It is recommended to have the same value set for the CaseInsensitiveOracle property in the staging and target systems.
In order to use case-insensitive support, you must configure the export mapping using
query definitions to find objects in the target system.
-
The value set for the CaseInsensitiveOracle property does not apply to the schema items, UoM values, and enum values.
-
Keyword searches with the criteria specified using the unique key and UID are case-sensitive.
-
The Run Inconsistency Property Values option in the Create Job Definition dialog box checks the value of the CaseInsensitiveOracle property of the staging system for the case-sensitivity of the rule execution.
Validation rules
The following table lists all the validation rules supplied with Data Validator and the system types that are considered for the case-sensitiveness of the rule execution.
|
Rule name |
System type |
|---|---|
|
Check Claimed to Sub Configuration |
Target system |
|
Check File Exists |
Not applicable (case-sensitive) |
|
Check For Cyclic Relationships |
Staging system |
|
Check Object Exists |
Target system |
|
Check File Exists for Document Revision |
Not applicable (case-sensitive) |
|
Check Parallel Claim |
Target system |
|
Check Is Claimable |
Target system |
|
Check Is Revisable |
Target system |
|
Check Revised to Sub Config |
Target system |
|
Check Revised to Parallel Config |
Target system |
|
Check Properties Against Schema |
Not applicable (case-sensitive because it searches for schema items) |
|
Check Properties Against Classification |
Not applicable (case-sensitive because it searches for schema items) |
|
Check Relationship Exists |
Target system |
|
Check Unique Key |
Not applicable (case-sensitive because the search criteria uses the unique key) |
|
Compare All Property Values For Objects |
Staging system and target system |
|
Compare Value |
Staging system and target system |
|
Date Time |
Not applicable |
|
Double |
Not applicable |
|
Integer |
Not applicable |
|
Regular Expression |
Not applicable (case-sensitive) |
|
Staging System Cardinality |
Not applicable (case-sensitive because it searches for schema items) |
|
String Does Not Start With |
Staging system |
|
String Length |
Not applicable |
|
String Not Equal To |
Staging system |
|
Target System Cardinality |
Not applicable (case-sensitive because it searches for schema items) |
|
UOM |
Target system |
Computed columns
The following table lists all the computed columns supplied with Data Validator and the system types that are considered for the case-sensitiveness of the rule execution.
|
Function name |
System type |
|---|---|
|
AddDefaultUOMIfMissing |
Not applicable (case-sensitive because the search criteria uses UoM values) |
|
Concat |
Not applicable (case-sensitive) |
|
ConvertToHash |
Not applicable |
|
DateTimeColumn |
Not applicable |
|
Decode |
Not applicable (case-sensitive) |
|
Divide |
Not applicable |
|
GetDefaultUOMIfMissing |
Not applicable (case-sensitive because the search criteria uses UoM values) |
|
GetFileName |
Not applicable |
|
GetJobDetails |
Not applicable |
|
GetMajorRevisionCodeFromTargetSystem |
Not applicable (case-sensitive because it searches for schema items) |
|
GetMinorRevisionCodeFromTargetSystem |
Not applicable (case-sensitive because it searches for schema items) |
|
GetTargetSystemValueIfEmptyReturnDefault |
Target system |
|
GetValueFromTargetSystem |
Target system |
|
IndexOf |
Not applicable (case-sensitive) |
|
Join |
Not applicable (case-sensitive) |
|
Left |
Not applicable |
|
Length |
Not applicable |
|
Minus |
Not applicable |
|
Multiply |
Not applicable |
|
PadLeft |
Not applicable (case-sensitive) |
|
PadRight |
Not applicable (case-sensitive) |
|
RegexMatch |
Not applicable (case-sensitive) |
|
RegexReplace |
Not applicable (case-sensitive) |
|
Replace |
Not applicable (case-sensitive) |
|
Right |
Not applicable |
|
Split |
Not applicable (case-sensitive) |
|
SplitAlphaNumericSequence |
Not applicable (case-sensitive) |
|
SubString |
Not applicable |
|
Sum |
Not applicable |
|
ToLower |
Not applicable (case-sensitive) |
|
ToUpper |
Not applicable (case-sensitive) |
|
Translate |
Not applicable (case-sensitive) |
|
Trim |
Not applicable (case-sensitive) |
|
TrimEnd |
Not applicable (case-sensitive) |
|
TrimStart |
Not applicable (case-sensitive) |
|
YMDColumn |
Not applicable |
Prompted APIs
The following table lists all the prompted APIs supplied with Data Validator and the system types that are considered for the case-sensitiveness of the rule execution.
|
Parameter name |
System type |
|---|---|
|
GetEnumEntries |
Not applicable (case-sensitive because the search criteria uses enumerated values) |
|
GetObjectPropertiesByType |
Target system |
|
GetValueFromTargetSystemObjects |
Target system |
|
GetValuesFromTargetSystemRelExpansion |
Target system |
Implicit delete rules
The implicit delete rules use the value set in the CaseInsensitiveOracle property of the target system for the case-sensitivity of the rule execution.
For SQL Server databases, the case-sensitivity of Data Validator is based on the collation settings. You must set the case-sensitive or case-insensitive
settings while installing the database. This setting will determine whether or not
Data Validator will consider case during rule execution.