Oracle® Enterprise Data Quality

Release Notes

12c (12.2.1.4.0)

E95653-01

September 2019

Oracle Enterprise Data Quality Release Notes

This document contains release information for Oracle Enterprise Data Quality (EDQ) 12c (12.2.1.4.0) and includes the following sections:

Oracle recommends you review this document before installing or working with the product.

New Features and Improvements

This section describes new features introduced in this release, as well as improvements.

Call External Web Service Processor

For this release EDQ offers a new processor called Call External Web Service which takes input data, configuration information, request payload and parses web service responses as the processor output. This processor makes it easier to call external REST web services within EDQ processes.

For more information, see the Call External Web Service section of Oracle Enterprise Data Quality Online Help .

Cassandra Data Store

A new data store is available to enable reading data from, and exporting data to, Cassandra databases.

Multiple Value Reference Data Editing

This release enables multiple value editing of Reference Data entries, to improve productivity when editing reference data, especially for standardization and product data classification purposes.

New REST API Documentation and Testing capabilities

New documentation of EDQ’s REST APIs is available from the EDQ Launchpad. The new documentation gives details and examples for all services, and a built-in testing facility. The ‘fixed’ services to manage EDQ configuration and jobs are documented under Web Services – REST API Specification, and the dynamic services, built by configuration, are documented under Web Services – Web Services - Web Services REST Endpoints.

Deprecation Notice

Rhino (the JavaScript Engine) was deprecated in release 12.2.1.0.0, and will be removed in the next major release of EDQ. Custom scripts that use the E4X functionality of Rhino (which is often used to construct XML), for example to call an external web service, should if possible be rewritten after upgrade to EDQ 12.2.1.1.0.

Issues Resolved

This section describes issues resolved in this release.

Table - Issues Resolved

Issue Notes

Case management reports with aggregations are not consistent with the drilldowns

Issues of consistency and overlap in some reports were noted. These issues have been fixed in this release.

Event log 'EventId' column removal can cause EDQ 9.0 upgrade issue

Users of version 9 of EDQ may have selected all event log columns (including EventId) for display and saved this selection.

EventId is no longer used, and users of previous releases reported that trying to load an event log that contains the extra saved column caused the application to shut down.

That condition has been fixed in this release.

Client/Server Timezone issues when using filters in Case Management

Conflicting time stamps (server versus client) have been resolved.

Unable to open 'Extract Building Identifier' parser in CDS Standardize Address

Loading symbol data was causing Director to run slowly in some circumstances. The issue has been resolved.

Vertical Data view in Case Management not appearing

An issue preventing proper display of Alerts in the vertical view was fixed in this release.

Incorrect key generation export name in CDS run profile

An incorrect key generation export name was discovered and fixed in this release.

IndexOutOfBoundsException error on job email icon with duplicate user display names

Duplicate display names were causing an error to be displayed when users clicked the job email icon. The issue has been resolved in this release, and job notification emails are generated without error.

WebService publishing fails if HTTPS is enabled but HTTP is disabled

An error occurred when EDQ's managed server was configured so that the main listen port was disabled but the SSL listen port was enabled. This issue has been resolved in this release.

Re-enable On-line Help for non-English languages

In a previous release, the online Help was available only in the English language. It is available in 10 languages (including English) in this release.

Match options for data-only from contributing comparisons are not saved

It was discovered that the match options for Data from only contributing comparisons and Data from only contributing compound comparisons were not being saved. It has been corrected in this release.

Download task does not support HTTPS through a proxy server

Using an HTTPS URL in the download task was causing an error when the task passed through a proxy. This issue has been resolved in this release.

Flag Key changes not reflected during Case Source import

An issue was reported in which Flag Key changes were not visible after import. The issue was resolved in this release.

Match cluster limit warnings rendered incorrectly in HTML job log report

An issue in which Match cluster limit warnings were being incorrectly rendered in the Event Log Job Messages HTML output has been corrected in this release.

Correct error status not returned when running runjob

Error status was not correctly reported (no error returned) when running runjob. This issue has been fixed and errors are now reported correctly.

E-mail notification does not support SMTP authentication

An issue was reported in which the email notification function did not work when an SMTP server requiring authentication was used. The defect has been addressed, and notifications are working properly in this release.

File uploads do not work with built-in SFTP server

