Informatica Corporation. MDM Multidomain Edition Version Release Notes November Contents. Installation and Upgrade. Before You Upgrade

Transcription

1 Informatica Corporation MDM Multidomain Edition Version Release Notes November 2014 Copyright (c) Informatica Corporation. All rights reserved. Contents MDM Multidomain Edition Version Installation and Upgrade Fixed Limitations Closed Enhancement Requests Known Limitations Informatica Global Customer Support The Informatica MDM Multidomain Edition Release Notes provide important information about known limitations of the release. Read this document carefully before you install the Informatica MDM Hub and Informatica Data Director. MDM Multidomain Edition Version Installation and Upgrade Before You Upgrade Verify that no subject area name begins with a number. If any subject area name begins with a number, change the name so that it begins with an alphabetic character. If a subject area name begins with a number, the composite object configuration generated by the MDM Hub causes Repository Manager validation errors. HORA Change List Promotion To promote a change list to an empty Operational Store, the match column length that the MDM Hub adds to the external match input table must not exceed The match column length is the MDM-HRN

2 sum of the lengths of all base object columns that are sources of the match column and the number of source columns. The change list promotion fails with the following error if the total length of the match column is greater than 4000: ORA-00910: specified length too long for its datatype HORA Dropped Support Effective in version , support is dropped for the following functionality: EJB2 Protocol The EJB2 protocol is obsolete and you must use EJB3 protocol to communicate with the MDM Hub through the Services Integration Framework (SIF) requests. IBM ILOG Charts Effective in version , ILOG charts are not supported for new customers or existing customers who previously licensed IBM ILOG chart software. Process Server Properties for Smart Search After you upgrade the MDM Hub, by default, the <MDM Hub Installation Directory>\hub\cleanse \resources\cmxcleanse.properties file does not include the following Process Server properties for smart search: cmx.ss.enabled Indicates whether to enable smart search. Set to true if you want to enable smart search. Set to false if you want to disable smart search. zookeeper.ticktime Length of a single tick, in milliseconds. ZooKeeper uses tick as the basic time unit to regulate timeouts. Default is 2000 ms. search.provisioning.maxshards Optional. Indicates the maximum number of copies of data that can be created on a single Apache Solr instance when you index the search data. Default is 1. To work around the issue, manually add the properties to the cmxcleanse.properties file. (HORA-51676) Enable Match Population On IBM DB2 After you install the Process Server in an IBM DB2 environment, you must enable the match population to use for the match rules. To enable match populations, contact Informatica Global Customer Support. HORA MDM-HRN

3 WebSphere Clustered Environments When you install the Hub Server in a WebSphere clustered environment, the deployment fails with errors. The issue appears to be related to IBM issue which is fixed in WebSphere At time of release, Informatica continues to test this release on WebSphere For updates, contact Global Customer Support. HORA Hub Server Installation in Console Mode in Oracle Environments When you install the Hub Server in console mode in an Oracle environment, the pre-installation summary has missing details. If you choose not to install Informatica Platform, a blank appears instead of the word "No" under the Install Informatica Platform heading of the summary. HORA Hub Server Installation in Console Mode You can install the Hub Server in console mode on UNIX. When you choose to install the Informatica platform as part of the Hub Server installation process, the prompts for the Informatica platform installation file locations do not appear. If you want to install the Informatica platform, perform the Hub Server installation in the graphical mode or silent mode. HORA Hub Server Installation on a WebSphere Application Server When you install the Hub Server on a WebSphere Application Server, the installation component patchinstallsetup fails. Workaround: Open the file <WebSphere profile home>/properties/soap.client.props file and increase com.ibm.soap.requesttimeout, and then restart the WebSphere server profile. Run patchinstallsetup.bat again. HORA Upgrade from Version to in Oracle Environments When upgrading the Hub Server from version to in an Oracle environment, the upgrade completes successfully, but the following error appears in the log: 19:26:22,012 INFO ImporterRole:44 - ddl: CREATE ROLE PROXY_ROLE ORA-01031: privileges insufficient You can safely ignore this error. HORA MDM-HRN

