Preface
Introduction to Data Validation Option
- Data Validation Option Overview
  - Data Validation Guidelines
- Data Validation Option Architecture
- Data Validation Test Components
- Data Validation Process
- Data Validation Views
- Data Validation Table Objects
- Data Validation Tests
- Data Validation Reports
- Data Validation Example
- Data Validation Client
Repositories
- Repositories Overview
- Adding a Repository
- Editing Repositories
- Deleting Repositories
- Refreshing Repositories
  - Troubleshooting a Repository Refresh
- Folders
- Exporting Repository Metadata
- Metadata Export and Import
  - Exporting Metadata
  - Importing Metadata
- Metadata Manager Integration
XML Data Source
- XML Data Source Overview
- XML Groups
- XML Data Conversion to a Relational Structure
  - Join View Properties for an XML File
  - Automatically Generating a Join View for an XML File
- Rules and Guidelines for XML Files
Tests for XML Data Sources
- Test for XML Data Sources Overview
- Importing XML Definitions and Viewing them in Data Validation Option
- Using XML Sources Directly in Table Pair or Single Table Tests
- Flattening XML using a Join View
- Editing Table and Column Names in the Join View
- Overriding XML Source File Information
- Troubleshooting
  - Maximum Row Size Limit
Connections
- Connections Overview
- File Connections
- Relational Connection Properties
  - Owner Name and Table Name Override
- SAP Connection Properties
Expressions
- Expressions Overview
- Expression Types
- Expression Editor
  - Data Type, Precision, and Scale of Field Expressions
  - Creating an Expression
- Expression Syntax
- Functions
- Operators
- Parameters
- Test Logic Processing in the Data Source
- Expression Examples
- Reusable Expressions
  - Rules and Guidelines for User-Defined Functions
  - Using PowerCenter User-Defined Functions in Data Validation Option
Table Pairs
- Table Pairs Overview
- Basic Properties for a Table Pair
- Advanced Properties for a Table Pair
- Rules and Guidelines for WHERE Clauses in a Table Pair
- Table Joins
  - Rules and Guidelines for Table Joins
  - Table Join Optimization
- Bad Records Configuration for a Table Pair
  - Bad Records in Flat File
  - Bad Records in Database Schema Mode
- Data Sampling for a Table Pair
  - Rules and Guidelines for Data Sampling
- PowerCenter Cache for a Table Pair
- Adding a Table Pair
- Table Pair Generation from Table Comparisons
- Editing Table Pairs
- Deleting Table Pairs
- Viewing Overall Test Results for a Table Pair
Tests for Table Pairs
- Tests for Table Pairs Overview
- Table-Pair Tests
- Test Properties for a Table Pair
- Adding a Table-Pair Test
- Automatic Test Generation for Table Pairs
  - Column Comparison by Position
- Generating Tests for a Table Pair
- Test Generation for a Table Pair from a Spreadsheet
  - Spreadsheet Requirements for Table-Pair Tests
  - Generating Tests for a Table Pair from a Spreadsheet
- Editing a Table-Pair Test
- Deleting a Table-Pair Test
- Running Table-Pair Tests
- Bad Records for a Table-Pair Test
- Viewing the Details of a Bad Record
- Table Pair Test Example
- Troubleshooting Table-Pair Tests
Single-Table Constraints
- Single-Table Constraints Overview
- Basic Properties for a Single-Table Constraint
- Advanced Properties for a Single-Table Constraint
- Bad Records Configuration for a Single-Table Constraint
  - Bad Records in Database Schema Mode
  - Bad Records in Flat File
- Data Sampling for a Single-Table Constraint
  - Rules and Guidelines for Data Sampling
- PowerCenter Cache for a Single-Table Constraint
- Adding a Single Table
- Editing Single Tables
- Deleting Single Tables
- Viewing Overall Test Results for a Single-Table Constraint
Tests for Single-Table Constraints
- Tests for Single-Table Constraints Overview
- Single-Table Constraint Tests
- Test Properties for a Single-Table Constraint
- Adding a Single-Table Constraint Test
- Test Generation for a Single-Table Constraint from a Spreadsheet
  - Spreadsheet Requirements for Single-Table Tests
  - Generating Tests for a Single-Table Constraint from a Spreadsheet
