de 86 releasenotes

7/30/2019 De 86 ReleaseNotes

1/18

InformaticaData Explorer8.6 Release Notes

July 2008

Copyright 2001-2008 Informatica Corporation

Part Number: IDE-86000-0011

ContentsWhats New in Data Explorer 8.6..............................................................................................................1Data Explorer Fixed Limitations................................................................................................................1

8.6 Fixed Limitations ............ ............. ............. ............. .............. ............. ............. ............. ............. .......25.0 SP4 Fixed Limitations ............ .............. ............. ............. .............. ............. .............. ............. ...........35.0 SP3 Fixed Limitations ............ .............. ............. ............. .............. ............. .............. ............. ...........35.0 SP2 Fixed Limitations ............ .............. ............. ............. .............. ............. .............. ............. ...........55.0 SP1 Fixed Limitations ............ .............. ............. ............. .............. ............. .............. ............. ...........65.0 GA Fixed Limitations......................................................................................................................75.0 FCS Fixed Limitations...................................................................................................................11

Data Explorer Known Limitations ............. ............. .............. .............. ............. .............. ............. ............. 13DataDirect Drivers ............ ............. .............. ............. ............. .............. ............. .............. ............. .......13Data Explorer Client............................................................................................................................14Data Explorer Installation....................................................................................................................16Data Explorer Repository ............. .............. ............. .............. ............. ............. .............. ............. .........16Data Explorer Repository Reporting ............ .............. ............. .............. .............. ............. ............. .......17Data Explorer Fixed Target Mapping...................................................................................................18

Contact Information............ .............. ............. ............. .............. ............. .............. ............. ............. .........18

Note: This document contains important information about installation, fixed limitations, and known

limitations for Data Explorer. Do not install or upgrade to this release from a previous version without

carefully reading the relevant sections on upgrading and bug fixes, since bug fixes may change the behavior

of existing software.For more complete information on the product, consult the manuals and online help.

Whats New in Data Explorer 8.6

This release of Data Explorer includes the following new features and functionality:

Usability enhancements. The Data Explorer Client user interface has undergone significant changes to

enhance the user experience.

Flat file importer. The Data Explorer Client features a flat file import utility that operates within the userinterface and that allows users to import flat file data without header information.

Reporting with Data Analyzer. Data Explorer installs a set of repository reports that can be run by

PowerCenter Data Analyzer.

Project versioning. Repository projects now maintain version information for audit trail and genealogypurposes.

Integration with Data Quality. Data Explorer users can export source profiling rules as dictionary files

for use in Informatica Data Quality plans.

Data Explorer Fixed Limitations

This section describes limitations that have been fixed in Data Explorer.


2/18

Page 2 of 18

8.6 Fixed Limitations

CR Description

179298 In cases where a rule reads a table WHERE clause and where a user subsequently updates the WHERE

clause, the rule is not refreshing to use the latest WHERE clause instructions.

178765 UNIX installers encounter file copy issues and raise an error for files odbc.odbc and odbc.ini when thecopy (cp) command is set to interactive.

177265 When a user performs drill-down analysis with the Export Results option enabled on table data importedwith a WHERE clause, the WHERE clause is no applied to the data written to the file.

177175 Drilling down on an INTEGER (n,n) inferred type in column analysis returned incorrect results.

176173 The Data Explorer Client Grid Viewer displays table information only if you have installed Microsoft .NETFramework 1.1 using the Data Explorer installer.

175175 Data Explorer loses connectivity with a project after significant periods of idle time (for example eighthours).

173872 Data Explorer prevents users from creating duplicate domain names but does not generate an error

message if a user attempts to do so.

172002 Attempts to export a project to a repository on Microsoft SQL Server could fail, raising a kernel exceptionerror message. Kernel exception error with Data Explorer client when export a project to repository

Closed

170630 Data Explorer does not recall user changes to default values when the user returns to perform a given

operation.

132187 Crystal Reports repository reports can be utilized in a Microsoft SQL Server environment only. See alsoissue numbers 187859, 187834.

127002 DataDirect 5.2 drivers do not support the import of Microsoft SQL Server tables into Data Explorer on

HPUX platforms.

126998 Bogus error message arises while stopping the Data Explorer Listener on Solaris platforms with the

command /etc/init.d/idelistener stop.

126970 Data Explorer includes only metadata in the copy of the schema and excludes patterns, value

frequencies, inferred datatypes, and sample data from the source schema.

126920 Importing metadata from a Sybase 15 database and performing Empty Column Analysis gives incorrectresults.

126919 A discrepancy arises in the results of Constant Analysis on Sybase 15 and Oracle 9i databases.

126918 Foreign keys are not displayed properly while importing tables from a Sybase 15 database.

