Informatica Corporation Informatica 9 Version 9.0 Release Notes January Contents

Transcription

1 Contents Informatica Corporation Informatica 9 Version 9.0 Release Notes January 2010 Copyright Informatica Corporation Informatica Domain... 2 Informatica Domain Installation... 2 Informatica Domain Closed Enhancement Requests...3 Informatica Domain Known Limitations... 3 Informatica Domain Documentation Updates... 4 PowerCenter... 4 PowerCenter Compilers... 4 PowerCenter Fixes... 4 PowerCenter Closed Enhancement Requests... 6 PowerCenter Known Limitations... 6 PowerCenter Third-Party Limitations... 7 PowerCenter Documentation Updates... 7 PowerExchange... 8 PowerExchange Installation... 8 PowerExchange Fixes... 8 PowerExchange Known Limitations... 9 Informatica Analyst Informatica Analyst Known Limitations Informatica Developer Informatica Developer Known Limitations Informatica Developer Documentation Updates Data Quality Content Installer Data Quality Content Installer Known Limitations Data Analyzer Data Analyzer Known Limitations Data Analyzer Documentation Updates Metadata Manager Metadata Manager Fixes Metadata Manager Closed Enhancement Requests Metadata Manager Known Limitations Contact Information This document contains important information about installation, fixed limitations, and known limitations for the Informatica domain, PowerCenter, Data Analyzer, Metadata Manager, Informatica Data Quality, and Informatica Data Services. IN_RLN_90000_

2 Informatica Domain Informatica Domain Installation Upgrade You cannot upgrade to Informatica 9 from previous versions of PowerCenter, Metadata Manager, Data Analyzer, Data Quality, Data Explorer, or PowerExchange. Informatica Domain Patches and Libraries Platform Operating System Operating System Patch Java 6 Patch Linux-x64 Redhat el _13 Linux-x86 Redhat el _13 Linux-x64 SuSe bit SUSE Linux Enterprise Server 10 (x86_64) VERSION = 10 PATCHLEVEL = _13 Linux-x86 SuSe bit SUSE Linux Enterprise Server 10 (i586) VERSION = 10 PATCHLEVEL = _13 Linux-x64 SuSe bit SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = _13 Linux-x86 SuSe11 32-bit SUSE Linux Enterprise Server 11 (i586) VERSION = 11 PATCHLEVEL = _13 Solaris-sp64 Solaris 10 U6 10/08- kernel-patch _13 Win-x64 Win-x86 Windows 2003 SP2 and above 1.6.0_13 (win x64) 1.6.0_12 (win x86) Win-x64 Win-x86 Windows bit Windows bit SP1 SP _13 (win x64) 1.6.0_12 (win x86) To run the AXIS samples or any client application developed with AXIS, you need AXIS 1.4. You can find AXIS libraries in $INFA_HOME/server/samples/WebServices/lib/axis-1.4. Informatica Domain Functionality Not Available in 9.0 The following functionality is not available in 9.0: Upgrade wizard Node diagnostics Alerts -2- IN_RLN_90000_0003

3 Mixed-version domains a license management report Domain permissions Configure preferences Parameter file File wait events Informatica Domain Closed Enhancement Requests Informatica Administrator does not show all ports used by different Informatica components. Informatica Domain Known Limitations When the master gateway node fails over to another node, all other gateway nodes shut down When you create a PowerCenter Integration Service through infacmd and you do not specify the code page process option, you cannot view or change the code pages in the Administrator tool. Workaround: Specify the code page when you create the service, or use the infacmd isp UpdateServiceProcess command to change the code page When the gateway node fails over, the Model Repository Service continues to try to connect to the previous gateway node. Workaround: Restart the Model Repository Service infacmd considers case for parameters such as node name when you create a service. The service appears in the Navigator but not in the domain perspective. Workaround: Enter all dependent domain objects as case sensitive You must specify the Java memory values in megabytes. You cannot specify gigabytes or kilobytes The infasetup isp definedomain command returns incorrect error messages when the command contains tablespace errors The $PMRootDir service process variable shows unknown location after you add a node to a grid The infasetup isp definedomain command does not have a parameter to configure the schema for a Microsoft SQL Server database. Workaround: Configure the schema for the domain configuration database to be the default schema for that user account The DTM hangs when you connect to mysql through ODBC to preview columns of the bit datatype with a precision greater than You cannot import a Sybase table through ODBC when the table name contains more than 30 IN_RLN_90000_

