11g Release 1 (11.1)
This document contains important information not included in the Oracle Warehouse Builder documentation.
This document provides the following information on Oracle Warehouse Builder 11g Release 1 (11.1):
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.
The Oracle Warehouse Builder 11g Release 1 (11.1) documentation set includes these publications:
Oracle Warehouse Builder Installation and Administration Guide
Oracle Warehouse Builder User's Guide
Oracle Warehouse Builder API and Scripting Reference
To access to documentation set, including the latest version of the release notes, refer to the following Web site:
For the latest information on platform-specific requirements, certifications and patches, refer to the following Web site:
This section lists the known issues and limitations in the Oracle Warehouse Builder 11g Release 1 (11.1) release. They are grouped into the following categories:
5213153, 5191402: NLS: NON-ASCII CHARACTERS ARE CORRUPTED IN GENERATED EEX FILE
When you deploy business definitions that include non-ASCII characters, the deployment fails with errors.
Workaround: Manually import the .eex file generated by Warehouse Builder for the deployed objects into your Discoverer EUL. The .eex file is located in the
5189802: EXECUTING A CUBE MAPPING MAY GENERATE ERROR ORA-20101
When you attempt to execute a mapping that includes a cube partitioned on a time dimension, you may encounter "ERROR ORA-20101: <timestamp> Error Occurred in <error location>: Attempt to write to non-existent partition..."
5176858: USER INPUT IN A CUSTOM DIALOG MAY TRIGGER THE INCORRECT OUTCOMING TRANSITION
When you run an expert that includes multiple custom dialogs, the expert traverses the correct transition for the first custom dialog but may proceed with the wrong transition in subsequent custom dialogs. For example, if you select CANCEL on the first custom dialog and OK on a subsequent custom dialog, the expert may fail to reset a flag and therefore erroneously traverse the CANCEL transition after both custom dialogs.
Workaround: Reset the flag by entering
set EXIT_CODE 0 in the pre-processing of the task.
6074518: UI MESSAGES ARE NOT DISPLAYED IN SQLPLUS WINDOW
In the Design Center, if you attempt to start the SQL Plus window from the Tools menu, you may encounter errors. For certain languages such as Japanese, Korean, and Chinese, you may not be able to invoke the SQL Plus window from the Design Center. Or, you may not be able to see user interface messages.
Workaround: Invoke SQL Plus from a tool other than Warehouse Builder.
5372377: CANNOT SET DATE WHEN MIDDLE-TIER LOCALE IS DIFFERENT
When the Locale setting of the Repository Browser listener is different from the Locale setting of the Repository Browser, errors occur when you try to display reports using the Repository Browser.
5112489: REPOSITORY ASSISTANT DOES NOT FOLLOW LOCALE PREFERENCE
In the Design Center, if you set the locale to a different language, the change does not affect the Repository Assistant. That is, if you select a new locale using the Appearance Preferences in the Preferences dialog box, commit the changes, and then launch the Repository Assistant, the system default language displays in the assistant despite your selection in the Design Center.
5122612: UNABLE TO CREATE MULTIBYTE TARGET USER IN OMB PLUS
When you create a target user using OMB Plus, if you use multibyte characters in the user name, the target user creation fails.
5031270: NLS:OWB1012:HARDCODE IN DESIGN CENTER
When you change the Locale preference in the Design Center, certain object names or folder names still display in English. These include the names of various categories of pre-defined Warehouse Builder transformations (displayed under the Public Transformations node of the Global Explorer), MY_PROJECT, the default control center called DEFAULT_CONTROL_CENTER, the folder called DERIVED_DATA_RULES that contains derived data rules, and the default configuration called DEFAULT_CONFIGURATION.
5017820, 4915836: NON-EUROPEAN FONT GLYPHS ARE CORRUPTED IN SVG
When you export the diagram displayed on the Data Object Editor canvas to an .SVG file, certain Arabic and Asian characters are corrupted.
Workaround: Export the diagram using the JPEG format.
3066632: WAREHOUSE BUILDER FLAT FILE SAMPLE WIZARD COUNTS A MULTI-BYTE CHARACTER LENGTH AS 1
The Warehouse Builder Flat File Sample Wizard does not handle multi-byte characters in delimited files correctly, when translated into Japanese. The Sample Wizard handles a multi-byte character in delimited files as 1 length.
Workaround: Manually edit the length using the Flat File Sample Wizard.
2887323: DO NOT SET BREAKPOINTS FOR OPERATORS OR MAPPINGS THAT CANNOT BE STEPPED THROUGH
You will not be able to set breakpoints for operators that cannot be stepped through. In the Warehouse Builder client, the breakpoint button is not disabled. However, when you click this button, no action is performed.
2887449: MAP EXECUTION DONE MESSAGE COMES UP BEFORE RESULTS ARE DISPLAYED
In the current release, the mapping debugger displays a message that the mapping execution is complete, the progress bar continues to show activity, and then displays the debugging results. This is incorrect. The message that the mapping execution is complete should not appear until after the debugging results display.
2983137: DEBUGGER CREATES LOG FILE
The Debugger creates a log file called
debugger.log in the
/owb/bin/admin directory. The log file includes each step processed during mapping debug sessions and the generated code.
Workaround: Delete this file, if it becomes very large.
These issues include functions currently included in the Mapping Debugger that have not yet been enabled as well as functions that intend to be added in future releases.
Mappings run using the debug mode in the Mapping Editor are intended to be used for debug purposes only. Mappings run from the Mapping Editor do not perform as well as mappings that are run using the Control Center. This is attributed to the set up of temporary objects necessary to support the debugging capabilities. Use the Control Center to run mappings.
You cannot pause an active debug run using the Pause button on the toolbar or the associated item in the debug menu.
Mapping statistics will be provided in a future release. The statistics will appear as an additional tab on the left bottom panel.
You cannot use the Repository Browser to view the results of a mapping run in debug mode.
Breakpoint and watch settings are not preserved between debug sessions.
Only mappings that can be implemented as a PL/SQL package can currently be run in debug mode. ABAP mappings are not supported in the debugger.
The following mapping operators are not supported when running mappings in debug mode:
6050580:DATE FORMAT ERROR USING START TO RUN MAPPINGIn limited cases, you may encounter unexpected behavior when running a mapping that loads and transforms timestamp data. For example, if you deploy and run a mapping that transforms a column from timestamp type to varchar2, the resulting data in the target column may be incorrect.
Workaround: This behavior does not arise when using the Mapping Debugger. Run the mapping and load the data using the Mapping Debugger.
5212360: MAPPINGS CREATED IN OMB PLUS MAY DISPLAY INCORRECTLY
In the Mapping Editor, a mapping that was created via OMB Plus may display as containing a single operator despite having multiple operators.
3014556: CANNOT COPY A SAP SOURCE TABLE IN DEFINE TEST DATA
In this release, you may encounter the warning message "ORA-01861: literal does not match format string" when you use the Create Table option for an SAP source table in the define test data.
2763192: FULL OUTER JOIN QUERIES TO TABLE FUNCTION GIVES WRONG NUMBER OF ROWS ON BULK FETCH
When the query containing a full outer join is passed as a REF cursor parameter to a table function, during execution, the wrong number of rows is fetched.
Workaround: Avoid mappings that result in a full outer join being used as a REF cursor parameter to a table function.
2577706: POST MAPPING PROCESS RUNS REGARDLESS OF SUCCESS/FAILURE OF MAPPING
The mapping return status has one of three values:
SUCCESS - Mapping completes successfully with no errors
WARNING - Mapping completes with errors but not over the max error limit
ERROR - Mapping does not complete OR mapping has errors over the max error limit
The Maximum Number of Errors parameter applies to the count of errors for the entire mapping run, whether run in set-based, row-based, or failover modes. Consider the following cases:
Max number of errors set to 50, mapping run in set-based mode. Data did not load successfully. One error resulted from failure of the set-based load DML statement. Mapping return status is "WARNING".
Max number of errors set to 50, mapping run in set-based mode, "Enable constraint" property set to false. Data loaded successfully but 60 constraint violation errors occurred during re-enabling of constraint. Mapping return status is "ERROR".
Max number of errors set to 50, mapping run in row-based mode. Some data loaded successfully but with many errors. Mapping will terminate after hitting the 50th error. Mapping return status is "ERROR".
Max number of errors set to 50, mapping run in set-based failover to row-based mode. Data did not load successfully in set-based process. One error resulted from failure of the set-based load DML statement. Some data loaded successfully in row-based process but with many errors. Mapping will terminate after hitting the 49th error in row-based because there was one error counted in set-based. Mapping return status is "ERROR".
4558688: SCRIPT GENERATION FOR IMPORT OF METADATA FOR EXTERNAL TABLES FAILS FOR LONGER DEFINITIONS
When you import metadata for an external table from an Oracle database, if the length of the external table access parameters is more than 4000 characters, the access parameters are truncated. Thus the imported external table cannot be generated successfully.
4581172, 4658511: DEFERRED OBJECTS LISTED IN METAMODEL QUERY
The OMB Plus scripting language includes commands for certain objects that were descoped from Oracle Warehouse Builder 11g Release 1 (11.1). These objects will be supported in a future release of Warehouse Builder. The list of objects that are listed in OMB Plus model queries, but are not available for use in the current release are as follows:
ADVANCED_QUEUES (limited support)
TABLE_FUNCTION (limited support)
5129228: MULTIPLE REPOSITORY BROWSER SESSIONS FROM A SINGLE CLIENT MACHINE NOT SUPPORTED
If you launch multiple Repository Browser sessions from a single internet browser on a single client machine, you will encounter unexpected results. This scenario is not supported. As a consequence, you cannot browse multiple repositories with a single internet browser on a single machine.
Workaround: Each Repository Browser session requires its own internet cookies storage. If feasible, you can launch multiple, different internet browsers to maintain an equivalent number of Repository Browser sessions on the same machine.
1477144: WAREHOUSE UPGRADE CANNOT DELETE AN INDEX
The Warehouse Upgrade does not drop an index from the data warehouse when you delete that index from the model in the Warehouse Builder repository. The upgrade script is created and deployed successfully but the index remains in the database.
Workaround: Use another database tool external to Warehouse Builder (such as, SQL*Plus, or Enterprise Manager) to drop the index.
1811047: PARTITION VALUES AND WAREHOUSE UPGRADE SCRIPTS
Warehouse Upgrade scripts are incorrectly generated for objects that have had partition values changed or new partition keys added to a previously deployed partition.
Workaround: Using an external Oracle database tool (SQL*Plus or Enterprise Manager), drop the partition and then recreate it.
5127178: LAYOUT OF OWB WINDOW SEEMS CORRUPTED OR UNUSABLE
Sometimes, although very rarely, the layout of an editor window may become corrupted or unusable.
Workaround: Delete the appropriate layout editor file, close the Warehouse Builder client, and then log in again.
The layout editor files use self-explanatory names and are located in the
/bin/admin directory. For example, the Data Object Editor layout file is called
SchemaEditorLayout.xml and the Mapping Editor layout file is called
Using the Warehouse Builder Connector to SAP R/3, you can access versions of SAP that rely on the SAP R/3 technology, including SAP 3.x, 4.x, 4.7, 5.0 and mySAP ERP 2004. For a list of supported platforms and versions, refer to the certification information available a the following Web site:
4483510: PLUGGABLE MAPPINGS DO NOT WORK IN SAP MAPPINGS.
5215322: WAREHOUSE BUILDER CONNECTOR TO SAP R/3 REQUIRES SAP LIBRARY FILE
To access SAP R/3 in the Design Center, first obtain the SAP RFC library from SAP and copy it to the
To access SAP R/3 in the Control Center, first obtain the SAP RFC library from SAP and copy it to the
OWB_SERVER_HOME is the directory where the Warehouse Builder control center service is installed.
You cannot create advanced queues in Oracle Warehouse Builder 11g Release 1 (11.1). You can however import an MDL file that contains advanced queues created using a previous release and deploy these advanced queues.
Note that, in the current release, you cannot create a mapping with an Advanced Queue operator. You can have a mapping containing an Advanced Queue operator only if you import an MDL file that was created using an earlier Warehouse Builder version.
The following information should be included in the section entitled "Performing Data Profiling" in Chapter 22, Understanding Data Quality Management.
Data profiling can only profile 165 columns per table, view, or materialized view. This limitation is described in bug 6505764.
If your table, view, or materialized view has more than 165 columns, you must use an attribute set to select 165 or fewer columns for profiling. The following section describes the procedure for profiling data using attribute sets.
You can use an attribute set to restrict a data profiling operation to a subset of columns from a table, view or materialized view. Reasons to use an attribute set include:
You can decrease profiling time by excluding columns for which you do not need profiling results.
Data profiling can only profile up to 165 columns from a table, view, or materialized view at a time. You can use an attribute set to select a set of 165 or fewer columns to profile from the object.
Data profiling, using attribute sets, consists of the following high-level steps:
Use the following steps to define an attribute set in a table, view, or materialized view.
In the Project Explorer, double-click the table, view, or materialized view.
The Data Object Editor for the selected object is opened.
In the Details panel, select the Attribute Sets tab.
In the Attribute Sets section, click a blank area in the Name column and enter the name of the attribute set to create.
Close the Data Object Editor.
Double-click the table, view, or materialized view in which you created an attribute set in step 3.
The Data Object Editor for the selected object is displayed.
On the Attributes Sets tab, select the name of the attribute set created in step 3.
The Attributes of the selected attribute set section displays the attributes in the data object.
Select Include for all the attributes that you want included in the attribute set.
Save your changes and close the Data Object Editor.
Use the following steps to create a data profile that contains the attribute set.
In the Project Explorer, right-click the Data Profiles node and select New.
The Welcome page of the Create Data Profile Wizard is displayed.
On the Welcome page, click Next.
On the Name and Description page, enter a name and an optional description for the data profile. Click Next.
On the Select Objects page, select the data object that you want to profile and use the shuttle arrows to move the data object to the Selected list.
When the selected data object contains attribute sets, the Choose Attribute Set dialog box is displayed.
On the Choose Attribute Set dialog box, select the attribute set that you want to profile and click OK.
On the Select Objects page, click Next.
On the Summary page, review the options you choose on the previous wizard pages and click Finish.
The data profile is created and added to the Navigator tree.
For details about how to profile objects using a data profile, refer to the section titled "Steps to Perform Data Profiling" in the Oracle Warehouse Builder User's Guide.
The following is a limited list of known issues from previous releases. These issues were reported in a previous set of release notes and are now resolved in Oracle Warehouse Builder 11g Release 1 (11.1).
5934899: NEED TO DOCUMENT IN DETAIL SCD2 UPDATE BEHAVIOR
5372855: KEY LOOKUP ON SCD2 - PARENT VALUES ARE NOT RETURNED
5187382: CANNOT CREATE A FISCAL TIME DIM IN A LOCALE OTHER THAN ENGLISH
5026036: NLS: CORRUPTED OBJECT NAME IN IMPORT OBJECT SELECTION WHEN IMPORT BINARY MDL
4307126: XML LOAD FROM VIEW WITH DBLINKS DOES NOT LOAD ROWS, LOCAL VIEW DOES LOAD ROWS
3029309: DEBUGGING MAP WITH OPERATORS HAVING THE SAME NAME IN BUSINESS NAME MODE
Oracle Warehouse Builder Release Notes, 11g Release 1 (11.1)
Copyright © 2000, 2012, 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.