126904 Importing metadata from a Sybase 12.5 database results in incorrect display of Doc data type.

126895 Errors arise in column profiling when importing metadata from a DB2 database using native databasedrivers.

126888 A warning message displayed during metadata import from a DB2 8.2 or Microsoft SQL Server database.

126813 Validation of foreign key is not possible with native Oracle database drivers, even though there is aforeign key relationship within the tables.


3/18

Page 3 of 18

126546 Data Explorer returns the following error message when you export a Project to the repository: Can binda long value only for insert into a Long Column.

126420 Error arises while performing drill-down analysis on a Date attribute from a value frequency result.

126408 See 126970.

5.0 SP4 Fixed Limitations

This section describes limitations fixed in Data Explorer 5.0 SP4 (Builds 1170 and Build 1167).

Limitation fixed in Build 1170:

CR Description

181631 When a user attempts to create a new project in Data Explorer 5.0 Service Pack 4 on an AIX 5.3 system,

Data Explorer Server raised an error from which it could not recover and closed without saving work.

Limitations fixed in Build 1167:

CR Description

176608 Auto Save does not work when enabled from the Settings > Options window.

176483 Opening multiple projects in succession causes memory issues in Data Explorer.

176058 Silent Installation for the Data Explorer Client and Data Explorer Server does not work as expected.

176004 Providing Unique Port Numbers for the Axio 4.4 Listener and Data Explorer 5.0 Listener does not ensure

both Listeners are running. If the Axio 4.4 Listener is running, and the Data Explorer 5.0 Listener attempts

to start up, it will fail. Similarly, if the Data Explorer 5.0 Listener is running, the Axio 4.4 Listener will notstart up.

175341 Axio 4.4 provided an option to save profile results displayed in a grid. This is not available in DataExplorer 5.0.

175257 The column profile log does not display sorted column names if more than one column is profiled.

174019 Transformation tags are not persisted through an IROB import. Therefore, the association between atransform object and its parent is lost.

170015 Using the Source Profiler to import Cobol or IMS files results in a parsing error.

169374 Changes to a domain are not reflected in the Properties window unless you save the project and reopenit.

136394 Data Explorer does not persist the alternate data file path provided for a flat file.


This section describes limitations that were fixed in Data Explorer 5.0 SP3.


4/18

Page 4 of 18

CR Description

174711 See 174543.

174666 In Data Explorer 5.0, if you select the Column Value Frequencies option while exporting to a DataExplorer repository, the E01ValFreqPairs table is not populated.

174617 Data Explorer 5.0 does not display correct data when you drill down Inferred key column violations.

174543 On the HP-UX platform, installation fails if you try to install Data Explorer 5.0 on a previous installation ofAxio 4.4.

174530 The Data Explorer 5.0 installation on the AIX platform fails but the message displayed conveys asuccessful install.

172928 In Data Explorer 5.0 SP2, if you do not save changes to a project when prompted and instead use File >

Save to save the project, you will not be able to close the file or exit from the Data Explorer Client.

172462 Mismatch in the row count values returned by the Validate Join and Drill Down feature.

171280 Drilling down on a flat file that contains the documented data type causes an Invalid Where Clause error.

170470 Data Explorer 5.0 crashes if you export to PDF format with a custom Crystal Report.

170099 Saving a project does not save the value in the Reviewed column.

169779 On windows, if you opt not to overwrite the configuration files while installing 5.0 SP2 over an existing 5.0GA or SP1 installation, the 5.0 SP2 version of the axio_server.ini and colprof.ini configuration files are notcopied.

169609 Using Ctrl-C and Ctrl-V to copy an existing object tag to another object causes the text to be pasted twice.

169354 While drilling down on columns, Data Explorer uses the Inferred Data Type instead of the DocumentedData Type thus causing drill down to fail.

169106 If you installed Data Explorer 5.0 SP2 over an existing 5.0 GA or SP1 installation, uninstalling DataExplorer using the 5.0 SP2 uninstaller does not uninstall Data Explorer components but displays the

message that the uninstallation process is successful.

169103 Running the 5.0 GA or SP1 Uninstaller on an installation that has been upgraded to 5.0 SP2 returns anerror.

168904 The installation summary displays the following message if you choose to install UNIX distribution filesonly:

The installation of Data Explorer 5.0 SP2 is finished, but some errors occurred during the install. Please

see the installation log for details.

168577 Opting to restart the system using the Uninstallation Wizard does not work.

168338 The documented data type influences the execution of data rules thus causing the rules to fail.

136392 Data Explorer Source Profiler fails to create the .rst file when the Windows system variables TEMP andTMP do not point to the same path.

136047 Data Explorer Server appears connected even though no connection exists.

