Informatica Corporation Informatica Cloud Spring 2015 Release Notes April Contents

Transcription

1 Informatica Corporation Informatica Cloud Spring 2015 Release Notes April 2015 Copyright (c) Informatica Corporation. All rights reserved. Contents Before You Upgrade... 2 Back Up Informatica B2B Data Transformation Files Prepare the Secure Agent Fixed Limitations... 3 Informatica Cloud Connector Fixed Limitations... 3 Known Limitations... 3 Informatica Cloud Data Masking Known Limitations... 7 Informatica Cloud Connector Known Limitations... 8 Informatica Cloud Connector Toolkit Known Limitations Third Party Limitations Informatica Resources Informatica Documentation Informatica Web Site Informatica Cloud Web Site Informatica Cloud Communities Informatica Cloud Marketplace Informatica Cloud Connector Documentation Informatica Knowledge Base Informatica Cloud Trust Site Informatica Global Customer Support This document contains important information about new features and enhancements, known limitations, and third-party limitations for Informatica Cloud. IC-RLN

2 Before You Upgrade Back Up Informatica B2B Data Transformation Files If you use Informatica B2B Data Transformation, you must back up files in the Secure Agent directory and restore the files after upgrade. The DataTransformation package has been renamed to the DT_Secure Agent package. During upgrade, the Secure Agent installation directory will be modified to support this change. Before you upgrade, copy the files in the DataTransformation directory and restore the files after upgrade to the corresponding new location. The following table lists the files that you should back up and then restore: File Type Path Before Upgrade Path After Upgrade Data Transformation Services files TGP files DLL and JAR files Configuration file <SecureAgent_InstallDir>/ DataTransformation/ServiceDB <SecureAgent_InstallDir>/ DataTransformation/autoInclude/ user <SecureAgent_InstallDir>/ DataTransformation/externLibs/user <SecureAgent_InstallDir>/ DataTransformation/CMConfig.xml <SecureAgent_InstallDir>/rdtmDir/DT / ServiceDB <SecureAgent_InstallDir>/ DT_secureAgent/autoInclude/user <SecureAgent_InstallDir> / DT_secureAgent/externLibs/user <SecureAgent_InstallDir> / DT_secureAgent/CMConfig.xml Prepare the Secure Agent Perform the following steps to ensure that the Secure Agent is ready for upgrade: 1. Ensure that the Secure Agent server has sufficient disk space available for upgrade. To calculate the free space required for upgrade, use the following formula: Minimum required free space = 2 * (size of current <Secure Agent installation directory>) + 1 GB 2. Close all open log files on the Secure Agent to avoid file lock issues. 3. Back up third-party libraries, security certificates, and configuration files that you have added to <Secure Agent installation directory>/main. Keep a copy of these files in <Secure Agent installation directory>/main/bin/rdtm-extra. For example, you might want to back up the following libraries and configuration files: Microsoft Dynamics CRM krb5.conf and login.conf files SAP JCo libraries SAP RFC SDK libraries SAPRFC.ini file 2 IC-RLN

3 4. Disable tasks scheduled during the maintenance window. To configure a blackout period for the organization, click Configure > Schedules > Blackout Period. If you use an external method to schedule tasks, ensure that no tasks are scheduled to run during the maintenance window. Fixed Limitations The following table describes fixed limitations: CR INFA INFA In integration templates, Union transformation objects require input groups to use the same field names and datatypes. In mappings, Source transformations that include multiple SAP Table objects display all join types. Use the inner join or left join type. Other join types cause the task to fail. Informatica Cloud Connector Fixed Limitations The following table describes fixed limitations for Informatica Cloud Connectors: CR CON-495 When you run a data synchronization task to read data from SAP, the Informatica Cloud Connector rounds decimal values for fields of the CURR data type. Known Limitations The following table describes general Informatica Cloud known limitations: CR ICS-1491 ICS-1497 ICS-1542 For Salesforce web services, if a mapping uses more than one Web Services transformation, you cannot pass the new endpoint URL returned from the first Web Service transformation to any downstream Web Service transformations. Workaround: Create another WSConsumer connection using the URL returned from the first Web Service transformation and define a business service that uses the connection. Use the new business service for the downstream Web Services transformation. For NetSuite web services, when you define a business service and configure a web service operation, some operations that have had a choice element or derived type selected will not appear correctly when the Configure Operation window is reopened. The configured nodes might appear more than once, appearing with the option to select the choice element or derived type, and appearing with the option selected. Web services requests and responses that have unicode characters might return unexpected results. IC-RLN

