How can you change the default port number for OBIEE 10g?

Follow these steps and change the port in OBIEE 10G :

1. Open the file named default-web-site.xml in \OracleBI\oc4j_bi\j2ee\home\config and change the port value.

2. Change the port in OracleBI\oc4j_bi\j2ee\home\applications\bioffice\bioffice\WEB-INF\bioffice.xml file.

3. Change the port in OracleBI\xmlp\XMLP\Admin\Configuration\xmlp-server-config.xml.

4. Change the port in OracleBIData\web\config\instanceconfig.xml.

5. After the changes re-start OC4J for the changes to take effect.

Before making any changes back up the files mentioned above.

Reference Document: https://support.oracle.com/epmos/faces/DocumentDisplay?id=1073934.1

https://support.oracle.com/epmos/faces/DocumentDisplay?id=759312.1

Steps to Set Up Usage Tracking and Create Usage Reports

The Oracle BI Server supports the collection of usage tracking data. When usage tracking is enabled, the Oracle BI Server collects usage tracking data for each query, and it writes statistics to a usage tracking log file or inserts them directly into a database table.

It is strongly recommended that you use direct insertion instead of writing to a log file. The Oracle BI Summary Advisor feature works in conjunction with the usage tracking feature. Summary Advisor works only with direct insertion usage tracking. Oracle BI Summary Advisor is available when you are running Oracle Business Intelligence on the Oracle Exalytics Machine.

Link to Steps to setup Usage Tracking : https://support.oracle.com/epmos/faces/DocumentDisplay?id=1539971.1

Should The OBIEE 11g Catalog Manager Be Able To Open On Linux / Unix?

This applies to OBIEE 11g (11.1.1.3) and greater versions. Start the Catalog Manager via the following commands:

Using the command line, change to the following directory:

ORACLE_INSTANCE\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obipsn\catalogmanager

then run the appropriate script:
runcat.cmd (on Windows)

runcat.sh (on UNIX)

Currently, the Catalog Manager gui will not run on other Unix environments (i.e. AIX, Solaris, HP-UX) due to plugin limitations.  It will however run in "light" or command-line mode.

See
./runcat.sh -help
for more information.

For more help on any one of these commands, please enter:

runcat.cmd/runcat.sh -cmd <command> -help

Reference Documents:

MetalinkNotes:  https://support.oracle.com/epmos/faces/DocContentDisplay?_afrLoop=64739792296937&id=1412163.1

Find the Status of the iBot Develiry through Back-End Table

The scheduler tables are used by Oracle Delivers and are populated with information from the Scheduler jobs. The tables are:

Table Name	Table Description
S_NQ_JOB	This table is used by Scheduler to store information about scheduled jobs
S_NQ_INSTANCE	The S_NQ_INSTANCE table stores information about scheduled job instances
S_NQ_ERR_MSG	This table stores error messages for Scheduler job instances that do not complete successfully.
S_NQ_JOB_PARAM	This table holds information about Scheduler job parameters for scheduled jobs

We can check STATUS from S_NQ_INSTANCE table, which can have different values....

STATUS =0 Completed
STATUS =1 Running
STATUS =2 Failed
STATUS =3 Cancelled
STATUS =5 Timedout

Location of the Log

OracleBI_Home\server\Log\iBots

Following query will give us a list of ibots failing since previous day.  

select STRING_AGG( DISTINCT(J.name)) AS FAILING_IBOTS
from s_nq_job j, 
s_nq_instance i
where j.job_id = i.job_id
and i.status in (2,4)
and (i.begin_ts - 8/24) > trunc(sysdate) - 1;

-Asifkhan P.

How To Send iBot To Non-OBIEE

It is not possible in OBIEE 10g (10.1.3.4.1) as the needed functionality does not exist.

However, it is possible in 11g as this was a highly requested feature that was added. Oracle BI 11g allows agents to send non-personalized content to any email address (typically a user who is outside of the BI system). There are still licensing requirements for users who will be creating agents or using the Delivers functionality in OBIEE.

Reference Document:

Metalink Note: https://support.oracle.com/epmos/faces/DocumentDisplay?id=1209501.1

OBIEE 11G New Features (Reports&Dashboards)