4 Upgrade Installation for Entity 360 View When you upgrade Hub Server, the entity360view.ear sometimes fails to install due to a timed out error. Workaround: You can run the installation components patchinstallsetup or postinstallsetup again. Alternatively, run the following command from the infamdm\hub\server\bin folder:./sip_ant.sh -Dentity360view.ear.dodeploy=true deploy.entity360view-ear HORA After You Install or Upgrade the Hub Server When using WebSphere or JBoss, after installing or upgrading the Hub Server, you need to delete temporary files from the application server Temp directory and restart the application server. HORA Fixed Limitations MDM Hub Fixed Limitations The following table describes fixed limitations: HORA HORA-51811, HORA HORA-51410, HORA HORA-51178, HORA HORA-51044, HORA HORA-50936, HORA HORA HORA-50770, HORA HORA-50769, HORA The Stage job for MDM_sample fails in IBM DB2 and Microsoft SQL Server. When you open the Merge Manager, the following errors appear: SIP-09070: Couldn't get merge information records SIP-10322: java.lang.nullpointerexception The Enable Distinct feature does not work correctly when PKEY columns pass through three or more levels of functions. Tokenization fails with the following error: SIP-16013: SQL Loader failed while loading file hub tmp-keyf0.dat. Return code is 2. When the MDM Hub manages a high number of users, the Users and Groups tool responds very slowly. When you use the SIF API to make a SearchQuery call on a base object, the call does not return effective dates for the BVT. When you run stage jobs from Batch Groups, a connection leak occurs. When you run an automerge job on Party, the process fails with an Optimistic Lock Failure. Issues with match and merge. For EXACT Match query, the indexes are not created properly. When NULL to NULL Matching is not enabled, the match job still matches records with a NULL value. 4 MDM-HRN

5 HORA HORA-50723, HORA HORA-50701, HORA HORA-50686, HORA HORA HORA-50340, HORA HORA-50295, HORA HORA-50275, HORA HORA-50131, HORA HORA-50099, HORA HORA HORA HORA-50048, HORA HORA-50043, HORA HORA-49863, HORA HORA-49853, HORA HORA-49011, HORA With an idb Oracle datasource, the unmerge API returns the wrong rowid for unmergereturn. If you use an ORS-specific API to create a PUT request with periodstartdate and periodenddate, the MDM Hub updates the database with a NULL value. In SQL Server 2012, the Operational Store validation process runs very slowly. When creating the MDM Hub Master Database from a remote Windows machine, the build fails if you use spaces in the database path. When you test an IDQ function, the test generates a run-time exception. The autopromote batch job and cmxsm.auto_promote run much slower than the load process. When running a searchmatch request with a recordstoreturn value, the number of records returned is correct, but the records do not represent the highest match scores. When you use the CleansePut API, the put operation fails with the following error: Unique Value of the Custom Unique Column in the inserted XREF was found in other BO. When you set the landing table column to not nullable, the ORS validation process returns the following error: SIP-MV for RAW/REJ/PRL/OPL that the column needs to be nullable After you define the task assignment userexit, the task assignment daemon returns errors. If you use SIF DELETE to delete pending cross-reference records from an active parent record, active child records are incorrectly soft deleted. If you create a base object with a fuzzy and exact match rule and then run the match, the match process fails with the following error: SQL0552N (-552) SQLERRMC=GPM_ORS;IMPLICIT CREATE SCHEMA The UpdateRel API runs very slowly. When sequences are loaded into the cache, a Numeric Overload error appears in the cmxserver log file. () When a validation rule exists on columns that are missing in the stage table, the validation process returns the following message as an error when a warning would be sufficient. SIP-MV The SIF API generation process runs very slowly. Before deleting a message queue, delete any message triggers that are pointing to the message queue. MDM-HRN