4 characters. For more information, contact DataDirect and refer to issue WR W a The infacmd isp SwitchToWorkerNode command fails to switch a master gateway node to a worker node. An error occurs See The master node shuts down if it does not have enough file descriptors. Some master domains may require more than 1,024 file descriptors. Informatica Domain Documentation Updates Command Reference Add the following parameter to the infacmd isp ImportUsersAndGroups command: Options RemoveInvalidReferences -rf Optional. Removes invalid references from the import group before adding it to the domain. PowerCenter PowerCenter Compilers You can use any C compiler for Custom transformation procedures. Use the C++ compilers versions that appear in the Product Availability Matrix. The Product Availability Matrix is available on the Support page at Use C++ compiler versions for any External Procedure or Custom transformation, and when you develop with PowerExchange SDK. If you compiled the DLL or shared library with a C++ compiler version that does not appear in the Product Availability Matrix, you need to recompile it. You do not need to recompile a Java transformation if the JDK is compatible with the version you used for the previous compile. PowerCenter Fixes The DTM process shuts down unexpectedly when a Unstructured Data transformation session has more than 20 output ports The DTM process shuts down unexpectedly when you configure the error log options for a flat file in the session properties The Integration Service adds the empty XML namespace prefixes while converting the XML anytype datatype to the string datatype. -4- IN_RLN_90000_0003

5 After an upgrade from 8.1.1, you cannot edit the precision of the Integer datatype that is set as 10 in a fixed-width flat file The Integration Service does not save the scheduler in a versioned repository after you convert a nonreusable scheduler to a reusable scheduler for a workflow The Administrator tool displays ContentMaster in the licensed options instead of Data Transformation The PowerCenter Services user needs the write permissions for the PowerCenter Services installation directory to attach a session log to a post-session After you export the workflow from the Repository Manager and import it into the Workflow Manager, the fixed-width flat file property that treats multiple delimiters as one gets disabled When you delete a mapping from the Designer, the Designer displays a message that states the mapplet will be deleted from the repository The Integration Service hangs sessions with a Normalizer transformation when the session is configured to run on a grid with three nodes The Integration Service reads data with a single thread from a Sorter transformation session set for dynamic partitioning and configured to run on a grid with nodes on Solaris and 64-bit AIX The Designer cannot import an exported XML target definition that has the Long datatype with a precision of Users cannot connect to the repository after a failover XML Parser transformation does not retain primary key values after you deploy the transformation from the test repository to the production repository Deploying a deployment group that has a global shortcut creates name conflicts with the objects in the global shortcut and adds additional objects in the target repository Service Manager memory leak occurs when a Repository Service process shuts down unexpectedly on a domain that runs without the High Availability option Pushdown optimization session fails or causes the Workflow Manager to shut down when any Union transformation port is not connected to a downstream transformation The Integration Service configured to write column headers to flat file targets fails sessions configured to use the header command output to generate a header row in the flat file target Expression masking returns source data values when the expression is empty Session log does not contain Oracle database error when a SELECT statement fails within a before insert trigger English help appears instead of Japanese when you use Firefox to log in to the Administration Console Mapping Architect for Visio cannot generate a mapping when a Router transformation has multiple inputs from different sources and transformations Integration Service shuts down when truncate target table option set The session log contains incorrect statistics in the load summary when streaming is enabled for the XML Parser transformation Designer does not update the ports in a Normalizer transformation when you change the ports in the IN_RLN_90000_

6 VSAM source The installer does not log the custom string settings in the debug log See The Repository Manager displays an error when you import an object into a repository that has no folders Cannot import a Rank transformation into the PowerCenter repository because the Integer datatype is not valid. PowerCenter Closed Enhancement Requests Importing an XML definition as an entity relationship does not import some inheritance relationships Configure a database connection property to commit rows to an IBM DB2 target in a SQL transformation SQL transformation session configured with the Verbose Data session log tracking level should log the complete SQL query in the session log The Java Mapping Framework does not include transformation shortcuts After you export a workflow and import the workflow into the Workflow Manager, the fixed-width flat file property that treats multiple delimiters as one is not imported The DB2/AIX64=DB2ODBC.DLL entry is not included by default in powrmart.ini Running a query using the pmrep ExecuteQuery command takes longer to complete than running the query from the Repository Manager Replace the CLOB datatype with the varchar datatype in an IBM DB2 and Sybase repository Lookup transformation should return multiple rows from a lookup. PowerCenter Known Limitations The Administrator tool might not list the deployed applications in the Applications view if the Data Integration Service is running a non-master gateway node on SuSe 11 Linux You cannot enter tab keys on the Java Code tab of the Java transformation Java syntax highlighting is not available in the Java Code tab of the Java transformation , , The workflow hangs when it uses a parameter file, and the Integration Service on Linux 32-bit uses an operating system profile. Parameter files and file watch events are not supported in IN_RLN_90000_0003