1. REQUESTS are renamed as ANALYSIS. 2. IBOTS are renamed as AGENTS. 3. CHARTS are renamed as GRAPHS. 4. Map view is instroduced. 5. Presentation variables can hold multiple values. 6. KPI's and SCORECARD's are introduced. 7. ACTION LINKS, MASTER-DETAIL reports, SELECTION STEPS are introduced. 8. Selection and Groups are introduced. 9. Interaction tab is introduced. 10. Breadcrumbs have been added to help users understand their current location within Oracle BI content. 11. Ability to export an entire dashboard or a single dashboard page to Microsoft Excel 2007+ 12. Slider Dashboard Prompts. 13. Trellis Chart Creation 14. Waterfall Chart 15. Column Format --> Contains HTML markup 16. Selection Steps View

OBIEE 10g and 11g: Support and Certification of Internet Explorer Browser Version

Today one of our user had issue while access analytics using IE9, then finally found that IE9  is not going to support for OBIEE 10.1.3.4.1.  IE9 will supports only OBIEE 10.1.3.4.2 or higher version. So just wanted to share support and certification information.

• Internet Explorer 6 :
  Currently, this is only supported with OBIEE 10g.
• Internet Explorer 7 :
  Currently, this is supported with OBIEE 10g and OBIEE 11g  (11.1.1.3.0 and onwards).
• Internet Explorer 8 :
  Currently, this is supported with OBIEE 10g (10.1.3.4.1.and onwards) and OBIEE 11g  (11.1.1.3.0 and onwards).
• Internet Explorer 9 :
  Currently, this is only supported with OBIEE 10.1.3.4.2 and OBIEE 11.1.1.6.0.
• Internet Explorer 10 :
  Currently, this is supported with OBIEE 10.1.3.4.2 and OBIEE 11.1.1.7.1 and later.
• Internet Explorer 11 :
  Currently, this is not supported with either OBIEE 10g or OBIEE 11g.

Reference links:

• Metalink note for reference : https://support.oracle.com/epmos/faces/DocumentDisplay?id=1347987.1 
• System Requirements and Supported Platforms OBIEE 10.1.3.3, 10.1.3.4 : http://docs.oracle.com/cd/E10415_01/doc/bi.1013/e10417.pdf

OBIEE 11G New Features (RPD)

1. Hierarchy object introduced in Presentation layer . 2. Join is done from FACT to DIMENSION. 3. 11g displays COLUMN NAMEs along with table names in mappings. 4. New time series functions PERIOD ROLLING and AGGREGATE AT is instroduced. 5. AGGREGATE PERSISTENCE WIZARD creates indexes automatically. 6. PARENT CHILD, UNBALANCED (RAGGED,SKIPPED) HIERARCHY are instroduced. 7. Repository has password. 8. Dedicated connection pool need for initialization blocks in 11g. In 10g, we can use any connection pool. 9. Now Repository version will be automatically maintains. 10. You can now generate an XML patch file that contains only the changes made to a repository. 11. LTS priority ordering. 12. ID columns for Descriptive Columns. 13. Lookup Logical Tables.

OBIEE 11G New Features (Security)

1. USERS and GROUPS are created in Weblogic. 2. Groups no longer exist and are replaced by Application roles. Data level security is implemented by using Application roles to which users belong to. 3. In Presentaion Catalog, AuthenticatedUser role is used instead of Everyone group. 4. Application roles are managed in an external policy store. Application role objects exist in the repository, but these objects are pointers (references) to the externally managed roles. 5. Users are managed in an external authentication provider and are no longer managed in the repository. User objects exist in the repository, but these objects are pointers (references) to the externally managed users. 6. In 11g any named user can be granted administrative permissions if desired. This compares to 10g where there was a single user with administrative permissions who was named Administrator. 7. Security Policies are now mapped to Application roles not to Groups. 8. No more Administrator User. -Any number of users have admin privileges.

OBIEE 11G New Features (Installation)

1. Repository Creation Utility(RCU) is used for creating repository. 2. Oracle WebLogic Server replaces Oracle Application Server and Oracle Containers for Java (OC4J). 3. Supports IBM WebSphere (11.1.1.7) 4. Many configuration settings can be done using EM. 5. BI Composer is automatically installed and configured 6. Oracle Business Intelligence 11g Installer includes ONLINE HELP for each installation screen. 7. Oracle Business Intelligence Uses New Command Line Utilities(WLST, OPMN)

OBIEE Performance tuning

• Connection Pools

