Oracle® Enterprise Data Quality for Product Data

Release Notes

Release 11g R1 (11.1.1.6)

E29149-05

March 2014

This document contains the release information for Oracle Enterprise Data Quality for Product Data (EDQP) Release 11g R1. It describes both documented functionality of this release and differences between prior releases.

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

1 EDQP Release 11g R1 11.1.1.6.2

Various bugs and issues fixes were implemented in the 11.1.1.6.2 release.

2 EDQP Release 11g R1 11.1.1.6.1

This section details the 11.1.1.6.1 release.

2.1 Bugs and Issues Resolved

The following sections describe the bugs and issues that are resolved in this release.

2.1.1 BugDB # 16030742:

SPECIAL CHARACTER IN DSA DESCRIPTION STEP CAUSES DSA TO NOT LOAD

To correctly display UTF-8 non-Latin characters in the Oracle DataLens Administration Server web page, you must configure your Oracle Database or PostgreSQL Database to use UTF-8 encoding. Otherwise, some characters may not be rendered correctly due to encoding differences.

2.1.2 BugDB # 16232093:

OFFICE 2010 PROFESSIONAL 64-BIT SERVICES FOR EXCEL INSTALL NOT RECOGNIZING EXCEL

On clients running Office 2010 Professional 64-bit, it is possible that Services for Excel does not get installed using the AutoBuild button on the launch pad. This is because the Excel installation is not being recognized.

2.1.3 BugDB # 15966752:

STAT MATCH DIALOG SHOWS INCORRECT INDEX NAME

The Stat Match widget was updated so that the index selection, based on the database connection selection, is correct. In the previous version, if there were multiple database connections, changing the database connection selection resulted in the indexes associated with the connection being displayed, without updating the index selection.

2.1.4 BugDB # 14463522:

LARGE PACKAGE CHECK INS WITH MANY LENSES FAILS WITH TIMEOUT ERROR

When checking in a large DSA package containing numerous data lenses, it is possible that communication with the Oracle DataLens Server will time out and the check in does not complete. Adjusting the WebLogic Server Java Transaction API (JTA) timeout value to 3600 seconds allows the DSA package enough time to check in the entire package and complete this DSA job.

2.1.5 BugDB # 16068819:

DATA LENSES NOT GETTING LOADED ON PRODUCTION AFTER PACKAGE PROMOTION UNTIL SERVER RESTARTED

When a data lens is selected for loading by a user for a particular server from the Administration web page, and a Transform Server is sent a message to load that data lens, the Transform Server may have already downloaded that data lens following a deployment operation and so believes there is no need to load that data lens. On both the Administration and Transform Servers, additional information about which data lenses have been loaded was added to correct this issue.

2.1.6 BugDB # 15880161:

ADD POSTGRESSQL AS A DATABASE TYPE FOR AN OPERATIONAL CONNECTION TYPE

PostgreSQL Version 9.2.2 has been added as a database type that can be used as an Operational database connection type.

2.1.7 BugDB # 15974800:

MAX ROWS IS WRONG FOR OFFICE EXCEL 2010 32-BIT

When running jobs from Excel worksheets that contain more than 80,000 rows, Excel stops responding after the "Transmitting Records to the Server" message is displayed. The jobs complete and are indicated as completed in Job Status pane of the Administration web page. Services for Excel was updated to correct this issue and properly process worksheets in excess of 80,000 rows.

2.1.8 BugDB # 15873178:

SERVICES FOR EXCEL INSTALLATION INTERFERES WITH USER'S ABILITY TO OPEN EXCEL FILES

When opening Excel and an Excel file by double-clicking on it, Excel starts but the file is not opened. This is a known issue with the Excel application and can be corrected by following the instructions at the Microsoft Support Web site at

http://support.microsoft.com/kb/211494

2.1.9 BugDB # 14787983:

SERVICES FOR EXCEL INSTALL NEEDS REMOVE ALL TRANSLATION FILES IN PROPERTIES FOLDER

Services for Excel was updated to remove all of the translation files in the properties directory because legacy translation files in this directory cause errors when Excel is started due to missing or invalid string ids. The installer for Services for Excel now automatically removes these files as part of the removal of previous versions.

2.1.10 BugDB # 14532068:

FOR IMMUTABLE ORACLE HOME REQUIREMENT INSTALL CONFIG FILES TO SEPARATE DIRECTORY

All system run-time configuration files are now placed in the EDQPdomain directory For example, C:/Oracle/Middleware/user_projects/domains/dls_domain/pdq where the pdq directory contains all of the application run-time configuration files including files that are updated at run-time.

2.1.11 BugDB # 14733024:

KB FOLDER IS MISSING ON CLIENT SITE IN 11G

