Release Notes for IDMC
- Release Notes for IDMC
- All Products
Issue | Description |
|---|---|
SCAN-24058 | When you run a Microsoft Azure Data Factory catalog source job, the job fails with a
NullPointerException error when processing control
activities. |
SCAN-25854 | When you run a Microsoft Azure Data Factory catalog source job,
the job completes with indexing and graph conversion
errors. |
CDGC-82731 | If you apply a catalog source filter on the Lineage
Discovery tab of the
Configure page, navigate to another page
in Metadata Command Center ,
and return to the Configure page, the filter
is removed. |
SCAN-24437 | When you run an Informatica Intelligent Cloud Services catalog source job to extract
metadata from Reference 360 assets in a sub-organization, the job
fails with the following error: Scan finished with abnormal
exit status. Reason: No input was
processed |
SCAN-24500 | When you run a Microsoft Azure Data Factory
catalog source job to extract pipelines, pipeline activities for the
same Run ID are split across multiple pipeline
instances. |
SCAN-24584 | When you run a SAS Base Programs (Accelerator) catalog source
job, the job fails with the following error: Parse error
(InputMismatch) on token: '('
This issue occurs due to an unsupported function syntax in the SAS script. |
SCAN-24785 | When you run an SAS Base Programs (Accelerator) catalog source job to
extract metadata from XLSX files with headers that contain empty
cells, the job fails with the following
error: NullPointerException: Cannot invoke <...>
because the return value of <...> is null
|
SCAN-23317 | When you run a catalog source job that includes stored procedures
on an SAS Base Programs (Accelerator) catalog source, the job
fails with a parsing error. |
Issue | Description |
|---|---|
CDGC-79973 | Data profiling tasks fail with the following
error: java.lang.IllegalStateException: No inferred type
found
This issue occurs when the data source contains a column
named Default. |
CDGC-76045 | If data classification delete jobs fail, you
can't perform actions such as delete, edit, or copy on the
failed data classifications. This issue occurs when you run
multiple data classification delete jobs at the same time.
|
MDP-8276 | Informatica Intelligent Cloud Services catalog source job fails if
the
https://dm-us.informaticacloud.com/*identity-service/home
IICS URL does not end with
/identity-service/home and the following
service error occurs: "Can't display the code values.
Try again later"
|
CDGC-75897 | Multiple bulk ingestion subtasks run and fail
for jobs with merge operations. This issue occurs when there
is a significant time interval between batches sent for
ingestion. |
SCAN-21247 | SAS Base Programs (Accelerator) catalog source
jobs that contain input SAS code with the symbol 'G' as the last
argument in a CALL SYMPUTX statement fail with the following
error: Unsupported expression of type: Unknown
|
SCAN-22020 | The link catalog sources logic generates
lineage for all schemas with the same prefix instead of linking
only specific schemas configured as the source and
target. |
CDGC-79252 | The permissions to manage a custom catalog
source are ignored and incorrect permissions are assigned.
|
SCAN-18674 | When Oracle Cloud Infrastructure GoldenGate
catalog sources include 'DDLERROR' and 'DBOptions' functions in
a mapping statement, metadata extraction jobs fail with the
following error: ERROR (ScannerComponent -
BaseChainExecutor:52) - Could not finish execution due
to:Parse error (InputMismatch) on token:
''DEVELOPMENT''.
|
SCAN-19989 | When you cancel a metadata extraction job, the
job status moves to Failed instead of Cancelled.
|
SCAN-21107 | When you perform connection assignment at the
database level for an SAP Business Objects catalog source, you
can't view the lineage information between external connections
and reports. This issue occurs if the source system includes
reports without a schema.
|
CDGC-81704 | When you run a File System catalog source job
and perform data classification, the hierarchical fields in JSON
files don’t get classified.
|
SCAN-7159 | When you run a Microsoft Azure Data Factory
catalog source job, the job fails with the following error:
No default value for the following
variable:[].
This issue occurs when you use a default parameter in
Dataflow. |
SCAN-19769 | When you run a Microsoft Azure Data Factory
catalog source job to extract dynamic pipelines with the JSON
function, the job succeeds, but the lineage shows data sets as
expressions.
|
SCAN-20061 | When you run a Microsoft Azure Data Factory
catalog source job to extract metadata from pipelines that
contain activities with system variables, the system variables
don't get extracted.
|
SCAN-16293 | When you run a Microsoft Azure Data Factory
catalog source job to extract supported activities that include
variables with the Array data type, Data Governance and Catalog doesn't display the lineage and
generates the following error: Could not evaluate ADF
expression @variables
|
SCAN-17082 | When you run a Microsoft SQL Server Analysis
Services catalog source job, the job fails with the following
error: Parse error (InputMismatch) on token:
'(' . This issue occurs due to unsupported
statements in the script. |
SCAN-10927 | When you run a Microsoft SQL Server Reporting
Services (SSRS) catalog source job, the job fails with the
following error: Connection property not a key=value
pair
This issue occurs when you use a connection property value
that contains the = character. |
SCAN-21406 | When you run a MicroStrategy catalog source
job, the job fails with the following error: Could not
initialize MicroStrategy COM API. Error code=0x80040154.
Message: Class not registered
|
SCAN-20539 | When you run an IBM InfoSphere DataStage
metadata extraction job, if the job includes a 'Create Table'
action with a parameterized table name, the parameter is not
resolved correctly.
|
SCAN-20779 | When you run an Informatica PowerCenter
catalog source job on a Windows Secure Agent that uses MS
Windows Latin 1 code page to read and write data, the job fails
with the following error: pmrep's code page (UTF-8
encoding of Unicode) is not one-way compatible to repository
PCPROD's code page (ISO 8859-1 Western European) .
|
SCAN-20141 | When you run an Oracle Cloud Infrastructure
GoldenGate metadata extraction job, the job fails with the
following error: Parse error (InputMismatch) on
token: 'TARGET'
The issue occurs when there is no comma before the 'TARGET'
clause in a map statement. |
SCAN-17266 | When you run an SAS Base Programs
(Accelerator) or an SAS Base Libraries (Accelerator) catalog
source job to extract metadata from SAS macro definitions, the
job fails with the following error: Parse error
(InputMismatch) on token: '%include'
|
SCAN-21769 | When you run a TIBCO Spotfire catalog source
metadata extraction job, the Test Connection phase lasts for an
extended amount of time.
|
SCAN-22071 | When you run metadata extraction jobs on SAP
BusinessObjects catalog sources, the jobs fail with the
following error: Illegal Argument: The
DirectoryStructureModel <...> already contains a
ConnectionStoreContent with this Name
|
CDGC-76545 | When you schedule a custom catalog source
metadata extraction job to run on a recurring basis, the Type
value in the Data Governance and Catalog search filter changes.
|
MDP-8669 | When you unassign connections, the reindexing
operation in the connection unassignment job fails with the
following error: Column '<column name>' does
not exist.
|
SCAN-20971 | You can't view data element level lineage
information for an IBM InfoSphere Datastage catalog source that
reads data from a data set and writes to a database table.
|
SCAN-20214 | You can't view lineage from table to view when
you run an incremental metadata extraction job.
|
Issue | Description |
|---|---|
MDP-4190 | When you run multiple jobs with merge
operations that have object references across multiple source
systems, the jobs complete with errors in the DEBUG log or fail
with the following error: Indexing failed
|
SCAN-13790 | When you run a metadata extraction job on an SAP Datasphere
catalog source, the job fails with the following error:
Could not execute Datasphere
API
This issue occurs when the access token for the client ID
expires.
|
SCAN-18203 | When you run a Microsoft Azure Data Factory
catalog source job that calls a Databricks notebook, the job
fails with the following error: Python code raised an
exception: unsupported operand type(s) for | : 'type' and
'PythonNone'
This issue occurs when the Databricks notebook contains the
PythonNone element. |
SCAN-18072 | You can’t clone the configuration of an Informatica
PowerCenter catalog source. This issue occurs due to double
encryption of passwords. |
SCAN-17887 | When you run SAS Base Programs (Accelerator)
catalog source jobs on external tables in a Teradata Database,
the jobs fail with the following error: Failed to
process SasProcSqlOptions
|
SCAN-17884 | When you run metadata extraction jobs on SAS
Base Programs (Accelerator) catalog sources, the jobs fail with
the following message in the debug log:
com.compactsolutionsllc.cdimc.common.exceptions.ParseException:
Parse error (NoViableAlt) on token: 'float'.
|
SCAN-15867 | When you run a Microsoft Azure Data Factory catalog source
job to extract metadata from pipelines that contain Switch
pipeline activity, the subsequent child activities don't get
extracted.
|
SCAN-15301 | Metadata extraction jobs fail for an Oracle
Golden Gate catalog source and the following error message
appears in the debug log file: Parse error (NoViableAlt)
on token: 'integratedparams'. Line.column: 29.15, Text: [
>integratedparams< (_logminer_parallel_read ]
com.compactsolutionsllc.cdimc.common.exceptions.ParseException:
Parse error (NoViableAlt) on token: 'integratedparams'.
Line.column: 29.15, Text: [ >integratedparams<
(_logminer_parallel_read . This issue occurs if
the source system includes the
TRANLOGOPTIONS function in an
extract or replica asset.
|
MDP-6272 | Data profiling tasks fail with the following
error:
This issue occurs when the column name includes the SELECT
keyword and you run the task with the Top N sampling option. |
MDP-4190 | When you run multiple jobs with merge
operations that have object references across multiple source
systems, the jobs complete with errors in the DEBUG log or fail
with the following error: Indexing failed
|
CDGC-77083 | When you customize an Asset Type layout, the
list of user groups displays a maximum of 20 entries.
|
Issue | Description |
|---|---|
SCAN-12619 | Metadata Extraction jobs fail to parse
Databricks Python pipeline activities for Microsoft Azure Data
Factory catalog sources and the following error occurs:
|
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:
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:
|
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:
|
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:
|
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:
|
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:
|