- Editing a Single-Table Constraint Test
- Deleting a Single-Table Constraint Test
- Running Single-Table Constraint Tests
- Bad Records for Single-Table Constraint Tests
- Viewing the Details of a Bad Record
Examples of Tests from Spreadsheets
- Examples of Tests from Spreadsheets Overview
- Spreadsheet Import and Export of Table Pair Tests
- Spreadsheet Import for Compare Tables
  - Scenario 1 - Add tables to the Compare Tables Import Spreadsheet
    - Adding Tables to the Compare Tables Import Spreadsheet
  - Scenario 2 - Importing the Compare Tables Spreadsheet into DVO
SQL Views
- SQL Views Overview
- SQL View Properties
- Rules and Guidelines for SQL Views
- Adding an SQL View
- Editing SQL Views
- Deleting SQL Views
- SQL View Example
Lookup Views
- Lookup Views Overview
- Lookup View Properties
- Adding Lookup Views
- Editing Lookup Views
- Deleting Lookup Views
- Lookup Views Example
Join Views
- Join Views Overview
- Join View Data Sources
- Join View Properties
- Output Field Properties
  - Column Aliases
- Adding a Join View
- Join View Example
Aggregate Views
- Aggregate Views Overview
- Aggregate View Editor
- Aggregate View Properties
  - Group By Columns
  - Using Sorted Input
- Rules and Guidelines for Aggregate Views
- Adding an Aggregate View
- Editing Aggregate Views
- Deleting Aggregate Views
- Aggregate View Example
Business Intelligence and Reporting Tools Reports
- Business Intelligence and Reporting Tools Reports Overview
- BIRT Report Examples
Dashboards
- Dashboards Overview
- Dashboard Types
DVOCmd Command Line Program
- DVOCmd Command Line Program Overview
- Rules and Guidelines for Running DVOCmd Commands
- CopyFolder
- CreateUserConfig
- DisableInformaticaAuthentication
- EncryptPassword
- ExportMetadata
- ImportMetadata
- InstallTests
  - Cache Settings
- LinkDVOUsersToInformatica
- PurgeRuns
- RefreshRepository
- RunTests
  - Running Multiple Table Pair Objects in Parallel
  - Cache Settings
- UpdateInformaticaAuthenticationConfiguration
- UpgradeRepository
- Rules and Guidelines for Special Characters
Troubleshooting
- Troubleshooting Overview
- Troubleshooting Initial Errors
- Troubleshooting Ongoing Errors
- Troubleshooting Command Line Errors
Datatype Reference
- Test, Operator, and Datatypes Matrix for Table Pair Tests
- Test, Operator, and Datatypes Matrix for Single-Table Constraints
- Selecting a Valid PowerCenter Transformation Data Type for an Expression
- Properties of PowerCenter Transformation Data Types
Reporting Views
- Reporting Views Overview
- Using the Reporting Views
  - Sample Queries for Custom Reports
- results_summary_view
- rs_bad_records_view
- results_id_view
- meta_sv_view
- meta_lv_view
- meta_jv_view
- meta_ds_view
- meta_tp_view
- meta_av_view
- rs_jv_id_view
- rs_lv_id_view
- rs_sv_id_view
- rs_av_id_view
Metadata Import Syntax
- Metadata Import Syntax Overview
- Table Pair with One Test
- Table Pair with an SQL View as a Source
- Table Pair with Two Flat Files
- Table Pair with XML File and Relational Table
- Single-Table Constraint
- SQL View
- Lookup View
Jasper Reports
- Jasper Reports Overview
  - Status in Jasper Reports
  - Generating a Report
- Jasper Report Types
- Jasper Report Examples
Glossary
- aggregate tests
- bad records
- constraint value
- count test
- data validation
- Data Validation Option repository
- Data Validation Option user
- Data Validation Option folder
- DVOCmd
- format test
- inner join
- join view
- lookup view
- outer join
- single table
- SQL view
- table comparison
- table pair
- threshold
- unique test
- value test

Data Validation Option User Guide

10.4.0
- 10.5.2
- 10.5.1
- 10.5

Back Next

RunTests

Runs all tests for one or more single-table objects or table-pair objects. You can run this command on Windows or UNIX.

For example, to run tests for a table pair with the external ID "abc123," enter the following command:

