Release Notes for IDMC
- Release Notes for IDMC
- All Products
ASK INFAPreview
Please log in to access Ask INFA.
ASK INFAPreview
Issue
| Description
|
|---|---|
CDIPC-14771
| The Data Integration Service registration to CloudConnect failed with the
Request to registered endpoint was not successful error.
|
CDIPC-14717
| On AIX 7.3, when you migrated a PowerCenter domain to CDI-PC, the migration completed successfully, but the
Migration Assessment Summary window displayed the following incorrect result:
[Fail] Operating System: Operating system not supported. Refer PAM for the list of supported operating system.
|
CDIPC-14712
| CDI-PC install failed while running the
SilentInputMigrate.properties file to migrate a domain in silent mode.
|
CDIPC-13927
| In an AIX environment with the Data Integration Service enabled to use Operating System Profiles (OSP) in a CDI-PC domain, while running a native Data Engineering Integration mapping with a Java transformation, the mapping failed with the following error:
[ICMD_10033] Command [runmapping] failed with error [[CORE_0003] An internal exception occurred with message: java.lang.Exception: [MPSVCCMN_10094] The Mapping Service Module failed to run the job with ID [7MNKxvmGEe-1CQU2CNB4BQ] because of the following error: [EdtmExec_00007] [DtmDTF_0001] Data Transport Error, Origin :[IProxyDTMService :: stopDTM RPC].].
|
CDIPC-13917
| When migrating an SSL- or Kerberos-enabled 10.5.x or 10.4.x PowerCenter domain configured in IBM DB2 to CDI-PC, the
Migration Assessment Summary window displayed an incorrect result.
|
CDIPC-12036
| When creating the CDI-PC Repository Service using the installer, incorrect connection failure messages were intermittently logged in the CDI-PC log files.
|
WB-6988
| The mapplet count in the assessment summary report and the repository dashboard did not match.
|
WB-7294
| When you converted Data Engineering Integration assets from Model repositories, the assets were not published if mapplets contained targets.
|
WB-7213
| After a Model repository assessment was complete, the Mapplets sheet of the
<Repository_Name>_ASSESSMENT_SUMMARY Excel file displayed the mapplet name instead of the mapplet instance name.
|
WB-7848
| After converting mapping assets, connecting links were missing between transformations.
|
Issue
| Description
|
|---|---|
WB-7076
| Converting mapping assets to Data Integration failed if the assets contained graphic data types.
|
WB-7034
| Repointing assets from Oracle to Databricks resulted in an incorrect table name as default-table after conversion.
|
WB-6957
| The schema name specified in the advanced properties of the repointed connections was not applied correctly and the schema name from the last connection was used for all transformations.
|
WB-6917
| Conversion task failed due to an error in the process workflow.
|
WB-6909
| Conversion of workflow assets failed if an unsupported XML source was found in a mapping task with repoint configuration.
|
WB-6872
| Conversion of mapping assets failed with the error
Exception occurred while publishing asset to CDI ===> 403 Forbidden due to duplicate parameters of the reused mapplets.
|
WB-6857
| After converting mapping assets, the data size of joined columns was not being adopted correctly, causing joiner failures.
|
WB-6491
| Conversion of mapping tasks failed with
403 Forbidden error due to unresponsive sequence transformations within mapplets.
|
WB-6289
| When you ran conversion tasks using Workbench automation, the tasks failed due to heavy workload on the service.
|
WB-6191
| The assessment report Excel file downloaded from CDI-PC contained the IDs of the manual and partial flags instead of the flag names. For example, the report contained
TCT_SEQ_GEN_SAME_PIPELINE as the flag name instead of
Transformation Sequence Generation Same Pipeline .
|
WB-6088
| The description column of the assessment report Excel file did not include the list of flags if none of the flags contributed to the partial conversion status of a workflow.
|
Issue
| Description
|
|---|---|
CDIPC-12805
| In AIX, the creation of CDI-PC repository content in a CDI-PC domain using Kerberos authentication failed when attempting to create the content through the CDI-PC installer.
|
CDIPC-11792
| In AIX, after uninstalling CDI-PC server using the console mode, the directory structure did not get deleted.
|
CDIPC-8242
| Uninstalling CDI-PC removed all files and folders that you had placed in the
<UID>/Informatica directory.
|
PC2C-8109
| Conversion of PowerCenter assets to Cloud Data Integration failed if mapping assets contained native transformations and unsupported application specification.
|
WB-5549
| After you exported metadata of taskflow assets to update command tasks, the bulk update task report contained an incorrect value for the runtime environment.
|
WB-5372
| After you exported metadata of mapping assets to update mapping SQL queries, the bulk update task failed if the query length of an asset exceeded 32,000 characters.
|
WB-1605
| After you re-assessed a repository, the conversion status of the converted assets changed to
Pending even if there was no change to the PowerCenter assets.
|
Issue
| Description
|
|---|---|
CDIPC-11068
| One of the CDI-PC installer screens on migration,
Migration Prerequisites - Step 2 of 8 , displayed an incorrect message about the need for an Informatica domain to not be Kerberos authenticated.
|
CDIPC-10816
| The operating system fails with the following error when you run the
Pre-Installation (i10Pi) System Check Tool on Red Hat Enterprise Linux 9 hosts:
[Fail] Operating System: Operating system is RHEL 9.3 (Plow). Operating system version is 5.14.0-362.24.1.el9_3.x86_64. Install an operating system that is supported with the CDI-PC installation. Refer to the Informatica Product Availability Matrix (PAM) for platform support information.
|
CDIPC-10259
| If a domain name included non-EN characters, the domain update took longer than usual to complete.
|
CDIPC-10213
| In a multi-node domain update, the update did not complete if the master gateway node did not start after the update. Because the master gateway node identified when the update began must update and start before other nodes updated, the update did not progress.
|
CDIPC-10137
| If you update the domain name or port number after an update fails, the update fails when you retry the update.
Workaround: Change the domain details to what they were when you initiated the update on both the domain machine and in the domain details in
Informatica Intelligent Cloud Services . Then retry the update.
|
WB-4058
| When you created a
Connection Map configuration and ran a conversion task with the configuration, the Secure Agent uploaded the
Connection_Details.xls file to internal storage.
|