135794 Drill Down on a pattern imported using ODBC 5.2 fails if it has a WHERE clause.


5/18

Page 5 of 18

CR Description

133217 Drill down criteria should be set to Between by default. This will allow one to capture all rows matching a

query. The default is currently set to Not Between.

131540 Drilling down on columns that contain non-alphanumeric characters in their name causes drill down to fail

even though they successfully profile.

131378 Foreign Key analysis fails with the unsupported data type error if you use DataDirect Oracle 5.2 drivers.

130521 On the Windows XP platform, if you are using Data Explorer 5.0 with locale set to French, the ImportMetadata window does not display any information.

126295 See 174530.

126949 The results grid viewers refresh multiple times when there are multiple windows open in the Data Explorer

Client.

126149 Find dialog does not search correctly in Logs and Reports. The focus appears to be on the top panel thatcontains the report names but if you select Ctrl+F in the text pane, the search is actually applied to the file

names.



CR Description

136293 When you import a table without a Where Clause and add a Table Where Clause during a drill down,Data Explorer does not retain the Table Where Clause.

136275 The Data Explorer Client returns a JIT exception, when the server process on a UNIX server is stoppedmanually.

135998 When you validate a key or an alternate key and use the Where Clause, Data Explorer does not displaythe results correctly.

135863 Drill down results are incorrect if the user specifies a condition in the text box of WHERE clause.

135709 Drill down on a pattern or inferred data type using double-click does not return the same results as adrill down using right-click.

134370 Data Explorer displays the Validate foreign key window when you validate inferred foreign keys.

134321 The Invalid Value Set criteria in the drill down feature is available even for valid values added to thedomain or column.

134159 The Drill down does not use the Table Where Clause option for creating a rule.

133496 Data Explorer does not display results for the Project Reports on the screen, but displays them in theLog Report Viewer.

133402 When you execute rules on a table, Data Explorer does not disable the Set Datasource option.

133363 On an HP-UX server, Data Explorer displays a JIT debugging window when you scroll through the listof schemas available on the validate redundancy model window.


6/18

Page 6 of 18

CR Description

133055 When you import 100000 rows of sample data on an AIX server, Data Explorer returns the Connection

Lost error message on the Data Explorer Client.

132150 The server license expires if the Data Explorer Client is idle for a long time.

132012 If you abruptly exit from the Data Explorer Client using File > Exit or clicking the X icon on the window,

the client does not shut down properly.

131295 When you create and execute rules for imported data, Data Explorer does not retain the WhereClauses that you use for profiling tables.

126731 When you stop the Listener, Data Explorer does not always stop server processes.

126386 You cannot set a data source when you validate an alternate key.

126149 Find does not work in Log Reports or Repository Reports.



CR Description

130264 Installation Guide has wrong information about running a Data Explorer installation from the commandline argument (silent installation).

127736 When you click Export to Repository to export two projects simultaneously, one action times out or fails.

127734 When you export a project to the Data Explorer repository, there is a difference in performance between

AIX-based Data Explorer Server and Windows 2003-based Data Explorer Server.

127698 Data Explorer does not respond when you double click an Analysis task such as exporting a project tothe repository.

127692 When you select the Export option from the Rule Execution Results grid, Data Explorer exports ValueFrequencies.

127501 When you resize a column from the Midi properties panel (context menu properties panel) or Value

Frequency panel of the properties viewer, the columns overlap.

127496 The Data Explorer Client consumes large amounts of memory even before a user logs on to DataExplorer.

127465 An error occurs if you log in using a port number other than the default port 1416.

127420 When you create a join between two Tables on a single Column, Data Explorer returns the following

warning: No parent columns populated in list.

127285 The Import Sample Data window limits the starting row number to less than 32,769 when you loadsample data.

127022 The size of the windows used to create and edit tags is inconsistent.


7/18

Page 7 of 18

CR Description

127021 When you create a domain, only this domain appears in the Domain List window. The Domain List

window does not list existing domains.

127018 Data Explorer crashes when you create a join without specifying any condition and view the non-

overlapping parent tables without validating them.

127011 If you specify text when creating tags, Data Explorer validates the text.

127010 If you create an Action Item and specify the due date, Data Explorer changes the due date to thesystem date.

127009 An error appears when you click Execute Rule and select the Table and Column names.

127008 When you double-click a dependency from the Model Dependency tab to view the columns in the

Determinant and Dependent lists of that dependency, Data Explorer returns the following errormessage: The named cursor was not found. Additional Information: Cursor #f000040a not found orsupported. Reference Code: e0021003.

126998 Installation Guide has wrong information about Data Explorer listener commands.

5.0 GA Fixed Limitations

This section describes limitations that were fixed in Data Explorer 5.0 GA. To update the three- and four-