The kb and xmlsupport directories in the EDQP_HOME/system were not built correctly in the EDQP client application Java WebStart jar files. The jar files have been corrected to contain the correct kb and xmlsupport directories. The event is reported in the job status with the warning that the state change will not be saved.

2.1.12 BugDB # 14414901:

COMBINE THE 32-BIT AND-64 BIT SERVICES FOR EXCEL INSTALLATIONS

Services for Excel/Autobuild is now installed from the AutoBuild button on the Web Admin launchpad. There is now a single button for both the 32-bit and 64-bit installations. Services for Excel will install the version that is appropriate for your computer.

2.1.13 BugDB # 14641385:

JAVA API FAILED FOR INVALID USER IDS

The access to the user management using the Java API changed in 11g and requires a valid user id when the DeployedListRequest call is made. This causes an exception error when a valid user id is not provided; this was not necessary in previous releases.

2.1.14 BugDB # 14727139:

CLIENT MISSING SYSTEM/KB FOLDER

See Section 2.1.11, "BugDB # 14733024:."

2.1.15 BugDB # 14780607:

KB FOLDER IS MISSING ON CLIENT IN 11G; ALSO THE XMLSUPPORT

See Section 2.1.11, "BugDB # 14733024:."

2.1.16 BugDB # 14775546:

NULL POINTER EXCEPTION - PHRASE/TERM IMPORT IN KNOWLEDGE STUDIO

Using Java 7 Update 6 and greater, when you attempt to import a phrase/term import Excel worksheet with fullform column entries that have unsupported characters, and then choosing to expand the fullform into variants, a Null Pointer Exception error occurs. The NPE has no stack trace. The comparison functionality has been improved to correctly handle the unsupported (null) characters.

2.1.17 BugDB # 14770351:

PREVENT HEAP OVERFLOW CREATED BY JAVA 1.7_06 CHANGE IN STRING IMPLEMENTATION

Java 7 Update 6 modified the implementation of String such that the new String created by substring() no longer uses a backing store to the original string, which saved to integers, resulting in a heap memory overflow condition.

The use of string tokens was updated so that if the original string is needed for basic functionality or debugging a reference of the string is passed correctly.

2.1.18 BugDB # 14651303:

GATEKEEPER HUNG AND STUCK THREAD AFTER DATA LENS DEPLOYMENT

The 'gatekeeper' is the mechanism that ensures that a data lens is not replaced while it is being used in a running job and queues up the requests waiting for jobs to finish that use the data lens.

When running jobs with a data lens that appears to be deployed, it is possible for the job to stop responding as a result of a stuck thread related to the data lens deployment.

The gate keeper data lens deployment functionality has be refined to improve synchronization. However, should this issue occur, you must restart your Oracle DataLens Server.

2.1.19 BugDB # 14686582:

KNOWLEDGE STUDIO - KB.CFG FILE IS MISSING IN PROJECT FOLDERS

See Section 2.1.11, "BugDB # 14733024:."

2.2 Known Issues and Workarounds

The following sections describe known issues and any workarounds that exist in the 11g R1 (11.1.1.6.1) release.

2.2.1 BugDB # 16249956:

SERVICES FOR EXCEL IS NOT GETTING LOADED IN EXCEL 2003 AFTER SUCESSFUL INSTALLATION

Services for Excel may not appear in Excel 2003 on a 32-bit Windows 7 system after a successful installation. This is a result of a problem with the 32-bit Microsoft Office 2003 Primary Interop Assemblies (PIA); the necessary .Net Programmability Support is not being installed. This is a known issue. You can correct this issue by downloading and installing following the Microsoft Office 2003 PIA using the instructions at the Microsoft Download Web site at

http://www.microsoft.com/en-us/download/details.aspx?id=20923

2.2.2 Upgrading Errors

When upgrading from 11.1.1.6.0 to 11.1.16.1 the following error occurs and can be ignored:

<Jan 16, 2013 1:43:37 PM MST> <Error> <oracle.pdq.server.svr.util.AutoDeployer
<BEA-000000> <AutoDeployer could not find user. Please set up a user in System A
dmin user as System User String Constants using EDQP admin>

This does not affect the ability to AutoDeploy.

3 EDQP Release 11g R1 11.1.1.6.0

This section details the 11g R1 11.1.1.6.0 release.

3.1 Bugs and Issues Resolved

The following sections describe the bugs and issues that are resolved in this release.

3.1.1 BugDB # 11931385:

PROVIDE OPTION TO USE THE ORIGINAL CATEGORY NAME CASE FOR THE ITEM DEF NAME

In the first step of the AutoBuild Wizard there is now an option to use the original category case for naming item definitions. This option to use the original category name case for the item definition name, including both case and punctuation, can be selected from the item definition comment field.