6 HORA-48999, HORA HORA-48979, HORA HORA-48966, HORA HORA-48955, HORA HORA-48953, HORA HORA-48946, HORA HORA-48917, HORA HORA-48887, HORA HORA-48868, HORA HORA-48817, HORA HORA HORA HORA HORA-39369, HDBT HORA The documentation for fuzzy match rules incorrectly states that, when the Match Purpose is Individual, the Match Column list can contain either ID or Date. In fact, the list must contain both the ID and the Date. When you import a Common Warehouse Model file, the Repository Manager generates an error. In UNIX environments, the Operational Store upgrade fails. When you add tables to a query, the tables do not link even though foreign keys are present, and the MDM Hub generates an error. When you run stage jobs, the MDM Hub generates the following error intermittently: java.util.concurrentmodificationexception When a parent table has a child REL table with two foreign keys to the parent table, and you run automerge, the automerge process fails with a deadlock condition. When you assign a block of tasks, IDD determines which users are available for each task. If IDD determines a user in not available for a task, IDD does not consider this information when it determines available users for the next task. The CleansePut API does not process carriage returns in data. When you perform a multithreaded batch load to a timeline-enabled base object from a staging table with multiple versions of records, some valid record versions are marked as No action. When you use specific columns to enable delta detection in the MDM Hub, duplicate values from different source systems result in rejects. When you use the Operational Store sample schema, you cannot open the Hierarchies tool in the Hub Console. L10N DE: Invalid characters are displayed in the sqlplus window when creating an Operational Store. Static view creation fails for base objects that have many columns. When you approve a task, column errors occur in the server log even when the column does not have validation rules. When a base object has a putable package, the SearchMatch option is missing from ORSspecific API. 6 MDM-HRN

7 HORA HORA Javadoc for PromotePendingXREFs SIF API includes the following incorrect information: When a list of column names is provided in the request, only the columns represented by the list of names will be kept on the XREF promoted to the ACTIVE state. Data for columns that are not specified will be lost after the promotion. The actual behavior is that all column values are retained for the promoted XREF. In the Data Manager, when you update a column value that meets a validation rule, trust score does not downgrade. Informatica Data Director Fixed Limitations Review the Release Notes of previous releases for information about previous fixed limitations. The following table describes fixed limitations: HORA HORA HORA-51035, HORA HORA-50664, HORA HORA-50051, HORA When you configure data security for auto task assignment, task assignment fails. Unable to add hierarchy code and rel type code into the layout of child that is defined as many-to-many and is Hierarchy Manager enabled. When you save the configuration, the following error appears: HM columns are already added to CO/CS definition. After changing the LAST_UPDATE_DATE column to Putable and updating the record by using CleansePut, you cannot pass a value to the LAST_UPDATE_DATE column. When you save a query from a subject area, the Save Query function fails with an error. The Mark for Save feature creates a new cross-reference record instead of updating the effective period for the existing cross-reference record. MDM-HRN

8 HORA-42411, HORA HORA If you search for a record that is in the pending state and then try to add it to the Hierarchy View, the record is not added. The MDM Hub generates an error. When you use Internet Explorer to upload a custom Login Provider jar, an error occurs and you cannot upload the file. Closed Enhancement Requests MDM Hub Closed Enhancement Requests The following table describes closed enhancement requests: HORA-50935, HORA HORA-48957, HORA HORA-48890, HORA HORA-48876, HORA HORA-48872, HORA HORA With timeline enabled, if you load multiple versions in the same batch, the following error appears: Active Record will create gap. You can use the Hub Console to identify users that have acquired a lock in the MDM Hub. Improved the performance of ORS-specific APIs generation by providing the option to select specific objects for which you want to generate APIs. You can generate ORS-specific APIs for Operational Store objects that you select. The MDM Hub associates a version ID with each ORS-specific APIs client JAR file that it generates. Implemented encryption in the following ways: - Encrypt data before sending data from IDD to the Hub server - Encrypt data before executing the cleanse function A sample of DataEncryptor is included in the resource kit. You can use it to encrypt and decrypt CSV files. In JBoss, you can set the OFF-SET to support uniqueness of ports when multiple standalone profiles are running under the same server installation. The MDM Hub sets the JBoss remoting port dynamically. 8 MDM-HRN

