Professional Documents
Culture Documents
com,09959531832
1) Database
2) Connection Pool
3) Catalog
4) Schema
5) Physical Table
6) Physical Column
7) Key Columns
Database objects
Highest level object
Primary Key
1) Uniquely identifies a single row of data
2) Comprised of a column or set of columns
3) Set of columns represent a compound or composite key
4) Identified by
Foreign Key
icon
SAMP_TIME_DAY_D=CLAENDER_DATE
Joins In SQL
1. Equi join.
Physical JoinS
1) Equalent to Equi Join
2) Accepts only = operator
3) Most used join in physical Layer
4) Primary Key Foreign Key relationships between tables
5) When you import keys in a physical schema, the primary key-foreign key joins are
automatically defined.
Complex joins
1) a. Equivalent to Non Equi join
2) b. Accepts all operators like (=,<>,=>,,=.etc.)
3) c. Less used join in Physical layer.
4) Complex joins are used to express relationships that do not involve a Primary Key
Foreign Key relationship
Create complex joins
1)
SAMP_REVENUE_F
SAMP_TIME_DAY_D
Step 3:
Select the SAMP_TIME_DAY_D. CALENDAR_DATE column, and then select
SAMP_REVENUE_F.BILL_DAY_DT to join the tables. Ensure that the Expression edit box (at the bottom)
contains the following expression:
. Click OK to close the Physical Foreign Key dialog box. The join is visible in the Physical Diagram.
"orcl".""."BISAMPLE"."SAMP_TIME_DAY_D"."CALENDAR_DATE" =
orcl".""."BISAMPLE"."SAMP_REVENUE_F"."BILL_DAY_DT"
"orcl".""."BISAMPLE"."SAMP_PRODUCTS_D"."PROD_KEY" =
"orcl".""."BISAMPLE"."SAMP_REVENUE_F"."PROD_KEY"
"orcl".""."BISAMPLE"."SAMP_CUSTOMERS_D"."CUST_KEY" =
"orcl".""."BISAMPLE"."SAMP_REVENUE_F"."CUST_KEY"
. Click the Auto Layout button on the toolbar.
13 Select File > Save or click the Save button on the toolbar to save the repository.
.
Click No.
Complex join
Step 1: import tables from SCOTT schema
EMP
DEPT
Step 2 :right click on connection poolimport metadataselect foreign Keys
Step 3:
1.2
Database Types
1.1)
2) A catalog contains all the schemas (metadata) for a physical database object.
3) A schema contains only the metadata information for a particular user or application.
4) Model the Physical layer after the way your data source is structured.
Note the following:
1)
You must create a physical database object before you can create a physical catalog object
or a physical schema object.
2)
After you implement a certain type of grouping, you cannot change it later. For example, if
you decide to implement database > schema > table, you cannot add a catalog afterward.
1) Creating Catalogs
In the Physical layer of a large repository, administrators can create physical catalogs that
contain one or more physical schemas.
To create a catalog:
1. In the Physical layer of the Administration Tool, right-click a physical database and select
New Object, then select Physical Catalog.
was in a separate catalog. You would initialize a session variable named Client, for example,
that could be used to set the name for the catalog object dynamically when a user signs on to
the Oracle BI Server.
You specify the session variable to use in the Dynamic Name tab of the Physical Catalog or
Physical Schema dialog.
Note:
The Dynamic Name tab is not active unless at least one session variable is defined.
To specify the session variable to use in the Dynamic Name tab:
1. In the Name column of the Dynamic Name tab, click the name of the session variable that
you want to use. The initial value for the variable (if any) is shown in the Default Initializer
column.
The name of the variable is displayed in the dynamic name field, and the Select button
toggles to the Clear button.
To remove assignment for a session variable in the Dynamic Name tab:
Click Clear to remove the assignment for the variable as the dynamic name.
The value not assigned is displayed in the dynamic name field, and the Clear button toggles
to the Select button.
You can sort the entries in a column by clicking the Name or Default Initializer column
heading. Clicking a column heading toggles the order of the entries in that column between
ascending and descending order, according to the column type.
Setting Up Display Folders in the Physical Layer
You can create display folders to organize table objects in the Physical layer. They have no
effect on query processing. After you create a display folder, the selected tables appear in the
folder as a shortcut and in the Physical layer tree as an object. You can hide the objects so that
you only view the shortcuts in the display folder
Note:
Deleting a table in a display folder deletes only the shortcut to that object. When you delete a
column in a display folder, however, the column is actually deleted.
To set up a physical display folder:
1. In the Physical layer of the Administration Tool, right-click a physical database and select
New Object, then select Physical Display Folder.
2. In the Physical Display Folder dialog, type a name for the folder.
3. To add tables to the display folder, click Add. Then, in the Browse dialog, select the fact or
physical tables you want to add to the folder and click select.
Alternatively, you can drag one or more physical tables to the display folder after you close
the dialog.
4. Click OK.
Physical Table
TABLE PROPERTIES
1) phsyical
It is a regular phsyicle table which exists in a phsyical database.
here any phsyical object which phsyically exists in database or pshycal database
can be created as a phsyicle type of table.
2) select
in select type of table we can write any valid SQL.
Cache
Table cache property enables query output to be cached and maintained as per cache
persistent time.
We can see more on cache manager
Deploy view
We can see this option enabled for the table which have created with table type select.
By selecting deploy view obiee will create a physical view on database against the
gainst which specified under
Select type database Sql.
Verify Connection
2 . When update row counts completes, move the cursor over the tables and observe that row
count information is now visible, including when the row count was last updated.
3 . Expand tables and observe that row count information is also visible for individual columns.
4 . Right-click a table and select View Data to view the data for the table.
5 . Close the View Data dialog box when you are done. It is a good idea to update row counts or
view data after an import to verify connectivity. Viewing data or updating row count, if
successful, tells you that your connection is configured correctly.
Alias Table
You can change the source table of an alias table, if the new source table is a superset of the
current source table.
1 . It is recommended that you use table aliases frequently in the Physical layer to eliminate
extraneous joins and to include best practice naming conventions for physical table names.
Right-click SAMP_TIME_DAY_D and select New Object > Alias to open the Physical Table
dialog box.
3 . In the Description field, enter Time Dimension Alias at day grain. Stores one record for each
day.
4 . Click the Columns tab. Note that alias tables inherit all column definitions from the source
table.
6 . Repeat the steps and create the following aliases for the remaining physical tables.
SAMP_ADDRESSES_D = D4 Address
SAMP_CUSTOMERS_D = D3 Customer
SAMP_PRODUCTS_D = D2 Product
SAMP_REVENUE_F = F1 Revenue
Key Columns
Primary Key
Uniquely identifies a single row of data
Comprised
Identified by
Foreign Key
icon
Keys tab and Foreign Keys tab of the Physical Table dialog box
Joins
Physical Join
Complex Join
Physical Join
When you import keys in a physical schema, the primary key-foreign key joins are
automatically defined.
Any other joins within each database or between databases have to be explicitly defined to
Right-click one of the highlighted alias tables and select Physical Diagram > Selected Object(s)
Only to open the Physical Diagram. Alternatively, you can click the Physical Diagram button
on the toolbar.
Selected Object(s) Only.
Displays only the selected objects. Joins appear only if they exist between the objects
that you select.
Object(s) and Direct Joins. Displays the selected objects and any tables that join to the
objects that you select.
Object(s) and All Joins.
Displays the selected objects, as well as each object that is related directly or indirectly to the
selected object through some join path. If all the objects in a schema are related, then using
this option diagrams every table, even if you only select one table
4 . You may want to adjust the objects in the Physical Diagram. If so, use the toolbar buttons to
zoom in, zoom out, fit the diagram, collapse or expand objects, select objects, and so forth:
6 . Click the F1 Revenue table and then the D1 Time table. The Physical Foreign Key dialog box
opens. It matters which table you click first. The join creates a one-to-many (1:N) relationship
that joins the key column in the first table to a foreign key column in the second table.
8 . Click OK to close the Physical Foreign Key dialog box. The join is visible in the Physical
Diagram.
Please be aware of the following upgrade considerations for Oracle BI EE 11g Release 1
(11.1.1.5): Joins in the Physical and Business Model diagrams are now represented by a line
with an arrow at the "one" end of the join, rather than the line with crows feet at the "many"
end of the join that was used in previous releases. When creating joins in the Physical and
Business Model Diagrams, you now select the "many" end of the join first, and then select the
"one" end of the join. In previous releases, joins in the diagrams were created by selecting the
"one" end of the join first.
9 . Repeat the steps to create joins for the remaining tables. Use the following expressions as a
guide. Please notice that D4 Address joins to D3 Customer.
"orcl".""."BISAMPLE"."D2 Product"."PROD_KEY" = "orcl".""."BISAMPLE"."F1 Revenue"."PROD_KEY"
12 . Click the X in the upper right corner to close the Physical Diagram.
13 . Select File > Save or click the Save button on the toolbar to save the repository.
14 . Click No when prompted to check global consistency. Checking Global Consistency checks for
errors in the entire repository. Some of the more common checks are done in the Business
Model and Mapping layer and Presentation layer. Since these layers are not defined yet, bypass
this check until the other layers in the repository are built. You learn more about consistency
check later in this tutorial.
15 . Leave the Administration Tool and the repository open for the next topic.
Congratulations! You have successfully created a new repository, imported a table schema
from an external data source into the Physical layer, created aliases, and defined keys and
joins.
In the next topic you learn how to build the Business Model and Mapping layer of a
repository.
Database object
Importing a schema automatically creates a database object for the schema but you need to set
up the database properties.
If you create a database object manually, you need to manually set up all database elements
such as connection pool, tables, and columns.
Allow direct database requests by default (check box)
Allow populate queries by default (check box)
Data Source Definition
CRM Metadata Tables
Database
Virtual Private Database
Persist Connection Pool
Allow direct database requests by default (check box)
1) When checked, allows everyone to execute physical queries.
2) The Oracle BI Server will send unprocessed, user-entered, physical SQL directly to an
underlying database.
3) The returned results set can be rendered in Oracle BI Presentation Services, and then charted,
rendered in a dashboard, and treated as an Oracle BI request.
4) If you want most but not all users to be able to execute physical queries, check this option and
then limit queries for specific users or groups
2) If you want most but not all users to be able to execute POPULATE SQL, check this option
and then limit queries for specific users or groups
A persist connection pool is a database property that is used for specific types of queries
(typically used to support Marketing queries).
2) In some queries, all of the logical query cannot be sent to the transactional database
because that database might not support all of the functions in the query.
3) This issue might be solved by temporarily constructing a physical table in the database and
rewriting the Oracle BI Server query to reference the new temporary physical table.
You could use the persist connection pool in the following situations:
Use to rewrite the logical SQL result set to a managed table. Typically used by Oracle's
Siebel Marketing Server to write segmentation cache result sets.
Perform a generalized sub query.
Stores a nonfunction sub query in a temporary table and then rewrites the original sub
query result against this table.
Reduces data movement between the Oracle BI Server and the database and supports
unlimited IN list values and might result in improved performance.
SQL Features Supported by a Database
1) When you import the schema or specify a database type in the General tab of the Database
dialog box, the Feature table is automatically populated with default values appropriate for
the database type.
2) These are the SQL features that the Oracle BI Server uses with this data source.
3) You can tailor the default query features for a database.
4) For example, if a data source supports left outer join queries but you want to prohibit the
Oracle BI Server from sending such queries to a particular database, you can change this
default setting in the Feature table.
Ask DBMS
A button that is used only if you are installing and querying a database that has no Features
table. It allows you to query this database for Feature table entries
Default
A check box that identifies default SQL features. Default SQL features that are supported by the
database type of the data source are automatically selected.
Find
A button that allows you to type a string to help you locate a feature in the list.
Find Again
A button that becomes available after you click Find. Allows you to perform multiple searches
for the same string.
Revert to Defaults
A button that restores the default values.
Value
A check box that allows you to specify additional SQL features. Select to enable a query type or
clear to disable a query type.
It is strongly recommended that you do not disable the default SQL features.
connection pool
1)
The connection pool is an object in the Physical layer that describes access to the data source.
2) It contains information about the connection between the Oracle BI Server and that data
source.
3) The Physical layer in the Administration Tool contains at least one connection pool for each
database.
4) When you create the physical layer by importing a schema for a data source, the connection
pool is created automatically.
6) Connection pools allow multiple concurrent data source requests (queries) to share a single
database connection, reducing the overhead of connecting to a database.
I had that approach ready i.e to create a read only schema. But which is that i cannot import
from multiple schemas with in a same database. The only situation you use multiple
Connection Pools within the same database is when you want to separate the query's from the
initialization blocks. You use the same credentials for both Connection Pools. The first one is
automatically selected by the query while you point your initialization block to the second one.
Alias Table
Duplicate Table
or circular join