When you run a profiling task after enabling CLAIRE Insight inference, the CLAIRE Insight inference fails intermittently with the following error:

Could not roll back JPA transaction; nested exception is org.hibernate.TransactionException: Unable to rollback against JDBC Connection

Profiling fails on Snowflake with the following error when the schema name is in lowercase:

org.springframework.web.client.HttpServerErrorException$InternalServerError: 500 Internal Server Error

When you create a mapplet connection profile from a source mapplet with two joined SQL Snowflake connections and run the profile, the job fails with the following error:

Profile job failed with error null.

When you export a profile that is configured with an SQL filter condition, the exported file doesn't contain the filter condition.

Profiling fails on Snowflake with the following error while processing rows of a large table:

SQL [n/a]; nested exception is org.hibernate.exception.DataException: could not execute statement

When you create a data profiling task on a data source with the JDBC v2 connection, you can't select a table as the source object after you select a schema.

Data Profiling rounds up the profiling result percentages to 0% instead of 0.01% when only one row out of more than 10 million rows matches the specified data quality rule.   

When you update the advanced options for a pattern and rerun a data profiling task, the result displays an incorrect number of rows.

When you enter additional JDBC connection parameters for a Snowflake connection in a profiling task, Data Profiling recognizes the following keys in uppercase but not lowercase characters:

DB
SCHEMA

When you test a rule specification that CLAIRE generated as an insight on a profile, the test fails.

When you run a profiling job that reads data over a JDBC V2 connection and you filter the data on a date or timestamp column, the job fails.

When you run a profiling job on a mapplet, the profiling job fails. The issue arises when the source and target fields have the same names.

A profile job can fail on an upgraded POD if a profile was running at the time that the POD was upgraded.

Data Quality and Governance adds a duplicate rule occurrence to a scorecard profile in the following scenario:

You import a profiling task and run the task.
You import the profiling task for a second time and run the task again.

When you create a mapplet connection profile from a source mapplet with two joined SQL Snowflake connections and run the profile, the job fails.

When you create and save a Databricks profile and then edit the Advanced Options configuration, the columns disappear and the profile is not saved.

When you run a Databricks profile, add a filter or use the SQL override option, and re-run the profile, the job fails with the following error:

[FATAL] The following SQL exception occurred: [Unable to prepare statement for query...}

When you run a Databricks profile on a source that contains mixed-case column names and then apply a query on the columns, the query job fails with the following error:

SQL Error [ FnName: Prepare – [Simba][Hardy] (80) Syntax or semantic analysis error thrown in server while executing query.

When you run a Databricks profile on complex data types in advanced mode, the profile results for the columns include junk values.

When you add a rule to a profile and then run the profile, you can't compare rules and columns on the Compare Columns tab.

If you want to use the Explore page to run a profile, the

Run

option doesn't appear in the drop down menu.

When you run a profile on a source mapplet and you want to select Databricks source object, the profile job fails with the following error:

The selected mapplet <> is not supported as a source object for profiling

.

When you run an Amazon Redshift profile on assets with the SUPER data type, the job fails with the following error:

Invalid datatype: super

.

When you run a query on Databricks profile results, the job fails with the following error:

Syntax or semantic analysis error thrown in server while executing query

. This issue occurs when you use mixed case or special characters in your query.

When you run a few profiling tasks concurrently, the insight inference job fails with the following error:

Job for profile <> threw an exception. Returning no results

.

When you run the profile on a Salesforce source object, the job fails when some scale values in numeric fields are automatically defined as greater than precision values.

When you run a profiling task for a source that contains empty tables or files, the scores show 0, but they are pushed to the Rule Occurrence.

When you export a profile that uses a mapplet as a source object and import the same profile, the profiling job fails with an internal DTM error.

When you create a profile on a source mapplet, the profiling job fails with the following error:

FileNotFound exception

When you export values that include accented characters, such as "Ó", to a dictionary, the values do not appear correctly in the dictionary.

When you export profiling results to an Excel file, the profile URL available in the Excel file is incorrect.

When you run a profiling job for a Google Big Query source and apply the timestamp filter, the profiling task fails with the following error:

No matching signature for operator >= for argument types: TIMESTAMP, DATE

When you delete a profile or a profile run with rule occurrences, the corresponding scorecard results are not deleted.

When you create a profile with source mapplets that include binary datatypes in the output field, the drilldown job fails.

You can't preview data on a profile that reads an SAP, Amazon Redshift, Snowflake, Amazon S3, Amazon Athena, Azure Data Lake Storage Gen2, or Google BigQuery the source object.

The changes that you make to an exception rule and a profile appear incorrectly, and the following error message appears:

Unsaved Changes warning message

. This issue occurs when you perform the following steps:

In Data Quality, create an exception rule.
In Data Profiling, create a profile using a CSV file source object for a flat file connection.
Save the profile and create a exception task.
Edit the exception rule to remove input columns that are configured in the rule specification.
Add new columns and configure the exception rule.
Save the rule.
Edit the profile to change the source object.
Save the profile

Data Profiling

does not consider the schema name in the source connection while running the profiling job.

When you enable the

Disable data storage value

option for an Administrator role,

Data Profiling

displays the sensitive information such as minimum and maximum values on the profiling

Results

page. This issue occurs if use

Data Profiling

on an advanced cluster.

The

Columns

tab in a profile does not display columns of the double data type for an Amazon Athena source object.

A drilldown operation on profiling results fails in the following scenario:

The profiling task reads an SAP HANA source object over an ODBC connection.
You drill down on a column of string data types.

When you run a profile on a Databricks Delta source object that includes nested complex data types such as array of array or array of map, the profile job fails.

When you run a profiling task with a query on a Google BigQuery source object, the session log does not display the query that the profiling task uses.

If you run a profiling task on a mapplet that reads a Microsoft SQL Server source object, the profiling task fails.

When you run a query on a profiling task that reads an SAP HANA source object over an ODBC connection, the query fails.

A profiling task fails when you apply a query filter on a MariaDB source object.

A profiling task fails in the following scenario:

You run the task on a source object over an Amazon Redshift V2 connection.
The source object contains a column with the timestamptz data type.

If you schedule multiple profiling tasks to run concurrently, some insights jobs that include inferred insights may fail.