Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Before You Upgrade the Domain on Linux
  4. Before You Upgrade the Domain on UNIX
  5. Before You Upgrade the Domain on Windows
  6. Prepare for the Upgrade
  7. Upgrade the Domain
  8. Upgrade the Domain with Changes to Node Configuration
  9. Before You Upgrade the Application Services
  10. Application Service Upgrade
  11. Informatica Client Upgrade
  12. After You Upgrade
  13. Appendix A: Upgrade Checklist

Upgrading from Versions 10.4.0 and 10.4.1 (10.5)

Upgrading from Versions 10.4.0 and 10.4.1 (10.5)

Troubleshooting the Domain Upgrade

Troubleshooting the Domain Upgrade

Consider the following troubleshooting tips when you face any issue during or after the domain upgrade:
The domain upgrade fails.
If the upgrade does not complete successfully, review log files to determine the cause of the failure. The upgrade log files are in the root of the directory where the new version of Informatica is installed. Review the following log file: Informatica_<Version>_Services_Upgrade.log.
If the upgrade continues to fail, restore the domain configuration repository database from the backup and run the installer again.
404 error message appears when you access the Administrator tool.
If the Administrator tool is configured for secure communication, you might receive a
404 Not Found
message when you access the Administrator tool. This issue occurs when the machine that runs the gateway node cannot access the keystore file used for the HTTPS connection to the Administrator tool. Copy the file to an accessible location, and then shut down the domain. Run the infasetup UpdateGatewayNode command to update the gateway node with the location of the keystore file. You must run the command on each gateway node in the domain.
The domain crashes during or after the upgrade.
If the domain crashes during or after the upgrade, restore the siteKey file from the domain backup or generate the encryption key using the same keyword and domain name that you specified while generating the sitekey in the previous version of the domain.
In a multi-node configuration, errors might occur when you use a different site key than the master node.
If you have a multi-node configuration and when you use a different site key, you might run into the following errors:
021-03-03 12:51:44,795 FATAL [Domain Monitor] [DOM_10061] Cannot register node [newISPNode1] with the domain because the master gateway node is not running or is not connected to the domain. Verify that all gateway nodes are running on the domain. com.informatica.isp.corecommon.exceptions.ISPException: [CCM_10342] The following exception occurred: [[FrameworkUtils_0018] The encryption key for the node is different from the encryption for the domain. All the nodes in a domain must use the same encryption key. To change the encryption key for the domain, run the infasetup migrateEncryptionKey command on all nodes in the domain.].)
To resolve this issue, ensure that you use the same site key as in the master node.

0 COMMENTS

We’d like to hear from you!