Oracle® Enterprise Data Quality

Release Notes

12c (12.1.3)


May 2014

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

Oracle recommends you review its contents before installing or working with the product.

1 New Features and Improvements

The following sections describe the new features introduced in this release as well as improvements.

1.1 DIR-13825: Oracle Access Manager Integration

EDQ can now be integrated with Oracle Access Manager.

1.2 DIR-12459 - Document Handled XML Format

New documentation has been added to describe the ability of EDQ to read in and write out XML data. See ”Configuring EDQ to Process XML Data Files” in Oracle Fusion Middleware Integrating Enterprise Data Quality With External Systems.

1.3 DIR-13870 - Improvements To Director When Working With Databases With Many Tables.

Improvements have been made to the snapshot, external reference data and export wizards so that they work better with databases with large numbers of tables. In the snapshot wizard, it is now possible to switch to the SQL view or enter a table name before the list of tables is loaded. The list of tables can also be filtered in all wizards.

1.4 DIR-13871 - Ability To Write To Reference Data

It is now possible to write to Reference Data sets in a process that is configured in Director. This works in the same way as writing a Staged Data set. For more information, see the Reference Data help topic in Director.

2 Bugs Resolved

The following sections describe the bugs resolved in this release.

2.1 BugDB # 18118843: Attribute Names Automatically Renamed In EDQ Merge Attributes Processor

Outputs were being automatically renamed when attributes were moved. This has been fixed.

2.2 BugDB # 17202807 - UI Results Browser Shows Database Error When There Is No Underlying Data

When selecting a process for which there was no results data, the Director Results Browser and the logs displayed a database error, rather than an appropriate message. The message ”The process needs to be run before viewing results” is now displayed, and no error is written to the log.

2.3 BugDB # 17085911 - Job with Multiple Snapshots Does Not Unlock After Failing A Second Time

If a job had multiple data stores connecting to multiple data sources and one of the data stores pointed to a non-existent file, the job failed. However, when the job was run a second time, there was an error, and a third attempt to run the job produced a ”Job still running” message. The only way to resolve this problem was to restart the application server. Now, when such a job is rerun, the locks are released and it starts.

2.4 BugDB # 16536222 - Add Case Key Checker To The Pre-Migration Step Prior To CM Migration And Upgrade

The Case Management premigration check script did not detect a problem that caused the migration of the key to fail, thus causing the entire upgrade to fail. To resolve this, a key migration checker was added to the premigration script.

2.5 BugDB # 13623253 - ”Username/Password Incorrect” Message When Results/Director Services Are Down

When the Results and Director services were not running and Director was launched, the login screen returned a ”username/password incorrect” message, even though the credentials were valid. The message ”'Server configuration error” is now displayed in this case.

3 Known Issues and Workarounds

The following sections describe known issues and any workarounds that exist in the 12c (12.1.3).

3.1 BugDB # 18281806 - Dashboard Publication Not Working From Compound Processors

There is a known issue where Dashboard publication does not work correctly from compound processors. For example, a configured audit check that is selected as the Dashboard member processor and then configured at the parent level (with Dashboard publication on) always publishes its results with 'No data to display'. However, the same processor works correctly if publishing outside of the compound processors.

3.2 BugDB # 18473996 - Incorrect Summary Values In Dashboard

There is a known issue where index values on Dashboards are calculated as expected until the number of values reaches 16,500. After that number of values, the Dashboard displays negative values.

3.3 BugDB # 18287262 - Wrong Error When Process Writes Reference Data That Breaks Uniqueness Constraint

There is a known issue where a misleading message is returned if data that is written to a reference data set violates a uniqueness constraint. The message ”process is not valid for running” incorrectly implies that there is a problem in the process design, rather than a uniqueness violation.

4 Upgrade Considerations

The following are some of the major considerations for upgrading to 12c (12.1.3).

4.1 Upgrades in an Oracle WebLogic Server Environment

  • Read Planning an Upgrade of Oracle Fusion Middleware for guidelines for preparing to upgrade to Oracle Fusion Middleware 12c (12.1.3). 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 or later and was installed with Oracle Universal Installer (OUI), you can use the Upgrade Assistant to upgrade your installation directly to 12c (12.1.3). If your version of EDQ is earlier than Release 11g (, you must first upgrade your software to at least version, and then upgrade that environment to 12c (12.1.3). To upgrade to version, see Oracle Enterprise Data Quality Installation and Upgrade Guide Release 11g R1 ( at

  • 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.

To upgrade to 12c (12.1.3), see ”Upgrading EDQ On WebLogic Servers” in Oracle Fusion Middleware Installing and Configuring Enterprise Data Quality.

4.2 Upgrades in an Apache Tomcat Environment

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

To upgrade to 12c (12.1.3), see ”Upgrading EDQ On Tomcat Servers” in Oracle Fusion Middleware Installing and Configuring Enterprise Data Quality.

5 Related Documents

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

EDQ Documentation Library

The following publications are provided to help you install and use EDQ:

Find the latest version of these guides and all of the Oracle product documentation at


Online Help

Online help is provided for all Oracle 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.

6 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit or visit if you are hearing impaired.

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


Copyright © 2013, 2014, 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, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

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 on 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. 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.