Table of Contents

Search

  1. Preface
  2. Introduction to Data Validation Option
  3. Repositories
  4. XML Data Source
  5. Tests for XML Data Sources
  6. Connections
  7. Expressions
  8. Table Pairs
  9. Tests for Table Pairs
  10. Single-Table Constraints
  11. Tests for Single-Table Constraints
  12. Examples of Tests from Spreadsheets
  13. SQL Views
  14. Lookup Views
  15. Join Views
  16. Aggregate Views
  17. Business Intelligence and Reporting Tools Reports
  18. Dashboards
  19. DVOCmd Command Line Program
  20. Troubleshooting
  21. Appendix A: Datatype Reference
  22. Appendix B: Reporting Views
  23. Appendix C: Metadata Import Syntax
  24. Appendix D: Jasper Reports
  25. Appendix E: Glossary

Data Validation Option User Guide

Data Validation Option User Guide

Troubleshooting Initial Errors

Troubleshooting Initial Errors

This section assumes that you have installed Data Validation Option.
I get the following out-of-memory error when I invoke Data Validation Option:
The JVM could not be started. The maximum heap size (-Xmx) might be too large or an antivirus or a firewall tool could block the execution.
This error occurs in the following situations:
  • The JVM that Data Validation Option uses is unable to reserve the maximum Java heap memory.
  • The system has memory but is unable to allocate it.
By default, Data Validation Option allocates a maximum heap memory of 1024 MB. This error occurs if the system on which you install Data Validation Option, is unable to reserve the specified maximum heap memory.
To resolve this error, override the default value to value lower than 1024 MB. Perform one of the following steps to lower the value:
  • Start Data Validation Option from the command line using following command:
    "<Data Validation Option installation directory>\DataValidator.exe" -J-Xmx786m -J-Xms256m
  • Create the
    DVOClient.vmoptions
    or
    DVOClientCore.vmoptions
    file in the Data Validation Option root directory and add the following line:
    –Xmx<values>
  • Edit the shortcut to the Datavalidator.exe and add the following parameter in the Target box:
    "<Data Validation Option installation directory>\DataValidator.exe" -J-Xmx1024m -J-Xms256m
The following image shows the parameter in the Target box:
The image shows the parameter in the Target box.
This section assumes that you have installed Data Validation Option and not executed any successful tests. This section also assumes that the first test is a simple test that does not contain expressions or SQL views.
The following table describes common initial errors:
Error
Possible Cause and Solution
Cannot connect to the Data Validation Option repository
Database credentials are incorrect. Check the server, port, and database name specified in the URL line. If the problem persists, contact your database administrator.
If the problem is database username and password, the error message explicitly states this.
Cannot read the PowerCenter repository
Check the repository settings up to
Security Domain
. (Informatica Domain names are not used until later.) If you cannot resolve the error, contact the Informatica administrator.
Another way to troubleshoot this error is by trying to log into the repository through the pmrep command line utility.
If you get an out-of-memory error when you access large repositories, increase the Java heap size of the Data Validation Client from the command line.
You can increase the Java heap size from the command line with the following command:
DVOClient.exe -J-Xmx<heapsize value>
Default is 1024 MB.
Installation Error
Verify that the Data Validation Option folder is closed in the Designer, Workflow Manager and the Repository Manager. The Workflow Monitor can be open.
Verify that the INFA_HOME environment variable is set.
Verify that the Data Validation Option folder exists.
Run Error
Verify that the Data Validation Option folder is closed.
Check the Informatica Domain name and Integration Service names. Verify that they are running.
Verify that the PowerCenter connection name (connection to the Data Validation Option repository) is correct, and that the user has the privilege to use it.
Open the session log and look for session errors. Most session failures are caused by an incorrect connection.
If the error is “Cannot get object class for dvo/infact/PivotPluginImpl,” the dvoct.jar file cannot be read either because it is not on the server, because of its privileges, or because the information entered in the Administrator tool is incorrect.
Verify that the user has the privilege to use the connection to the Data Validation Option repository specified in the
Tools
Preferences
Data Validation Option
database. This will also be apparent in the session log.
If you install PowerCenter 9.0.1 or earlier and the data source is SAP, install ABAP program on the mapping generated by the test in the Designer tool.
No Results
Verify that there is data in the data set you are analyzing. Tables should have records, and filters and joins should not result in an empty set.
Verify that the connection to the Data Validation Option repository specified in the Workflow Manager points to the Data Validation Option repository.