How to decide on Connection Pool Number
– Maximum number of connections in a connection pool : 20% of concurrent users
* number of reports per dashboard.
– How Connection Pool can improvise Performance
– Create dedicated connection pools for your Session Variables.
– Create dedicated connection pools for your report queries.
– Always use OCI Call Interface in the rpd if your backend db is Oracle
– Using ODBC for the Oracle RDBMS Connection can degrade performance
– DB tracing
– ODBC tracing is enabled to troubleshoot ODBC issues. This can cause huge
 performance problems. This is not indicated in any OBI logs.

• Setting the NQSConfig.ini parameters

– Setting following NQSConfig.ini parameters that can affect OBI performance
– SORT_MEMORY_SIZE: specifies the maximum amount of memory to be used for each sort operation
– SORT_BUFFER_INCREMENT_SIZE: specifies the increment by which the sort memory is increased as more memory is needed
– VIRTUAL_TABLE_PAGE_SIZE: specifies the size of a memory page for OBI internal processing
– There are some more parameters which can help/effect the performance
– SERVER_THREAD_RANGE
– SERVER_THREAD_STACK_SIZE
– DB_GATEWAY_THREAD_STACK_SIZE
– MAX_SESSION_LIMIT
– MAX_REQUEST_PER_SESSION_LIMIT
– BUFFER_POOL_SIZE
– MAX_CACHE_ENTRY_SIZE
– DATA_STORAGE_PATHS
– INIT_BLOCK_CACHE_ENTRIES
• Periodcally check performance monitoring using..
        - http://<host url>:<port number>/analytics/saw.dll?perfmon

• Use of “filter By” Option compared to “Case When”
• Always specify the number of elements per level. BI Server will use it to identify
  aggregate tables and mini dimensions. It does not need to be accurate, a rough estimate is fine.
• Exposing materialized views in Physical layer
• Deploying SSL will have a level of overhead on the overall performance
• Formatting of reports has overhead on the system verse executing HTML based reports only (i.e. Dashboards)
• Turning off logging
• Setting query limits
• Pushing calculations to the database
• Using database hints
• Infrastructure sizing
• Using aggregates
• Constraining results using a WHERE clause
• Limiting the number of initialization blocks
• Caching (Last Resort)
• Depending on your configuration, enable some parameters in database feature:
• Always specify the content level in all logical table
• Delete Unused Views from Presentation Layer
• Do not overuse dashboard conditions, it has a cost on performance.
• Dashboard should be as interactive as possible:
– column selectors,
– Contextual drill-down,
– guided navigation
• Using aggregates
– Enabling OBI to generate queries against smaller, summarized tables
• Constraining results using a WHERE clause
– Limiting the rows returned from a data source
• Caching
– Fulfilling a query from a local cache as opposed to processing the query through a data source
• Limiting the number of initialization blocks
– Initialization block queries are executed when OBI is started and when users log in
• Turning off logging in production
         – No overhead for OBI to generate log files
• Setting query limits
         – Enabling OBI to track and cancel runaway queries
• Pushing calculations to the database
– Automatically pushing certain operations to the database based on database feature entries
• Exposing materialized views in Physical layer
– Guarantees to choose the most economical table source to satisfy a query
• Using database hints
– Forcing the database query optimizer to execute the statement in a more efficient way
• Network Issues
– Any network issues. It may be necessary to enable network tracing tools, if you suspect problems with slow network.
• Other Factors
– Sizing of the OBI servers is an important part in implementations when the number
 of users and the complexity of the dashboards/reports is significant. It may be
 necessary to involve infrastructure Admin to get a sizing review for large
 implementations.
– The size of the RPD and webcatalog may affect start up times of the services. It is
 recommended to clean up the RPD and webcatalog to remove redundant objects.
– Sometimes ODBC tracing is enabled to troubleshoot ODBC issues. This can cause
 huge performance problems. This is not indicated in any OBI logs.
– When analyzing the NqQuery.log, if the Physical SQL is taken a lot of time,
 performance tuning needs to be done on the database.
– Oracle Database features like proper indexing , partitioning and Star
 Transformations can help performance to a great extent.
• RPD considerations
– The RPD should be designed according to best practices.
– De-normalize dimensional objects, combine several dimensional attributes into
 one flat table. This will help reduce joins.
– Model your physical tables in a way that should help in creating simpler Business Models.
– Use Aggregate Tables when necessary to help better performance.
– Aggregate tables will need additional ETL, storage and complex mapping efforts.
– The size of the RPD may affect start up times of the services
• Complex Calculations
– It may be better to move complex calculations to ETL for performance reasons.
– If customers have complex logic that involves complex SQL, it is a good idea to
 consider pushing this logic to ETL rather than handling it in the RPD at the run time