digit numbers to the current six-digit CR format, add 125000.

CR Description

1911 Data Explorer does not respond when you try to re-open a project that is already open.

1903 The Uninstall folder is placed in a wrong folder within the Data Explorer installer.

1894

Importing metadata for the first time by setting options for the Owner and Table name results in anexecution error. Following the same steps for a second time renders the Data Explorer Client

inactive.

1887 No message displays to indicate that a maximum of 16000 value frequencies may be loaded.

1876 Executing a single step in the Job Manager causes the remaining steps to be executed.

1867The Execute Rule task displays wrong results when the Select by Object option is selected in theExecute Rule Execute Immediate dialog box.

1855 The Validate Join task displays wrong results and causes the output to be inconsistent.

1853The Value Frequency information does not appear for all values of the Column in the properties

viewer.

1846Right-clicking various analysis options on a closed project results in an unhandled exception and

causes Data Explorer to crash.

1839Connection to the server is lost when executing rule results after adding a condition for drill downand making a rule.

1832 Duplicate inferred datatypes appear for certain Columns after Column profiling.


8/18

Page 8 of 18

CR Description

1831The Value Frequency panel of the properties viewer for a Column refreshes constantly and displays

previously-visited Column values.

1828

When you import an IROB file of a physical view of a project, the logical view of the project appears

instead.

1825 Performing table structural profiling on saved drill down data results in an error.

1824Performing table structure profiling more than once with different options displays only the original

output.

1821 Frequency Analysis does not capture recent changes to source data.

1804 While executing Show Violations, Column headers appear correct but the data is incorrect.

1802 Adding values to a domain results in a memory leak if the value contains an ampersand character.

1801 Adding a particular pattern to a domain results in an unhandled exception.

1787When exporting drill down results, files with duplicate file names are appended with a _1 after the

extension instead of the name.

1783The Midi properties panel (context menu properties panel) and small properties panel do not displaydots for leading or trailing blanks.

1779 Launching Data Explorer 5.0 Source Profiler causes a fatal application error.

1777Deleting a Column from the context menu after performing column profiling results in an unhandled

exception.

1767 Unable to install Data Explorer on Solaris 10.

1764 Column profiling information is not always included when importing metadata to a schema.

1753 The Delete Repository Project dialog box deletes the wrong projects.

1745 Validating an Alternate Key results in an unhandled exception.

1739 The Property icon does not appear in the properties viewer for the Alternate Key and foreign key.

1736 Using the Drill Down option from Source Datatype Analysis task results in an unhandled exception.

1735 Using the Drill Down option from Pattern Analysis results in an unhandled exception.

1733 In the Frequency Analysis results, the Column context menu does not display sub-menu options.

1732 Value Frequency does not capture recent changes to source data.

1727 Column profiling results are invalid if metadata is imported with Profile Columns box cleared.

1726 Adding values to a domain results in a memory leak if the value contains an ampersand character.

1723The Cancel operation does not work as expected while importing metadata and performing drilldown operations.


9/18

Page 9 of 18

CR Description

1721Changing the default options before executing a Validate Join task results in a server error during

execution.

1720 Validating a Key over a particular data set from the Navigator results in an exception.

1719Some of the Data Explorer application icons are not updated under Start > All Programs >Informatica.

1718 Adding transformation tags to Columns results in a server kernel exception.

1703 The context menu options at a Schema level are inconsistent with those at a Table level.

1702Clicking on the header of a Parent Table Column list or Child Table Column list while creating a join

results in an unhandled exception.

1701 Patterns cannot be added to the Domain.

1699

Using the Job Manager to executing jobs on data imported from Oracle sometimes causes

unhandled exceptions.

1698 The context menu options for table structural profiling are confusing.

1697 Using the Make Rule option when drilling down results in an unhandled exception.

1694 The Column context menus in the Navigator and the Properties panel are inconsistent.

1692 The Inferred datatypes context menu is not available from the Properties panel.

1691 The Drill Down option is not available in the patterns context menu.

1688The Drill Down option is not available in the patterns context menu, and patterns do not executewhen double-clicked.

1686 The context menu for tags does not appear when there are no existing tags.

1684 The model dependency Show Violations option displays inaccurate column headers.

1683 The model dependency Show Violations option causes errors.

1678 The Set Domain option does not save the Domain name consistently.

1675 The context menu does not appear in the Tags panel when no tags exist.

1674 Job steps cannot be executed.

1672 Rules cannot be deleted with the Delete key.

1667 Validating a join causes Data Explorer to hang.

1665 The Validate Join option does not display results.

1664 Duplicate and incomplete join properties and details display.

1663 Selecting all values in a value frequency list causes Data Explorer to hang.


