Unable to Login in to OBIEE 11g

• Check whether all the services are up or not.
• Most of the times cluster server will not be up due to which you may see this issue.
• If you are using Windows Environment then try configuring loop back adapter.
• If you are using Windows Environment in Laptop then make sure that before you start the servers wifi is switched of. This is mandatory step because host will be conflicted in case of wifi.
• Check in the logs what are the errors it is throwing.
• Most of the errors will be related to Networking such as Host, Wifi, Environment Variables, Improper shutdown.

If you see any errors in the log file kindly send to me. I will try to help you regarding this.

Unresolved Column in OBIEE 11g

Many of you might have notices this error during their Initial developments. This is one of the many common mistakes we might done during the import.


Odbc driver returned an error (SQLExecDirectW).

A general error has occurred. [nQSError: 27005] Unresolved column:

Primary check what you have to do is to check whether this column is present in your Database or not.

• Open the RPD.
• Right click on the column.
• Select view data.
• If you see that ODBC error here then it would not be present in the database.
• Check the column name again in the database and correct it.

OBIEE Checklist Document

Checklist document is used to validate all the development work that you have done in OBIEE.

This is one of the important document which will let the business know that we have completed and validated all the development.

You can download this file from the below link

http://downloads.ziddu.com/download/25275530/OBIEE_Checklist_Document.rtf.html


Forward me if you have any other versions of the same.

OBIEE LLD - Low Level Design

1. Scope of the project
2. Data source system structure which includes all columns and its details
3. Repository details (Physical layer details, tables and join between tables, BMM Layer details and Presentation Layer Details) and variables and user group details
4. Report Details
5. Users and Security details

OBIEE HLD - High Level Design

1. scope of the project
2. Source database design
3. High level warehouse design ( Star schema /snowflake schema) structure
4. Fact tables and Dimension tables and relation between the tables
4. Oracle BI Distributed architecture
5. Authorization and Authentication Details (User and group)
6. Standard Guidelines

How to set Cache Settings in OBIEE 11g

Enabling Cache:

1. Go to Fusion Middleware Control and log in as weblogic.
2. In the left pane, expand Business Intelligence
3. Click coreapplication.
4. Click Capacity Management.
5. Click the Performance tab.
6. Click Lock and Edit Configuration.
7. Select Cache Enabled.
8. Click Apply to activate the changes.
9. Click Activate Changes.
10. Restart Oracle BI components to apply recent changes.

Modifying Cache Parameters:

Use Fusion Middleware Control to set query cache parameters. You can use Fusion

Middleware Control to set the maximum number of cache entries in the query cache, as

well as the maximum size for a single cache entry.

1. Return to Fusion Middleware Control, which should still be open. If it is not open, enter the http://localhost:7001/em and log in to Fusion Middleware Control as weblogic with password welcome1.
2. In the left pane, expand Business Intelligence.
3. Click coreapplication.
4. Click Capacity Management.
5. Click the Performance tab.
6. Click Lock and Edit Configuration.
7. Change Maximum cache entries from 1000 to 10000.
8. Apply and activate your changes.
9. Leave Fusion Middleware Control open, but do not restart to apply recent changes at this time.

Modifying Cache Parameters Manually

Use NQSConfig.ini to view and manually edit additional query cache parameters.

1. Navigate to D:\bi\instances\instance1\config\OracleBIServerComponent\coreapplication_obis1.
2. Before making changes to NQSConfig.ini, make a copy of the file and paste it in the same directory.
3. Open NQSConfig.ini.
4. Navigate to the CACHE section.
5. Make the following modifications:
6. Modify the MAX_ROWS_PER_CACHE_ENTRY parameter as follows: MAX_ROWS_PER_CACHE_ENTRY = 50000

This parameter controls the maximum number of rows for any cache entry. Limiting the

number of rows is a useful way to avoid using up the cache space with runaway

queries that return large numbers of rows. If the number of rows a query returns is

greater than the value specified in the MAX_ROWS_PER_CACHE_ENTRY parameter,

the query is not cached.

Notice the DATA_STORAGE_PATH parameter. This parameter specifies one or more

directories for query cache storage, and the maximum size for each storage directory.

These directories are used to store the cached query results and are accessed when a

cache hit occurs.

Notice that the MAX_CACHE_ENTRIES parameter is changed to 10000. Changes

made to cache configuration in Fusion Middleware Control are written to this file.

       7. Save and close NQSConfig.INI.
       8. Return to Fusion Middleware Control and restart Oracle BI components.

How to set Logging Level to user in OBIEE

1. Set logging levels for users to allow you to track queries in query logs.
• Select Manage > Identity to open Identity Manager.
• In the left pane, select Identity Management > BI Repository.
• Select Action > Set Online User Filter.
• Enter an asterisk in the field and click OK to retrieve users.
• In the right pane, double-click on the User to open the User properties dialogue box.
• Set the logging level to 2 and click OK.
• Save the repository.