Oracle® Warehouse Builder

Business Intelligence Objects

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 owb_home/owb/deployed_files directory.

Dimensional Objects

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

Experts

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.

Languages and Translations

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.

Mapping Debugger

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

General Restrictions in the Mapping Debugger

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.

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

2. You cannot pause an active debug run using the pause button on the toolbar or the associated item in the debug menu.

3. Mapping statistics will be provided in a future release. The statistics will appear as an additional tab on the left bottom panel.

4. You cannot use the Repository Browser to view the results of a mapping run in debug mode.

5. Breakpoint and watch settings are not preserved between debug sessions.

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

7. The following mapping operators are not supported when running mappings in debug mode:

   • Advanced Queue

   • Flat File

Mapping Designs and Configurations

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.

Workaround: When viewing mappings created in the scripting language, use the auto-layout command in the Mapping Editor to view the entire mapping.

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.

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

Importing Data from an Oracle Database

5467424: IMPORT WIZARD THROWS ORA-00997 IMPORTING A TABLE

When you import table definitions from an Oracle Database, you may encounter an error such as "Repository Error Message: ORA-00997: illegal use of LONG datatype...". This occurs when the CURSOR_SHARING parameter is set to FORCE or SIMILAR.

Workaround: Set the database parameter CURSOR_SHARING to EXACT.

MDL Import

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.

OMB Plus Scripts

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 10g Release 2 (10.2). 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)

• ASSOCIATION_RULES_MODEL

• ATTRIBUTE_IMPORTANCE_MODEL

• CLASSIFICATION_MODEL

• CLUSTERING_MODEL

• FEATURE_SELECTION_MODEL

• LCRCAST_OPERATOR

• LCRSPLITTER_OPERATOR

• MINING_MODEL

• MULTIPLEXER_OPERATOR

• QUEUE_PROPAGATION

• QUEUE_TABLE

• REGRESSION_MODEL

• REAL_TIME_MAPPING

• STREAMS_CAPTURE_PROCESS

• STREAMS_QUEUE_SUBPROCESS

• STREAMS_QUEUE

• TABLE_FUNCTION (limited support)

Repository Browser

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.

Upgrade

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.

User Interface

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 OWB_HOME/bin/admin directory. For example, the Data Object Editor layout file is called SchemaEditorLayout.xml and the Mapping Editor layout file is called MappingEditorLayout.xml.

Warehouse Builder Connector to SAP R/3

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:

http://metalink.oracle.com

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 <OWB_CLIENT_HOME>/owb/bin/admin.

To access SAP R/3 in the Control Center, first obtain the SAP RFC library from SAP and copy it to <OWB_SERVER_HOME>/owb/bin/admin where OWB_SERVER_HOME is the directory where Warehouse Builder control center service is installed.

Revisions to the Oracle Warehouse Builder User's Guide 11g Release 1 (11.1)

In chapter 8, Designing, Process Flows, the following content should be added at the beginning of the section entitled "Instructions for Defining Process Flows".

Before You Begin

To enable deployment of process flows, install Oracle Workflow as described in "Enabling Integration with Oracle Workflow" in the Oracle Warehouse Builder Installation and Administration Guide 11g Release 1 (11.1).