Professional Documents
Culture Documents
[Max Marks: 75
10
(c)
Branch
dimension
Price
measure/fact
The Price can not be summed up across any dimension.
Percentages and ratios are non additive.
(d)
Q2
10
Step 4
The fourth screen is the protocol selection screen.
By default the TCP protocol is selected in this screen.
TCP is the standard communication protocol for internet and most local networks
Select the protocol and click next.
Step 5
The fifth and final screen asks the TCP/IP port number for the listener to run.
The default port number is 1521 and continues with the default port number.
It will ask us if we want to configure another listener. Select no to finish the listener
configuration.
(b) What is design center? Explain the functions of project explorer and connection
explorer windows.
(c)
Design Center
The Design Center is the main graphical interface used for the logical design of the data
warehouse. Through Design Center we define our sources and targets and design our
ETL processes to load the target from the source. The logical design will be stored in
a workspace in the Repository on the server.
Project Explorer
Through the Project Explorer window we can create objects that are relevant to our
project. It has nodes for each of the design objects we'll be able to create. We need to
design an object under the Databases node to model the source database. If we expand
the Databases node in the tree, we will notice that it includes both Oracle and NonOracle databases. It also has option to pull data from flat files. The Project Explorer can
also be used for defining the target structure.
Connection Explorer
The Connection Explorer is where the connections are defined to our various objects in
the Project Explorer. The workspace has to know how to connect to the various
databases, files, and applications we may have defined in our Project Explorer. As we
begin creating modules in the Project Explorer, it will ask for connection information
and this information will be stored and be accessible from the Connection Explorer
window. Connection information can also be created explicitly from within the
Connection Explorer.
Explain OWB components and architecture with diagram.
Following are the client side components:
Design Center
Repository Browser.
Following are the server side components:
Control Center Service
Repository
Target Schema.
(d)
The Design Center is the primary graphical user interface for designing a logical design
of the data warehouse.
Design Center is used to :
import source objects
design ETL processes
define the integration solution.
The Control Center Manager is a part of the design center. It manages communication
between target schema and design centre. As soon as you define a new object in the
Design Center, the object is listed in the Control Center Manager under its deployment
location. The design objects are stored as metadata in a centralized repository known
as workspace. This is where all of the design information is stored for the target systems
you are creating. The Repository Browser is another user interface used to browse
design metadata. The Target Schema is where OWB will deploy the object to, and
where the execution of ETL processes that load our data warehouse will take place. It
contains the objects that were designed in the Data Center, as well as the ETL code to
load those objects.
Explain the various steps involved in installing oracle database software.
Download the appropriate install file from Oracle web site
Unzip the install files into a folder to begin the installation
Run the setup.exe file from that folder to launch the Oracle Universal Installer
program (OUI) to begin the installation
step1 (to configure security updates)
Asks your email address and oracle support password to configure security updates.
step2 (to specify installation options)
following are the installation options
create and configure a database
install database software only
upgrade an existing database.
step3 (Install Type)
Here you can select the type of installation you want to perform.
The following are the installation types:
Single Instance database installation
Real Application Cluster database installation (RAC)
step4 (Language) To select the language in which your product will run
step5 (Product edition)
You can choose the edition of the database to install, Enterprise, Standard, Standard
Edition One, or Personal Edition.
step6(Installation Location)
This step asks you to specify the installation location for storing Oracle configuration
files and software files.
step7 (Prerequisite checks)
In this step oracle will checks the environment to see whether it meets the
requirements for successful installation. The prerequisite checks include checking of
operating system, physical memory, swap space, network configuration etc.
step8 shows the installation summary.
step9 (Install Product)
The actual installation happens in step 9. A progress bar proceeds to the right as the
installation happens and steps for Prepare, Copy Files, and Setup Files are checked
off as they are done.
step10 shows the success or failure of database installation
Q3
Q1
10
A target schema contains the data objects that contain your data warehouse data. The
target schema is going to be the main location for the data warehouse. When we talk
about our "data warehouse" after we have it all constructed and implemented, the target
schema is what we will be referring to. You can design a relational target schema or a
dimensional target schema. Every target module must be mapped to a target schema.
(b)
(c)
each level: id (identifies that level), Start and end date (designate time period of that
level), time span (number of days in the time period), description etc.
Level Attributes
Each level has Level Attributes associated with it that provide descriptive information
about the value in that level. For example, Day level has level attributes such as day of
week, day of month, day of quarter, day of year etc.
Hierarchies
It is composed of certain levels in order. There can be one or more hierarchies in a
dimension. The month, quarter and year can be a hierarchy. The data can be viewed at
each of these levels, and the next level up would simply be a summation of all the
lower-level data within that period.
(d)
Q4
(a)
(b)
The data mapping is the input needed to feed the ETL process. Mappings are visual
representations of the flow of data from source to target and the operations that need to
be performed on the data.
What is staging? What are its benefits? Explain the situation where staging is essential.
Staging
Staging is the process of copying the source data temporarily into tables in target
database. The purpose is to perform any cleaning and transformations before loading
the source data into the final target tables. Staging stores the results of each logical step
of transformation in staging tables. The idea is that in case of any failure you can restart
your ETL from the last successful staging step.
Staging make sense in the following case
large amount of data to load
many transformations to perform on that data while loading.
Pulling data from non-oracle databases
This process will take a lot longer if we directly access the remote database to pull and
transform data. We'll also be doing all of the manipulations and transformations in
memory and if anything fails; we'll have to start all over again.
Benefits
Source database connection can be freed immediately after copying the data to the
staging area. The formatting and restructuring of the data happens later with data in
the staging area.
If the ETL process needs to be restarted, there is no need to go back to disturb the
source system to retrieve the data.
(c)
(d)
for each quarter of the year. But we need to save that information by quarter, and not
by year. So taking a simple example as follows:
YEAR Q1_sales
Q2_sales Q3_sales Q4_sales
---------- ---------- ---------- ---------- ---------2005 10000 15000
14000 25000
we wish to transform the data set to the following with a row for each quarter:
YEAR QTR SALES
---------- -- ---------2005 Q1 10000
2005 Q2 15000
2005 Q3 14000
2005 Q4 25000
Q5
(b)
The first group represents main attributes for the cube and contains data elements to
which we will need to map. Other groups represent the dimensions that are linked to
the cube. As far as the dimensions are concerned we make separate map for them prior
to cube mapping. The data we map for the dimensions will be to attributes in the main
cube group, which will indicate to the cube which record is applicable from each of the
dimensions.
Cube has attributes for surrogate and business identifiers defined for each dimension
of the cube.
All business identifiers are prefixed with the name of the dimension
The name of a dimension is used as the surrogate identifier for that dimension.
Say for example, if SKU and NAME are two business identifiers in PRODUCT
dimension, then the main attribute group will have three PRODUCT related
identifiers; PRODUCT_SKU, PRODUCT_NAME, PRODUCT.
Apart from surrogate and business identifiers, the main attribute group also contains
the measures we have defined for the cube.
What is expression operator? Explain the mapping of a date field SALE_DATE to a
numeric field DAY_CODE by applying TO_CHAR() and TO_NUMBER() functions
through expression operator. The string format for TO_CHAR() function is
YYYMMDD'.
The expression operator represents an SQL expression that can be applied to the output
to produce the desired result. Any valid SQL code for an expression can be used, and
we can reference input attributes to include them as well as functions.
Drag the Expression operator onto the mapping.
It has two groups definedan input group, INGRP1and an output group,
OUTGRP1.
Link the SALE_DATE attribute of source table to the INGRP1 of the
EXPRESSION operator.
Right-click on OUTGRP1 and select Open Details... from the pop-up menu.
This will display the Expression Editor window for the expression.
Click on the Output Attributes tab and add a new output attribute OUTPUT1 of
number type and click OK.
Click on OUTPUT1 output attribute in the EXPRESSION operator and turn our
attention to the property window of the Mapping Editor.
The Properly Window shows Expression as its first property.
Click the blank space after the label Expression.
This shows a button with three dots.
(c)
Validating Objects
The process of validation is all about making sure the objects and mappings we've
defined in the Warehouse Builder have no obvious errors in design.
Oracle Warehouse Builder runs a series of validation tests to ensure that data object
definitions are complete and that scripts can be generated and deployed.
When these tests are complete, the results are displayed.
Oracle Warehouse Builder enables you to open object editors and correct any invalid
objects before continuing.
Validating objects and mapping can be done with the help of Design Center.
Validation of repository objects can be done with the help of Data Object Editor.
Validation of mapping can be done through Mapping Editor.
Generating Objects
Generation deals with creating the code that will be executed to create the objects
and run the mapping
With the generation step in the Warehouse Builder, we can generate the code that
we need to use to build and load our data warehouse.
The objectsdimensions, cube, tables, and so onwill have SQL Data Definition
Language (or DDL) statements produced, which when executed will build the
objects in the database.
The mappings will have the PL/SQL code produced that when it's run, will load the
objects.
Like validation, generation also can be done with the help of Data Object Editor and
Mapping Editor.
(d) What is object deployment? Explain the functions of control center manager.
Q6
Deployment is the process of creating physical objects in the target schema based
on the logical definitions created using the Design Center.
The process of deploying is where the database objects are actually created and
PL/SQL code is actually loaded and compiled in the target database.
During initial stages of design no physical objects have been created in the target
schema.
The operations such as importing metadata for tables, defining objects, mapping
and so on and do forth are performed with respect to OWB Design Center client.
These objects are created as Warehouse Builder repository objects.
So for the actual deployment of object in the target database, we have to use
Control Center Service, which must be running for the deployments to function.
The Design Center creates a logical design of the data warehouse.
The logical design will be stored in a workspace in the Repository on the server.
The Control Center Manager is used for the creation of physical objects into the
target schema by deploying the logical design.
The Control Center Manager is used to execute the design by running the code
associated with the ETL that we have designed.
The Control Center Manager interacts with the Control Center Service, which runs
on the server.
The Target Schema is where OWB will deploy the object to, and where the
execution of the ETL processes that load our data warehouse will take place.
10
(a)
What is recycle bin? Describe the features of warehouse builder recycle bin window.
Q7
(b)
(c)
10
(d)
warehouse or other data sources and loaded in a multidimensional database which looks
like a hypercube. Hypercube is a cube with many dimensions.
What are mapping operators? Explain any two source target mapping operators in
detail.
Mapping operators
These are the basic design elements to construct an ETL mapping. Used to represent
sources and targets in the data flow. Also used to represent how to transform the data
from source to target.
Explain about any two source target operators
(e)
(f)
What are the two ways of validating repository objects in object editor?
Briefly explain various deploy actions of Object Details window.
Following are the two ways to Validate an object from Data Object Editor:
Right-click on the object displayed on the Canvas and select Validate from the popup menu
Select the object displayed on the canvas and then click on the Validate icon from
the toolbar.
Deploy Action: Following are the actions
Create: Create the object; if an object with the same name already exists, this can
generate an error upon deployment
Upgrade: Upgrade the object in place, preserving data
Drop: Delete the object
Replace: Delete and recreate the object; this option does not preserve data
What are the matching strategies for synchronizing workspace objects with its
mapping operator? Explain inbound and outbound synchronization.
Inbound uses the specified repository object to update the operator in our mapping
for matching. It means that the changes in workspace object will be reflected in
mapping operator.
Outbound option would update the workspace object with the changes we've made to
the operator in the mapping. It means that the changes in mapping operator will be
reflected in workspace object
Following are the three matching strategies
Match by Object Identifier
Each source attribute is identified with a uniquely created ID internal to the
Warehouse Builder metadata. The unique ID stored in the operator for each attribute is
exactly same as that of the corresponding attribute in the workspace object to which the
operator is synchronized with. This matching strategy compares the unique object
identifier of an operator attribute with that of a workspace object.
Match by Object Name
This strategy matches the bound names of the operator attributes to the physical names
of the workspace object attributes.
Match by Object Position
This strategy matchs operator attributes with attributes of the selected workspace
object by position. The first attribute of the operator is synchronized with the first
attribute of the workspace object, the second with the second, and so on.