• Avoid Cross-database joins
– Cross-database joins or “federated queries” can be expensive in terms of
 performance when compared to joins within the same database. For cross-database
 joins, tables are normally loaded into memory, and then joined.
• Caching (THE LAST RESORT)
– Caching can be very helpful in alleviating performance issues for complex queries
 that are reused many times.
– iBots can be used to seed queries during off peak hours to achieve performance.
• DBFeatures
– If one of the dbfeatures is turned off, improper SQL may be generated by OBI.
– Improper SQL may cause performance degradation
• Control long running queries
– Set certain timeout parameters in the RPD
• Use a default value for the prompts in dashboards.
– This will make sure that the reports will return a smaller result set
– If this is not possible to do due to the business requirements
• Consider adding some links on the dashboard page for reports.
• If the query ran quickly in the NqQuery.log, then Presentation services may be taking
  more time to display the results.
– If you have a significant number of Charts or Pivot table views for the reports.
– Changing the existing reports to Table view could help performance
• Too many pivot tables and charts on a dashboard page can make the UI very slow
• Check for hidden sections and guided navigations that will run always.
• Make sure the logconfig.xml file is not modified to get enhanced logging. This is not
  recommended in production systems.
• SQL request contains Non-cacheable element Current_Timestamp, Current_Time, Rand,
  Populate, or a parameter marker then it is not added to the cache
• Result set is too big. MAX_ROWS_PER_CACHE_ENTRY and MAX_CACHE_ENTRY_SIZE
  parameters in nqsconfig.ini limit the max rows and max size for cache
• Oracle BI Server is clustered.
• Caching cannot be used for constrained Prompts.
• If session variables are used, caching will not work since this results in the cache being
  specific to a user.
• ORDER BY clause made up of columns in the select list. Queries that order by columns
  not contained in the select list result in cache misses.
• Cache entries become specific to users depending on the way data-level security is
  setup in the RPD.
• The logical query has an additional column as compared to the seeded query.

OBIEE 11g: Bugs Fixed in 11.1.1.7.1

Oracle Support Document 1566140.1 (OBIEE 11g: Bugs Fixed in 11.1.1.7.1 ) can be found at: https://support.oracle.com/epmos/faces/DocumentDisplay?id=1566140.1

OBIEE 11g: Bugs Fixed in 11.1.1.7.0

Oracle Support Document 1546028.1 (OBIEE 11g: Bugs Fixed in 11.1.1.7.0 ) can be found at: https://support.oracle.com/epmos/faces/DocumentDisplay?id=1546028.1

How To Start / Stop An OBIEE 11g (11.1.1.x) Unix / Linux Environment Via Command-line

This post will describe one method to start and stop an Oracle Business Intelligence Enterprise Edition (OBIEE) 11g (11.1.1.x) environment on the Linux/Unix platform via the command-line. 

The high-level manual steps are:

• Set your environment
• Start WLS Admin Server in the background
• Start WLS NodeManager
• Start WLS Managed Server
• Start Oracle Instance (system components managed by OPMN)

1. Set your environment (manually or via script). 

MW_HOME=/[path]/[obiee11g_middleware_home]; export MW_HOME
DOMAIN_HOME=/$MW_HOME/user_projects/domains/bifoundation_domain; export DOMAIN_HOME
WL_HOME=$MW_HOME/wlserver_10.3; export WL_HOME
ORACLE_HOME=$MW_HOME/Oracle_BI1; export ORACLE_HOME
ORACLE_INSTANCE=$MW_HOME/instances/instance1; export ORACLE_INSTANCE
#
# You may also want to set your PATH environment to avoid having to use
# paths in the commands
#
PATH=$WL_HOME/server/bin:$DOMAIN_HOME/bin:$ORACLE_INSTANCE/bin:$ORACLE_HOME/OPatch:$PATH; export PATH

2. Start the WebLogic (WLS) Administration Server in the background.

nohup sh $DOMAIN_HOME/bin/startWebLogic.sh -Dweblogic.management.username=weblogic -Dweblogic.management.password=[_your_password_] > wls_start.log &

Next, tail the log to determine if the server started completely.
execute:
tail -f [log name]
wait until you see:
<WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

 there should be no further lines after this. If successful,  proceed to step 3. If errors, correct them and restart.

3. Start Node Manager 

