|
|
 Copyright © 2003, 2003 Oracle Corporation. All Rights Reserved. |
|
| Oracle 9i Warehouse Builder Release Notes Release 9.2 Part Number B10999-01 |
|
Oracle is a registered trademark, and Oracle9i and SQL*Plus are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.
Copyright © 2003 Oracle Corporation.
All Rights Reserved.
July 2, 2003
Part No. B10999-01
These release notes provide the following information on Oracle9i Warehouse Builder Release 9.2:
In previous releases, Warehouse Builder was available for Solaris and Windows platforms (NT, 2000, XP). Beginning with this release, Warehouse Builder is scheduled to be available for the following additional platforms:
Go to http://metalink.oracle.com to verify final availability. Note that the OLAP Bridges feature is only available on Windows platforms and the Name and Address Server is only available on Windows and Solaris platforms.
This section lists the Oracle database versions with which Warehouse Builder is certified and the required patches. Go to http://metalink.oracle.com for updates on certification and patches.
For all gateways, including generic connectivity, you must apply database patches to both the repository and target databases. To download gateway patches, go to the patch section of MetaLink. Select Product: Oracle Transparent Gateway for [database] and the appropriate platform.
Database: Oracle 9.2.0 Enterprise Edition. This version of the database no longer supports Oracle 7.3 sources. Oracle9i Warehouse Builder is not certified against Oracle9i Standard Edition.
Application Server: Oracle9iAS Release 2 (optional).
Oracle Enterprise Manager: OEM 9.2.
Database: Oracle 9.0.1.3 Enterprise Edition. Oracle9i Warehouse Builder is not certified against Oracle9i Standard Edition.
Application Server: Oracle9iAS Release 2 (optional).
Oracle Enterprise Manager: OEM 9.0.1.
Open System Gateways: Oracle Transparent Gateway version 9.0.1 for Informix, Sybase or Microsoft SQL Server only after you upgrade the Oracle Server to 9.0.1.2 and apply patch 2200201.
Mainframe Gateways: Oracle Transparent Gateway for DB2 on IBM OS 390 (MVS) version 8.1.7.
DRDA Gateway: Oracle Transparent Gateway for DRDA version 8.0.4.1.
Some features new in Oracle9i Warehouse Builder leverage functionality from the Oracle9i Release 2 database. The following functionality is not available for use with Oracle9.0.1 and previous versions:
Database: Oracle 8.1.7 Enterprise Edition.
Open System Gateways: Use Oracle Transparent Gateway versions 8.1.6 for Informix, Sybase or Microsoft SQL Server after applying the appropriate gateway patches.
Mainframe Gateways: Oracle Transparent Gateway for DB2 on IBM OS 390 (MVS) version 8.1.7.
DRDA Gateway: Use Oracle Transparent Gateway for DRDA version 8.0.4.
Some features new in Oracle9i Warehouse Builder leverage functionality from the Oracle9i database. The following functionality is not available for use with Oracle8i and previous versions:
The following scenarios describe the current multiple user functionality.
SCENARIO 1
The Deployment Manager performs a commit after generation is performed, which will unlock the objects. Hence they can be altered in OMB Plus. When the Deployment Manager is invoked from the console, this commit is not performed, and so the objects are still locked until a commit is performed manually.
The deployment commit is needed to ensure consistency between the runtime and design repositories. In actual fact, there are two commits: one as soon as you press 'Deploy' (which displays a Commit dialog box to the user), and the second is performed immediately after the generation is complete. As a result, the second commit is only committing the generated results.
Once the generation has been performed, and the Pre Deployment Generation results screen is displayed, the generated scripts have already been passed to the runtime platform in preparation for the deployment. Users may continue to change the design objects without affecting the deployment (this could be through another client, or OMB).
SCENARIO 2
Object is not locked. Open editor or property sheet. Object gets locked (other sessions UI or OMB trying to access object will get it in a read only mode). Don't do any changes. Close editor or property sheet. Lock gets released.
SCENARIO 3
For many objects when configuration properties are opened, validation is performed 'underground', thus object is 'altered' and closing configuration would not release the lock. However, validation happens only for a newly created object or for an updated object. If you open or close the configuration parameters window for non-modified object, the lock will be released.
PROBLEMS WHEN RUNNING CONCURRENT WAREHOUSE BUILDER SESSIONS FROM THE SAME OWB_HOME (2990726)
Whether you start multiple sessions from the Warehouse Builder client, or OMB Plus, or both, you may encounter problems using Cut/Copy/Paste in the client or the OMBCOPY OMBMOVE scripting commands in OMB Plus. This is because Warehouse Builder currently allows only a single clipboard. You may encounter the following issues:
Workaround
Do not attempt to use the clipboard in separate session. Complete the use in one session before you use another session.
This release introduces a new commit strategy for mappings with multiple targets. In previous releases, Warehouse Builder performed independent commits. That is, Warehouse Builder committed and rolled back each target separately and independently of other targets. Warehouse Builder now also performs correlated commits. Warehouse Builder considers all targets collectively and commits or rolls back data uniformly across all targets. Use the correlated commit when it is important to ensure that every row in the source impacts all affected targets uniformly.
Warehouse Builder now enables you to create public database links that can be shared across a database. Repository owners, as well as any user with the CREATE PUBLIC DATABASE LINK privilege can create public database links.
In previous releases, Warehouse Builder by default created a temporary table for mappings that required additional processing of source data before exchanging partitions. This occurred when the mapping contained remote sources or multiple sources joined together. You can now by-pass the creation of a temporary table and directly swap a source into a target. Use Direct PEL in a mapping to instantaneously publish fact tables that you loaded in a previously executed mapping.
Warehouse Builder now supports the following data types for flat files:
Beginning in this release, use the Mapping Debugger to locate data flow and user errors in the PL/SQL code that Warehouse Builder generates from the mappings.
In previous releases, to perform data quality functions, you used Warehouse Builder in conjunction with Oracle Pure Integrate. In this release, Warehouse Builder incorporates data quality functionality formerly available in Oracle Pure Integrate. You can use the Match-Merge Wizard or Operator Editor to define business rules for matching and merging records.
In a previous release, you could perform metadata change management using the OMB Plus scripting utility. Beginning in this release, you can also access these functions for the Warehouse Builder client user interface. Metadata change management enables you to take snapshots of metadata objects and use them for backup and history management. Snapshots are supported for any object on the navigation tree and can store information about an object alone (such as a table or module), or the objects within it as well (such as the tables within a module).
Beginning in this release, Warehouse Builder is compatible with multiple certified Name and Address software providers. Third-party vendors can license Name and Address software directly to you for use with Warehouse Builder. This allows you to choose a name and address provider whose offering is the most appropriate for your project.
If you previously purchased a Name and Address license for use with Warehouse Builder 9.0.4, you have the following options:
OR
If you want to continue to use the Trillium adaptor, perform the following manual steps to enable the adaptor:
For Windows, add ..\Trillium\win32 to the PATH environment variable. From the start menu, select settings/control panel/system. Select the advanced tab, select environment variables.
For Solaris, add ../Trillium/solaris to LD_LIBRARY_PATH.
For Linux, add ../Trillium/linux to LD_LIBRARY_PATH.
For Windows, from the start menu, select settings/control panel/system. Select the advanced tab, select environment variables, select New. Create the following variables and values:
For Solaris and Linux, add the following variables to the login shell:
In Warehouse Builder 9.0.4, Trillium specific options were defined in NameAddr.properties. Beginning in this release, NameAddr.properties does not contain vendor specific setting. The country specific table path properties and the "enableDetailLogging" property are Trillium specific and are now located in tss.properties.
In previous releases, you defined the Name-Address operator using the mapping canvas and the operator Configuration Properties sheet. Beginning with this release, you can use either the Name-Address Wizard or Operator editor.
Starting in this release, Warehouse Builder now includes a Public Application Programming Interface (API). You can use this java API to directly access the Warehouse Builder metadata platform from your application. To access the API, unzip and extract the following file to a folder on your local machine:
<owb home directory>/owb/lib/int/pubapi_javadoc.jar
Double click on the file index.html. Select the Help link for information on how to use the API.
To use the API, include the following directories and libraries in the CLASSPATH for the client application:
<owbhome>/owb/lib/int/admin; <owbhome>/owb/lib/int/publicapi.jar; <owbhome>/owb/lib/int/owb0.jar; <owbhome>/owb/lib/int/owb1.jar; <owbhome>/owb/lib/int/owb2.jar; <owbhome>/owb/lib/int/owb3.jar; <owbhome>/owb/lib/int/owb4.jar; <owbhome>/owb/lib/int/owb5.jar; <owbhome>/owb/lib/int/owb6.jar
Run your client application in the directory:
<owbhome>/owb/lib/int/admin
Warehouse Builder provides increased support for Real Application Clusters (RAC). Warehouse Builder now supports the use of net service names in the runtime. This enables client side load balancing. Warehouse Builder also provides an increased availability in the runtime service. For example, if either the service instance or its associated node fails or is taken out of service, then the runtime service instance on a different node can take over. While the Warehouse Builder design repository can also be used in a RAC cluster, it will not take advantage of any failover features of RAC for this release.
Warehouse Builder now provides advanced repository security and auditing options that you can implement according to your security requirements. The advanced security options include the following:
Download metadata bridges from the MITI website (Metaintegration Technology Inc., www.metaintegration.net) for a specific metadata source, to import designs from third party design tools, such as various versions of Erwin, Rational Rose, Power Designer etc. After you download and install the MITI software on the Warehouse Builder client machine, the menus for various supported tools appear in the Warehouse Builder metadata import wizard. Refer to the MITI web site for a complete list of supported prodcuts.
MAPPING GENERATES INCORRECT RESULTS WHEN CORRELATED COMMIT SET TO TRUE AND OPERATING MODE AT SET BASED FAIL OVER TO ROW BASED (2932912, 2936225)
When using Oracle database 9.2.0.3, mappings may generate incorrect results when correlated commit set to true and the operating mode is set based fail over to row based. The same mapping with operating mode set to row based or set based completes successfully.
TO LOAD MAPPINGS USING PEL, DISABLE CORRELATED COMMIT (2992304)
In this release, mappings that use partition exchange loading and correlated commit may fail.
Workaround
Disable correlated commit.
SAMPLING A FIXED LENGTH FLAT FILE WITH A DECIMAL FIELD ISSUES ERROR INCORRECTLY(3031142)
If you use the Flat File Sample wizard to sample a fixed length flat file, Warehouse Builder may incorrectly report validation message VLD-2839 stating that a field definition as exceeding the allowed length for a fixed length record. This occurs when the flat file includes a DECIMAL field as the last field in the file.
EXTERNAL TABLE MAY GENERATE INVALID RESULTS WHEN BASED ON A FLAT FILE WITH DECIMAL FIELD (3031449)
Warehouse Builder may generate invalid results if you base an external table on a flat file with a DECIMAL field as the last field in the file. This is known to occur when the flat file was created using the OMB Plus scripting language.
Workaround
Open the properties sheet, select the Fields tab, close the properties sheet and regenerate the mapping.
DO NOT SETBREAKPOINTS FOR OPERATORS OR MAPPINGS THAT CANNOT BE STEPPED THROUGH (2887323, 2981111)
For mappings with multiple targets and correlated commit set to true, you cannot set breakpoints on the targets. If you set a breakpoint on an operator that does not permit stepping through, Warehouse Builder discards the breakpoint. Setting breakpoints on the following operators is ineffective:
MAP EXECUTION DONE MESSAGE COMES UP BEFORE RESULTS ARE DISPLAYED (2887449)
In the current release, the 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.
DEBUGGER DISPLAYS TWO ROWS IN WATCH POINT TAB FOR CONSTANT AND MAPPING INPUT PARAMETER OPERATOR (2962621)
In this release, the Debugger incorrectly displays the Constant and Mapping Input Parameter operator as having two rows in the watch point tab.
DEBUGGER DOES NOT SUPPORT ADVANCED QUEUES (2979844)
In this release, the Debugger does not support debugging of Advanced Queues.
DEBUGGER CREATES LOG FILE (2983137)
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. Delete this file if it becomes very large.
DEBUGGER MAY ALLOW YOU TO EDIT MAPPINGS (2996824, 298161, 2976127, 3020874)
In this release, the Debugger may give you error messages but incorrectly allow you to edit a mapping while in the debug mode. Do not edit a mapping during a debugger session.
Workaround
ORA-00972: IDENTIFIER IS TOO LONG MSG SHOWS FOR NON-ORACLE SOURCES MAP (30126210)
When you run the Mapping Debugger in indirect access mode on a mapping with a non-Oracle source, you may encounter error ORA-00972. This occurs when you specify a database link with a name greater than 30 characters.
Workaround
Specify a database link name with 30 characters or less.
CANNOT COPY A SAP SOURCE TABLE IN DEFINE TEST DATA (3014556)
In this release, you may encounter warning message
ORA-01861: literal does not match format string
when you use the Create New table option for an SAP source table in the define test data.
DEBUGGING MAP WITH OPERATORS HAVING THE SAME NAME IN BUSINESS NAME MODE (3029309)
When you debug a mapping with naming mode set to business name mode and propagation to physical name selected, the debugger may not display all operators when you attempt to pick the next step.
Workaround
Debugging mappings with naming mode set to physical naming mode.
USER REQUIRED TO SPECIFY LENGTH FIELDS FOR NAME AND ADDRESS COMPONENTS(3003335)
The Warehouse Builder default length field for name and address output components is zero. To process name and address components properly, you must populate the length fields for all specified components. Refer to your Name Address service provider documentation for acceptable length values.
SECURITY CAN NOT HANDLE FOR SERVICES WHEN PROJECT IS FROZEN (2661282)
In this release, certain service level operations including mdl import, mdl export, and generate are not disabled for frozen projects. You may decide to take other measures to prevent intrusive operation such as these.
INCONSISTENT BEHAVIOR IN OWB REPOSITORY ASSISTANT MAY IMPEDE SECURITY FUNCTIONALITY (3029007)
When you install a repository using the OWB Repository Assistant, the repository installation may complete without a confirmation message.When this occurs, you can connect to the OWB repository as a repository owner, but not as a normal user. This negates Warehouse Builder security functions.
Workaround
Connect as repository schema through SQL Plus. For example, if your sechem name is owb_repos , then issue the following statements:
SQL+> delete from owb_role_info; var out varchar2(100); SQL+> call WBSecurityHelper.initRoleInfo(:out,'my_pwd', 'OWB_REPOS')
where my_pwd is the pwd used protect the Warehouse Builder role
SQL+> call WBSecurityHelper.updateRolePwd('my_pwd')
where string my_pwd should be the same pwd used above
SQL+> COMMIT;
SOME BRIDGES NOT SUPPORTED ON UNIX
The Discoverer bridge generates an EEX file that must be imported using the Discoverer Admin tool, which is only available on Windows. The ERWin and PowerDesigner bridges are only supported on the Windows platform.
REPOSITORY AND RUNTIME REPOSITORY ASSISTANTS: DROPPING A REPOSITORY
When you drop a repository in the Repository Assistant or the Runtime Assistant, the Assistant removes all repository objects. It does not remove any other objects from the schema, such as database links and user deployed objects, and it does not remove the schema itself. You must remove these objects manually.
BRIDGES DO NOT RUN FIRST TIME AFTER INSTALL (2237444)
When you run the bridge during the first user interface session, it will not find the preferences.properties file.
Workaround
Close the Warehouse Builder Client once, open it again, and run the bridge.
CUT/COPY/PASTE DOES NOT SUPPORT PROJECTS (2277487)
The cut, copy and paste functionality does not currently support projects. These operations are limited to design objects only, including all the objects stored within projects.
Workaround
To copy a project into another repository, use the MDL Import and Export utilities.
RIGHT-CLICK POP-UP MENUS MAY NOT APPEAR (1621822, 1766652)
In the console and Module Editor, be careful about shrinking the window horizontally and where you position the cursor if you use a right-click pop-up menu for any node. If the window is shrunk too far you may have to either right click on the extreme left or the extreme right of the node label. If you click in the middle of the label the menu will not appear. Also if the window is narrower than the menu, the menu will not appear.
Workaround
Stretch the window horizontally and the menu will appear. Or, use the menu bar items, such as Transformation, Edit, and View, instead of the pop-up menu.
RENAMING LARGE OBJECTS (2048683)
Renaming very large objects (for example, mappings with many operators and attributes) can take several minutes. The time can be reduced if you close any Editors for that object.
User name and password quoted in code (2089342)
The user name and password are always quoted in the generated code. Do not enclose quotes around user/password.
USE AVAILABLE WIZARDS TO VIEW AND EDIT OPERATORS (2854976)
In this release, do not use the operator properties dialog to view and edit the Match-Merge operator and the Name and Address operator. Use the wizard editor. To edit Match-Merge operator and the Name and Address operators, right click on the operator in the mapping canvas and select Edit. Do not select Operator Properties. In a future release, the Operator Properties dialog will not be available for operators that have wizards.
VALIDATION AND GENERATION OF LARGE PROJECT SEEMS EXTREMELY SLOW (2998887)
Warehouse Builder may be slow to fetch and display the results of a validation for very large projects. This occurs when the memory available to Warehouse Builder is insufficient to allow all objects to remain in cache while fetching the validation results.
Workaround
If the validation or generation of a large project takes a significant amount of time, increase the amount of memory available to Warehouse Builder. If you launch Warehouse Builder from owbclient.bat, change the java command with maximum memory set to 80% of the available physical memory. For example:
..\..\..\jdk\jre\bin\java -Xms64M -Xmx512M -Dlimit=512M
Ensure you have physical memory available on your machine to accommodate this setting.
DATABASE LINKS GENERATED WITH QUOTED LOWER LETTERS GIVES ORA-00942 (2720359)
If you update the database links module properties and set the user and/or password in lower case or mix of lower and upper case, the generated database link contains user and/or password in quoted lower or mixed case, and may result in ORA-00942. Configuration of database links (or registration of locations in releases after 9.0.4) will preserve the case of the username and password entered by the user when database links are generated. Therefore it is important to use the appropriate case for the referenced object; i.e. uppercase for Oracle and mixed case for some non-Oracle systems.
DATABASE LINKS THAT CONNECT TO GATEWAYS REQUIRE GLOBAL-NAMES SET TO FALSE (2789391)
Global-name setting should be set to false on the host of the Runtime Platform if you have database links that connect to a Gateway. This impacts the database link that is created by the Importer. The installation notes advise that global-names are set to false.
DEPLOYMENT MANAGER SHOWS NO INDICATION THAT UPGRADE GENERATION HAS FAILED (2786899)
The Deployment Manager may incorrectly display the deployment status for a failed upgrade. The Deployment Results dialog may report an upgrade as successful when it failed or was never deployed because the impact report indicated errors.
Workaround
To determine the correct status, do one of the following:
View the deployment status in the Runtime Audit Browser.
OR
In the Deployment Results Dialog, in the top grid, click on the row containing the upgraded object. The details grid displays the detailed result message for that upgrade.
ORA-12154 UNABLE TO RESOLVE TNS NAME ERROR (2935974)
You may encounter the error message ORA-12154 when you deploy objects. This error occurs when you type an invalid NetServiceName in the location registration dialog. Warehouse Builder does not currently validate the NetServicesName in the location registration dialog.
DATABASE LINK GETS GENERATED EVEN THOUGH LOCATION IS LOCAL (2682262)
In some cases, Warehouse Builder may generate a database link when one is not required and is not used.
LOCATION NAMES MUST BE UNIQUE WITHIN A RUNTIME REPOSITORY (2712901)
Errors occur during deployment due to limitations in the way locations are identified. These errors occur if you use locations with the same name or if you use locations previously deployed from another project.
After deploying to a location for the first time, an internal identifier is registered to the location and is used to identify the location as unique between the design and runtime repositories. Errors will occur if you try to deploy using the same location from another project. This can happen if you import a project that contains the previously used location and attempt to use it during a deployment. Additionally, all location names must be unique within a runtime repository. Renaming locations does not change the internal identifier, so an error would still occur if you only re-name the location.
Workaround
ERROR PROCESSING DEPENDENCIES MAY CAUSE DEPLOYMENT TO FAIL (2944626)
A deployment may not be possible if errors occur when processing the dependencies between objects selected for Upgrade. There is a particular problem when renamed objects are deployed with the Upgrade action. This will cause errors to be seen in the Upgrade Impact Report and you will not be able to proceed with the deployment.
Workaround
Upgrade the objects individually with the following strategies:
PROCESS FLOW LOCATIONS FOR WORKFLOW 2.6 NOT UPGRADED CORRECTLY (3027103)
In this release, the Deployment Manager does not correctly upgrade process flow locations for Workflow 2.6.
Workaround
DEPLOY MGR NOT DISPLAYING HISTORY - TWO LOCAITONS WITH SAME NAME IN REPO (3027073)
The Deployment Manager may incorrectly display all objects under a location as New and not previously deployed. This can be caused if there are two or more locations with the same name in the same Design Repository.
Workaround
Rename one of the locations.
FLAT FILE SAMPLE HANGS FOR LARGE EBCDIC FILES (2327414)
Flat file sample wizard may hang during sampling of large EBCDIC files. This is because, currently, when Warehouse Builder samples files, it assumes lines are <CR> delimited and the character set is ASCII.
Workaround
Sample a small representative data sample file before sampling the entire file.
SPECIFYING PATHS FOR LOCATIONS FOR FLAT FILE AND EXTERNAL TABLES (2803476)
When using SQL*Loader mappings, when you define flat file and external table locations that reference a Windows platform, include an additional directory separator following the path such as,
c:\temp\
and not
c:\temp
FETCH-ACROSS-COMMIT IS NOT SUPPORTED BY GENERIC HS COMPONENT OF THE DATABASE. (2585118, 2584812)
When you access non-Oracle Sources via gateways, you may encounter ORA-01002 FETCH OUT OF SEQUENCE ERROR IN PL/SQL. Fetch-across-commit is not supported by generic HS component of the database.
SELECT STATEMENT FOR THE VIEW IS NOT DISPLAYED FOR HSODBC SOURCE (2604966, 2627237)
When views are imported into Warehouse Builder from a non-Oracle Source, such as SQL SERVER, accessing via HSODBC, the SQL statement tab of the View properties does not contain the actual SQL used in creation of the view.
When views are imported into Warehouse Builder from Informix Source via Informix Gateway, the full query text is not returned by the gateway. Only first 64 characters of the query are returned by the gateway.
GATEWAY LOCATION CONNECTION NOT VERIFIED PRIOR TO RUNTIME REGISTRATION (2806240)
When you register a Gateway location in the Deployment Manager or through OMB Plus, Warehouse Builder currently does not verify the connection details.
RTC-5312: ERROR WHILE DEPLOYING A RDB GATEWAY MAP (2981639)
You may encounter error RTC-5312 when executing a mapping that accesses tables using an RDB gateway.
Workaround
To access tables from an RDB gateway, configure each table in a mapping and specify an existing database link to be used to access the object. You can use the dblink property of the mapping and specify a dblink manually outside of Warehouse Builder. This results in a select statement such as
select .... from 'table@dblink'
MATERIALIZED VIEW QUERY REWRITE (1364923)
By default, Warehouse Builder creates unique key constraint on each dimension level and generates a unique key constraint for the dimension table for the lowest or standalone level. Because unique keys allow null values, this can be a problem for materialized view query rewrite. The query is not redirected to the materialized view. The problem is a materialized delta join, which is a join that occurs in the materialized view but not in the query. You must guarantee LOSSLESSNESS for a join in the materialized view you want to discard.
You can do this with a foreign key relationship and a NOT NULL constraint on the foreign key column. Or, you can use an outer join (for the dimension join key column) and a NOT NULL constraint on the join key column in the fact (foreign key column).
Workaround
Open the dimension table properties and change the constraint type to Primary Key for all lowest level and standalone level constraints.
UNPREDICTABLE OUTCOME FOR SET BASED FAIL OVER RUNS TO MULTIPLE TARGETS (1807064)
Where multiple targets are involved, the order of the mappings to those targets is unpredictable, and may vary from one generation to the next for exactly the same mapping. In failover modes, if any of the batch procedures fail, it will skip the rest of the set-based processing. If the mapping has errors for one table but not for the other, it is unpredictable whether the mapping without errors will run in set-based or row-based mode. This has the following implications:
Workaround
Consider running mappings with multiple targets with correlated commit set to true. Review the documentation on correlated commit in the Oracle 9i Warehouse Builder User's Guide.
PARALLEL ROW CODE MAPPING UNPIVOT + FULL OUTER JOIN DOWNSTREAM. DML TYPE TRUNCATE/INSERT (2696005, 2713647)
A mapping may fail to deploy due to an inconsistent data type when a table function is passed to a cursor containing a nested sub-query as a parameter, there are more than three levels of nesting, and the columns with DATE type contain a 'to number clause'. This problem occurs when you set Parallel Row Code to 'true'.
Workaround
Generate mappings with the above characteristics in with Parallel Row Code set to 'false'.
MAPPING WITH TRUNCATE/INSERT OR INSERT AND PARALLEL ROW CODE SET TO YES (2698141, 2706928)
The execution of a table function may fail with internal errors when a cursor referring to a remote table is passed as an argument to the table function. This problem occurs when you set Parallel Row Code to 'true'.
Workaround
Generate mappings with the above characteristics in with Parallel Row Code set to 'false'.
MAPPING CONTAINING A TABLE FUNCTION OPERATOR RETURNING A TABLE OF SCALAR IN SET BASED MODE (2702085, 2708816)
Execution of a mapping containing a Table Function operator, whose outgroup property 'Return Table of scalar' is set to 'True', fails with an ora-22905 error. The issue is with a scalar argument to the table function being called with a PL/SQL variable as the formal parameter.
Workaround
Avoid mappings with the characteristics described above.
INSERT/UPDATE: DIFFERENT NUMBER OF ROWS IN DIFF MODES (2708335, 2711993)
A mapping with a Full Outer Join with load type set to INSERT/UPDATE and generated as a set based MERGE may return the wrong number of rows.
Workaround
Avoid maps with the characteristics described above.
MAPPING CONTAING A TABLE FUNCTION OPERATOR WITHOUT BULK IS GIVING PROBLEMS IN EXECUTION (2711405,2711518,2711545)
Mappings containing a Table Function operator and not set to bulk mode may fail in the execution. This happens especially if the table function associated with TABLE FUNCTION OPERATOR has a pragma autonomous transaction. Also the execution gives problems only in the row based and row based target mode.
Workaround
Set the commit frequency such that there are not frequent commits before end of fetch is reached on the cursor.
EXECUTION OF A MAPPING CONTAINING TWO TABLE FUNCTION OPERATORS APPEARING CONSECUTIVELY (2711518, 2689214, 2690025)
Execution of a mapping containing two Table Function operators in sequence can result in a loop.
Workaround
Avoid using consecutive table functions.
CONSTRAINT PROPERTIES FOR LOADING AND MATCHING NOT UPDATED WHEN RECONCILED (2447219)
Changes to constraint properties, such as primary key column properties, are not updated in mappings during inbound reconcile.
Workaround
UNEXPECTED DATA INSERTED INTO TARGET: MERGE AS SELECT FROM REMOTE SYNONYMS (2721640, 2721852)
Values instead of numbers are generated in results of a mapping when run for the second time. The mapping contains a merge statement that selects from remote tables that are joined. The mapping also contains a group by condition.
Workaround
Simplify the mapping until the problem is no longer exhibited.
PARALLEL ROW CODE = Y - MAPPING RUNS FOR 90 MIN IN ROW MODE AND FAILS (2761711, 2763192)
When the query containing a full outer join is passed as a ref-cursor parameter to the table function, during execution, wrong number of rows is fetched.
Workaround
Avoid mappings that result in full outer join being used as a ref cursor parameter to a table function.
VALIDATION ERROR WHEN PARALLEL ROW CODE NOT GENERATED (2761724)
Warehouse Builder reports Error VLD-1127 or VLD-1125 when a mapping has Parallel Row Code is set to true and Warehouse Builder cannot the generate parallel code due to any of the following restrictions:
Workaround
Set the Parallel Row Code option to false.
The parallel row code mapping configuration option cannot be used in the following circumstances since 'Parallel' code uses a database feature called table functions.
INTERNAL TABLES CANNOT BE CONFIGURED (2062170)
While trying to configure a map which has SAP tables as it's source to generate ABAP code, the configuration properties sub-screen has a parameter 'Use Internal tables' whose default value is 'FALSE'. If the default value of this parameter is changed to 'TRUE' no change will be reflected in the ABAP code that will be generated.
POST MAPPING PROCESS RUNS REGARDLESS OF SUCCESS/FAILURE OF MAPPING (2577706, 2797671)
The mapping return status has one of three values:
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:
DIFFERENT RESULTS IN ALL THREE MODES (2708357, 2712141)
In set based mode, you may see duplicate rows in the target in the case of mappings containing joiner, aggregator, unpivot, lookup and splitter. The same problem may occur in other maps. Also, the mapping will be accessing source tables via DB links. If you see a lot of duplicates being inserted into target, first verify the source data. In particular data that is coming into unpivot must be unique by unpivot key columns.
Workaround
Use row based mode for these maps.
UNIQUE KEY VIOLATED DURING EXECUTION OF SQL*LOADER MAPPING, RESULTS SHOW NO PROBLEMS (2761777)
In previous releases, the DIRECT setting for SQL*Loader mappings defaulted to TRUE. Beginning in this release, the DIRECT setting for SQL*Loader mappings now defaults to FALSE. If you wish to set DIRECT to TRUE to get better performance please read the restrictions on the DIRECT load option in the SQL*Loader documentation.
CHOOSE LEADING SOURCE DIALOG NOT FUNCTIONING PROPERLY (2859423)
When you debug a mapping with a Joiner operator, the Debugger prompts you to select the leading source for the join. In this release, the user interface allows you to cancel the Choose Leading Source dialog without selecting a leading source. This is incorrect. You must select a leading source.
NEW NAMES FOR CUBES, DIMENSIONS, MATERIALIZED VIEWS, AND TABLES NOT PROPAGATED TO IMPACT REPORTS (2970967, 2970970)
In this release you cannot rename Cube, Dimension, Materialized View, and Table operators in Warehouse Builder. If you rename these objects, the new names are not propagated to the Lineage Impact Analysis report.
MAPPING WITH TABLE FUNCTIONS AND CASE OR DECODE STATEMENTS MAY FAIL (2974587, 2974597)
If you design a mapping with a Table Function operator and an Expression operator with the CASE or DECODE expression, the mapping may fail. CASE statements inside a Table Function do not function correctly.
UNIQUE KEY DROP DOWN LIST ONLY SHOWS THE DEFAULT LEVEL UNIQUE KEY (2989450)
Warehouse Builder generates a unique key on the dimension table when you create a level. In the cube wizard and cube property sheet, you can create foreign keys on the fact table to refer to these generated dimension unique keys. In addition, you can create any number of custom unique keys on the dimension table. If you need to refer to these custom unique keys, use the table property sheet of the fact table. To do this, open cube editor, click Launch table property sheet under the Fact menu. Go to foreign key tab to create a foreign key to refer to any generated or custom unique key on the dimension table.
MAPPINGS WITH AQ OPERATOR MIDSTREAM AND PARALLEL SET TO TRUE GIVES INCORRECT RESULTS (2996088)
A mapping may generate incorrect results if it includes an AQ operator midstream and parallel is set to true. The AQ operator is considered midstream if it is neither a source or target but an intermediate operator in the mapping.
Workaround
To use an AQ operator midstream, set parallel to false.
MAPPINGS MAY FAIL TO EXECUTE OR DEPLOY ON ORACLE DATABASE 9.2 (3011029)
Some mappings may fail to execute or deploy on Oracle 9.2 without the appropriate patches. This occurs, for example, in mappings that generate a MERGE statement.
Workaround
Apply 9.2 PatchSet 3 to your Oracle 9.2 instance.
MDL EXPORT FROM SCRIPTING OR COMMAND LINE MDL
Create a MDL Control file and specify the keyword SUPPORTEDLANGUAGESID to export the Other (supported) Languages in the MDL data file. For example, the wildcard indicates to export all other languages in the following:
SUPPORTEDLANGUAGESID=*
If you have a specific language to export (e.g., repository contains more than one supported language), then specify the language ISO id such as the following for Spanish:
SUPPORTEDLANGUAGESID=es_ES
Below is an example of the OMBEXPORT command using a MDL control file:
OMBEXPORT TO MDL_FILE 'd:/mdl/exp1.mdl' FROM PROJECT 'MY_PROJECT' CONTROL_FILE 'd:/mdl/parameters.ctl' OUTPUT LOG TO 'd:/mdl/exp1.log'
Exporting the Other (supported) Languages from the OWB client (Metadata Export) is not available.
9.2.0.3.1 OLAP SERVER PATCH DEPENDENCY FOR OLAP (2774351)
To use the OLAP Analytical Workspace with Warehouse Builder, you need to apply the Oracle database 9.2.0.3.0 patch, patch #2897078 for Windows or patch # 2761332 for Sun Solaris. You also must apply patch OLAP 9.2.0.3.1.
CWM2 IN OLAP DOES NOT SUPPORT HIERARCHIAL AND LIST DIMENSIONS (2978324)
CWM2 in OLAP does not support dimensions of type hierarchical and list. A dimension must be one type or the other. In this release, Warehouse Builder gives no warning of this when you design, validate, or deploy dimension. If you execute the bridge, the dimension can be cloned in the AW. If the OLAP API is enabled, only one type will be projected.
PERF: OEM JOB EXECUTION PERFORMANCE ISSUE (2614173)
When executing jobs through OEM there is a significant delay between the job actually completing as seen in OEM console and the runtime platform being notified by OEM that the job has completed. The job completes successfully, but there is a 50 second delay.
Workaround
Wait a minute or two for the notification.
OMB PLUS RETURNS EXCEPTION ERROR AND HANGS WHEN DOUBLE QUOTES ARE NOT MATCHED IN A REGULAR EXPRESSION. (2778229)
Due to a known issue in Jacl, OMB Plus can return an exception and then hang. This occurs when the double quotes in a string are not matched by a regular expression.
OMB Plus returns the following exception:
Exception in thread "main" java.lang.StringIndexOutOfBoundsException: String index out of range: -1
Workaround
In the script always match the double quotes in the regular expression.
GENERATING DIMENSION SCRIPTS IN OMBPLUS OVERWRITES THE DIM-TABLE SCRIPT (2804168)
Problem: If you use the OMBCOMPILE or OMBDEPLOY script to save the scripts for a Dimension, the script for the Dimension will overwrite the script for the table implementing the Dimension. This is because both the Dimension and the Table have the same file name.
Workaround
Use the UI to store the Table script as a different file name, e.g. product_table.ddl.
PROCESS FLOWS NOT AVAILABLE FOR USE WITH ORACLE 8.1.7 DATABASE
Due to limitations in the Oracle 8.1.7 database, you cannot deploy process flows to that version of the database.
PASTE NOT AN OPTION WHEN COPY PROCESS FLOW FROM ONE PROJECT INTO ANOTHER (2803158)
Although you can copy a process flow, you cannot paste the process flow into another project. This is because the reconcile option is not available for a process flow in this release.
PROCESS FLOW HANGS WHEN THE PROCESS FLOW INCLUDES A MAPPING OR EXTERNAL PROCESS WITH THE SAME NAMES AS THE PROCESS FLOW (2823721)
A process flow hangs when you attempt to execute a mapping activity or external process activity with the same name as the process flow that contains it.
Workaround
For reliable deployment and execution, assign unique names to all process flows, mappings, and external processes deployed to the same runtime platform. Rename either the process flow or the mapping or external process. If you rename the mapping, you must delete the mapping activity from the process flow and add the newly renamed mapping activity to the activity.
The Oracle Net Service field has been added to the following pages:
For the field, type the tnsname for the database. The tnsname contains the Service Name in the tnsnames.ora file. Maximum Length: 30 Characters.
Database locations can be defined using either Host Name, Port Number and Service Name or using Net Service Name and Service Name. Net Service Name is a name that is defined in your tnsnames.ora file. A Net ServiceName should be defined in the appropriate Oracle Home. For example, to deploy to a location identified by Net Service Name the name should be defined in the Oracle Home of the Runtime Platform Service. Database links are generated in the form <service-name>@<connector-name>. If you have global-names set to true, it is important that the service-name you specify for the location matches the global-name of the database you want to link to.
DO NOT REMOVE LAST NODE FROM RUNTIME AUDIT BROWSER REPORT (3028355)
In the Runtime Audit Browser Service Node Report, do not remove the last node from the list. In this release, you cannot use the Add Node button if the list is empty. Please contact Support if you inadvertently remove the last node from the list.
PRE-MODEL AND POST-MODEL TRIGGERS FOR SQL*LOADER (1524760)
Pre-model and post-model triggers for SQL*Loader do not function correctly.
Workaround
You can define an external process for the function that you wanted in the pre or post mapping triggers and use OEM or Workflow to call the external processes before or after the SQL*Loader mapping.
THE CONFIG PARAMS FOR NAME AND LOCATION OF SQLLOADER CONTROL AND LOG FILE (2793993)
Using the Configuration Properties sheet, it is possible to specify the name and location for a SQL*Loader Control file and its Log file. Any values specified against these Configuration properties will not have any effect and the Runtime will use default values.
WAREWHOUSE UPGRADE CANNOT DELETE AN INDEX (1477144, 1668554)
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.
PARTITION VALUES AND WAREHOUSE UPGRADE SCRIPTS (1811047)
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.
CANNOT MINIMIZED WAREHOUSE BUILDER BROWSER PORTLETS ADDED TO ORACLE9iAS PORTAL (2429528)
OWB Browser portlets cannot be minimized. The COLLAPSED portlets feature is only supported from 9iAS version 9.0.2 and higher.
RESTRICTIONS FOR USING LINEAGE IMPACT ANALYSIS REPORTS
Lineage Impact Analysis reports do not work on an Oracle 9.0.1 instance if the original XML toolkit (version 9.0.1) is installed. Make sure a higher version is installed in the SYS schema. This problem does not occur in 9.0.2.
Lineage Impact Analysis reports do not work on an Oracle 9.0.1 instance if the Warehouse Builder repository is installed into a non-default tablespace with Locally Managed and Segment Management Clause set to AUTO. The reports do work in Warehouse Builder repository is installed into a default tablespace.
Install the Warehouse Builder Browser schema into a iAS instance, not the Warehouse Builder Repository instance.
Due to limitations in Oracle 8i and 9i Release 1 of the database, when applying the style sheet, the Warehouse Builder XML Toolkit is limited by memory of the JVM process in the server. It is advisable to use XML files, less than 10MB, that require no style sheet or use a simple style sheet. Larger XML files can be handled if the document splitter feature is utilized, otherwise use SQL*Loader. In Oracle 9.2 of the database, the XML features will alleviate these issues.
None.
2848011 MAPPINGS WITH ADVANCED QUEUES DO NOT HAVE DEBUGGING SUPPORT.
2897320 DEBUGGER DOES NOT DIRECTLY SUPPORT MAPPINGS WITH NON-ORACLE SOURCES
2882376 DEBUGGING MAPPING WITH FLAT FILE SOURCE GIVES JAVA EXCEPTION
2894924 CANNOT DEBUG MAP WITH TABLE AS BOTH SOURCE AND TARGET
2899915 JNPE IN DEBUGGER AFTER ADDING OPERATOR TO MAP FOLLOWED BY INITIALIZATION
2903483 MULTIPLE NA MAPS FAIL TO EXECUTE WHEN AUTOSHUTDOWN IS TRUE
2896624 DEPLOY RESULTS OF A SQL LOADER MAPPING ARE NOT DISPLAYING CORRECTLY
2709446 UPGRADE OF RENAMED TABLE CONTAINING CONSTRAINTS FAILS- CONSTRAINT NOT UNIQUE
2872198 MAPPING TO SECOND RECORD OF TARGET FILE GIVES ERROR
2443195 CONFIGURE DIALOG FOR SEQUENCES DOES NOT ALLOW START VALUE GREATER THAN SIX DIGITS
2552773, 2563523 ENHANCEMENT FOR STAGELESS PEL
2790711 UNEXPECTED BEHAVIOR WHEN ASSIGNING PARTITION KEYS
2798143 INCORRECT VALIDATION MESSAGES, CHANGES TO MAPPING ARE LOST
2802888 EXPRESSION BUILDER FAILS ON BOOLEAN CONTEXT VALIDATION FOLLOWED BY NON-BOOLEAN CONTEXT
2830837, 2830726 SAP SOURCE TABLES CANNOT BE ACCESSED IN THE DEBUGGER
2876044 PROCESS FLOW UDPS WITH STRING VALUES ARE NOT PERSISTED USING THE UI
2878439 USER DEFINED PROPERTIES DO NOT GET PROPAGATED INTO BROWSER
2889334 RUNTIME AUDIT BROWSER INCORRECTLY STATE ROWS SELECTED TO ZERO
2902349 MAPS WITH PARALLEL ROW CODE SET TO 'YES' FAIL IN DEPLOYMENT
2911829 PRE-DEFINED PUBLIC TRANSFORMATION WB_OLAP_LOAD_DIMENSION FAILS TO LOAD DATA
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle Corporation is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/
|
|
Copyright © 2003, 2003 Oracle Corporation. All Rights Reserved. |
|