This document contains information on fixed and known limitations for Test Data Management.

Transcription

1 Informatica Corporation Test Data Management Version Release Notes August 2014 Copyright (c) Informatica Corporation. All rights reserved. Contents Informatica Version Installation and Upgrade Fixed Limitations Known Limitations Informatica Global Customer Support... 8 This document contains information on fixed and known limitations for Test Data Management. Informatica Version Installation and Upgrade Use the Test Data Management installer to perform the following tasks: A fresh install of Test Data Management An upgrade to Test Data Management The Test Data Management installer does not have an option to install or upgrade Informatica services. Before you install or upgrade to TDM 9.6.0, you must use an Informatica installer to install or upgrade to Informatica You can upgrade to Test Data Management from Persistent Data Masking and Data Subset HotFix 2 or later versions. When you upgrade, the installer copies the TDM files to the specified directory. Note: If you have a TDM version earlier than HotFix 2, you must upgrade to at least version HotFix 2 before you can upgrade to Test Data Management If you use the rule simulator in TDM, apply the following updates to Test Data Management after you install or upgrade to 9.6.0: Install EBF Install EBF TDM-RLN

2 9.6.0 Fixed Limitations For information about previous fixed limitations, review the Release Notes of previous releases. The following table describes limitations fixed in this release: When you override the source owner name and target prefix name at the source level in a plan, they do not get updated in the control XML TDM does not sort object lists on the UI You cannot save the ILM Repository password Data domain profiling on columns with complex regex functions does not return any data You cannot generate workflows for Sybase source or target connections TDM does not support VARCHAR(MAX) data type on Microsoft SQL Server connections Workflow generation happens synchronously before the workflow is submitted Import fails for project XMLs that are exported with constraints across multiple sources that are not correct You cannot generate workflows in parallel sessions TDM generates huge mappings for entities and groups with related tables For tables that have composite primary keys, TDM generates an in-place masking workflow with only one primary key connected in a mapping Integer columns convert to Varchar2 during masking TDM shows an incorrect error message when you disable a constraint When you perform a subset operation, the SQL to read the source table does not place the parentheses correctly when you use filters on two columns in a single table The Disable Index/Constraint option does not work as expected You cannot sort jobs in ascending or descending order in the Monitor view TDM generates an error when you run a subset workflow if the plan includes a table managed in both an entity and a group Workflow generation fails for tables that have columns with VARCHAR(MAX) data type on Microsoft SQL Server connections Workflows do not generate as expected on versioned repositories You cannot use the masking type Random for the date data type in any locale other than English. 2 TDM-RLN

3 You cannot assign an advanced or custom rule to a table that has columns with Varchar(max) data type, if you import the table directly. An HTTP error occurs If an advanced rule is configured with lookup ports for substitution and the standard rule that it uses is not, the mapping it generates does not have the lookup port configured When there are more than 10 tables to mask that use multiple rules, mappings are not imported successfully Disabled constraints are not disabled in the imported project XML file When you assign rules only on mandatory fields, TDM generates a java null pointer exception Mappings that TDM generates have a timestamp length of 19 and precision of 0 even though the default length is 26 and precision is When you mask a table with multiple parent and child columns, the Sorter transformation causes issues The number of tables per workflow in step 5 of the Plan UI is listed as the number of tables per mapping Known Limitations The following table describes known limitations: When you use <=, >=, <, >, and!= operators to configure conditional constraints for a numeric datatype, the generated results might not be valid. Workaround: When you assign generation rules to columns with conditional constraints, enter a sufficient range in the minimum and maximum values You cannot export a project in a non DBO (SQL) environment You cannot override the connection information in a plan at the table level or data source level when the connection includes tables across data sources You cannot search for TDM objects from the search field in a non DBO environment. The search does not return results or generate an error or log message. TDM-RLN

4 You cannot override connection information in a plan at the table level or data source level if the target includes flat files. The plan uses the connection information at the plan level. Workaround: To override connection information at the table level or data source level, edit the flat file separator to an operating system dependent separator. For example, in Linux, edit the file separator that displays as $PMTargetFileDir\ to $PMTargetFileDir/ When you do not enter the source schema name at the plan level, the source owner name is appended to the SQL generated. Workaround: Enter the source schema name at the plan level Mapgen generates invalid drop table scripts for staging tables when the table names are case sensitive. Mapgen does not add the closing double quotes in the drop table script, and the workflow fails. Workaround: Edit the SQL file in the <INFA_HOME> \TDM\cache\<plan_name> location and add the closing double quotes before you run the workflow There is no fix available for Heartbleed for TDM Tomcat on OpenSSL When you create a connection In Test Data Manager with the connection type PWX DB2 for z/os, the values for some properties are not saved correctly in PowerCenter. For the Write Mode property, if you select the value Confirm Write On in Test Data Manager, the value is saved as Confirm write Off in PowerCenter. For the Off Load Processing property, if you select the value Auto in Test Data Manager, the value is saved as No in PowerCenter. Workaround: Log in to Workflow Manager and change the values in PowerCenter An Illegal Argument Exception error occurs when you use the Workflow Stop or Workflow Abort options to stop a workflow execution When you select a table in the second data source during step seven of the plan creation workflow, the details do not load. The load icon does not disappear. Workaround: Select the override check box, and select the first data source and then select the table in the second data source. The details load and the load icon disappears A plan generates invalid mappings if any of the columns include spaces in the column name. Workaround: Do not use spaces in column names. 4 TDM-RLN