nohup sh  $WL_HOME/server/bin/startNodeManager.sh > startNodeManager.log &

Next, tail the log to determine if the server started completely. 
tail -f [log name]

Look for <INFO> <Secure socket listener started on port 9556>

4.Start the OBI Managed Server (bi_server1 -- default  - java bits)

nohup sh $DOMAIN_HOME/bin/startManagedWebLogic.sh bi_server1 http://server.domain:7001 > start_bi_server1.log &

Next, tail the log to determine if the server started completely. 

tail -f [log name]
look for "Server started in RUNNING mode: 

<Mon D, YYYY H:MM:SS PM EDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "wls_ods1" for domain "IDMDomain" running in Production Mode>
<Mon D, YYYY H:MM:SS PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Mon D, YYYY H:MM:SS PM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode

5. Start the OBIEE System Components ( BI Servers -- c++ bits)

$ORACLE_INSTANCE/bin/opmnctl startall

Next, execute:  opmnctl status or opmnctl status -l (lower case L) to ensure the processes are started properly/completely. 

The output will look similar to this:

$ORACLE_INSTANCE/bin/opmnctl status -l

Processes in Instance: instance1
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ias-component | process-type | pid | status | uid | memused | uptime | ports
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
coreapplication_obiccs1 | OracleBIClusterCo~ | 11741 | Alive | 70916792 | 55188 | 0:01:01 | N/A
coreapplication_obisch1 | OracleBIScheduler~ | 11740 | Alive | 70916789 | 122388 | 0:01:01 | N/A
coreapplication_obijh1 | OracleBIJavaHostC~ | 11739 | Alive | 70916790 | 1186088 | 0:01:01 | javahost:9810
coreapplication_obips1 | OracleBIPresentat~ | 11742 | Alive | 70916791 | 261576 | 0:01:01 | N/A
coreapplication_obis1 | OracleBIServerCom~ | 11738 | Alive | 70916788 | 150904 | 0:01:01 | N/A

Stopping the enviroment cleanly via the command-line:

Reverse the steps above with the following commands:

1. Stop the Oracle Instance
   
   $ORACLE_INSTANCE/bin/opmnctl stopall
2. Stop the OBIEE Managed Server (bi_server1)
   
   $DOMAIN_HOME/bin/stopManagedWebLogic.sh bi_server1 t3://host.domain:7001 username password
   If running other managed servers, then stop them in the same manner.
3. Stop the the WebLogic (WLS) Administration Server
   
   $DOMAIN_HOME/bin/stopWebLogic.sh username password t3://host.domain:7001
4. At this point, since the node manager was started in another shell in the background, then you will need to kill the JVM process that the node manager is running under. There should be no risk of corruption at this point since everything is already shutdown.  If you had started the node manager in a shell (and not in the background), then you could just close the shell.
   
   You can use the command ps -ef | grep [os user] to check for running processes under the specified user and then kill the JVM process with kill -9 [PID] (where PID is the process id of the running JVM)

Manual start/stop OBIEE 10g services in linux/unix

Here how you can stop and start OBIEE 10g services.

TO STOP:

cd <>/OracleBI/setup/
./run-sa.sh stop -----------------stopBI server
./run-saw.sh stop----------------stop Presentation server
./run-sch.sh stop---------------- stop Schedular
./run-ccs.sh stop----------------- stop Cluster Controller

TO START:

cd <>/OracleBI/setup/
./run-sa.sh start--------------to start BI server
./run-saw.sh start-------------to start Presentation server
./run-sch.sh start----------to start Schedular
./run-ccs.sh start----------to start Cluster Controller

OBIEE 11g config/log file locations

OBIEE 11g config and log file locations: 

EM Console

Login to the URL

http://server.domain:7001/em

and navigate to:

Fam_bifoundation_domain-Business Intelligence-coreapplications-Diagnostics-Log Messages

These are all the available files:

Presentation Services Log
Server Log
Scheduler Log
JavaHost Log
Cluster Controller Log
Action Services Log
Security Services Log
Administrator Services Log

*************************************************************************

To check the files directly, you can use the following:

1) Admin Server logs

AdminServer-diagnostic.log

Directory:

$MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/servers/AdminServer/logs

or

$DOMAIN_HOME/servers/AdminServer/logs

2) Managed Server logs

bi_server1-diagnostic.log

Directory:

$MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/servers/bi_server1/logs

or

$DOMAIN_HOME/servers/bi_server1/logs/

3) Node Manager logs

