Release Notes for Oracle Data Integrator
This document describes known issues associated with Oracle Data Integrator and includes information regarding post-installation patches. It includes the following sections:
This section contains information on the following:
When a tab containing a page is closed in Oracle Data Integrator Console, all the tabs after this one reset their task flows (the navigation actions that were made). The pages in these tabs reset to the original object that was opened. 
This section contains information on the following issues:
Load plans with many parallel steps might run out of available database connections, as every parallel step consumes an extra connection. This can be controlled by limiting the 'maximum number of sessions' in the Agent configuration. 
When importing a master or work repository, the import dialog prompts you to enter the Export Key used when the repository was exported. After entering the incorrect key three times, a dialog is shown which suggests you can import the repository without cipher text. Selecting this option and clicking OK fails with the following error:
ODI-3049:exception while importing master_encr.zip. Failure reason ODI-14146: Incorrect Export Key
This section contains information on the following issues:
Oracle WebLogic Configuration Wizard does not support Oracle RAC URLs for datasources. When a datasource is included in a Java EE Agent template that has been generated using Oracle Data Integrator Studio, this template fails to deploy, and raises the following exception:
com.oracle.cie.wizard.WizardController - Uncaught Exception java.lang.NullPointerException atcom.oracle.cie.domain.jdbc.DatasourceXBeanAspectHelper.decomposeURL
As a workaround, do not include this datasource definition in the generated template and deploy the datasource from Oracle Data Integrator Studio. [9436451, 9457218]
When more than 1000 objects are in a folder, markers added to any of the objects in the folder will not appear. [10010838, 10060828]
When refreshing a Load Plan to pick the latest Scenario reference in the Load Plan, the latest scenario is determined by the Scenario Creation timestamp. However, during ODI agent execution, the latest scenario is determined by the alphabetical ascending sort order of the Scenario Version string value, selecting the last Scenario in the list. 
When a load plan is being executed across multiple agents, the agent logic relies on dbms_lock to be released by a database in the event of a client connection disruption. However, if the client connection is disconnected due to a network error which prevents the agent from receiving a database lock release, the load plan execution may be stuck blocked in a lock acquisition request.
As a workaround, configure the database level property
sqlnet.expire in the sqlnet.ora file to 1 minute, or some other relatively short period. This setting forces the database to check for client connection validity periodically, so that in the event of a disconnection the dbms_lock can be released within a few minutes rather than hours. Releasing the dbms_lock allows the load plan to complete or fail in a timely manner rather than hanging. 
While a mapping is displayed in the structure pane, clicking on other items in the Designer Navigator tree causes the display to go blank, as expected (because these items have not been loaded). However, selecting the open mapping in the tree does not cause the display in the structure pane to re-draw the open mapping.
To view the open mapping in the structure pane after it has been blanked, select the open mapping tab. 
When a design time object is directly executed on a remote agent from ODI studio, if the remote agent is down at that moment, then the session is left in waiting state and the Physical Agent will be set as Local (No Agent). The session will be marked as stale session when the remote agent comes up.
You can safely delete this stale session and try again with an agent that is up and running. 
Tracked variables are not displayed in the Variables node in the Session List in the Operator Navigator. However, the variables can be viewed in the Variable and Sequence Values section of the Session Step or Session Task Editor. 
After creating a diagram for a model containing one or more datastores, if the model is duplicated using a shortcut, the new duplicated model contains the diagram with the datastores. Selecting a datastore causes it to be opened in the original model, rather than in the duplicated model. 
After materializing a shortcut for a datastore, open mappings using this datastore fail while saving and the following error is displayed:
ODI-26182: Object was modified by another user and cannot be saved.
As a workaround, close and reopen the mapping and repeat changes. 
A Groovy script, depending on external JDBC drivers, may fail with a
ClassNotFoundException as the JDBC drivers in the user classpath are not found.
As a workaround, edit
odi.conf and add the JDBC driver jar using
AddJavaLibFile. For example,
If two or more unsaved reusable mappings with the same name (such as the default name, "New Reusable Mapping") are open in ODI Studio, and one is closed using the File -> Close menu item, all of the reusable mappings with that name are closed, even if one or more have unsaved changes.
Closing a reusable mapping using the X icon on the editor does not cause this issue. 
When using the Test Connection button for the Enterprise Scheduler, the test connection dialog is opened with a drop down list to pick the agent where the connection test should be performed. Local agent is incorrectly included in the drop down list even though a local agent cannot be used for an ESS-ODI asynchronous invocation communication channel. 
This section contains information on the following issues:
By default, all loaded KMs in the repository are replaced during repository upgrade, irrespective of whether they are modified or not. Do not upgrade the KMs during repository upgrade.
The following are the workarounds to upgrade the KMs:
If you have SAP KMs, you must not upgrade the KMs during repository upgrade. The new SAP KMs require new ODI SAP components. Using new SAP KMs with old ODI SAP components causes any SAP mappings to fail.
As a workaround, uncheck Replace KMs with Mandatory Updates when upgrading the ODI repositories. To upgrade SAP KMs, follow the upgrade instructions given in the Application Adapters Guide for Oracle Data Integrator for the respective ODI SAP adapter.
If you have any custom KMs, the customizations are lost if you upgrade the KMs during repository upgrade.
As a workaround, uncheck Replace KMs with Mandatory Updates when upgrading the ODI repositories. After you upgrade the repositories, manually replace only those KMs that you want to upgrade.
"IKM SQL Incremental Update (Row by Row)" fails on task Flag rows for update if the target table name contains Japanese characters. In the generated code, the integration table name appears as
? characters replace Japanese characters.
As a workaround, replace this IKM with another IKM suitable for the technology. For example, "IKM Oracle Incremental Update" for Oracle. 
When attempting to save edits or deletes of data from an MSSQL model, an error similar to the following may be displayed:
java.sql.SQLSyntaxErrorException: [OWLS][SQLServer JDBC Driver][SQLServer]Invalid object name 'dbo.SRC_CUSTOMER'.
SQL generated by the internal Jbuilder library uses only the SCHEMA and TABLE names, but not the CATALOG field, which prevents a connection for edit/update from being made with the target MSSQL dataserver. 
"IKM SQL Incremental Update (Row by Row)" fails if the KM option LOG_FILE_NAME is set to a Windows path containing backslashes, for example
LOG_FILE_NAME=C:\user\joe\odi_load.log. This worked in 11g releases.
As a workaround, use a double backslash in the path, for example
When an exception thrown by a Jython script contains Non-ASCII data, the Non-ASCII data might be replaced with
???. However, this does not mean that business data is affected, and more information can be obtained in the exception stack. 
While creating a table on Teradata, the Teradata JDBC driver version prior to 188.8.131.52 may throw the exception
Cannot create nonfallback table <table> with AMP down. This is due to a bug in the Teradata driver while getting the FetchRowCount after executing the table creation SQL.
To resolve the issue, contact Teradata to get a fix for the Teradata JDBC driver. 
The integration knowledge module IKM Oracle Control Append must be replaced with the 12.1.3 version when upgrading to ODI 12.1.3 or later, from earlier versions of ODI. 
ODI 12.1.2 and 12.1.3 allows the use of the MySQL ENUM datatype in mappings, with the following restrictions:
FLOW and STATIC control must be disabled
Create target table must be disabled
The MySQL database cannot be used as an external database store. The generated SQL for the database can cause syntax exceptions.
The external database store is used for XML, Complex File, or LDAP drivers, as described in "Part IV, Appendixes" of Connectivity and Knowledge Modules Guide for Oracle Data Integrator. 
When selecting the technology HBase and a logical schema inside a model, the following error is displayed:
ODI-20754: Driver name cannot be empty
The error message is incorrect, as an HBase data server cannot have a driver name configured. The error won't be displayed after customized reverse engineering is selected for the model. 
The RKM SQL (JYTHON) fails if JDBC driver doesn't support REMARKS columns. 
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
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® Fusion Middleware Release Notes for Oracle Data Integrator, 12c (12.1.3)
Copyright © 2010, 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 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 failsafe, 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.