Useful OBIEE Links:

Based on your local environment setup,some may not be accessible.
http://hostname:7001/console         
      access Administran Server
http://hostname:7001/em
        Fusion Middleware Control (FMW)
http://hostname:9704/analytics
      verify the status of bi_server1.
http://hostname:9704/analytics/saw.dll?IBotSummary
      create agents
http://hostname:9704/analytics/saw.dll?bipublisherEntry&Action=new&itemType=.xdm
      create a new datamodel for BI Publisher
http://hostname:9704/analytics/saw.dll?bieehome
      access home page
http://hostname:9704/analytics/saw.dll?Admin
     Administration Page
http://hostname:9704/analytics/saw.dll?ManageGroups
      Manage catalog groups
http://hostname:9704/analytics/saw.dll?Sessions
      Manage sessions or for killing a session
http://hostname:9704/analytics/saw.dll?ManageIBotSessions
      Manage Agent sessions
http://hostname:9704/analytics/saw.dll?bipublisherEntry&Done=%2fanalytics%2fsaw.dll%3fAdmin&Action=admin
      Manage BI Publisher previleges
http://hostname:9704/analytics/olh/l_en/biee0194.htm
      launch help documents
http://hostname:9704/analytics/saw.dll?catalog&action=searchpanel&type=all
      perform Catalog search
http://hostname:9704/analytics/saw.dll?perfmon
      view Performance related metrics
http://hostname:9704/analytics/saw.dll?PrivilegeAdmin
      Manage various permissions with in analytics
http://hostname:9704/wsm-pm
      verify the status of Web Services Manager.
http://hostname:9704/xmlpserver
      accesss Oracle BI Publisher application.
http://hostname:9704/ui
      Oracle Real-Time Decisions application.
http://hostname:9704/bioffice/about.jsp
      verify the status of the Oracle BI for Microsoft Office application.
http://hostname:9704/bicomposer
      verify the status of the Oracle BI Composer application, if this link throw error implies bi composer is not configured.
http://slc01egt.us.oracle.com:9704/analytics/saw.dll?wsdl
                                        access web services.

How mIgrate OBIEE 11g Roles and Application Security from Dev to PROD

Stage the system jazn data xml file from Dev and PROD in a temporary location respectively as shown below

/u01/obiee/stage/dev
/u01/obiee/stage/prod

Then also make a jps-config-policy.xml file as below in the stage direcry. Update the Location respectively and save the file

--?xml version="1.0" encoding="UTF-8" standalone='yes'?>
--jpsConfig xmlns="http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd"
schema-major-version="11" schema-minor-version="1">
--!-- This property is for jaas mode. Possible values are "off", "doas" and "doasprivileged" -->
--property name="oracle.security.jps.jaas.mode" value="off"/>
 --propertySets>
--!-- SAML Trusted Issuer -->
--propertySet name="saml.trusted.issuers.1">
--property name="name" value="www.oracle.com"/>
--/propertySet>    --/propertySets>
 --serviceProviders>
--serviceProvider type="POLICY_SRE" name="policysre.xml.provider" class="oracle.security.jps.internal.policysre.xml.XmlPolicySreProvider">            --description>XML-based PolicySre Provider--/description>        --/serviceProvider>    --/serviceProviders>
 --serviceInstances>
 --!-- JPS XML Policy Sre Service Instance -->
--serviceInstance provider="policysre.xml.provider" location="/u01/obiee/stage/dev/system-jazn-data.xml" name="srcpolicysre.xml">
--description>File Based Policy Sre Service Instance--/description>
--/serviceInstance>
 --serviceInstance provider="policysre.xml.provider" location="/cs/obiee/ial/stage/prod/system-jazn-data.xml" name="policysre.xml">
--description>File Based Policy Sre Service Instance--/description>
--/serviceInstance>
 --/serviceInstances>
 --jpsContexts default="default">