7 The Integration Service writes an incorrect decimal number to a DB2 target decimal column when the precision is 19 or greater and PowerCenter is running on Linux 32-bit. Workaround: Enable high precision You do not have to disable the Integration Service before you change the grid on which the Integration Service runs A session uses an increasing amount of memory when a Java transformation passes rows to the Unstructured Data transformation Pushdown optimization session fails when Source Qualifier transformations are based on the same source When you enter a date range for a random data mask, the Designer accepts invalid date values. PowerCenter Third-Party Limitations Teradata ODBC session on UNIX fails when you use the update system operator and set the OptimizeTeradataUpdate custom property. For more information, see Teradata incident <RECDCHD82>. PowerCenter Documentation Updates PowerCenter Advanced Workflow Guide Pushdown Optimization Add the following rules and guidelines for pushdown optimization The Integration Service processes the Joiner transformation if the join condition is based on a column with a binary datatype. Pushdown optimization stops at the Lookup transformation when the mapping contains a lookup on a Netezza and the lookup match policy is not set to "Match All Values." PowerCenter Repository Guide Exporting and Importing Objects Importing Objects from Informatica Developer Remove the following text: If you import a mapping or mapplet that contains data quality transformations, you must have the Informatica Data Quality Integration for PowerCenter plug-in, or you cannot import the objects into PowerCenter. Step 4 in Updating Imported Objects should read as follows: Verify that reference tables exist. When you import mappings or mapplets with transformations that use reference tables, verify that the reference table files exist in the PowerCenter dictionary directory on the machine that hosts Informatica Services: <PowerCenter Installation Directory>\services\<Informatica Developer Project Name>\<Informatica Developer Folder Name> IN_RLN_90000_

8 If the reference table files are not in this directory, the PowerCenter sessions that use the reference tables do not run. PowerExchange PowerExchange Installation Follow the procedures in the PowerExchange Installation Guide for a full, first-time installation. Before you begin, verify that PowerExchange 9.0 supports your operating system and database versions. For more information about PowerExchange software requirements, see the Planning Guide for Installation and Migration. PowerExchange Fixes If you use the Database Id Override field in the PowerCenter session properties to override the Database ID value in an Adabas data map, the workflow associated with the session might fail. PowerExchange ignores the override value In you use DB2 Version 9.1 for z/os new-function mode in a data-sharing environment, change data loss might occur if you have multiple log records with the same LRSN in a data-sharing member. If two of these records are begin-ur records, the DB2 EC creates two begin-uow records that have the same UOWID for the PowerExchange Logger. When one of these UOWs ends, the PowerExchange Logger rejects all further change records for the other UOW and issues the error message PWXEDM172777E If you use an Adabas data map that creates a row for each array entry in a variable-length array and the array contains empty entries and fields that are not mapped, when you run a workflow with a mapping based on the data map, PowerExchange might return rows containing the empty array entries to PowerCenter If you start multiple instances of the PowerExchange Logger for Linux, UNIX, and Windows that use the same configuration file or share the same directories on shared network disks, contention issues can arise because of the use of lock files. In this case, the second PowerExchange Logger instance does not start If you configure PowerExchange to use alternative log files on i5/os, the PowerExchange Listener process logs messages to a single file. This behavior occurs even though the FILENUM parameter in the TRACING statement is set to a value greater than On z/os, the PowerExchange Listener task might end abnormally with an S0C4 in the DTLDMSMF load module at offset C if you specify the STATS parameter in the DBMOVER configuration file to write SMF statistics. This error occurs because of a resource locking issue On i5/os, PowerExchange might not update restart token values when a journal receiver switch occurs during a period of inactivity With PowerExchange HotFix 1 and HotFix 3, the attribute Database file overrides on a PWX DB2i5OS relational connection for a bulk data movement session fails to override the default source or target DB2 table. -8- IN_RLN_90000_0003