10/18

Page 10 of 18

CR Description

1660 UNIX install paths have not been updated.

1659 Domain values cannot be added from another Domain.

1655 Double-clicking a Job in the Navigator does not display required information.

1653Confusing error messages appear when changing the inferred data type of a Column to aninappropriate data type.

1644 An inappropriate physical views grid displays.

1642 The context menu for the Make Synonym option is incomplete.

1641 The 5.2 DataDirect installer appears in the 5.1 folder.

1639 The % Pattern column in the Pattern Analysis window sorts data by characters and not by numbers.

1634 The primary data type displays incorrect Date datatypes in the Overview window.

1629 The Recent Projects menu does not allow selecting from its submenus.

1626 Errors occur when changing the data source path when drilling down on flat file data.

1625 The Toggle Percent option in the Properties window context menu is not functioning.

1624 The context menu in the Properties window allows for adding tags.

1623 Adding a New Rule tag in Sample Data column causes Data Explorer to crash.

1622 The Options General tab does not limit Maximum Value Frequencies to less than 16,000.

1619 The wrong column headers appear in the rule execution results grid.

1618 The Min and Max values in the column profiling display grid do not line up.

1613 The Column name drop down in the Validating Dependencies dialog box too small for large names.

1612 Using the Drill Down Is Not option returns all records.

1611 Duplicate datatypes can appear with different percentages.

1607 Disable value set radio buttons display in the Drill Down Panel even when no value set is available.

1606 Incomplete synchronization when adding Tags to Synonym and Field objects.

1605 Performing Table Structural Profiling with no sample data available causes Data Explorer to hang.

1601 Executing a rule in Tag window does not display results.

1600 Using the Drill Down by Data Type option causes a row count mismatch.

1595 Null strings are not treated as null values.

1582 Editing foreign keys causes an unhandled exception.


11/18

Page 11 of 18

CR Description

1574 Errors sometimes occur when drilling down on sources imported using ODBC drivers.

1572 Errors occur when double clicking on the inferred data type analysis results.

1571 Importing metadata sometimes causes the Data Explorer Server to crash.

1569 The Tags window does not display newly-added tags.

1566 Patterns and values added to the domain are not saved.

1562 Objects are not saved when using the Execute Rule Select by Object option.

1540 Data Source information for the Execute Rule Select by Search option does not load correctly.

1486 Drilling down causes importer processes to launch and does not close them appropriately.

1473 Drill down results do not display consistently.

1376 The online help glossary is empty.

1374 You cannot use the Add button to add an XML driver when using the ODBC administrator for the

DataDirect drivers.

5.0 FCS Fixed Limitations

This section describes limitations that were fixed in Data Explorer 5.0 FCS.

CR Description

1367 Installation Guide has the wrong information on installing Crystal Reports and .NET.

1364 Options set for Column Profiling do not persist.

1363 Tags on Sample Data do not appear.

1362 Drill down results do not display when double-clicking on row.

1361 JRE 1.4 installs twice in the JRE 1.4 directory.

1359 Data Explorer Client hangs after importing sample data and saving the project.

1330 The Data Explorer Listener on some AIX installations generates an incorrect UMI.

1309 Data Explorer Client does not allow you to limit data rule to certain fields.

1299 Running axiobatch does not work on UNIX unless you set the LIBPATH environment variable(documentation updated).

1296 Data Explorer repeats all job steps in a sequence when the user chooses Execute from the contextmenu for a single step.

1295 Installing Data Explorer on AIX is not successful but the installer displays an inappropriatesuccessful message.


12/18

Page 12 of 18

CR Description

1292 Using the administrator login for the Data Explorer Listener web interface, the login is not recognized

until the second attempt.

1290 DDL created by Data Explorer is not accepted by FTM/XML and parsing fails.

1287 After you save a VALIDATE FOREIGN KEY task that includes both a parent and child WHEREclause, the parent WHERE clause overwrites the child WHERE clause.

1285 Job Step Manager does not display a batch program.

1280 If a child job has a WHERE clause but the parent does not, the child WHERE clause is not visiblewhen editing the job (although the child WHERE clause does execute with the job step) and

therefore cannot be removed.

1278 During key validation, Data Explorer ignores the parent WHERE clause and ignores the TableWHERE clause for the child and parent importers.

1277 During key validation, Data Explorer ignores the WHERE clause.

1276 When editing a Job Step for importing metadata, the Job Step Manager selects column profiling

even when it was not selected in the original Job Step definition.

1262 The Repository Reports option appears twice in the Data Explorer Client Windows Start menu.

1257 Documentation directory is inconsistent with other directory names (should be Documentation 5.0).

1255 See CR 1243.

1252 Export to file produces a batch syntax error.

