Release Notes > Known issues
  

Known issues

The tables in this section describe known issues for Data Governance and Catalog.

November 2025 known issues

Issue
Description
CDAM-5816
When applying data protections to an Oracle data source, Data Marketplace treats number data type values as an integer. Data Integration treats number data type values as a decimal.
CDGC-87483
When you run a data profile on CDS views from an SAP ERP source system, the profiling job fails with the following error message:
Unsupported metadata builder for com.infa.odin.models.application.saps4hana.CDSViews
CDGC-87451
When you run a data profile with the Less Than or Equals or the Greater Than or Equals operator in the filter conditions, the profiling job fails with the following error message:
No enum constant com.informatica.ccgf.components.profiling.api.scope.config.Operator.LESS_THAN_OR_EQUALS
CDGC-86787
When you run a data profile, the value frequency results for columns with null values appear as empty values.
CDGC-86697
When you run a data profile, the column statistics do not display the minimum and maximum values for data elements from the following source systems:
  • - Databricks
  • - IBM Db2 for LUW
  • - Amazon Redshift
  • - SAP HANA Database
CDGC-81354
When you create a workflow ticket to track asset creation, the ticket does not go into the Resolved status. Even after the asset is created and you resolve the ticket, the ticket is goes back to the Open status and the associated asset stays in the In review status.
SCAN-28874
There is a possible issue that when Metadata Command Center scans IDMC metadata that contains multiple Data Integration mapping tasks, it misidentifies the data protection attributes. Set filters to ensure that Metadata Command Center only scans a single mapping task.
SCAN-28779
If you make changes to a data access policy after running a Data Integration mapping task and scanning the IDMC metadata, the changes to the data access policies are only reflected when running a mapping task through a taskflow.

July 2025 known issues

Issue
Description
CDAM-5553
If you’re using a connection to Databricks to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.
CDGC-82928
The Save button for the catalog source is disabled if you apply the data observability exclude metric filter for Data Type and Data Freshness.
CDGC-82861
Data de-identification policies automatically inherit stakeholders from the associated precedence tiers. Although the user interface does not display these stakeholders, you can still initiate a workflow.
CDGC-82823
When you open a data observability anomaly event page for the first time, the bar chart for the selected metric might not appear.
As a workaround, refresh or reopen the data observability event page to load the bar chart.

April 2025 known issues

Issue
Description
CDGC-78895
On the History tab of a ticket page, the Task Assignee Users and Task Assignee Groups attributes display the values, Deleted User and Deleted Group even when the asset has no stakeholders that were deleted.
CDGC-77401
On the New Tasks Inbox > Unassigned Tasks tab, the system displays tasks that are assigned only to you until you click the Claim button. The Claim button appears even for tasks without multiple stakeholders.

February 2025 known issues

Issue
Description
CDAM-4045
When using Managed Access in Data Marketplace with an Oracle source system, if the Oracle connection permissions are incorrect, it might fail silently, not presenting any tables to the user.
CDAM-2623
When running a mapping that includes an Access Policy transformation in Data Integration, policy resolution fails and an error appear if the source is Amazon S3 in Parquet or Avro format.
MDP-6191
When you import assets that have custom attributes values with commas, the bulk import job reports an error.
SCAN-16942
The Amazon S3 file type ORC appears as 'Undefined' in Data Governance and Catalog.

November 2024 known issues

Issue
Description
MDP-5743
If there are duplicates in the reference source system or in the endpoints, after you perform case-insensitive connection assignment, the unmatched assets might still appear as reference objects in the endpoint hierarchy.
SCAN-14621
Reference resource names for SAP Business Warehouse and SAP BW/4HANA catalog sources appear as 'XXXX' in the lineage.

September 2024 known issues

Issue
Description
MDP-2133
The job for previewing failed rows for SAP Business Warehouse (BW) and SAP S/4HANA catalog sources fails with an error.
To work around this issue, perform the following steps:
  1. 1In Metadata Command Center, open the catalog source.
  2. 2On the Data Profiling and Quality tab, select the Agent Cache option in the Cache Result field.
  3. 3Run the catalog source.