--!-- This is the default JPS context. All the mendary services and Login Modules must be configured in this default context -->
--jpsContext name="sourceFileSre">
--serviceInstanceRef ref="srcpolicysre.xml"/>
--/jpsContext> --jpsContext name="targetFileSre">
--serviceInstanceRef ref="policysre.xml"/>
--/jpsContext>
--/jpsContexts>
--/jpsConfig>
~

Now source the WLST : /middlewarehome/Oracle_BI1/common/bin
wlst.sh
migrateSecuritySre(type="appPolicies", srcApp="obi", configFile="/u01/obiee/stage/jps-config-policy.xml", src="sourceFileSre", dst="targetFileSre", overWrite="false")
Ignore any Warnings.
The prod (system-jazn-data.xml) file will be updated with the new roles from Dev (/u01/obiee/stage/prod).
Take this file and deploy in actual direcry in Prod.

Master Note for OBIEE 11G Patch Releases

OBIEE 11g: Required and Recommended Bundle Patches and Patch Sets (Doc ID 1488475.1)

Repoint OBIEE 11G to new RCU

1.     Login in to the weblogic console, navigate from left menu, services --> datasources and change all datasources to point to new DB from the list

2.     Log in to EM, Then go to Business Intelligence folder à coreapplication àGo to the Deployment tab and then to Scheduler tab. Change the Datasource.

Finally you can check in the system_registry table if any changes are required (Don’t think anything is required here) But will be good to compare old and new table.

Now restart all services including Admin Server.

OBIEE 11g SSL/SSO/LDAP Notes

OBIEE 11g: Authentication: Errors and Configuration Issues (Doc ID 1472856.1) - Master Note

OBIEE11g - SSL LDAP/ADSI Authentication Setup and Configuration (Doc ID 1326641.1)

OBIEE 11g: How To Setup ADSI LDAP Security Provider (Doc ID 1273961.1)

OBIEE 11g: Configuring Authentication and SSO with Active Directory and Windows Native Authentication (Doc ID 1274953.1)

How To Configure OBIEE 11g To Authenticate Using a Database Identity Store (SQL Authenticator) (Doc ID 1338007.1)

OBIEE11g: SSL Setup and Configuration (Doc ID 1326781.1)

NOTE:1390127.1 - OBIEE 11g: How To Check each Configuration Step when Configuring Authentication and SSO with Active Directory and Windows Native Authentication.

Configuring External LDAP Providers with "iplanet Directory Server" (Doc ID 352036.1)

Weblogic Server Not Closing LDAP (iPlanet) Connection (Doc ID 1308807.1)

Troubleshooting LDAP Issues Support Pattern (Doc ID 1077534.1)

How to Configure Users from an External LDAP for WebLogic Administration Purposes (Doc ID 1384908.1)

OBIEE 11g Security Articles from RittManmead Consulting

http://www.rittmanmead.com/2012/03/obiee-11g-security-week-managing-application-roles-and-policies-and-managing-security-migrations-and-deployments/

http://www.rittmanmead.com/2012/03/obiee-11g-security-week-subject-area-catalog-and-functional-area-security-2/

http://www.rittmanmead.com/2012/03/obiee-11g-security-week-row-level-security/

http://www.rittmanmead.com/2012/03/obiee-11g-security-week-connecting-to-active-directory-and-obtaining-group-membership-from-database-tables/

http://www.rittmanmead.com/2010/10/obiee-11gr1-security-explained-an-11g-security-overview/

http://www.rittmanmead.com/2010/10/obiee-11gr1-security-explained-working-with-the-default-security-configuration/

WLST for adding and removing users in EM