1247 Drilling down on a in the frequency value analysis gives the incorrect WHERE syntax.

1245 A memory leak occurs in the value frequency list after sorting the frequency column several times.

1244 VALIDATE KEY generates incorrect syntax for TABLE WHERE clause when importing metadata.

1243 The definition for the UDB view, EV01OVERLAP, is incorrect because the values are in quotes butthe data type of the fields is numeric.

1242 Data Explorer 5.0 cannot access files on a Windows network directory where the user has full

read/write permissions.

1139 An installation error message occurs when installing or uninstalling DataDirect drivers.

980 Changing a password when the client is disconnected causes the session to be orphaned.

601 When you highlight an existing tag in the Attribute Tag Viewer and press Enter, the tag does notopen for editing.

599 Syntax for the DB2 LOAD Utility format file is out of date with the latest version and causes inputerrors with valid syntax.

487 Changing the password for a newly created user causes user name to disappear and you cannotadd more users.


13/18

Page 13 of 18

CR Description

430 Drill down where there are over 1,000 valid values generates a WHERE clause too large for Data

Explorer to handle.

380 Drill down requests do not return the expected values.

358 Microsoft SQL Server trims blanks in a Varchar column that participates in a key and thereforereports duplicate rejected values when they are not.

Data Explorer Known Limitations

The following limitations may arise when using Data Explorer. If you encounter difficulties or have further

questions about any of these limitations, contact Informatica Global Customer Support and reference the

CR number.

DataDirect Drivers

187515, 136812: HP-UX users w ho expor t a project to a DB2 reposito ry c an lose

con nect ivi ty w ith Data Explorer Server

This issue has been traced to the Data Direct ODBC Drivers. If you experience difficulty with this issue,

contact Informatica Global Customer Support.

187427: Expo rt ing a p roject to a DB2 reposito ry can fai l

This issue has been traced to the DataDirect ODBC Drivers.

Workaround: Use IBM ODBC Drivers.

175950: DataDirect 5.3 ODBC Driv ers are no t compatib le with Solaris 2.6Informatica ships DataDirect 5.2 SP2 and 5.3 ODBC drivers with Data Explorer 5.0 SP3. On UNIX, while

the default ODBC driver installed is DataDirect 5.3, it is not compatible with Solaris 2.6.

Workaround: Use DataDirect 5.2 SP2 ODBC drivers with Solaris 2.6. To configure DataDirect 5.2 SP2

ODBC drivers for Data Explorer, run the following commands:

$ set INSTALLDIR=

$ export INSTALLDIR

$ rm $INSTALLDIR/datadirect

$ cd $INSTALLDIR

$ ln s server500/datadirect52 datadirect

$ cd datadirect

$ cp odbc.ini odbc.ini.orig

$ sed "s:/INSTALLDIR:$INSTALLDIR/datadirect:" odbc.ini

Note: If you are using a shell other than sh, bsh, ksh or bash, the commands will vary. After running theabove mentioned commands, configure ODBC drivers in the new odbc.ini file.


14/18

Page 14 of 18

Data Explorer Client

188025: Attemp ting to edit an enc rypted XML fi le (for example ide_username_86.xml)

usin g the Edit Server File opt io n closes the project with a Netwo rk Communic at ion Error.

187961: Attemptin g to log o n to Data Explorer Server wh ere the Listener is no t runnin g w il l

impede subsequent logon at tempts to a Server whose Listener is running

In this case, the server version information does not display correctly without further user activity, for

example selecting localhost to refresh the server information.

187764: Duplic ate rule is saved un expectedly wh en user saves rule outpu t

When a user creates a rule on a column and runs the rule, Data Explorer prompts the user to retain the

results. If the user accepts the prompt, Data Explorer creates a duplicate rule on the tags.

174782: FTM Schema Manager is no t correct ly parsing Or acle or Micro soft SQL Server

schema du ring 'Imp ort from File' operat ions

The schema encounters problems parsing DDL on these database types.

174174, 174156: Data Explo rer Client does no t handle abrup t disco nnect ion from the

Server graceful ly w hi le working in a project

If connectivity between the Client and Server is lost abruptly, for example by a severed network

connection, any project dialog boxes open at the time of disconnection will display error messages when

acted on by users.

126992: Dri l l down o n Date data type does not disp lay any results wh en you imp ort data

from a flat fi le

If you import data from a flat file that does not contain the date datatypes in the ODBC Canonical format,

then you cannot perform drill down on the date attribute. The Data Explorer Server considers all dates as

similar, as theDrill Down converts all dates into the ODBC Canonical format. If the original format of the

date datatype is not in the ODBC Canonical format, Data Explorer does not display any drill down results.

Workaround:

Change the date data type to String.

-or-

