Base Measure, Case when &Filter Using

Base Measure, Case when, Filter Using :

All above 3 methods used to filter the data only, see the bellow difference

ODI - Knowledge Modules Description

                              Oracle Data Integrator 11g Knowledge Modules Description

1. RKM Oracle:
Reverse-engineers tables, views, columns, primary keys, non-unique indexes and foreign keys.

2. JKM Oracle 10g Consistent (Streams):
Creates the journalizing infrastructure for consistent set journalizing on Oracle 10g tables, using Oracle Streams.

3. JKM Oracle 11g Consistent (Streams):
Creates the journalizing infrastructure for consistent set journalizing on Oracle 11g tables, using Oracle Streams.

4. JKM Oracle Consistent:
Creates the journalizing infrastructure for consistent set journalizing on Oracle tables using triggers.

5. JKM Oracle Consistent (Update Date):
Creates the journalizing infrastructure for consistent set journalizing on Oracle tables using triggers based on a Last Update Date column on the source tables.

6. JKM Oracle Simple
creates the journalizing infrastructure for simple journalizing on Oracle tables using triggers.

7. JKM Oracle to Oracle Consistent (OGG):
Creates and manages the ODI CDC framework infrastructure when using Oracle GoldenGate for CDC. See Chapter 26, "Oracle Golden Gate" for more information.

8. CKM Oracle:
Checks data integrity against constraints defined on an Oracle table.

9. LKM File to Oracle (EXTERNAL TABLE):
Loads data from a file to an Oracle staging area using the EXTERNAL TABLE SQL Command.

10. LKM File to Oracle (SQLLDR):
Loads data from a file to an Oracle staging area using the SQL*Loader command line utility.

11. LKM MSSQL to Oracle (BCP SQLLDR)
Loads data from a Microsoft SQL Server to Oracle database (staging area) using the BCP and SQL*Loader utilities.

12. LKM Oracle BI to Oracle (DBLINK)
Loads data from any Oracle BI physical layer to an Oracle target database using database links. See Chapter 17, "Oracle Business Intelligence Enterprise Edition" for more information.

13. LKM Oracle to Oracle (DBLINK)
Loads data from an Oracle source database to an Oracle staging area database using database links.

14. LKM Oracle to Oracle (data pump)
Loads data from an Oracle source database to an Oracle staging area database using external tables in the data pump format.

15. LKM SQL to Oracle
Loads data from any ANSI SQL-92 source database to an Oracle staging area.

16. LKM SAP BW to Oracle (SQLLDR)
Loads data from SAP BW systems to an Oracle staging using SQL*Loader utilities. See the Oracle Fusion Middleware Application Adapters Guide for Oracle Data Integrator for more information.

17. LKM SAP ERP to Oracle (SQLLDR)
Loads data from SAP ERP systems to an Oracle staging using SQL*Loader utilities. See the Oracle Fusion Middleware Application Adapters Guide for Oracle Data Integrator for more information.

18. IKM Oracle AW Incremental Update
Integrates data in an Oracle target table in incremental update mode and is able to refresh a Cube in an Analytical Workspace. See Chapter 21, "Oracle OLAP" for more information.

19. IKM Oracle Incremental Update
Integrates data in an Oracle target table in incremental update mode.

20. IKM Oracle Incremental Update (MERGE)
Integrates data in an Oracle target table in incremental update mode, using a MERGE statement.

21. IKM Oracle Incremental Update (PL SQL)
Integrates data in an Oracle target table in incremental update mode using PL/SQL.

22. IKM Oracle Multi Table Insert
Integrates data from one source into one or many Oracle target tables in append mode, using a multi-table insert statement (MTI).

23. IKM Oracle Slowly Changing Dimension
Integrates data in an Oracle target table used as a Type II Slowly Changing Dimension.

24. IKM Oracle Spatial Incremental Update
Integrates data into an Oracle (9i or above) target table in incremental update mode using the MERGE DML statement. This module supports the SDO_GEOMETRY data type.

25. IKM Oracle to Oracle Control Append (DBLINK)
Integrates data from one Oracle instance into an Oracle target table on another Oracle instance in control append mode.
This IKM is typically used for ETL configurations: source and target tables are on different Oracle instances and the interface's staging area is set to the logical schema of the source tables or a third schema.

