Cloud Data Integration : 2016 : November Skip navigation
2016

Are you facing issues after the Informatica Cloud Fall '16 upgrade? We are here to help. We have identified some of the common issues encountered by users and pulled together a list of solutions to help you address them. Read on to know more.

 

Note: If you have any concerns please open a case with Informatica Support by clicking on Contact Support option within Informatica Cloud.

 

SUMMARY

 

At the bottom of this post, we have a running list of known issues in Fall '16 upgrade and their solutions. We will continue to update this list so check back later for more updates. If you already have a network.informatica.com login, we recommend following  this post so that you can automatically receive updates for any new issues.

 

You can also follow us on Twitter @INFAsupport for all the latest updates on Informatica Cloud Fall '16

 

ISSUES AND SOLUTIONS (APP2 and APP3) Nov 19, 2016 -

 

Issue: Upgrade failure. [Cannot download upgrade file:https://icsdownloadsecure.informatica.com/ICS/r23/mirror1/download/upgrade-24.1.2.1.0.0.0/fullupgrade/win32/upgrade.zip: [There is not enough space on the disk]]

 

Solution: The minimum free space required for the upgrade is equal to 2X size of the current <SecureAgent>\Main directory plus 1 GB. Please ensure that enough disk space is available.

You may remove old upgrade backups such as Main2, Main3, Main4 etc. You can check the cache directory and remove any files there. You can remove the tomcat log or session logs that has gotten large or accumulated over time.

ISSUE 2: The upgrade was not successful. [================================  02/06/2016  1:36:27.41  copy upgrades\fullupgrade\FileLockDetect.exe FileLockDetect.exe        1 file(s) copied. Waiting for file handles to clean up ERROR: Input redirection is not supported, exiting the process immediately. JAVA_HOME: .\jre agentCoreMajorUpgrMarker exists  Do major upgrade.  Interim agent exists before upgrade, so remove it first.  main2\tomcat\work\Tomcat - The directory is not empty. main2 cannot be removed.  ]

 

SOLUTION 2: Please visit the discussion link: https://network.informatica.com/message/199683

Problem: Jobs on Windows using ODBC fail with the following error: Data source name not found and no default driver specified Database driver error.


Solution: The agent should run as an Administrator

During the upgrade the agent will update the registry to add need ODBC entries. If your agent does not have access to update the registry you may face the following error:

WRT_8001 Error connecting to database... WRT_8001 [Session s_dss_000GSG0I0000000000xx Username YOURUSER Error -1 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Database driver error... Function Name : Connect Database driver error... Function Name : Connect Database Error: Failed to connect to database using user [xxx] and connection string [odbc://dbtype=<oracle or SQLServer>;host=,host.;port=<port>;database=<database>].]

This occurs in Windows for Oracle and SQL Server type connections.

 

Cause: Since there is a new ODBC driver for oracle and SQL server, as a part of upgrade, the registry will be updated to add new entries for these 2 drivers, if the user running the agent does not have permission to modify the registry entries, then these entries will not be added to the registry, hence when the task tried to load the drivers, it looks for registry entry and fails.

 

Solution: If you are not running your agent as an Administrator we recommend you run as an Administrator before the upgrade. KB149494 has the steps to run as an Administrator.

 

What if I face the above error after the upgrade?

 

1) Trigger the upgrade by modifying the infaagentversion file (in a text editor) in {agent}/main and change 26.* - to 25.*

2) Restart the agent as admin (steps same as in KB149494)

 

Issue: Upgrade failure. [Cannot download upgrade file:https://icoss1.informaticacloud.com/saas/download/upgrade-22.3.2.1.0.0.0/fullupgrade/linux32/upgrade.zip: [Download failed due to HTTP 403 response.]]

 

Solution: Please visit the document  link: Secure Agent IP Address KB:112401

Issue: Upgrade failure. [Cannot download upgrade file:https://icsdownloadsecure.informatica.com/ICS/r23/mirror2/download/upgrade-22.3.2.1.0.0.0/fullupgrade/win32/upgrade.zip: [Download failed due to HTTP 502 response.]]

 

Solution: This is because our mirror sites have not been whitelisted in your network. Please contact Informatica Cloud Support with your orgid, so that we can push the download via a secure site.

Issue: ODBC DSN not found on Linux after the upgrade will encounter the following error:

The connection test failed because of the following error: [unixODBC][Driver Manager]Data source name not found, and no default driver specified (0)


Solution:


This is because the odbc.ini file was in the main directory and it was backed up to main2 folder during the upgrade.

To fix the issue copy over the odbc.ini file from infaagent/main2 to infaagent/main.

Also you should store the odbc.ini outside of main, going forward, or keep a copy in rdtm-extra directory, so it is copied back automatically after future upgrades.

Issue: Issues while reading data using Microsoft Excel connector:

You might notice issues when trying to use Microsoft excel connector on ICS. The test connection would be successful however when trying to select the connection as a source in DSS\mapping task we receive error occurred while fetching objects.


Solution:

We have a solution for this issue and customers can reach out to Informatica Support to get the patch.

Issue: Data source name not found and no default driver specified Database driver error


Solution:

The agent should run as an Administrator

During the upgrade the agent will update the registry to add need ODBC entries. If your agent does not have access to update the registry you may face the following error:

WRT_8001 Error connecting to database... WRT_8001 [Session s_dss_000GSG0I0000000000xx Username YOURUSER Error -1 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Database driver error... Function Name : Connect Database driver error... Function Name : Connect Database Error: Failed to connect to database using user [xxx] and connection string [odbc://dbtype=<oracle or SQLServer>;host=,host.;port=<port>;database=<database>].]

This occurs in Windows for Oracle and SQL Server type connections.

 

Cause: Since there is a new ODBC driver for oracle and SQL server, as a part of upgrade, the registry will be updated to add new entries for these 2 drivers, if the user running the agent does not have permission to modify the registry entries, then these entries will not be added to the registry, hence when the task tried to load the drivers, it looks for registry entry and fails.

 

Solution: If you are not running your agent as an Administrator we recommend you run as an Administrator before the upgrade. KB149494 has the steps to run as an Administrator.

 

What if I face the above error after the upgrade?

 

  1. 1) Trigger the upgrade by modifying the infaagentversion file (in a text editor) in {agent}/main and change 26.* - to 25.*
  2. 2) Restart the agent as admin (steps same as in KB149494)

 

ISSUES AND SOLUTIONS (APP only) Nov 12, 2016 -

 

Issue: Upgrade failure. [Cannot download upgrade file:https://icsdownloadsecure.informatica.com/ICS/r23/mirror1/download/upgrade-24.1.2.1.0.0.0/fullupgrade/win32/upgrade.zip: [There is not enough space on the disk]]

 

Solution: The minimum free space required for the upgrade is equal to 2X size of the current <SecureAgent>\Main directory plus 1 GB. Please ensure that enough disk space is available.

You may remove old upgrade backups such as Main2, Main3, Main4 etc. You can check the cache directory and remove any files there. You can remove the tomcat log or session logs that has gotten large or accumulated over time.

 

Issue: Upgrade failure. [Cannot download upgrade file:https://icoss1.informaticacloud.com/saas/download/upgrade-22.3.2.1.0.0.0/fullupgrade/linux32/upgrade.zip: [Download failed due to HTTP 403 response.]]

 

Solution: Please visit the document  link: Secure Agent IP Address KB:112401

 

Issue: Upgrade failure. [Cannot download upgrade file:https://icsdownloadsecure.informatica.com/ICS/r23/mirror2/download/upgrade-22.3.2.1.0.0.0/fullupgrade/win32/upgrade.zip: [Download failed due to HTTP 502 response.]]

 

Solution: This is because our mirror sites have not been whitelisted in your network. Please contact Informatica Cloud Support with your orgid, so that we can push the download via a secure site.


New features and Documentation - Fall '16

Informatica Cloud Fall 2016

ISSUE: Log File Name Change Starting from next release, Fall ‘16, we are providing an option to create the tomcat and infaagent logs with rolling log appenders after a certain size for e.g.: 100MB. This will help to ensure that the filesize is limited, and help to resolve disk space issues. The infaagent.log will still be created and will contain output from the windows service (infaagent.exe) and scripts (agent_start, runAgentCore, etc.). There is a separate file called agentcore.log from the agentcore process, which will now contain the current content of the infaagent.log. Log rolling configuration is applied to the tomcat.log as well.


Solution:

How will this impact me?If you are parsing the infaagent.log file currently, you will need to start parsing agentcore.log, after the upgrade to Fall ’16.  If you simply read the logs when there is an issue, then there is no impact. The only impact is if you have any process that automatically reads/parses the log files. For more details on default log size and configuring/tuning to your specific requirements, please refer to the following KB.

Issue: ODBC DSN not found on Linux after the upgrade will encounter the following error:

The connection test failed because of the following error: [unixODBC][Driver Manager]Data source name not found, and no default driver specified (0)


Solution:


This is because the odbc.ini file was in the main directory and it was backed up to main2 folder during the upgrade.

To fix the issue copy over the odbc.ini file from infaagent/main2 to infaagent/main.

Also you should store the odbc.ini outside of main, going forward, or keep a copy in rdtm-extra directory, so it is copied back automatically after future upgrades.

Issue: Customers on Linux with PowerCenter and Cloud using the same user to start both services will encounter the following error: Internal error. The DTM process terminated unexpectedly. Contact Informatica Global Customer Support.

 

Solution: Put a line on the top of the agent_start.sh file, located under <agent install Dir>  ‘unset INFA_HOME’  and restart your agnet.

Issue: Task fails at runtime with below Error message on windows for Oracle or SQL Server type connections: WRT_8001 Error connecting to database... WRT_8001 [Session s_dss_000XXX0I00000xxxxxxx Username User_Name DB Error -1 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Database driver error... Function Name : Connect Database driver error... Function Name : Connect Database Error: Failed to connect to database using user [User_Name] and connection string [odbc://dbtype=<oracle or SQLServer>;host=,host.;port=<port>;database=<database>].]

 

Solution:

Please reach out to Informatica Support with the infaagentversion file and we shall help you resolve the issue.