Table of Contents


  1. Abstract
  2. Informatica Installation
  3. Informatica Upgrade
  4. 10.1 Fixed Limitations and Closed Enhancements
  5. 10.1 Known Limitations
  6. Informatica Global Customer Support

Profile and Scorecard Known Limitations

The following table describes known limitations:
Outlier detection does not work when the profiling warehouse is on a Microsoft SQL Server database.
Domain discovery fails when you choose all the data domains and choose Hive as the run-time environment.
When you create and run a column profile on the Blaze engine, the columns display incorrect scale and sometimes infer incorrect data type.
In the Analyst tool, the outlier count in summary view displays 0 instead of N/A when the following conditions are true:
  1. You create and run a column profile.
  2. In the summary view, you detect outliers.
  3. You edit the profile and run the profile.
  4. You view the profile results in summary view.
Column profile runs for a Sqoop source fail when you select a few columns for the profile.
Workaround: Select all the columns for column profiles with Sqoop source.
When you create and run a column profile on a data source that has a column with Timestamp with Time Zone data type and you choose Hive or Hadoop as the run-time environment, the profile run fails.
There are no infacmd sch commands for profiles and scorecards.
In the Developer tool, when you use Apache Drill to create a Parquet file and you create a column profile on the Parquet file, an error appears.
Column profile run fails when you configure a JDBC connection for the profiling warehouse and you run the profile on the Blaze engine.