Directory: WL_HOME/common/nodemanager

Example:

C:\OBI_11116\wlserver_10.3\common\nodemanager

4) BI Componets logs

Directory: $MIDDLEWARE_HOME/instances/instance2/diagnostics

5) OPMN: Oracle Process Manager and Notification Server

All files under the directory:

$MIDDLEWARE_HOME/instances/instanceX/diagnostics/logs/OPMN/opmn

or

$ORACLE_INSTANCE/diagnostics/logs/OPMN/opmn

6) Enterprise Manager Log

emoms.trc

Directory:

$MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/servers/sysman/log

or

$DOMAIN_HOME/servers/sysman/log

7) Miscellaneous log files

7.1) Installation logs.

7.2) Opatch.

7.3) Repository Creation Utility (RCU).

7.4) Upgrade Assistant (UA).

7.5) Map Viewer log files.

7.6) BI Publisher log file.

7.7) EmbeddedLDAP (can be used in conjunction with the access.logs, as above).

7.8) You can also review the Event Viewer log on Windows and the syslog on Linux or UNIX.

7.9) What Are Diagnostic Log Configuration Files?

7.10) Oracle Business Intelligence Mobile

---

Log files in detail

1. Admin Server logs

AdminServer-diagnostic.log

Directory:
$MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/servers/AdminServer/logs
or
$DOMAIN_HOME/servers/AdminServer/logs

Example:
C:\OBIEE_11G\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

 If there is no Managed Server (for instance, you did Simple Install), you should review these log files:

access.log
AdminServer.log

Domain log file:
bifoundation_domain.log

2. Managed Server log

bi_server1-diagnostic.log

Directory:
$MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/servers/bi_server1/logs
or
$DOMAIN_HOME/servers/bi_server1/logs/

Example:
C:\OBIEE_11g\user_projects\domains\bifoundation_domain\servers\bi_server1\logs

Other files:

access.log
bi_server1.log
bi_server1.out
bi_server1.out00001

3. Node Manager log files

WL_HOME/common/nodemanager

or

$MIDDLEWARE_HOME/wlserver_10.3/common/nodemanager

Example:
C:\OBI_11116\wlserver_10.3\common\nodemanager

4. BI Componets logs file are under:

$MIDDLEWARE_HOME/instances/instance2/diagnostics

In detail:

4.1) BI Server log files.

$MIDDLEWARE_HOME/instances/instance2/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1

Example:
C:\OBIEE_11g\instances\instance2\diagnostics\logs\OracleBIServerComponent\coreapplication_obis1

To confirm the above path, review the 'component-logs.xml' file, these lines to see if the default path has changed:

<log path="diagnostics/logs/OracleBIServerComponent/coreapplication_obis1/nqquery.log">
 ...
 ...
 <log path="diagnostics/logs/OracleBIServerComponent/coreapplication_obis1/nqserver.log">

The files to review are:

4.1.1) Queries run by BI

nqquery.log

4.1.2) BI Server log file

nqserver.log

4.1.3) Administration Tool

servername_NQSAdminTool.log (example, jjuan4_NQSAdminTool.log)

4.1.4) nQUDMLExec

servername_nQUDMLExec.log (examle, jjuan4_nQUDMLExec.log)

4.1.5) Migration Utility

servername_obieerpdmigrateutil.log (example, jjuan4_obieerpdmigrateutil.log)

4.1.6) Repository log

<ORACLE_INSTANCE>/OracleBIServerComponent/coreapplication_obis1/repository

4.1.7) System logging level (for BISystem user).

Using Administration Tool, in Tools->Options->Repository->System Logging Level to set the log level.

This option determines the default query logging level for the internal BISystem user. The BISystem user owns the Oracle BI Server
system processes and is not exposed in any user interface.

A query logging level of 0 (the default) means no logging. Set this logging
level to 2 to enable query logging for internal system processes like event
polling and initialization blocks.

4.1.8) Usage Tracking (Only if redirected to logs)

NQAcct.yyyymmdd.hhmmss.log

STORAGE_DIRECTORY parameter in the Usage Tracking section of the
NQSConfig.INI file determines the location of usage tracking log files


Example:
C:\OBIEE_11G\instances\instance2\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository\SampleAppLite.rpd.Log

4.2) Presentation Server log files

$MIDDLEWARE_HOME/instances/instance2/diagnostics/logs/OracleBIPresentationServicesComponent/coreapplication_obips1