9 Informatica Data Director Closed Enhancement Requests The following table describes closed enhancement requests: HORA After updating an IDD application to use the ActiveVOS Server that is installed with the Hub Server in v , an administrative user can view completed tasks for all users. Known Limitations MDM Hub Known Limitations The following table describes known limitations: HORA HORA HORA HORA HORA HORA HORA HORA HORA The MDM Hub does not support the import of a change list created in one database type into the repository of another database type. For example, you cannot import a change list created in Oracle into a Microsoft SQL Server repository. When you use change lists with custom queries to promote changes to metadata, the change list promotion might fail. Workaround: Remove the Operational Store name from the tables that you use in custom queries. Enabling state management for a base object that has custom packages does not resolve Repository Manager validation error SIP-MV Workaround: Drop the custom packages and then enable state management. When you register an Operational Store in the Hub Console, if the database host name that you specify contains period (.) or uppercase characters, the batch jobs fail. Workaround: Do not use the IP address or the fully qualified domain name of the remote database as the database host name. Use the host name of the remote database as the database host name without fully qualifying the name. Ensure that the database host name does not contain uppercase characters. The MDM Hub does not support case-sensitive database collation for Microsoft SQL Server. The MDM Hub does not support the Hard Delete Detection feature for IBM DB2 or Microsoft SQL Server. The MDM Hub does not support custom validation rules for IBM DB2 or Microsoft SQL Server. When using idb Oracle, a user with the Security Access Manager (SAM) Proxy Role for an Operational Store has access to functions that are not intended for the role. In particular, a user with the Proxy Role can access the MET promote, the Promote button, and the Import button. After creating an ORS and applying a changelist from a previous version, the Base Object Multi Thread Batch Ind property is set incorrectly to 0. Workaround: You can set this property to a value of 1 from the Hub Console. MDM-HRN

10 HORA HORA HORA HORA HORA HORA HORA HORA If you add a new user in the Hub Console and immediately change the user password, the user cannot log in with the new password. Workaround: Instruct the user to log in with the existing password and then change the password. In a Microsoft SQL Server environment, the GetOneHop API request might stop responding. Workaround: For the repository table C_REPOS_SEARCH_RESULT_STATE, set LOCK_ESCALATION to DISABLED. On high loads with multiple cleanse servers involved, the automerge job sometimes fails. Workaround: Restart the application server and then run the automerge job again. When you run a match job with network speeds of 10 Gbps in full duplex mode, the match job does not complete. Workaround: Set the network speed to 1 Gbps in full duplex mode. When you run a load job in a Microsoft SQL Server environment, the MDM Hub fails to process records that contain special characters. Special characters include accented letters or letters with diacritical marks. Workaround: Special characters in keys can cause issues with key duplication. Avoid use of special characters in a primary key. Also, key duplication can occur if you have some primary keys in uppercase and some in lowercase. Ensure all primary keys are in one case. When cmx.server.automerge.threads_per_job=1, the automerge process merges conflicts up to a maximum of 1,000 records and cleans the remaining records from the _MTCH table. Workaround: To merge all records, set the value of this property to 20 in the cmxserver.properties file: cmx.server.automerge.threads_per_job=20 After you install the MDM Hub, the job metrics do not appear in the Hub Console when you run a stage job for the first time. The job metrics appear in the Hub Console for all subsequent stage jobs. When you view the Hub Console in the Chinese language, the date format appears in English. 10 MDM-HRN

11 Composite Object and Composite Service Known Limitations The following table describes known limitations: HORA HORA HORA HORA HORA HORA HORA HORA HORA HORA When you perform a partial promote of components related to composite objects in Repository Manager, validation errors might occur. Workaround: Promote the complete composite object configuration. When you promote a searchable composite object configuration in Repository Manager, validation errors occur. Workaround: Promote the complete composite object configuration that the searchable composite object configuration is associated with. When you run a read composite service for a deleted grandchild record, the composite service call does not return data. When you promote a REST service in Repository Manager, validation errors occur. Workaround: Promote the composite services configuration. The MDM Hub does not prevent you from creating a child record that does not share the same effective period as the parent record. Workaround: Ensure you maintain timeline consistency within a composite object when you create a record. When you read a pending record, the composite service does not return the record and an error occurs. Workaround: Add?recordStates=ACTIVE,PENDING to the REST URL. When you update records in a composite object, more exceptions occur than are expected. When you specify a source key and source system to delete a record, the composite service deletes the base object record instead of a cross-reference record. The MDM Hub does not prevent you from deleting a record that has an active child record. Repository Manager does not handle conflicts correctly during composite object configuration promotion. When multiple objects in a composite object have the same name but their hubobject values refer to different base objects, Repository Manager generates validation errors but successfully promotes the composite object configuration. Workaround: Use unique names for objects that do not refer to the same base objects. Informatica Data Director Known Limitations The following table describes known limitations: HORA HORA Some Informatica Data Director menu items are not localized. Subject Area names cannot begin with a number. MDM-HRN

