Issue | Description |
|---|---|
SCAN-16620 | When you run an Informatica PowerCenter catalog source job with a parameter file that contains spaces in a [global] heading, the metadata extraction job fails to parse the file content. |
SCAN-16414 | Duplicate mapping task instances appear on the Relationships tab of mapping task assets in Data Governance and Catalog. This issue occurs if the mapping task includes tables, and you perform connection assignment with IDMC metadata as the origin catalog source, and then run the mapping task again in Data Integration. |
SCAN-15712 | If you run a dbt catalog source job to extract metadata from schemas, the metadata extraction job completes with the following error: Unable to process dbt node model.cci_dbt_foundation_project.psu_migration_dim. com.compactsolutionsllc.cdimc.common.exceptions.CdimcRuntimeException: Exception while executing query: show streams like '%' in "product" This error occurs if model files include SQL queries that refer to schemas with names in lowercase. |
SCAN-15175 | When you run a Microsoft Azure Data Factory job to extract metadata from ADF pipelines, the job fails to evaluate ADF expressions. This happens when the expressions cite other expressions nested two or more levels beneath the main pipeline flow. |
SCAN-14755 | When you run an Informatica PowerCenter catalog source job to extract metadata from a workflow, the job does not extract the schema specified in the 'Transaction Environment SQL' attribute. |
SCAN-14451 | When you run a metadata extraction job on SSRS reports that contain MDX queries with a Microsoft SQL Server Analysis Services catalog source, the job fails with the following error: Unable to parse script |
SCAN-13584 | An Informatica PowerCenter catalog source job generates the following parse error if you include a curly brace (}) within a comment in an SQL query: Cannot parse SQL: Unable to parse script |
SCAN-13583 | An Informatica PowerCenter catalog source job generates the following parse error if there are no output connectors for the Source Qualifier: Cannot parse SQL: Unable to parse script |
SCAN-13571 | When you run an IBM InfoSphere DataStage catalog source job that uses a relational stored procedure in the target table, the job fails with the following error: java.lang.RuntimeException: java.util.NoSuchElementException: No value present. |
SCAN-13539 | When you run a Microsoft Azure Data Factory catalog source job to extract metadata from pipelines, the ForEach activity links the source records to the target tables instead of linking each record processed by the activity to one target table based on the query. |
MDP-6101 | Data Preview jobs for failed rows fail for tables that contain reference data elements. This issue occurs when you set the Cache Result property value to No Cache for the Data Quality rule occurrence. |
CDGC-75614 | When you create a user group policy, only up to 200 user groups appear in the list to select the user group. |
Issue | Description |
|---|---|
MDP-3995 | Data Quality jobs fail with the following error: Index 16 out of bounds for length 15 This issue occurs if the source system contains data elements with an unsupported data type. |
CDGC-72507 | When you configure a custom attribute, the maximum character length of the placeholder text is 255 instead of 512. |
CDGC-69187 | The following error occurs if you modify the default value of a published custom attribute and save it: Cannot perform the operations on attribute draft. Invalid Default values passed in request payload. Correct the error and try again. |
CDGC-72365 | Data Preview jobs for failed rows fail for tables or views that contain columns or view columns with NVARCHAR(MAX) data type. This issue occurs when you set the Cache Result property value to No Cache. |
SCAN-11414 | If you run a Microsoft Azure Data Factory catalog source job to extract metadata from pipelines that include an AND expression, the metadata extraction job fails. |
SCAN-13768 | If you run an Oracle Business Intelligence catalog source that includes an expression attribute of a size greater than 32 KB, the bulk ingestion job fails with the following error: ElasticsearchException[Elasticsearch exception [type=max_bytes_length_exceeded_exception, reason=max_bytes_length_exceeded_exception: bytes can be at most 32766 in length; got 60735]] |
Issue | Description |
|---|---|
SCAN-12375 | If you run a Microsoft SQL Server Analysis Services catalog source job with source data that contains empty perspective tables, the metadata extraction job fails with the following error: Cannot convert project: <...> due to: Cannot invoke <...> because the return value of <...> is null |
CDGC-66205 | Data Quality jobs that include a rule specification created in Data Quality with a space in the rule set name fail with the following error: Workflow generation failed for object: <...> with error: Output Port PrimaryRule Set3 does not exist in specified rule. |
SCAN-11408 | When you run a Microsoft Azure Data Factory catalog source job to extract metadata from pipelines, the job fails with the following error: ERROR (ScannerComponent - ApplicationWrapper:124) - Fatal exception occurred during metadata extraction: null java.lang.StackOverflowError: null |
Issue | Description |
|---|---|
CDGC-69269 | IDMC metadata jobs fail with the following error: Content-Service: Request Failed. |
CDGC-67025 | Batch profiling tasks fail with one of the following errors: org.hibernate.exception.LockAcquisitionException: could not execute statement Exception occurred in Clearing Staging Contents with error : timeout |
Issue | Description |
|---|---|
CDGC-65232 | If you run a catalog source job that includes data profiling on a Secure Agent that has IDMC metadata enabled, profiling-related parameter files might remain in the IDMC metadata directory. |
CDGC-66208 | If you perform connection assignment that is not case-sensitive and then unassign the connection, the reference asset location gets changed and the Hierarchy tab in Data Governance and Catalog doesn't display any information about the asset. |
CDGC-67045 | If you schedule multiple jobs to run simultaneously on a runtime environment with more than one Secure Agent available, all of the jobs are routed to the same Secure Agent. |
SCAN-10310 | When you run an Informatica Intelligent Cloud Services catalog source job to extract a mapping task run from a taskflow, the metadata extraction job fails with the following error: Problem loading metadata from Cloud: Problem fetching tasks from Cloud: Could not read xml: due to: Premature end of file. |
SCAN-6549 | When you run an Informatica PowerCenter catalog source that includes parameters for the source or target, the parameter name appears in the Connection Name field on the Connection Assignment tab. |
SCAN-8296 | If you run a MicroStrategy catalog source job with the Miscellaneous Options -sp or -sf to skip extracting folders or prompts, these objects are still extracted. |
SCAN-5074 | When you run a Microsoft SQL Server Analysis Services catalog source, the job succeeds but does not extract metadata from all projects. |
CDGC-66502 | You can't copy a custom catalog source configuration. |
CDGC-64417 | When you run a Data Profiling or Data Quality job on a File System catalog source that includes files with special characters, the job fails with the following error: java.lang.RuntimeException: java.io.IOException: (startline 1) EOF reached before encapsulated token finished |
CDGC-66398 | Data profiling tasks that run on the Windows Secure Agent fail if the source data contains table or column names with Norwegian characters. |
SCAN-9895 | When you run a Microsoft Azure Data Factory catalog source job to extract metadata from Databricks expressions, the job succeeds but the transform function generates a parsing error. |
Issue | Description |
|---|---|
CDGC-60416 | When you run an SAP BusinessObjects catalog source job, the job fails with the following error: unable to browse miti content |
CDGC-63241 | When you run a Data Quality job, the job fails with the following error: Workflow generation failed for object: <table name> with error: null |
CDGC-64580 | When you modify a schedule and try to save it, the save fails with the following error: Filter Config not valid option group name. |
CDGC-66080 | When you customize custom attributes, the default value of attributes with Multi-line Rich Text subtype appears as "HTML TEXT", regardless of the default value that you specify when you create the custom attribute. |
CDGC-66006 | An IDMC Metadata Bulk Sync job with a filter to include metadata from a folder in a project fails to extract metadata from the folder if the folder and project have the same name. |
SCAN-8470 | When you run a relational catalog source job with a filter to include metadata from a table, the job merges the columns of all tables with the same name in a different case. |
SCAN-6088 | When you run an Informatica Intelligent Cloud Services catalog source job, metadata extraction fails with the following error: Fatal exception occurred during metadata extraction: null This issue occurs if you perform connection assignment to a Microsoft Azure Data Lake Storage Gen2 source system that contains a partitioned file path with a forward slash (/). |
Issue | Description |
|---|---|
MDP-2789 | Upgrades of Metadata Command Center, Data Governance and Catalog, and Data Marketplace fail when there are IDMC metadata jobs in the starting, running, or submitted status. |
SCAN-757 | When you run a Microsoft Azure Data Factory catalog source job to extract metadata from pipelines that contain only Execute Pipeline activity, the parent pipeline doesn't get extracted. |
CDGC-63901 | When you disable a catalog source job schedule that was created before April 2024, the job runs based on the schedule and fails. |
Issue | Description |
|---|---|
MDP-2789 | When you enable IDMC metadata in Metadata Command Center and run a Data Integration task, multiple IDMC metadata jobs appear on the Monitor page in Metadata Command Center. |
CDGC-63899 | When you configure a schedule for multiple capabilities and save the schedule, the time and date are incorrectly saved. |
CDGC-59471 | When you use File System catalog source to extract metadata from a Microsoft Excel file and the size of the file exceeds 20 MB, the metadata extraction job fails with the following error: Failed to extract metadata for file<file id>. |
MDX-38136 | When you export ISX files to IBM InfoSphere DataStage catalog source and some DataStage jobs include an empty Parameter Set, the export job fails with the following error: Cannot read ISX parameter set entry. |
MDX-35518 | When you run a Microsoft Azure Data Factory catalog source job that contains files with names that start with @, the job fails with the following error: Cannot convert graph default-121 to GraphToDatabricksModelConverter model. Trying to build asset from data_file but it's name is empty. |
MDP-2209 | Relationship discovery tasks fail with the following error: Task with name: Relationship Discovery id: <ID> failed/errored. Please contact Informatica support. |
CDGC-61500 | You can add new asset types to an existing workflow configuration with active tickets even if the role assigned to the workflow does not have the necessary privileges to access the new asset type. |
CDGC-43141 | When you run data profiling tasks on any catalog source, few objects fail with the following error: Exception occurred while copying session log for the mapping |
MDX-41052 | When you run an Informatica Intelligent Cloud Services catalog source job, the job fails with the following error: Could not find session extension for key: < > This happens because of an unconnected source component. |
MDX-41050 | When you run an Informatica Intelligent Cloud Services catalog source job, the job fails with the following error: Could not process session <...> due to: expected one element but was: <...>. This happens because of the presence of more than one operation in the parser IMX node. |
MDX-40847 | When you run an Informatica Intelligent Cloud Services catalog source job, the job fails with the following error: Could not convert source due to: Unsupported attribute value for: {} The job fails because of the unsupported "{}" attribute value present in the source data. |
CDGC-57352 | Extra spaces in Excel worksheet names are included in core.location and core.name values in Avro files for Qlik Sense catalog sources. |
CDGC-56514 | File System catalog sources extract created on and modified on attribute values from source files instead of the Windows file system. |
CDGC-57833 | If you define table names within quotes, Qlik Sense catalog source jobs don't extract tables as expected. |
MDX-40365 | When you run a Microsoft Azure Data Factory catalog source job to process operational metadata, the job fails to fetch all the pipeline instances and fetches only the first 100 pipeline instances. The incorrect count of pipeline instances appear on the Metadata Extraction Details panel of the catalog source job in Data Governance and Catalog. |
MDX-39378 | Extraction of metadata from a tabular model using the Microsoft SQL Server Analysis Services catalog source fails with the following error: java.lang.NullPointerException: null |