How to Hide or Disable "Create Bookmark Link" in OBIEE? | How to Hide or Disable "Create Prompted Link in OBIEE

The Create Bookmark Link is enabled by default in OBIEE. The following entry in the instanceconfig.xml under the "ServerInstance" node decides the feature of create bookmark link and create prompted link. 

<Dashboard>
<EnableBookmarkURL>True</EnableBookmarkURL>
<EnablePromptedURL>True</EnablePromptedURL>
<BookmarkExpirationDays>30</BookmarkExpirationDays>
</Dashboard>

Inline Prompts in OBIEE 11g

A prompt that is created at the OBIEE analysis level is called an inline prompt. This is referred as inline prompt because the prompt is embedded in the analysis and is not stored in the Oracle BI Presentation Catalog. That means the prompt is created for that particular analysis and therefore cannot be added to other analyses.

Types of Dimensions

Dimension

A dimension table typically has two types of columns, primary keys to fact tables and textual\descriptive data.

Eg: Time, Customer

Types of Dimensions

1. Slowly Changing Dimensions
2. Rapidly Changing Dimensions
3. Junk Dimensions
4. Inferred Dimensions
5. Conformed Dimensions
6. Degenerate Dimensions
7. Role Playing Dimensions
8. Shrunken Dimensions
9. Static Dimensions 

Slowly Changing Dimensions

Attributes of a dimension that would undergo changes over time. It depends on the business requirement whether particular attribute history of changes should be preserved in the data warehouse. This is called a slowly changing attribute and a dimension containing such an attribute is called a slowly changing dimension.

Types of Fact Table

The Types of Fact Table are

1. Snapshot
2. Cumulative
3. Factless Fact Table

Snapshot

This type of fact table describes the state of things in a particular instance of time, and usually includes more semi-additive and non-additive facts. The second example presented here is a snapshot fact table.

Eg: Daily balances fact can be summed up through the customers dimension but not through the time dimension.

Types of Facts

Fact

A fact table typically has two types of columns, foreign keys to dimension tables and measures those that contain numeric facts. A fact table can contain fact’s data on detail or aggregated level.

Eg: Sales, Cost, and Profit

Types of Facts

1. Non-Additive
2. Semi-Additive
3. Additive

Different Types of Logging Levels in OBIEE

Logging Levels	Logging Level Information That Is Logged
Level 0	No logging
Level 1	Logs the SQL statement issued from the client application. Logs the elapsed times for query compilation, query execution, query cache processing, and back-end database processing. Logs the query status like whether it is a success, failure, termination, or timeout. Logs the user ID, session ID, and request ID for each query.
Level 2	Logs everything logged in Level 1. Additionally, for each query, Logs the repository name, business model name, presentation catalog name which is called as Subject Area in Answers. Logs the SQL for the queries issued against physical databases. Logs the queries issued against the cache. Logs the number of rows returned from each query against a physical database and from queries issued against the cache, and the number of rows returned to the client application
Level 3	Logs everything logged in Level 2 Additionally, Adds a log entry for the logical query plan, when a query that was supposed to seed the cache was not inserted into the cache, when existing cache entries are purged to make room for the current query, and when the attempt to update the exact match hit detector fails
Level 4	Logs everything logged in Level 3 Additionally, logs the query execution plan.
Level 5	Logs everything logged in Level 4 Additionally, logs intermediate row counts at various points in the execution plan.
Level 6 & 7	For future purpose

Advantages of using Alias Table in OBIEE

1. OBIEE does not support Circular join in BMM layer, we can overcome this problem by creating alias table for one of the table in that circular join.
2. You can create a join relationship which is different than the actual foreign key relationship in the database. This helps in defining relationships to meet business model criteria.

Why are we creating Alias table?

The following points are the main reasons to create an alias table:

• To reuse an existing table more than once in your physical layer instead of importing it several times.
• To set up multiple tables, each with different keys, names, or joins, when a single data source table needs to serve in different semantic roles. Setting up alias tables in this case is a way or will help us to avoid triangular or circular joins.

What is an Alias Table in OBIEE?

It is a reference to a physical table. Aliases are created in the physical layer of the repository and are an important part of designing a physical layer. An alias table is a physical table that references a different physical table as its source (called the original table).

nQLogViewer in OBIEE

We can use the log viewer utility nQLogViewerto view the query log.Each entry in the query log is tagged with the user ID, session ID and request ID.The User ID will have the details of the user who issued the query, the session ID will have the details of the session in which the query was initiated, and the request ID will have the individual query.

Location of nQLogViewer

• 11g: Oracle_BI_HOME/bifoundation/server/bin/nqlogviewer.

You must run first the bi-init initialization file.

BI-INIT INITIALIZATION FILE: Before running any of the Oracle BI Server command-line utilities, you must now run bi-init.cmd (or bi-init.sh on UNIX) to launch a command prompt or shell window that is initialized to your Oracle instance.

Location of this bi-init initialization file utility:

ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreapplication/setup

• 10g: Oracle_BI/server/bin/nqlogviewer

Syntax

To run the nQlogViewer utility, open a Command window and type nQlogViewer with any combination of its arguments.

The syntax is as follows:

nqlogviewer [-u<user_ID>] [-f<log_input_filename>]

          [-o<output_result_filename>]

          [-s<session_ID>] [-r<request_ID>]

where:

• user_ID

The name of a user in the Oracle BI repository.By using this the user specified in the syntax only can use the query logging. If it is not specified ,all the users for whom query logging is enabled will be shown.

• log_input_filename

The name of an existing log file. This parameter is required.

• output_result_filename

The name of a file in which the output of the log viewer to be stored. If the file exists, results are appended to the file. If the file does not exist, a new file is created. If not specified, output is sent to the monitor screen.

• session_ID

The session ID of the user session.The Oracle BI Server assigns each session a unique ID when the session is initiated. This limits the scope of the log entries to the specified session ID. If not specified, all session IDs are shown.

• request_ID

The request ID of an individual query. The Oracle BI Server assigns each query a unique ID when the query is initiated. This limits the scope of the log entries to the specified request ID. If not specified, all request IDs are show

How to Configure Write Back in OBIEE Report?

Follow the steps, screenshots and other referenced posts to configure write back in OBIEE reports.

Table Properties

First, you should choose a report in Answers to be able to writing back to the database.

1. Go to the Table Component
2. Click on the write back properties icon.Remark that each column have on this head a letter C and a number (Ex. c1, C2, … )

1. Fill the template name with for example:SetWriteBackValue. (This name will indicate later the statement to update or insert in the database)

 

Column Properties

1. Set to “write back” the value integration type of the column you want to be able to update.

Also refer the below mentioned topics to get more knowledge on Write Back.

• Write Back inOBIEE
• How Write BackWorks in OBIEE
• Write-BackTemplate Example in OBIEE
• Write-BackLimitations in OBIEE