12 HORA HORA HORA HORA After you install Microsoft Windows update KB , you cannot select the first Wednesday of the year in the date selection calendar. When you use the Chrome browser, you cannot log in to Informatica Data Director with saved credentials. For IBM DB2 Operational Store databases, Task Administration occasionally fails. Workaround: Increase the maximum number of client connections allowed for each database partition through the following command: db2 UPDATE DBM CFG USING MAX_CONNECTIONS 300 MAX_COORDAGENTS 300 In Configuration Manager, when you edit a subject area configuration to set the edit style of a column to Checkbox but then cancel the change, a null pointer exception occurs when you open a new subject area entity form. Entity 360 Known Limitations The following table describes known limitations: HORA HORA HORA HORA HORA HORA HORA HORA If you restart the application server while logged in to the Entity 360 view, you cannot log back in after you refresh the page. Workaround: Enter a valid Entity 360 view URL in your browser. If you perform a search in the Entity 360 view and apply an integer field filter on the search results, Informatica Data Director generates an error. In WebLogic environments, after you log in to the Entity 360 view and then clear your browser cache, you cannot log in to the Entity 360 view again. Workaround: Clear the cookies from your browser. When you view a pending record in the Entity 360 view, there is no indication that the record is pending. The GetOneHop component displays entity label data that comes from the cross-reference table instead of the base object. Entity 360 access control depends on the base object of the root composite object, not on Subject Area permissions. In the Entity 360 view, the GetOneHop Component does not sort related entities. If an Operational Store used in Informatica Data Director has a searchable configuration that is invalid, then you cannot log in to the Entity 360 view. Workaround: Ensure all searchable configurations are valid for each Operational Store used in Informatica Data Director. 12 MDM-HRN

13 HORA In the Entity 360 view, when you open Hierarchy Manager for a record with 100 relationships, Informatica Data Director generates an error. Workaround: To fix Java compatability issues, set the system property java.util.arrays.uselegacymergesort to true. HORA In the Entity 360 view, the GetOneHop Component does not show more than 100 relationships for a record. There is no pager button to view more relationships. Workaround: Configure the data view component with a value for size that is smaller than the GetListLimit value in C_REPOS_DATABASE. HORA HORA HORA HORA HORA HORA HORA HORA HORA HORA HORA HORA HORA After you set the system property IDD2COCSConverter.prefixCoNames to true, the Entity 360 view configuration fails. The Entity 360 view is disabled by default in Informatica Data Director. Workaround: In the cmxserver.properties file, set the cmx.e360.view.enabled property to true. After you update the server properties, you must validate the schema and then redeploy the Informatica Data Director application. Then restart the Hub Console for the change to take effect. In the Entity 360 view, the Person.Organization.org record does not appear. After you select a child record of Person.Organization, the Person.Organization.org appears. In the Entity 360 view, the details for a base object do not appear correctly for many-to-many child records. To configure the Entity 360 view, you need direct access to the C_REPOS_COMPONENT_INSTANCE table to insert data into it. There is no tool in the user interface of Informatica Data Director to configure the components for the Entity 360 view. You cannot log in to Informatica Data Director application in Entity 360 view. Workaround: Release the lock in the MDM Hub Console and clear browser cookies. The Entity 360 matches component does not display null values correctly. The Twitter component loads more slowly than expected. When you open Entity 360 view from an entity component, the count in the Matches component is incorrect. Workaround: Open the entity view from search results. Entity 360 components in the right hand panel are not formatted correctly. If a composite object root node record does not contain data, the child record is not formatted correctly. The Entity 360 cross-reference record component does not display pending cross-reference records. The Entity 360 cross-reference record component only displays active crossreference records. You can log in to Entity 360 before Informatica Data Director starts. MDM-HRN