/u01/obiee/middlewarehome/Oracle_BI1/common/bin$ ./wlst.sh (Sources the enviroment and required libraries for opss)


Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline>  connect('biadmin','XXXXXXXXX','localhost:29000')
Connecting to t3://localhost:29000 with userid biadmin ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'bifoundation_domain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
wls:/bifoundation_domain/serverConfig>  listAppRoles("obi")
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)
[ [Principal Clz Name : oracle.security.jps.service.policystore.ApplicationRole, Principal Name : BISystem, Type : APP_ROLE], Display Name : BI System Role, Description : null, Guid : F224900024E511E3BF8DAD4CACA361BB]
[ [Principal Clz Name : oracle.security.jps.service.policystore.ApplicationRole, Principal Name : BIAdministrator, Type : APP_ROLE], Display Name : BI Administrator Role, Description : null, Guid : F225053024E511E3BF8DAD4CACA361BB]
[ [Principal Clz Name : oracle.security.jps.service.policystore.ApplicationRole, Principal Name : BIAuthor, Type : APP_ROLE], Display Name : BI Author Role, Description : null, Guid : F225053124E511E3BF8DAD4CACA361BB]
[ [Principal Clz Name : oracle.security.jps.service.policystore.ApplicationRole, Principal Name : BIConsumer, Type : APP_ROLE], Display Name : BI Consumer Role, Description : null, Guid : F225053224E511E3BF8DAD4CACA361BB]


wls:/bifoundation_domain/serverConfig> grantAppRole('obi','BIAdministrator','weblogic.security.principal.WLSUserImpl','User1')
Already in Domain Runtime Tree


wls:/bifoundation_domain/serverConfig> listAppRoleMembers('obi','BIAdministrator')
Already in Domain Runtime Tree
[Principal Clz Name : weblogic.security.principal.WLSGroupImpl, Principal Name : BIAdministrators, Type : ENT_ROLE]
[Principal Clz Name : weblogic.security.principal.WLSUserImpl, Principal Name : User1, Type : ENT_USER]
[Principal Clz Name : weblogic.security.principal.WLSUserImpl, Principal Name : User2, Type : ENT_USER]
[Principal Clz Name : weblogic.security.principal.WLSUserImpl, Principal Name : User3, Type : ENT_USER]
[Principal Clz Name : weblogic.security.principal.WLSUserImpl, Principal Name : User4, Type : ENT_USER]


wls:/bifoundation_domain/serverConfig> revokeAppRole('obi','BIAdministrator','weblogic.security.principal.WLSUserImpl','User1')
Already in Domain Runtime Tree
wls:/bifoundation_domain/serverConfig> revokeAppRole('obi','BIAdministrator','weblogic.security.principal.WLSUserImpl','User2')
Already in Domain Runtime Tree
wls:/bifoundation_domain/serverConfig> grantAppRole('obi','BIAdministrator','weblogic.security.principal.WLSUserImpl','User1')
Already in Domain Runtime Tree
wls:/bifoundation_domain/serverConfig> exit ()