Ensure that the date data type in the flat file is in the ODBC Canonical format.

126948: The Data Explorer Client appears to hang when it is accessing large amoun t of

data for display on the results grid

When the Data Explorer Client accesses large amount of data to display on the results grid, it appears tohang. You can view the data in the results grids after specified time intervals. If you specify large values for

the messaging parameters in the Data Explorer Client Startup settings, the Data Explorer Client displays the

data in the results grids only after it fetches the number of rows specified in the parameters. The DataExplorer Client uses a lot of system memory if the results grids contain a large amount of data. Close the

results grids to release the memory.

Workaround: Set a small value for the number of rows to display for initial read. Data Explorer reads this

number of rows initially and displays the data in the results grid. You can review the data while Data

Explorer fetches the subsequent rows. Set a larger number for subsequent reads so that Data Exploreraccesses the data source at fewer frequencies.


15/18

Page 15 of 18

126930: Data Explo rer returns an un handled except ion w hile adding a values to a dom ain

If you import metadata from a flat file that contains hexadecimal characters and add values to a domain,

Data Explorer returns the following error: System.Xml.XmlException.

If you drill down on data that contains hexadecimal characters, Data Explorer returns the following error:Illegal character found in drill down value. Drill down cannot be executed.

Data Explorer does not support binary and hexadecimal characters.

126891: Import in g metadata from a DB2 8.1 or 8.2 database results in in correct disp lay of

Doc d ata type

Importing metadata from a DB2 database does not display the Doc data type for a column correctly. If theimporter uses the native drivers, it results in the above issue.

Workaround: Use the DataDirect 5.2 DB2 drivers to configure your ODBC connection.

126871: Inval id Do c-Inf data typ e values are reported for som e of th e datatypes

If you import a table using native database drivers and perform Column profiling on the table, the Doc-Inf

data type shows invalid values. For example, if the Integer field shows the Doc data type as NUMBER(*,0)

and the Inf data type as NUMBER(1,0), the Doc-Inf data type shows the value Incompatible. This is

incorrect.

Workaround: Use the DataDirect 5.2 drivers to connect to the database and import metadata.

126808: The Primary Key or fo reign key in an imported Table are not displayed co rrect ly in

the Data Explorer Client

If you import a table with a distinct Primary Key using native database drivers, the Data Explorer client

displays all the columns in the table as Primary Keys.

Workaround: Use the DataDirect 5.2 drivers to configure your ODBC connection and import tables using

the ODBC option.

126799: Inval id results sh ow n for any inferred Date datatype

When you drill down on an inferred Data datatype, Data Explorer displays invalid results which do notmatch with the conforming numbers shown in the panel.

Workaround: Add all the conforming numbers shown in the panel by date to get accurate results.

126771: When a Value Frequency viewer is o pen, the Data Explorer Client does n ot di splay

prof i l ing resul ts of another Column

If you keep the value frequency viewer for one column open and perform column profiling or any other

task on the same table or another table, you cannot view the profiling results. This is a limitation in Data

Explorer.

Workaround:

View the value frequency for the first column in the properties panel.

-or-

Close the value frequency results grid and then perform column profiling or any other task on thesecond table.


16/18

Page 16 of 18

Data Explorer Installation

188085: UNIX GUI instal ler does n ot set L istener port number

The GUI mode installer does not set the Listener port number. To set this number post-install, edit the

ide_server.ini file as described below.

y Verify that the Listener is not running.

y In the listener.ini file, set the port number in the ListenerPort parameter.

y In the ide_server.ini file, set the port number values for the IDE_ELMPORT andIDE_LISTENER_PORT parameters. Remove the quotation marks from these parameters.

y Re-start the Listener.

188080: UNIX Conso le mod e instal ler does not set Listener po rt number correct ly in al l

cases

The UNIX Console mode installer sets the port value to 1416 and does not provide an option to set a non-

default value. To set a non-default value, follow the steps below:

y Verify that the Listener is not running.

y In the ide_server.ini file, set the port number values for the IDE_ELMPORT andIDE_LISTENER_PORT parameters. Ensure that quotation marks do not enclose the parameter.

y Re-start the Listener.

188079: Data Explorer Client do es no t recogn ize a Data Explorer Server on UNIX wh en a

non -default Listener port num ber is def ined

This issue arises because the port number values for these variables are enclosed in quotation marks in theide_server.ini file, as follows:

IDE_ELMPORT="1500"

IDE_LISTENER_PORT="1500"

Workaround: Remove the quotation marks for these parameters in the ide_server.ini file.

187765: Unin stal l ing Data Explorer Client on a Microso ft Vista machine m ay generate a

bogu s error message

Performing a client uninstall generates an error stating that the process was unable to un-install ODBC