DVOCmd RunTests abc123

The

RunTests

command uses the following syntax:

DVOCmd RunTests external_ID [external_ID …] [--confdir conf_dir] [--username User name] [--password Password] [--ePassword Password Environment Variable] [--namespace Namespace] [--email email_ID,...] [--sendEmail NotPass] [--cacheSize CACHESIZE] [--folderNames]

The following table describes

RunTests

options and arguments:

Option	Argument	Description
-	external_ID	Required if you do not use folderNames. External ID of a single-table object or a table-pair object. You can separate multiple external IDs with spaces. If the folder name or external ID contains commas, spaces, or special characters, you will need to use different syntax.
--confdir	conf_dir	The user configuration directory. Specify the configuration directory if you have multiple Data Validation Option repositories on a client machine. If you have one Data Validation Option repository on a client machine and have not changed the configuration directory, you do not need to specify this option. Enclose the file path in quotes.
--username	User name	User name in the Informatica domain for which you configured Informatica authentication. Required if you configure Informatica authentication.
--password	Password	Password for the user name. Required if you configure Informatica authentication. If you set the password option, then do not set the ePassword option.
--ePassword	Password Environment Variable	Encrypted form of the password of the Informatica user name. Use the DVOCmd EncryptPassword command to encrypt the password. Set an environment variable to the encrypted password and use the variable in the ePassword option. The command replaces the environment variable with the encrypted password and then decrypts the password. If you set the ePassword option, then do not set the password option. If the command contains both the password and ePassword options, then the Data Validation Option uses the ePassword and ignores the password.
--namespace	Namespace	Namespace of the LDAP domain. Required if you configure Informatica Authentication and the domain uses LDAP authentication.
--email	email_ID	The email address to which Data Validation Option sends an email when the tests complete. You can provide multiple email addresses separated by commas. The email provides a link to the test results and specifies whether the tests pass or fail. If the PowerCenter Integration Service is running on Windows, configure the outgoing mail server with the following custom properties: SMTPServerAddress, SMTPPortNumber, SMTPFromAddress, and SMTPServerTimeout. To send mail with Microsoft Outlook, enter the Microsoft Exchange profile in the MSExchangeProfile configuration property in the PowerCenter Integration Service.
--sendEmail	NotPass	Data Validation Option sends an email if a test fails.
--cacheSize	CACHESIZE	Memory allocation to generate transformations in PowerCenter mappings. Increase the cache size for tests that contain multiple joins and lookups. Default is 20 MB for the data cache and 10 MB for the index cache. Specify "Auto" to enable PowerCenter to compute the cache size. When you run the RunTests command and set the cache size, Data Validation Option installs the tests in the repository before it runs the test.
--folderNames	folderA	Required if you do not use external_ID. Runs all objects in the specified folders. Separate multiple folder names with commas If your folder name or external ID contains commas, spaces, or special characters, you must use different syntax. If the folders have a large number of objects, the PowerCenter Integration Service places them in a queue to run. The PowerCenter Integration Service limits the number of sessions that can run concurrently based on the Max Concurrent Runs property configured in the Data Validation preferences.

The DVOCmd RunTests command returns the following output:

ERROR: TablePairs: <number>; Pass: <number>; Fail: <number>; No Result: <number>; Install/Run error: <number>.

The following table describes the output:

Output	Description
TablePairs	Number of table-pair objects or single-table objects that you run in the RunTests command.
Pass	Number of table-pair objects or single-table objects for which all tests completed successfully.
Fail	Number of table-pair objects or single-table objects for which at least one test failed.
No Result	Number of table-pair objects that returned no matching records based on the table join.
Install/Run Error	Number of table-pair objects or single-table objects for which Data Validation Option could not generate or install mappings successfully.

If you run the DVOCmd RunTests command from a shell script or batch file, the command returns a return code. For example, the command returns the return code to the %errorlevel% environment variable on Windows. The return code represents the status of all tests that the DVOCmd RunTests command runs. If you run tests for multiple single-table objects or table-pair objects, the return code applies to all tests for all single-table objects or all table-pair objects.

The following table describes the possible return codes for the DVOCmd RunTests command:

Return Code	Description
0	All tests are successful.
1	At least one test fails. A test fails if it fails to install, fails to run, does not return any result, or does not meet the test condition.