Issue | Description |
|---|---|
CDIPC-16064 | When you migrate a non-TLS PowerCenter domain with HTTPS enabled for the Administrator tool to CDI-PC, the UpdateDomainOptions command fails. Workaround:
infacmd UpdateDomainOptions -dn <DOMAIN_NAME> -pd <DOMAIN_PASSWORD> -un <DOMAIN_USER> -do TLSMode=true -sdn <SECURITY_DOMAIN_NAME> For detailed instructions on how to run the UpdateDomainOptions command, see UpdateDomainOptions. |
CDIPC-15557 | When you create a CDI-PC domain using non-ASCII characters in the domain and node names, and configure the Integration Service and Repository Service with the Japanese Extended UNIX Code (including JIS X 0212) code page, the CDI-PC Integration Service fails to enable with a code page mismatch error. Workaround: To resolve this issue, you must align the code pages so they are identical.
|
Issue | Description |
|---|---|
WB-7212 | When you assess a Model repository, the <Repository_Name>_ASSESSMENT_SUMMARY Excel file displays the application count in the repository as zero. |
Issue | Description |
|---|---|
CDIPC-12172 | In a Kerberos-authenticated environment, when the CDI-PC domain goes into offline mode, the Data Integration Service and Model Repository Service pages don't load in Informatica Administrator (the Administrator tool). Additionally, running a workflow from the Administrator tool returns an incorrect error message stating that the domain is de registered. |
Issue | Description |
|---|---|
CDIPC-12127 | After you migrate a domain to CDI-PC, the first scheduled purge run fails with the following error: [2024-08-14 19:36:30,237 IST] [ERROR] [Purge_Metering_Data_Worker-Thread_1] [PurgeMeteringDataTask] [CloudConn_10204] Metered data purge failed for repository [RS_ALL_1056]. Error: [Text '' could not be parsed at index 0] [2024-08-14 19:36:30,239 IST] [ERROR] [Purge_Metering_Data_Worker-Thread_1] [PurgeMeteringDataTask] [CloudConn_10204] Metered data purge failed for repository [RS_CDC]. Error: [Text '' could not be parsed at index 0] However, the purge runs after the first failure is successful. |
Issue | Description |
|---|---|
WB-3928, WB-3876 | If a conversion task contains a mapping that was already converted into a Data Integration mapping, the conversion job fails if there is any change in the mapping parameters. You might observe one of the following errors: 403 Forbidden: Provide a parameter with following name and type 500 Internal Server Error: Unable to load object - You do not have sufficient privileges or permissions to access the requested asset Workaround: Delete the assets with the same name from Data Integration conversion location and run the conversion task again. |