4 CR ICS-395 ICS-385 DMT-56 DMT-55 DMT-52 DMT-42 DMT-26 INFA INFA INFA INFA INFA INFA When you try to create an advanced relationship between source objects that have been joined using a custom relationship, the join condition is cleared. Creating an advanced relationship using a custom relationship is not supported. In the Mapping Configuration application, the Advanced Relationship dialog box is editable in View mode. You cannot perform an automatch of incoming fields from the Data Masking transformation and target fields in the Field Mapping section of the target transformation. Workaround: You must manually map the incoming fields and target fields in the Field Mapping section of the target transformation. A mapping that includes the Substitution masking technique fails when the source precision is less than the dictionary value precision. Workaround: When you use the Substitution masking technique, ensure that the source precision is more than the dictionary value precision. An incorrect error message, "Invalid mapping import and no import log generated" appears when you run a mapping that uses the Data Masking transformation without the appropriate cmask package. Workaround: Apply the cmask package before you run a mapping that uses the Data Masking transformation. A mapping that includes the Credit Card masking technique returns unexpected results when you disable the property Keep Issuer. Workaround: Enable the property Keep Issuer when you use the Credit Card masking technique in a mapping. A mapping that includes the SIN masking technique fails when you disable the property Start Digit. Workaround: Enable the property Start Digit and enter a start digit value when you use the SIN masking technique. Tasks that include more than two Salesforce source objects and a SOQL query or source filter can fail when the query does not include the primary source object in the expression. Workaround: For a SOQL query, include the relationship path to the primary source object as follows: <relationship_path>.field_name='value'. For example, the following expression filters Salesforce data in the contact and account objects by a user named Lee: Contact.Account.CreatedBy.Name='Lee'. Metadata override for Salesforce targets does not work at run time. Tasks that use a $LastRunDate to filter SQL Server 2012 source data fail. Mapping configuration tasks that pass binary data through a Normalizer transformation fail with data type conversion errors. The Normalizer transformation does not support binary data types. The Mapping Configuration application rejects flat file rows that include newline characters within a field when all source fields are not included in the data flow. Workaround: Include all source fields in the data flow. Even if you do not need all fields written to the target, use a field rule to include all fields to the first transformation after the source. If necessary, you can add an Expression or Filter transformation to handle this issue. 4 IC-RLN

5 CR INFA INFA INFA INFA INFA INFA INFA INFA INFA INFA INFA INFA INFA INFA INFA Do not use data filters or perform lookups with Oracle or SQL Server connections that use the following code pages: - Shift-JIS - ISO Latin 9 (Western European) - ISO Eastern European - ISO Cyrillic - ISO Latin 5 (Turkish) Do not use the following code pages for any connection type except flat file, Oracle, and SQL Server. The following code pages display for other connection types, but are not valid code page options: - Shift-JIS - ISO Latin 9 (Western European) - ISO Eastern European - ISO Cyrillic - ISO Latin 5 (Turkish) You can delete a connection that is used in a mapping. You should not be able to delete connections that are used in mappings or tasks. Mapping binary fields in data synchronization tasks can cause the task to fail. Do not map binary fields in data synchronization tasks. When using a parameterized user-defined join in custom integration tasks, use fully qualified names for source fields. When you replicate a source with a name that includes a dollar sign ($), the target name replaces the dollar sign with an underscore (_). In data synchronization tasks with database targets, the Update Target property is cleared if you click the Refresh Fields option on the Field Mappings page of the Data Synchronization wizard. Salesforce External ID fields with the Auto Number data type cannot be used as upsert fields. They will be available in the Upsert Field Name option. The general status message for migration can indicate that the migration was successful even when some objects were not migrated. Workaround: Review the migration details in the Migration Results table. When migrating objects, the initial review of objects is case sensitive, so if an object of the same exists in the target organization with a different case, it seems as if the object will be migrated. However, the object is not migrated, as noted in the Migration Results table. When an object is not migrated because an object of the same type and name exists in the target organization, child objects such as connections or custom sources might still be migrated. When you migrating an object, all child objects are migrated to the target organization. However, in the target organization, you can only see and access the objects with valid licenses. In PowerCenter tasks, connection errors occur when you use Microsoft Dynamics CRM connections with Active Directory authentication and an HTTP service URL. Workaround: Do not include Microsoft Dynamics CRM connection information in the PowerCenter mapping. Instead, select the Microsoft Dynamics CRM connection when you configure the PowerCenter task. IC-RLN