drivers. This error message arises when Java is not recorded in the system path. The uninstall process

completes regardless of this error message.

187534: Unin stal l ing Data Explorer 8.6 from a Window s mach ine that also ho sts an earl ier

version of Data Explo rer also unregisters the L istener of the earl ier version

On a Windows machine that hosts both Data Explorer 8.6 and an earlier version of Data Explorer, the

uninstall of version 8.6 does not leave a running Listener for the earlier version. The user must manually re-

register the earlier Listener service.

Data Explorer Repository

187501: Batch comm and to d isplay versioned projects returns no data

The following command returns a blank line:

show versioned ide repository project names;


17/18

Page 17 of 18

The command to show details from a versioned project works without incident.

126297: SAP colum n names are too long for o lder version s of the Data Explorer reposito ry

SAP column names are too long to store in the repository in older versions (before 4.3) of Data Explorer.

If you need to access an old repository version, contact Informatica Global Customer Support.

Data Explorer Repository Reporting

188581: 'Column Tags Summary by Colum n Coun t ' repo rt malfunct ion s on f i l ter update

wh en PowerCenter Data Analyzer reads data from a SQL Server or Oracle database

When running a Data Analyzer report on a Microsoft SQL Server or Oracle data source, if the user edits the

report and tries to update the value for the 'Test_Project' attribute filter, Data Explorer does not complete

the operation and generates an error message.

Workaround for Oracle data source users: fully remove the filter and recreate it. The report will display

correctly.

187859, 187834: Crystal Reports mu st use rep osito ry sch ema ide_repo

The Crystal Reports installed with Data Explorer will fail to run if the Data Explorer repository is createdon a schema with a name other than ide_repo. This issue is observed in cases where Crystal Reports has

been installed through Data Explorer and no other installation of Crystal Reports is present.

187852: Select ing attr ibute values for a versioned pro ject raises an error in Data Explorer

Client

This issue has been observed with a DB2 Data Explorer repository. It arises when the following two Data

Analyzer reports are run and the user selects the option to show attribute values for a versioned project:

y Column pattern trend

y Column profile trend

187575: Tag reports may raise errors w hen run on a DB2 database

187429: Data Analyzer reports d o not run succ essfu l ly from a Sybase repository

When a user hosts a Data Analyzer instance and assigns a Sybase Data Explorer repository as the data

source, the installed Data Analyzer reports do not run successfully. When the user runs a report, the results

are not generated, and the view names and corresponding column names in the report query are capitalized.

187351: Data Analyzer repo rts opened from pu blic folders may thro w except ion s wh en

reading from a Microso ft SQL Server source

In this scenario, opening the following two reports from 'Public Folders > Informatica Data Explorer >

Column Profiling' throws a NullPointerException:

Top 10 Most Frequent Values

Bottom 10 Most Frequent Values


18/18

Page 18 of 18

Data Explorer Fixed Target Mapping

187825: Repo sitory p rojects do no t display when conn ect ing to an Oracle repository u sing

DataDirect ODBC 5.3 dri vers

When a user connects to the Data Explorer repository using Data Explorer FTM with Oracle Data Direct

5.3 drivers, the projects stored in the repository are not visible.

Workaround: Connect to the repository using Data Explorer FTM with Oracle Native Drivers.

Contact Information

There are many ways to access Informatica Technical Support. You can contact a Customer Support Centerthrough telephone, email, or the WebSupport Service.

Use the following email addresses to contact Informatica Technical Support:

y [email protected] for technical inquiries

y [email protected] for general customer service requests

WebSupport requires a user name and password. You can request a user name and password athttp://my.informatica.com.

Use the following telephone numbers to contact Informatica Global Customer Support:

North America /South America

Europe / Middle East / Africa Asia / Australia

Informatica CorporationHeadquarters

100 Cardinal WayRedwood City, California94063United States

Toll Free+1 877 463 2435

Standard RateBrazil: +55 11 3523 7761

Mexico: +52 55 1168 9763United States: +1 650 385 5800

Informatica Software Ltd.6 Waltham Park

Waltham Road, White WalthamMaidenhead, BerkshireSL6 3TNUnited Kingdom

Toll Free00 800 4632 4357

Standard RateBelgium: +32 15 281 702

France: +33 1 41 38 92 26Germany: +49 1805 702 702Netherlands: +31 306 022 797

United Kingdom: +44 1628 511 445

Informatica Business SolutionsPvt. Ltd.

Diamond DistrictTower B, 3rd Floor150 Airport RoadBangalore 560 008

India

Toll Free

Australia: 1 800 151 830Singapore: 001 800 4632 4357

Standard RateIndia: +91 80 4112 5738

de 86 releasenotes

Documents