|Oracle® Retail Data Model Release Notes
10g Release 2 (10.2)
Part Number B32407-04
10g Release 2 (10.2)
Known issues in the current release of Oracle Retail Data Model are documented in the following sections:
This release contains several fixes to Intra-ETL that significantly improve Intra-ETL performance. The changes to Intra-ETL are described in bugs 8393457. 8393467, 8536971, 8562335, 8562916, and 8569785.
The following issues exist regarding using Oracle Retail Data Model with Oracle Database 11g:
When using Oracle Database 126.96.36.199, the deinstallation option for Oracle Retail Data Model is greyed out in Oracle Installer.
This issue is documented with Oracle bug 8272088
The OLAP component of Oracle Retail Data Model is certified with Oracle Database 10g Release 2 (10.2.0.3 and higher) and Oracle Database 11g Release 1 (188.8.131.52 and higher).
The details relating to the certification of Oracle Retail Data Model OLAP Option of Component are as follows:
The Oracle Retail Data Model Installation Guide lists the certified versions of Oracle OLAP (and AWM).
The OLAP component of Oracle Retail Data Model contains two different code bases for the 10g and 11g versions of the Database. These two sets of sources are present in different folders (directories) in the shiphome and are used as described in the database version-specific install process outlined in the Oracle Retail Data Model Installation Guide.
The OLAP component of Oracle Retail Data Model that is installed for use with Oracle Database 11g Release 1 was developed with the OLAP cube type setting of
11g. However, some OLAP features of Oracle Database 11g Release 1 (for example, Query Rewrite using Cube-based Materialized Views and automatic refresh of cubes from relational tables) are not available in this release of Oracle Retail Data Model. These OLAP features are planned in the next release.
The OLAP Dashboard for Oracle Retail Data Model functions against either version of the Database (that is, Oracle 10g Release 2 or Oracle 11g Release 1). Access to the Database from OBIEE (front-end, mid-tier) is the same as the Oracle Database 10g Release 2 mode of access of Oracle OLAP cubes from OBIEE.
The following issues exist when using the OUI Installer or online Help for Oracle Retail Data Model:
readme.txtfile displays on the last screen of the Installer
After installation, the OUI Installer automatically shows the Oracle Database
readme.txt file on the last screen. It does not show information specific to Oracle Retail Data Model
This issue is tracked with Oracle bug number 8284660.
Selecting Help by clicking a Help button on the OUI Installer dialogs does not display a Help topic that is specific to a displayed Oracle Retail Data Model dialog. Instead, selecting Help in this manner always displays the Help topic that is the introduction to Oracle Retail Data Model.
Non-ASCII characters on Help Navigator may display garbled for most Java GUI conventional components on Linux 4.0. The problem only impacts Help Navigator tree; it does not impact the Help topic window.
This issue is tracked with Oracle bug 6503286 which also provides a workaround.
Oracle Retail Data Model provides relational implementation of out-of-stock prediction through the use of a model SQL function. The Intra-ETL that transforms the base model to the relational out-of-stock model is now included with the Oracle Retail Data Model package.
The following tables have been renamed and synonyms for the original table names have been created.
|Original Table Name and New Synonym Name||New Table Name|
Note:Do not delete the synonyms even if this is the first time you have installed Oracle Retail Data Model.
This issue is documented with Oracle bug number 8227932.
Oracle Retail Data Model has the following known issues relating to the Relational, Data Mining and OLAP components:
See also:Oracle OLAP Certification
Oracle Retail Data Model OLAP cubes are populated through SQL scripts that use the
RBIA_OLAP_ETL_AW_LOAD package that is provided with the OLAP component to load data from relational tables (defined by the
bia_rtl schema) into the OLAP cubes in the PSLSINV analytic workspace (defined by the
As discussed in Oracle Retail Data Model Reference, Oracle Retail Data Model provides you with a script to perform the initial load of the OLAP cubes. This script (sometimes called the OLAP cube "historical load script" or "initial load script") starts from a "clean slate" (that is, an empty analytic workspace). It not only populates the Sales and Inventory cubes, but also generates forecasts into the Sales Forecast and Inventory Forecast cubes, and, then, aggregates those forecast cubes. Oracle Retail Data Model performs this forecasting using two generic OLAP DML forecast programs,
FORECAST_STOCK_INV present in the PSLSINV analytic workspace. By default, these programs generate the forecasts for Year 3 (
BSNS_YR_2007) based on the input data for Year 1 (
BSNS_YR_2005) and Year 2 (
BSNS_YR_2006). These programs run on a per store, per product, per day (period) basis.
To perform incremental loading of OLAP cubes you need to write your own incremental load script using the subprograms of the
RBIA_OLAP_ETL_AW_LOAD package documented in Oracle Retail Data Model Reference. If you want that incremental load script to perform forecasting, then it must contain OLAP DML
CALL commands to execute OLAP DML forecasting programs.
When creating forecasts to run intermittently, the main points to consider are the frequency with which you want to run the forecasts and the duration of future time periods over which you want to forecast. For example, you could schedule the forecasts to execute every month and use the same forecasting time periods as those used by the historical load script. In this case, you could decide to have the intermittent forecasts overwrite the data in the forecast cubes. On the other hand, you could forecast more frequently, in which case, to avoid overlapping forecasts, you could create new forecasting programs and new measures to hold the intermittent forecasts.
When refreshing the materialized views, users may experience some abnormal disrupts due to Oracle bug 7330434. This issues is also recorded in ORDM bug 8276387. This may happen during installation or Intra-ETL execution.
Oracle Retail Data Model has the following known issues related to translation:
Oracle Retail Data Model supports only one language per instance at this time for Lookup seed data translation.
Some labels and text in certain areas of on the sample BIEE reports are not translated. For example, the webcat contents under
/shared are translated, while those under
/users are not translated.
The lookup messages described in the following table are not translated in the 10.2.1.0.0 release. This issue is documented with Oracle bug number 8267819.
|Lookup Type||Lookup Category||Lookup Code||Untranslated Description|
|DWL_TRX_TYP||POSCNTRL||SUSPEND||POS Control Transaction
|DWL_TRX_TYP||POSCNTRL||RESUME||POS Control Transaction
These are the issues related to sample reports and dashboards:
See also:Translation issues.
The reports and dashboards that are used in examples and delivered with Oracle Retail Data Model are provided only for demonstration purposes. They are not supported by Oracle.
Some reports that display currency data fail on the dashboard when used with OBIEE 10.1.3.4. They display the following error:
Invalid Handle Of 'PKN3saw8CurrencyE' Exception.
This issue is documented with Oracle bug number 8267842.
Edit the report:
Select Page Options, then select Edit Dashboard.
Select Properties, then select Modify Request.
Set the format of column that is not displaying properly to the default format.
Save the Report.
Go to Dashboard.
Edit the report:
Select Page Options, then select Edit Dashboard.
Select Properties, then select Modify Request.
Set the format of the column back to Currency data type.
Login into dashboard as
Select Answers, then RBIA, then Campaign, then Campaign Key.
Add Campaign Key onto the report.
Show results for the answers fails with the following error.
Error: Status: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: Campaign.Campaign Code.
The solution to this problem is to fix the metadata consistency warnings (that is, the problem stated in
In BIEE Administrator, open the reports metadata file (that is, the RPD file).
Select File, then select Check Global Consistency.
Check the result of Step 2. Fix the warnings.
The following features are not included in this release:
The Parser from Flexible Hierarchies to Named Dimensions
The 4690 POS Collector
Sample POS Loss Report
This release of Oracle Retail Data Model also fixes the following bugs:
Bitmap index corrected (bug number 8393431)
Foreign key added to DWB_CUST_SRVC_RQST (bug number 8575533)
Correction to DWD_POS_CONTRL (bug number 8562335)
Data type correction (bug number 8562448)
Partition option now creates partitions for all tables (bug number 8536859)
Missing DAY_KEY added to derived tables (bug number 8508075)
Corrected target table column name (bug number 8289087)
The Oracle Retail Data Model Operations Guide, new at this release, describes how to create and maintain a data warehouse based on the Oracle Retail Data Model. Operations information that was in the Oracle Retail Data Model Installation Guide and the Oracle Retail Data Model Reference is now in this new manual, along with additional information.
You can find the most recent documentation for Oracle Retail Data Model on the Oracle Technology Network Documentation Web site at
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. 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. Accessibility standards will continue to evolve over time, and Oracle 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 more information, visit the Oracle Accessibility Program Web site at
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Deaf/Hard of Hearing Access to Oracle Support Services
To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at
http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is available at
Oracle Retail Data Model Release Notes, 10g Release 2 (10.2)
Copyright © 2009, 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 software or related documentation 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 USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software 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 which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Oracle Retail Data Model is based on the ARTS 5.0 standard.