14 Smart Search Known Limitations The following table describes known limitations: MDM-574 HORA HORA HORA HORA HORA HORA HORA HORA HORA Smart Search is not recommended if your data exceeds three million records. Higher volumes of data cause slower indexing and search operations. The Initially Index Smart Search Data job stops responding. Workaround: Set the job status to incomplete, restart the application server, and run the Initially Index Smart Search Data job after a few minutes. The first smart search request takes a long time to return results after you configure smart search and run the Initially Index Smart Search Data job for the first time. Smart search requests might fail against large data set. If the composite objects do not include a field named displayname, the Name column in the Search workspace displays random field values when you perform a smart search. Workaround: To set a field for the Name column, use a database tool to open the C_REPOS_CO_CS_CONFIG table and set the displayname property of the composite objects to an appropriate field in the BLOB data of the SEARCHABLE_CO configuration type. Smart search requests return the following error message after you remove a searchable column from a layout in the Configuration Manager: [SearchService_30027] Exception occured while getting query the constructor Workaround: Stop the application server, delete the <MDM Hub Installation Directory>\hub\cleanse\solr folder, and delete all the files in the ZooKeeper data directory that you set when you configured the Process Server. Restart the application server, run the Initially Index Smart Search Data job after a few minutes, and perform the smart search. Smart search requests do not return results after you configure a field as a searchable field and run the Initially Index Smart Search Data job. Workaround: Stop the application server, delete the <MDM Hub Installation Directory>\hub\cleanse\solr folder, and delete all the files in the ZooKeeper data directory that you set when you configured the Process Server. Restart the application server, run the Initially Index Smart Search Data job after a few minutes, and perform the smart search. In the Informatica Data Director application, if a non-admin user who has the READ privilege on all the subject areas and base objects performs a smart search, the hierarchy view and the data view of a result do not display any data. The non-admin user cannot create a task for a result. If a non-admin user who does not have any privilege performs a smart search, the Informatica Data Director application displays an unclear error message. After you create an inactive relationship between two entities and run the Initially Index Smart Search Data job, a smart search request returns the entities that have inactive relationship. 14 MDM-HRN

15 HORA HORA When you specify the filter type for a field in the C_REPOS_COMPONENT_INSTANCE table as UNDEFINED in uppercase and perform a smart search, you get the following error message in the application server log file: ERROR [org.jboss.as.ejb3.invocation] (http-/ :8080-2) JBAS014134: EJB Invocation failed on component SearchClientConfiguration for method public abstract Workaround: Specify the filter type as undefined in lowercase and perform the smart search again. Smart search requests fail in a WebSphere environment if you specify the application server SSL port as the HTTP port when you add a process server. Workaround: Use a non-ssl port as the HTTP port of the application server. The default application server SSL port is 9443, and the default non-ssl port is HORA After you perform a smart search, the Search workspace cannot display more than 2000 results from each composite object when you scroll through the workspace to view the results. HORA HORA HORA HORA HORA HORA HORA Smart search requests do not display some records after you run a load job, and you get the following error message in the server log file: SIP-52039: Failed to create a collection for the composite object Workaround: Stop the application server, delete the <MDM Hub Installation Directory>\hub\cleanse\solr folder, and delete all the files in the ZooKeeper data directory that you set when you configured the Process Server. Restart the application server, run the Initially Index Smart Search Data job after a few minutes, and perform the smart search. Smart search results are not correctly filtered when you enter a filter value in a CHAR type field and filter the results. Workaround: Change the data type of the field to VARCHAR or add spaces to the string when you enter a filter value so that the total character count of the filter value matches the defined field length of the field. After you configure smart search and restart the WebLogic or WebSphere application server, the application server log file includes the following error message: [ERROR] com.informatica.mdm.search.provisioning.collectionhelper: KeeperErrorCode = NoNode for /live_nodes Workaround: Ignore the error message. Smart search requests do not display the merged or unmerged records after you manually merge or unmerge records in the Data Manager. Workaround: Run the Initially Index Smart Search Data job to add the merged or unmerged records to the index and perform the smart search again. The Initially Index Smart Search Data job might return incorrect metrics if you run the job more than once. When you use a date format such as or 11\-20\-2014 as a search string and perform a smart search, the request returns no results. If you use a date format such as Nov , the request returns results that match 20, 2014, or November. Smart search requests do not return results for a non-admin user. MDM-HRN