9 The following code-page conversion errors might occur when you use PowerExchange to move bulk or change data with Arabic characters from a z/os source that uses the ICU EBCDIC-based IBM-420 code page to a Windows target: Digits are reversed when both Arabic characters and EBCDIC digits are present in the same field. Fixed shape EBCDIC Arabic characters in the IBM-420 code page do not properly convert to variable shaped characters in the Windows 1256 code page. Word boundaries might be ignored The DTLURDMO utility incorrectly issues error message PWX if you copy a data map under another file name by using the RENAME MAP parameter in the DM_COPY statement If you configure PowerExchange Condense on i5/os to perform a file switch after a specific number of records and do not use commitment control attributes on the PWXPC connection, Condense jobs might stop responding after running for a while. In this case, you must issue the End(*IMMED) command to stop the jobs On Linux, UNIX, and Windows, the PowerExchange Logger does not flush records to its log files based on the FILE_FLUSH_VAL frequency that is specified in the pwxccl.cfg configuration file. Instead, the PowerExchange Logger flushes records when a file switch occurs. This error is caused by the incorrect interaction of time-based criteria related to PowerExchange Logger processing When you run a workflow that includes a mapping with a DB2 for i5/os Stored Procedure transformation of the type Source Pre-Load, PowerExchange returns error message PWX Also, the workflow ends abnormally. This issue pertains to workflows for bulk data movement or CDC For Oracle CDC on Linux, UNIX, or Windows, the maximum value for the Array Size parameter in the ORCL CAPI_CONNECTION statement is too small on systems that have a high level of database change activity. The maximum value has been increased from 1,000 rows to 2,147,483,647 rows On z/os, if PowerExchange loads an IMS DBD multiple times, the PowerExchange Listener might end abnormally with abend code 878. This problem occurs because dynamically allocated buffers for the loads are not freed properly. PowerExchange Known Limitations If you use the DTLURDMO utility to copy capture registrations, data maps, or extraction maps from a source system to a target system and the DBMOVER configuration file on each system specifies SECURITY=1, the user ID and password that you enter for the DTLURDMO utility must be configured on both systems. You cannot specify different user IDs and passwords for the source and target systems in the DTLURDMO control statements. Workaround: Temporarily specify SECURITY=(0,N) while running the DTLURDMO utility, or use the same user ID and password on the source and target systems if possible If you use the Microsoft SQL Server updatetext and inserttext commands to update a TEXT field in a registered table, PowerExchange issues error message PWX The message indicates that PowerExchange does not recognize the update type and cannot capture data for that field. Workaround: Do one of the following actions: Change the datatype of the field from TEXT to VARCHAR(MAX). Edit the capture registration to add the TEXT field, and then remove the TEXT field from the extraction map. IN_RLN_90000_

10 If you use the DTLURDMO utility REG_COPY statement to copy Microsoft SQL Server capture registrations on a 32-bit Windows machine, an unhandled win32 exception might occur in DTLURDMO.exe. This error occurs when the REG_COPY operation tries to use a MODIFY statement that includes the MSSOPTS parameter with the DBNAME option. You can successfully perform this type of REG_COPY operation on a 64-bit Windows system If you restart the PowerExchange Logger for Linux, UNIX, or Windows after a failure, CDC sessions in continuous extraction mode might fail with error message PWX This message indicates that the CAPI returned a sequence token that is not in ascending order or is not of the correct length. This message might also be issued if a CDC extraction session reads a PowerExchange Logger log file twice when extracting part of the data in that file. Workaround: Restart the workflow After you warm start a DB2 for i5/os CDC session with the RESTART1 and RESTART2 override statements set to CURRENT_RESTART in the restart token file, the workflow might end abnormally with error message PWX The message incorrectly reports error code CPF7062. The error is actually caused by a missing sequence token value. Workaround: In the restart token file, enter specific token values for the RESTART1 and RESTART2 statements The PowerExchange Listener might run out of memory because of a problem with storing excessive messages in memory. Workaround: Stop the PowerExchange Listener and then restart it On a Windows 64-bit machine, Oracle connection error messages might be garbled if you use the following code page settings: In the DBMOVER configuration file, the PowerExchange DTLMSG_CODEPAGE, LOG_CODEPAGE, and CODEPAGE statements are set for Japanese. The Oracle NLS_LANGUAGE parameter for the Oracle database is set to Japanese. The NLS_LANG environment variable for the system is set to Japanese_Japan.JA16SJIS. Note: The PowerExchange messages are displayed correctly in Japanese. Workaround: Verify that the Oracle connection information in the DBMOVER configuration file is correct PowerExchange Condense behaves unpredictably based on the file switch criteria in the PowerExchange Condense configuration file. This problem occurs when you set the FILE_SWITCH_IT parameter to M, for minutes, and set the NO_DATA_WAIT2 parameter to a time interval, in seconds, that is a greater than the time interval, in minutes, set in the FILE_SWITCH_VAL parameter. Workaround: If you use minutes as the file switch units, set the FILE_SWITCH_VAL parameter to a time interval that is greater than the time interval that is specified in the NO_DATA_WAIT2 parameter PowerExchange cannot use SSL when running with a Linux 64-bit operating system on an Itanium machine. PowerExchange issues the following error message: PWX Can't read certificate chain file. Key=key PowerExchange is not able to read DB2 for z/os image copies for partitioned table spaces. In this situation, PowerExchange issues the following message: PWX Dictionary Page found. Image copy reading not supported for compressed TS IN_RLN_90000_0003