For More Info: Refer to section 9.3 Managing Application Policies with OPSS Scripts (Oracle® Fusion Middleware Application Security Guide
11g Release 1 (11.1.1)


 

OBIEE Performance Tuning Guide

OBIEE 11g Infrastructure Performance Tuning Guide (Doc ID 1333049.1)

How to change ports in OBIEE 11G

Stop all OBIEE services



Edit the config.xm File





FMW_HOME/user_projects/domains/bifoundation_domain/config/config.xml



Note: Backup the file before editing.



The default Admin Server port is 7001 and is not present in the file. But if we need to change it then simply add the listen-port tag under machine tag.



8005



Example:





AdminServer

1000

200000

20

21



AdminServer

true



true

500

true

8002

true

disclosure

{AES}KSbntba0UEOz4=

true

BuiltinSSLValidationOnly

BuiltinSSLValidationOnly

false

false

false

FQDN

8005

true











Similarly we can change the bi_server related ports



bi_server1



bi_server1

true



true

500

true

8004

true

disclosure



true

BuiltinSSLValidationOnly

BuiltinSSLValidationOnly

false

false

false



FQDN

8003

true

bi_cluster



javac



bi_server1



Update BI Server Config File



FMW_HOME/instances/instance1/config/OracleBIServerComponent/coreapplication_obis1/NQSConfig.INI

Note: backup file before editing.



FMW_SECURITY_SERVICE_URL = "http://192.1.1.1:8003";  Corresponds to non-ssl port of bi_server

FMW_UPDATE_ROLE_AND_USER_REF_GUIDS = YES;  Change from NO to YES



Start the OBIEE services and revert back the

FMW_UPDATE_ROLE_AND_USER_REF_GUIDS = NO;



The other method is to do the change via Weblogic Console GUI. But if you need to change the default admin port it’s better to do the changes directly in the files stated above.

Delete a user from WEB Catalog

Go to the catalog location and under users delete the whole user ID folder
ex. if user is joefern, delete the folder joefern in users

once this is done, look for any file names with the user ID under root/system/security
Most likely there will be files in users and accountid folders. if found, delete those files.

Active Directory setup in OBIEE 11g

http://www.peakindicators.com/index.php/knowledge-base/1113-obiee-11g-active-directory-authentication

How to change Browser Title in OBIEE 11G (The Text you see at the top of the Internet Browser Window)

Log on to the Oracle BI server.

Change directory to {MiddlewareHome}\Oracle_BI1\bifoundation\web\msgdb\l_en\messages\

Open productmessages.xml

Change TEXT tag embeded in : WebMessage name=”kmsgProductPortal"

--Oracle BI Interactive Dashboards--
To:
--Your Custom Message--

If any other laguages need the change find the respective language folder in
{MiddlewareHome}\Oracle_BI1\bifoundation\web\msgdb and do as above

Restart all services

How to publish RPD in OBIEE 11G Manually

To deploy RPD in OBIEE 11G manually follow the belwo process. Although this is not recommended , but if you have any issues with EM then the below process will come handy, as it did for me. In my case my EM had issue with locking and updating files.

1. Disbale central Configuration setting from within EM (Refer my earlier post on how to do this, here)
2. Stop all BI Services
3. Upload you new RPD (xxxxxx_02.rpd) to the the server (Location can be found out from your .INI file)
5. Update the INI file with the new name of RPD. make sure its a new name and not existing name.
     ex: xxxxxx_02.rpd

4. Login to EM, login to Enterprise Manager, in the folder structure on the left side, expand WebLogic   Domain and right-click bifoundation_domain..select Security --> Credentials. Expand "oracle.bi.enterprise" and create a key
ex: Key: repository. xxxxxx_02
5. Add a entry for your RPD as per other existing entries, user name will be tempvalue and enter RPD password for the password field.
6. Save the entry
7. Restart BI Services

How to Disbale Fusion Middleware Control in OBIEE/how to set parameters manually (EM Managed Settings)

D.1 Disabling Fusion Middleware Control from Managing Oracle Business Intelligence Configuration Settings

Caution:

Do not attempt to manually update configuration settings that are normally managed by Fusion Middleware Control unless you have been specifically instructed by Oracle Support Services.

Complete this task to prevent manual updates from being overwritten by Fusion Middleware Control for Oracle Business Intelligence configuration settings that are normally managed by Fusion Middleware Control.

You should not manually update configuration settings (that are normally managed by Fusion Middleware Control) without disabling Fusion Middleware Control. Otherwise, your manual changes are overwritten when the Administration Server is restarted, or if changes are activated.
When Fusion Middleware Control is disabled, the Oracle Business Intelligence configuration settings are disabled in the user interface, the Lock Configuration buttons are unavailable, and a message ("Central Configuration is disabled") is displayed.

If you disable Fusion Middleware Control from managing Oracle Business Intelligence configuration settings, then you can continue to use Fusion Middleware Control for other functions such as starting, stopping, restarting, monitoring performance, and viewing diagnostics.
You can disable Fusion Middleware Control from managing Oracle Business Intelligence configuration settings by manually updating a setting in the biee-domain.xml file, as described in the following procedure.

To disable Fusion Middleware Control from managing Oracle Business Intelligence configuration settings:

Caution:

Do not attempt to manually update a configuration setting that is normally managed by Fusion Middleware Control unless you have been specifically instructed by Oracle Support Services.

1. Stop Oracle Business Intelligence.
   For information, see Chapter 4, "Starting and Stopping Oracle Business Intelligence."
2. Complete the following steps to set the centralConfigurationEnabled setting in the biee-domain.xml file:
   
   1. Open the biee-domain.xml file in a text editor.
      The biee-domain.xml file is located in:
      user_projects\domains\bifoundation_domain\config\fmwconfig\biee-domain.xml
   2. Locate the centralConfigurationEnabled element and ensure that its value is set to false.
      To reenable the element, set it to true.
   3. Save the biee-domain.xml file.
3. Restart Oracle Business Intelligence.

D.2 Manually Updating Oracle Business Intelligence Configuration Settings Normally Managed by Fusion Middleware Control

Do not disable Fusion Middleware Control from updating Oracle Business Intelligence configuration settings unless specifically instructed to by Oracle Support Services. If you must update configuration settings normally managed by Fusion Middleware Control, then you can use this procedure.

Configuration settings that are normally managed by Fusion Middleware Control, and which you manually update in a text editor, are overwritten by Fusion Middleware Control when you restart the Administration Server. Therefore you must disable Fusion Middleware Control from overwriting manual configuration changes for parts of the Oracle Business Intelligence system that are centrally managed.

Caution:

If you manually update configuration settings that are normally managed by Fusion Middleware Control (when Fusion Middleware Control is disabled), then you are likely to have to make identical changes in multiple copies of configuration files on multiple computers. If you fail to make appropriate changes in all of the necessary configuration files, then the system is incorrectly configured.

Configuration elements that are normally managed by Fusion Middleware Control are clearly marked in the configuration file as follows:

To manually update the Oracle Business Intelligence configuration settings that are normally managed by Fusion Middleware Control:

1. If not yet done, disable Fusion Middleware Control from being able to update Oracle Business Intelligence configuration settings.
   For information, see Section D.1, "Disabling Fusion Middleware Control from Managing Oracle Business Intelligence Configuration Settings."
2. Stop Oracle Business Intelligence.
   For information, see Chapter 4, "Starting and Stopping Oracle Business Intelligence."
3. Make a backup copy of each configuration file that you plan to edit.
4. Open the configuration file in a text editor.
   
   Note:

   If Oracle Business Intelligence is installed on multiple computers or in multiple locations, then a copy of the configuration file exists for each installation, and each file contains duplicate settings. Therefore, you must locate and make the same changes in each copy of a configuration file.
   For information, see Section 3.6, "Where Are Configuration Files Located?"
5. In each configuration file to change, locate the element, or create the new element if a setting must be added to the file.
   For information, see Appendix C, "Mapping User Interface Labels with Configuration File Elements."
6. Enter the appropriate changes.
7. Save your changes and close the configuration file.
8. Restart Oracle Business Intelligence.

Opatch Error while applying OBIEE patch on Windows

If you hit this error Exception in thread "main" java.lang.NoClassDefFoundError

inspite of setting ORACLE_HOME and the path variables. Please check your CLASSPATH. On a windows system if there are any spaces in the path, then it will fail. So clear any paths having spaces or avaoid having spaces in your paths. I had some other paths in the classpath varaible not related to OBIEE.

So I cleared the classpath varable and only set the Classpath=OBI_HOME/lib (This path does not any spaces in its path).

After setting this, the opatch worked.

Please check if this applicable to you. For me this was not relevant as I already had the correct seetings:

Opatch Fails with Exception in thread "main" java.lang.NoClassDefFoundError: # OPatch failed with error code 1 [ID 1335889.1]

Connecting to Catalog Manager in OBIEE 11g

While doing deployments in OBIEE catalog from different environment (like moving objects from DEV to UAT or PROD), we need to connect to the catalog manager in online mode.

To Connect to catalog manager: open catalog manager from Oracle Business Intellinge tool on start menu in Windows. For Unix you can launch the catalog manager directly from the server using the  ./runcat.sh if you have VNC setup or any Xwindows tool.

This will open the catalog manager, now at thge top menu click file --> open catalog manager. This will pop up user information applet.

Type: online mode
URL: http://hostname:9704/analytics/saw.dll
User: biadmin
password:xxxxxx

Select locale as english and click ok. This takes you in and you can perform different functions like archive objects or to deploy unarchive objects that have been archived from another environment.

The other way to access the same functionality over the web is to login to analytics server and the click catalog near the home link on the top right corner.
http://hostname:9704/analytics/saw.dll?catalog

Disabling http port in OBIEE 11G after SSL Setup

disabling the http port for managed server in Weblogic is quite simple. simply access the console and under managed server general tab uncheck listen port enable and save.

However whenever you restart the managed serever in case of OBIEE, it is bi_sever1, then the server fails to restart. On checking the bi_server1.out file, you will notice the error

Server subsystem failed. Reason: java.lang.AssertionError: No replication server channel for bi_server1
java.lang.AssertionError: No replication server channel for bi_server1

upon checking metalink or oracle support

Startup Error After Enabling Https Listen Port On Bi_server1 [ID 1332151.1]

The solution is :

Enable SSL for bi_cluster as well. Steps are as follows:

1 In the WLS Console, left frame, expand Environment, select Clusters, then select bi_cluster from the right hand frame.

2 Select the tab for Configuration, then the Replication tab. (Make sure Lock and Edit is clicked to allow changes)

3 Select Secure Replication Enabled (checkbox is marked), then save the page.

4 Restart Weblogic services.

This is not currently documented. Documentation bug 12338650 is logged to address.

Note: This issue arises due to weblogic by default uses http port for cluster replication communication and once http is disabled there isnt any port for commmunication.

Refer: http://download.oracle.com/docs/cd/E21764_01/web.1111/e13701/network.htm#CNFGD167

Starting and stopping OBIEE in 10g and 11g

Starting/Stopping Oracle OBIEE 11G

OBIEE 11g is hosted on Weblogic and hence the scripts to start/stop services is totally different from that in 10G.

The start sequnces is:

• Node Manager (wls console and EM, scripts located in  WLS_HOME/bin)
• AdminServer (scripts located under domain/bi_foundation/bin)
• BI Managed Server  (scripts located under domain/bi_foundation/bin)
• Process Manager (Start all bi Services, scripts located at INSTANCE_HOME/bin, uses opmnctl -startall/status)

The Scripts are:

• Node Manager: startNodeManager (cmd or sh)
• AdminServer: startWeblogic (cmd or sh)
• BI Managed Server: startManagedServer (cmd or sh)
• Process Manager: opmnctl  startall

 

Stop Sequence:

The reverse order needs to be followed to stop Services.

• opmnctl stopall
• stopManagedServer (cmd or sh)
• stopWeblogic (cmd or sh)
• Node Manager: To stop nodemanager on unix directly kill the process. On windows if registered as a service stop node manager service.

 

Starting/Stopping Oracle OBIEE 10G

Oracle BI start/stop scripts are located in the directory OracleBI_HOME/setup. The main  scripts are:

• oc4j (start OC4J)
• run-sa.sh (calls user.sh and starts the Oracle BI Server)
• run-saw.sh (calls saw.sh and starts the Oracle BI Presentation Services.)
• run-sch.sh (for BI Scheduler)
• run-ccs.sh (for the Cluster Controller)
• sa-cli.sh (Sets up the environment for running the Oracle BI Client)

The order in which the differnt services in OBIEE are stopped/restarted is important. Below is the start sequence for OBI Component:

• OC4J
• Oracle Business Intelligence Server service.
• Oracle Business Intelligence Presentation Services service.
• Oracle Business Intelligence Scheduler Server service.

Scripts to start:

oc4j -start

run-sa.sh start
run-saw.sh start
run-ccs.sh start  --> Oracle BI Cluster Controller (Only required if OBIEE Cluster is setup)

 

Scripts to Stop:

 

run-ccs.sh stop
run-saw.sh stop
run-sa.sh stop
oc4j -shutdown -port 23791 -password oc4jadmin

OBIEE 11G and 10G Logs

The log files for OBIEE Individual components are under INSTANCE_HOME/instances/instance1/diagnostics/logs. 

11G has neatly compartmentalised logs for each individual components of OBIEE, Below are the location for each of thos components.

Installation log    -->  OBIEE_HOME/logs

nqquery log   -->     OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1

nqserver log   -->     OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1

servername_NQSAdminTool log   -->  OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1

servername_NQSUDMLExec log  -->  OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1

servername_obieerpdmigrateutil log (Migration log)  -->   OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1

sawlog0 log (presentation)      -->     OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIPresentationServicesComponent/coreapplication_obips1

jh log (Java Host)     -->     OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIJavaHostComponent\coreapplication_obijh

webcatupgrade log (Web Catalog Upgrade)     -->    OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIPresentationServicesComponent/coreapplication_obips1

nqscheduler log (Agents)        --> OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBISchedulerComponent/coreapplication_obisch1

nqcluster log    -->   OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIClusterControllerComponent\coreapplication_obiccs1

ODBC log      -->     OBIEE_HOME/instances/instance1/diagnostics/logs/OracleBIODBCComponent/coreapplication_obips1

opmn log      -->      OBIEE_HOME/instances/instance1/diagnostics/logs/OPMN/opmn

Also Logs can be accessed via the EM Console http://server.domain:7001/em

navigate to: Farm_bifoundation_domain-> Business Intelligence-> coreapplications-> Dagnostics-> Log Messages

It is also possible to set individual component level logging from the EM console or rather manage logging for the whole system:

Farm_bifoundation --> application deployment. Select the component and right click to get the options, select logs --> log configuration or view log

OBIEE 10G:

The main logs in OBIEE 10G are as below.

1. BI Presentation Server log can be located from BI_HOME\OracleBIData\web\log\sawlog0.log

This log is useful for Presentation Server login issues and answers/dashboard related issues.

To increase the logging on this server to get a detailed logging to troubleshoot the SSO and integration issues by modifying the logconfig.xml file present in C:\OracleBIData\web\config folder

2. BI Server logs are NQServer.log and NQQuery.log present in BI_HOME\OracleBI\server\Log folder

 NQServer.log consists of BI Server Start up issues and Subject areas loaded and the datasources connected from within the RPD. If the NQSConfig.ini has errors or if RPD has version issues or if proper RPD is not loaded, the BI Server fails to start and this will be recorded in the NQServer.log

NQQuery.log consits of BI Server query operations. We can also check if the result is coming from cache or straight from database. We can get the actual time to execute the query. We can get the physical and logical query from this log.

3. BI Cluster Controller log can located from BI_HOME\OracleBI\server\Log folder. When the cluster is setup with OBIEE server nodes, the NQCluster.log file would provide the cluster nodes connectivity and status information. Along with the NQServer.log , NQCluster.log would be very useful for cluster related issues.

4. BI Javahost can be located from BI_HOME\OracleBIData\web\log\javahost\jhost0.log. This is used for identifying the issues with the charts and graphs generated by Java from Answers/Dashboard reports.

5. BI Scheduler can be located from BI_HOME\OracleBI\server\Log\NQScheduler.log. This is used for identifying the issues related to delivers/scheduler. To increase the logging on scheduler, set the debug flag to true in the scheduler job manager configuration window.

OBIEE 11G Maintenance Mode

Setting the maintenance on makes the system readonly. This feature is of particular importance to us when you want to do maintenance activities but still allow the users to access the application. Users will not be able to save any reports and thus maintain the consistancy of the webcatalog.

The maintenance mode can be toggled ON/OFF on the main OBIEE page when you login to analytics with the link http://servername:port/analytics. At the top right corner of the page click administration link, on the resulting page under Maintenance and Troubleshooting section, you will notice the link toggle Maintenance Mode. Click the link to turn ON/OFF. In a clustered environment the mode can be toggled on each node seperatley.

When set ON, users will recieve a message saying the "System is in Maintenance Mode. Please Try again later". whenever any user tries to save a report.