16 HORA HORA HORA When you perform a smart search, the Search workspace cannot display more than 100 facets for a field. When you add or edit a Process Server, the Hub Console does not validate the value that you specify for the ZooKeeper data directory. After you perform a smart search, when you scroll through the Search workspace to view the next batch of results, you cannot scroll up to view the previous batch of results. Workaround: Perform the smart search again and scroll through the workspace to view the required results. MDM Hub Integration with Informatica Platform Known Limitations The following table describes known limitations: HORA HORA HORA HORA HORA HORA HORA HORA HORA If you perform the stage process in the Informatica platform, you cannot use the ClenasePut API. If you perform the stage process in the Informatica platform, the MDM Hub cannot detect the records that are hard-deleted in source systems. When you enable the option to preserve the source system keys for Informatica platform staging, source system keys are not preserved. When you perform Informatica platform staging, you cannot set up delta detection and audit trails for the staging table data. When you perform Informatica platform staging, source records that indicate that the last updated date is in the future are inserted into the LAST_UPDATE_DATE column in the staging table. Workaround: Configure transformations for the stage process that can reject records that indicate that the last updated date is in the future. After you open a logical data object in Informatica Developer (the Developer tool), the Save button becomes available before you make any changes. When you open a logical data object in the Developer tool, the following warning appears: Model Contains Data Objects from Informatica Analyst. Workaround: You can ignore the warning. During the Model repository synchronization process, the MDM Hub does not create a mapping with a logical data object to write to. To run Informatica platform staging, create a mapping that includes a physical data object as the source, a logical data object as the output, and a mapplet for cleanse operations. When you synchronize the Model repository with the MDM Hub, the synchronization process creates a customized data object and a relational data object. Do not use either the customized data object or the relational data object as direct targets in any mapping that you define. 16 MDM-HRN

17 HORA HORA When you synchronize the Model repository with the MDM Hub, the synchronization process creates a logical data object read mapping and logical data object write mapping. If you open one of these logical data objects in the editor and then save them, the objects disappear from the Model repository. Workaround: You can ignore the issue. You cannot use the same mapping to transfer data from multiple source systems. Informatica Dynamic Data Masking Known Limitations The following table describes known limitations: HORA In Microsoft SQL Server environments, when you try to add a record to a base object that has been blocked by Dynamic Data Masking, the MDM Hub generates the following error: An unknown error occurred. Workaround: Restart the Dynamic Data Masking service and unregister the Operational Store. Then restart the JBoss application server. In the Dynamic Data Masking management console, remove the current port and add a different listening port. Finally, in the MDM Hub, register the Operational Store and set Dynamic Data Masking to the new port. HORA To use Dynamic Data Masking in the MDM Hub, you must have Dynamic Data Masking and Emergency Bug Fix installed. Earlier versions of Dynamic Data Masking are not compatible with the MDM Hub. MDM Hub Integration with Informatica ActiveVOS Known Limitations The following table describes known limitations: HORA HORA HORA In the Task Inbox, task filters do not work as expected. - Title filter. Non-exact match does not work. For example, if you have a task with the title abc1 and you filter by abc, the abc1 task is not found. - Due Date Status filter. The On time value does not work. All tasks are always displayed. - Select Task Type from dashboard. No tasks are displayed. - Due Date filter. All tasks are always displayed. In the Task Inbox, unexpected values appear in the Task Type filter list. For example, the list contains only the Review No Approve task type, but the Task Inbox contains tasks with other task types. When you configure multiple Operational Stores to use the ActiveVOS workflow engine, the total tasks count in the IDD Task Inbox is incorrect for a particular Operational Store. The tasks count shows the total tasks count across all Operational Stores. MDM-HRN

18 HORA MDM-2537, HORA ActiveVOS tasks created in one Operational Store are visible in other Operational Stores for the admin user. When the ActiveVOS Server runs in a different application server than the Hub Server, a user cannot claim a task from the Task Inbox. Workaround: Ensure that the user account has the same password in both systems. 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 18 MDM-HRN