Example:
C:\OBIEE_11g\instances\instance2\diagnostics\logs\OracleBIPresentationServicesComponent\coreapplication_obips1

File to check:
sawlog0.log

4.2.1) Java Host

$MIDDLEWARE_HOME/instances/instance2/diagnostics/logs/OracleBIJavaHostComponent/coreapplication_obijh1

Example:
C:\OBIEE_11g\instances\instance2\diagnostics\logs\OracleBIJavaHostComponent\coreapplication_obijh1

Files to check:

jh.log
jh-1.log
jh-2.log

4.3) Web Catalog Upgrade.

$MIDDLEWARE_HOME/instances/instance2/diagnostics/logs/OracleBIPresentationServicesComponent/coreapplication_obips1

Example:
C:\OBIEE_11g\instances\instance2\diagnostics\logs\OracleBIPresentationServicesComponent\coreapplication_obips1

File to check:
webcatupgrade0.log

http://aseng-wiki.us.oracle.com/asengwiki/display/~mikhail_shmulyan/BIPS+Logging+Configuration

4.4) Scheduler log

$MIDDLEWARE_HOME/instances/instance2/diagnostics/logs/OracleBISchedulerComponent/coreapplication_obisch1

Example:
C:\OBIEE_11g\instances\instance2\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1

File to check:
nqscheduler.log
console~coreapplication_obisch1~1.log

4.4.1) iBot log files.

- You can review the log files using the Windows client tool Job Manager

- You can also review the following log files:

Agent-1-1.err
Agent-1-1.log

Review the instanceconfig.xml file under

$MIDDLEWARE_HOME/instances/instance2/config/OracleBISchedulerComponent/coreapplication_obisch1

Example:
C:\OBIEE_11g\instances\instance2\config\OracleBISchedulerComponent\coreapplication_obisch1


to see the path where the iBot log files are created:

iBots>
            <Log_Dir>C:\OBIEE_11g\instances\instance2\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1</Log_Dir>
            <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><Web_Server>
            jjuan2-es.es.oracle.com:9710</Web_Server>
        <

By default, it is the same path as the Scheduler log but you can modify it.

The path is:

$MIDDLEWARE_HOME/instances/instance2/diagnostics/logs/OracleBISchedulerComponent/coreapplication_obisch1

Example:
C:\OBIEE_11g\instances\instance2\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1

4.5) Cluster Controller

$MIDDLEWARE_HOME/instances/instance2/diagnostics/logs/OracleBIClusterControllerComponent/coreapplication_obiccs1

Example:
C:\OBIEE_11g\instances\instance2\diagnostics\logs\OracleBIClusterControllerComponent\coreapplication_obiccs1

File to check:
nqcluster.log

4.6) ODBC

$MIDDLEWARE_HOME/instances/instance2/diagnostics/logs/OracleBIODBCComponent/coreapplication_obips1

Example:
C:\OBIEE_11g\instances\instance2\diagnostics\logs\OracleBIODBCComponent\coreapplication_obips1

5. OPMN: Oracle Process Manager and Notification Server

All files under the below directory:

debug.log
logquery~1.log
opmn.log
opmn.out
service.log

$MIDDLEWARE_HOME/instances/instanceX/diagnostics/logs/OPMN/opmn
or
$ORACLE_INSTANCE/diagnostics/logs/OPMN/opmn

6. Enterprise Manager Log

emoms.trc

Directory:
$MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/servers/sysman/log
or
$DOMAIN_HOME/servers/sysman/log

7. Miscellaneous log files

7.1) Installation logs

7.1.1) OBIEE Installation and Configuration ($ORACLE_HOME/bin/config.sh):

$MIDDLEWARE_HOME/cfgtoollogs/oui

Examples:
C:\OBIEE_11g\Oracle_BI1\cfgtoollogs\oui

2011-12-23_02-58-20PM.log
install2011-12-23_02-58-20PM.log
install2011-12-23_02-58-20PM.out
installActions2011-12-23_02-58-20PM.log
installProfile2011-12-23_02-58-20PM.log
oraInstall2011-12-23_02-58-20PM.err
oraInstall2011-12-23_02-58-20PM.out

or
$MIDDLEWARE_HOME/oracle_common/cfgtoollogs/oui

Examples:
C:\OBIEE_11g\oracle_common\cfgtoollogs\oui

install2011-12-23_02-58-20PM.log
installActions2011-12-23_02-58-20PM.log
installProfile2011-12-23_02-58-20PM.log