11 PowerExchange produces a core dump when you use PowerExchange ODBC to access data on the following 32-bit operating systems: SUN SPARC Linux x86 Workaround: Use PWXPC connections instead of relational ODBC connections for PowerExchange access to data. Alternatively, use the Data Direct Version 5.1 driver manager or the Data Direct Version 5.2 driver manager with a patch level greater than Oracle change data that PowerExchange extracts in conjunction with Oracle LogMiner might be incomplete if you run PowerExchange in an Oracle RAC environment. Oracle LogMiner might not extract all change data when performing continuous mining across log sequences that contain points in time where one or more instances have been stopped or started. As a result, the application of change data to target tables can either fail or be incomplete. Workaround: For information about the problem, refer to Oracle bug number or contact Oracle Support for assistance. Oracle supplies patches to fix this problem for Oracle Oracle has incorporated the fix into Oracle and If the lowest level segment in an IMS database is not keyed, the Update all matching segments option on the IMS Options tab of the Table Properties dialog box in the PowerExchange Navigator does not work. Workaround: Do not select the Update all matching segments option if you have non-keyed segments When concatenated key (CCK) fields are passed from IMS to PowerExchange to create SSAs, PowerExchange does not use a lower-level CCK field unless you provide the CCK of the ROOT. The absence of the root key causes unqualified GN calls to scan IMS databases. Workaround: Always specify the key of the root When a DB2 for z/os bulk data movement operation fails, PowerExchange might not write an error message to the PowerExchange message log or PowerCenter session log to notify you of the situation. The PowerCenter session appears to complete successfully. Informatica Analyst Informatica Analyst Known Limitations The Analyst Service on SuSe Linux bit shuts down unexpectedly when you create a flat file data object or import a reference table from a flat file in the Analyst tool and preview the data. Workaround: Use the Developer tool to create the flat file data object and preview the data in the flat file or reference table in the Analyst tool To enable the prebuilt Informatica rules to function correctly when installed to the Model repository, the staging database read by the rules must be named "Staging" and the user name and logon details of the application user must match the staging database connection details The Analyst tool cannot find and replace values on the first string column in a reference table when all columns are included in the Replace All search criteria and if the string being searched contains upper case characters. Workaround: Select a column and search for a string. Or, select all columns and search for a string that contains all lower case characters. IN_RLN_90000_