26. SKM Oracle
Generates data access Web services for Oracle databases. See "Working with Data Services" in the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator for information about how to use this SKM.

Unable to comminicate with OracleFMW Mapviewer server in OBIEE 11g

While configure Map Data  in Analytics  Page Showing bellow error.

Unable to comminicate with OracleFMW Mapviewer server 

This is problem with IE Browser, change browser and see.

if same error is showing Add bellow tags in instanceconfig.xml file after marketing tags

<SpatialMaps>

<ColocatedOracleMapViewerContextPath>/mapviewer</ColocatedOracleMapViewerContextPath>

<RemoteOracleMapViewerAbsoluteURL></RemoteOracleMapViewerAbsoluteURL> <LayerDataLayout>

<MaxRecords>600</MaxRecords>

</LayerDataLayout>

</SpatialMaps>

Next :)

Upgrading ATG & FSM in DEV_BIACOMP Schema

Hi All,

While configure obia 11.1.1.8.1 showing bellow error

INST-08067: ATG repository version 11.1.1.7.0 is older than minimum required 11.1.1.7.2' error while to do the configuration step of BI apps version 11.1.1.8.1

In RCU  DEV_ BIACOOMP schema installation with old components so we need to upgrade the ATG And FSM.

follow the bellow steps : 

1. Navigate to bellow path 

<Oracle Home>\Oracle_BI1\biapps\tools\lib

2. ATG Upgrade

Run bellow command with 

java -jar biappsrepositoryutil.jar upgradeATG bi.oracle.home=c:/Middleware1/Oracle_BI1/ work.dir=C:\work biacomp.user=DEV_BIACOMP biacomp.password=system123 db.conn.sid.url=Avinash-PC:1521:OBIE atg.db.seed.url=Avinash-PC:1521/OBIE db.sys.user=sys db.sys.password=system123

3. FSM Upgrade : 

java -jar biappsrepositoryutil.jar upgradeFSM bi.oracle.home=c:/Middleware1/Oracle_BI1/ work.dir=C:\work biacomp.user=DEV_BIACOMP biacomp.password=system123 db.conn.sid.url=Avinash-PC:1521:OBIE fsm.db.seed.url=Avinash-PC:1521/OBIE db.sys.user=sys db.sys.password=system123

Here I used  

work.dir=any path(C:/work) and details about DB only.

NQSError 61004

All,

While Trimming OBIA 11.1.1.7.1/8.1 getting bellow error.

NQSError 61004 : Path can't found, that time copy original rpd into bellow path and command again.

<Oracle Home>\Oracle_BI1\bifoundation\server\bin

Thx,

OBIEE 11g - bash_profile in LINUX

Bash Profile in LINUX :

# Using :  User Environment variables while starting the programs.
# Path : /home/oracle   -- Here oracle is user.

# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
        . ~/.bashrc
fi

# User specific environment and startup programs

TEMP=/tmp
TMP=/tmp
ORACLE_BASE=/usr/app/oracle
ORACLE_HOME=/usr/app/oracle/product/11.2.0/client_1
TNS_ADMIN=/usr/app/oracle/product/11.2.0/client_1/network/admin
PATH=$PATH:$HOME/bin:$ORACLE_HOME/bin
LD_LIBRARY_PATH=/usr/app/oracle/Middleware/Oracle_BI1/bifoundation/odbc/lib

export PATH TMP TEMP ORACLE_BASE ORACLE_HOME TNS_ADMIN LD_LIBRARY_PATH

OBIEE 11g - Prompts & Hierarchical Prompts

Hierarchical Prompts : 

• Hierarchical prompts generate selection steps. This impact the report layout as it includes the members that must be shown in the report.

Prompts : 

• Normal prompts generate filters. Filters do not impact the report layout but only the data retrieved from the database.

Hierarchical prompt:

Normal Prompt :

Note : Selection steps are not filters. Hierarchical prompts do not behave like normal prompts. Choose wisely.

Difference Between Filter & Selection Step

All,

Applying filters in reports may seem similar to selection steps.
see bellow image

Filters:
• Are always applied on all views.

