Dac11g PDF
Dac11g PDF
Dac11g PDF
August 2011
Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration
Console, 11g Release 1 (11.1.1)
E14849-01
Copyright 2011, Oracle and/or its affiliates. All rights reserved.
Primary Author:
Jill Arehart
Contributors: Oracle Business Intelligence development, product management, and quality assurance teams.
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 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 America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
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 licensed through X/Open Company, Ltd.
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.
Contents
Preface ............................................................................................................................................................... xv
Documentation Accessibility ...................................................................................................................
Audience.....................................................................................................................................................
Related Documents ...................................................................................................................................
Conventions ...............................................................................................................................................
xv
xv
xv
xvi
2-1
2-1
2-2
2-4
2-6
3-12
3-12
3-13
3-13
3-14
3-14
3-14
3-15
iv
4-27
4-28
4-28
4-29
4-29
4-30
4-31
4-31
4-31
How the DAC Server Handles Requests to Start and Stop Execution Plans............................. 6-19
8-11
8-11
8-12
8-13
8-13
8-14
8-15
8-15
9-1
9-2
9-2
9-4
9-4
10-1
10-2
10-3
10-4
10-5
10-5
10-5
10-5
10-6
10-6
10-6
10-7
10-7
10-7
10-7
10-8
10-8
10-8
10-8
10-9
10-10
10-11
10-12
10-12
vii
11-2
11-2
11-3
11-4
11-5
11-5
11-5
11-6
11-6
11-6
11-8
11-9
11-10
11-12
11-12
11-14
11-15
11-16
13
viii
12-1
12-2
12-3
12-3
12-4
12-4
12-5
12-7
12-7
12-8
12-8
12-9
12-9
12-9
13-1
13-1
13-2
13-3
13-4
13-5
13-5
13-5
13-5
13-5
13-5
13-6
13-6
13-6
13-7
13-7
13-7
13-8
13-8
13-8
13-8
13-9
13-9
13-9
13-9
13-10
13-10
13-10
13-11
13-11
13-11
13-12
13-12
13-12
13-13
13-14
13-14
13-14
13-15
13-15
14-1
14-2
14-2
14-3
14-3
14-3
14-3
14-3
15-1
15-2
15-2
15-3
15-3
ix
15-4
15-7
15-7
15-8
15-11
15-12
15-12
15-13
15-15
15-15
15-16
15-18
15-18
15-19
15-20
16-2
16-3
16-4
16-5
16-5
16-5
16-5
16-6
16-6
16-6
16-6
16-6
16-6
16-6
16-7
16-7
16-7
16-7
16-7
16-8
16-8
16-10
16-11
16-13
16-14
16-15
16-17
16-18
16-19
16-20
16-21
16-21
16-21
16-22
16-23
16-23
16-25
16-26
16-27
16-28
16-28
16-28
16-29
16-29
16-30
16-30
16-31
16-31
16-32
16-32
16-33
16-34
16-34
16-34
16-34
16-36
16-36
16-37
16-37
16-38
16-39
16-40
16-40
16-40
16-41
16-41
16-41
16-42
16-42
16-42
16-43
16-43
16-45
16-46
16-50
16-51
16-51
xi
xii
A-4
A-4
A-5
A-6
A-6
Index
xiii
xiv
Preface
The Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse
Administration Console contains information about using the Data Warehouse
Administration Console (DAC), a centralized console for management, configuration,
administration, loading, and monitoring of the Oracle Business Analytics Warehouse.
Documentation Accessibility
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.
Access to Oracle Support
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.
Audience
This document is intended for data warehouse administrators and ETL developers
and operators.
Related Documents
For more information, see the following Oracle Business Intelligence Applications 11g
Release 1 (11.1.1.) documents:
Also see the following documents in the Oracle Business Intelligence Enterprise
Edition 11g Release 1 (11.1.1) documentation set
The Oracle Business Intelligence chapter in Oracle Fusion Middleware Release Notes
for your platform
xv
Conventions
The following text conventions are used in this document:
xvi
Convention
Meaning
boldface
italic
monospace
1
Whats New in This Release
This chapter lists the new features in the current release of Oracle Business Intelligence
Data Warehouse Administration Console (DAC). It also provides information about
hardware and software requirements, platforms, and databases.
The chapter contains the following topics:
1-1
1-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
1-3
1-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
2
About DAC Security
DAC Repository. Resides on a database and stores the metadata (semantics of the
Oracle Business Analytics Warehouse) that represents the data warehouse
processes.
DAC Client. A thick client (Swing GUI).
DAC Server. Can be deployed as an enterprise application on the Web Logic
Server (referred to as Web mode) or as a standalone Java application (referred to as
standalone mode).
When DAC runs in Fusion Middleware mode, users are defined in the WebLogic
Server identity store (LDAP) and authenticated against a BI domain. The Fusion
Middleware tier authenticates the users for access to the DAC repository. The LDAP
credentials indicate: 1) whether the user is valid, and 2) the users role. The DAC
Client also accesses database credentials stored in an encrypted cwallet.sso file in the
file system to access the DAC repository database. The database credentials are used to
manipulate objects in the repository through direct JDBC access.
When DAC runs in DAC standalone authentication mode, the DAC Client
authenticates users and gets user permissions against user credentials stored in the
DAC repository.
password information that allows connectivity to the DAC repository, to all of the data
sources accessed by the BI Server (including the transactional data source), and to the
data warehouse.
Therefore, for production environments, in both Fusion Middleware and DAC
standalone authentication deployment modes, you must install the DAC Client
according to the following requirements:
The DAC Client must be physically located in the server tier with the other
middle-tier components.
The DAC Client should be accessed only by trusted users.
The DAC Client should be accessible only through remote log in tools if it is
accessed outside of the server tier.
The DAC Client should not be installed on the administrators desktop.
2-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Gets user name and password from user (can be optionally saved on the file
system).
b.
Reads the database connection information from the encrypted cwallet.sso file
stored on the file system.
c.
d.
e.
Authenticates and gets permissions through the DAC Server in the BI domain
using the BI domain URL.
2.
DAC Server reads the database connection information from the file system and
connects to the DAC repository upon startup.
3.
Automation utilities read the database connection information from the file system
and connect to the DAC repository.
Note: The automation utilities are not interactive
4.
DAC Server command line utilities read the DAC Server information from the file
system and send it as a Web service request, which is authenticated with proper
user credentials.
2-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Gets user name and password from user (can be optionally saved on the file
system).
b.
Reads the database connection information from the encrypted cwallet.sso file
stored on the file system.
c.
d.
Authenticates and gets permissions against user credentials stored in the DAC
repository.
2.
DAC Server reads the database connection information from the file system and
connects to the DAC repository upon startup.
3.
Automation utilities read the database connection information from the file system
and connect to the DAC repository. Note: The automation utilities are not
interactive.
4.
DAC Server command line utilities read the DAC Server information from the file
system and send it as a Web service request, which is authenticated with proper
user credentials.
DAC is used for orchestrating ETL processes, and, therefore, should be accessed
by a limited number of administrators with the appropriate privileges. The
schema level operations that require administrator privileges include but are not
limited to the following:
Truncating tables
Managing indexes
Because of the sensitive nature of schema level operations, DAC should also be
secured by the operating system level security.
The DAC repository should be stored in a different database from the data
warehouse and transactional applications databases. This allows for restriction of
DAC users, if necessary.
2-6 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
3
Before You Begin Using DAC
This chapter provides an overview of DAC and explains fundamental concepts that
you need to know before you begin using DAC.
This chapter contains the following topics:
Introduction to DAC
The Client tier contains the Informatica PowerCenter client tools and the DAC
Client.
The Server tier contains the following:
DAC Server. The DAC Server executes the instructions from the DAC Client.
It manages data warehouse processes, including scheduling, loading of the
ETL, and configuring the subject areas to be loaded. It dynamically adjusts its
actions based on information in the DAC repository. Depending on your
business needs, you might incrementally refresh the Oracle Business Analytics
Introduction to DAC
DAC Repository. The DAC repository stores the metadata (semantics of the
Oracle Business Analytics Warehouse) that represents the data warehouse
processes.
The Database tier contains the transactional and data warehouse databases.
Introduction to DAC
DAC provides a framework for the entire life cycle of data warehouse
implementations, including the setup, configuration, administration, and loading of
data warehouses. DAC enables you to create, configure, execute, and monitor modular
data warehouse applications in a parallel, high-performing environment.
DAC is a metadata-driven ETL orchestration tool that complements ETL platforms,
such as Informatica. It provides application-specific capabilities that are not prebuilt into
ETL platforms. For example, ETL platforms are not aware of the semantics of the
subject areas being populated in the data warehouse nor the method in which they are
populated.
DAC provides application capabilities at a layer of abstraction above the ETL
execution platform that enable you to do the following:
Manage indexes
3-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Introduction to DAC
Introduction to DAC
3-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
The phases of the process and the actions associated with them are as follows:
Setup
Design
Execute
Monitor
make a copy of a predefined container and then modify the metadata to create your
own custom source system container. This enables the DAC Client to track
customizations you make in the copy of the source system container, such as newly
created objects and modified objects. DAC is also able to compare the modified objects
with the predefined object definitions in the predefined container. This feature enables
DAC to rollback changes to the objects if necessary. For more information, see "About
Object Ownership in DAC".
Caution: You cannot modify objects in the predefined source system
containers either through the DAC Client or directly through SQL
statements to the DAC repository. You must make a copy of a
predefined container in order to make any changes to it.
Execution plan. A data transformation plan that is defined on subject areas and is
transformed at certain frequencies of time. Execution plans are defined based on
business requirements for when the data warehouse needs to be loaded. Execution
plans can be scheduled for full or incremental loads.
Subject area. A logical grouping of tables related to a particular subject or
application context. A subject area includes the tasks that are associated with the
tables, as well as the tasks required to load the tables. Subject areas are assigned to
execution plans.
Tables. Physical database tables defined in the database schema. The tables can be
transactional database tables or data warehouse tables. Table types include
dimension, hierarchy, aggregate, and so on. Flat files can also be used as sources or
targets.
Tasks. Units of work for loading tables. Tasks comprise the following: source and
target tables, phase, execution type, truncate properties, and commands for full or
incremental loads. Tasks can do the following: execute Informatica workflows,
execute batch files, call database stored procedures, and execute SQL, XML, and
operating system commands. When you assemble a subject area, DAC
automatically assigns tasks to it. Tasks that are automatically assigned to the
subject area by DAC are indicated by the Autogenerated flag in the Tasks subtab
of the Subject Areas tab.
Task properties are critical in ETL design and execution. DAC automatically
assembles tasks into subject areas based on task properties, such as source and
target tables. Tasks in the ETL queue are prioritized by the DAC Server, based on
task properties, such as phase, source and target connections, and truncate
properties.
3-6 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Task group. A group of tasks that you define because you want to impose a
specific order of execution. A task group is considered to be a "special task."
Indexes. Physical database indexes to be defined in the database schema to
improve the performance of the ETL processes or the queries for reporting
purposes.
Schedule. A schedule specifies when and how often an execution plan runs. An
execution plan can be scheduled for different frequencies or for recurrences by
defining multiple schedules.
For best practice tips about the DAC repository objects, see"Considerations When
Defining Repository Objects".
When you make changes to an original object that has been referenced by other
containers, any updates to the original object are immediately reflected in the
referenced object. If you delete the original object, all referenced objects are also
deleted.
Changes to an original object's child objects are not automatically reflected in the
referenced object's child objects. You need to push the changes to the referenced object's
child objects by using the Push to References right-click command. And, conversely,
you can import into a referenced object the changes made to an original object. This
function is referred to as a re-reference.
For a description of the ownership functionality available in the Design view
right-click menu, see "Ownership Right-Click Commands".
Views Buttons
Right-Click Menus
Navigation Tree
Editable Lists
3-8 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Key to figure:
a. File menus
b. Views button and container drop-down list
c. Top pane tabs
d. Top pane toolbar
e. DAC Server monitor icon
f. Editable lists
g. Bottom pane tabs
Views Buttons
The View buttons are located directly under the menu bar and provide access to the
Design, Setup, and Execute views. For detailed information about the functionality
provided in the DAC views, see the following sections in Chapter 16, "DAC Functional
Reference":
Right-Click Menus
For a detailed description of the commands available in right-click menus, see the
section titled "Right-Click Menu Commands" in Chapter 16, "DAC Functional
Reference."
3-10 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Navigation Tree
The navigation tree appears on the left side of the DAC window, as shown in
Figure 310. It displays the top-level tabs of the selected view.
Figure 310 DAC Navigation Tree
Editable Lists
The top and bottom panes of the DAC window display records in a list format. Some
of the columns in the list are editable, and others are read-only. The toolbar at the top
of each pane enables you to perform various tasks associated with a selected record in
the list. For a description of the toolbar commands, see "Top Pane Toolbar".
A right-click menu is also accessible from the lists in both the top and bottom panes.
For a description of these commands, see "Right-Click Menus".
The list format enables you to do the following:
Edit the data in place and save the record by either clicking another record in the
list or clicking the Save button.
Use the query functionality in pop-up dialogs for fields that refer to values from
other entities.
Use Ctrl+C to copy an editable string to the clipboard (not available for read-only
strings).
3-11
Use Ctrl+V to paste a string from the clipboard into a selected cell that supports a
string data type.
Object Type
Font
Referenced object
Clone
Operator
Description
Placed before a value, returns records containing a value equal to the query
value.
<
Placed before a value, returns records containing a value less than the query
value.
>
Placed before a value, returns records containing a value greater than the query
value.
<>
Placed before a value, returns records containing a value that is not equal to the
query value.
<=
Placed before a value, returns records containing a value less than or equal to the
query value.
>=
Placed before a value, returns records containing a value greater than or equal to
the query value.
Wildcard that can be placed in the middle, or at the beginning or end of a text
string.
""
3-12 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Description
Escape symbol is used when double quotes should not be processed as a special
symbol. For example, !("*null text" or(\"*\")) is a value expression for
a text field. The query returns values that do not end with a string null text
and that are not surrounded by double quotes.
()
NULL
AND
Placed between values, returns only records for which all the given conditions
are true. (Not case sensitive.)
OR
Placed between values, returns records for which at least one condition is true.
(Not case sensitive.)
*Extract* lists all tasks whose name contains the word Extract.
!Extract* lists all tasks whose name does not start with the word Extract.
Extract* or Aggregate* lists all tasks whose name starts with Extract or
Aggregate.
Load* and *Aggregate* lists all tasks whose name starts with Load and also
contains the word Aggregate.
"Extract for Wave Dimension" or "Load into Wave Dimension" lists
tasks whose name is either Extract for Wave Dimension or Load into Wave Dimension.
When using spaces within strings, you need to enclose the
string with quotes ("").
Note:
In the top or bottom pane of the DAC Client, click Query on the toolbar or in the
right-click menu.
A blank row in a list is displayed.
2.
3.
In the date field, click the Calendar icon on the right side of the cell.
The Date dialog is displayed.
3-13
2.
Enter the date and time for which you want to search, and select the appropriate
query condition.
2.
Select Flat Views, and then select a context-sensitive column on which you want
to query.
3.
4.
5.
In the Update Record Set dialog, select the column you want to update, and then
click Set Value.
6.
7.
To update records that are referenced objects, select Update Referenced Records.
If you select this check box, referenced objects as well as original and cloned
objects will be updated. The referenced objects will become clones, and the
ownership column for these records will be updated to reflect the new ownership.
If you do not select this check box, only the columns in records that are original or
cloned objects (objects owned by the source system container) will be modified.
8.
Click OK.
9.
To Do This
Press
ALT+V.
3-14 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Press
Arrow keys.
Enter.
Up arrow key.
Activate a cell.
Spacebar.
F2.
Enter.
Esc.
To activate a multi-value
group (MVG) cell.
Tab
Shift+Tab.
Arrow keys.
F6.
F10.
Alt+spacebar.
3-15
files are installed in the Oracle Home directory for Oracle Business Intelligence.
After you complete the Fusion Applications provisioning process, you must
perform additional setup and configuration tasks related to DAC. For more
information about the required tasks you must perform, see Oracle Fusion
Middleware Configuration Guide for Oracle Business Intelligence Applications.
3-16 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
4
Setup Tasks and Concepts for DAC
Administrators
This chapter provides information about the administrative tasks that must be
performed in order for a DAC environment to be operable. It also includes various
concepts related to DAC operations that a DAC administrator should be aware of.
Note: If you installed and configured DAC using the Oracle BI Applications
installation process and by following the post-installation instructions in Oracle Fusion
Middleware Configuration Guide for Oracle Business Intelligence Applications, you do not
need to repeat the same tasks that appear in this chapter.
This chapter contains the following topics:
Applying Patches
option appears in the DAC Client as "DAC"). See "DAC Authentication in Oracle
Fusion Middleware (WebLogic Server) Mode" and "DAC Authentication in Standalone
Mode" for topology diagrams that illustrate these two authentication modes.
Fusion Middleware Mode
The Fusion Middleware mode uses the Fusion Middleware security model. This model
requires the DAC repository to be configured for Web mode and a valid DAC Server
URL to be present in the DAC repository. Authentication occurs through Web service
calls to the DAC enterprise application deployed in WebLogic Server. The DAC
enterprise application that the URL points to must be running for the authentication to
occur.
DAC Standalone Authentication Mode
DAC standalone authentication mode uses the DAC user account security model.
DAC user account information is stored in the DAC repository. A DAC user with the
Administrator role creates user accounts with the appropriate user names, passwords,
and roles. The DAC administrator needs to distribute the user account information
(name and password) to the users to enable them to log into the DAC Client and
repository. In standalone mode, the DAC Server does not participate in user
authentication.
Using the DAC standalone authentication mode, a user can connect to a DAC
repository that is configured for either Fusion Middleware or standalone mode.
However, when the DAC repository is in Fusion Middleware (Web) mode and the user
is authenticated through standalone mode, the user cannot run ETLs, because the user
cannot connect to the DAC Server. When standalone mode is used for both the user
and DAC repository, connecting to the DAC Server is possible, and, therefore, ETLs
can be run.
4-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
The initial login process for an administrator varies depending on the authentication
mode being used and whether an authentication file was already created.
If you are using Fusion Middleware authentication, the authentication file was created
during the Oracle BI Applications set up and configuration process. You will need to
know the location of this file when you log into DAC for the first time.
If you are using DAC standalone authentication, you will create an authentication file
while logging into DAC for the first time. To do so, you will need to know the
database schema owner and password.
Regardless of the authentication mode, an administrator must distribute the
authentication file to all user accounts (those authenticated through DAC as well as
through WebLogic Server) that need to access the specified DAC repository. For more
information about the authentication file, see "About the DAC Authentication File".
To log in to DAC for the first time
1.
2.
Click Configure.
3.
In the Configuring... dialog, select Create Connection, and then click Next.
4.
Field
Required Value
Name
Connection type
Field
Required Value
Connection String, or
Database name, or TNS
Name, or Service Name
Database Host
Enter the name of the machine where the DAC repository will
reside.
Database Port
DB URL (Optional)
DB Driver (Optional)
Authentication File
Log Level
Specifies a client log level for the client session. The logs are
saved in <Domain_Home>\dac\log\client <clients logical
connection name>.
5.
b.
c.
d.
e.
Note:
6.
4-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
b.
In the Authentication File dialog, select Create authentication file, and click
OK.
c.
Navigate to the directory where you want to save the new authentication file,
and click OK.
d.
In the Create Authentication File dialog, enter the Table Owner Name and
Password for the database where the repository will reside.
e.
Click Generate Random Encryption Key to generate an encryption key for the
authentication file. The key is displayed in the Key field.
Alternatively, you can enter a key in the Key field. The key must be at least 24
characters long.
f.
g.
Note:
7.
8.
In the Login... dialog, select the appropriate Connection from the drop-down
list.
b.
c.
d.
If you want DAC to remember the password for this connection, select
Remember Password.
e.
Click Login.
The DAC Client is displayed.
9.
In the Login... dialog, select the appropriate Connection from the drop-down
list.
b.
For a first-time login, you can enter any values in the User Name and
Password fields, because the DAC repository that you just created does not
contain any user names or passwords.
A user account will be created with the user name and password you enter in
this step. This user account is automatically assigned the Administrator role.
c.
d.
If you want DAC to remember the password for this connection, select
Remember Password.
e.
Click Login.
10. (Optional) To specify the DAC view and tab that you want to appear each time
11. If a DAC repository has not already been created, you will be prompted to create
Configuring the Connection Between the DAC Server and DAC Repository
In standalone DAC mode, the DAC Server connects to other components in the
DAC environment using TCP/IP. When the DAC Server runs in standalone mode,
the DAC repository must also be configured as standalone (by selecting Tools,
DAC Server Management, Repository Configuration). For a description and
topology of standalone mode, see "DAC Authentication in Standalone Mode".
In Web mode, the DAC Server runs as an enterprise application on WebLogic
Server. The DAC repository must also be configured as Web mode. For a
description and topology of Web mode, see "DAC Authentication in Oracle Fusion
Middleware (WebLogic Server) Mode".
You can access the DAC Server using the following methods:
DAC Client. The DAC Client is a command and control interface that enables you
to perform schema management tasks, and configure, administer and monitor
execution plans. The DAC Client accesses the DAC Server through TCP/IP. You
can access the DAC Client through the Start menu or by double-clicking the
startclient.bat file in the <Domain_Home>\dac directory.
Oracle Enterprise Manager Fusion Middleware Control MBean Browser. You
can view information about running, failed and queued execution plans and the
status of the DAC Server. See "Viewing DAC Metrics Using Fusion Middleware
Control MBean Browser" for information about accessing DAC through Fusion
Middleware Control MBean Browser.
Oracle WebLogic Server. The DAC Server runs as an enterprise application on the
WebLogic Server. You can monitor the status of the DAC Server application
through the WebLogic Server Administration Console. Only one DAC Server
4-6 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
application can be run against the DAC repository at one time. Therefore, the DAC
Server application should be deployed to only one managed server. If more than
one DAC Server application is run against the DAC repository, the repository will
be corrupted.
See "Monitoring the DAC Server Using WebLogic Server" for information about
accessing the DAC Server through the WebLogic Server Administration Console.
Command Line. You can access the DAC Server using the command line in order
to start and stop execution plans and to get status information for servers,
databases, and execution plans. See "Accessing the DAC Server Using the
Command Line" for more information.
WSDL File. You can use a WSDL (Web service definition language) file in order to
write service calls to the DAC Server. To access the WSDL file, invoke the
following URL:
http//<host of the managed WebLogic Server>:<port of the managed WebLogic
Server>/DACServer/DACServerManagerService?wsdl
Note:
In the BI cluster, when one of the managed servers fails unexpectedly, the second
managed server will automatically continue an ETL execution from the point at which
it stopped. To enable this operation, the DAC system property "Auto Restart ETL"
must be set to True (in the DAC System Properties tab in the Setup view). When the
second managed server is automatically started, the execution graph status is
reconstructed from the run history tables.
The following scenarios are possible for individual workflows that were started but
not completed by the first managed server:
If the workflow is still running on the Informatica Integration Service grid, DAC
will wait for it to complete.
The second managed server is also capable of authenticating any DAC user defined in
a common credential store.
pmcmd.exe - Used to start and stop workflows and to get workflow status.
In addition, Oracle recommends that the DAC Server and Informatica Integration
Service are on a shared network drive, because DAC produces parameters files that are
consumed by Informatica.
For information about setting up Informatica for high availability, see the Informatica
documentation.
In the DAC Client, on the Tools menu, select DAC Server Management, and then
select Repository Configuration.
2.
Field
Description
Mode
If you are using Web mode, enter the URL for the DAC
enterprise application that is deployed on WebLogic
Server.
Standalone Mode
Configuration:
3.
Click Save.
Configuring the Connection Between the DAC Server and DAC Repository
On Windows, you can use the DAC Client to configure the connection between the
DAC Server and the DAC repository if the DAC Client and DAC Server are running in
the same \dac folder.
Optionally, or to configure a DAC Server installed in another folder or on another
Windows machine, use the serverSetupPrompt.bat file to configure the repository
connection from the additional machine or folder
On UNIX or Linux, use the serverSetupPrompt.sh script to configure the connection
between the DAC Server and the DAC repository.
Note the following points:
Setup Tasks and Concepts for DAC Administrators 4-9
In Web mode, you must first complete the procedure "Configuring the DAC
Repository to Allow DAC Server Connections" before you perform the procedure
in this section.
In standalone mode, you must configure the connection between the DAC Server
and DAC repository from the location where the DAC Server will be running.
Only one DAC Server at a time should connect to a DAC repository. It is possible
to configure connections between multiple DAC Servers and a single DAC
repository, but only one DAC Server at a time should be allowed to connect to the
DAC repository.
To use the DAC Client to configure the connection between the DAC Server and the
DAC repository
1.
Make sure an authentication file (cwallet.sso) has been created and placed in the
<DAC_Config_Location>\conf-shared\security\repository directory.
2.
In the DAC Client, on the Tools menu, select DAC Server Management, and then
select DAC Server Setup.
3.
4.
5.
Click Test Connection to make sure the DAC repository connection works.
6.
Click Save.
To use the serverSetupPrompt files to configure the connection between the DAC
Server and the DAC repository
1.
2.
Enter 1 in the 'Please make your selection' prompt to enter repository connection
information.
3.
Enter the number for the type of database storing the DAC repository from the list
of connection type choices.
4.
5.
6.
7.
Enter 6 to exit.
4-10 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Select Start, Programs, Oracle Business Intelligence, Oracle DAC, and then
Start Server or Stop Server.
Note: When you execute ./stopserver.csh or ./stopserver.sh, the server will issue a
warning about the shutdown request. When the server receives the request, it will
shut down even if there is an ETL in progress. The statuses for the ETL run will
not be set correctly. The next time the DAC Server starts, it will set the status to
Failed for any uncompleted run.
Tip: When you start the DAC Server, look at the DAC Server status
icon in the DAC console to make sure that the DAC Server has started.
The DAC Server status icon should either be orange (idle) or green
(active). If Accessibility mode is enabled, the icon for an idle DAC
Server is replaced with the text "Connected to idle DAC Server," and
the icon for an active DAC Server is replaced with the text "Connected
to active DAC Server."
Note: In Web mode, the process for the DAC Server to move from idle
status to active can take a number of minutes.
To run the DAC Server in the background
The nohup command allows the DAC Server to run in the background on UNIX.
Note: To stop the DAC Server running as a background process, use stopserver.sh
or stopserver.csh.
Note: When you execute ./stopserver.csh or ./stopserver.sh, the server will issue a
warning about the shutdown request. When the server receives the request, it will shut
down even if there is an ETL in progress. The statuses for the ETL run will not be set
correctly. The next time the DAC Server starts, it will set the status to Failed for any
uncompleted run.
Tip: When you start the DAC Server, look at the DAC Server status
icon in the DAC console to make sure that the DAC Server has started.
The DAC Server status icon should either be orange (idle) or green
(active). If Accessibility mode is enabled, the icon for an idle DAC
Server is replaced with the text "Connected to idle DAC Server," and
the icon for an active DAC Server is replaced with the text "Connected
to active DAC Server."
Note: In Web mode, the process for the DAC Server to move from idle
status to active can take a number of minutes.
In the DAC Client, on the Tools menu, select one of the following:
Using the command line. For instructions, see "Using the Command Line to
Access the DAC Server".
For data source usage notifications, you need to complete additional configuration
steps, as described in "Setting Up Extract Delays, Event Delays and Data Source
Notifications".
2.
3.
Field
Description
Name
Email Address
4-12 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Field
Description
Notification Level
Inactive
In Web mode, you must first complete the procedure "Configuring the DAC
Repository to Allow DAC Server Connections" before you perform the procedure
in this section.
In standalone mode, you must configure email administrator account from the
location where the DAC Server will be running.
For the email functionality to work, you must be using an SMTP server in which
the SMTP authentication mode LOGIN is enabled. For example, if you are using
Microsoft Exchange Server, you must enable the SMTP module and enable
authentication in the Basic Mode. The SMTP server outbound email authentication
must be turned on for the DAC Server to be able to send email notifications.
In the DAC Client, on the Tools menu, select DAC Server Management, and then
select DAC Server Setup.
2.
Click Yes.
The Server Configuration dialog box appears.
3.
Click the Email Configuration tab, and enter the email details for the email
address to which you want to send DAC Server information notifications.
Field
Description
User Name
Password
Email Server
Email Address
Needs Authentication
Needs SSL
4.
5.
Click Save.
2.
For each record, enter the following information in the Edit subtab:
Field
Description
Name
Type
Connection Type
Database type.
Password
4-14 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Field
Description
Host
Port
Port number where the database listens (for example, 1521 is the
default for an Oracle database).
Source Priority
Field
Description
A JDBC driver for the data source connection. The value in this
field must conform to the database specifications. Use this option to
specify a unique driver for a particular physical data source.
URL (Optional)
A JDBC URL for the data source connection. The value in this field
must conform to the database specifications. Use this option to
specify a unique URL for a particular data source. For example, this
option can be useful if this physical data source uses Oracle RAC
and other data sources use a different database type.
3.
4.
Click Save.
Connectivity Requirements
Defining the Informatica Domains File Path for the DAC Client and DAC Server
4-16 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Connectivity Requirements
You should be familiar with the following connectivity requirements for DAC and
Informatica.
Database Connectivity
You must install and configure the appropriate database connectivity software on the
machines that host the Informatica PowerCenter Services, DAC Server, and DAC
Client.
To ensure DAC has access to pmrep and pmcmd, do one of the following:
Defining the Informatica Domains File Path for the DAC Client and DAC Server
In order for the DAC Client and Server to be able to use the pmrep and pmcmd
programs, the path of the Informatica Domains file 'domains.infa' must be defined in
the dac_env.cmd or dac_env.sh file on both the DAC Client machine and the DAC
Server machine.
4-18 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Note: The name for the connection specified in Informatica must match the name of
the physical data source in DAC to which it maps.
To configure relational connections in Informatica Workflow Manager
1.
2.
3.
Create a connection for each transactional (OLTP) database, and a connection for
the Oracle Business Analytics Warehouse (OLAP) database. For each database
connection, do the following:
a.
b.
c.
d.
You can register multiple Integration Service services, but you must register at
least one service.
You must register one Repository Service. You should only register one Repository
Service.
Tip: To locate Informatica services properties that you may need to
complete this procedure, log into the Informatica Administrator and
select the appropriate service.
2.
For the Informatica Integration Service that you want to register, do the following:
a.
Field
Description
Name
Type
Select Informatica.
Service
Domain
Login
Password
Repository Name
Inactive
b.
c.
3.
For the Informatica Repository Service you want to register, do the following:
a.
Field
Description
Name
Type
Select Repository.
Hostname
Server Port
Login
Password
4-20 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Field
Description
Repository Name
Inactive
b.
c.
The number of Runnable tasks in the queue. A Runnable task is a task for which
the Depends On tasks have completed and is ready to be run but is waiting for an
Informatica slot to be available. For information about the different task run
statuses, see "Current Runs Tab".
For an optimal run, the runnable queue should be at zero or should reach zero in a
short time. For example, Figure 42 shows an ideal performance run when 15
sessions were run in parallel. There were many runnable tasks before the process
began, but the queue soon reached zero.
You can generate a run analysis such as Figure 42 from the right-click menu
(select Get Run Information, then select Get Graph) on the DAC Current Runs and
Run History tabs. If you find that the runnable curve does not reach zero in a short
time, you should increase the Num Parallel Workflows per EP parameter value to
make more Informatica slots available.
2.
3.
4.
5.
2.
3.
4.
Use the New option to display the New Custom Property dialog, and add the
following custom properties:
4-22 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Table 41
Custom Properties
Value
Notes
ServerPort
<Server Port
Number>
overrideMpltVarWithMapVar
Yes
DisableDB2BulkMode
Yes
5.
6.
Make sure that the Integration Service and Repository Service that you created
during the Informatica PowerCenter installation are running.
2.
Click the Configure Security icon in the top, right corner of the Informatica
Administrator work area to display the Security tab.
3.
In the Users area, expand the Native directory and select Administrator.
Note: Do not select an existing user from an LDAP domain.
4.
Click the Privileges tab, and make sure that the correct Domain and Repository
Service are selected.
5.
Click OK.
2.
In the Users area, click Actions, then Create User to display the Create User
dialog.
Note: Do not create this user in an LDAP domain.
3.
Use the Create User dialog to specify the user details, then click OK.
4.
In the Users area, select the new user, click the Privileges tab, then click Edit to
display the Edit Roles and Privileges dialog.
5.
Use the Roles tab and Privileges tab to select the appropriate Domain and
Repository Service.
6.
Click OK.
2.
3.
4.
5.
Use the DataMovementMode drop down list to specify either ASCII or Unicode,
then click OK to save the change.
2.
3.
4-24 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
4.
5.
In DAC, go to the Setup view, and select the Informatica Servers tab.
6.
Select the appropriate Informatica Service record and enter the name of the
environment variable that you created in step 2 of this procedure as the value in
the Password field. Save the record.
7.
8.
9.
If the DAC Server is located on the same machine, start the DAC Server and run
an execution plan.
Set the environmental variable on the server machine and modify the <DAC_
Config_Location>\conf-shared\infa_command.xml.
b.
Shut down the DAC Server when testing Informatica connectivity or unit
testing a DAC task using the DAC Client.
Set the environmental variable on the server machine and modify the <DAC_
Config_Location>\conf-shared\infa_command.xml.
b.
Shut down the DAC Server when testing Informatica connectivity or unit
testing a DAC task using the DAC Client.
To allow you to use the DAC Actions feature to execute any SQL statement
The Actions feature allows you to do the following:
For more information about the DAC Actions feature, see "Using Actions to
Optimize Indexes and Collect Statistics on Tables".
2.
3.
In the Edit subtab, enter the appropriate information for the BI Server. For a
description of the fields, see "Setting Up Physical Data Sources".
4.
5.
Click Save.
6.
b.
c.
d.
e.
f.
g.
4-26 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
If the target folder is empty, DAC exports the metadata without a warning.
If the target folder contains DAC metadata, DAC issues a warning and you must
click OK to proceed with the export. The export process replaces all content in the
target folder.
If the target folder has non-DAC metadata as well as DAC metadata, DAC issues a
warning, and you must click OK to proceed with the export. The export process
replaces all content in the folder. All non-DAC metadata is deleted.
If the target folder has only non-DAC metadata, DAC cannot export into the
specified target folder.
In the DAC Client, on the Tools menu, select DAC Repository Management, and
then select Export.
2.
Select the directory to which you want to export DAC metadata, or accept the
default directory.
3.
Select the source system containers that hold the metadata you want to export.
4.
Logical. Exports all information contained in the Design view and metadata
defined in the Seed Data menu.
System. Exports all information contained in the Setup view, except
passwords for servers and database connections.
Run Time. Exports information about ETL runs and schedules (contained in
the Execute view).
User Data. (Applicable to DAC standalone authentication only) Exports the
users, roles, and passwords. Note: When importing roles and passwords, if the
encryption key is different in the repository to which you are importing from
that in which the metadata was exported, the roles and passwords will be
unreadable.
5.
Click OK.
6.
In the DAC Client, on the Tools menu, select DAC Repository Management, and
then select Import.
2.
Select the directory from which you want to import DAC metadata, or accept the
default directory.
3.
Select the appropriate applications for which you want to import metadata.
4.
Applying Patches
Logical. Exports all information contained in the Design view and metadata
defined in the Seed Data menu.
System. Exports all information contained in the Setup view, except
passwords for servers and database connections.
Run Time. Exports information about ETL runs and schedules (contained in
the Execute view).
User Data. (Applicable to DAC standalone authentication only) Exports the
users, roles, and passwords. Note: When importing roles and passwords, if the
encryption key is different in the repository to which you are importing from
that in which the metadata was exported, the roles and passwords will be
unreadable.
5.
6.
If you want DAC to import new records and update existing records, select
Update Existing Records. If you do not select this check box, DAC will only insert
new records. This option is only available if you do not select the Truncate
Repository Tables option.
Note: When importing DAC metadata into a container, if you select the Update
Existing Records option (and not the Truncate Repository Tables option), you also
need to import the metadata into any child containers. Otherwise, the child
containers will be inconsistent with the parent container.
7.
(Optional) Select Enable bulk mode to insert the imported metadata into the
repository as an array insert. You should elect this option only if you also selected
the Truncate Repository Tables option.
This action increases the speed of the import process.
8.
Click OK.
9.
Applying Patches
The DAC metadata patch feature enables you to do the following:
For more information about the DAC metadata patch feature, see Chapter 12,
"Working With DAC Metadata Patches."
4-28 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
For more information about the DAC external executor framework, see Chapter 14,
"Integrating DAC With Other ETL Tools."
DAC Permission
BI Administrator
Administrator
BI Author
Developer, Operator
BI Consumer
Guest
BIA_ADMINISTRATOR_DUTY
Administrator
BIA_FUNCTIONAL_DEVELOPER_DUTY
Developer
BIA_IMPLRMENTATION_MANAGER_
DUTY
Operator
As shown in Table 43, each DAC permission has a set of privileges that determines
what DAC functionality the permission can access.
Table 43
Permission
Privileges
Administrator
Developer
Export dialog
Privileges
Operator
Guest
In the DAC Client, on the File menu, select DAC User Management.
2.
3.
b.
Click in the Roles field, and then select the roles you want to associate with
this user account.
4.
Click Save.
5.
6.
Distribute the authentication file for the database where the DAC repository
resides to the user.
2.
In the DAC User Management dialog, select the user account you want to delete.
3.
Click Delete.
4.
2.
In the DAC User Management dialog, select the user account you want to
inactivate.
3.
4.
Click Save.
5.
4-30 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Create and save a text file containing user account information in one of the
following formats:
<user name>
The default role is Developer, and the default password is the same as the user
name.
You can use different formats on different lines in the text file.
2.
3.
Right-click in the DAC User Management dialog, and select Read Users From
File.
4.
Navigate to the text file, select it, and then click OK.
The new user account information will appear in the DAC User Management
dialog.
The authentication file (cwallet.sso) file is updated with the new key.
In the DAC Client, on the Tools menu, select DAC Repository Management, and
then select Change Encryption Key.
2.
Click Generate Random Encryption Key to generate an encryption key. The key is
displayed in the Key field. Alternatively, you can enter a key in the Key field. The
key must be at least 24 characters long.
3.
Click OK.
4.
Distribute the updated authentication file (cwallet.sso) to all users that connect to
this repository.
2.
3.
In the Configuring... dialog, select Modify Connection, and then click Next.
4.
Click in the Authentication File field to open the Authentication File dialog.
5.
From the drop-down list, select Modify existing authentication file, and then
click OK.
6.
7.
Enter a new table owner name and password, and then click OK.
8.
9.
Distribute the updated authentication file (cwallet.sso) to all user accounts that
connect to this repository.
4-32 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
5
5
This chapter provides the essential information you need to get started using DAC to
run ETL processes.
Before you can perform the operations in this chapter, you
need to have completed certain administrative setup tasks. If you
installed and set up Oracle BI Applications by following the steps in
Oracle Fusion Middleware Configuration Guide for Oracle Business
Intelligence Applications, you have already completed the necessary
tasks, and you are ready to begin running ETL processes, as described
in this chapter.
Note:
Before running ETL processes, you should also be familiar with the
concepts discussed in "About Source System Containers".
This chapter contains the following topics:
5-1
2.
Click Configure.
3.
In the Configuring... dialog, select Create Connection, and then click Next.
4.
Field
Required Value
Name
Connection type
5-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Field
Required Value
Connection String, or
Database name, or TNS
Name, or Service Name
Database Host
Database Port
DB URL (Optional)
DB Driver (Optional)
Authentication File
Log Level
Specifies a client log level for the client session. The logs are
saved in <Domain_Home>\dac\log\client <clients logical
connection name>.
5.
b.
c.
d.
e.
Note:
6.
7.
In the Login... dialog, select the appropriate Connection from the drop-down
list.
b.
5-3
This must match the user name and password stored in the WebLogic Server
identity store.
c.
d.
If you want DAC to remember the password for this connection, select
Remember Password.
e.
Click Login.
The DAC Client is displayed.
8.
9.
In the Login... dialog, select the appropriate Connection from the drop-down
list.
b.
c.
d.
If you want DAC to remember the password for this connection, select
Remember Password.
e.
Click Login.
In the Starting tab dialog, specify the initial view and tab that you want to appear
each time you log in, or leave the default. Click OK.
Make sure the DAC Server is running. For instructions on starting the DAC Server,
see "Starting and Stopping the DAC Server (Standalone Mode)".
2.
3.
4.
5-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
a.
b.
Once the execution plan starts running you can monitor its progress in the Current
Runs tab. See "Monitoring Execution Plan Processes" for instructions.
To run a customized execution plan
1.
2.
In the Execute view, go to the Execution Plans tab, and click New.
3.
4.
b.
c.
In the Choose Subject Areas dialog, select the custom container from the
drop-down list that you created in step 1.
d.
Query for the subject area you want to associate with the execution plan.
e.
f.
5.
Click the Connectivity Parameters subtab, and then click Generate in the
bottom pane toolbar.
The Generating Parameters... dialog lists the containers that are involved in
this execution plan.
b.
In the Generating Parameters dialog, enter the number of copies for each
source system container. Unless you are running a multi-source execution
plan, enter the value 1, and then click OK.
DAC automatically generates the parameters required for the source system
container.
c.
In the Value column, for each folder or database connection, select the
appropriate physical folder name or database connection.
For the data source type of FlatFileConnection, make sure you
have copied all files into the directory specified in the DAC system
property InformaticaParameterFileLocation.
Note:
d.
Leave the default values in the Delay and Prune Time fields.
5-5
For a description of all the fields in this subtab, see "Execution Plans Tab:
Connectivity Parameters Subtab".
6.
7.
(Optional) Add one or more tasks that will run before the ordered tasks generated
by DAC.
a.
b.
c.
Query for and select the task you want to add, and then click Add. Note: Only
tasks that have the task phase Pre ETL Process will appear in this list.
(Optional) Add one or more tasks that will run after the ordered tasks generated
by DAC.
a.
b.
c.
Query for and select the task you want to add, and then click Add. Note: Only
tasks that have the task phase Post ETL Process will appear in this list
8.
In the top pane of the Execution Plans tab, make sure the new execution plan is
highlighted, and click Build.
9.
In the Building... dialog, select the option Selected Record Only, to build only the
selected execution plan.
b.
Click Refresh in the bottom pane toolbar to populate the list of ordered tasks.
c.
To view details about a specific task, select the task, and then click Details in
the bottom pane toolbar.
For instructions on unit testing a task, see "Unit Testing Execution Plan Tasks".
11. Make sure the DAC Server is running. For instructions on starting the DAC Server,
b.
Once the execution plan starts running you can monitor its progress in the Current
Runs tab. For instructions, "Monitoring Execution Plan Processes".
For information about how refresh dates are tracked, see "About Refresh Dates
and DACs Incremental Load Strategy".
To schedule an execution plan, see "Scheduling an Execution Plan".
compare the modified objects with the predefined object definitions in the predefined
container. This feature enables you to selectively rollback changes to the objects if
necessary.
For information about managing object ownership, see "Ownership Right-Click
Commands".
You can also create a new, empty container if you want to build your own container
with customized metadata.
To create a new container or copy an existing container
1.
In DAC menu bar, select File, and then New Source System Container.
2.
3.
ID: CUST_FUSN_V1
4.
5.
If you are making a copy of an existing container, select the existing container from
the drop-down list, and then click OK.
Note: All records in the base container will be referenced to the newly created
custom container, and parent-child relationships between the containers will be
established.
5-7
2.
3.
Queued. Task is waiting for one or more predecessor tasks to complete. Appears
as light yellow.
2.
3.
Waiting. Task is eligible to run but is waiting because a time delay for the source
was defined in the connectivity parameters or because an event delay was defined
at the data source level (see "Setting Up Extract Delays, Event Delays and Data
Source Notifications"). Appears as white.
4.
Running. Task obtained a resource token and has started running. Appears as
blue.
5.
Paused. Task is a member of a task group and has paused until the child tasks of
the task group are completed. Appears as blue.
6.
Completed. All task details of the task have executed successfully. Appears as
green.
7.
Failed. One or more of the task details of the task have failed. Appears as red.
8.
Stopped. Task has stopped because one or more predecessor tasks failed. Appears
as ochre.
5-8 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
9.
Not Executed. Task has a heuristics definition that prevents it from running (see
"Using Heuristics to Manage Tasks, Tables and Indexes"). Appears as white.
In general, when an execution plan starts, the first tasks to run are those with no
dependencies (or predecessors). A task becomes "Runnable" if all of its predecessor
tasks are completed. When all of the tasks of an execution plan are completed, the
status of the execution plan becomes "Completed."
2.
3.
In the drop-down list on the right side of the subtab toolbar, select Failed.
The failed tasks are displayed.
4.
2.
3.
4.
5.
6.
If you want the schedule to run once, select the Run Only Once check box,
and then select a start date.
To create a periodic schedule, select a recurrence pattern, and enter the
appropriate date and time parameters.
Click Save.
5-9
Go to the Execution Plans tab in the Execute view, and select the appropriate
execution plan.
2.
3.
Query for and select the task that you want to test.
4.
5.
5-10 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Scenario
Null
Null
Full Load
Yes
Null
Not Null
Full Load
No
Not Null
Null
Full Load
Yes
Not Null
Not Null
Incremental
Load
No
Note: Refresh dates for micro ETL execution plans are kept separate from the refresh
dates for regular execution plans. DAC saves refresh dates for micro ETL execution
plans in the Micro ETL Refresh Dates subtab of the Execution Plans tab (Execute view)
and refresh dates for regular execution plans in the Refresh Dates subtab of the
Physical Data Sources tab (Setup view).
For timestamps that appear in the Run History tab of the Execute view, DAC uses
the ETL start time of the DAC Server host.
For refresh dates, which are stored in the Refresh Dates subtab of the Physical Data
Sources tab in the Setup view, DAC stores the timestamp of the data source
database.
For example, an ETL process is started on 1/1/2011 at 10 PM Central standard
time. It runs for an hour and some tasks fail, and, therefore, the ETL process fails.
The ETL process is restarted on 1/2/2011 at 8:00 AM. This time the ETL process
successfully completes. At the end of the ETL process, DAC updates the refresh
dates for all the primary and auxiliary source tables and the target tables that
participated in the ETL process as 1/1/2011 10:00 PM Central standard time but
adjusts the times based on the time zone of the transactional system and the data
warehouse. In this example, the data is sourced in Pacific standard time (-2 hours),
so the timestamp of the source tables is 1/1/2011 8:00 PM. The data warehouse is
in the Eastern standard time (+1 hour), so the timestamp of the target tables is
1/1/2011 11:00 PM.
For flat file sources, DAC uses the timestamp of the DAC Server host.
For incremental ETL processes, the ETL logic uses two types of timestamps:
LAST_REFRESH_DATE. The last time data was extracted from the table.
5-12 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
6
Building and Running Execution Plans
How the DAC Server Handles Requests to Start and Stop Execution Plans
6-1
This extract and load combination supports modular execution plan deployments,
enabling you to deploy a new source system or new subject area that will write to
data warehouse tables that already contain data. When you deploy a new source
system or subject area, the refresh dates for the source and staging tables will be
null; and, therefore, DAC will invoke the full extract workflow. If the target tables
have refresh dates (because they are populated by another source system or
subject area), DAC will invoke an incremental load command.
The incremental load process requires additional logic to determine whether a
record should be inserted or updated. Therefore, if you add a new source
connection to populate an existing data warehouse, you should expect the
incremental load to be slower than when running a full load.
Truncate table.
2.
Drop indexes.
3.
4.
Create indexes.
5.
Analyze table.
For instructions on building a single-source execution plan, see "Building and Running
Execution Plans".
6-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Homogeneous. This type of execution plan extracts data from multiple instances
of the same source system. For example, a business might have an instance of
Oracle Fusion Applications in one location and time zone and another instance of
Oracle Fusion Applications in another location and time zone. In such cases, the
timing of data extraction from the different instances can be staggered to meet
your business requirements.
Heterogeneous. This type of execution plan extracts data from multiple instances
of dissimilar source systems. For example, a business might have an instance of
Siebel 8.0 in one location and instance of Oracle EBS 11i in another location. You
can also stagger the timing of data extraction when you use this type of execution
plan, by setting the Delay property in the Connectivity Parameters subtab of the
Execution Plans tab.
For instructions on building a multi-source execution plan, see "Building and Running
Execution Plans".
2.
3.
4.
5.
6.
Analyze table.
Building and Running Execution Plans
6-3
Task Groups
Tasks should belong to the same task groups across all source system containers
associated with the multi-source execution plan.
Full and Incremental Workflow Commands
Full and incremental workflow commands need to match for tasks across all source
system containers.
Configuring Extracts and Notifications
You can delay extracts for a particular source system by using the Delay property in
the Connectivity Parameters subtab of the Execution Plans tab. You can also use the
Event Delay feature to configure the extracts for different source systems to occur
independently.
The Notifications feature enables you to initiate email notifications and the execution
of custom SQL based on the first or last read or write operations on a particular data
source. See "Setting Up Extract Delays, Event Delays and Data Source Notifications"
for more information.
Task Physical Folder Instance Priority
DAC deduplicates tasks from multiple source containers or multiple instances of the
same container based on the task name, the primary physical source, and the primary
physical target. DAC executes only a single instance of the task. If multiple containers
contain the same task, with the same source and target databases but different task
physical folders, then DAC will pick one folder. If folders have different priorities, the
folder with the lowest priority will be picked. If folders have the same priority, DAC
randomly selects a folder.
In Oracle BI Applications, the Instance Priority for task physical folders is predefined.
In certain situations, such as if you are using a vertical application, you may want to
execute a task from a different folder. You can specify the preference of task physical
folders by modifying the Instance Priority. To do so, on the Tools menu, select Seed
Data, and then select Task Physical Folders.
DATASOURCE_NUM_ID
Multiple extract and single load. In this scenario, as illustrated in Figure 62, data
is extracted from multiple sources and loaded into central staging tables. After all
of the extract tasks have completed, the data is loaded into the data warehouse in a
single load process.
Multiple extract and multiple loads. In this scenario, as illustrated in Figure 63,
data is extracted from multiple sources and loaded into non-centralized staging
6-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
tables. After all of the extract tasks have completed, the data is loaded into
multiple data warehouses using multiple load processes.
Figure 62 Multiple Extract and Single Load Option
6-5
6-6 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
records for the micro ETL execution plan. Micro ETL refresh dates do not affect the
refresh dates of regular execution plans.
Caution: Micro ETL processes can cause issues with data
inconsistencies, data availability, and additional load on the
transactional database. Therefore, you should consider the following
factors before implementing a micro ETL process:
For related star schemas, if one schema is omitted from a micro ETL execution
plan, the cross-star reports may be inaccurate. For example, if the Person fact table
is refreshed more frequently than the Revenue fact table, a report that spans the
Person and Revenue dimensional schemas may produce inconsistent results.
If you omit dimension tables from a micro ETL execution plan, the foreign keys for
the fact tables will point to Unspecified rows for the new dimension records. The
foreign key references will be resolved when the Complete ETL execution plan is
run, but users of the reports should be aware of such inconsistencies.
If you do not include aggregate tables in micro ETL execution plans, the reports
that use data from these tables will be inconsistent with the reports that use data
from the detailed fact tables. However, if aggregate tables are included in the
micro ETL execution plan, the aggregate calculations are performed for each ETL
process, which will take a constant amount of time and may be inefficient to
perform at such frequent intervals.
Hierarchy tables are rebuilt during every ETL execution plan by querying the base
dimension tables. This operation takes a constant amount of time. If the base tables
are big, this operation may take a long time and may be inefficient if the micro ETL
execution plan runs several times a day. However, if you avoid populating the
hierarchy tables during micro ETL processes, data inconsistencies will occur.
With micro ETL execution plans, caching will occur more frequently, which may
have performance implications.
Micro ETL execution plans will put more load on the transactional database
because of the frequent extracts.
For instructions on building a micro ETL execution plan, see "Building and Running
Execution Plans".
Task source and target tables. The dependency algorithm first looks at a task's
source and target tables. For example, suppose table A is populated by task T1 by
reading from table B, and table B is populated by task T2 by reading from table C.
The algorithm would determine task T2 should be executed before T1.
A task with a target table that is not a source table in any other task will be a leaf
node.
Task phase priority. An ETL process typically goes through a number of phases.
The task phase priority determines the order in which the phase will occur. For
Oracle BI Applications, the task phase priorities are predefined. You can view or
modify the priorities by selecting Tools, Seed Data, Task Phases.
An example of a typical order in which phases are executed is as follows:
Building and Running Execution Plans
6-7
1.
Extract Dimension
2.
Extract Fact
3.
Load Dimension
4.
5.
6.
Update Dimensions
Truncate properties. DAC truncates a target table only once during the life span of
an ETL execution. If multiple tasks write to the same table, the following rules
apply:
The first task truncates the target table. This task has the highest priority. Even
if there are multiple tasks that could potentially truncate a tableeither from
the source container or across multiple source containersonly the first task
will truncate the table.
The task reading from the data source with the highest priority truncates the
tables and drops the indexes. The last task writing to the table from the data
source with the highest priority creates the indexes. The last task writing to the
table will create query indexes.
DAC does not truncate the target tables during the execution of the
subsequent tasks even if the Truncate Always or Truncate for Full Load
properties are selected.
If the task belongs to a task group and the task groups Truncate Always or
Truncate for Full Load properties are different from the individual task
truncate properties, the tasks truncate properties are ignored. Note: You can
use a task action if you want to override this behavior. See "Using Actions to
Optimize Indexes and Collect Statistics on Tables" for information about the
actions feature.
Priority of the source connection. When there is more than one source system,
you need to specify the priority of each source connection in the Source Priority
field in the Physical Data Sources tab of Setup view.
Task groups. The first task in the group determines the position of the group in
the dependency graph.
DAC randomly organizes tasks that have the same property values, because it
does not allow parallel reads and writes on any table. If you want to force tasks to
be executed in a particular order, or in parallel, you can create a task group that
allows you to specify an execution order. For instructions on creating a task group,
see "Creating a Task Group"
6-8 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
In the Physical Data Sources tab, set database connections to the transactional and
data warehouse databases.
In the Informatica Servers tab, registered the Informatica Repository Service and
Integration Service.
Created a custom container from which you will select the subject areas for the
execution plan.
Before you attempt to run a multi-source execution plan, you must first define the
priority for each source. The priority specifies the order in which DAC will load the
data from the different sources.
To define a source priority for multi-source execution plans
1.
2.
For each of the physical data sources that will participate in the multi-source
execution plan, enter a numerical value in the Source Priority field.
The lower the numerical value, the higher the priority. For example, if you enter a
value of 1, data from this source will be loaded first.
2.
b.
In the top pane window or in the Edit subtab, enter the following information.
Field
Description
Name
Micro ETL
Analyze
Drop/Create Indices
Inactive
c.
3.
Click Save.
For a micro ETL execution plan, create a subject area in the Subject Areas tab of the
Design view by doing one of the following:
6-9
Assemble the subject area by clicking Assemble in the top pane toolbar. See
"Creating a Subject Area" for more information.
4.
b.
c.
In the Choose Subject Areas dialog, select the appropriate source system
container from the drop-down list.
d.
Query for the subject area you want to associate with the execution plan. For
micro ETL execution plans, query for the subject area you created in step 3.
e.
f.
5.
Click the Connectivity Parameters subtab, and then click Generate in the
bottom pane toolbar.
The Generating Parameters... dialog lists the containers that are involved in
this execution plan.
b.
Enter the number of copies of each container that are needed, and then click
OK.
DAC automatically generates the parameters required for each copy of the
source system container. Note that not all copies require all of the possible
parameters.
c.
In the Value column, for each folder or database connection, select the
appropriate physical folder name or database connection.
For the data source type of FlatFileConnection, make sure you
have copied all files into the directory specified in the DAC system
property InformaticaParameterFileLocation.
Note:
6.
d.
(Optional) If you are extracting data from more than one source system and
want to stagger the data extracts, in the Delay field for the appropriate data
source, enter a value for the number of minutes you want to delay this extract
after the first extract process has started.
e.
(Optional) Set the Prune Time property. This setting subtracts the Prune Time
value from the LAST_REFRESH_DATE and supplies this value as the value
for the $$LAST_EXTRACT_DATE parameter. See "Prune Time Column" for
more information.
(Optional) Add one or more tasks that will run before the ordered tasks generated
by DAC.
a.
b.
c.
Query for and select the task you want to add, and then click Add.
6-10 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
7.
(Optional) Add one or more tasks that will run after the ordered tasks generated
by DAC.
a.
b.
c.
Query for and select the task you want to add, and then click Add.
8.
In the top pane of the Execution Plans tab, make sure the new execution plan is
highlighted, and click Build.
9.
In the Building... dialog, select the option Selected Record Only, to build only the
selected execution plan.
10. Click the Ordered Tasks subtab, and verify the following:
a.
Click Details in the toolbar, and review each tasks predecessor and successor
tasks to confirm tasks common to multiple sources are ordered in a manner
consistent with the priority of the source connection.
b.
Confirm that load tasks appear only once even if there are multiple extracts for
tables common to multiple sources.
c.
For tasks common to multiple sources, click Unit Test in the toolbar, and
confirm that the first common task truncates the common target table and the
following tasks do not. For instructions on unit testing a task, see "Unit Testing
Execution Plan Tasks".
11. Make sure the DAC Server is running. For instructions on starting the DAC Server,
b.
Once the execution plan starts running you can monitor its progress in the Current
Runs tab. For instructions, "Monitoring Execution Plan Processes".
For information about how refresh dates are tracked, see "About Refresh Dates
and DACs Incremental Load Strategy".
To schedule an execution plan, see "Scheduling an Execution Plan".
The execution plans share one or more target tables on the same physical data
source.
An execution plan has a target table that is a source for another execution plan. For
example, execution plan A writes to table 1 on the physical data source DW and
execution plan B reads from table 1 on DW.
An execution plan has a source table that is a target table for another execution
plan. For example, execution plan C reads from table 2 on the physical data source
DW and execution plan D writes to table 2 on DW.
6-12 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Note:
2.
Right-click one of the execution plans you want to compare, and then select
Concurrent Dependency.
3.
From the drop-down list in the Concurrent Dependency dialog, select the
execution plan you want to compare with the execution plan you selected in step
2.
The common target tables between the two execution plans are displayed as well
as the tables that one execution plan writes to and the tables that the other
execution plan reads from.
In the DAC Setup view, select the DAC System Properties tab.
2.
3.
Click in the Value column, and enter a value that specifies the number of
execution plans you want to run in parallel.
4.
Click Save.
5.
Restart the DAC Server by selecting Tools, DAC Server Management, Restart
DAC Server.
2.
Select the execution plan for which you want to define the dependency attribute of
another execution plan.
For example, if you want to define the execution plan Oracle 11.5.10 Enterprise
Sales as independent from the execution plan Procurement and Spend: Oracle
11.5.10, select Procurement and Spend: Oracle 11.5.10 in this step.
3.
4.
Locate the execution plan whose dependency attribute you want to set:
a.
b.
c.
5.
6.
Independent
Defines the execution plan selected in the Concurrent Dependency subtab as
independent of the execution plan selected in the top window.
Dependent
Defines the execution plan selected in the Concurrent Dependency subtab as
dependent on the execution plan selected in the top window
7.
6-14 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Use the Extract Delay feature to stagger the timing of data extraction from
different source systems.
Polling Frequency - Specifies in minutes how often DAC will try to create the
connection.
Upon Timeout - The possible action DAC will take if the Timeout period
elapses without a connection being available. The options are:
Fail - DAC will fail all of the tasks that read and write to the unavailable
source. The failed tasks are marked as Stopped.
Skip - DAC will skip the tasks that read and write to the unavailable source.
The refresh dates for primary and auxiliary source and target tables will not be
persisted. This allows for the next ETL process to pick up the data since the
prior ETL event was not successful. The skipped tasks are marked as
Completed, and the task details reflect a Not Executed status.
In this example, the Lazy Initialization property is enabled on the CRM source.
The Polling Frequency is set at one minute, and the Timeout period is set to 120
minutes. Therefore, DAC will poll the CRM source every minute for 120 minutes.
If the connection becomes available within 120 minutes, DAC will create the
connection pool and the ETL will proceed. If the Timeout period elapses, and Fail
is selected for the Upon Timeout property, the tasks that read and write to the
unavailable source will fail. If the Timeout period elapses, and Skip is selected, the
tasks will be skipped, and the extract from the financial source will proceed.
Condition SQL - A SQL that can be executed against the data source to verify
if the data source is ready.
Cleanup SQL - A SQL that can be executed upon the successful occurrence of
the event for the data source and upon successfully executing the Condition
SQL. This property applies only if a Condition SQL is defined.
You can set up an event delay for situations similar to those described above as well as
a combination of the examples described above.
To set up an event delay
1.
2.
In the top pane, select the physical data source for which you want to define an
event delay.
3.
4.
5.
Click in the Name field to expose the drop-down list, and select
EventBasedDelay.
6.
7.
8.
Complete the fields in the Property Value dialog using the following information:
Field
Description
Lazy Initialization
6-16 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Field
Description
Condition SQL
Click in the field to open a text box where you can enter a
SQL statement that defines a condition that DAC will
execute against the data source to verify if the data source
is ready.
This SQL should return a value in the form of a number. A
result of 0 indicates the data source is not ready. A
non-zero result means the event has happened.
Cleanup SQL
Timeout (min)
Upon Timeout
Fail. DAC will fail all of the tasks that read and write
to the unavailable source. The failed tasks are marked
as Stopped.
For example, using the scenario described in the
introduction to this section, the financial data extract
will occur and the financial-specific load tasks will
run, but the CRM data extract will not occur and load
tasks that are specific to both financial and CRM data
will not run.
Skip. DAC will skip the tasks that read and write to
the unavailable source. The refresh dates for primary
and auxiliary source and target tables will not be
persisted. This allows for the next ETL process to pick
up the data since the prior ETL event was not
successful. The skipped tasks are marked as
Completed, and the task details reflect a Not Executed
status.
For example, using the scenario described in the
introduction to this section, the tasks related to CRM
and to both CRM and financial data will be skipped.
Extracts and loads related to the financial source will
occur.
9.
The email notification contains the execution plan name, the ETL run name and
timestamp, the data source name, and the data source usage category. The recipients of
the email are the email accounts set up in the procedure "Setting Up Email
Notifications in the DAC Client and Server".
When you define the data source usage notification properties, you can also define
custom SQL that will be executed upon the occurrence of the specified data source
usage category. In the custom SQL, you can use the DAC variable @DAC_
NOTIFICATION_RECORD in a parameter.
To set up a notification
1.
2.
In the top pane, select the physical data source for which you want to define an
event delay.
3.
4.
5.
Click in the Name field to expose the drop-down list, and select the appropriate
data source usage category.
6.
7.
8.
Complete the fields in the Property Value dialog using the following information:
Field
Description
Send Email
Execute SQL
Click in the field to open a text box where you can enter a
SQL statement that DAC will execute against the data
source when the selected operation occurs.
Is Stored Procedure
9.
6-18 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
How the DAC Server Handles Requests to Start and Stop Execution Plans
How the DAC Server Handles Requests to Start and Stop Execution Plans
Starting an Execution Plan
When the DAC Server receives a request to start an execution plan, it performs a series
of checks to verify that the execution plan can be started. It first checks that an
execution plan with the requested name exists and that the execution plan is active.
Next, it checks the status of the execution plan that last ran. If an execution plan is still
running and the DAC Server receives a request to start another execution plan, the
request will be rejected. If an execution plan failed, a request to run the same execution
plan again will be executed. However, a request to run a different execution plan will
be rejected. If the execution plan that last ran completed successfully, a request to run a
new execution plan will be executed.
When the DAC Server receives a request to start an execution plan, it will issue a
warning if any of the following conditions are true. (A warning is for informational
purposes and does not mean the execution plan will not start.)
The Generic Task Concurrency Limit value in the DAC System Properties tab is
not a positive number.
There are no active Informatica Integration Service or Repository Service
registered in the Informatica Servers tab.
One or more Informatica Integration Services do not have the passwords defined
in the Informatica Servers tab.
One or more Informatica Integration Services do not have a Num Parallel
Workflows per EP value properly defined in the Informatica Servers tab.
One or more data sources do not have the Table Owner or Table Owner Password
values properly defined in the Physical Data Sources tab.
One or more data sources do not have a maximum number of connections (Num
Connections per EP) value properly defined in the Physical Data Sources tab.
One or more data sources do not have a Data Source Number defined in the
Physical Data Sources tab.
The name of the execution plan that is running is different from the name in the
request.
There is no execution plan currently running.
How the DAC Server Handles Requests to Start and Stop Execution Plans
6-20 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
7
7
This chapter provides information about customizing DAC objects for inclusion in
ETL processes.
This chapter contains the following topics:
7-1
Note:
When changes are made to objects in the container that owns them, the change is
instantaneous.
Changes made to parent objects in the owner container are automatically pushed
to the parent referenced objects.
When you add child objects to a parent object, you must use the Push to
References right-click command (Design view) to push the changes to the child
referenced objects. For example, if you add a column to a table that is registered in
DAC, the new column is not automatically added to the references in the other
containers referencing the parent object. You must use the Push to References
command to effect the column changes in the other referenced tables.
When you delete a referenced object, only the referenced object is deleted. The
original object is not deleted.
If you delete an object from the owner container, the object is deleted as well as
referenced objects in other containers. This is referred to as a deep delete. For
example, if you delete a table from the owner container, the table and columns are
deleted from the owner container and all the containers that reference this object.
If you delete a column from the owner table, the column is deleted in all the
referenced objects.
If you delete child objects from the owner object, the referenced child objects are
automatically deleted.
Start your work with tasks in Informatica. After you create a workflow, do the
following in the DAC Task tab:
Ensure all the source and target tables are defined for the task.
You can use the task synchronize functionality to import data from
Informatica. You can also manually assign the source or target tables.
Select at least one primary table because the incremental and full mode properties
are determined based on the refresh dates of the primary table.
Design tasks so that they load only one table at a time.
Define granular tasks rather than tasks that include bigger blocks of processes.
Granular tasks are more efficient and have better restartability.
7-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Do not truncate a table on the source system tables (for example, Oracle, Siebel or
PeopleSoft sources).
Ensure the truncate property for the target tables is set properly.
For tables that need to get truncated regardless of the mode of the run (Full or
Incremental), set the Truncate Always property to True.
For tables that need to get incrementally loaded, set the Truncate for Full Load
property to True.
Select the Analyze Table option if the task should analyze the table. The default
value for this option is True if either of the Truncate options are selected.
Do not truncate a table more than once within the single life span of an ETL.
If a task that writes to a target table is contingent upon another table being loaded,
use conditional tables. This ensures that the task qualifies only if the conditional
table is part of the subject area design.
Assign an appropriate phase to the task. An understanding of task phases is
essential to understanding ETL processes.
If you want to force a relationship where none exists, consider using phase
dependencies. For example, if you have an ETL process in which the extract facts
and extract dimensions do not share any common source or target tables, but the
design requires that the extract facts should run before extracting dimensions,
then, for the task that extracts facts, add extract dimension as the phase that waits.
For more information about phase dependencies, see "Tasks Tab: Phase
Dependency Subtab".
Ensure you do not introduce conflicting phase dependencies. This can cause the
DAC Server to hang.
If the source qualifier needs to use a data parameter, always use the DAC date
parameter that can be formatted to the database-specific syntax.
Do not create task groups unnecessarily. Doing so can adversely impact the DACs
auto-dependency functionality, which automatically orders tasks for an execution
plan. Create task groups only to satisfy the points listed below.
Avoid circular relationships among tasks if the tasks are of the same phase. For
example, avoid situations in which Task 1 reads from Table A and writes to Table
B, and Task 2 reads from Table B and writes to Table A. You can use task groups to
avoid these situations. Note: If tasks belong to different phases, this situation is
acceptable.
If you have many tasks belonging to the same phase that write to the same table,
you can use task groups to run the tasks in parallel. If the target tables need to be
truncated before the tasks are run, select the properties Truncate Always and
Truncate Full Load in the Task Group tab.
Do not mix extracts and loads under a single table group.
Do not make Task Groups for obvious ordering needs. DAC handles ordering in
such cases.
If a source system container uses a task group, make other containers that
reference the task also include the task group.
7-3
Index names must be unique. Oracle, DB2 and Teradata databases enforce this rule
by default. However, SQL Server databases do not enforce this rule. If you are
using a SQL Server database, you must ensure all index names are unique.
Always use all upper case characters for column names.
If you have a foreign key column, associate the foreign key table and the join
column. DAC uses this information to identify all the related tables to be loaded
when a certain table needs to be loaded in the data warehouse.
Do not register any columns for source system container tables.
Ensure you add all the appropriate system columns. For example, all tables should
have the following:
Pay attention to which columns need to gather statistics. Note that column
statistics are somewhat equivalent to indexes.
If you would have had indexes that span multiple columns for other
databases, consider defining multi-column statistics for Teradata.
7-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
If you have a foreign key column, associate the foreign key table with the join
column. DAC uses this information to identify all the related tables to be loaded
when a certain table needs to be loaded in the data warehouse.
For Teradata databases:
Pay attention to which columns need to gather statistics. Note that column
statistics are somewhat equivalent to indexes.
If you would have had indexes that span multiple columns for other
databases, consider defining multi-column statistics for Teradata.
Use configuration tags to tag tasks that you do not want to be part of all the
defined subject areas.
A tagged task can be re-associated with a subject area by assigning the
configuration tag to the subject area.
Use source system parameters when tasks in the source system container need a
particular value.
To define a subject area, associate only fact tables with it. DAC automatically
computes which additional aggregate tables and dimension tables to associate
with the subject area based on the related tables you define and foreign key
relationships.
If you delete a task from a subject area using the Delete button on the Task tab, the
next time you assemble the subject area the task may be included. However, if you
inactivate the task by selecting Inactive in the Task tab, the task will remain
inactive when you re-assemble the subject area.
Avoid adding tasks or inactivating tasks manually.
7-5
If many tasks with the same name across source system containers read and write
to the same data source, DAC will consider them to be the same task.
If the logical source to physical mapping yields multiple records, DAC will
produce as many runtime instances of the task.
DAC orders tasks in the most efficient manner possible based on the following:
Phase of task
Note:
You can add tables, columns, and indexes to the data warehouse, and you can modify
the existing objects. Customizing the data warehouse in this way requires using DAC
and Informatica client tools.
Figure 71 shows the major steps required for adding a new object to the data
warehouse or modifying existing objects. As shown in Figure 71, you can begin the
customization process by adding or modifying the new data warehouse object in DAC
and then using the DACs schema creation and upgrade functionality to propagate the
changes to the data warehouse. Alternatively, you can add or modify the object
directly in the data warehouse database and then use the DAC's Import from Database
command to add the new object in DAC.
7-6 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
In the Design view, select the appropriate source system container from the
drop-down list.
7-7
2.
Click New.
b.
In the Edit subtab, enter the appropriate information about the table, and click
Save.
For a description of the fields in this tab, see "Tables Tab".
3.
b.
Enter the appropriate column information for each column you want to add to
the table, and click Save.
c.
Note:
4.
Create the new tables and columns in the data warehouse database.
DAC provides several ways to create and upgrade data warehouse schemas.
Carefully review Chapter 10, "Managing Data Warehouse Schemas," and select the
method that best suits your requirements.
To add a new table and columns using the DAC's Import command
1.
Add the new table and column definitions into the data warehouse database.
2.
In the DAC Design view, select the appropriate source system container from the
drop-down list.
3.
In the Tables tab, right-click and select Import from Database, Import
Database Tables.
b.
c.
Optionally, enter filter criteria to identity the table name you entered in Step 1.
See "DAC Query Commands and Operators" for available filter commands
and operators.
d.
e.
In the list of tables displayed, select the Import check box for the tables you
want to import.
f.
4.
In the Tables tab, query for the table you imported in Step 3.
b.
With the table highlighted, right-click and select Import from Database,
Import Database Columns.
c.
In the Importing Columns... dialog, select Selected Record Only, and then
click OK.
d.
7-8 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Explanation
e.
In the list of columns displayed, select the Import check box for the columns
you want to import.
f.
Add the new index definition into the data warehouse database.
2.
In the DAC Design view, select the appropriate source system container from the
drop-down list.
3.
In the Tables tab, query for the table for which you want to import index
definitions.
4.
5.
Choose to import indexes for a selected table or for all the records retrieved in the
query, and click OK.
6.
In the Import Indices dialog, select the appropriate data warehouse from the Data
Sources drop-down list.
7.
In the list of indexes displayed, select the Import check box for the indexes
you want to import.
b.
7-9
In the DAC Design view, select the appropriate source system container from the
drop-down list.
2.
Create a custom logical folder for the custom folder you created in the Informatica
repository.
3.
a.
On the Tools menu, select Seed Data, and then select Task Logical Folders.
b.
c.
Enter a name for the custom logical folder, and click Save.
d.
Create a custom physical folder for the custom folder you created in the
Informatica repository.
a.
On the Tools menu, select Seed Data, and then select Task Physical Folders.
b.
c.
d.
4.
5.
Register the custom logical and physical folders you created in steps 2 and 3 in the
Source System Folders tab.
a.
b.
Click New.
c.
In the Edit subtab, enter the name of the custom logical folder in the Logical
Folder field.
d.
Enter the name of the custom physical folder in the Physical Folder field, and
click Save.
In the Design view, select Tasks, and click New in the top pane toolbar.
b.
c.
d.
7-10 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
e.
In the Tasks tab, enter the remaining information required for the task.
For a description of the fields in this tab, see "Tasks Tab".
The new table is now ready to be associated with a subject area. For information
about creating a subject area, see "Creating a Subject Area".
In the Design view, select the appropriate source system container from the
drop-down list.
2.
In the Tasks tab, query for the task for which you want to add a phase dependency,
and make sure it is highlighted.
3.
4.
5.
In the Choose Phases dialog, query for a task phase, select the phase, and click
Add.
6.
Click OK in the message box that states the phase was added.
7.
In the window on the right side of the dialog, select the appropriate values for the
following properties:
Property
Description
Action
Possible values:
Grain
Possible values:
Property
Description
Scope
9.
In the Subject Areas tab, query for the appropriate subject area.
b.
Click Assemble.
b.
c.
Enter the number of copies of each container that are needed, and then click
OK.
DAC automatically generates the parameters required for each copy of the
source system container. Note that not all copies require all of the possible
parameters.
d.
In the Value column, for each folder or database connection, select the
appropriate physical folder name or database connection.
For the data source type of FlatFileConnection, make sure you
have copied all files into the directory specified in the DAC system
property InformaticaParameterFileLocation.
Note:
e.
7-12 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
DAC does not allow parallel reads and writes on the same table; therefore, DAC
randomly assigns priorities to tasks that have the same properties. You can group tasks
by using the Task Group feature to enforce a particular behavior.
The task group feature can be useful in the following situations:
You want to enforce a particular order for multiple tasks writing to the same table.
You want tasks to run in parallel (because you know the tasks have no
dependencies among them).
You want to create a task action to truncate a table when you have multiple tasks
writing to the same table.
You have circular tables, and need to enforce an order. For example, task 1 reads
from table A and writes to table B, and task 2 reads from table B and writes to
table A.
In the Design view, select the appropriate source system container from the
drop-down list.
2.
In the Task Groups tab, click New in the top pane toolbar.
3.
In the Edit subtab, enter a name and select the appropriate properties.
4.
Click the Child Tasks subtab, and click Add/Remove in the toolbar.
5.
In the left-hand window of the Choose Child Tasks dialog, query for the tasks you
want to add to the task group.
6.
7.
In the window on the right side, enter a value in the Dependency Order field to
specify an execution order.
8.
9.
subject area. This method only applies to tasks that are autogenerated tasks of a
subject area. For instructions, see "To reassign autogenerated tasks to a subject
area".
Assign only configuration tag tasks to a subject area (excludes the subject area's
autogenerated tasks)
You can also set up a configuration tag so that only tasks that were assigned to the
configuration tag participate in a specific subject area. In this case, the subject
area's autogenerated tasks do not participate. For instructions, see "To assign only
configuration tag tasks to a subject area (excludes the subject area's autogenerated
tasks)"
In the Design view, select the appropriate source system container from the
drop-down list.
2.
3.
a.
In the Configuration Tags tab, click New in the top pane toolbar.
b.
c.
d.
Click Save.
With the new configuration tag highlighted in the top pane, click the Tasks
subtab.
b.
c.
In the Tasks dialog, query for the tasks you want to add to the configuration
tag.
d.
e.
In Design view, select the appropriate source system container from the
drop-down list.
2.
In the Configuration Tags tab, query for the configuration tag that contains the
tasks you want to reassign to a subject area.
3.
Verify the configuration tag contains the appropriate tasks by clicking the Tasks
subtab and reviewing the list of tasks associated with this configuration tag.
Only a subject areas autogenerated tasks will be reassigned. If
non-autogenerated tasks appear in the list, the DAC will ignore them.
Note:
7-14 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
4.
5.
Associate the configuration tag with the subject areas to which you want to
reassign the tasks.
a.
With the configuration tag highlighted in the top pane, click the Subject Areas
subtab.
b.
c.
In the Subject Areas dialog, query for one or more subject areas to which you
want to reassign the task or tasks.
d.
e.
In the Subject Area tab, query for all the subjects areas you added to the
configuration tag.
b.
In the Design view, select the appropriate source system container from the
drop-down list.
2.
3.
4.
5.
a.
In the Configuration Tags tab, click New in the top pane toolbar.
b.
c.
d.
Click Save.
With the new configuration tag highlighted in the top pane, click the Tasks
subtab.
b.
c.
In the Tasks dialog, query for the extraneous tasks you want to add to the
configuration tag.
d.
e.
Associate the configuration tag with the subject areas to which you want to add
the non-autogenerated tasks.
a.
With the configuration tag highlighted in the top pane, click the Subject Areas
subtab.
b.
c.
In the Subject Areas dialog, query for one or more subject areas to which you
want to add the non-autogenerated tasks.
d.
e.
In the Subject Area tab, query for all the subjects areas you added to the
configuration tag.
Customizing ETL Processes 7-15
b.
To assign only configuration tag tasks to a subject area (excludes the subject area's
autogenerated tasks)
1.
In the Design view, select the appropriate source system container from the
drop-down list.
2.
In the Subject Areas tab, query for the subject area to which you want to add
configuration tag tasks.
Note:
3.
Select the Configuration Tag Tasks Only check box, and click Save.
4.
5.
6.
7.
a.
In the Configuration Tags tab, click New in the top pane toolbar.
b.
c.
d.
Click Save.
With the new configuration tag highlighted in the top pane, click the Tasks
subtab.
b.
c.
In the Tasks dialog, query for the tasks you want to add to the configuration
tag.
d.
e.
With the configuration tag highlighted in the top pane, click the Subject Areas
subtab.
b.
c.
In the Subject Areas dialog, query for the appropriate subject area.
d.
e.
In the Subject Area tab, query for all the subjects areas you added to the
configuration tag.
b.
7-16 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Index actions can override the default behavior for dropping and creating indexes
by mode type (full load, incremental load, or both). The Index action types are
Create Index and Drop Index.
For example, you can define an index action to create indexes for tasks with the
commands defined for full loads, or incremental loads, or both types, or you can
define an action to drop indexes at a certain time on specific tables. Index actions
override all other index properties.
Table actions can override the default behavior for truncating and analyzing
tables by mode type. The Table action types are Truncate Table and Analyze Table.
For example, you can define a table action to truncate tables with the commands
defined for full loads, or incremental loads, or both. Table actions override all
other table properties.
Task actions can add new functionality based on various task behaviors. The
following task action types are available:
Failure Action. Executes a SQL script if a task fails during its execution.
Upon Failure Restart. Executes a SQL script when a task that previously failed
is restarted.
In the DAC Client, on the Tools menu, select Seed Data, and then select one of the
following:
Index Actions
Table Actions
Task Actions
3.
In the new record field, enter a descriptive name for the action, and then click
Save.
4.
5.
Flat View displays the SQL entries in a list format in their order of execution.
Category View displays the entries by the categories SQL and Stored
Procedure.
You can reorder the entries in the tree by dragging and dropping them.
6.
Click Add.
7.
Field
Description
Name
Type
7-18 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Field
Description
Database Connection
Type
Table Type
Continue on Fail
Retries
Valid Database
Platforms
8.
9.
Note:
Repository Object".
In the Design view, navigate to one of the following tabs, depending on the object
type for which you want to assign an action:
Indices tab
Tables tab
Tasks tab
2.
Select or query for the object for which you want to assign an action.
3.
With the appropriate object selected in the top pane, select the Actions subtab.
4.
5.
b.
c.
Double-click in the Action field to open the Choose Action dialog, and select
an action.
d.
e.
7-20 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Table 71
Function
Description
getAdditionalColumns()
getAnalyzeStatement()
getAnalyzeTableStatement()
getBitMapString
getClusteredString
getCreateIndexStatement()
getDBType()
getDropIndexStatement()
getHashString()
getImageSuffix()
getIndexColumns()
getIndexName()
getIndexTableSpace()
getNamedSource()
getRvrsScanString()
getTableName()
getTableOwner()
getTableSpace()
getTruncateTableStatement()
getUniqueColumns()
getUniqueString()
Table 72
Function
Description
getAnalyzeTableStatement()
getDBType()
Description
getImageSuffix()
getCreateIndexStatement()
getNamedSource()
getDropIndexStatement()
getTableName()
getTableOwnerName()
getTableSpace()
getTruncateTableStatement()
Table 73
Function
Description
getAnalyzeTableStatement()
getDBType()
getImageSuffix()
getNamedSource()
getTableName()
getTableOwner()
getTableSpace()
getTruncateTableStatement()
Note:
7-22 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
2.
Query for the task to which you want add multiple workflows.
3.
4.
b.
c.
d.
e.
Click in the Value field to open the Enter Parameter Value dialog.
f.
g.
In the appropriate database fields, enter the full command name for both
database types.
For example, enter SIL_PersonDimension_Full in the Oracle field and SIL_
PersonDimension_Full_TD in the Teradata field.
5.
b.
c.
d.
e.
Click in the Value field to open the Enter Parameter Value dialog.
Customizing ETL Processes 7-23
f.
g.
In the appropriate database fields, enter the incremental command name for
both database types.
For example, enter SIL_PersonDimension in the Oracle field and SIL_
PersonDimension_TD in the Teradata field.
6.
7.
8.
9.
Click Save.
7-24 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
8
Defining and Managing Parameters
Overview of Parameters
Defining Parameters
Overview of Parameters
This section contains the following topics:
8-1
Overview of Parameters
The ETL start time is an example of a runtime parameter that you can define at the
source system, task, or execution plan level. Runtime parameters use predefined
DAC variables to access attribute values that vary for different ETL runs. See
"About DAC Variables" for more information.
Performance can be enhanced by defining parameters using database-specific
syntax to write query hints. DAC passes database-specific parameters to the
Informatica Source Qualifier as a SQL override.
You can define static or runtime parameters in the DAC repository (using the DAC
Client) to apply to source systems, tasks, or execution plans. You can also define
parameters whose values come from outside of DAC, such as from external relational
sources that DAC accesses through SQL interfaces, or from external technology stacks
that DAC accesses through a Java API interface.
In addition, some parameters used by Oracle BI Applications are defined by the user
in the Oracle BI Applications Configuration Manager. See Oracle Fusion Middleware
Configuration Guide for Oracle Business Intelligence Applications for information about the
parameters that are defined in the Configuration Manager. Also, depending on your
environment, some predefined parameters used by Oracle BI Applications may be
held in flat files named parameterfileDW.txt and parameterfileOLTP.txt, which are
stored in the directory <Domain_Home>\dac\Informatica\parameters\input. Oracle
recommends that you do not modify these parameter flat files. Instead, if you need to
customize the value of the parameters, you can define new parameters in the DAC
repository.
Note:
8-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Overview of Parameters
Task Parameters
Task parameters apply to one particular task in a source system container. You can
view existing task parameters and define new ones in the Parameters subtab of the
Task tab in the Design view.
Rules of Precedence
DAC evaluates the hierarchy of precedence for parameters as follows:
1.
2.
Task parameters take precedence over source system parameters and global
external parameters.
3.
For example, if the same parameter is registered as a source system parameter and as a
task parameter, DAC will evaluate the value of the task parameter. Similarly, if the
same parameter is registered as a source system parameter and as a global external
parameter, DAC will evaluate the value of the source system parameter.
8-3
Overview of Parameters
8-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Overview of Parameters
For instructions on defining a parameter using the Multi-Parameter Text data type, see
"Defining a Multi-Parameter Type Parameter".
Multi-Parameter Timestamp
Applies to source system and task parameters. The value for the parameter is defined
as timestamps in name-value pairs using user-defined SQL.
For instructions on defining a parameter using the Multi-Parameter Timestamp data
type, see "Defining a Multi-Parameter Type Parameter".
External-Parameter Text
Applies to source system parameters only. The value for the parameter is defined
using a parameter producer Java API. The External-Parameter Text data type enables
you to create a library and classes to implement the DACTextParameterProducer
interface.
For instructions on defining a parameter using the External-Parameter Text data type,
see "Defining an External Type Parameter".
External-Parameter Timestamp
Applies to source system parameters only. The value for the parameter is defined
using a parameter producer Java interface. The External-Parameter Timestamp data
type enables you to create a library and classes to implement the
DACTimestampParameterProducer interface.
For instructions on defining a parameter using the External-Parameter Timestamp
data type, see "Defining an External Type Parameter".
Global Multi-Parameter Text or Timestamp
Applies to global parameters only. The value for the parameter is defined as
name-value pairs using user-defined SQL.
For instructions on defining a global parameter, see "Defining a Global External
Parameter".
8-5
Oracle recommends that you do not modify the parameter text files. Instead, if you
need to customize the value of the parameters, you can define parameters in the DAC
repository at either the source system level or the task level.
Note:
8-6 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
@DAC_ETL_START_TIME. Returns the timestamp for the start time of the ETL
process.
@DAC_ETL_START_TIME_FOR_SOURCE. Returns the timestamp for the
source database.
@DAC_ETL_START_TIME_FOR_TARGET. This variable returns the timestamp
for the target database.
@DAC_ETL_PRUNED_START_TIME. Returns the current execution plans
actual start time minus the prune minutes.
@DAC_ETL_PRUNED_START_TIME_FOR_SOURCE. Returns the current
execution plans actual start time adjusted to the source database time zone, minus
the prune minutes.
@DAC_ETL_PRUNED_START_TIME_FOR_TARGET. Returns the current
execution plans actual start time adjusted to the target database time zone, minus
the prune minutes.
8-7
Defining Parameters
Defining Parameters
This section provides instructions for defining parameters based on the data type.
To define a source system parameter, in the Design view, click the Source
System Parameters tab, and then click New in the toolbar.
To define a task parameter, in the Design view, click the Tasks tab, then click
the Parameters subtab, and then click New in the bottom pane toolbar.
2.
In the new record field, enter a parameter name in the Name field.
3.
4.
5.
Click in the Value field to open the Enter Parameter Value dialog.
6.
Static. Specifies a value that remains constant for all ETL runs.
Runtime. Specifies the value will be provided by DAC during the execution of
the task.
8-8 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Defining Parameters
7.
If you selected the Static option, enter a text value in the text window, and click
OK.
8.
If you selected the Runtime option, select a DAC Variable from the list, and click
OK.
9.
Click Save.
Note: You can inactivate the parameter by selecting the Inactive check box.
To define a source system parameter, in the Design view, click the Source
System Parameters tab, and then click New in the toolbar.
To define a task parameter, in the Design view, click the Tasks tab, then click
the Parameters subtab, and then click New in the bottom pane toolbar.
2.
In the new record field, enter a parameter name in the Name field.
3.
4.
5.
Click in the Value field to open the Enter Parameter Value dialog.
6.
7.
8.
9.
b.
Click in the appropriate database type field to open the text box.
b.
Note: You can inactivate the parameter by selecting the Inactive check box.
To define a source system parameter, in the Design view, click the Source
System Parameters tab, and then click New in the toolbar.
8-9
Defining Parameters
To define a task parameter, in the Design view, click the Tasks tab, then click
the Parameters subtab, and then click New in the bottom pane toolbar.
2.
In the new record field, enter a parameter name in the Name field.
3.
4.
5.
Click in the Value field to open the Enter Parameter Value dialog.
6.
7.
8.
Static. Specifies a value that remains constant for all ETL runs.
Runtime. Specifies the value will be provided by DAC during the execution of
the task.
SQL. Enables you to define the parameter using SQL.
b.
Click in the Value field to open the Enter Parameter Value dialog.
b.
c.
From the Function list, select a format to which DAC will convert the date. If
you select Custom, enter a custom date format.
If you select SQL Syntax or SQL Syntax (Date Only), select a Connection Type.
9.
Click in the SQL field to open the Enter Parameter Value dialog.
b.
c.
Note: You can inactivate the parameter by selecting the Inactive check box.
To define a source system parameter, in the Design view, click the Source
System Parameters tab, and then click New in the toolbar.
To define a task parameter, in the Design view, click the Tasks tab, then click
the Parameters subtab, and then click New in the bottom pane toolbar.
2.
In the new record field, enter a parameter name in the Name field.
3.
8-10 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Defining Parameters
4.
5.
Click in the Value field to open the Enter Parameter Value dialog.
6.
7.
8.
Click Save.
Note: You can inactivate the parameter by selecting the Inactive check box.
Text Interface
The External-Parameter Text data type uses the DACTextParameterProducer interface
to return string values. The interface maps data source number IDs, database types,
JDBC connections, and initialization parameters.
The DACTextParameterProducer interface is as follows:
public interface DACTextParameterProducer {
/**
* Populating external parameters
*
* @param runtimeContext - runtime properties like DNS id to type map
* @param jdbcConnection
* @throws DACParameterProducerException
*/
public void init(Map<Object, Object> runtimeContext
,java.sql.Connection jdbcConnection) throws
DACParameterProducerException;
/**
* @param dsnId
* @param taskName
* @return all parameters (global, dsn-specific and dsn-task specific)
that apply to a given task
* @throws DACParameterProducerException
*/
public Map<String, String> getParameters(int dsnID
,String taskName) throws DACParameterProducerException;
/**
* Forcing implementing classes to explicitly implement finalize method.
* All parameter stores inside are expected to be cleared as a result.
*
* @throws Throwable
*/
public void finalize() throws Throwable;
}
Defining Parameters
Create a valid Java archive with one or more classes that will implement the
DACTextParameterProducer interface.
In this procedure, "abc.paramproducer.jar" is used as an example for the archive
name.
2.
3.
For DAC installations on Windows, add the archive to the set DACLIB entry in the
config.bat file.
For example, the set DACLIB entry would look similar to the following after
adding the archive named abc.paramproducer.jar:
set DACLIB=.\DAWSystem.jar;.;.\lib\wsclient_
extended.jar;.\lib\wls-jse-client-wsm-dependencies.jar;.\lib\biacm.paramproduce
r.jar; .\lib\abc.paramproducer.jar;
4.
In DAC installations on UNIX, add the archive to the export DACLIB entry in the
config.sh file.
For example, the export DACLIB entry would look similar to the following after
adding the archive named abc.paramproducer.jar:
export DACLIB=./DAWSystem.jar:.:./lib/wsclient_
extended.jar:./lib/wls-jse-client-wsm-dependencies.jar:./lib/biacm.paramproduce
r.jar:./lib/ abc.paramproducer.jar:
5.
If the DAC Server is deployed in WebLogic, copy the archive to the domains
library directory.
6.
b.
c.
d.
e.
f.
Click in the Value field to open the Enter Parameter Value dialog.
g.
h.
Enter the full class name for the interface in the External API field.
i.
Click OK.
8-12 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Defining Parameters
7.
Note: You can inactivate the parameter by selecting the Inactive check box.
Timestamp Interface
The External-Parameter Timestamp data type uses the
DACTimestampParameterProducer interface to return timestamp values. DAC
formats the timestamp during the ETL process according to your specifications.
The DACTimestampParameterProducer interface is as follows:
public interface DACTimestampParameterProducer {
/**
* Populating external parameters
*
* @param runtimeContext - runtime properties like DNS id to type map
* @param jdbcConnection
* @throws DACParameterProducerException
*/
public void init(Map<Object, Object> runtimeContext
,java.sql.Connection jdbcConnection) throws
DACParameterProducerException;
/**
* @param dsnId
* @param taskName
* @return all parameters (global, dsn-specific and dsn-task specific) that
apply to a given task
* @throws DACParameterProducerException
*/
public Map<String, Timestamp> getParameters(int dsnId
,String taskName) throws DACParameterProducerException;
/**
* Forcing implementing classes to explicitly implement finalize method.
* All parameter stores inside are expected to be cleared as a result.
*
* @throws Throwable
*/
public void finalize() throws Throwable;
}
Create a valid Java archive with one or more classes that will implement the
DACTimestampParameterProducer interface.
In this procedure, "abc.paramproducer.jar" is used as an example for the archive
name.
2.
Defining Parameters
3.
For DAC installations on Windows, add the archive to the set DACLIB entry in the
config.bat file.
For example, the set DACLIB entry would look similar to the following after
adding the archive named abc.paramproducer.jar:
set DACLIB=.\DAWSystem.jar;.;.\lib\wsclient_
extended.jar;.\lib\wls-jse-client-wsm-dependencies.jar;.\lib\biacm.paramproduce
r.jar; .\lib\abc.paramproducer.jar;
4.
In DAC installations on UNIX, add the archive to the export DACLIB entry in the
config.sh file.
For example, the export DACLIB entry would look similar to the following after
adding the archive named abc.paramproducer.jar:
export DACLIB=./DAWSystem.jar:.:./lib/wsclient_
extended.jar:./lib/wls-jse-client-wsm-dependencies.jar:./lib/biacm.paramproduce
r.jar:./lib/ abc.paramproducer.jar:
5.
If the DAC Server is deployed in WebLogic, copy the archive to the domains
library directory.
6.
b.
c.
d.
e.
7.
f.
Click in the Value field to open the Enter Parameter Value dialog.
g.
h.
Enter the full class name for the interface in the External API field.
i.
j.
k.
Click OK.
Note: You can inactivate the parameter by selecting the Inactive check box.
Defining Parameters
To define a source system parameter, in the Design view, click the Source
System Parameters tab, and then click New in the toolbar.
To define a task parameter, in the Design view, click the Tasks tab, then click
the Parameters subtab, and then click New in the bottom pane toolbar.
2.
In the new record field, enter a parameter name in the Name field.
3.
4.
5.
Click in the Value field to open the Enter Parameter Value dialog.
6.
7.
8.
Click Save.
Note: You can inactivate the parameter by selecting the Inactive check box.
To define a source system parameter, in the Design view, click the Source
System Parameters tab, and then click New in the toolbar.
To define a task parameter, in the Design view, click the Tasks tab, then click
the Parameters subtab, and then click New in the bottom pane toolbar.
2.
In the new record field, enter a parameter name in the Name field.
3.
4.
5.
Click in the Value field to open the Enter Parameter Value dialog.
6.
7.
Click Save.
Note: You can inactivate the parameter by selecting the Inactive check box.
Defining Parameters
1.
In the DAC Client, on the Tools menu, select Seed Data, Global External
Parameters.
The Global External Parameters dialog is displayed.
2.
3.
In the new record field, enter a name for the parameter in the Name field.
4.
5.
By DSN-Task. Returns name-value pairs for a specific data source and task.
6.
Click in the Value field to open the Enter Parameter Value dialog.
7.
8.
If you selected the Global Multi-Parameter Text data type, enter the parameter
definition as a SQL statement.
9.
If you selected the Global Multi-Parameter Timestamp data type, from the
Function list, select a format to which DAC will convert the date. If you select
Custom, enter a custom date format.
8-16 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
9
Designing Subject Areas
Note:
Tables. Which tables need to be populated in the data warehouse? From which
tables does the organization source data? What tables will create the star schemas?
Subject areas. Do the subject areas cover all the relevant tables?
To preview a subject area, follow the procedure "Creating a Subject Area" through the
assembly and review stages, but do not complete the process (by clicking Accept in the
Subject Area Assembly dialog) unless the subject area is suitable for your needs.
DAC identifies the dimension tables associated with the facts and adds these
tables to the subject area.
2.
DAC identifies the related tables, such as aggregates, associated with the fact or
dimension tables and adds them to the subject area definition.
3.
DAC identifies the tasks for which the dimension and fact tables listed in the two
processes above are targets tables and adds these tasks into the subject area.
Tasks that DAC automatically assigns to a subject area are indicated with the
Autogenerated flag (in the Tasks subtab of the Subject Areas tab).
You can inactivate a task from participating in a subject area by selecting the
Inactive check box (in the Tasks subtab of the Subject Areas tab). When the
Inactive check box is selected, the task remains inactive even if you reassemble the
subject area.
You can also remove a task from a subject area using the Add/Remove command
in the Tasks subtab of the subject Areas tab, but when you remove a task it is only
removed from the subject area until you reassemble the subject area.
4.
DAC identifies the source tables for the tasks identified in the previous process
and adds these tables to the subject area.
DAC performs this process recursively until all necessary tasks have been added to the
subject area. A task is added to the subject area only once, even if it is associated with
several tables in the subject area. DAC then expands or trims the total number of tasks
based on the configuration rules, which are defined as configuration tags. This process
can be resource intensive because DAC loads all of the objects in the source system
container into memory before parsing.
In the Design view, select the appropriate source system container from the
drop-down list in the toolbar.
2.
3.
4.
9-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
b.
If you want to assign only configuration tag tasks to the subject area and
exclude the subject areas autogenerated tasks, select the Configuration Tag
Tasks Only check box.
c.
Click Save.
5.
Make sure the new subject area name is highlighted in the top pane, and click the
Tables subtab.
6.
7.
8.
Select the fact table (use Shift+click to select more than one table), and click Add.
The tables are added to the right-hand window, which represents the subject area.
9.
If you select the option All Records in the List, DAC will assemble all the subject
areas listed in the top pane.
DAC assembles the selected subject area by determining what dimensions and
other related tables are required.
The Subject Area Assembly dialog is displayed. The tree view on the left side
shows the fact tables that belong to the subject area. You can expand the fact table
node to view its related tables.
12. Click Calculate Task List to assemble the tasks needed to load the tables displayed
In the tree view, remove one or more tables from the subject area by
deselecting the check box to the left of the table name.
b.
c.
d.
e.
Click OK in the message box stating the subject area was successfully
assembled.
15. (Optional) Click the Tasks subtab to view which tasks DAC has determined are
Add or remove additional fact tables. You can add or remove fact tables using the
Add/Remove command in the Tables subtab of the Subject Areas tab.
Add or remove tasks. You can add or remove individual tasks using the
Add/Remove command in the Tasks subtab of the Subject Areas tab. You can also
remove tasks by assigning a task to a configuration tag. See "Working with
Configuration Tags" for more information.
After you modify an existing subject area, you need to reassemble it (by selecting it
and clicking Assemble in the Subject Areas tab). This action opens the Subject Area
Assembly dialog, where you can calculate the new task list and view the tasks that
were added and removed in the Task Difference Report tab.
A new task is added to the data warehouse that extracts data from or loads data
into any of the tables associated with the subject area.
A task associated with the subject area is deleted, activated or inactivated.
A configuration tag is added to the subject area or to a table or task associated
with the subject area.
Note: You do not need to reassemble a subject area if an attribute of a task changes but
the task is already associated with a subject area.
9-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
10
Managing Data Warehouse Schemas
10
DAC enables you to manage data warehouse schemas by creating, upgrading, and
dropping data warehouse tables.
This chapter contains the following topics:
Creating, upgrading or dropping an entire schema. This option uses the Data
Warehouse Configuration Wizard to do a mass update of the schema by creating,
upgrading, or dropping all tables at once. This option also enables you to create
delete triggers on a transactional database for Siebel sources. See "Creating,
Upgrading or Dropping an Entire Schema for Oracle Databases" for instructions.
Creating, upgrading or dropping subsets of tables. This option uses the Generate
DW Table Scripts right-click menu command to create, upgrade, or drop subsets of
tables in the schema by generating SQL scripts in the Oracle database format. See
"Creating, Upgrading or Dropping Subsets of Tables in the Schema for Oracle
Databases" for instructions.
In addition, customizing the schema creation and upgrade process is possible for
advanced DAC users. See "Advanced Usage of the Schema Creation and Upgrade
Process for Oracle Databases" for more information about customization options.
Note: Before you perform the procedures in this section, make sure you have done the
following:
From the DAC menu bar, select Tools, ETL Management, Configure.
2.
In the Sources dialog box, select Oracle as the target and source database platform.
3.
4.
Select the appropriate option to generate a SQL script to create, upgrade, or drop
data warehouse tables. For Siebel sources you can also select the option to create
delete triggers in the transactional data warehouse.
Note: If you select the option to upgrade the data warehouse schema, the SQL
scripts that DAC generates depend on what data warehouse objects need to be
upgraded. See "About the Upgrade Schema SQL Scripts" for more information.
5.
Click Next.
The Data Warehouse tab is active.
6.
Field
Description
Container
The name of the source system containers for which you want to create,
upgrade or drop the data warehouse tables. Separate multiple names with
commas.
If you leave this field blank, DAC performs the action specified for all source
system containers.
If there are tables that are common to multiple containers, then only one
table will be created. If columns are different for the same table across
containers, DAC will create a table that has all the columns in the same table.
When you specify a container name, you must enter the name exactly as it
appears in the container drop-down list.
Is Unicode
Execute
Select this option of you want DAC to execute the SQL script automatically
after it is generated.
If you do not select this option, you can manually execute the script at a later
time. DAC stores the SQL scripts in <Domain_
Home>\dac\conf\sqlgen\sql\oracle.
Note: If you are upgrading the data warehouse schema, depending on what
objects need to be updated, DAC may generate a SQL script named
upgrade-questionable.sql. DAC will not automatically execute this script.
You must execute it manually after you have reviewed and corrected it as
necessary. For more information about the upgrade scripts, see "About the
Upgrade Schema SQL Scripts".
10-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Field
Description
Physical Data
Source
7.
Click Start.
The Run Status tab displays information about the process, as follows:
If a 'Failure' message is displayed, the data warehouse tables have not been
created. Use the log information in <Domain_
Home>\dac\log\config\generate_ctl.log to diagnose the error. The
createtables.log is not generated.
Creating, Upgrading or Dropping Subsets of Tables in the Schema for Oracle Databases
To create, upgrade or drop subsets of tables, you use the Generate DW Table Scripts
right-click menu command to generate SQL scripts in the Oracle database format.
You can access the right-click menu command from the tabs described in Table 101,
depending on the context for the schema update:
Table 101
Tab
Purpose
Use when you are working with a subject area and need to
update a subset of tables.
Use when you have applied a patch to the DAC repository and
need to update the data warehouse schema.
Go to the appropriate tab (as described in Table 101) and query for the tables with
which you want to update the schema.
2.
Right-click in the list of tables, and then select Generate DW Table Scripts for
Oracle.
3.
In the "Perform Operations for" area, select one of the following, and then click
OK.
4.
In the Generate DW Table Scripts for Oracle dialog, specify the following options:
Field
Description
Create New
Select this option to generate a SQL script to create new data warehouse
tables.
Upgrade
Existing
Drop Tables
Select this option to generate a SQL script to drop tables from the data
warehouse schema.
Unicode
Execute
If you do not select this option, you can manually execute the script at a later
time.
DAC stores the SQL scripts in <Domain_
Home>\dac\conf\sqlgen\sql\oracle.
Physical Data
Source
5.
Click Start.
The Run Status tab displays information about the process, as follows:
If a 'Failure' message is displayed, the data warehouse tables have not been
created. Use the log information in <Domain_
Home>\dac\log\config\generate_ctl.log to diagnose the error. The
createtables.log is not generated.
Advanced Usage of the Schema Creation and Upgrade Process for Oracle Databases
If you are an advanced DAC user, you can customize the schema creation and upgrade
process. This section provides information you need to know before customizing the
SQL scripts.
This section contains the following topics:
10-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Error Handling
Creating or Upgrading the Schema When You Have Multiple Source System
Containers
Customizing the Schema XML Templates
Because of the nature of these changes, the SQL scripts may fail when executed.
Therefore, a DBA must review the upgrade-questionable.sql file before it is executed,
and make any necessary corrections to the SQL statements. DAC saves this file in the
directory <Domain_Home>\dac\conf\sqlgen\sql\oracle directory. You cannot
choose to have this script executed upon generation. You must execute it manually
after it has been reviewed and corrected as necessary.
CHAR. The CHAR data type specifies a fixed-length character string. The
maximum length is enforced by the destination database. When you create a
CHAR column, you must specify the maximum number of bytes or characters of
data the column can hold in the Length field (in the Columns subtab of the Tables
tab in DAC). If you try to insert a value that is shorter than the specified length,
trailing spaces are added to the column value at run time.
VARCHAR. The VARCHAR data type specifies a variable-length character string.
The maximum length is enforced by the destination database. When you create a
VARCHAR column, you must specify the maximum number of bytes or characters
of data it can hold in the Length field (in the Columns subtab of the Tables tab in
DAC).
DATE. The DATE data type specifies a valid date. The valid date is enforced by
the destination database.
NUMBER. The NUMBER data type stores positive and negative fixed and
floating-point numbers. The maximum length for this value is enforced by the
destination database. When you create a number column, you must specify a
Length and Precision in the Columns subtab of the Tables tab in DAC. The Length
value is the maximum number of bytes or characters of data the column can hold.
The Precision value is the total number of significant decimal digits, where the
most significant digit is the left-most nonzero digit, and the least significant digit is
the right-most known digit.
TIMESTAMP. The TIMESTAMP data type stores the date and timestamp. The
maximum length for this value is enforced by the destination database.
NULL, NOT NULL and Default Values A column can have a NULL value if, in DAC, the
Nullable check box is selected in the Columns subtab of the Tables tab. If the Nullable
check box is not selected, the column is declared NOT NULL. NOT NULL columns
must contain a value. If a NOT NULL column does not have an explicit value, it will
get the default value if one is specified in the Default Value field in the Columns
subtab. If a NOT NULL column does not have an explicit value and a default value is
not specified, then it will get the value specified in the defaults.properties file only
when this column is an existing column that is being upgraded.
For the upgrade process, the defaults.properties file enables you to specify missing
default values for data warehouse tables with NOT NULL columns for which default
values are not specified in DAC. This file also specifies the equivalents of CURRENT
TIMESTAMP based on database type. This file is located in the <DAC_Config_
Location>\CustomSQLs\Schema_Templates directory.
In the defaults.properties file, the default values specified are grouped by database
type. The entries for the Oracle database type look similar to the following:
ORACLE_VARCHAR=' '
ORACLE_CHAR=' '
ORACLE_NUMBER=0
ORACLE_DATE=SYSDATE
ORACLE_TIMESTAMP=SYSDATE
ORACLE_%NOW%=SYSDATE
10-6 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
For the default values you enter in DAC, you need to enclose in single quotes the
values for CHAR, VARCHAR, DATE, and TIMESTAMP data types.
Column Ordering In DAC, the column order is specified in the Position field of the
Columns subtab in the Tables tab. Each column must have a unique position, and the
column position specified in DAC must match the column position specified in the
Informatica repository.
Unicode Considerations When generating SQL scripts to create or upgrade the schema,
you can indicate in DAC whether the schema should be created as Unicode. When you
create a schema as Unicode, you can still define specific table columns as non-Unicode
in DAC by going to the Columns subtab in the Tables tab.
Index Creation Indexes are not created during the schema creation process. Indexes are
created at runtime during the first full load.
Error Handling
Errors should be handled using an iterative process. Figure 101 illustrates the general
process for handling errors during the schema creation and upgrade processes. The
first step is to generate the SQL scripts for creating or upgrading the data warehouse
schema. Next, you can review the SQL scripts before executing and also review the
SQL generation log file, which is located in the directory <Domain_
Home>\dac\log\config. You then execute the scripts, and check the SQL execution
log file for errors. This file is located in the directory <Domain_
Home>\dac\log\config.
If errors occurred during the script execution, you need to interpret the error messages
and determine the best way to alter the metadata in DAC. Once you have made the
necessary changes to the metadata, you can then re-execute the scripts, check the log
files, and make any additional changes to the metadata. You need to repeat this
process until no errors appear in the execution log file.
Figure 101 Error Handling Iterative Process
Creating or Upgrading the Schema When You Have Multiple Source System
Containers
If your environment uses multiple source system containers, when you upgrade the
schema, the upgrade-questionable.sql file will log discrepancies among the containers,
such as discrepancies with data types. The process of finding errors will be iterative.
You can execute the scripts, review them to find errors, and fix the errors before
executing the scripts.
For the upgrade scripts to execute successfully, the containers must be synchronized. If
you have made changes in one container, you need to replicate the changes in the
other containers. You can do so by referencing the new or changed object or by
recreating the new or changed object across all containers. For information about how
to reference repository objects, see "About Object Ownership in DAC".
About XML Template Files Used for Creating the Data Warehouse Schema
About XML Template Files Used for Creating the Data Warehouse Schema There are two XML
templates that control the schema creation process: createschema_template_
designation.xml and createschema_<database type>.xml.
When you create the data warehouse schema, you can use the default settings in these
XML templates or you can customize them to suit your needs. If you use the default
settings, you do not need to change any information in the files before following the
procedure "Creating, Upgrading or Dropping Subsets of Tables in the Schema for
Oracle Databases".
The XML templates are located in the directory <DAC_Config_
Location>\CustomSQLs\Schema_Templates directory.
About createschema_template_designation.xml The createschema_template_
designation.xml file designates which schema creation template or templates will be
used to create the data warehouse schema. By default, the preconfigured
createschema_<database type>.xml file is designated as the template for creating all
data warehouse tables. If necessary, you can modify the createschema_<database
type>.xml file or you can create your own schema creation templates in XML format.
The createschema_template_designation.xml file enables you to specify schema
creation templates to do the following:
Specify a single schema creation template for creating all the data warehouse
tables or all tables other than those created by the override templates.
Specify an override schema creation template for specific tables by table name.
Specify an override schema creation template for specific tables by table type.
Oracle database type. The XML elements available for customizing are TABLE_NAMES,
TABLE_TYPES, and ALL_OTHER_TABLES. Templates specified in the TABLE_NAMES
and TABLE_TYPES tags will override the template specified in the ALL_OTHER_
TABLES tag.
<CREATE_SCHEMA_TEMPLATE_DESIGNATION>
<ORACLE>
<TEMPLATE NAME = "">
<TABLE_NAMES></TABLE_NAMES>
</TEMPLATE>
<TEMPLATE NAME = "">
<TABLE_TYPES></TABLE_TYPES>
</TEMPLATE>
<TEMPLATE NAME = "createschema_oracle.xml">
<ALL_OTHER_TABLES/>
</TEMPLATE>
</ORACLE>
2.
3.
4.
b.
Enter the template name as the value for TEMPLATE NAME attribute. The
value must be enclosed within quotes.
c.
Enter the table name as text content for the TABLE_NAMES element.
5.
b.
Enter the template name as the value for the in the TEMPLATE NAME attribute.
The value must be enclosed within quotes.
c.
Enter the table type as text content for the TABLE_TYPES element.
To designate a template for all tables or for all tables other than those created by
templates specified in the steps above:
a.
b.
6.
Enter the template name as the value for the in the TEMPLATE NAME attribute.
The value must be enclosed within quotes.
Customization Example
As an example, if you wanted to designate custom templates for the following:
10-10 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
<ORACLE>
<TEMPLATE NAME = "createschema_employee_table.xml">
<TABLE_NAMES>W_EMPLOYEE_D</TABLE_NAMES>
</TEMPLATE>
<TEMPLATE NAME = "createschema_fact.xml">
<TABLE_TYPES>FACT</TABLE_TYPES>
</TEMPLATE>
<TEMPLATE NAME = "createschema_oracle.xml">
<ALL_OTHER_TABLES/>
</TEMPLATE>
</ORACLE>
2.
3.
4.
b.
Enter the tablespace name as the value for the TABLESPACE NAME attribute.
The value must be enclosed within quotes.
c.
Enter the table name as text content for the TABLE_NAMES element.
5.
b.
Enter the tablespace name as the value for the in the TABLESPACE NAME
attribute. The value must be enclosed within quotes.
c.
Enter the table type as text content for the TABLE_TYPES element.
To designate a tablespace for all tables or for all tables other than those created by
templates specified in the steps above:
a.
b.
Enter the tablespace name as the value for the in the TABLESPACE NAME
attribute. The value must be enclosed within quotes.
10-11
6.
(Optional) Add additional SQL statements as the text content of the element
<SUPPLEMENT> towards the end of the file.
7.
About the Upgrade XML Template The upgradeschema_oracle.xml file contains the
database-dependent SQL syntax used to upgrade the data warehouse schema with
changes that were made to tables in DAC. This file is located in the <DAC_Config_
Location>\CustomSQLs\Schema_Templates directory. You should not change any of
the SQL syntax in this file.
From the DAC menu bar, select Tools, ETL Management, Configure.
2.
In the Sources dialog box, select the database platform for the target data
warehouse and source transactional database.
3.
4.
Select the appropriate option to create, upgrade, or drop data warehouse tables.
For Siebel sources you can also select the option to create delete triggers in the
transactional data warehouse. Then, click Next.
The Data Warehouse tab is active.
5.
Enter the appropriate information for the database in which you want to store the
data warehouse tables. The information that you need to enter is dependent on the
type of target database.
10-12 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Field
Description
Container
The name of the source system containers for which you want to create,
upgrade or drop the data warehouse tables. Separate multiple names with
commas.
If you leave this field blank, DAC performs the action specified for all source
system containers.
If there are tables that are common to multiple containers, then only one
table will be created. If columns are different for the same table across
containers, DAC will create a table that has all the columns in the same table.
If you only want to deploy a subset of the source business applications for
which you imported seed data earlier, then use this field to specify a
container name. When you specify a container name, you must enter the
name exactly as it appears in the container drop-down list.
Table Owner
Valid database owner, username, or account that you set up to hold the data
warehouse.
Password
Valid database user password for the database owner, username, or account
that you specified in the Table Owner field.
ODBC Data
Source
Data Source Name (DSN) for the Oracle Business Analytics Warehouse.
Tablespace
Is Unicode
6.
You must specify the name of the ODBC connection that you created for the
data warehouse.
Click Start.
The Run Status tab displays information about the process, as follows:
If a 'Failure' message is displayed, the data warehouse tables have not been
created. Use the log information in <Domain_
Home>\dac\log\config\generate_ctl.log to diagnose the error. The
createtables.log is not generated.
For Teradata databases, DAC generates a SQL script for the specified action.
The script is saved in the <Domain_Home>\dac\conf\sqlgen\sql\teradata
directory. You need to manually execute the script in the data warehouse to
complete the specified process.
10-13
10-14 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
11
Performance Tuning With DAC
11
DAC provides functionality related to indexes, tables, tasks, and workflows that
enables you to enhance performance.
This chapter contains the following topics:
Managing Indexes
Looping of Workflows
Managing Indexes
In general, during the ETL process, before a table is truncated, all the indexes, as
defined in the repository, will be dropped before the data is loaded and recreated
automatically after the data is loaded. The dropping of indexes before the data load
and recreating them after the data load improves ETL performance.
If you create an index on the database and it is not registered in the DAC repository,
the index will not be dropped and the load will fail.
For Teradata databases, only secondary indexes should be registered in DAC. You
should not register primary indexes or the more complex indexes, such as single- and
multi-table indexes, because they cannot be dropped and recreated.
In the DAC Design view, the Indices tab lists all the indexes associated with the
selected source system container. It is recommended that you do not register in DAC
any indexes for source tables.
This section contains the following topics:
Index Behavior
Index Behavior
The general sequence of actions related to indexes when a task runs is as follows:
1.
2.
Managing Indexes
3.
4.
5.
6.
7.
Note: Successor tasks can start before query-related and unique indexes are created.
Note:
In the Physical Data Sources tab of the Setup view, click the Index Spaces subtab.
2.
3.
When asked if you want to generate database properties based on table type, click
Yes.
A list of available table types is displayed in the Table Type list.
4.
5.
In the Index Space column, enter an index space for each table type, and click
Save.
In the Physical Data Sources tab of the Setup view, select the appropriate physical
data source in the top pane list.
2.
3.
4.
In the Name field, query for and enter the names of the table for which you want
to specify how many indexes can be created in parallel.
5.
For each table, in the Number of Parallel Indexes field, enter the number of
indexes you want to create in parallel.
6.
Click Save.
To specify how many indexes can be created in parallel for all tables associated with
a physical data source
11-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
1.
In the Physical Data Sources tab of the Setup view, select the appropriate physical
data source in the top pane list.
2.
3.
In the Num Parallel Indexes Per Table field, enter a numeric value to specify how
many indexes can be created in parallel for a table on the specified physical data
source.
4.
Click Save.
2.
b.
For instructions on defining an index action, see "Defining a SQL Script for an
Action".
3.
In the Indices tab, query for the table name and indexes that need to be
dropped and created during the incremental runs.
4.
b.
For each record in the list of query results, right-click and select Add Actions.
c.
Select Drop Index as the Action Type, Incremental as the Load Type, and
Drop Partitioned Index as the Action.
b.
5.
6.
In the Indices tab, query for the table name and indexes that need to be
dropped and created during the incremental runs.
b.
For each record in the list of query results, right-click and select Add Actions.
c.
Select Drop Index as the Action Type, Incremental as the Load Type, and
Enable Partitioned Index as the Action.
b.
c.
7.
In the Tables tab, query for the table names that need to be analyzed during
the incremental runs.
b.
For each record in the list of query results, right-click and select Add Actions.
c.
Select Analyze Table as the Action Type, Incremental as the Load Type, and
Analyze Current Partition as the Action.
For a more detailed example of using partitions, see "Oracle Business Intelligence
Applications Version 7.9.6.x Performance Recommendations [ID 870314.1]" on My
Oracle Support.
11-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Note:
2.
3.
Providing the means for computing the source and target counts to be used in the
computation of heuristics.
Example Using the Count Option: Assume you configure DAC heuristics to count
the incremental records in the primary source table. You have determined
performance is only impacted during an incremental load with indexes in place if
there are more than ten records to be loaded, so you set the threshold value at 10.
If DAC heuristics finds between zero and nine incremental records in the primary
source table, DAC will not drop and recreate indexes when the data is loaded into
the target tables. The data will be loaded with indexes in place. If DAC heuristics
finds ten or more incremental records in the primary staging table, DAC will drop
and recreate indexes during the load process.
Example Using the Ratio Option: Assume you configure DAC heuristics to
provide a ratio of the number of incremental records in the primary source table
and the total number of records in the target table. You have determined that if
incoming records are 5% or more of the total target table record count, then
performance can be impacted with indexes in place. Therefore, you set the
threshold value at 5. If DAC heuristics finds the ratio of incremental records in the
primary source table to be 5% or more of the total records in the target table, then
DAC will drop and recreate indexes during the load process. If the percentage of
incremental records is equal or less than 5%, DAC will load the new records with
the indexes in place.
11-6 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
You use the Heuristics dialog to define heuristics rules. The Heuristics dialog contains
the following fields:
Heuristic
The possible values are Count and Ratio. These options provide flexibility in how
you gather intelligence. The Count option provides a count of the number of
incremental records in the primary staging table that will be included in the ETL
process. The Ratio option provides the number of incremental records in the
primary source table and the total number of records in the target table. This value
is expressed in the threshold field as a percentage.
The Count option can be useful if you are deciding whether or not to run a task.
For example, if you only want a task to run if there is one or more records in a
staging table, you would select the Count option and set the Threshold value at 1.
DAC heuristics counts the number of records in the staging table. If it finds one or
more records, the task will run. If it finds no records, the task will not run.
The Ratio option can be useful if you are deciding whether to drop and create
indexes or analyze tables. For examples of using the count and ratio options, see
"Using Heuristics to Determine Whether Indexes Are Dropped and Created".
Metric
Provides options for how multiple primary source tables are handled (that is,
when more than one primary source table is associated with the same task). If you
are defining a heuristics rule that involves a single primary source table, the Metric
field does not apply.
The possible values are the following:
Sum
Aggregates the total of new or changed records in all of the primary source
tables.
Average
Returns an average of the new or changed records in all of the primary source
tables. That is, it will divide the sum of all the new or changed records in all of
the primary tables by the number of primary tables.
Max
Returns the largest count of new or changed records of all of the primary
source tables.
Min
Returns the smallest count of new or changed records of all of the primary
source tables.
Source Table
The possible values are the following:
Primary
Specifies that intelligence will be gathered on one or more primary tables
associated with the task that this heuristics rule is assigned to.
Threshold
The numerical value above which DAC heuristics will allow a particular action to
take place.
For example, if you are doing a count of a primary staging table to determine
whether a task should run, and if you want the task to run if one or more records
appears in the table, you would set the Threshold value at 1.
If you use the Ratio option, the threshold value is a percentage. For example,
suppose you were defining a heuristics rule for determining whether tables should
be analyzed after an ETL process, and you knew you wanted to analyze tables if
the incoming rows were more than 5% of the total target rows. In this case, you
would set the threshold value at 5.
In the DAC Client, on the Tools menu, select Seed Data, Heuristics.
The Heuristics dialog is displayed.
2.
3.
In the Name field, enter a descriptive name for the heuristics rule.
4.
Count
Provides a count of the number of records in the primary source table that will
be included in the ETL process (based on the task to which you assign the
heuristics rule).
Ratio
Provides a count of the number of records in the primary source table and the
total number of records in the target table. If you select the Ratio option, the
value of the Threshold field is a percentage.
5.
If this heuristics rule applies to a task with multiple primary tables, select one of
the following:
6.
Sum. Aggregates the total of new or changed records in all of the primary
source tables.
Average. Returns an average of the new or changed records in all of the
primary source tables.
Max. Returns the largest count of new or changed records of all of the primary
source tables.
Min. Returns the smallest count of new or changed records of all of the
primary source tables.
11-8 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
7.
In the Threshold field, enter a numerical value above which DAC heuristics will
allow a particular action to take place.
For examples, see "About Heuristics Rules and the Heuristics Dialog".
8.
(Optional) If you want to create this heuristics rule but leave it inactive, select
Inactive.
9.
Click Save.
After you create the heuristics rule, you need to assign the rule to a task. For
instructions, see "Assigning a Heuristics Rule to a Task".
2.
In the Tasks tab, select the task to which you want to assign the heuristics rule.
3.
4.
5.
Click in the Name field to expose the drop-down list, and then select Heuristics.
6.
7.
8.
For a rule that determines whether a task should run, click in the Task
Heuristic field, and then select the appropriate heuristics rule.
For a rule that determines whether tables should be analyzed, click in the
Table Heuristic field, and then select the appropriate heuristics rule.
For a rule that determines whether indexes should be dropped and recreated,
click in the Index Heuristic field, and then select the appropriate heuristics
rule.
Click OK in the Select Value dialog, and then click OK in the Property Value
dialog.
The heuristics rule is now assigned to a task and will be processed when the task to
which it is assigned is called by an execution plan.
Heuristics rules are reflected in the Status Description field in the Task Details tab of
the Details dialog, which is accessible by going to the Tasks subtab in the Current Runs
or Run History tabs and clicking the Details button on subtab toolbar. The Status
Description will indicate whether a step was skipped because of a heuristics rule, and
the task status will be Not Executed.
Note:
In the Design view, select the appropriate source system container from the
drop-down list.
2.
3.
4.
5.
In the Name field, enter a descriptive name for the SQL, and then click Save.
6.
7.
Select a format for the tree view on the left side of the window.
Flat view displays the SQL entries in a list format in their order of execution.
Category view displays the entries by the categories Custom SQL and Stored
Procedure.
You can reorder the entries in the tree by dragging and dropping them.
8.
9.
Field
Description
Name
Type
11-10 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Field
Description
Continue on Fail
Retries
The SQL Statement tab to the left of the text box lists the supported SQL functions
and DAC source system parameters that you can use in constructing custom SQL
statements. Double-click a function or source system parameter to move it into the
text box.
The source systems parameters list contains the applicable source system
parameters defined in the DAC repository, with the prefix @DAC_. During
runtime, the DAC Server resolves the source system parameter and replaces its
name with the runtime value.
See Table 111 for a list of supported SQL functions.
Table 111
Function
Description
getAnalyzeTableStatement()
getDBType()
getImageSuffix()
getNamedSource()
getTableName()
getTableOwner()
getTableSpace()
getTruncateTableStatement()
toString()
11. (Optional) Enter a comment about the SQL in the Comment tab.
12. Click OK.
13. If the SQL statement contains source tables, assign the heuristics SQL to the source
tables.
a.
b.
Select the task whose source table is the one to which you want to assign the
heuristics SQL.
c.
11-11
Looping of Workflows
d.
e.
f.
Select or query for the SQL heuristics rule you created in the preceding steps,
then click OK.
b.
Select the task whose target table is the one to which you want to assign the
heuristics SQL.
c.
d.
e.
f.
Select or query for the SQL heuristics rule you created in the preceding steps,
then click OK.
The heuristics SQL is now assigned to a task and will be processed when the
task to which it is assigned is called by an execution plan.
Looping of Workflows
You can configure the full and incremental load commands for tasks to repeat (or
loop) multiple times during the execution of an ETL process. This feature can be useful
to enhance performance in the following ways:
The process for setting up workflows for looping involves two steps: First you define
the looping properties, and then you create parameters to access the looping
properties you defined.
This section includes the following topics:
b.
11-12 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Looping of Workflows
c.
In the Edit Workflow dialog, select the Enabled check box for the Configure
Concurrent Execution property.
d.
e.
f.
Click OK.
2.
In the DAC Design view, select the appropriate container from the drop-down list.
3.
In the Tasks tab, query for the task for which you want to configure looping.
4.
With the appropriate task selected in the top pane, click the Extended Properties
subtab.
5.
6.
7.
In the Loops field, enter a numeric value to specify how many times you want the
workflow to repeat.
The number of loops that you specify is applicable to all task execution types, that
is, Informatica, SQL File, Stored Procedure, and External Program.
8.
(Optional) Select the Parallel check box to have the run instances of the same task
execute in parallel. If you do not select the Parallel check box, the run instances of
the same task will be executed serially.
Note:
9.
Run instances will be executed in parallel only if resources are available. For
example, if your environment is set up to run 10 workflows in parallel, and a
tasks Number of Loops property is set to 20, only the first 10 instances will be
executed. These 10 instances will have a Current Runs status of Running. The
remaining 10 instances will have a status of Runnable. For a description of all
Current Runs statuses, see "Current Runs Tab".
When the instances are executed in serial, the first failure encountered stops
the rest of the executions.
When the instances are executed in parallel, any failure in the running batch
stops the rest of the executions.
11-13
Looping of Workflows
When the task executes, DAC assigns an instance number to each instance of the
workflow. You can view the instance number in the Task Details subtab of the Current
Runs tab.
The instance number is accessible as a predefined DAC variable named @DAC_TASK_
RUN_INSTANCE_NUMBER. You can use this DAC variable as a runtime value for
parameters that you create. The DAC variable @DAC_TASK_RUN_INSTANCE_
NUMBER is available for use with parameters at the source system and task level.
Conditional statement
For example, if the loop number is one, provide value x, or else provide the value
y.
For more information about how parameters are used in DAC, see "Defining and
Managing Parameters".
To create a parameter with a static value
1.
In the DAC Design view, select the appropriate container from the drop-down list.
2.
To set up a parameter at the task level, go to the Task tab, and click the
Parameters subtab.
To set up a parameter at the source system level, go to the Source System
Parameters tab.
3.
4.
5.
6.
7.
8.
Click in the Value field to open the Enter Parameter Value dialog.
9.
Select Static.
11-14 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Looping of Workflows
In the Design view, select the appropriate container from the drop-down list.
2.
To set up a parameter at the task level, go to the Task tab, and click the
Parameters subtab.
To set up a parameter at the source system level, go to the Source System
Parameters tab.
3.
4.
5.
6.
7.
8.
Click in the Value field to open the Enter Parameter Value dialog.
9.
Select Runtime.
Modify the schema for the staging table and introduce a numerical column called
LOOP_NUMBER.
2.
In DAC, create a task level parameter for the extract process called NUMBER_OF_
LOOPS, and set the value to 5.
3.
Modify the extract mapping for the Informatica task so that each of the records
loaded in the staging table gets a value of from 1 to 5.
4.
Create a task level parameter in DAC for the load process called NUMBER_OF_
LOOPS, and set it to the same value as the extract mapping.
5.
11-15
will be populated with a different number, from 1 to 5, for each invocation of the
task.
6.
In the extended properties for the task, create a new record for "Loops" and set the
value as @DAC_NUMBER_OF_LOOPS.
7.
Modify the Informatica mapping to include a where clause for the load logic:
"WHERE LOOP_NUMBER = $$CURRENT_LOOP
WHERE LOOP_NUMBER = $$current_LOOP
When DAC runs the load process, it will spawn off five processes in parallel, and
will send a specific value for the CURRENT_LOOP_NUMBER parameter to
Informatica. Because DAC is reading and writing in parallel, the data load time
can be reduced.
2.
Locate the Analyze Table syntax for the appropriate database type.
For example, the syntax for an Oracle database is as follows:
<SqlQuery name = "ORACLE_ANALYZE_TABLE" STORED_PROCEDURE = "TRUE"> DBMS_
STATS.GATHER_TABLE_STATS(ownname => '@TABLEOWNER', tabname => '%1', estimate_
percent => 30, method_opt => 'FOR ALL COLUMNS SIZE AUTO',cascade => true )
</SqlQuery>
3.
Note:
11-16 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
1.
2.
Locate the Create Index syntax for the appropriate database type, and edit the
syntax.
11-17
11-18 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
12
Working With DAC Metadata Patches
12
The DAC metadata patch feature enables you to import and export subsets of DAC
metadata at a fine grain.
This chapter contains the following topics:
Note:
Step 1: Create a new, empty patch. The DAC automatically assigns the patch
version value as 1 and the status as Open. Open patches are listed in the Working
Patches tab in the Setup view.
For instructions on creating a patch, see "Creating a Patch".
Step 2: Add contents to the patch. For information about what objects you can
add to a patch, see "About Patch Contents". A patch must have an Open status in
order for objects to be added or removed. The patch stores pointers to the
repository objects.
For instructions on adding contents to a patch, see "Adding Contents to a Patch".
Step 3: Close the patch. When you change the patch status to Closed, the patch
can no longer be edited. You can reopen a Closed patch in order to edit it. When
you change the status from Closed to Open, the patch version is automatically
incremented by 1. Closed patches are listed in the Working Patches tab.
For instructions on closing a patch, see "Changing the Status of a Patch".
Step 4: Export the patch. When you export the patch, the patch and its contents
are stored in an XML file in a directory you specify.
For instructions on exporting a patch, see "Exporting a DAC Metadata Patch".
Step 5: Apply the patch to the DAC repository. When you apply a patch, the
DAC repository is upgraded with the patch contents stored in the XML file. After
the patch process, the patch status will be one of the following:
For information about why objects are not applied to the DAC repository, see
"When Does a Patch Fail to be Applied to the DAC Repository?" Applied patches
are listed in the Applied Patches tab in the Setup view.
For instructions on applying a patch, see "Applying a DAC Metadata Patch to the
DAC Repository".
Step 6: Upgrade the data warehouse schema. If the patch contents included
column-level changes, you need to upgrade the data warehouse schema with the
same updates that were made to the DAC repository.
For instructions on upgrading the data warehouse schema, see Chapter 10,
"Managing Data Warehouse Schemas."
12-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Creating a Patch
For a description of the complete DAC metadata patching life cycle, see "DAC
Metadata Patching Life Cycle".
Creating a Patch
Follow this procedure to create a new patch.
To create a patch
1.
2.
3.
Enter a descriptive name for the patch, and then click Save.
DAC automatically sets the status as Open and the Patch Version as 1.
Adding contents by manual selection. Using this method, you manually select
container-dependent and seed data objects you want to add to the patch. For
instructions, see "Adding Contents to a Patch by Manual Selection".
Adding contents based on a timestamp range. Using this method, you configure
a period of time between two timestamps. All eligible objects that are new or
changed between these two timestamps, in all source systems, will be added to the
patch. For instructions, see "Adding Contents to a Patch Based on a Timestamp
Range".
Table 121
Subject area
Configuration tags
Tables
Tasks
Actions
Columns
Indexes
Multi-Column Statistics
Related tables
Actions
Columns
Tables
Indexes
12-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Tasks
Actions
Conditional tables
Configuration tags
Extended properties
Execution type
Phase dependencies
Parameters
Source tables
Target tables
Task groups
Child tasks
Configuration tags
Subject areas
Tasks
Logical folders
Physical folders
None
None
Seed data objects (objects defined or viewed by clicking Tools on the menu bar,
and then selecting Seed Data)
Execution types
Heuristics
Task phases
Patches
You can also add other patches to a patch. A patch added to another patch
becomes the child patch. The parent patch is referred to as a cumulative patch. A
cumulative patch can include both objects and other patches (including the patch
contents).
1.
Review the section "About Patch Contents" for information about which
repository objects you can add to a patch.
2.
Make sure the patch that you want to add contents to has the status Open. You can
only add contents to an Open patch. If the patch is Closed, you can reopen it. For
instructions, see "Changing the Status of a Patch".
3.
Select the appropriate source system container from the drop-down list.
b.
Go to the appropriate tab, and query for the objects you want to add to the
patch.
c.
In the list of query results, right-click, and select Add Object(s) to Patch.
d.
e.
In the Patches dialog, click in the Select a Patch field, and then select the
appropriate patch to which you want to add contents.
f.
4.
On the Tools menu, select Seed Data, and then select the appropriate menu
item.
b.
Right-click the object you want to add to the patch, and then select Add
Object(s) to Patch.
c.
d.
5.
In the Patches dialog, click in the Select a Patch field, and then select the
appropriate patch to which you want to add contents.
In the Working Patches tab of the DAC Setup view, select the patch that you
want to add to another patch.
b.
c.
In the Patches dialog, click in the Select a Patch field, and then select the patch
to which you want to add the child patch.
6.
A message dialog informs you which objects were added to the patch. Click OK.
7.
Click the Contents subtab to view container-dependent and seed data objects.
Both parent and child objects are listed in the Contents subtab.
12-6 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Click the Child Patches subtab to view child patches added to the patch. Only
the patch (and not the patch contents) is listed in the Child Patches subtab. For
nested patchesthat is, a child patch that has its own child patchonly the
immediate child patch is listed in the Child Patches subtab.
Review the section "About Patch Contents" for information about which
repository objects will be added to the patch.
2.
Make sure the patch that you want to add contents to has the status Open. You can
only add contents to an Open patch. If the patch is Closed, you can reopen it. For
instructions, see "Changing the Status of a Patch".
3.
4.
5.
Right-click the patch, select Patches, and then select Add Objects to Patch (Time
Range).
6.
In the Patching... dialog, click in the From Timestamp field to open the Date
dialog, and configure the beginning timestamp:
a.
b.
c.
Select the hour, minute, and second for the beginning timestamp.
d.
Click OK.
7.
Click in the To Timestamp field, and configure the ending timestamp by following
the substeps in Step 6.
8.
2.
3.
Note:
To export a patch
1.
2.
3.
Make sure the patch status is Closed. If the patch is Open, you need to close it by
following the instructions in "Changing the Status of a Patch".
4.
Right-click the patch, select Patches, and then select Export Patch.
5.
b.
In the File Name field, you can leave the default name of the file, which is in
the format <patchName><version>.xml, or you can enter a new name.
c.
Click Save.
On the Tools menu, select DAC Repository Management, then select Apply
Patch.
2.
3.
a.
Select the folder that contains the XML file you want to import.
b.
c.
Click Open.
A message dialog informs you whether the process was successful. Click OK to
close the dialog.
The applied patches are listed in the Applied Patches tab. The status of an applied
patch can be one of the following:
Completed. All objects in the patch were successfully applied to the DAC
repository
Incomplete. Some objects were successfully applied, but other objects failed to
be applied.
12-8 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
4.
Update the data warehouse schema to reflect the patch applied to the DAC
repository. For information about updating the schema, see "Creating, Upgrading
or Dropping Subsets of Tables in the Schema for Oracle Databases".
Note: You can only update the data warehouse schema with a subset of tables
(tables included in a patch) if you are using an Oracle database for the data
warehouse.
The container name in the XML file does not match the container name in the
DAC repository.
An object in the XML file has a container name that does not exist in the DAC
repository.
12-10 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
13
13
Make sure you have installed the supported version of the Java SDK.
2.
DAWSystem.jar
Common Tasks Performed in the DAC 13-1
3.
dac.properties
dacCmdLine.bat or dacCmdLine.sh
Edit the JAVA_HOME variable to point to the directory where the Java SDK is
installed.
Make sure there are no spaces in the path reference.
b.
4.
Edit the DAC_HOME variable to point to the directory where the DAC is
installed.
Parameter
Value
ServerHost=
ServerPort=
RepositoryStampVal=
Description
StartServer
StopServer
StartETL
Starts an execution plan. You must specify an execution plan name. -wait
option lets you start the execution plan in synchronous mode.
StopETL
ETLStatus
If you do not specify an execution plan name, the status of the execution
plan that last ran is returned. If you specify an execution plan name, the
status of the specified execution plan is returned.
DatabaseStatus
Verifies whether the DAC Server can connect to all active database
connections. You do not need to specify an execution plan name.
InformaticaStatus
Verifies whether the DAC Server is able to ping all active Informatica
PowerCenter Services machines.
13-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Note:
For example:
Command Line
Description
dacCmdLine EtlStatus
dacCmdLine EtlStatus
Forecast
dacCmdLine databasestatus
dacCmdLine InformaticaStatus Returns the health status of all the Informatica PowerCenter
Services connections as defined in the DAC Client on the
Informatica Services tab.
Summary of the requested execution plan. If there are multiple instances of the
same execution plan, a summary of the instance that last ran is returned. Below is
an example of the information contained in the summary.
(c) 2009 Oracle
Oracle DAC Server comprising the etl execution-management, scheduler, logger,
and network server.
ETL details for the last run:
ETL Process Id : 255 ETL Name : Complete ETL Run Name : DRY RUN OF Complete
ETL: ETL Run - 2004-06-17 18:30:13.201 DAC Server : (<host name>) DAC Port :
3141 Status: Stopped Log File Name: Complete_ETL.255.log Database Connection(s)
Used :
InformaticaServer4-<host name>:(4)
InformaticaServer3-<host name>:(3)
InformaticaServer2-<host name>:(2)
InformaticaServer1-<host name>:(10)
Start Time: 2004-06-17 19:00:06.885 Message: ETL was interrupted Actual Start
Time: 2004-06-17 18:30:13.357 End Time: 2004-06-17 19:05:56.781 Total Time
Taken: 35 Minutes
Start Time For This Run: 2004-06-17 19:00:06.885 Total Time Taken For This Run:
5 Minutes
Total steps: 212 Running steps: 0 Complete steps: 142 Failed/Stopped steps:70
Command Credentials
Database Credentials
Export Patch
JKS Password
Server Setup
Set Password
13-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
where:
Parameter
Description
file name
Syntax to change encryption key by explicitly specifying the key from command line
input:
<path to connection file> changeEncryptionKey
Note: An authentication file is not required for this operation. The repository
password will be taken from command line input.
Caution: This operation will clear all database, Informatica, and
external executor passwords as well as all DAC user data. Use this
command only when the authentication file with the encryption key
was lost and cannot be recovered. After removing the encrypted data
from the DAc repository, generate the authentication file with a new
encryption key, and log into the DAC repository using the DAC
Client. When prompted to add the encryption key, update all
passwords in the DAC repository and distribute the new
authentication file to all required DAC users.
Command Credentials
The cmdCredentials parameter stores credentials for the DAC command line utility for
both the Fusion Middleware and DAC standalone authentication modes.
Syntax:
cmdCredentials <path to cwallet.sso file> <user name>
Note: The password will be taken from command line input. Also, make sure to
include the cwallet.sso file name in the path.
where:
Parameter
Description
unicode
tablespace
13-6 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Note: The user password will be taken from command line input.
where:
Parameter
Description
unicode
where:
Parameter
Description
from timestamp
to timestamp
The ending timestamp for the timestamp range. The format is the same
as that of the "from timestamp."
-now
Database Credentials
The dbCredentials property generates an authentication file (cwallet.sso) with the
DAC repository credentials and encryption key.
Syntax for explicit key and credentials:
dbCredentials <path to cwallet.sso file> <user name> -withKey
Syntax to update credentials in existing file without modifying the encryption key:
dbCredentials <path to cwallet.sso file> <user name> -noKey
Note: The user password will be taken from command line input.
where:
Parameter
Description
where:
Parameter
Description
folder name
container name
(Optional) Name of the source system container for which you want to
export DAC metadata. If no container is named, all containers that are
found in the file structure will be exported.
where:
Parameter
Description
folder name
category
Export Patch
The exportPatch property exports a DAC metadata repository patch in XML format.
Syntax:
<path to connection file> exportPatch <file name> <patch name>
where:
Parameter
Description
file name
JKS Password
The jksPassword parameter stores the password for the Java key store.
Syntax:
jksPassword <path to cwallet.sso file>
Note: The password will be taken from command line input. Also, make sure to
include the cwallet.sso file name in the path.
Note: The definition file will be generated for the specified containers. If you do not
specify a container, the file will be generated for all containers.
where:
Parameter
Description
folder name
container name
(Optional) Name of the source system container for which you want to
import DAC metadata. If no container is named, all containers that are
found in the file structure will be imported.
-noTruncate
-noUpdate
where:
Parameter
Description
folder name
13-10 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Parameter
Description
category
-noTruncate
-noUpdate
where:
Parameter
Description
file name
Server Setup
The serverSetup property sets up the DAC Server connection to the DAC repository.
Syntax:
<path to connection file> serverSetup <database type> <database name/instance
name/tns> <host> <port>
Note: If Fusion Middleware authentication is specified in the connection file, the DAC
Server URL should be specified in the properties file and the DAC Server will be set to
where the URL points (location can be a remote server). If DAC standalone
authentication is specified in the connection file, you must configure the repository
connection properties in the properties file. The DAC Server will be set up in the local
installation. The user name, password, and encryption key will be taken from the
database credentials (cwallet.sso) file.
Set Password
The setPassword parameter sets the password for the Informatica Integration Service,
Informatica Repository Service, and physical data sources in the DAC repository.
Syntax:
<path to connection file> setPassword <type> <logical name>
where:
Parameter
Description
type
logical name
Note: The password will be taken from command line input. If the logical name or
password contains spaces, surround the entry in double quotes.
where:
Parameter
Description
execute
From the Start menu, select Programs, Accessories, System Tools, Scheduled
Tasks.
2.
3.
13-12 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
4.
5.
Enter the domain user account to start the DAC Server and a password, and click
Finish.
The startserver task is displayed in the Scheduled Task window.
6.
7.
In the Settings tab, deselect the Stop the task if it runs for 72 hours check box.
From the Programs menu, select Accessories, System Tools, Scheduled Tasks.
2.
From the Programs menu, select Accessories, System Tools, Scheduled Tasks.
2.
From the Programs menu, select Accessories, System Tools, Scheduled Tasks.
2.
3.
2.
Edit the config.bat file to set the DAC_HOME variable appropriately for each
instance.
For example if you copy the C:\<Domain_Home>\dac directory to C:\<Domain_
Home>\DAC_SERVER2\dac, make sure that the C:\<Domain_Home>\DAC_
SERVER2\dac config.bat file is configured correctly.
3.
Launch each of the DAC Clients by navigating to the DAC directories and
double-clicking the startclient.bat file.
4.
b.
Click Yes.
5.
c.
d.
Click Save.
b.
Field
Description
Mode
Select Standalone.
Standalone Mode
Configuration:
Host
Alternative Hosts
Port
6.
On the Tools menu, select ETL Management, and then select Reset Data
Warehouse.
The Reset Data Warehouse dialog is displayed and requests you to confirm you
want to reset the data warehouse.
2.
3.
Click Yes.
13-14 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
2.
In the Navigator window, expand the WebLogic Domain folder and the
bifoundation_domain node, and select the AdminServer node.
3.
Display the WebLogic Server menu and select System MBean Browser from the
menu to display the Fusion Middleware Control System MBean Browser.
4.
where host is the DNS name or IP address of the DAC Server and port is the
listen port on which the WebLogic Server is listening for requests. The default
port is 7001.
2.
Enter the system administrator user name and password and click Login.
This system wide administration user name and password was specified during
the installation process, and you can use it to log in to WebLogic Server
Administration Console and Fusion Middleware Control. Alternatively, enter a
user name that belongs to one of the following security groups:
Administrators
Operators
Deployers
Monitors
3.
Click on the Deployments link in the navigation tree on the left to display the list
of deployed applications.
4.
13-16 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
14
Integrating DAC With Other ETL Tools
14
The external executor framework enables you to integrate DAC with ETL engines
other than Informatica. The general process for integrating DAC and an ETL engine is
as follows:
Step 1: Create a Java library for the required interfaces and classes.
DACExecutorDescriptor
DACExecutor
DACExecutorJob
DACExecutorDescriptor
The DACExecutorDescriptor interface is a starting point for integrating an ETL engine
with DAC. It describes what the ETL engine does and the properties it requires. An
instance of DACExecutorDescriptor is used by the DAC code to generate the required
executors during an ETL process.
The properties for this interface need to implement
com.oracle.dac.thirdparty.executor.DACExecutorProperty. You can
customize the implementation by using
com.oracle.dac.thirdparty.executor.DACExecutorPropertyImpl.
In the sample SQL Executor code (located in Oracle_
Home\dac\documentation\External_Executors\SampleSQLExecutor),
DACExecutorDescriptor is implemented by
com.oracle.dac.thirdparty.executor.samplesqlexecutor.SampleSQLEx
ecutorDescriptor. This interface produces the corresponding executor
DACExecutor and requires the following properties:
JDBC URL
Database user
DACExecutor
The DACExecutor interface is an instance of an external executor. The DACExecutor
object is instantiated during the ETL process and is used to communicate with the ETL
engine. Multiple instances of DACExecutor can be created during an ETL process to
communicate with multiple ETL engines of a specific type. DACExecutor is initialized
with a set of properties (as defined in the DAC metadata) and is used to create
DACExecutorJobs, one for each DAC task. A map of DAC parameters relevant for the
task and DAC task definitions is provided. Task definition information includes the
following:
Task name
14-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
DACExecutorJob
DACExecutorJob runs actual tasks on the external ETL engine. Jobs are created by
executors during the ETL process. One job is responsible to run one task. Jobs are also
initialized in the executor using task parameters. DACExecutorJob should implement
a synchronous call to the ETL engine and report back the execution status.
In the sample SQL Executor code, DACExecutorJob is implemented by
com.oracle.dac.thirdparty.executor.samplesqlexecutor.SampleSQLExecutorJob. For
each task of the execution type that corresponds to SampleSQLExecutorDescriptor, one
job is run and makes an entry with the task command (for full or incremental mode,
depending what load type is appropriate) and the current timestamp in the table
SAMPLE_SQL_TBL.
DACExecutorConnectionHelper
DACExecutorLoggingUtils
DACExecutorConnectionHelper
You can use the DACExecutorConnectionHelper utility to create and manage database
connection pools and to execute SQL statements with or without bind parameters.
When using this utility, make sure to call the cleanUp() method at the end of the ETL
process (when the method is called on the executor that owns an instance of
DACExcecutorConnectionHelper).
DACExecutorLoggingUtils
You can use the DACExecutorLoggingUtils class to have messages and exceptions
added to DAC Server and ETL log files. The ETL logs are saved in the <Domain_
Home>\dac\log\<subdirectory specific to ETL run> directory.
2.
3.
b.
Append the library file name and directory path to the end of the DACLIB
entry in the config.bat or config.sh file:
In the config.sh file, the DACLIB entry should look similar to:
export DACLIB=${BI_ORACLE_HOME}/dac/DAWSystem.jar:${BI_ORACLE_
HOME}/biacm/applications/biacm.paramproducer.jar:${BI_ORACLE_
HOME}/dac/lib/dac-external-parameters.jar:{BI_ORACLE_HOME}/dac/lib/<fila
name>
4.
On the DAC Server machine, add the library to the WebLogic domain libraries
folder.
5.
Define an execution type for the tasks that will be executed by the external
executor.
a.
On the Tools menu, select Seed Data, and then select Execution Types.
The Execution Types dialog is displayed.
b.
c.
d.
6.
e.
Click Save.
f.
b.
c.
d.
From the Type drop-down list, select the execution type you defined in the
previous step.
e.
Click Save.
f.
Click Generate.
g.
Go to the Properties subtab, and click Refresh in the bottom pane toolbar.
The list of properties defined in DACExecutorDescriptor is displayed in the
Properties subtab.
7.
h.
i.
Click Save.
Create the DAC tasks that will need to run on the external executor.
a.
14-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
b.
c.
Enter the appropriate task definitions. For a description of each field, see
"Tasks Tab". For the Execution Type, make sure you select the execution type
you defined in step 6.
d.
Click Save.
14-6 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
15
Upgrading, Comparing and Merging DAC
Repositories
15
The DAC Upgrade/Merge Wizard enables you to upgrade and merge the content of
DAC repositories.
This chapter contains the following topics:
Stage
Possible Actions
Open the Upgrade/Merge Wizard by selecting from the DAC toolbar Tools, then
DAC Repository Management, and then Upgrade/Merge Wizard.
The Upgrade/Merge Wizard dialog displays the type of upgrade or merge process
you previously started.
2.
From the Perform drop-down list, select Reset and click OK.
3.
In the Reset Upgrade Process dialog, re-type the text in the text box to confirm you
want to proceed, and click Yes.
A message dialog tells you the reset process was successful.
4.
Click OK.
15-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Use this option to upgrade a DAC repository in the release 7.8.4 format, which has
a non-partitioned DAC repository structure, to the new release, which has a
partitioned DAC repository structure. For more information, see "About the
Repository Upgrade (DAC 784) Option".
Refresh Base
Use this option to upgrade the DAC repository when you are upgrading from an
older release of Oracle BI Applications to a new release. For more information, see
"About the Refresh Base Option".
Replace Base
Use this option to upgrade the DAC repository when you are phasing out an
older release of a transactional application and moving to a newer release, for
example, phasing out Siebel 7.5.3 and moving to Siebel 7.8. For more information,
see "About the Replace Base Option".
DAC versions before Oracle BI Applications 7.9 had a non-partitioned DAC repository
structure and held metadata for a single application. DAC versions released with
Oracle BI Applications 7.9 and higher and with the DAC 10.1.3.4 release and higher
have partitioned DAC repository structures. The partitioned structure, also known as a
container, can hold metadata for multiple applications.
The Repository Upgrade (DAC 784) option enables you to upgrade from the DAC
repository release 7.8.4 (non-partitioned) to the new partitioned structure.
If you want to upgrade a pre-7.8.4 release of a DAC repository,
you must first upgrade the repository to the 7.8.4 release before you
can use the Repository Upgrade (DAC 784) option to upgrade to the
new release.
Note:
Figure 152 Upgrade Process for Repository Upgrade (DAC 784) Option
In Step 1 of the high-level process flow, you import the existing 7.8.4 DAC repository
into the repository temporary tables. The existing 7.8.4 repository is referred to as the
source in the Upgrade/Merge Wizard.
In Step 2, you create a Difference Report that compares the existing repository with the
new base container, which is referred to as the target. (The new base container is the
version to which you are upgrading and is the version you imported from the file
system.)
In Step 3, you accept or reject the objects that the Difference Report shows as being
either present or changed in the source but not the target. See Section , "Resolving
Object Differences in the View Difference Report" for a description of how objects are
merged based on the action you take.
In Step 4, after you have resolved the differences, you then execute the merge. In Step
5, the Upgrade/Merge Wizard references the customizations in the newly merged
custom container with the new base container.
Note:
Before you begin this procedure, you need to have already installed the new release of
Oracle BI Applications and imported the metadata that is the same version as the
metadata in the existing 7.8.4 DAC repository. For example, if the existing 7.8.4
repository contains Siebel 6.3 metadata, you need to have imported the Siebel 6.3
source system container metadata from the new Oracle BI Applications release. If you
15-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
are using Oracle BI Applications 7.9.x with the DAC 7.9.x, then you should have the
correct Siebel source system container in the 7.9.x DAC repository.
You should also review the section "Resolving Object Differences in the View
Difference Report" to gain an understanding of the options for resolving object
differences.
To upgrade a DAC repository in the release 7.8.4 format to the new release
1.
2.
b.
c.
Edit the entries for folder, database connection, and subject area to reflect the
upgrade environment. See the comments in the datamapping.xml file for
instructions.
Configure the connection between the release 7.8.4 DAC repository and the new
DAC Client.
a.
b.
Click New to create a new record for the 7.8.4 DAC repository.
c.
The value for the Type field must be set to DAC repository.
d.
e.
Click Save.
3.
4.
From the drop-down list, select Repository Upgrade (DAC 784), and then click
OK.
The Import 7.8.4 Repository dialog is displayed.
5.
From the 784 Repository drop-down list, select the repository you configured in
Step 1.
In order for a repository to appear in the drop-down list, it
must be configured in the Physical Data Sources tab of the Setup view.
Note:
6.
From the Source System Container drop-down list, select the new base container
to which you are upgrading. This is the container you will compare against the
existing release 7.8.4 DAC repository.
Caution: Make sure you select the appropriate container. If you
select a container different from that contained in the existing release
7.8.4 DAC repository, the Difference Report will compare dissimilar
source system containers and will be inaccurate.
7.
Select the categories of metadata from the existing release 7.8.4 DAC repository
you want to import into the repository temporary tables for comparison with the
new base container. The categories are as follows:
Categories Options
Description
Logical
Imports all information contained in the DAC Design view and the
execution plan information for the DAC Execute view.
Run Time
Imports ETL Run History and the last refresh date information.
System
The release 7.8.4 DAC repository tables are imported into the temporary tables.
8.
9.
Create the Difference Report to compare the differences between the source and
target DAC repositories.
a.
Enter a name for the Difference Report, or leave the default name.
b.
From the Source System Container drop-down list, select the new base
container.
c.
In the New Custom Container ID/Name fields, enter an ID and a name for the
custom container that will be created during the upgrade process.
The ID and Name fields are alphanumeric. The Name field can contain spaces
and must be at least five characters long. The ID field cannot contain spaces.
d.
e.
Click OK.
When the Difference Report is complete, the Creating Difference Report dialog
tells you how long the process took.
f.
Click OK.
The View Difference Report dialog displays the differences between the
existing and new DAC repositories.
10. In the View Difference Report dialog, resolve the differences between the existing
(source) and new (target) containers, that is, between the release 7.8.4 DAC
repository and the repository that contains the new base container. To resolve the
differences, you need to deselect the Accept Source check box for each object that
appears in the difference report.
For detailed information about the View Difference Report, see "Resolving Object
Differences in the View Difference Report".
a.
In the navigation tree, select the repository object for which you want to view
the differences between the existing and new repositories.
If the object selected in the navigation tree is a hierarchical object, the subtabs
for the child objects appear in the bottom pane of the Object Difference
window.
b.
(Optional) Filter the objects that appear in the Object Difference window by
selecting one of the options from the drop-down list in the toolbar.
15-6 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
c.
For parent objects in the top pane and any child objects in the bottom pane,
deselect the Accept Source check box.
For detailed information about these options and the merge outcome, see
"Possible Repository Merge Outcomes Based on Your Decisions"
If a child object has been changed but not the parent object, the
parent object will still appear in the Object Difference window even
though it has not been changed.
Note:
d.
(Optional) After you have deselected the Accept Source check box for each
repository object, select Resolved check box to indicate you have resolved the
object.
e.
Click Merge.
The Merge dialog is displayed and lists the details of the merge.
The Refresh Base option enables you to upgrade an existing customized DAC
repository. You should use this option if you are upgrading from a DAC release higher
than 7.8.4. If you are upgrading a DAC repository in the release 7.8.4 format or
lower-numbered releases, see "About the Repository Upgrade (DAC 784) Option".
The Refresh Base option enables you to compare a new base container with the
existing customized repository and to create a Difference Report. If you want to
upgrade an existing customized DAC repository without comparing repositories and
creating a Difference Report, you can use the Simplified Refresh From Base option. See
"About the Simplified Refresh From Base Option" for more information.
In Step 1 of the high-level process flow, you import the repository data for the new
base container from the file system into the repository temporary tables. This
repository is referred to as the source in the Upgrade/Merge Wizard.
In Step 2, you create a Difference Report that compares the new base container with
the existing repository (including customizations). The existing customized repository
is referred to as the target.
In Step 3, you accept or reject the objects that the Difference Report shows as being
present or changed in the source but not the target. See "Possible Repository Merge
Outcomes Based on Your Decisions" for a description of how objects are merged based
on the action you take.
In Step 4, after you have resolved the differences, you then execute the merge. In Step
5, the DAC references the customizations in the newly merged repository with the new
base container.
The repository data is imported from a file system and should
be in the format of DAC 10.1.3.4 or higher. If it is in the 7.9.x format,
you should do the following:
Note:
1.
Restore the repository data into a database using the 7.9.x DAC (using the
regular DAC import process).
2.
3.
The metadata in the folder in Step 3 above will become the source
for this upgrade.
15-8 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Before you begin this procedure you should review the section "Resolving Object
Differences in the View Difference Report" to gain an understanding of the options for
resolving object differences.
Note: If you are also upgrading your source system to a new version, after upgrading
your existing repository, follow the steps in "To set up folder mappings and the
physical data source connection".
To upgrade an existing repository using the Refresh Base option
1.
2.
From the drop-down list, select Refresh Base, and then click OK.
The Import Source System Container dialog is displayed.
3.
Click Change import/export folder to navigate to the directory that holds the
metadata files for the new base container to which you are upgrading.
4.
Select the container to which you are upgrading from the Source System Container
drop-down list, and click OK.
5.
In the Importing Tables dialog, re-type the text in the text box to confirm you want
to proceed, and click Yes.
When the import process is complete, the Importing Tables dialog tells you how
long the process took.
6.
Click OK.
The Create Difference Report dialog is displayed.
7.
Create the Difference Report to view the differences between the new and existing
DAC repositories.
a.
Enter a name for the Difference Report, or leave the default name.
b.
c.
d.
Click OK.
When the Difference Report is complete, the Creating Difference Report dialog
tells you how long the process took.
e.
Click OK.
The View Difference Report dialog displays the differences between the new
and existing DAC repositories.
8.
In the View Difference Report dialog, resolve the differences between the new
repository (source) and existing repository (target). For detailed information about
the View Difference Report, see "Resolving Object Differences in the View
Difference Report".
To resolve the differences, you either accept or reject the objects that are listed as
new or changed in the new repository (the version to which you are upgrading).
a.
In the navigation tree, select the repository object for which you want to view
the differences between the new and existing repositories.
If the object selected in the navigation tree is a hierarchical object, the subtabs
for the child objects appear in the bottom pane of the Object Difference
window.
b.
(Optional) Filter the objects that appear in the top, right window by selecting
one of the options from the drop-down list in the toolbar.
c.
For parent objects in the top pane and any child objects in the bottom pane,
accept or reject the object in the difference list by selecting or deselecting the
Accept Source check box.
For detailed information about these options and the merge outcome, see
"Possible Repository Merge Outcomes Based on Your Decisions".
If a child object has been changed but not the parent object, the
parent object will still appear in the Object Difference window even
though it has not been changed.
Note:
d.
(Optional) Once you have made a decision about whether to accept or reject
the difference, select the Resolved check box to indicate you have resolved the
object.
e.
Repeat Steps a, b, and c, until you have resolved all object differences.
f.
Click Merge.
The Merge dialog is displayed and lists the details of the merge.
9.
10. Click OK in the Merging Repositories dialog when the merge process is complete.
If you are also upgrading your source system to a new version, after upgrading the
existing repository, follow the steps below.
To set up folder mappings and the physical data source connection
1.
In the custom container, delete all of the mappings for logical folders to physical
folders, which are listed in the Source System Folders tab in the DAC Design view.
2.
In the custom container, reference the mappings for the logical folders to physical
folders from the new base container.
a.
b.
In the Reference dialog, select the new base container from the drop-down list.
c.
Select all the mapping records that appear in the list, and click Add.
The Adding dialog lists the mappings that were added to the custom
container.
3.
d.
e.
Change the name of the physical data source connection to reflect the name of the
upgraded source system.
a.
b.
c.
Change the name of the source connection to reflect the name of the upgraded
source system.
For example, if you are upgrading from Oracle EBS R11 to R12, and the source
connection name was Ora_R11, you would change it to Ora_R12. Do not
change any other value in this record.
15-10 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
d.
Click Save.
4.
In Informatica Workflow Manager, open the Relational Connection Browser (in the
menu bar, select Connections, and then select Relational), and edit the name of
the connection to match the name you entered in step 3.
5.
Upgrade the existing DAC repository tables to be compatible with the new DAC
repository release.
a.
Configure the new DAC Client version to read the DAC metadata from the
existing DAC repository.
b.
Log in to the DAC and select Yes if prompted to upgrade the repository tables.
2.
Export the custom applications from the existing custom repository to a folder
other than the standard DAC export folder (DAC\export) or the folder into which
you backed up metadata in the previous format.
3.
Import the new DAC metadata for the application from the standard DAC export
folder (DAC\export). Select the Truncate Repository Tables check box.
For instructions on importing DAC metadata, see "Importing DAC Metadata".
4.
Import the customized DAC metadata that you exported in Step 2, and deselect
the Truncate Repository Tables check box.
This will append all the custom data to the repository, thus bringing in the
customizations, which include the following:
5.
Refresh the source system container to locate any missing objects in the
customized application. The missing objects are any new objects that the
15-11
preconfigured applications may have that are not referenced in the custom
applications.
6.
a.
b.
From the drop-down list, select Simplified Refresh From Base, and then click
OK.
c.
Select the appropriate container from the Source System Container drop-down
list, and click OK.
d.
Rebuild all the subject areas and execution plans in the customized application to
include any new changes in the object dependency. For information about
building subject areas and execution plans, see Chapter 7, "Customizing ETL
Processes,", Chapter 9, "Designing Subject Areas," and Chapter 6, "Building and
Running Execution Plans."
The Replace Base option enables you to upgrade the DAC repository when you are
phasing out an older release of a transactional application and moving to a newer
release, for example, phasing out Siebel 7.5.3 and moving to Siebel 7.8.
15-12 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
In Step 1 of the high-level process flow, you import the repository data for the new
base container into the repository temporary tables. This repository is referred to as the
source in the Upgrade/Merge Wizard
In Step 2, you create a Difference Report that compares the new base container (source
repository) with the existing base container (including customizations). The existing
base container is referred to as the target
In Step 3, you accept or reject the objects that the Difference Report shows as being
present in the source but not the target or changed in the source but not the target. See
Section , "Possible Repository Merge Outcomes Based on Your Decisions" for a
description of how objects are merged based on the action you take.
In Step 4, after you have resolved the differences, you then execute the merge. In Step
5, the DAC references the customizations in the newly merged repository with the new
base container.
The repository data is imported from a file system and should
be in the format of DAC 10.1.3.4 or higher. If it is in the 7.9.x format,
you should do the following:
Note:
1.
Restore the repository data into a database using the 7.9.x DAC (using the
regular DAC import process).
2.
3.
The metadata in the folder in Step 3 above will become the source
for this upgrade.
15-13
Before you begin this procedure you should review the section "Resolving Object
Differences in the View Difference Report" to gain an understanding of the options for
resolving object differences.
To upgrade an existing DAC repository
1.
2.
From the drop-down list, select Replace Base, and then click OK.
The Import Source System Container dialog is displayed.
3.
Click Change import/export folder to navigate to the directory that holds the
metadata files for the new base container to which you are upgrading.
4.
Select the appropriate container from the Source System Container drop-down list,
and click OK.
5.
In the Importing Tables dialog, re-type the text in the text box to confirm you want
to proceed, and click Yes.
When the import process is complete, the Importing Tables dialog tells you how
long the process took.
6.
Click OK.
The Create Difference Report dialog is displayed.
7.
Create the Difference Report to view the differences between the new and existing
DAC repositories.
a.
Enter a name for the Difference Report, or leave the default name.
b.
c.
d.
Click OK.
When the Difference Report is complete, the Creating Difference Report dialog
tells you how long the process took.
e.
Click OK.
The View Difference Report dialog displays the differences between the new
and existing DAC repositories.
8.
In the View Difference Report dialog, resolve the differences between the new
repository (source) and existing repository (target). For detailed information about
the View Difference Report, see "Resolving Object Differences in the View
Difference Report".
To resolve the differences, you either accept or reject the objects that are listed as
new or changed in the new repository (the version to which you are upgrading).
a.
In the navigation tree, select the repository object for which you want to view
the differences between the new and existing repositories.
If the object selected in the navigation tree is a hierarchical object, the subtabs
for the child objects appear in the bottom pane of the Object Difference
window.
b.
(Optional) Filter the objects that appear in the top, right window by selecting
one of the options from the drop-down list in the toolbar.
15-14 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
c.
For parent objects in the top pane and any child objects in the bottom pane,
accept or reject the object in the difference list by selecting or deselecting the
Accept Source check box.
For detailed information about these options and the merge outcome, see
"Possible Repository Merge Outcomes Based on Your Decisions".
If a child object has been changed but not the parent object, the
parent object will still appear in the Object Difference window even
though it has not been changed.
Note:
d.
(Optional) Once you have made a decision about whether to accept or reject
the difference, select the Resolved check box to indicate you have resolved the
object.
e.
Repeat Steps a, b, and c, until you have resolved all object differences.
f.
Click Merge.
The Merge dialog is displayed and lists the details of the merge.
9.
10. Click OK in the Merging Repositories dialog when the merge process is complete.
11. Rebuild all the subject areas and execution plans in the customized application to
include any new changes in the object dependency. For information about
building subject areas and execution plans, see Chapter 7, "Customizing ETL
Processes,", Chapter 9, "Designing Subject Areas," and Chapter 6, "Building and
Running Execution Plans."
The Peer to Peer Merge option enables you to merge DAC repositories of different
instances of the same release. For example, in a development environment you may
have two instances of a DAC repository used with Oracle BI Applications release 7.9.5
that you want to merge.
15-15
In Step 1 of the high-level process flow, you export one instance of the existing
customized source system container to the file system and then import this container
into the repository temporary tables. This repository is referred to as the source in the
Upgrade/Merge Wizard.
In Step 2, you create a Difference Report that compares the instance 1 container
(including customizations) with the instance 2 container (including customizations).
The instance 2 container is referred to as the target.
In Step 3, you accept or reject the objects that the Difference Report shows as being
present or changed in the source but not the target. See Section , "Possible Repository
Merge Outcomes Based on Your Decisions" for a description of how objects are
merged based on the action you take.
In Step 4, after you have resolved the differences, you then execute the merge. In Step
5, the Upgrade/Merge Wizard references the customizations in the newly merged
container with the instance 1 base container.
2.
From the drop-down list, select Replace Base, and then click OK.
The Import Source System Container dialog is displayed.
15-16 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
3.
Click Change import/export folder to navigate to the directory that holds the
metadata files for instance 1 of the source system container you want to merge.
4.
Select the appropriate container from the Source System Container drop-down list,
and click OK.
5.
In the Importing Tables dialog, re-type the text in the text box to confirm you want
to proceed, and click Yes.
When the import process is complete, the Importing Tables dialog tells you how
long the process took.
6.
Click OK.
The Create Difference Report dialog is displayed.
7.
Create the Difference Report to view the differences between the instance 1
container and the instance 2 container.
a.
Enter a name for the Difference Report, or leave the default name.
b.
c.
d.
Click OK.
When the Difference Report is complete, the Creating Difference Report dialog
tells you how long the process took.
e.
Click OK.
The View Difference Report dialog displays the differences between the
instance 1 and instance 2 containers.
8.
In the View Difference Report dialog, resolve the differences between the instance
1 and instance 2 DAC repositories. The instance 1 repository is referred to as the
source or existing container, and instance 2 as the target or new container. For
detailed information about the View Difference Report, see "Resolving Object
Differences in the View Difference Report".
To resolve the differences, you either accept or reject the objects that appear as new
or changed in the instance 1 container but do not appear in the instance 2
container.
a.
In the navigation tree, select the repository object for which you want to view
the differences between the instance 1 and instance 2 containers.
If the object selected in the navigation tree is a hierarchical object, the subtabs
for the child objects appear in the bottom pane of the Object Difference
window.
b.
(Optional) Filter the objects that appear in the top, right window by selecting
one of the options from the drop-down list in the toolbar.
c.
For parent objects in the top pane and any child objects in the bottom pane,
accept or reject the object in the difference list by selecting or deselecting the
Accept Source check box.
For detailed information about these options and the merge outcome, see
"Possible Repository Merge Outcomes Based on Your Decisions".
15-17
If a child object has been changed but not the parent object, the
parent object will still appear in the Object Difference window even
though it has not been changed.
Note:
d.
(Optional) Once you have made a decision about whether to accept or reject
the difference, select the Resolved check box to indicate you have resolved the
object.
e.
Repeat Steps a, b, and c, until you have resolved all object differences.
f.
Click Merge.
The Merge dialog is displayed and lists the details of the merge.
9.
10. Click OK in the Merging Repositories dialog when the merge process is complete.
The Upgrade/Merge Wizard generates a View Difference Report for the following
upgrade and merge options:
Refresh Base
Replace Base
A View Difference Report is not available if you select to upgrade using the Simplified
Refresh From Base option. For more information about the upgrade and merge
options, see "Overview of Upgrade and Merge Options".
15-18 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Navigation Tree
The navigation tree displays the repository object types that are compared in the
existing and new repositories. When you select a repository object in the
navigation tree, the differences are listed in the object difference window.
User Key
Unique identifier for the object.
Change Description
Indicates the type of difference that exists between the containers.
Container
The new or target container.
Accept Source
Selecting the Accept Source check box indicates you want to accept the change
that appears in the source container. For detailed information about the
15-19
Resolved
Optional field that indicates the object difference has been resolved. Note: This
field is for user reference only. It does not have an affect on the merge process.
Text Fields
The text fields in at the bottom of the dialog, labeled "New Source System
Container "and "Existing Source System Container," display a textual and
hierarchical representation of the object difference selected in the Object Difference
window.
Query Functionality
You can query for objects in the Object Difference window and in the subtabs. For
more information about the DAC query functionality, see "Using the DAC Query
Functionality".
Deleted-Source. Displays objects that were deleted from the source container.
Deleted-Target. Displays objects that were deleted from the target container.
Modified. Displays objects that were modified differently in the source and
target containers.
The following tables list the merge outcomes based on the decision you make about
the object differences listed in the View Difference Report.
Table 152, " Merge Outcomes for Repository Upgrade (DAC 784) Option"
15-20 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Table 153, " Merge Outcomes for Replace Base and Refresh Base Options"
Table 152
Change
Object
Ownership
Type
Description
Added-Source
Original
Added-Source
Clone
Not applicable
Added-Source
Reference
Not applicable
Added-Target
Original
Added-Target
Clone
Added-Target
Reference
Deleted-Source
Original
Deleted-Source
Clone
Deleted-Source
Reference
Deleted-Target
Original
Deleted-Target
Clone
Deleted-Target
Reference
Not applicable
15-21
Table 152 (Cont.) Merge Outcomes for Repository Upgrade (DAC 784) Option
Object
Ownership
Type
Description
Modified
Not
applicable
Modified-Cloned
Clone
Not applicable
Modified-Referenced Reference
The parent of a
referenced object has
been modified in the
source container.
Not applicable
Not applicable
Cloned-Source
Not
applicable
Not applicable
Not applicable
Cloned-Target
Not
applicable
Not applicable
Change
Table 153
Change
Object
Ownership
Type
Description
Added-Source
Original
Not applicable
Added-Source
Clone
Not applicable
Automatically adjusts
the lineage for objects in
child containers if the
object was referenced in
them.
Added-Source
Reference
Added-Target
Original
Not applicable
Automatically adjusts
the lineage for objects in
child containers.
Added-Target
Clone
Automatically adjusts
the lineage for objects in
child containers.
15-22 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Table 153 (Cont.) Merge Outcomes for Replace Base and Refresh Base Options
Change
Object
Ownership
Type
Description
Added-Target
Reference
Automatically adjusts
the lineage for objects in
child containers.
Deleted-Source
Original
Automatically adjusts
the lineage for objects in
child containers if the
object was referenced in
them.
Deleted-Source
Clone
Automatically adjusts
the lineage for objects in
child containers if the
object was referenced in
them.
Deleted-Source
Reference
Automatically adjusts
the lineage for objects in
child containers if the
object was referenced in
them.
Deleted-Target
Original
Not applicable
Deleted-Target
Clone
Not applicable
Deleted-Target
Reference
Modified
Not
applicable
Not applicable
Not applicable
15-23
Table 153 (Cont.) Merge Outcomes for Replace Base and Refresh Base Options
Change
Object
Ownership
Type
Description
Modified-Cloned
Clone
Modified-Referenced Reference
Not applicable
Automatically adjusts
the lineage for objects in
child containers if the
object was referenced in
them.
Cloned-Source
Not
applicable
Not applicable
Not applicable
Cloned-Target
Not
applicable
Not applicable
Table 154
Change
Object
Ownership
Type
Description
Added-Source
Original
Not applicable
Added-Source
Clone
Not applicable
Automatically adjusts
the lineage for objects in
child containers.
Object will be added to Not applicable
the target custom
container as a referenced
object.
Added-Source
Reference
Added-Target
Original
Automatically adjusts
the lineage for objects in
child containers.
15-24 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Change
Object
Ownership
Type
Description
Added-Target
Clone
Automatically adjusts
the lineage for objects in
child containers.
Added-Target
Reference
Automatically adjusts
the lineage for objects in
child containers.
Deleted-Source
Original
Automatically adjusts
the lineage for objects in
child containers if the
objects were referenced
in them.
Deleted-Source
Clone
Automatically adjusts
the lineage for objects in
child containers if the
objects were referenced
in them.
Deleted-Source
Reference
Automatically adjusts
the lineage for objects in
child containers if the
objects were referenced
in them.
Deleted-Target
Original
Not applicable
Deleted-Target
Clone
Not applicable
Deleted-Target
Reference
15-25
Modified
Not
applicable
Not applicable
Not applicable
Modified-Cloned
Clone
Change
Modified-Referenced Reference
Cloned-Source
Cloned-Target
Not
applicable
Not
applicable
The parent of a
referenced object has
been modified in the
source container.
Not applicable
Automatically adjusts
the lineage for objects in
child containers if the
objects were referenced
in them.
Not applicable
Automatically adjusts
the lineage for objects in
child containers.
15-26 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
16
DAC Functional Reference
16
This chapter describes the functionality available in the DAC tabs, menu commands,
and right-click commands. It contains the following main topics:
16-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Command
Description
DAC User
Management
Enables users who are currently logged into DAC to change their
password.
Close
Command
Description
Design
Setup
Execute
16-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
UI Preferences
Enables you to export the DAC metadata, in XML format, based on the source system
container, in order to back up the metadata or to reproduce the environment
elsewhere. In the Export dialog, you can specify a directory in which to store the XML
file or accept the default directory, which is dac\export.
In the Export dialog, you can select the following category options:
Logical. Exports all information contained in the Design view and metadata
defined in the Seed Data menu.
Run Time. Exports information about ETL runs and schedules (contained in the
Execute view).
System. Exports all information contained in the Setup view, except passwords for
servers and database connections.
Update existing records. (Applicable to DAC standalone authentication only)
Exports the users, roles, and passwords.
Note: You can move small sets of data, without exporting the entire DAC repository,
by using the DAC patching functionality. For more information, see Chapter 12,
"Working With DAC Metadata Patches."
Import
Enables you to import the DAC metadata for the source system containers you specify.
In the Import dialog, you can specify the following:
Import/Export folder. A directory from which to import the data. The default
directory is DAC\export.
Truncate repository tables. Indicates whether you want to truncate the repository
tables. If you select this option, the existing metadata is overwritten.
Enable bulk mode. Indicates whether bulk mode is enabled. In bulk mode the
imported metadata is inserted into the repository as an array insert. Using this
option improves performance. If you do not select this option, DAC upserts
records in the repository tables one row at a time.
Update existing records. (Applicable to DAC standalone authentication only)
Imports the users, roles, and passwords.
In the Import dialog, you can select the following category options:
Logical. Exports all information contained in the Design view and metadata
defined in the Seed Data menu.
Run Time. Exports information about ETL runs and schedules (contained in the
Execute view).
System. Exports all information contained in the Setup view, except passwords for
servers and database connections.
Update existing records. (Applicable to DAC standalone authentication only)
Exports the users, roles, and passwords.
Enables you to generate a DAC repository report based on the following criteria:
Ownerless Objects
Unreferenced Objects
Dead References
The Upgrade/Merge Wizard enables you to upgrade and merge the content of DAC
repositories. For more information, see "Upgrading, Comparing and Merging DAC
Repositories".
Apply Patch
Enables you to apply a DAC metadata patch to the DAC repository. For more
information, see "Working With DAC Metadata Patches".
Purge Run Details
Enables you to purge completed runs from the run history. The last run cannot be
purged.
In the Purging Run History... dialog, the following options are available:
Delete all completed runs. Purges all completed runs except for the last run.
Delete completed runs before specified date. Enables you to select a date before
which all runs except the last run will be purged.
Keep run definition. Purges all related information about a run but leaves the run
header information.
Enables you to run analyze table commands for all the DAC repository tables.
Default Index Properties
Enables you to specify which databases will be associated with newly created indexes.
Repository Audit Trail
Enables you to access the Repository Audit Trail, which stores information about
actions performed on the repository, users, machine IP addresses, and repository
timestamps. You can also add user-defined audit trail records.
16-6 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Enables you to drop all the DAC repository tables. This action deletes all data in the
repository.
Change Encryption Key
Enables you to change the DAC repository encryption key. See "Changing the DAC
Repository Encryption Key" for instructions.
Command
Description
When running the DAC Server in Web mode, allows you to start the
DAC Server.
When running the DAC Server in Web mode, allows you to restart
the DAC Server.
When running the DAC Server in Web mode, allows you to stop the
DAC Server.
Command
Description
Configure
Clears the refresh dates for all source and target tables. This action
forces a full load to occur during the next ETL process.
Command
Description
Windows (MFS)
UNIX (MOTIF)
Java (METAL)
UI Preferences
The UI Preferences menu command displays the UI Preferences dialog, which contains
the following options:
16-8 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Always Show Last Updated. Displays the Last Updated column in all tabs and
subtabs. This column shows the timestamp for when the repository object was last
updated.
Always show system columns. Displays system columns in all tabs and subtabs.
Start in Query Mode. Indicates a tab or subtab will start in Query Mode. Select a
tab or subtab from the navigation window, and then select the Start in Query
Mode check box.
Accessibility Mode Enabled. Enables accessible keyboard shortcuts. For a
description of the shortcuts, see "DAC Accessibility Keyboard Options".
Command
Description
Login Details
System Information
DAC Help
About DAC
16-10 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Tool
Description
New
Save
Undo
Undoes changes made to the current record after the last save.
Delete
Deletes the selected record. If you delete a parent record, the child
records are also deleted.
When you delete a column from a table, the column is not automatically
deleted from the index.
The DAC does not display deleted objects. You must look at the
database to figure out what objects were deleted.
Query
Opens a blank query field where you can enter query criteria.
Refresh
Retrieves the data from the repository with the last used query.
Help
Table 168 describes the commands available in the top pane toolbar when the Design
view is active.
Table 168
Command
Description
Reference
Assemble
Drop-down list
Table 169 describes the commands available in the top pane toolbar when the Setup
view is active.
Table 169
Tool
Description
Generate
Test
Table 1610 describes the commands available in the top pane toolbar when the
Execute view is active.
Table 1610
Tool
Description
Build
Run Now
Stop
Abort
Restart
(Current Runs and Run History tabs) Restarts the selected ETL
after the ETL has failed, stopped, or been aborted.
Auto Refresh(
Current Runs tab). Enables you to turn on and off the automatic
screen refresh functionality and set the refresh interval.
16-12 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Command
Description
Copy String
Paste String
Pastes a string from the clipboard into a selected cell that supports a string
data type.
New
Copy Record
Creates a copy of the selected record, with a unique record ID. The new
record is committed to the DAC repository when you click the Save button
or click outside the cell.
In the Design view tabs (except for the Indices tab), Copy Record copies the
selected record and the record's child records. When you copy a subject area,
the tables are also copied but the tasks are not copied. You need to use the
Assemble command to reassemble the subject area and add tasks to it.
In the Design view Indices tab and Setup and Execute views, Copy Record
copies only the selected record.
Save
Undo
Undoes the changes made to the current record after the last save.
Delete
Deletes the selected record. If you delete a parent record, the child records
are also deleted.
When you delete a column from a table, the column is not automatically
deleted from the index. You must manually delete columns from indexes
that were deleted from a table or else the ETL process will fail.
The DAC does not display deleted objects. You must look at the database to
figure out what objects were deleted.
Query
Refresh
Retrieves the data from the repository with the last used query.
UI Preferences
Output to File
Outputs to a text file in the DAC root directory the contents of the current
tab's record list.
Record Info
Displays the record's unique ID, object type, current source system, owner
source system, and the timestamp for when it was last updated. It also
displays the source system lineage and the source systems that reference the
object.
Update Records For some columns, enables you to update the column value for each row to a
single value.
16-14 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Reference. Opens the Reference dialog, which enables you to reference objects
from one container to another. The reference function works like a symbolic link or
shortcut.
Re-Reference. If an object is a referenced object, that is, a reference to an object in
another container, and a change is made to the original object's child objects, use
this command to import the changes to the referenced object.
Push to References. If an original object is changed, you can use this command to
export the changes to all referenced objects' child objects.
De-Clone. When you make changes to a referenced object, the new object is called
a clone. This command enables you to revert a cloned object back to its state as a
reference.
Compare Clone with Original. Shows the difference between the clone and the
base object that was modified.
Re-Assign Record. This command enables you to reassign an objects ownership.
For more information about the ownership of objects, see "About Object Ownership in
DAC".
Add Object(s) to Patch
Enables you to add the selected object or all objects in the list to a patch. You specify
the patch to which you want to add the object or objects, and then specify whether you
want to add to the patch only the parent object or the parent object, child object, and
extended properties. For more information about patches, see "Working With DAC
Metadata Patches".
Assemble
(Subject Areas tab) Assembles a specified subject area by adding to the subject area the
dimension and related tables as well as the associated tasks. For more information, see
"Creating a Subject Area".
Generate Index Scripts
(Tables and Indices tabs) Generates drop and create index scripts and analyze tables
scripts for all tables that participate in the ETL process. The results are stored in the
log\scripts directory.
Generate DW Table Scripts for Oracle
(Tables tab and Target For Tasks (RO) subtab in the Tables tab) Enables you to generate
scripts for creating, upgrading, and dropping data warehouse tables for Oracle
database types. For more information, see "Creating, Upgrading or Dropping Subsets
of Tables in the Schema for Oracle Databases".
Related Tasks
(Tables tab) Shows all tasks that directly or indirectly participate in populating the
selected table.
DAC Functional Reference 16-15
Image and Trigger Scripts. Generates change capture scripts for tables with
defined image suffixes. The scripts may include delete triggers, create and drop
statements for delete triggers, and image tables and their indexes.
View Scripts. Generates change capture view scripts for full or incremental mode
for tables that participate in the change capture process. This command can be
used for unit testing.
Change Capture SQL. Generates change capture SQL scripts for full or
incremental mode for tables that participate in the change capture process. This
command can be used for unit testing.
Import Database Tables. Imports table definitions from a selected database. This
action does not import columns.
Import Indices. Import index definitions from a selected database for one or more
tables as listed in the result of the query.
Import Database Columns. Import column definitions from a selected database.
See "Adding a New Table and Columns to the Data Warehouse" for more information.
Add Actions
(Tables, Indices, and Tasks tabs) Enables you to add previously defined actions to
tables, indices, or tasks. For more information about actions, see "Using Actions to
Optimize Indexes and Collect Statistics on Tables".
Import Foreign Keys
(Tables tab) Enables you to import foreign key columns from the data warehouse and
associate the columns with foreign key tables. You can enter the table and column
information in the text box or import the information from a file. If you select the
Clone Referenced Records check box, DAC will make clones of any records that are
referenced objects. If you do not select Clone Referenced Records, DAC will not import
foreign keys for any referenced object.
Output Task Description
(Tasks tab) Saves to an HTML file the description for a selected task or for all tasks.
Synchronize Tasks
(Tasks tab) Imports the source and target table definitions for a task from Informatica
into the DAC repository. You can also choose to activate tables that had previously
been inactive or inactivate tables in DAC that are associated with the task but do not
appear in Informatica.
Flat Views
Opens a dialog that enables you to query for various objects, modify data, and do
mass updates.
16-16 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Command
Description
Test Connection
In Physical Data Sources tab, this command tests the database connection.
In the Informatica Servers tab, this command tests the connection to the
Repository Service and Integration Service.
The DAC Server performs this command if the DAC Client is connected
to a server. If the DAC Client is not connected to a DAC Server, then the
DAC Client performs the command.
Patches
Export Patch - Exports a patch and its contents from the DAC
repository and saves it in an XML file in a directory you specify.
Add as Child Patch(es) - Adds the selected patch as a child patch to
a patch you specify.
Add Objects to Patch (Time Range) - Adds contents to a patch based
on a period between two timestamps that you specify.
See Chapter 12, "Working With DAC Metadata Patches," for more
information about patches.
Command
Description
Run Now
Reset source(s)
(Execution Plans tab) Resets the refresh dates to null for all tables
relevant to the execution plan. You can choose to reset refresh dates
for tables in one or more source and target data sources.
Show Tables
(Execution Plans tab) Shows execution plan source and target tables.
(Execution Plans tab) Shows if two execution plans are sharing any
common source or target tables. When there are such instances, DAC
will serialize their execution. If there is no commonality, they can be
run in parallel.
Build
Auto Refresh
Restart
(Current Runs and Run History tab) Restarts the selected execution
plan.
Abort
(Current Runs and Run History tab) Stops the execution of the
selected execution plan and changes the status to Failed.
Mark as Completed
(Current Runs and Run History tabs) Fetches the log file for this run
from the DAC Server and saves it in the \ServerLog directory.
(Current Runs and Run History tabs) Saves a description of the run
as an HTML file in the Log\Statistics directory.
Flat Views
Opens a dialog that enables you to query for various objects, modify
data, and do mass updates.
16-18 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Indices Tab
Tables Tab
Tasks Tab
16-20 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Indices Tab
Indices Tab
The Indices tab lists all the indexes associated with the selected source system
container.
For more information, see:
Managing Indexes
Note:
ETL. An ETL index is used during the ETL process. DAC decides when to create
ETL indexes (unlike During ETL indexes) and usually does so early in the ETL
process.
Query. A query index is used during the reporting process and not during the ETL
process. DAC creates query indexes at a point that has minimal impact on the ETL
process. The last task reading from a table creates the query indexes.
During ETL. A During ETL index is used during the ETL process at a specific
point that you define. If you define a During ETL index, you need to make sure
that the index is assigned to a task, or else the index will not be created. You
should only assign one During ETL index to one task per execution plan. Only
advanced DAC users with a thorough understanding of the execution plans
should define During ETL indexes.
It is recommended that you have a clear understanding of when and where the index
will be used at the time you register the index in DAC.
Databases Column
Lists the databases associated with the selected index.
# Unique Columns Column
For unique indexes, the number of columns that will be unique.
16-22 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Is Unique Column
Indicates whether the index is unique.
Is Clustered Column
Indicates whether the index is clustered. There can be only one clustered index per
table.
Is Bitmap Column
Indicates whether the index is of the bitmap type.
Allow Reverse Scan Column
Applicable only for DB2-UDB databases. The index will be created with the Allow
Reverse Scan option.
Always Drop & Create Column
Indicates whether the index will be dropped and created regardless of whether the
table is being loaded using a full load or incremental load.
Always Drop & Create Bitmap Column
Indicates whether indexes of the bitmap type will be dropped and created regardless
of whether the table is being loaded using a full load or incremental load.
Index actions can override the default index behavior for dropping and creating
indexes by mode type (full load, incremental load, or both).
Action Type Column
The index action types are the following:
Create Index
Drop Index
Indices Tab
Position Column
The ordinal position of the column in the index structure.
Sort Order Column
Indicates whether the index sort order is ascending or descending.
16-24 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
16-26 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
16-28 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Included Column
Indicates whether the extended table is included in the selected subject area. If the
check box is selected, the extended table will be included in the subject area assembly
process.
Name Column
The name of the table associated with the selected subject area.
16-30 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Tables Tab
The Tables tab lists the physical database tables defined in the database schema that
are associated with the selected source system container. It enables you to view and
edit existing tables and to create new ones.
For more information, see:
Warehouse Column
Indicates whether the table is a warehouse table. If this option is not selected, the
schema creation process will not include this table.
Image Suffix Column
Suffix for image tables. Applicable only to Siebel source tables. For more information
about image tables, see the description of the Change Capture Scripts command in the
section "Design View Right-Click Menu Commands".
Is MultiSet Column
Indicates whether the table is a MultiSet table. Applicable only to Teradata databases.
Has Unique Primary Index Column
Indicates whether the table has a Unique Primary Index. Applicable only to Teradata
databases.
The table action types enable you to trigger SQL scripts to analyze or truncate tables.
Table actions for analyzing or truncating tables override all other table properties.
Action Type Column
The default actions on a table during an ETL process are truncating a table and
analyzing a table. If you want to override any of these syntaxes, you can define actions
by mode (full or incremental). Once an action is defined, it overrides the default
behavior.
Note: You can associate an action to multiple objects at the same time. First, identify
the objects that you want to associate an action with by using the query functionality.
Then, right-click on the results displayed, and select Associate Actions. Next, select an
action and the mode you want to associate it with.
The table action types are the following:
Analyze Table
Tables Tab
Truncate Table
Use this type to truncate tables.
Length Column
An integer value that indicates how many characters a column can hold.
Precision Column
An integer value that indicates the total number of digits to the left and right of the
decimal point.
16-32 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Nullable Column
Indicates the column can have a NULL value. "NULL" stands for the absence of a
known value. If the Nullable check box is not selected, the column is declared NOT
NULL, which means the column must contain a value. When inserting a row without
providing an explicit value for a column, that column will get the default value if the
column has one or NULL if the column is not specified as NOT NULL. Otherwise, an
error is generated
Unicode Column
Indicates whether the column is Unicode.
Foreign Key to Table Column
Indicates the table in which the column is a foreign key.
Foreign Key to Column
Indicates the column that is a foreign key.
Default Value Column
The default value must be the same data type as the column. If the value is a CHAR or
VARCHAR type, the value must be enclosed within quotes ("<value>"). If the value is
a number, it does not need to be enclosed within quotes.
Teradata Length Column
Applicable to Teradata databases only. Indicates the column length.
Teradata Precision Column
Applicable to Teradata databases only. Indicates the column precision.
Teradata Primary Index Order Column
Applicable to Teradata databases only. On Teradata databases, it is important to have a
primary index for every table. This column indicates the position that a given column
will have in the primary index. If the value is 0 or empty, the column is not part of a
primary index.
For Teradata Statistics Column
Applicable to Teradata databases only. If the check box is selected, DAC will collect
statistics on the specified column.
Tables Tab
Is Unique Column
Indicates whether the index is unique.
Is Clustered Column
Indicates whether the index is clustered. There can be only one clustered index for
each table.
Is Bitmap Column
Indicates whether the index is of the bitmap type.
Allow Reverse Scan Column
Applicable only for DB2-UDB databases. The index will be created with the Allow
Reverse Scan option.
16-34 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
available for you to assign to a task. The DAC Server uses the task phase to prioritize
tasks and to generate a summary of the time taken for each of the phases.
Data Source Column
Data source for the task.
Truncate Always Column
Indicates the target table will be truncated regardless of whether a full or incremental
load is occurring.
Truncate for Full Load Column
Indicates the target tables will be truncated only when a full load is occurring.
Analyze Tables Column
Indicates the tables will be analyzed during the ETL process.
16-36 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Tasks Tab
Tasks Tab
The Tasks tab lists all the tasks associated with the selected source system container.
For more information, see:
16-38 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
In addition, there are several internal execution types that you will not be able to select
when creating new tasks. Tasks of these types are categorized as either internal change
capture tasks or internal data warehouse tasks. All of these tasks are color-coded in
pink in the Tasks tab.
IMG_BUILD
Used for internal change capture. If you are using multiple Siebel transactional
sources, you cannot change the behavior of the change capture process. This task
requires change capture tables to be created on the other sources also. When
adding additional Siebel sources, on the Tables tab in the Design view, right-click
and select Change Capture Tasks. This action generates change capture tasks. Use
this same action to disable or delete change capture tasks.
IMG_SYNC
Used for internal change capture. If you are using multiple Siebel transactional
sources, you can create this task for the additional tasks for doing similar change
capture sync processes. You cannot change the behavior of the change capture
sync process. This task requires change capture tables to be created on the other
sources also. This task should be used with discretion for Siebel sources only.
Success Action. Use to execute a SQL script after a task runs successfully.
Tasks Tab
Failure Action. Use to execute a SQL script if a task fails during its execution.
Restart Action. Use to execute a SQL script when a task that previously failed is
restarted.
Upon Failure Restart Action. Use to execute a SQL script to restart a task that
fails.
Looping of workflows. Enables you to configure the full and incremental load
commands for tasks to repeat (or loop) multiple times during the execution of an
ETL process. For instructions, see "Looping of Workflows".
Heuristics. Enables you to assign a heuristics rule to a task. For instructions, see
"Assigning a Heuristics Rule to a Task".
16-40 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Wait. Indicates the selected task will wait to be executed until the tasks of a
specified phase have been executed.
Block. Indicates the selected task will block all tasks of the specified phase from
being executed until is has been executed.
Grain Column
Applicable only for blocks. Enables you to specify whether the action you choose
affects all tasks of a specified phase or related tasks. Possible values are the following:
Tasks Tab
Scope Column
For multi-source execution plans only. Specifies how the Block action of the phase
dependency behaves in relation to multi-source execution plans. Possible values are
the following:
Both
Indicates the blocking action is active for tasks that have the same source and
target physical data source connections.
Source
Indicates the blocking action is active for tasks that have the same source physical
data source connection.
Target
Indicates the blocking action is active for tasks that have the same target physical
data source connection.
None
Indicates the blocking action is active for all tasks regardless of the source and
target physical data source connections.
Phase Column
The ETL phase that will apply to the Action and Grain properties.
Primary
Indicates the table is a primary source of data.
Auxiliary
Indicates the table is a secondary source of data.
Lookup
Indicates the table is a lookup table.
16-42 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Note:
A table can be neither Primary nor Auxiliary but still be used for
getting some attributes to populate a dimension or fact table. The
changes in these kinds of source tables are not reflected in the
dimension or fact table once the data is populated.
Data Source Column
Data source for the table. When a data source is not specified, the default is the tasks
primary source.
Alias Column
An alternative name for a source table.
When multiple tasks from different execution plans read from the same source table
and write to the same target table, it is necessary to define an alias for one of the source
tables in order for DAC to track refresh dates accurately.
DAC stores refresh dates by the combination of data source and table name. If an alias
is not defined in situations in which tasks from two different execution plans read
from the same source table and write to the same target table, issues with data
inconsistency can arise.
Tasks Tab
created, the table is analyzed so that the index statistics are up-to-date. When the
Truncate Always option is selected, this option is unnecessary.
Analyze Column
Indicates the tables will be analyzed during the ETL process.
16-44 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
In full mode:
During the change capture phase, views will be dropped and created as full
views.
16-46 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
During the change capture sync process, incremental views will be generated.
In incremental mode:
If the view does not exist, the incremental view will be created.
Dryrun
Possible values are True and False.
Indicates whether tasks are executed without invoking Informatica workflows. The
following processes are executed: change capture, truncation of tables, drop and
creation of indexes, and analyze statements.
This option should be used for debugging purposes only and not used in a production
environment.
Generic SQL Concurrency Limit
When the execution plan includes several tasks with the execution type of SQL or
Stored Procedure, this property controls how many of such tasks will be run
concurrently at any given time. The value should be numerical. The changes will be
effective for the next ETL. Restarting the DAC Server is not required.
Generic Task Concurrency Limit
Determines how many tasks with execution types other than Informatica can be run
concurrently. The value must be numerical.
To set this value, you should consider what the external tasks do. For example, if the
tasks open connections to a database, you should consider how this would affect the
predefined tasks. The value must be numerical.
HeartBeatInterval
The frequency (in seconds) the DAC Server polls all subsystems, including database
connections, to check whether they are in a consistent state. If the subsystems are not
in a consistent state, recovery and correction mechanisms are triggered. The value
must be numerical. For example, a value of 900 (the default value) indicates the system
will perform subsystem diagnostics and recovery procedures every 900 seconds.
InformaticaFileParameterLocation
Directory where the Informatica parameter files are stored. This is the directory in
which the DAC Server creates the Informatica parameter files and from which
Informatica reads the files.
No Run
Possible values are True and False.
When this property is set to True, tasks are generated in the Task Details subtab of the
Current Runs tab, but the tasks are not executed and the refresh dates are not updated.
Use this property for debugging purposes only.
Output Redirect
Possible values are True and False.
When set to True, logging information and standard output and errors are redirected
to files in the log directory. The file containing standard output starts with out_ and
ends with the .log extension. The standard error messages are in the file starting with
err_ and ending with the .log extension.
If this property is set to False, the logging information is directed to the machines
standard output and error files, which typically defaults to the console from which the
DAC Server was launched if the server was launched in a visible console mode. If the
server is launched as a Windows service, the logging information is directed to the
service log. If the DAC Server was launched with the command shell not visible, all
logging information is deleted.
Repository DB Pool Size
Indicates the maximum number of connections to the DAC Repository that the DAC
Server will maintain.
The idle DAC Server maintains a small spool of pre-existing database connections to
the DAC Repository for efficiency and resource optimization. It increases the pool size
to the value specified in this property when running a regular ETL process and reverts
to the default on completion of the ETL process.
You should consult with the DBA for the DAC Repository database when setting this
property.
Repository Name
Unique name for the DAC Repository. This name is displayed on the title bar.
Repository Upgrade Lockdown
Possible values are True and False.
When set to True, the DAC Repository cannot be upgraded to a newer version.
SQL Trace
Possible values are True and False.
When set to True, a hint is sent to the database connectivity layer of the DAC Server to
enable SQL tracing. Thus, every SQL statement that is run by the DAC Server is
spooled to the appropriate output log file.
It is recommended that you set this property to False, because enabling SQL tracing
causes the log files to grow extremely large in a short period.
Scheduler.Poll.Interval
Frequency (in seconds) the DAC Server polls for changes in the schedule
configuration.
Script After Every ETL
The name of the script or executable to be run after every execution plan. The file must
be placed in the DAC\scripts directory. For example, after running an execution plan,
you might want to run a process or perform certain tasks. These can be contained in a
script or executable.
Script Before Every ETL
The name of the script or executable to be run before every execution plan. The file
must be placed in the DAC\scripts directory. For example, before running an
execution plan, you might want to run a process or perform certain tasks. These can be
contained in a script or executable.
16-48 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
The execution plan will run only after the external process has finished. Therefore, it is
important that the script or executable does not fail.
Server Log Level
The output logging level. Possible values are the following:
FINEST
FINER
FINE
CONFIG
INFO
WARNING
SEVERE
The values are case sensitive. The values produce varying degrees of output reporting
detail, with the Severe value producing minimal log details, and the Finest value
producing the most extensive amount of reporting.
The recommended value for production environments is INFO.
Test Run
Possible values are True and False.
When set to True, the execution plan will not stop on errors.
Verify and Create Non-Existing Indices
Possible values are True and False.
When set to True, indexes defined in the DAC Repository will be automatically created
in the data warehouse database during an incremental load.
Note: When this system property is set to True, the DAC Server verifies whether
indexes defined in the DAC Repository are also defined in the data warehouse
database. This verification process can delay the execution of an execution plan.
WebClient.Poll.Interval
Frequency (in seconds) the DAC Client polls the DAC Server for its status when the
DAC Server is running in Web mode.
WorkerPoolSize
The number of worker threads available in the worker pool.
The worker threads do operations such as:
The value for this property should correspond to the number of task details that are
anticipated to run in parallel.
10
Notifies recipient of success or failure of each task.
5
Notifies recipient of success of failure of the entire ETL process.
1
Notifies recipient that ETL completed successfully.
16-50 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Properties Subtab
The Properties subtab contains the properties that you must configure to integrate
DAC with other ETL tools. See Chapter 14, "Integrating DAC With Other ETL Tools"
for more information.
Property Order Column
Used to sort the records in the subtab. Does not affect the functionality of the external
executor.
Name Column
Name of the property.
Value Column
The value that defines the property.
Note:
Name Column
Name of the Informatica Integration Service or Repository Service.
Type Column
Type of server.
Informatica
Specifies the Informatica Integration Service.
Repository
Specifies the Informatica Repository Service.
Service Column
The Informatica Integration Service name.
Server Port Column
Port number used by the Informatica Integration Service or Repository Service to
listen to requests.
Domain Column
Informatica domain name (as seen in Informatica Administrator.
Login Column
Informatica repository user name who has Administrator privileges for the
Informatica repository. Note that DAC must log in to Informatica as an Informatica
repository Administrator user that is configured in the native security domain.
Password Column
Password for the user specified in the Login field.
Num Parallel Workflows per EP Column
The maximum number of workflows that can be executed in parallel on the
Informatica Integration Service.
16-52 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Source
Warehouse
Informatica Repository
DAC Repository
Other
BI Server
For Oracle Fusion Applications only. Indicates the BI Server is registered as a data
source.
For instructions on registering the BI Server in DAC, see "Integrating DAC and
Oracle BI Server".
Oracle (OCI8)
Connects to an Oracle database using the tnsnames entry.
Oracle (Thin)
Connects to an Oracle database using thin driver.
DB2
DB2 UDB database.
DB2-390
DB2 390 database.
MSSQL
Microsoft SQL Server database.
Teradata
Teradata database.
Flat File
16-54 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
URL (Optional)
Specifies a JDBC URL for the data source connection. The value in this field must
conform to the database specifications.
Connection pool name used to register the BI Server as a data source (applies only
to Oracle Fusion Applications). For instructions on integrating DAC and the BI
Server, see "Integrating DAC and Oracle BI Server".
Event delay to configure the extracts for the different data sources in a
multi-source environment to occur independently. For instructions on setting up
an event delay, see "Setting Up Extract Delays, Event Delays and Data Source
Notifications".
Name Column
The name of the DAC extended property.
Value Column
The definition for the extended property.
Note:
16-56 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Note:
Name Column
Name of source or target table.
Execution Plan Column
The name of the execution plan to which the source or target table belongs.
Refresh Date Column
The refresh date for the source or target table.
Analyze Date Column
Indicates when the table was analyzed.
Number of Rows Column
Valid for target tables only. Indicates the total number of rows in the table after the
table has been loaded.
Open. A patch must have an Open status in order for objects to be added or
removed. Open patches cannot be exported.
Closed. When the patch status is changed to Closed, the patch can no longer be
edited. You can reopen a Closed patch in order to edit it. Closed patches can be
exported.
16-58 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Status Column
The status of an applied patch can be one of the following:
Completed. All objects in the patch were successfully applied to the DAC
repository
Incomplete. The patch application process completed with at least one error. Some
objects were applied successfully to the DAC repository.
Scheduler Tab
16-60 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Description
Completed
Failed
Not Executed
Tasks were not able to run before the DAC Server stopped.
Paused
Task group members are waiting for the other tasks in the group to be
executed.
Queued
Tasks for which the Depends On tasks are not yet completed.
Requeued
Tasks with a previous Failed status are submitted again. Tasks will
start running as soon as an Informatica slot is available.
Runnable
Tasks for which the Depends On tasks have completed and are ready
to be run but are waiting for an Informatica slot to be available.
Running
Tasks for which the Depends On tasks have been completed, have
gotten an Informatica slot, and are being executed.
Stopped
16-62 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
If a task has failed and has been requeued, it gets the maximum priority.
Tasks with greater phase priorities are executed next. When several tasks of the
same phase are eligible to run, the tasks with greater task priorities are executed
next. The prioritization is also based on the number of dependent tasks, the
number of source tables, and the average time taken by a task.
Depth Column
The level of the tasks dependency. Tasks that have no dependencies are depth 0. Tasks
that depend on other tasks of depth 0 are depth 1, and so on
Name Column
The task name.
Mode Column
Indicates whether the task will load in full or incremental load.
Group Column
Indicates the name of the task group, if the task belongs to one.
Task Status Column
Possible task statuses are the following:
Queued. Task is waiting for one or more predecessor tasks to complete. Appears
as light yellow.
16-64 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
16-66 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
For more information about building an execution plan, see "Building and Running
Execution Plans".
16-68 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Pre-ETL actions
Tables to be analyzed
Folder
Indicates an Informatica folder.
Datasource
Indicates a database connection parameter.
Name Column
Logical name of the folder or database connection.
Value Column
Physical name of the folder or database connection.
Delay Column
Indicates how many minutes an extract of a data source will be delayed after the first
extract of a multiple source extract process has started. For more information about
multi-source execution plans, see "Setting Up Extract Delays".
Prune Time Column
The Prune Time setting subtracts the number of prune minutes from the LAST_
REFRESH_DATE and supplies this value as the value for the $$LAST_EXTRACT_
DATE parameter. This property must be set based on experience with processes, such
as remote sync, that potentially can cause records to be missed.
Source System Column
Name of the source system associated with the parameter.
16-72 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Scheduler Tab
The Scheduler tab enables you to schedule ETL processes to be executed either once or
periodically. When you schedule an ETL or make changes to a schedule, the DAC
Server picks up the information from the DAC Client. The DAC Server polls the DAC
repository for changes periodically at a frequency set in the DAC System Properties
tab.
The top pane of the Scheduler tab lists ETL runs that have been scheduled. The bottom
window enables you to schedule an ETL run.
For instructions on scheduling ETL processes, see "Scheduling an Execution Plan".
Execution Plan Column
The name of the scheduled execution plan.
Last Schedule Status Column
The last run status of the scheduled ETL process. Possible values are Running,
Completed or Stopped.
Next Trigger Column
Time the scheduled ETL run will next be executed.
Status Description Column
Description of the last ETL run. Possible values are Running, Completed, or the reason
the process stopped.
Recurrence Column
Indicates how often the schedule will be executed.
Scheduler Tab
16-74 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
A
Troubleshooting DAC
This appendix describes common problems and how to resolve them. It contains the
following topics:
Tables Are Not Truncated When More Than One Task Writes to the Same Target
Table
Remove all the encrypted data from the DAC repository by calling the automation
utility command clearEncryptedData.
2.
Copy the new cwallet.sso file to the appropriate directory where the DAC
repository can access it. The default directory is <DAC_Config_
Location>\conf-shared\security\repository.
4.
b.
c.
Enter the table owner name and password, and click OK.
A message informs you whether the operation was successful.
d.
Distribute the new cwallet.sso file to all DAC installations that connect to this
repository.
b.
c.
For tasks with the status Failed, click Details in the subtab toolbar.
The Details dialog displays additional information about the task details.
2.
3.
4.
a.
b.
Restart the execution plan that failed by selecting it in the top pane of the Current
Run tab, and then clicking Restart.
DAC will rerun all the tasks with a status other than Completed.
Note: You can also manually run a task, change the task status to Completed, and then
restart the execution plan. Tasks with the status Completed will be skipped.
Caution: The DAC Server does not validate tasks that have been run
manually.
A-2 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Running. If a workflow is still running in Informatica, DAC waits for the running
workflow to finish execution.
If the workflow has successfully completed, DAC will change the status of the
task detail to Completed and will resume execution of the successors.
If the workflow has failed, DAC will change the status of the task detail to
Failed and will eventually halt the ETL. This is analogous to a normal failure
encountered during ETL execution.
Completed. If the workflow had completed in Informatica, the task will not be
re-run. DAC will change the status of the task detail to Completed and will
resume execution of the successors.
Failed. If the workflow in Informatica had failed, DAC will resubmit the workflow
for execution when the ETL process restarts.
Note: If a failed task includes truncate statements, the truncate action will occur
again when the task is restarted. This will also trigger the Upon Failure Restart
action if one is defined for the task.
correct status as Failed. In order to execute the execution plan from the point of failure,
submit the request to the server again.
The DAC Server will automatically terminate if it looses connection to the DAC
repository.
With:
pmcmd startworkflow -u %USER -p %PASSWORD
%FOLDER -lpf %PARAMFILE %WORKFLOW
2.
%WAITMODE -s %SERVER:%PORT -f
With:
pmcmd startworkflow -sv %SERVER -d %DOMAIN -u %USER -p %PASSWORD %WAITMODE -f
%FOLDER -lpf %PARAMFILE %WORKFLOW
3.
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.
A-4 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
plan, DAC creates as many instances of the extract tasks as there are sources, without
having the need to duplicate the workflows or DAC metadata.
At runtime, DAC creates an individual parameter file for each session, which contains
the evaluated name-value pairs for all parameters. DAC stores the parameter file at the
location specified by the DAC system property InformaticaParameterFileLocation. The
default location is <Domain_Home>\dac\Informatica\parameters.
If a task in a multi-source environment fails and you want to restart it, you can do so
from DAC or from Informatica. See the following instructions.
To restart a failed task in a multi-source environment using DAC
1.
Go to the Execution Plans tab in the Execute view, and select the appropriate
execution plan.
2.
3.
4.
5.
2.
3.
Change the parameter file name to match the naming convention Informatica uses
for parameter files:
<Informatica directory name>.<Informatica session name>.txt
4.
1.
2.
Export the entire repository (logical, system, and run time categories).
3.
Stop the DAC Server and all DAC Clients except for the one you are using.
4.
5.
6.
7.
8.
Re-enter the passwords for all Informatica services and all physical data source
connections.
Tables Are Not Truncated When More Than One Task Writes to the Same
Target Table
The DAC behavior for truncating tables when more than one DAC task writes to the
same target table is as follows:
The first DAC task truncates the target table. DAC does not truncate the target
tables during the execution of the subsequent tasks even if the Truncate Always or
Truncate for Full Load flags are checked on the subsequent tasks.
DAC truncates a target table only once during the life span of one ETL execution.
If the DAC task belongs to a group and the group truncate property is different
from the individual task truncate properties, the target table will be not truncated.
If you want to override this default behavior, you can create a task action and use the
Preceding Action action type to specify in a custom SQL statement that the table
A-6 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Tables Are Not Truncated When More Than One Task Writes to the Same Target Table
should be truncated. For more information about configuring task actions, see "Using
Actions to Optimize Indexes and Collect Statistics on Tables".
Tables Are Not Truncated When More Than One Task Writes to the Same Target Table
A-8 User's Guide for Oracle Business Intelligence Data Warehouse Administration Console
Index
A
actions
about, 7-16
assigning to repository object, 7-20
defining SQL script for, 7-17
example, 7-23
functions, 7-20
overview of, 7-16
types, 7-16
administrator
logging into DAC, 4-2
tasks and concepts, 4-1
architecture
overview, 3-1
ASCII Data Movement Mode
how to set, 4-24
assigning actions
to repository object, 7-20
authentication file, 4-2
modifying, 4-31
authentication modes, 4-1
B
best practices
columns, 7-4
configuration tags, 7-5
execution plans, 7-5
indexes, 7-4
repository objects, 7-1
source system containers,
subject areas, 7-5
tables, 7-4
task group, 7-3
tasks, 7-2
7-2
C
certification information, 1-2
code page validation, relaxed, 4-24
columns
best practices, 7-4
command line parameters
DAC repository, 13-4
configuration tags
D
DAC
architecture overview, 3-1
authentication file, 4-2
authentication modes, 4-1
external executor, integrating, 14-1
heuristics, using, 11-4
integrating with BI Server, 4-25
logging into as DAC user, 5-2
object ownership, 3-7
performance tuning, 11-1
process life cycle, 3-5
quick start, 5-1
setting up communication with Informatica, 4-16
setting up system properties, 4-26
starting and stopping the server, 4-10
DAC metadata
distributing, 4-26
DAC metadata patches
working with, 12-1
DAC parameters
defining, 8-8
DAC repository
command line options, 13-4
command line parameters, 13-4
configuring DAC Server connection, 4-9
encryption key, changing, 4-31
DAC Server
accessing, 4-6
accessing through command line, 13-1
high-availability, 4-7
managing, 4-6
monitoring using MBean Browser, 13-15
monitoring using WebLogic Server., 13-15
starting and stopping, 4-10
starting and stopping manually, 4-10
DAC server
command line access, 13-1
running automatically, 13-12
running two on same machine, 13-13
DAC user accounts
managing, 4-29
Index-1
DAC variables
about, 8-6
Data Movement Mode
how to set, 4-24
data warehouse
customizing, 7-6
managing schemas, 10-1
resetting, 13-14
Data Warehouse Administration Console (DAC)
DAC window, 3-8
editable lists, 3-11
exporting metadata, 4-26
importing metadata, 4-27
menu bar, 3-9, 16-2
navigation tree, 3-11
object ownership, 3-7
top pane toolbar, 3-10, 16-11
user interface, 3-8
databases,supported, 1-2
DataMovementMode
how to set, 4-24
E
email notifications
setting up, 4-12
encryption key
changing, 4-31
recovering from lost key, A-1
ETL processes
customizing, 7-1
execution plan
micro ETL, 6-6
monitoring processes, 5-7
scheduling, 5-9
execution plans
about multi-source, 6-3
about single-source, 6-2
best practices, 7-5
build process rules, 6-7
building and running, 6-8
considerations for multi sources, 6-3
heterogeneous, about, 6-3
homogeneous, about, 6-3
introduction to, 6-1
micro ETL, 6-6
monitoring, 5-7
restarting upon failure, A-2
running, 5-4
running concurrently, 6-11
scheduling, 5-9
setting up data source notifications, 6-14
setting up event delays, 6-14
setting up extract delays, 6-14
starting, 6-19
unit testing tasks, 5-10
external executors
integrating with DAC, 14-1
Index-2
F
flat views
querying,
3-14
H
heuristics, 11-4
I
incremental load strategy
about, 5-10
indexes
adding to data warehouse, 7-9
best practices, 7-4
managing, 11-1
Informatica
communication with DAC, 4-16
creating repository administrator, 4-23
high availability, 4-8
mappings, creating, 7-10
native security domain, 4-23
server sessions, 4-21
setting Integration Services custom
properties, 4-22
setting relaxes code page validation, 4-22
Informatica PowerCenter Integration Services
setting relaxes code page validation, 4-24
Informatica repository
importing objects, 7-9
Informatica server
pointing multiple servers to single
repository, 13-14
M
memory requirements, 1-2
minimum disk space, 1-2
O
operating systems, supported, 1-2
Oracle Business Analytics Warehouse
adding columns, 7-7
adding indices, 7-9
adding new table, 7-7
customizing, 7-6
P
parameters
at runtime, 8-2
data types, 8-4
defining database specific text type
parameters, 8-9
defining SQL type parameters, 8-10
defining text type parameter, 8-8
defining timestamp type parameters, 8-9
nesting, 8-6
overview, 8-1
preconfigured, 8-5
patches
working with, 12-1
physical data sources
setting up, 4-14
platforms, supported, 1-2
Q
query functionality
flat views querying, 3-14
query commands, 3-12
query operators, 3-12
query procedures, 3-13
R
refresh dates
about, 5-10
adding, 5-11
computing timestamps, 5-11
relaxed code page validation, 4-24
repository object
ownership, 3-7
repository objects
best practices, 7-1
requirements, system, 1-2
right-click menu
common commands, 16-14
Design view commands, 16-15
Execute view commands, 16-18
Setup view commands, 16-17
S
security
client requirements, 2-1
Fusion Middleware mode, 2-2
overview, 2-1
recommended setup, 2-6
standalone mode, 2-4
source system container
about, 3-5
best practices, 7-2
copying, 5-6
creating, 5-6
creating or copying, 5-6
DAC Repository objects, 3-6
SQL script
defining, 7-17
starting the DAC Server, 4-10
subject areas
best practices, 7-5
creating, 9-2
designing, 9-1
how DAC determines tasks for, 9-2
when to reassemble, 9-4
supported installation types, 1-2
system properties
setting up, 4-26
system requirements, 1-2
T
tables
adding new tables, 7-7
best practices, 7-4
tablespaces
specifying for indexes by table type, 11-2
task group
best practices, 7-3
creating, 7-12
task phase dependency
setting, 7-11
tasks
best practices, 7-2
creating tasks for workflows, 7-10
execution and queue management, 3-3
identifying failure, 5-9
viewing life span, 5-8
U
Unicode Data Movement Mode
how to set, 4-24
unit testing tasks, 5-10
Upgrade/Merge Wizard
Difference Report, 15-18
Peer to Peer Merge option, 15-15
Refresh Base option, 15-11
Refresh Base upgrade option, 15-7
Replace Base option, 15-12
Repository Upgrade (DAC 784) option, 15-3
resetting, 15-2
resolving object differences, 15-18
upgrade/merge options, 15-2
user account
managing, 4-30
W
Whats New, 1-1
workflows
looping, 11-12
Index-3
Index-4