12 When you create the Analyst Service on a worker node in the Informatica domain, a user cannot log in to the Analyst tool URL because the URL uses the host name for the gateway node instead of the worker node. Workaround: To get the host name for the node, click the link for the Node property in the General Properties for the Analyst Service. In a browser window, enter the correct URL that contains the host name of the worker node The profiling warehouse can store a maximum of 85 Unicode characters (255 bytes) in a column value. If a column value exceeds this number, the value is truncated When you profile a flat file object that contains date data, the Analyst tool displays the date data in the format specified on the local system regardless of the date format in the flat file A operation to copy a reference table can take minutes to complete. An edit made to one copy of the reference table will appear in the other copy during that time Data previews of flat file data do not distinguish between invalid values and valid NULL values. Data preview shows values as NULL in both cases Profiling results do not read the time stamp assigned to a record to sub-second level when generating value frequency data. This can cause the value frequency results to omit data for records with a common hh:mm:ss time stamp Opening the top-level folder in a project can take longer than expected and raise an error The Analyst tool cannot drill down on column patterns in profiles that have UTF-8 data. Informatica Developer Informatica Developer Known Limitations Null pointer exception occurs when you preview a logical data object with an attribute that contains a list of values, a minimum value, a maximum value, or an expression You cannot run a query against a virtual table if the virtual table mapping contains a Consolidation transformation A Match transformation that uses a matching rule to generate identity match scores fails if the identity key field is not used in a matching strategy. The process does not display an error message You cannot run a mapping that contains two side-by-side Match transformations when both transformations are set to identity match mode. Work around: Configure the mapping to run the transformations serially A dual-source identity matching process does not generate match pairs between the master and candidate data sets if the master data set contains one record only The Informatica JDBC Driver does not support the use of SQL escape sequences for date and time literals. Workaround: Override the SQL query and replace the escape sequence with the TO_DATE function IN_RLN_90000_0003

13 A Parser transformation created in token parsing mode may handle parsed values badly if the Reverse Enabled mode is selected. In this case, the transformation may write the first value in a string both to parsed and unparsed output ports. It may also skip the final value in a string The Data Integration Service truncates data when it reads data from and writes the data to a column with a negative scale. Workaround: Change the scale of the target column to Data quality operations run slowly on Solaris. This behavior is observed in address validation and profiling operations Mapping validation does not invalidate a mapping that contains an Update Strategy transformation that is upstream from a Joiner transformation when the Joiner transformation and the Update Strategy are in nested mapplets Matching operations can generate incorrect clusters when non-matching transformations are added to a matching rule. This issue has been observed when a Standardization transformation is added Mapping generates a core file on Solaris 64-bit if you enable Truncate Target Table for an IBM DB2 9.5.x target and you set the number of rows you want to preview to The configuration settings for data quality transformations in mappings deployed to PowerCenter are not visible and cannot be edited The Developer tool may not display the correct drill-down results for a scorecard edited in the Analyst tool. Workaround: After editing the scorecard in the Analyst tool, re-connect to the repository from the Developer tool If you use the same dictionary in more than one transformation in a mapplet or mapping, the dictionary is loaded to memory for each transformation. This can place a burden on the memory available You cannot use Auto Link to connect ports to the Address Validator transformation if the linked ports define an invalid address template. Workaround: Connect ports to a single input port group on the Address Validator transformation. Informatica Developer Documentation Updates User Guide Export to PowerCenter Add the following guideline for exporting to PowerCenter: Verify that PowerCenter is configured with the correct plug-ins. If you export a mapping or mapplet that contains data quality transformations to PowerCenter 8.x, the Informatica Data Quality Integration for PowerCenter plug-in must be installed with PowerCenter. Online Help Address Validator Transformation The Informatica 9.0 online help refers to the Address Validator transformation as the Address Validation transformation. Section updated Jan 15, 2010 IN_RLN_90000_

14 Data Quality Content Installer Data Quality Content Installer Known Limitations The Server Content Installer cannot read a zip file if the path to the file contains one or more character spaces. Section added Jan 15, 2010 Data Analyzer Data Analyzer Known Limitations Data Analyzer displays DB2 AS/400 and DB2 OS/390 as datasource types even though support has been dropped for these databases. Data Analyzer Documentation Updates The Data Analyzer documentation describes how to access data lineage for a Data Analyzer report, attribute, or metric. However, Data Analyzer no longer supports data lineage. Metadata Manager Metadata Manager Fixes Parameter file syntax that is valid in PowerCenter is not valid in Metadata Manager Scrollbars may not appear for Details section when content does not fit Importing a business glossary from Microsoft Excel into a purged business glossary resource fails Command to import XML metadata for a custom resource is available Metadata Manager extracts temporary tables from an Oracle resource IN_RLN_90000_0003