Selection Steps:

• Are applied only if the corresponding column is included in the view.
• May generate additional logical and physical queries.

Look at bellow screen shots :

But see what happens when columns are removed from tables -

Next Time ..

Difference Between Group By And Calculated Item

                                                        Group by and Calculated Items

It is important to understand the differences between two types of selection steps: groups and calculated items.

Performance considerations - 

• Calculated items are computed on presentation server. They are executed on the (normally small) result set retrieved from BI Server. Usually they do not have any impact on performance.

• Groups are computed on the database. They generate additional logical and physical queries. They have a significant impact on resources required on the database, and therefore on global Performance.

Functionality perspective - 

• Calculated items formula are exactly applied on result set as they are. Aggregation rules used to compute the metrics on BI Server are not considered.
• Groups generate a query with a filter based on members selected. Aggregation rules are applied on BI Server as usual.

Next Time ..

Canonical Time Dimension in OBIEE

Canonical Time Dimension :

Each Business Model should include a main time dimension connected to almost all fact tables. This is necessary for reports that includes multiple facts. It is also much easier for end-users than having a time dimension per fact table.

OBIEE - Mini-Dimensions

Mini-Dimensions :

1. Mini-dimension tables include combinations of the most queried attributes of their parent dimensions.
2. They must be small compared to the parent dimension,so they can include only columns that have a relatively small number of distinct values.
   

Note : Mini-dimensions are joined both to main fact table and to

aggregate tables.

Used to : 

• They improve query performance because BI Server will often use this small table instead of the big parent dimension.

• They increase the usage of aggregate tables. Due to the level of aggregation, aggregate tables cannot be joined to the parent dimension. But they can be joined to the mini-dimension instead. It allows reports to use the aggregate table even if they use some columns from the corresponding dimension.

NeXt Time ..

OBIEE 11g - Exceeded configured maximum number of allowed output prompts, sections, rows or columns

There are various error messages produced in OBIEE 11g around "Exceeded Configured Maximum Number of ...". In this case we are looking at Output Prompts, Sections, Rows or Columns; which is not very specific.
There are now maximum limits set on the number of columns/rows/etc in a report. Why Oracle have done this I do not know; I have not noticed any change in performance by lowering these limits. The limits need to be applied separately for the different view objects available (i.e. <Table>, <Pivot>, etc).
These limits are set in the instanceconfig.xml file used by the Presentation Services.

 Follow the Linux commands below to locate the file.

Linux Command Prompt
> cd /opt/app/obiee/fmw_home1/instances/instance1 > cd config/OracleBIPresentationServicesComponent/coreapplication_obips1 > cp instanceconfig.xml instanceconfig.xml.original > vi instanceconfig.xml

As demonstrated above I would take a backup of the original, or current version, of the file before making any changes. The default settings are shown below. In the file it is commented that these settings are managed by the Enterprise Manager - ignore these comments.

instanceconfig.xml

... </ODBC> <Views> <Pivot> <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--> <!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery> <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--> <!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><DefaultRowsDisplayedInDownload>2500</DefaultRowsDisplayedInDownload> <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--> <!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><DisableAutoPreview>false</DisableAutoPreview> </Pivot> <Table> <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--> <!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery> <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--> <!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><DefaultRowsDisplayedInDownload>2500</DefaultRowsDisplayedInDownload> </Table> </Views> <Dashboard> ...

Notice that each of the objects has its own subsection within the <Views> section. There are various settings that are applied to each object type. In the update document below I have replaced this entire section. I describe each configuration item below.

After Modify instanceconfig.xml file...

instanceconfig.xml