3.1.2 BugDB # 13650593:

FULL FORM VARIANTS FOR YES VALUE SET VALUE IS DIFFERENT THAN FOR NO VALUE

Improved rule creation for attributes with Yes/No valuesets.

3.1.3 BugDB # 12582367:

MOVE THE VERSION REPOSITORY AND THE SHARED DATA INTO THE DATABASE

Move the data service application (DSA) and data lens version repository from shared disk configuration into the database. This eliminates the need to create a common network file system mount between servers and improves reliability.

3.1.4 BugDB # 10280191:

MOVE THE THREAD POOL SIZE FROM SERVER.CFG TO SERVERPROFILE

Move the thread pool size from server.cfg to ServerProfile.xml. Thread pool size can now be set from the server group configuration page on the Oracle DataLens Server Administration web page. This ability to tailor the thread pool size is especially helpful in situations where other applications are running within the same environment groups, such as Fusion PIM.

3.1.5 BugDB # 13470112:

SETTING MAX REVISIONS FAILS TO DELETE THE OLDER LENS VERSIONS

If number of revisions > maximum revisions, then the oldest revisions are deleted upon check-in of a new revision or server restart. By design, the currently deployed version does not get deleted.

3.1.6 BugDB # 9731895:

5544-PT: ENHANCEMENT - MOVE DEPLOYMENT AND USER LOCK INFORMATION TO THE DATABASE

Included capability to report on who has locked each DSA and data lens, last check-in date, area deployment information. This information is presented in the Oracle DataLens Server Administration web page.

3.1.7 BugDB # 10157721:

GATEKEEPER DEADLOCKS ON MULTIPLE DEPLOYMENT REQUESTS IN RAPID SUCCESSION

Fixed deadlock issue that occurs when a user attempts to deploy and promote a data lens several times in rapid succession. The gatekeeper can deadlock, causing many Lens Load Request Queued messages to appear in the server log.

3.1.8 BugDB # 14389931:

SHIFTJIS ENCODING CAUSING JOB RESULTS TO NOT BE RETURNED

Fixed the method that either corrupts or removes non-ASCII /ISO characters from the job input, which caused results to not be returned.

3.1.9 BugDB # 13649642:

AUTOBUILD SHOULD ESCAPE XML DELIMITERS BEFORE RUNNING XPATH QUERIES