5 The Import Metadata wizard does not display the names of data sources in ascending alphabetical order You cannot use the same TDM repository content in more than two domains. When you create the TDM service in a third domain, if you select the Content exists under specified string. Do not create new content. option, login fails You cannot generate a workflow if the plan name is too long. Workaround: Create plans with the name length within the normal value You cannot link TDM global objects to business terms in a domain that uses Kerberos network authentication. Workaround: Do not enable Kerberos network authentication if you want to link TDM global objects to business terms When you use non English locale characters in the PowerCenter Repository Service name, plans and workflows might fail. Erroneous characters might appear in log messages. Workaround: Use only English characters in the PowerCenter Repository Service name You cannot run CLI commands in an environment with Kerberos network authentication enabled Pre-processing and post-processing parameters added to a standard rule do not work when you add the standard rule to an advanced rule. Workaround: Use the advanced rule expression option to add any pre-processing or post-processing parameters to the rule TDM does not process workflows in parallel sessions for hierarchical VSAM connections. TDM processes all grouped tables in a single workflow You cannot select a default character set for Test Data Generation. Test Data Generation supports only the ASCII character set When you perform rule simulation on columns with data type double on DB2 connections, TDM generates an unsupported data type error. Workaround: Change the double column data type to decimal or real before you perform rule simulation on data on a DB2 connection You cannot perform rule simulation on data from Sybase connections. TDM-RLN

6 A user with the custom role Test Data Specialist cannot create or delete data generation rules. Workaround: From the Administrator tool, edit the TDM Service custom role Test Data Specialist to include the Manage Generation Rules privilege. Users must log in again for the changes to take effect Rule simulation does not generate accurate output for a rule with pre-processing and post-processing expression parameters. The output does not include changes added in the expression parameters When you create the Test Data Manager service, you cannot use a trusted connection or Windows NT authentication to connect to a Microsoft SQL Server database. Workaround: Create a user login and provide the user name and password when you connect to the database when you create the service TDM does not support the timestamp data type for Microsoft SQL Server connections You cannot create content for the TDM server on a DB2 database that has partitioned tablespaces. Workaround: Use a DB2 database that does not have partitioned tablespaces An error occurs when you run a plan with the following dictionary connection types: - DB2 for Linux, Unix, and Windows - DB2 for i5/os - DB2 for z/os Workaround: Use ODBC as the connection type for a dictionary on DB When you generate a cyclic mapping with composite primary keys and foreign keys, the recursive executor does not include the composite keys Multiple TDM services on the same node do not work simultaneously. Workaround: To create multiple TDM services in a domain, create each TDM service on a different node The connection string of the default staging and storage connections that the TDM installer creates during upgrade might not be valid. Workaround: Check the connection string before you run a plan workflow which uses the default storage or staging connections that the installer creates Workflow execution fails on hierarchical VSAM sources when the plan contains a Shuffle masking rule. 6 TDM-RLN

7 An entity is dropped from a plan if you change the entity parameter after you include the entity in the plan. Workaround: Create another plan with the updated entity Workflow generation fails for plans that include Shuffle masking rules on Microsoft SQL Server source connections You might not be able to disable the Test Data Manager Service for the first time after creating it. The Disable button might not work. Workaround: Refresh the browser before you disable the service If you select the parameter file option for the connection string in a plan, workflow generation fails Workflow generation fails for a plan that uses connection variables and includes a Lookup transformation. Lookup connections as connection variables do not get set in the workflow. Workaround: Use connections instead of connection variables Workflow execution fails for a plan that contains an Advanced rule that uses Substitution and Shuffle rules. Workaround: Make the substitution tables available from the source connection. The workflow runs successfully if the source and target are the same When you change a masking rule assignment from the Define Data Masking tab, the plan does not update with the change. Workaround: Create a new plan and add the updated rule to the new plan. TDM-RLN

8 On Microsoft SQL Server connections with the connection type ODBC, if a table contains columns with unique identifier data type, profiling might fail. Workaround: Do not use the ODBC connection type for Microsoft SQL Server connections if the table contains columns with unique identifier data type. Use the JDBC connection Workflow generation for Oracle Applications that include the Config group fail if the workflow includes database objects with the same name and different owner names. Workaround: Select the Override Plan Settings check box on the Source Settings page of the Create Plan or Edit Plan workflow. If the plan includes the same object in different schemas, or if the schema names are different in the source and target, select the Override Plan Settings check box for each data source when you create the plan. Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires a user name and password. You can request a user name and password at The telephone numbers for Informatica Global Customer Support are available from the Informatica web site at 8 TDM-RLN