| Oracle® Business Intelligence Data Warehouse Administration Console Release Notes Release 10.1.3.4.1 Part Number E12655-10 |
|
| View PDF |
| Oracle® Business Intelligence Data Warehouse Administration Console Release Notes Release 10.1.3.4.1 Part Number E12655-10 |
|
| View PDF |
Release Notes
Release 10.1.3.4.1
E12655-10
October 2012
These release notes describe known issues and workarounds for the Oracle Business Intelligence Data Warehouse Administration Console releases 10.1.3.4 and 10.1.3.4.1.
The Oracle Business Intelligence Data Warehouse Administration Console (DAC) is a centralized console for schema management as well as configuration, administration, loading, and monitoring of the Oracle Business Analytics Warehouse.
The following list describes the sections of this document:
These release notes are updated periodically as new information becomes available. To ensure that you are reading the latest release of the release notes, check the Oracle Business Intelligence Data Warehouse Administration Console Documentation Web site:
This section describes general issues and workarounds for the Oracle Business Intelligence Data Warehouse Administration Console. It contains the following topics:
For certification information, refer to the System Requirements and Supported Platforms for Oracle Business Intelligence Data Warehouse Administration Console document. This document is part of the Oracle Business Intelligence Data Warehouse Administration Console documentation set.
This section provides release notes on installing and upgrading Oracle Business Intelligence Data Warehouse Administration Console. It contains the following topics:
Section 2.2.1, "DAC Release 10.1.3.4 Usage with Oracle Business Intelligence Applications"
Section 2.2.2, "Custom SQL and Index Overrides Are Obsoleted"
Section 2.2.5, "DAC Installer Does Not Provide an Informatica 9.x Option"
This issues applies to releases 10.1.3.4 and 10.1.3.4.1.
DAC release 10.1.3.4 is an Oracle BI foundation component that is designed to be used with Oracle Business Intelligence Applications. Before installing DAC release 10.1.3.4, ensure that a working instance of any prior release of DAC exists in your current Oracle Business Intelligence Applications environment.
DAC release 10.1.3.4 will be installed in an Oracle home directory, which is a different directory from the current working Oracle BI/DAC directory. Therefore, DAC release 10.1.3.4 can be installed on the same machine that contains your current release of the DAC Client (or DAC Server). DAC release 10.1.3.4 can co-exist with previous releases.
When the DAC Client release 10.1.3.4 is configured to read DAC metadata in the current DAC repository database for the first time, the current DAC repository will be upgraded to be compatible with DAC release 10.1.3.4. Only the DAC Client release 10.1.3.4 (and DAC Server release 10.1.3.4) can be used to read that repository after the upgrade.
This issues applies to Releases 10.1.3.4 and 10.1.3.4.1.
Custom SQL and Index Overrides are not supported by DAC 10.1.3.4. If you are upgrading from an Oracle Business Intelligence Applications 7.9.x release of DAC, you need to manually convert your XML definitions to actions, as described in this section.
For all tasks, this issue applies to:
Pre-Full-Load Command
Pre-Incremental Load Command
Post-Full-Load Command
Pre-Incremental Load Command
For tasks that are of type SQL File, this issue applies to:
Load Types
Full Command
Incremental Command
Indexes
Index overrides
Upgrading the Existing Task Related SQL Files
For each definition in the XML files, you should create a new action under tasks (Tools->Seed Data->Tasks). You import your xml/sql files by right-clicking on a newly created action, and choosing 'Read Action From File'.
Once you have created these actions, associate them with the tasks that use them by defining actions under the Actions tab. Choose Preceding Action, Succeeding Action, and associate the appropriate mode (Full/Incremental/Both).
Note: If you have used pre and post SQL commands to manage indexes, consider using actions for indexes.
For the 'Full Command' and 'Incremental Command' tasks, define actions on the 'Command For Full Load' and 'Command For Incremental Load' fields, using the Choose button on the field itself.
This issues applies to release 10.1.3.4.1 only
When installing DAC server onto a non-English environment upon which no Oracle products have been installed and, therefore, no Oracle Home exists, the Specify Inventory Directory dialog appears. This dialog contains instructions for creating an inventory directory; however, for some users, these instructions may be truncated. See the below paragraphs for the dialog's full text.
"You are starting your first installation on this host. As part of this install, you need to specify a directory for installer files. This is called the "inventory directory." Within the inventory directory, the installer automatically sets up subdirectories for each product to contain inventory data and will consume typically 150 Kilobytes per product.
Enter the full path of the inventory directory.
You can specify an Operation System group that has write permissions to the above directory."
This issues applies to Releases 10.1.3.4 and 10.1.3.4.1.
During installation, the DAC installer asks for the location of Oracle Home. Note, the installer is not asking for an existing Oracle (Database) home. Instead, the installer is asking for the location where DAC has to be installed.
Provide an empty folder location as the Oracle Home for DAC.
This issues applies to Release 10.1.3.4 only.
The Informatica installation is a prerequisite for the DAC 10.1.3.4.1 installation. Prior versions of BI Applications utilizing DAC 10.1.3.4.1 used either Informatica 7.x or Informatica 8.x. Informatica version 9.0.1 is a new version of Informatica and is a prerequisite for BI Applications 7.9.6.3, but not for DAC 10.1.3.4.1. Note the following items:
The DAC 10.1.3.4.1 installer prompted users to indicate if the Informatica version used in their deployment is version 7.x or version 8.x. There is no option for Informatica version 9.x.
Users installing DAC 10.1.3.4.1 for use with BI Applications 7.9.6.3 are recommended to choose Informatica version 8.x when prompted even though the actual Informatica version deployed for use in BI Applications 7.9.6.3 is Informatica version 9.x.
This section provides release notes on DAC documentation. It contains the following topics:
This issues applies to release 10.1.3.4.1 only.
The DAC online help and manuals were not updated to reflect changes made to the DAC 10.1.3.4.1 installer and user interface.
There is no workaround for this issue.
This section provides release notes on the functionality of the Oracle Business Intelligence Data Warehouse Administration Console. It contains the following topics:
Section 3.2, "Configuring DAC 10.1.3.4.1 to Prevent a User Authentication Error on AIX"
Section 3.4, "Class Names for Teradata JDBC Driver Changed in Teradata Version 12"
Section 3.5, "DAC Task Failing On Non-English Operating System"
Section 3.6, "Option to Specify Index Space in Data Warehouse Configuration Wizard Is Obsolete"
This issues applies to release 10.1.3.4. For information about preventing this issue for release 10.1.3.4.1, see Section 3.2, "Configuring DAC 10.1.3.4.1 to Prevent a User Authentication Error on AIX".
If the DAC 10.1.3.4 server is installed on Unix and customers insert or modify any user property through the user management feature on the client, the "Can't Authenticate User" error appears at the next login.
Perform the following procedure before manipulating the user's properties.
Note:
These steps are required every time user passwords are modified on DAC 10.1.3.4 when the DAC server is on AIX.
Shutdown the DAC server.
Go to the DAC Client Set Up dialog and select the System Properties tab. Change the Server OS property from AIX to Windows (or any other value).
Save and close the client.
Make and save the required user changes.
Save and close the client.
Open the client and set the Server OS property back to AIX.
Save and close the client.
Start the DAC server and DAC client and confirm that the error message does not appear.
This issues applies to release 10.1.3.4.1. For information about preventing this issue for release 10.1.3.4, see Section 3.1, "Cannot Authenticate User on AIX".
If the DAC 10.1.3.4.1 server is installed on Unix and customers insert or modify any user property through the user management feature on the client, the "Can't Authenticate User" error appears at the next login.
To prevent this issue, you must perform the following configuration.
Shut down the DAC server.
Open the client and read the DAC repository. If the DAC repository is a prior release, click Yes when prompted to upgrade.
Go to the Setup menu and choose DAC System Properties. Enter the DAC server information.
On the AIX machine hosting the DAC server, navigate to the directory containing ServerSetupPrompt.sh.
Execute ServerSetupPrompt.sh.
Re-enter all passwords wherever they apply (for example, DAC repository and email).
Save your changes and start the DAC server.
This issues applies to releases 10.1.3.4 and 10.1.3.4.1.
DAC requires Teradata JDBC Driver 13.0.0.0 to connect to Teradata version R12. Note the following URLs.
To acquire the Teradata JDBC driver, go to the Teradata web site at
After accessing this site, go to the Teradata Download Center in the Teradata JDBC Driver section.
To acquire the Teradata JDBC Driver User Guide Release 13.00.00, go to the Teradata - Information Products Home page at
This release of the Teradata JDBC Driver is distributed as platform-independent JAR files in both ZIP (TeraJDBC__indep_indep.13.00.00.00.zip) and TAR (TeraJDBC__indep_indep.13.00.00.00.tar).
Perform the following procedure to properly set the classpath to refer to the correct JAR files.
Note:
It is recommended that you deinstall any previous release of the Teradata JDBC Driver prior to downloading and installing Teradata JDBC Driver 13.0.0.0.
Download either the ZIP file or the TAR file and unzip (or untar) the downloaded file into a directory of your choice.
Copy the following files into the DAC\lib folder.
terajdbc4.jar
tdgssconfig.jar
This issues applies to releases 10.1.3.4 and 10.1.3.4.1.
Starting in Teradata Version 12, the class names have changed for the Teradata JDBC driver. However, the names used in the previous version still work with DAC but with a warning. To avoid these warnings, modify DAC\conf\connection_template.xml when using Teradata Drivers Version 12 and above. To modify this file, open the connection_template.xml file and follow the instructions included in the file.
This issue applies to DAC 10.1.3.4.1 and Informatica PowerCenter 8.6.1, HotFix3.
DAC Server uses pmcmd to initiate the workflows on Informatica Server. In the English-based operating systems, DAC issues the commands in the non-blocking mode (asynchronously), and polls Informatica for the status of the workflow. The output of the pmcmd getWorkFlowDetails is spooled to the DAC\log directory, and then gets parsed to determine whether the workflow is still running, completed successfully, or failed.
However, for non-English based operating systems DAC issues commands in the waiting mode (synchronously). This means that when the process completes the exit code tells DAC whether the workflow succeeded or not.
The commands used by DAC to communicate with Informatica are externalized in a file called infa_commands.xml. The DAC 10.13.4.1 command template does not have a place holder for specifying the wait mode. Without this wait mode configuration, on non-English OS based installation, this results in DAC proceeding with the execution even before the workflow completes executing. This might result in errors, such as Informatica's bulk loader failing because of index presence or fact tables getting loaded without foreign key references. To fix the problem, go to DAC\conf folder and edit the file called infa_commands.xml. Depending upon the version of informatica you are using, edit either the block called START_WORKFLOW_7 or START_WORKFLOW_8 and verify whether %WAITMODE is in the syntax. If it is not, add it as follows:
For START_WORKFLOW_7 replace the following line:
pmcmd startworkflow -u %USER -p %PASSWORD -s %SERVER:%PORT -f %FOLDER -lpf %PARAMFILE %WORKFLOW
With:
pmcmd startworkflow -u %USER -p %PASSWORD %WAITMODE -s %SERVER:%PORT -f %FOLDER -lpf %PARAMFILE %WORKFLOW
For START_WORKFLOW_8 replace the following line:
pmcmd startworkflow -sv %SERVER -d %DOMAIN -u %USER -p %PASSWORD -f %FOLDER -lpf %PARAMFILE %WORKFLOW
With:
pmcmd startworkflow -sv %SERVER -d %DOMAIN -u %USER -p %PASSWORD %WAITMODE -f %FOLDER -lpf %PARAMFILE %WORKFLOW
Once you modify this file (the modifications should be done both on the DAC client and the server machines), restart the DAC server and client for the changes to take effect.
This issue applies to releases 10.1.3.4 and 10.1.3.4.1.
The option to specify an index space when creating data warehouse tables using the Data Warehouse Configuration Wizard is obsolete.
In release 10.1.3.4 and higher, the Physical Data Sources tab in the Setup view has a Default Index Space property that enables you to specify an index space for all indexes in the data warehouse. You can also specify an index space by table type in the Index Spaces subtab of the Physical Data Sources tab. An index space specified by table type overrides the Default Index Space property in the Physical Data Sources tab.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Business Intelligence Data Warehouse Administration Console Release Notes, Release 10.1.3.4.1
E12655-10
Copyright © 2010, 2012, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
 Copyright © 2010, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|