... </ODBC> <views>   <Cube>     <CubeMaxRecords>10000000</CubeMaxRecords>     <CubeMaxPopulatedCells>100000000</CubeMaxPopulatedCells>   </Cube>   <Table>     <MaxCells>10000</MaxCells>     <MaxPagesToRollOutInDelivery>1000</MaxPagesToRollOutInDelivery>     <MaxVisiblePages>1000</MaxVisiblePages>     <MaxVisibleRows>500</MaxVisibleRows>     <MaxVisibleSections>25</MaxVisibleSections>     <DefaultRowsDisplayed>30</DefaultRowsDisplayed>     <DefaultRowsDisplayedInDelivery>250</DefaultRowsDisplayedInDelivery>     <DefaultRowsDisplayedInDownload>65000</DefaultRowsDisplayedInDownload>   </Table>   <Pivot>     <MaxPagesToRollOutInDelivery>1000</MaxPagesToRollOutInDelivery>     <MaxVisibleColumns>300</MaxVisibleColumns>     <MaxVisiblePages>1000</MaxVisiblePages>     <MaxVisibleRows>500</MaxVisibleRows>     <MaxVisibleSections>25</MaxVisibleSections>     <DefaultRowsDisplayed>30</DefaultRowsDisplayed>     <DefaultRowsDisplayedInDelivery>250</DefaultRowsDisplayedInDelivery>     <DefaultRowsDisplayedInDownload>65000</DefaultRowsDisplayedInDownload>   </Pivot>   <Charts>     <MaxVisibleColumns>2000</MaxVisibleColumns>     <MaxVisiblePages>1000</MaxVisiblePages>     <MaxVisibleRows>2000</MaxVisibleRows>     <MaxVisibleSections>25</MaxVisibleSections>     <JavaHostReadLimitInKB>4096</JavaHostReadLimitInKB>   </Charts>   <Narrative>     <MaxRecords>200000</MaxRecords>     <DefaultRowsDisplayed>30</DefaultRowsDisplayed>   </Narrative> </Views></Views><Dashboard> ...

Cube settings affect the display and processing of data in pivot tables and charts. Cube settings are listed within their own element tags, cube. In this way they are different to other tags that are largely reused between different elements.

<CubeMaxRecords> - specifies the maximum number of records returned for a view to then process. The default is 40,000 records.

<CubeMaxPopulatedCells> - specifies the maximum number of data cells that can be populated in a view; the default is 120,000 cells.

<MaxCells> - specifies the maximum number of cells to be displayed in a view; it must be specified separately for each view type and is applicable to Table and Pivot views. The default is 50,000. The MaxCells should be equal to MaxVisibleColumns (in a pivot view) multiplied by the MaxVisibleRows.

<MaxPagesToRollOutInDelivery> - specifies the maximum number of pages included in a view when it is exposed via a Dashboard; the default is 1000.

<MaxRecords> - Applicable to the narrative view, or ticker, this element specifies the maximum number of records that can be processed to create a view; the default is 40,000.

<MaxVisiblePages> - specifies the maximum number of view prompts (or pages in a PDF) to be displayed for a Chart, Table or Pivot; the default is 1000 Pages.

<MaxVisibleRows> - specifies the maximum number of rows to be displayed in a chart, pivot or table; the default is 500.

<MaxVisibleSections> - specifies the maximum number of sections to be displayed in a chart, pivot or table; the default is 25 sections.

<MaxVisibleColumns> - specifies the maximum number of columns displayed in a chart of pivot table; the default is 300.

<DefaultRowsDisplayed> - specifies the default number of rows to display in a view. It can be applied to a Narrative, Pivot, Table or Trellis; the default is 25. This number should not exceen MaxVisibleRows.

<DefaultRowsDisplayedInDelivery> - specifies the maximum number of rows to display in a view when it is exposed via a Dashboard. Applicable to a Pivot or Table, the default is 100.

<DefaultRowsDisplayedInDownload> - specifies the maximum number of rows included in a view when it is exported, such as a PDF or Excel export. It is applicable to a Pivot or Table and the default is 65,000.

<JavaHostReadLimitInDB> - specifies the maximum amount of data sent to the browser for a chart. It is not relevant to any other view object.

After Modifications must need to restart the presentation services.

Disply previous 3month names

Hi All,

This is Commen requirement, need to disply all last 3months name.

Find bellow steps :

1.Here current month is September, select DATE,Month Names Column.
2. Add Filter convert on SQL on DATE Column
Use bellow query on filter Tab

Time.Date <= cast(current_date as date) and Time.Date >= TIMESTAMPADD(SQL_TSI_MONTH, -2, TIMESTAMPADD( SQL_TSI_DAY , DAYOFMONTH( CURRENT_DATE) * -(1) + 1, CURRENT_DATE))