6 CR INFA INFA INFA INFA INFA INFA INFA INFA INFA INFA INFA INFA INFA The Street With Number advanced option is ignored in Contact Validation tasks. The building number is always included with the street name at this time. Contact Validation tasks that validate postal addresses sometimes fail due to memory allocation, internal server, or transformation errors. Workarounds: If the task fails with the following error, use the Buffer Block Size advanced option to adjust the buffer block size: FATAL ERROR : Failed to allocate memory. Out of virtual memory. For other errors, try running the task again. If the problem persists, contact Informatica Global Customer Support. For data synchronization tasks running in real time after receiving a Salesforce outbound message, Secure Agent or network connection problems can result in data loss or unexpected job behavior. Previewing data for an Microsoft Dynamics CRM object that does not contain any data displays the following error instead of indicating that the object does not contain data: [X] An error occurred when fetching data for preview. Data synchronization tasks configured to run in real time upon arrival of outbound messages run even when Run permission is revoked. Microsoft Dynamics CRM connections should not display the Active Directory authentication type option when configured in data synchronization tasks. The Active Directory authentication type is not supported in data synchronization tasks. For data synchronization tasks with Microsoft Dynamics CRM targets, error rows are not written to the error rows file. You cannot use Microsoft Dynamics connections with IFD authentication in data synchronization tasks. Microsoft Dynamics CRM connections with IFD authentication fail during testing. PowerCenter tasks that write to Salesforce targets using the Salesforce Bulk API fail when run by a Secure Agent that uses FreeProxy or ISA Proxy. Workaround: If possible, use a different Secure Agent to run the task, or configure the Secure Agent to use a different proxy server. 6 IC-RLN

7 Informatica Cloud Data Masking Known Limitations The following table describes known limitations for the Data Masking application: CR CTDM-69 INFA INFA INFA INFA INFA INFA INFA A data masking task fails when you use a cloud runtime. Workaround: Use a runtime environment that contains at least one Secure Agent to perform data masking tasks. When you configure a Substitution State masking rule, the Lookup Input Port field that appears in the properties is not valid. Workaround: Ignore the Lookup Input Port field and continue the task. A data masking task with multiple source objects fails because the following Salesforce objects are not supported: UserLicense, Profile, Idea, Community, Group, and DandBCompany. Workaround: Do not select the UserLicense, Profile, Idea, Community, Group, or DandBCompany objects as multiple source objects in a data masking task. When you validate a custom masking expression, the application deletes the expression and closes the dialog box. The data masking task fails because the expression field is blank. Workaround: Do not validate custom masking expressions. When you run a data masking task, the application does not write the existing source external ID into the Salesforce target fields. Workaround: Disable the external ID constraint in the Salesforce target fields, and enable the external ID constraint after the task is complete. When you apply filters on the Account, Contact, or Lead objects in a data masking task, the Campaign Members object might not appear in the target fields if these Salesforce objects are not related to each other. The Lead object can be either a potential lead or a converted lead and so, the relationships between Contact, Account, and Lead objects might vary. Workaround: In a data masking task, apply filters for the Campaign object so that all the related objects appear in the target fields. When you run a data masking task, the application writes logs into a single error file instead of a separate file for each Salesforce object. Workaround: Download the error rows file and view the error logs for all the Salesforce objects in a single file. The format of the error file name is s_dmask_<jobid>_<number of time the file is appended>_error.csv. When you run data masking tasks, the process takes a long time to initialize and the application automatically switches from the Activity Monitor page to the Activity Log page without any messages. Workaround: Do not refresh the page. Wait till the Activity Log page appears and then go the Activity Monitor page to view the status of the data masking task. IC-RLN