AutoBuild allows XML delimiter characters in meta-data category codes (as well as, other places), including single quotes, double quotes, and angle brackets ('"<>). These XML delimiter characters should be escaped with proper XML escape sequences before running an XPath query. Added the W3C recommended XPath escape sequence.

3.1.10 BugDB # 14262595:

AUTOBUILD NEEDS TO GENERATE PROPER DISALLOWED LOGIC ON LENS UPDATE

Creation of item definition structure that eliminates former item definition ambiguities.

3.1.11 BugDB # 13257609:

EMBEDDED COMMAS CAUSE LINES TO BE DROPPED WHEN IMPORTING UNSPSC DESCRIPTIONS

Classification schemas (both UNSPSC and user-defined) in the Knowledge Studio can now be imported with greater accuracy and flexibility.

3.1.12 BugDB # 12875499:

ADD EDITABLE FULLFORM COLUMN TO KS TERM ATTRIBUTES DISPLAY

Ability to review and edit full forms for term rules is provided on a single interface page in the Knowledge Studio.

3.1.13 BugDB # 10226704:

NULL POINTER ERROR IN KNOWLEDGE STUDIO WHEN USING INSERT NEW PARENT

New parent insertion functionality expanded to cover additional rule-creation scenarios.

3.1.14 BugDB # 13852140:

REFINE HANDLING OF MULTIPLE ATTRIBUTE VALUES

New functionality for ordering and concatenation of multiple attribute values in Knowledge Studio.

3.1.15 BugDB # 13899883:

CATEGORY READER AND 5.6.2 (OR PRIOR) DATALENSES CONTAINING CLASSIFICATION TYPES

Improved category reader (for Classifications) accommodates greater number of schema formats.

3.1.16 BugDB # 13982871:

REDUCE THE NUMBER OF LENS REVISIONS KEPT BY THE KNOWLEDGE STUDIO

Data lens revisions limited to three unless specified otherwise by the user.

3.1.17 BugDB # 13935737:

UNIT CONVERSION PRECISION

Decimal rounding rules available globally (Unit Conversion) and for item definition attributes (Standardize Attributes) in the Knowledge Studio.

3.1.18 BugDB # 9916241:

THREE TO FOUR DIGIT CLASSIFICATION NUMBER RANGE IS NOT WORKING

Improved category reader (for Classifications) accommodates greater number of schema formats.

3.1.19 BugDB # 13600642:

COPY ATTRIBUTE STANDARDIZATION

Attribute Standardization rules may be copied across item definitions or across standardization types in the Knowledge Studio.

3.1.20 BugDB # 9732123:

6007-PT: EXTRA/MULTIPLE INSTANCES OF ATTRIBUTE VALUE NEED TO BE ORDERED

New functionality for ordering and concatenation of multiple attribute values in Knowledge Studio.

3.1.21 BugDB # 9731095:

4778-PT: REMOVE OROMATCH

Oromatch regular expression engine replaced with java.util.regex. Some regular expressions currently in use in data lenses or DSA may need to be modified. The Oracle JavaDoc for java.util.regex.Pattern can be referenced, as it is the most relevant spec for legal regular expression patterns.

3.2 Known Issues and Workarounds

The following sections describe known issues and any workarounds that exist in the 11g R1 (11.1.1.6.0) release.

3.2.1 BugDB # 14641385:

JAVA API FAILED FOR INVALID USER IDS

The EDQP 11.1.1.6.0 Java API expects a valid user to exist called, api. This valid user is automatically configured in the EDQP 11.1.1.6.1 Java API though it is not in the EDQP 11.1.1.6.0 Java API. If you are using the EDQP 11.1.1.6.0 Java API, you must manually create api user using the WebLogic console:

1. Ensure that your WebLogic Server is running on your Oracle DataLens Administration Server.

2. Open a supported web browser and enter the following URL:
http://hostname:port/console

where hostname is the DNS name or IP address of the Oracle DataLens Administration Server and port is the listen port on which the server is listening for requests (port 2229 by default).

If you configured the Oracle DataLens Administration Server to use Secure Socket Layer (SSL) you must add s after http as follows:

https://hostname:port/console

3. When the login page appears, enter the user name and the password you used to start the server, and then click Login.
Your WebLogic Administration Console log in web page is displayed.

4. In the Domain Structure panel for your EDQP domain (dls_domain is the default), click Security Realms.

5. Click myrealm.

6. Select the Users and Groups tab.

7. Click New to add a new user.

8. Enter api in the Name: field.

9. Enter Java API user in the Description: field.

10. Enter any character string compatible with WebLogic password standards in the Password: field, and then enter the same password in the Confirm Password field.

11. Click OK.
Once the api user exists, the Java API integration will work correctly.

12. Click Log Out to exit your WebLogic Administration Console.

3.2.2 BugDB # 13951158:

REPEATING ERRROR MESSAGE AFTER TIMEOUT ON WEB PAGE INACTIVITY

This message only appears when using the Internet Explorer browser. If the message appears, close your browser then reopen it or use one of the other supported browsers.

3.2.3 BugDB # 14521917

STUCK THREADS WILL OCCUR IF A JOB ATTEMPTS TO RUN BEFORE LENSES ARE LOADED

In a multi-server environment where transform servers are loading lenses and lenses are dispersed among servers in a group, ”stuck thread” errors may occur. This happens if you attempt to run a job that uses data lenses that have been promoted to an Oracle DataLens Transform Server, but have not finished loading. This condition can be cleared with a server restart.

Before running a job, users should review the Oracle DataLens Administration Server log to confirm that the data lens load process has been completed.

3.2.4 BugDB # 10288249

PRIORITY CANNOT BE CHANGED FOR RUNNING OR PENDING JOBS

A job which is either running or pending will use the priority that was set at the time the job was created.

3.2.5 BugDB # 14584382

DSA BOM REPORT DOES NOT RENDER CORRECTLY IN NON-IE BROWSERS

Using Internet Explorer, the DSA BOM is rendered in a easy-to-read report format. In other browsers, the report is displayed as an XML document.

4 Related Documents

Use the following documents in the EDQP documentation set to begin using the product:

- The Oracle Enterprise Data Quality for Product Data Getting Started Guide provides information about how to get started with EDQP.

- The Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Installation Guide provides detailed Oracle DataLens Server installation instructions.

- The Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Administration Guide provides information about managing an Oracle DataLens Server including users and user roles.

See the latest version of this and all documents in the Oracle Enterprise Data Quality for Product Data Documentation Web site at

http://docs.oracle.com/cd/E35636_01/index.htm

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

Access to Oracle Support

Oracle customers 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.

Oracle Enterprise Data Quality for Product Data Release Notes, Release 11g R1 (11.1.1.6)

E29149-05

Copyright © 2012, 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.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

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.

License Restrictions Warranty/Consequential Damages Disclaimer

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.

Warranty Disclaimer

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.

Restricted Rights Notice

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

Hazardous Applications Notice

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.

Third-Party Content, Products, and Services Disclaimer

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.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.