Domain Updates

Back Next

Troubleshooting update issues

A domain update can fail due to multiple reasons. View the error logs and correct the issue before you retry the update.

The update fails with unrelated error messages even after multiple restarts.: An update might fail at any stage and generate an error message. When you correct the issue mentioned and restart the update, the update fails again with an error message.; To correct the issue, perform the following tasks:
Verify the node status on the
CDI-PC Home page
.
If the node is unavailable, run the infaservice start command.
When the node is available, restart the update.

The node update appears as successful but the Clean-up stage generates a warning.: If you change port numbers or make other changes to a domain during an update, the update might complete but generate warnings.; You can ignore clean-up and finalize stage warnings if the node update is successful. To avoid such errors, don't make domain changes during updates. Domain changes can include changes to port numbers, domain name, and addition or removal of nodes.

Update fails during the Download stage with a certificate error in the taskoutput log file.: To enable communication between the Secure Agent and the domain, both the truststore certificates must be shared and available. If the update fails during the download stage because of a certificate error, the domain truststore and Secure Agent truststore certificates might not be exchanged. You see the following error:
Please check the host, port and TLS configurations. Error: [javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target]; Verify that the Secure Agent contains the domain truststore and that the domain certificates folder contains the Secure Agent certificate. See
Cloud Data Integration for PowerCenter Installation
for information. Stop all running processes associated with the domain and then retry the update.

Update fails at the Initialize stage and the page becomes unresponsive: The update fails and the page becomes unresponsive when the required amount of disk space is not available on the node. You see the following error in the CloudConnect logs:
[CloudConn_10010] Received launcher response: [mkdir: cannot create directory â/data/cdipc/Informatica/<XYZ>_UI_Diskspace/productx/sys/apps/listener/202304.<Version>.1/../tmpâ: No space left on device.; Create the required amount of disk space and retry the update.

Retry update fails in the Download stage.: The update fails and you can't restart the update if the Listener service is suspended.; Run the dmlistenerlauncher script to stop the Listener. Then retry the update. The dmlistenerlauncher script is stored in the following location:
<Installation directory>/Informatica/platform/sys/apps/listener/<current version number>; To run the script, enter:
./dmlistenerlauncher.sh stop

The INFA_HOME variable must be set to run the script.

The CDI-PC Integration Service does not get enabled after an update successfully completes.: The
CDI-PC Integration Service
might take some time to start or might fail to start after an update completes.; Restart the service if the service does not get enabled.

Updating a domain fails, but the domain status remains in update in progress state: If a node update fails in the first stage of update, the domain status remains as
In progress
for indefinite time in the
Domain Details
page and
Explore
page. As a result, the plan-level
Retry
button and the
Update Progress
does not appear in the
Update Plan
page. However, the node-level
Retry
button remains enabled in the
Update Plan
page.; Click the node-level
Retry
button. Once re-triggered, DMS restores the latest plan state from the database to ensure an accurate operation state assessment.

When you initiate an update of a CDI-PC domain running as a Windows service, the domain starts in the process mode instead of the service mode.: Reason
: In JDK 9 and later releases, the
java.endorsed.dirs
system property is no longer available.
CDI-PC April 2025
has upgraded its JDK version to 11. The
java.endorsed.dirs
JVM property is part of the registry in a Windows CDI-PC domain configured to start as a service. This specific registry entry was created while creating the domain and was not modified during the update from the CDI-PC service page (DMS).

Solution
:; After the domain is updated successfully, use the following command to stop the Informatica CDI-PC service on the target Windows system where you want to start the domain as a Windows service.

INFA_HOME/tomcat/bin/infaservice.bat shutdown

Run the following command to remove the Informatica CDI-PC service:

INFA_HOME/tomcat/bin/infaservice.bat remove "InformaticaCDI-PC"

Run the following command to reinstall the Informatica CDI-PC service:

INFA_HOME/tomcat/bin/infaservice.bat install "InformaticaCDI-PC" "Informatica CDI-PC"