8 Informatica Cloud Connector Known Limitations The following table describes known limitations for Informatica Cloud Connectors: ICC CR CON-562 CON-558 CON-557 CON-555 CON-552 CON-425 CON-454 CON-530 IRM-775 IRM-770 IRM-762 IRM-761 CON-162 For a Salesforce connection, if you create a saved query using the "WITH" key word, an error message appears that says the query is not valid. Workaround: Create a saved query without the "WITH" key word. For a Salesforce connection, a saved query does not return metadata for a polymorphic query in the SOQL query. For a Salesforce connection, a saved query will not return metadata for an aggregation query in the SOQL query. For a Salesforce connection, if you create a saved query that contains a complex query, an error message appears that says the query is not valid. Workaround: Use a simple SOQL query when you create a saved query. For a Salesforce connection, if you create a saved query that contains a relationship SOQL query, data corruption occurs when you run a data synchronization task that contains the saved query. When you run a task that uses a Salesforce source with formula datatype for number and currency field fails with a data overflow/conversion error. If you use Amazon Redshift source objects with more than two levels of relationships in a data synchronization task, the Refresh Fields option does not display the metadata for those objects. You can save and run the task, but the task fails at run time. Workaround: Create a new data synchronization task that contain objects with two or less than two levels of relationships, or use the mapping configuration task. PowerCenter error messages and NetSuite error messages are appended in the same error file. If any rows in the source file are rejected at the source qualifier level because of format issues (for example, date format is not correct) and rows in the same file are rejected from NetSuite, then both of the error messages are appended in the same file. When you enter incorrect connection properties, such as Tableau Server URL, user name, and password, the test connection does not fail. If the TDE directory on the Secure Agent machine does not contain a TDE file, Tableau Connector displays an error when you create a data synchronization task. The option to create a target in the data synchronization task also does not display. Workaround: Before you create a data synchronization task, ensure that at least one TDE file is present in the TDE file directory. When you select a TDE file, you cannot preview the data for the Tableau objects. If the specified site ID and project name in the advanced target properties are incorrect, the data synchronization task still creates a TDE file in the TDE directory but does not publish it. The Secure Agent appends the data to the TDE file even if you configure the Tableau target to not append data to the TDE file. CON-182 Tasks that read from SAP tables and include decimal fields with a maximum length of 29 places and 3 decimal places might fail. 8 IC-RLN