When connecting to the internal SFTP server, file uploads were returning an error (Couldn't get handle). The issue has been fixed in this release.

Length of keys generated in batch can exceed staging table column size

An issue was reported (in Customer Data Services Pack) in which errors occurred when the length of keys generated by EDQ exceeded the width of the table column. The keys are now truncated to address this issue.

Case Management Reports use all values that exist, rather than those in filter

Case Management Reports were erroneously including placeholders (rows/columns) for values not called for in the filter, in addition to the data called for in the filter. This issue has been fixed in this release.

Case Management temp files not deleted until server restart

Temp files were previously being retained until the server was restarted, at which time the temp files were deleted. The application has been updated so that the temp files are cleared when the application is closed.

Issue email notifications do not work if an LDAP userdisplayname is configured

The presence of userdisplayname was interfering with issue email notification. The issue has been resolved, and the presence of userdisplayname does not cause any problems.

Job email notifications do not work if an LDAP userdisplayname is configured

The presence of userdisplayname was interfering with job email notification. The issue has been resolved, and the presence of userdisplayname does not cause any problems.

Excel exports from Case Management reports with aggregations contain <nobr> tags

<nobr> and </nobr> tags were appearing in some Case Management reports exported to Microsoft Excel. This issue has been resolved.

One-way web service returns 'unresolvable error' with webservice tester

When testing a one-way web service using the webservice tester, an error message appeared (unresolvable error). This release includes the fix to this issue.

Configuration Analysis generates a null pointer exception when comparing jobs

An issue was reported in which users received null pointer exceptions when using Configuration Analysis when comparing jobs. This release addresses the issue and it is no longer observed.

Case Management 'State Changed By' filter on user Display Name does not work

When creating a filter using State Changed By, users can now filter users based on their Display Name.

Lucene index update is not committed for user updates of individual cases

Users reported not being able to search on attributes updated in Cases or Alerts until a re-index was performed. Functionality was updated to enable searching on updated attributes without having to re-index.

Option to log Case Management report requests for debug purposes

To provide additional debug logging of all user Case Management report requests:

  1. Access the following new EDQ mbean in JConsole on a running EDQ server:

    edq | Logging | Case Management Filter Execution

  2. Invoke the setLevel operation with a value of FINE.

    Whilst not recommended, this setting can be made permanent by adding the following line to logging.properties and restarting EDQ:

    com.datanomic.director.casemanagement.search.level = fine

Prevent running of very large Case Management reports to avoid memory problems

By default, attempts to run Case Management reports in which either axis contains more than 1000 entries will be rejected, and an error message displayed. The size of this limit is configurable, and can be set using the following new parameter in override.properties, for example to change it to 5000:

casemanager.maxReportWidth = 5000

Some CM reports with a date field with a week granularity will never finish

An issue has been reported in which running CM reports with a granularity of week caused looping that would not allow the report to be completed. This issue has been resolved in this release.

Known Issues and Workarounds

This section details known issues in this release, and their workarounds.

Opening Server Package File in Apple OSX Causes Error

An issue has been reported in which a user right-clicked on the Server node in the Project Browser (in Director) to open a Server Package file, and received a null pointer exception. This issue is being addressed. In the meantime, opening Server Package file can still be accomplished in the following ways:

  • File > Open Package File. Then navigate to the Dxi file containing project elements and import the file. This can then be copied into the Project Browser.

    Or

  • Drag and drop.

Upgrade Considerations

This section details major considerations for upgrading to 12c (12.2.1.4.0).

Upgrades in an Oracle WebLogic Server Environment
  • Read for guidelines for preparing to upgrade to Oracle Fusion Middleware 12c (12.2.1.4.0). This documentation also includes descriptions of terminology changes that you must understand to move forward to a 12c environment.

  • If your current EDQ version is 11.1.1.7 or later and was installed with Oracle Universal Installer (OUI), you can use the Upgrade Assistant to upgrade your installation directly to 12c (12.2.1.4.0).

  • All EDQ components must be shut down and remain stopped until you are prompted to start them at the end of these upgrade instructions. The WebLogic Server console must remain running until you are prompted to shut it down during the upgrade procedure.

For all upgrade scenarios, see Upgrading Enterprise Data Quality in Installing and Configuring Oracle Enterprise Data Quality guide.

Upgrades in an Apache Tomcat Environment

You can perform a direct upgrade to version 12c of EDQ only from Tomcat version 8. If you are running an earlier version of Tomcat, you must upgrade Tomcat to version 8 before proceeding with the EDQ upgrade. See the Apache Tomcat documentation at

http://tomcat.apache.org

To upgrade to 12c (12.2.1.4.0), see Upgrading Enterprise Data Quality in Installing and Configuring Oracle Enterprise Data Quality guide.

Related Documents

For more information about EDQ, see the following documents in the Enterprise Data Quality documentation set.

EDQ Documentation Library

Online Help

Online help is provided for all Enterprise Data Quality user applications. It is accessed in each application by pressing the F1 key or by clicking the Help icons. The main nodes in the Director project browser have integrated links to help pages. To access them, either select a node and then press F1, or right-click on an object in the Project Browser and then select Help. The EDQ processors in the Director Tool Palette have integrated help topics, as well. To access them, right-click on a processor on the canvas and then select Processor Help, or left-click on a processor on the canvas or tool palette and then press F1.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Accessible Access to Oracle Support

Oracle customers who have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Conventions

The following text conventions are used in this document:

Convention Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.


Oracle Enterprise Data Quality Release Notes, 12c (12.2.1.4.0)

E95653-01

Copyright © 2018, 2019, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.