Here Time.Date is my Dimession Column

3.save and see result.

Finaly Result like this

OBIEE 11g - upgrade 11.1.1.5.x & 6.0 to 11.1.1.7.0

Hi All,

Follow bellow word document steps.

https://docs.google.com/file/d/0BxBUO3DvOkSPd1N6ajdNbkkzMGs/edit


Thx,

Passing presentation variable to prompts in 11g

When we are using Presentation variables, Prompt functionality is very limited. One of those is using
option 'All Column Values'.Here I'm trying to depict a Tip to make use of option 'All Column Values'.
To demonstrate the same here I'm defining a Presentation variable as '' using Page or Dashboard Prompt.

When I select 'All Column Values' we see the report with 'No Results' message as shown below since the criteria is not set properly

Use the below case statement to so that the condition matches as shown in the image
<COLUMN> LIKE (CASE WHEN '@{U}{}'='' THEN '%%' ELSE '@{U}' END)

On the Dashboard page, the prompt with option 'All Column Values' is selected and the report results are as below

Till Next Time.....

NQLogViewer in OBIEE

We can use the log viewer utility nQLogViewer to 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:

In 11g : Oracle_BI_HOME/bifoundation/server/bin/nqlogviewer.
Note : 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:
In 11g : ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreapplication/setup
In 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>]

Here :

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

11.1.1.7.1 Patch Set Released

The Business Intelligence Enterprise Edition 11.1.1.7.1 patch set has been released (currently only for 32- and 64-bit Linux and Windows), and is available to download from My Oracle Support (https://support.oracle.com/).

Per the patch readme:
This patch set is available for all customers who are using Oracle Business Intelligence Enterprise Edition 11.1.1.7.0.

The Oracle Business Intelligence 11.1.1.7.1 patch set is comprised of the following patches: 
Patch 16453010 - Patch 11.1.1.7.1 (1 of 6) Oracle Business Intelligence Installer (BIINST)
Patch 16849017 - Patch 11.1.1.7.1 (2 of 6) Oracle Business Intelligence Publisher (BIP)
Patch 16916026 - Patch 11.1.1.7.1 (3 of 6) Enterprise Performance Management Components Installed from BI Installer 11.1.1.7.0 (BIFNDNEPM))
Patch 16850553 - Patch 11.1.1.7.1 (4 of 6) Oracle Business Intelligence Server (BIS)
Patch 16842070 - Patch 11.1.1.7.1 (5 of 6) Oracle Business Intelligence Presentation Services (BIPS)
Patch 16869578 - Patch 11.1.1.7.1 (6 of 6) Oracle Business Intelligence Platform Client Installers and Map Viewer
Also you must download
Patch 16569379 - Dynamic Monitoring Service patch

Note : OBIEE 11.1.1.7.1 patch set is available as patch 16556157. Unzipping this patch will give you the six patches listed above.

Till Next Time....

New BI Mobile Features in 11.1.1.7

14) Maximize views with double-tap gesture:

With this new feature, you can access on your iPad more data—even within dense dashboards—without the restrictions of the smaller form factor. You expand an individual view by double-tapping on it. The individual view then displays within the full screen of the iPad. This maximizing of views can be done on views accessed within a dashboard, and also when viewing an analysis independent of a dashboard. See "Working with Analyses and Dashboards."

15) New view and graph types:
The following new graph types are supported with BI Mobile: Performance tiles, Waterfall graphs, 100% stacked graph, Stacked graph

16) Fixed headers:

In analyses with fixed headers, you can use a single-finger drag gesture to scroll through data in all directions

17) Changing Orientation:

It is now possible to change between landscape and portrait orientation while viewing Oracle BI content.

18) Breadcrumbs:

You can see the navigation path you have taken while moving through the catalog as a trail of breadcrumbs (near the top of the screen by the Back arrow). In this way, you can see your current location and how you got there, then decide whether to use the Back arrow to navigate in reverse, or to use the Home icon to quickly return to the Home screen

19) Security toolkit:

The Oracle Business Intelligence Mobile Security Toolkit provides the ability to generate a signed version of the Oracle BI Mobile HD application. The toolkit includes the instructions and necessary content to build this application making use of Apple's Xcode and the IOS SDKs. The Oracle BI Mobile Security Toolkit will be updated on a regular basis in order to synchronize with the Oracle BI Mobile HD application available on the Apple App store. See "Using the Security Toolkit for Mobile Device Management."

20) Viewing of Oracle BI Publisher reports in dashboards

21) Integrated Full-Text Catalog Search:

As in the desktop version of Oracle BI EE, you can use full-text search to find catalog objects in Oracle BI Mobile based on attributes such as author and column name. This search is available after the administrator integrates Oracle BI Enterprise Edition with Oracle Endeca Server

New Features with OBIEE 11.1.1.7

The list covers new features for BI Presentation Layer, BI Mobile, BI Server, Server Administrators and BI Publisher. If you notice any other additional 11.1.1.7 features then please post a comment at the bottom ... :)

Presentation Services Features :

1) Recommended Visualizations Feature for Creating Views:

• When you create a view, you can choose a recommended view type based on the data in your analysis and, optionally, what you want to use it for (for example, to analyze trends).
• You can choose a suggested "Best Visualization" as well as a "Recommended Subtype". Or you can instead choose the "Recommended Visualization" option, for which you specify your intent for the new view.

2) Breadcrumbs :

• Breadcrumbs have been added to help users understand their current location within Oracle BI content and the path that they have used to navigate 
• Oracle BI Breadcrumbs display at the bottom of the page, and users can click a breadcrumb or the breadcrumb overflow button to navigate to a specific location on their breadcrumb trail.

3) Enhancement to Dashboards:

• The ability to create custom print layouts for high-fidelity printing of dashboard pages (i.e. automatic creation BI Publisher reports)
• A new default style called FusionFX (instead of "blaf")
• The addition of the Freeze Column option to the Column Properties menu. This option allows you to freeze a column at an edge (top or left) of a dashboard layout.
• The addition of "Size" and "Page Size" options that allow you to control the position and size of columns and sections.
• The ability to export an entire dashboard or a single dashboard page to Microsoft Excel 2007+
• A new "Replace Analysis in <Dashboard>" option added to Answers to replace an analysis on a dashboard.
• A new "Return to <Dashboard>" option within Answers to return to a dashboard from the Analysis editor.

4) Enhancements to Graphs

 In 7.0 comeing with Three New graph Views
 a) Waterfall graph,
 b) Stacked graph,
 c) 100% Stacked graph (the latter two are subtypes of Bar and Area graphs)
New Options :
Zoom to data range :- This option lets the system evaluate the range of values on an axis, and choose appropriate minimum and maximum values for the scale. This is useful when graphing a set of large values that are all within a small percentage of each other
Hide sliders in graph views that listen to master-detail events: For graphs in master-detail relationships, if you want to simplify the appearance of an analysis or dashboard, you can hide the slider that is created to accommodate detail columns.

5) Enhancements to Views :

• A new view type named performance tile. This view type displays a single aggregate measure value in a manner that is both visually simple and prominent.
• Action links in trellis views. In simple trellis views, action links can now be used on inner graphs per unit, including the context of the outer edges. Action links can also be used in legends and in axis labels. In advanced trellis views, action links can be used in micro charts, where the micro chart functions as a single unit (such as an aggregate number), including the context of the outer edges.
• For map views, you can now vary the width of a line by measure to accentuate a feature
• You can link a map view as a detail in a master-detail relationship
• Auto Correct option for Map views (as errors in Map views can occur for various reasons). If the issue appears to be related to missing layers, maps, or styles, then it might be possible to correct the map by replacing the missing map view components with similar items that exist in the spatial metadata 
• Legend and formatting highlighting
• Null suppression at view and analysis levels. You can set null suppression options at the view level (which overrides the analysis level) for data views including: table, pivot table, trellis (both simple and advanced), graph, gauge, and funnel views when the entire row or column contains nulls.
• Ability to include or exclude calculated items and groups at the view level for columns and column headers. Specifically, two new options have been added: Include Custom Member and Exclude Custom Member

For tables, pivot tables, and advanced trellises:

• The ability to ◦specify the method to be used to browse data — either scrolling or paging controls
• Re size rows and columns
• Row count. If your table or pivot table view contains a grand total or subtotal on the row edge, the display totals, that is the grand total and subtotals, are now included in the Rows per Page count for content paging. In prior releases, if you had the Rows per Page count set to 10 for example, the table or pivot table would display more than 10 records if display totals were shown in the view results
• For right-click interactions, the ability to specify whether the Hide Columns interaction is available at run time.

6) Enhancements to Prompts:

• This release includes an enhancement to the SQL Results prompt option. If you are working with double columns, you can now write the SQL statement so that filtering is done on code values rather than display values
• An enhancement to the prompt constraint option. The prompts designer can now limit a column prompt value list by more than one column
• This release includes enhancements to the parameters for prompted links.

7) New Menu Options for Exporting Views and Results:

This release adds the Excel 2007+ and Powerpoint 2007+ options for exporting views and results

8) Total Member Placement for Hierarchical Columns:

This release includes an enhancement that allows placement of total members on a hierarchy.

9) Browse Catalog Search Results by Object Attributes:

The capability to use full-text search to find catalog objects and then filter the search results by attributes. This search is available when the administrator integrates Oracle BI Enterprise Edition with Oracle Endeca Server. After the full-text search results are returned, the Catalog area displays a list of matching items, and the Search pane displays the search results grouped by attribute (that is, Type, Name, Path, and Created By)

10) Navigate from the Total or Grand Total in a Table or Pivot Table:

If an analysis contains a total or grand total and the associated attribute or hierarchical column contains an action link or a conditional action link, the action link (or conditional action link) is applied to both the column and the total or grand total.

11) New BI Desktop Tools Available for Download:

• Oracle Hyperion Smart View for Office
• Oracle Hyperion Financial Reporting Studio (if Essbase is installed)
• Oracle Essbase Studio Console (if Essbase is installed)
• Oracle Essbase Administrative Services Console (if Essbase is installed)

12) Enhancement to Favorites:

This release provides the capability to organize your favorites from the Category Tree area and the Selected Category area in the Manage Favorites dialog. In previous releases, you could organize favorites from the Category Tree area.

13) Integration of Oracle BI EE with Oracle Enterprise Performance Management System

With this release, OBIEE is integrated with Enterprise Performance Management Work space (as part of the installation process)

New BI Mobile Features

Till  To Next Time .. !!!

OBIEE 11g - Change the Rpd Password

Hi All,

One utility is Available in 11.1.1.7.0 to change the Rpd password by command line. 

Follow these steps to change the repository password using the obieerpdpwdchg utility, and then deploy the modified repository in Fusion Middleware Control:

1.Run bi-init to launch a command prompt.

Find the Location of the bi-init

A) Client installations : ORACLE_HOME/bifoundation/server/bin
B) Other all installations : ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreapplication/setup

 Double-click bi-init.cmd (or bi-init.bat for client installations) to display a command prompt that is initialized to your Oracle instance.

2. At the command prompt, type obieerpdpwdchg with the following arguments:

• -I name_and_path_of_existing_repository
• -O name_and_path_of_new_repository          

Then, enter the current (old) password and the new password when prompted. The repository password must be longer than five characters and cannot be empty. For example:

obieerpdpwdchg -I E:\SampleAppLite.rpd -O E:\New_SampleAppLite.rpd

Give password for repository: Admin123

Give password for repository: <new Password>

       Note that passwords are masked on the command line unless you include the -C option in the command to disable masking.

3. Open a Web browser and log in to Fusion Middleware Control from the computer where the updated repository is located.
4 .In the navigation tree, expand Business Intelligence and then click coreapplication to display the Business Intelligence Overview page.
5. Display the Repository tab of the Deployment page.
6. Click Lock and Edit Configuration.
7. Click Browse next to Repository File. Then, select the updated repository file and click Open.
8. Enter the new (updated) repository password in the Repository Password and the Confirm Password fields.

Make sure to specify the password that has been set in the repository. If the passwords do not match, the Oracle BI Server fails to start, and an error is logged in nqserver.log.

9. Click Apply, then click Activate Changes.
10. Return to the Business Intelligence Overview page and click Restart.