15 Metadata Manager Closed Enhancement Requests When you configure the Universe Inclusion List parameter for a Business Objects resource, Metadata Manager should list the universes in alphabetical order If a mapping parameter is not assigned a value in the parameter file, Metadata Manager should use the default value of the parameter in the mapping. Metadata Manager Known Limitations The Informatica installer does not set the INFA_HOME variable in the MIRSetup.xml file used by the Metadata Manager Agent. Workaround: Edit the MIRSetup.xml file located in the following directory: <InformaticaInstallationDir>\services\MetadataManagerService\mmagentapps\mmagent\conf Replace all instances with the absolute path of the Informatica installation directory If a PowerCenter mapping contains mapping parameters with default values and if session level overrides are provided in a parameter file for the same property, Metadata Manager does not display the session level overrides in the mapping object properties. However, the session level override values are used to display lineage correctly If you concurrently load two resources to a Metadata Manager repository on IBM DB2, Metadata Manager may fail one of the resource loads with the following error: Could not perform post load task. Cause:PreparedStatementCallback; SQL [INSERT INTO MM_ELEMENT_PATH (ELEMENT_UID, REPOSITORY_UID, NAME_PATH, ID_PATH) VALUES (?,?,?,?)]; [informatica][db2 JDBC Driver][DB2]ROLLBACK DUE TO DEADLOCK/TIMEOUT;REASON 2; If you create a business glossary in Microsoft Excel and do not specify the security domain that the data steward user account belongs to, Metadata Manager does not give the data steward user account full control on the business term when you import the business glossary When Metadata Manager runs on UNIX and uses ODBC drivers to connect to a Microsoft SQL Server 2005 source, Metadata Manager fails to load the Microsoft SQL Server 2005 resource with the following error: SQL Error [FnName: Fetch -- [Informatica][ODBC SQL Server Driver]20205] Importing a business glossary Excel file that has terms shared with other business glossaries throws an exception If you import a business glossary XML file and the data steward or owner user account does not exist in the target Metadata Manager instance, Metadata Manager lists the invalid user as the data steward or owner. IN_RLN_90000_

16 When you view data lineage, Metadata Manager occasionally displays the following error: java.lang.illegalstateexception: Cannot create a session after the response has been committed Workaround: Retry the operation For a Microsoft Analysis and Reporting Services resource, Metadata Manager does not extract reports that use a relational database as the data source if the data source path is specified in the Report Server Content property. Workaround: In the Report Server Content property, specify the report folder path instead of the data source path Data lineage does not correctly display Teradata procedures Cannot enable the Metadata Manager Service on a worker node when the worker node is on a UNIX machine and the gateway node is on a Windows machine. The Metadata Manager File Location property for the Metadata Manager Service uses the incorrect file path separator. Workaround: Edit the Metadata Manager File Location property to use the correct operating system file path separator. Restart the Metadata Manager Service On an Oracle repository, Metadata Manager occasionally hangs while creating links between connected resources. Workaround: Analyze the Metadata Manager repository on Oracle to improve performance in the Metadata Manager application If you assign a connection to multiple schemas, Metadata Manager creates links between matching objects for only one schema On a Microsoft SQL Server repository, indexing for an SAP R/3 resource fails with an SQLException when an extracted application component does not have a unique name. Workaround: When configuring the SAP R/3 resource, do not extract application components that have a child or parent with the same name Importing a business glossary XML file fails to import related catalog objects for custom class objects If you import a business glossary XML file and the user that created the links or comments for a business term does not exist in the target Metadata Manager instance, Metadata Manager does not import the links or comments created by the user. Metadata Manager displays that the import succeeds and does not notify you that the links or comments were not imported If you upload more than 200 PowerCenter parameter files, the browser may hang during the file upload process. Workaround: Upload no more than 100 parameter files at a time If a business term property has a string value with more than 4,000 characters, the audit trail does not display the entire value of the property. Workaround: Enter a line break after 115 characters If you create a struct relationship between an object class and a business term class in the Custom Metadata Configurator, you cannot create a field relationship between the business term and another object class type A resource load fails if the associated Integration Service uses the IBM DB2 9.5 client and you load metadata from IBM DB IN_RLN_90000_0003

17 If you change the direction of a relationship for a custom class, Metadata Manager does not update the direction for the relationship between the corresponding metadata objects in the catalog. Workaround: Reload the custom resource. IN_RLN_90000_

18 Contact Information Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Europe / Middle East / Africa Asia / Australia Toll Free Standard Rate Brazil: Mexico: United States: Toll Free Standard Rate Belgium: France: Germany: Netherlands: Spain and Portugal: United Kingdom: Toll Free Australia: Singapore: Standard Rate India: IN_RLN_90000_0003