9 ICC CR INFA INFA INFA INFA INFA INFA INFA INFA INFA INFA INFA INFA INFA INFA A task that uses an SAP table connection to write to a table fails with the following error when the primary key field name includes a tilde(~) or a single quote ('): [ERROR] Exception [SYSTEM_FAILURE] has been raised from the RFC call. A task with that uses an Informatica Cloud Connector fails with a java.lang.classnotfoundexception when the Linux Secure Agent was installed by the same user who installed PowerCenter on the machine, and the user profile CLASSPATH is configured to include the javalib or jre for the PowerCenter installation. Workaround: Use a different user profile to install the Secure Agent. Or, before you start the Secure Agent, ensure the CLASSPATH does not include references to the PowerCenter javalib or jre. When you run a task that includes an Informatica Cloud Connector with a Secure Agent on Windows 2003 or Windows XP (32-bit), the task can fail with the following error: Failed to load the JVM library: <..\..\..\jre\bin\server\jvm.dll Workaround: Install the Visual Studio 2010 redistributable on the Secure Agent machine. You can download the redistributable from the following location: For tasks that read from SAP tables, the session log includes the first 1000 characters of the ABAP query. Queries that include a large number of SAP fields might not be complete. In a data synchronization task, editing a connection for Informatica Cloud Connector prevents the task wizard from displaying the Display Technical Names Instead of Labels option. Workaround: Edit the connection separately, from the Connections list page. When you stop a task with an Amazon Redshift target through the activity monitor, the task aborts rather than stopping. Details about the task might not be written to the session log. Tasks that include Amazon Redshift or SAP table connections can fail due to short network disruptions. Advanced data filters for SAP tables do not recognize the pound sign (#) escape character. You cannot download error rows files from the activity log for data synchronization tasks with Amazon Redshift targets. Workaround: You can access error rows files in the following directory on the Secure Agent machine: <Secure Agent Installation Directory>\main\rdtmDir\error. Conversion from simple data filters to advanced data filters are not supported. Data filters for SAP table character data require a filter value of the same length as the character field. Workaround: Add leading zeros when you enter the filter value. For example, to filter a ten digit field by , use in the data filter. Tasks fail with errors when a lookup returns more than 20 rows. Workaround: When possible, configure the lookup to return fewer rows. Object search on labels for SAP objects is case-sensitive. IC-RLN

10 ICC CR INFA INFA INFA INFA INFA INFA INFA The data synchronization task wizard does not display lookup fields for Informatica Cloud Connector objects that are configured to be unfilterable. Do not use parameters defined in a parameter file in data filters for NetSuite sources. Using parameters in NetSuite data filters can result in no data being processed for the task. When you include custom NetSuite fields Transaction Column Fields (TCF) and Transaction Item Options (TIF) in a task, they are added to the field list of the child record rather than the parent record. In an integration template, do not use data type link rules to connect NetSuite sources to source qualifier objects. Workaround: Use the data type link rule between the source qualifier object and the rest of the data flow. Filters for NetSuite Multi-Select and Standard Record custom fields are not supported. A data synchronization task does not fail if you remove a mapped source field from a NetSuite source. For data synchronization tasks that use SAP targets, do not map FLDCLNT fields with the CLNT data type. SAP might reject the rows without logging the rows as rejected in the session log. (SAP reference number: ) Workaround: Map the CLNT field and make sure that data in this field matches the client specified in SAP Table Connector connection. Informatica Cloud Connector Toolkit Known Limitations The following table describes known limitations for the Informatica Cloud Connector toolkit: Toolkit CR INFA INFA INFA You cannot configure data filter row limits for Informatica Cloud Connectors. When you use an Informatica Cloud Connector for a lookup in a data synchronization task and you configure the lookup to produce an error when more than one match is found, the lookup returns null values regardless of the actual lookup data. Third Party Limitations The following table describes third-party known limitations: Third Party CR ICS-817 ICS-432 Due to a Postgres JDBC driver limitation, data synchronization tasks will fail when trying to write to a BIT type field. Due to a NetSuite limitation, you cannot see the isbookspecific column for multi-book account objects in connections using WSDL version 2014_2. 10 IC-RLN

11 Third Party CR CON-457 CON-180 INFA ICS-304 INFA CTDM-67 INFA When a data synchronization task has a JDBC target with a field of type DECIMAL with a precision of 32, and values are specified for the Success File Directory or Error File Directory, the task fails with a SQLSyntaxErrorException error. For a JDBC connection, JDBC internally invokes a Derby service when values are specified for the Success File Directory or Error File Directory. The processed rows that are to be written in the success and error files are temporarily stored in an in-memory table in Derby. Derby accepts precisions up to 31 digits. A decimal of precision 0-31 is allowed if the commit interval is greater than 1 and success and error file directories are specified. If you create a data synchronization task with a JDBC target object and a specified precision value (for example, 6,3) for decimals, if the target contains a decimal field with a precision that exceeds the specified precision value, the task fails. This is due to a Derby limitation. In tasks and the Mapping Designer, objects that cannot be queried by version 31 of the Salesforce API do not show up in the list of available objects for sources or targets. Due to a Salesforce limitation, when you use version 32.0 or 33.0 of the Salesforce API, the data masking task fails because the application cannot find the external IDs or the custom fields in the target. Workaround: Use API 31.0 or lower supported version of the API for inplace masking. Use API 28.0 or lower supported version of the API for data subset and data masking when the target is different from the source. Data replication and data synchronization tasks that use the Salesforce Bulk API and version 31 of the Salesforce API to replicate the following Salesforce objects fail: AcceptedEventRelation, CaseStatus, ContractStatus, DeclinedEventRelation, LeadStatus, OpportunityStage, PartnerRole, RecentlyViewed, SolutionStatus, TaskPriority, TaskStatus UndecidedEventRelation, UserProfile, and Attachment with binary fields. The tasks fail with the following error: Entity '<ObjectName>'is not supported by the Bulk API. For more information on the objects that cannot be queried with the Salesforce Bulk API, contact Salesforce. INFA Due to a Salesforce limitation, the data masking tasks fail when the SOQL exceeds 20,000 characters. Workaround: Contact Salesforce to increase the SOQL character limit for the account. INFA INFA INFA Due to a Salesforce limitation, the data masking tasks with the Upsert operation fail when the external ID or custom field for lookup does not exist or cannot be created in the targets. Due to a NetSuite limitation, you need a separate license for each connection to the same NetSuite account that a task makes. For example, to use the same NetSuite account as source, lookup, and target in a task, you need three NetSuite licenses. Due to an Oracle CRM On Demand limitation, you cannot use custom objects 4-15 with data synchronization tasks. IC-RLN

12 Third Party CR INFA Due to a JDBC driver limitation, the driver returns the Microsoft SQL Server 2008 Nvarchar(Max) field as Ntext and returns Varchar(Max) field as Text. As a result, Nvarchar(Max) or Varchar(Max) fields do not display in data filters. Workarounds: Enter the fields manually in an advanced data filter. Or, on the Field Mappings page, use the Edit Types option to edit the datatypes. Update incorrect Ntext fields to Nvarchar and incorrect Text fields to Varchar. INFA INFA INFA INFA Due to a NetSuite limitation, NetSuite Item Number data is not supported. Due to a NetSuite limitation, field metadata information such as primary key or not-null does not display in Informatica Cloud. NetSuite returns both the date and time using the following format for all date or time datatypes, regardless of whether you want only the date or time part: yyyy-mm-ddthh:mm:ss <AM PM>. For the TimeOfDay data type, the date part defaults to Custom integration tasks with multiple NetSuite sources fail if NetSuite does not allow multiple connections. Workaround: Use a NetSuite account that allows concurrent connections. Informatica Resources Informatica Documentation The Informatica Documentation team makes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through at infa_documentation@informatica.com. We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments. The Documentation team updates documentation as needed. To get the latest documentation for your product, navigate to Product Documentation from Informatica Web Site You can access the Informatica corporate web site at The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services. Informatica Cloud Web Site You can access the Informatica Cloud web site at This site contains information about Informatica Cloud editions and applications. 12 IC-RLN

13 Informatica Cloud Communities Use the Informatica Cloud Community to discuss and resolve technical issues in Informatica Cloud. You can also find technical tips, documentation updates, and answers to frequently asked questions. Access the Informatica Cloud Community at: Developers can learn more and share tips at the Cloud Developer community: Informatica Cloud Marketplace Visit the Informatica Marketplace to try and buy Informatica Cloud Connectors, Informatica Cloud integration templates, and Data Quality mapplets: Informatica Cloud Connector Documentation You can access documentation for Informatica Cloud Connectors at the Informatica Cloud Community: You can also download individual connector guides: Informatica Knowledge Base As an Informatica customer, you can access the Informatica Knowledge Base at Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team through at Informatica Cloud Trust Site You can access the Informatica Cloud trust site at This site provides real time information about Informatica Cloud system availability, current and historical data about system performance, and details about Informatica Cloud security policies. Informatica Global Customer Support You can contact a Customer Support Center by telephone or online. For online support, click Submit Support Request in the Informatica Cloud application. You can also use Online Support to log a case. Online Support requires a login. You can request a login at IC-RLN

14 The telephone numbers for Informatica Global Customer Support are available from the Informatica web site at 14 IC-RLN