| Oracle® Business Intelligence Applications Release Notes for Oracle Data Integrator Users Version 7.9.5.2 Part Number E14208-05 |
|
|
View PDF |
| Oracle® Business Intelligence Applications Release Notes for Oracle Data Integrator Users Version 7.9.5.2 Part Number E14208-05 |
|
|
View PDF |
These release notes describe known issues and workarounds for Oracle Business Intelligence Applications Version 7.9.5.2, and contain the following sections:
These release notes are updated periodically as new information becomes available. To ensure that you are reading the latest version of the release notes, check the Oracle Business Intelligence Applications Documentation Web site:
This section describes general issues and workarounds for Oracle Business Intelligence Applications products. It contains the following topics:
For certification information, refer to the System Requirements and Supported Platforms for Oracle Business Intelligence Applications for Oracle Data Integrator Users document. This document is part of the Oracle Business Intelligence Applications documentation set. It is also available from the following location:
This section provides release notes on installing and upgrading Oracle Business Intelligence Applications. It contains the following topics:
The Oracle Business Intelligence Applications installer requires the Oracle Business Intelligence Administration Tool to be installed on the installation machine. When installing Oracle BI Administration Tool or Oracle BI Enterprise Edition, you may choose to override the default names for the directories 'OracleBI' and 'OracleBIData'. However, if you include the characters, 'period' (.) or 'underscore' (_) in the directory names, the Oracle Business Intelligence Applications installation process throws an error, although these characters are legal in Windows directory names.
Workaround
Oracle recommends that you use the default directory names, (that is, 'OracleBI' and 'OracleBIData'). If you do not use the default directory names, avoid using periods and underscores in the directory names that you use.
This section provides corrections for the documentation set for Oracle Business Intelligence Applications. It contains the following topics:
All of the document corrections in this section are for Chapter 4, "Installing and Setting Up Oracle Business Intelligence Applications."
Privileges Provided to User DATA_BIAPPS
In section 4.3.3.1, "Creating the Required Databases and Tablespaces," Table 4-1 lists the required database users and tablespaces and the required privileges.
Because DATA_BIAPPS is granted with any privileges, it is recommended that there be no other schemas in the same instance as DATA_BIAPPS with data not meant for Oracle Business Intelligence Applications. In addition, for user DATA_BIAPPS, the privilege "CREATE ANY DIRECTORY" is listed. This privilege is not required for user DATA_BIAPPS.
Incorrect Description of BIAPPS_ODI Folder Structure
In section 4.4.2.2, "How to set up the Oracle BI Applications files for ODI," Step 4 describes the new directories that are created in the $ODI_HOME\oracledi\ directory when you unzip the biapps_odi.zip file. This section incorrectly notes the following directory structure:
\biapps_odi\odifiles\dbfiles\
This should read as \biapps_odi\dbfiles.
The following directory is also created on unzipping the file:
\biapps_odi\logs
Executing Gen Scenarios Procedure
Section 4.5.6, "How to generate the required ODI Scenarios," describes how to generate the ODI Scenarios. The Gen Scenarios procedure may take a few hours to execute. The time varies depending on the hardware, the proximity of the repository database from the ODI client, and network bandwidth.
Step 7 of this section requires that you verify the sessions that were run as part of the Gen Scenarios procedure. The screenshot shows an incorrect list of sessions.
The sessions that should show as completed successfully after the Gen Scenarios procedure is executed are:
Procedure - Gen Scenarios - Generate Scenarios
Procedure - Gen Scenarios - Create Scenario Folders
Procedure - Gen Scenarios - Organize Scenarios
User Should Change Default Password for BI Repository
In section 4.4.1, "How to Run the Oracle Business Intelligence Applications Installer (Windows)," a note at the end of this section provides information about the credentials for the OracleBIAnalyticsApps.rpd file provided with Oracle BI Applications. The default username and password are Administrator/SADMIN.
You should change the default password. Use the Oracle Business Intelligence Administration Tool to do so. For instructions, see the Oracle Business Intelligence Server Administration Guide.
Starting Oracle WebLogic Configuration Wizard Section
In section 4.5.8.3 "How to Set Up Oracle BI Applications Configuration Manager on Windows", Step 4.a should read:
4a. Launch the Oracle WebLogic Configuration Wizard by selecting Start > Programs > Oracle Fusion Middleware 11.1.1.0.1 > Weblogic 10.3 > Tools > Configuration Wizard.
Configure and Activate Automated Delete Handling Section
In section 4.6.6 "How to configure and activate Automated Delete Handling", the sentence preceding step 1 should read:
To configure and activate Automated Delete Handling:
Reference to One-off Fixes Folder
In section 4.6.2.1.4 "About the Utilities folder", the \Utilities\ folder in the screenshot should not include a sub-folder called 'One-Off Fixes'.
Section 4.1 About Oracle Business Intelligence Applications Topologies
In Section 4.1, the notes beneath Figure 4-1 contain the following errors:
References to MACHINE C should be to MACHINE D. MACHINE C is not included in the diagram.
References to MACHINE D should be to MACHINE E.
References to MACHINE GROUP E should be to MACHINE GROUP F.
The notes beneath Figure 4-1 should read:
Installation Tier
– MACHINE A (Windows-only)
MACHINE A is a machine that has installed Oracle Business Intelligence Administration Tool, on which you run the Oracle Business Intelligence Applications installer to install the Oracle Business Intelligence Applications files. You can also install Oracle Business Intelligence Applications on a machine that has installed Oracle Business Intelligence Enterprise Edition. When the Oracle Business Intelligence Applications installation is complete, you manually copy the following files from the installation machine (MACHINE A) to the Business Intelligence Deployment Tier (MACHINE GROUP F), as follows:
- You manually copy the OracleBI\Server\Repository\OracleBIAnalyticsApps.rpd file from MACHINE A to the machine that runs the BI Server in MACHINE GROUP F.
- You manually copy the OracleBIData\Web\Catalog\EnterpriseBusinessAnalytics\*.* files from MACHINE A to the machine that runs the BI Presentation Services Catalog in MACHINE GROUP F.
Note: You typically develop the RPD and Presentation Catalog and perform customization changes to fit your business requirements.
- You manually copy the biapps_odi.zip file from MACHINE A to the Oracle Data Integrator machine (that is, MACHINE B) and unzip the file into the \oracledi\ directory.
- You manually copy the Oracle BI Applications Configuration Manager files in the \OracleBI\dwrep\biapps_configmgr\ directory from MACHINE A to the Oracle Data Integrator machine (that is, MACHINE B).
E-LT Tier (Functional)
– MACHINE B (Windows, Unix, Linux)
MACHINE B is a machine on which ODI is installed, and which runs the ODI production environment (for example, ODI tools, ODI Agents). You manually copy the biapps_odi.zip to this machine, and unzip the file into the \oracledi\ directory. In addition, you manually copy the Oracle BI Applications Configuration Manager files in the \OracleBI\dwrep\biapps_configmgr\ directory from MACHINE A to this machine.
– MACHINE D (Windows, Unix, Linux)
MACHINE D is a machine that hosts the transactional (OLTP) database.
– MACHINE E (Windows, Unix, Linux)
MACHINE E is a machine that hosts the Oracle Business Analytics Warehouse database.
BI Deployment Tier (Functional)
– MACHINE GROUP F (Windows, Unix, Linux)
MACHINE GROUP F is a group of machines that runs the Oracle Business Intelligence Enterprise Edition components, which are used to deploy the business intelligence dashboards. For example, one machine might run the BI Server and BI Applications RPD, and another machine might run the BI Presentation Services and the Oracle Business Analytics Warehouse.
Section 6.2.1 How to Deploy Stored Procedures
The task in this section does not apply to Oracle Business Intelligence Applications Version 7.9.5.2. The SQL files mentioned in this task are not part of an Oracle Business Intelligence Applications Version 7.9.5.2 installation.
This section provides release notes for Oracle Business Intelligence Applications in general. It contains the following topics:
Section 1.3.2, "Lack of Time Zone Setting Prevents Delivery of iBots to Applications Users"
Section 1.3.3, "Issue with Exchange Rates and Transaction Currencies"
Section 1.3.5, "Installation Errors with Oracle Applications Server Advanced Security Option"
Section 1.3.7, "Column Heading Not Aligned When Editing Parameters"
Section 1.3.11, "Error: task SDE_ORA_PAYROLLFACT failed with error ORA-01722:invalid number"
Section 1.3.12, "Installing Oracle Data Integrator on Unix or Linux"
Section 1.3.13, "Invoking Oracle Data Integrator Scripts on Unix or Linux"
Section 1.3.14, "Specifying the ODI_HOME Environment Variable On Unix/Linux Platforms"
Section 1.3.15, "How to Secure the Employee Dimension in Oracle HR Analytics"
The Oracle Business Intelligence Delivers iBots use a predefined query against the SA System subject area to retrieve a list of applications users who are associated with the iBot's Recipient Group. When an iBot is run, this predefined query will fail with an error message that is similar to the following one:
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 27005] Unresolved column: "Time Zone".
The query error prevents the Oracle BI Delivers iBot from generating and delivering any content for the applications users that are associated with the iBot's Recipient Group. This impacts all iBot destination types including Interactive Dashboards and Emails and Disconnected Application cache generation for Oracle Business Intelligence Disconnected Analytics. The issue occurs because the 'Time Zone' presentation column name is incorrectly spelled as 'Timezone' in the SA System subject area.
To work around this issue use the Oracle Business Intelligence Administration Tool to change the name of the existing 'Timezone' presentation column in the SA System presentation catalog to 'Time Zone'.
For information on the SA System subject area, see the Oracle Business Intelligence Server Administration Guide.
The Oracle BI Delivers iBots use a predefined query against the SA System subject area to retrieve a list of applications users who are associated with the iBot's Recipient Group. When an iBot is run, users who do not have a time zone specified in user preferences are considered invalid users and iBots are not delivered to them.
This issue occurs because the join type for the S_TIMEZONE join in the S_USER Logical Table Source in the SA System Business Model is defined as INNER when it should be defined as RIGHT OUTER.
To work around this issue, perform these steps:
Display the Oracle Business Intelligence Administration Tool.
In the Business Model and Mapping layer, expand the SA System Business Model and the USER Logical Table.
Double-click the S_USER Logical Table Source under Sources in the USER Logical Table.
In the Logical Table Source - S_USER Dialog Box, change the type to RIGHT OUTER from INNER for the S_TIMEZONE join in the Joins section of the General tab.
For information on the SA System subject area, see the Oracle Business Intelligence Server Administration Guide.
Current design and support of multiple currencies within the Oracle BI Applications and the data warehouse assumes that the transactional system (or OLTP system) provides exchange rates and table structures that store exchange rates.
If the OLTP system does not provide exchange rates from the 'transaction currency' to the chosen 'one or more data warehouse currencies', then the Fact table will have a null exchange rate value for 'transaction' currency to 'Global1' currency, and hence, analysis based on Global currencies will not be possible for these transactions. It also impacts the correctness of the data for data that resides in various aggregate tables. This issue is also seen in the other two supported currencies (Global2 and Global3).
To work around this issue, ensure that the OLTP system has all currency exchange rates from all possible transaction currencies added to all the three chosen data warehouse currencies, up front. If this is not taken care of beforehand and you encounter a missing exchange rate issue, then you can rerun transactions in 'full' mode after you have fixed the missing exchange rate issue in the OLTP system.
The user name that appears in the Greetings message in the Oracle Business Intelligence Interactive Dashboards does not display correctly. The variable DISPLAY_NAME used in the Greetings message in the dashboard header gets populated through an Initialization Block called LOGIN Properties. Out of the box, the connection pool and SQL statements used in this init block point to the Siebel OLTP. You need to change the Connection pool and data source SQL for the Initialization Block: LOGIN Properties for Oracle EBS as a source, as described below.
The solution to this issue is:
Open the EnterpriseBusinessAnalytics.rpd file using Oracle BI Administration Tool.
Navigate to Manage > Variables to open the Variables Manager.
Under Session > Initialization Block, select the 'LOGIN Properties' initialization block.
Double-click to open the properties dialog box.
Click on the Edit Data Source button.
Click on the Browse button.
In the Select Connection Pool window, select Oracle EBS OLTP Connection Pool.
In the Default Initialization String box on the 'Session Variable Initialization Block Data Source - LOGIN Properties' window, enter the SQL as appropriate for your source system application and the database platform it is running on.
Table 1-1 Required SQL Strings For Each Source System Application And Database Combination
| Source System Application (and Database Platform) | SQL required for Default Initialization String |
|---|---|
|
Oracle EBS (Oracle RDBMS) |
Select PER.FULL_NAME, 0 from PER_ALL_PEOPLE_F PER, FND_USER USR WHERE USR.USER_NAME= ':USER' AND USR.EMPLOYEE_ID=PER.PERSON_ID AND (SYSDATE <= USR.END_DATE OR USR.END_DATE IS NULL) AND PER.EFFECTIVE_START_DATE <= USR.START_DATE AND (USR.START_DATE < PER.EFFECTIVE_END_DATE OR PER.EFFECTIVE_END_DATE IS NULL) |
When installing Oracle Business Intelligence Applications on top of an installation of the Oracle Business Intelligence Enterprise Edition that was installed using the Oracle Applications Server advanced security option, the following error message will be displayed:
"Password length is less than the required minimum, 8"
Oracle Business Intelligence Applications installation will abort and the OracleBIAnalyticsApps.rpd file will be corrupted.
The error happens because the MINIMUM_PASSWORD_LENGTH setting in the NQSConfig.ini file was set to 8 by the OBIEE installation. The workaround is to change the value of MINIMUM_PASSWORD_LENGTH to 0 in NQSConfig.ini, install Oracle Business Intelligence Applications, then change the value back to 8.
In Oracle BI Applications Configuration Manager > Administer Execution Plans, create a new Execution Plan record by copying an existing Execution Plan. The focus does not shift to the newly copied Execution Plan record.
In Oracle BI Applications Configuration Manager > Administer ELT Parameters, the column headings may not be aligned to the columns displayed in the Parameters table when a user double-clicks on a Parameter record to edit the value. This mis-alignment does not prevent editing of the Parameter value.
The Sort Order functionality in Oracle BI Applications Configuration Manager > Parameters Administration > Application Specific tab does not work correctly. Clicking on the sort icons in the column headings does not sort the rows in either ascending or descending order.
In Oracle BI Applications Configuration Manager > Monitor Executions page, click on the Create New Session icon. The Execute Package Structure dialog displays a dropdown box with the list of Execution Plans to select from. The Execution Plans dropdown displays a maximum of 25 Execution Plans. If there are more than 25 Execution Plans defined in the Administer Execution Plans page, the additional execution plans do not display in the dropdown.
To workaround this limitation, start the executions from the Administer Execution Plans page > Package Structure tab by selecting the desired Execution Plan record in the Execution Plans top pane and clicking on the Execute icon in the Package Structure tab of the bottom pane.
In Oracle BI Applications Configuration Manager, create multiple connections to different environments in the Manage Connections page. Log out of Oracle BI Applications Configuration Manager, and log in.
In the login page, specify user, password and select any connection except the first from the Connection dropdown. Oracle BI Applications Configuration Manager attempts to connect to the first connection in the list.
Users may receive invalid logon errors as Oracle BI Applications Configuration Manager attempts to authenticate the supplied username and password against the first environment.
If the credentials can be authenticated, Oracle BI Application Configuration Manager will connect to the first environment, instead of the environment selected in the dropdown.
This behavior happens only for the first login after multiple connections have been defined.
In order to workaround the issue, close the browser if an invalid logon error is received, or log out of Oracle BI Application Configuration Manager if the connection was made to the first environment. Open a new browser window, launch Oracle BI Applications Configuration Manager and select the desired connection from the dropdown.
If you have deployed Oracle Human Resources Analytics in a non-ENU environment, you may receive the following error:
Task SDE_ORA_PAYROLLFACT failed with error ORA-01722:invalid number
The following mappings are affected:
SDE_ORA_EmployeeDailySnapshotFact_1.W_EMP_DAILY_SNP_F_1_TMP.ACCR_VAC_HRS
SDE_ORA_PayGradeDimension.W_PAY_GRADE_DS.PG_MAX_HRLY_AMT
SDE_ORA_PayGradeDimension.W_PAY_GRADE_DS.PG_MID_HRLY_AMT
SDE_ORA_PayGradeDimension.W_PAY_GRADE_DS.PG_MIN_HRLY_AMT
To address this error, start Oracle Data Integrator Topology Manager, and display the Contexts tab. For each defined Context, navigate to the FlexFields tab. Set the NUMBER_EXTRACT_FORMAT FlexField to the format string used to represent numbers when these are stored in VARCHAR2 fields in the data sources associated with this context.
For example:
If you are sourcing using an instance of eBusiness Suite based in the US, you will likely use: 999999999999999.99.
If the source is based in Germany, you might use 999999999999999,99.
Note:
You should not encapsulate this string with single quotes.In a typical Oracle Data Integrator installation on Unix or Linux, the command to invoke the ODI Designer tool fails with this message:
/scratch/odi/odi10.1.3.5.0/oracledi/bin/designer.sh: line 23:
/bin/odiparams.sh: No such file or directory
Workaround
Before installing Oracle Data Integrator on Unix or Linux, create an environment variable called ODI_HOME. The ODI_HOME variable should point to the folder /oracledi/.
In a typical Oracle Data Integrator installation on Unix or Linux, ODI scripts will fail if you have not first changed the working directory to oracledi/bin ($ORACLE_HOME/bin).
Workaround
Before invoking any of the SH scripts that are installed with ODI (for example, designer.sh, topology.sh, security.sh, mimport.sh, or agent.sh), change the working directory to oracledi/bin ($ORACLE_HOME/bin).
When you install Oracle Business Intelligence Applications Version 7.9.5.2 on Unix or Linux platforms, you must create an environment variable called ODI_HOME that is set to the location of the \oracledi\ folder.
Oracle HR Analytics secures user data access using security filters applied to fact tables. These security filters restrict a user's access to a subset of the data based on his or her security profile by the securable dimensions e.g. organization, supervisor hierarchy, or business group. As delivered, the Employee dimension itself is not a securable dimension. This means that when a user browses the Employee dimension directly without selecting a metric that is secured by one of the securable dimensions, he or she will see all people in the Employee dimension regardless of his/her security access. However, it is important to point out that a user's data security will be applied when the user includes one or more metrics along with the Employee dimension attributes. By combining metrics with the Employee dimension, it indirectly secures the Employee dimension through the logical join between Employee dimension and the secured fact tables.
However, occasions might arise that require securing the Employee dimension so that a user can only view people within his/her security access when he/she browses the Employee dimension directly. Customers can decide to secure the Employee dimension during implementation.
Workaround
For instructions on how to secure the Employee dimension, please refer to Tech Note How to Secure Employee Dimension in OBIApps 7.9.6 and 7.9.6.1 (Doc ID 948928.1) that is available at My Oracle Support.
|
 Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