7.1.2) OraInventory files.

Examples:

installActions2011-12-15_03-21-41PM.log
oraInstall2011-12-05_02-55-22PM.err
oraInstall2011-12-05_02-55-22PM.out

Location:

- Windows:
C:\Program Files\Oracle\Inventory\logs

- Linux, AIX : Directory mentioned in /etc/oraInst.loc

- Solaris: Directory mentioned in /var/opt/oracle / oraInst.loc

- HP OpenVMS: Directory under sys$login

7.1.3) Make.log

$ORACLE_HOME/install/make.log

file to check for install/relinking.

7.2) Opatch

Files:
opatch*.log

Directory
$MIDDLEWARE_HOME/Oracle_BI1/cfgtoollogs/opatch

Example:

OUI location : C:/OBIEE_11G/Oracle_BI1/oui
Log file location : C:/OBIEE_11G/Oracle_BI1/cfgtoollogs/opatch/opatch2010-09-24_16-52-41PM.log
Patch history file: C:/OBIEE_11G/Oracle_BI1/cfgtoollogs/opatch/opatch_history.txt

Other file in the inventory directory. For example, on Windows:
C:/Program Files/Oracle/Inventory/logs

7.3) Repository Creation Utility (RCU)

Files:
biplatform.log
mds.log
rcu.log

If the RCU software is uncompressed in this directory:

D:\Trabajo\Docu\OBIEE\Software\11.1.1.6.0\Windows64

Check the following files, mainly the 'rcu.log':

D:\Trabajo\Docu\OBIEE\Software\11.1.1.6.0\Windows64\rcuHome\rcu\log\logdir.2012-02-23_10-17

biplatform.log
mds.log
rcu.log

7.4) Upgrade Assistant (UA)

$MIDDLEWARE_HOMEOracle_BI1/upgrade/logs

Example
C:/OBIEE_11g/Oracle_BI1/upgrade/logs

Files to check:
uaxxxx.log

Example:
ua2010-10-20-14-30-21PM.log

7.5) Map Viewer log files

$mapviewer_deploy_home/web.rar/WEB-INF/log

Example:
mapviewer_20.log in the directory

C:/OBIEE_11g/Oracle_BI1/bifoundation/jee/mapviewer.ear/web.rar/WEB-INF/log

Error messages and timestamped:
- Javascript console: Firefox, Chorme, IE with developer tools

7.6) BI Publisher log file

$MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/bipublisher

For example:
C:\OBIEE_11G\user_projects\domains\bifoundation_domain\servers\AdminServer\logs\bipublisher\bipublisher.log

Details:
========
$MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/servers

You will see entry for AdminServer and managed server. Depending on where bipublisher is
installed, go the

logs/bipublisher

folder.

BI Publisher Trace 32
========================
Go to FMW Control (EM)

http://server:70001/em

Farm_bifoundation_domain
  WebLogic Domain
    bi_cluster
    or
    AdminServer
  
    Right click and select Logs-Log Configuration
  
    In 'Log Levels' tab, search by: oracle.bi.bipssessionscache
  
    View: Runtime Loggers
    Search: All Categories
  
    oracle.bi
  
   oracle.bi.bipssessionscache  TRACE (32) FINEST
   oracle.bi.bipssessionscache.performance  TRACE (32) FINEST

7.7) EmbeddedLDAP (can be used in conjunction with the access.logs, as above).

EmbeddedLDAP.log
EmbeddedLDAPAccess.log

$DOMAIN_HOME/servers/server_name/data/ldap/log/EmbeddedLDAP.log DOMAIN_HOME/servers/server_name/data/ldap/log/

Example:
C:\OBIEE_11G\user_projects\domains\bifoundation_domain\servers\bi_server1\data\ldap\log\EmbeddedLDAP*.log

7.8) Event Viewer log (Windows) and syslog (Linux or UNIX)

You can also review the Event Viewer log on Windows and the syslog on Linux or UNIX. 

7.9) What Are Diagnostic Log Configuration Files?

Diagnostic log configuration files control output to diagnostic log files for Oracle Business Intelligence.
Log configuration files for Oracle Business Intelligence are stored in the following locations:

$ORACLE_INSTANCE/config/component_type/bi_component_name

Example:
logconfig.xml is the same as configuring at

http://server.domain:7001/em

Fam_bifoundation_domain-Business Intelligence-coreapplications-Diagnostics-Log Configuration