Cloud Data Integration : 2017 : April Skip navigation
2017

Are you facing issues after the Informatica Cloud Spring '17 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 Spring '17 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 Spring '17

 

ISSUES AND SOLUTIONS (APP2/3) April 22, 2017

Spring '17 Documentation

Informatica Cloud Spring 2017 - Helping customers accelerate their journey to the cloud

Issue: All tasks are failing post the upgrade and session log is not generated.

Internal error. The DTM process terminated unexpectedly

 

Solution:

 

Check if the session log directory is a non-default value. If so, revert it to the default value.

Steps:

Login to the ICS UI, Configure > Secure Agent.

Under System Configuration Details, choose Service = Data Integration Server and Type = DTM.

Check if the value of setting ‘$PMSessionLogDir’ is the default value '$PMRootDir\..\logs'.

If not, edit and revert back to the default value.

 

Wait for the Data Integration Service to restart automatically and then start the task.

Issue: 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: Please visit the discussion link: https://network.informatica.com/message/199683

Issue: “[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Database driver error” with Oracle/SQL Server/MySQL tasks after Informatica Cloud Spring 2017 upgrade on Windows Secure Agent

 

Solution:

This error may happen if the Registry entries that are sent as part of this upgrade were not updated during the upgrade.

Please follow the steps in this KB to resolve the issue: https://kb.informatica.com/solution/23/Pages/61/511902.aspx

Issue: The test connection for $SAP_CNX failed. Could not initialize class com.sap.conn.

jco.rt.JCo.JCoRuntimeFactory

The test connection for $SAP_CNX failed. Error getting the version of the native layer: Java.lang.UnsatisifiedLinkError: no sapjco3 in java.library.

 

Solution: You need to have the correct JCO libraries for the 64 bit Agent in the environment. If you have moved from 32 to 64 bit agent, then you need to download and setup the JCO files before connectivity to SAP can be established.

 

See the Solution in this KB 504336

Issue: Tasks with Hierarchy Builder transformation and REST V2 connector not processing data after Spring 2017 upgrade.

 

Solution:

This can happen if hierarchical data is sent to a string field in the REST V2 connector. The Request payload seen in the session log would show that there are “\” escape characters added to the request.

 

This issue can be resolved by adding a JVM Option to the Secure Agent configuration.

-      Navigate to Configure > Runtime Environments > Secure Agent.

-      Select “Data Integration Server” under Service and select Type as “DTM”

-      Edit the JVMOption1/2/3 etc.(whichever is available) and add the parameter '-DPromoteToArray=false'

-      Click on “Ok” to save the setting and wait for the Data Integration service to restart.

-      Run the task after the new Data Integration service is up.

Issue: Tasks that use Business Services will fail if the Business Services are edited, Existing unmodified tasks and newly created tasks will work fine.

 

Details:

The Spring 2017 release includes the following enhancement for REST V2 Connector:

 

A fault group to process fault response is enabled when you create a new business service or edit an existing business service.

 

After you upgrade to Spring 2017 release, if you edit a business service that is used in a REST V2 midstream transformation, the respective mapping will fail.


Solution:

 

To avoid this issue, do not edit the business service. If you edit the business service, recreate the midstream transformation and map all the required fields.

Issue: CA Certs Post Upgrade Task

 

 

Solution: ONLY if after past releases you have had to copy security Jars from the Jre2 backup directory back to the Jre directory, you will need to copy these files to a new location as the directory structure will change.

 

1.      Copy the local_policy.jar and the US_export_policy.jar files from the following directory:

<Secure Agent installation directory>\jre2\lib\security

2.      Paste the jar files to the following directory:

<Secure Agent installation directory>\jre\lib\security

3.      Restart the agent


connectors using security certificates - Amazon (Redshift, S3), Microsoft Dynamics CRM

Issue: 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 username 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: Copy Customized connector configuration files (if any)

If any of your licensed connector has configuration files, custom configured in your Informatica cloud secure agent, it is recommended that you copy these files

From

<Secure Agent installation directory>\main2\bin\rdtm\javalib\<plugin ID>\

 

To

<Secure Agent installation directory>\downloads\<latest connector zip package>\package\rdtm\javalib\<Plugin ID>

 

And

 

From:

<Secure Agent installation directory>\main2\tomcat\plugins\<plugin ID>\

 

To

<Secure Agent installation>\downloads\<latest connector zip package>\package\plugins\<Plugin ID>

 

connectorConfig File
AvaturecustomFields.ini
Birstbirstconfiguration.ini
Box APIconfig.properties
Coupacoupa.ini, read.xsd
Dropboxconfig.ini
Eloqua Bulk APIActivityConfig.json
Google APIconfig.properties
HadoopsetHadoopConnectorClassPath.sh
JDBCjdbc.ini
Jiraconfig.ini, jirafields.ini
JSON Targetconfig.ini
Marketoactivityattributes.csv
Open AirOpenAirCodes.properties
Quickbooks V2connectionparameters.ini
Workdayfields.ini
XML Sourceconfig.ini

Issue: Will Discovery IQ package available in Informatica Spring 2017 release.

 

During R27 upgrade, DiscoveryIQ package would be automatically removed and you may want to uninstall DiscoveryIQ agent  (especially windows agent env) from your environment.

Please refer to blog post for details of supported features of DiscoveryIQ and steps to uninstall DiscoveryIQ agent.

Issue:Tasks that use ODBC Connection, configured with DataDirect SequeLink driver, fail with error:

Specified driver could not be loaded due to system error  182:  (DataDirect SequeLink 6.0, C:\Program Files\DataDirect\slodbc60\dwslk22.dll).

 

Solution:

Copy the following files from the SequeLink/main2 folder

icuuc34.dll

libeay32.dll

ssleay32.dll

to

%AGENT_HOME%\downloads\package-ICSAgent_Rxx\package\ICS\main\bin\rdtm folder.

(Choose option ‘Copy and Replace’ when prompted)

 

This change will cause tasks that use Salesforce Connection with API version 32 or less to fail with:

Couldn't load the library [pmsfdcXXX.dll] for plug-in #310600.  Error msg: [Database driver event...Error occurred loading library [pmsfdcXXX.dll]. System error encountered is 182. Error text is The operating system cannot run %1.].

 

To resolve the problem with the Salesforce connection, change the Service URL in Salesforce to use API version 33 or higher.

 

ISSUES AND SOLUTIONS (APP) April 15, 2017

Spring '17 Documentation

Informatica Cloud Spring 2017 - Helping customers accelerate their journey to the cloud

Issue: 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: Please visit the discussion link: https://network.informatica.com/message/199683

Issue: The test connection for $SAP_CNX failed. Could not initialize class com.sap.conn.

jco.rt.JCo.JCoRuntimeFactory

The test connection for $SAP_CNX failed. Error getting the version of the native layer: Java.lang.UnsatisifiedLinkError: no sapjco3 in java.library.

 

Solution: You need to have the correct JCO libraries for the 64 bit Agent in the environment. If you have moved from 32 to 64 bit agent, then you need to download and setup the JCO files before connectivity to SAP can be established.

 

See the Solution in this KB 504336

Issue: CA Certs Post Upgrade Task

 

 

Solution: ONLY if after past releases you have had to copy security Jars from the Jre2 backup directory back to the Jre directory, you will need to copy these files to a new location as the directory structure will change.

 

1.      Copy the local_policy.jar and the US_export_policy.jar files from the following directory:

<Secure Agent installation directory>\jre2\lib\security

2.      Paste the jar files to the following directory:

<Secure Agent installation directory>\jre\lib\security

3.      Restart the agent


connectors using security certificates - Amazon (Redshift, S3), Microsoft Dynamics CRM

Issue: 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 username 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: Copy Customized connector configuration files (if any)

If any of your licensed connector has configuration files, custom configured in your Informatica cloud secure agent, it is recommended that you copy these files

From

<Secure Agent installation directory>\main2\bin\rdtm\javalib\<plugin ID>\

 

To

<Secure Agent installation directory>\downloads\<latest connector zip package>\package\rdtm\javalib\<Plugin ID>

 

And

 

From:

<Secure Agent installation directory>\main2\tomcat\plugins\<plugin ID>\

 

To

<Secure Agent installation>\downloads\<latest connector zip package>\package\plugins\<Plugin ID>

 

connectorConfig File
AvaturecustomFields.ini
Birstbirstconfiguration.ini
Box APIconfig.properties
Coupacoupa.ini, read.xsd
Dropboxconfig.ini
Eloqua Bulk APIActivityConfig.json
Google APIconfig.properties
HadoopsetHadoopConnectorClassPath.sh
JDBCjdbc.ini
Jiraconfig.ini, jirafields.ini
JSON Targetconfig.ini
Marketoactivityattributes.csv
Open AirOpenAirCodes.properties
Quickbooks V2connectionparameters.ini
Workdayfields.ini
XML Sourceconfig.ini

Issue: Will Discovery IQ package available in Informatica Spring 2017 release.

 

During R27 upgrade, DiscoveryIQ package would be automatically removed and you may want to uninstall DiscoveryIQ agent  (especially windows agent env) from your environment.

Please refer to blog post for details of supported features of DiscoveryIQ and steps to uninstall DiscoveryIQ agent.

Issue: Tasks that use Business Services will fail if the Business Services are edited, Existing unmodified tasks and newly created tasks will work fine.

 

Details:

The Spring 2017 release includes the following enhancement for REST V2 Connector:

 

A fault group to process fault response is enabled when you create a new business service or edit an existing business service.

 

After you upgrade to Spring 2017 release, if you edit a business service that is used in a REST V2 midstream transformation, the respective mapping will fail.


Solution:

 

To avoid this issue, do not edit the business service. If you edit the business service, recreate the midstream transformation and map all the required fields.

Issue:Tasks that use ODBC Connection, configured with DataDirect SequeLink driver, fail with error:

Specified driver could not be loaded due to system error  182:  (DataDirect SequeLink 6.0, C:\Program Files\DataDirect\slodbc60\dwslk22.dll).

 

Solution:

Copy the following files from the SequeLink/main2 folder

 

libeay32.dll

ssleay32.dll

to

%AGENT_HOME%\downloads\package-ICSAgent_Rxx\package\ICS\main\bin\rdtm folder.

(Choose option ‘Copy and Replace’ when prompted)

 

This change will cause tasks that use Salesforce Connection with API version 32 or less to fail with:

Couldn't load the library [pmsfdcXXX.dll] for plug-in #310600.  Error msg: [Database driver event...Error occurred loading library [pmsfdcXXX.dll]. System error encountered is 182. Error text is The operating system cannot run %1.].

 

To resolve the problem with the Salesforce connection, change the Service URL in Salesforce to use API version 33 or higher.