Showing posts with label OBIEE Troubleshooting. Show all posts
Showing posts with label OBIEE Troubleshooting. Show all posts

Troubleshooting Active Directory Authentication

One of the most common causes of issues in Active Directory configuration is simply not having the correct settings. It’s useful when trying to diagnose AD LDAP issues to have an LDAP browser to hand. Using an LDAP browser you can test the Base DNs you’re using and the credentials used to connect to the LDAP store, then drill into how your AD/LDAP store is organised to, for example, view the attributes your AD store is using, check name hierarchies (useful for diagnosing Base DN issues) etc



We can use LDAP browsers such as Apache Directory Studio or JXplorer that are free to use for testing the LDAP credentials.
  

MapViewer Runtime Failure


Accessing the MapViewer URL (http://hostname:port/mapviewer), returns an Error 500 Internal Server Error.
In the managed server log 
(MW_HOME/user_projects/domains/bifoundation_domain/servers/bi_server1/logs/bi_server1-diagnostic.log), the following error is recorded at start up:

[ERROR] [] [javax.enterprise.resource.webcontainer.jsf.application] [tid: [STANDBY].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'][userId: <anonymous>] [ecid: 0000Jvu4d^5FKAW5Hzt1if1He7T^000002,0] [APP: mapviewer#11.1.1] JSF1030: The specified InjectionProvider implementation 'com.bea.faces.WeblogicInjectionProvider' cannot be loaded.

Resolution:

Delete the WebLogic internal cache of the MapViewer application.
  1. Stop the Managed Server (for example, bi_server1).
  2. Delete the following files from the MapViewer deployment (for example, MW_HOME/Oracle_BI1/bifoundation/jee/mapviewer.ear
web.war/WEB-INF/lib/adf-faces-api.jar
web.war/WEB-INF/lib/adf-faces-impl.jar
web.war/WEB-INF/lib/commons-digester.jar
web.war/WEB-INF/lib/commons-logging-1.1.jar
web.war/WEB-INF/lib/jsf-api.jar
web.war/WEB-INF/lib/jsf-impl.jar
web.war/WEB-INF/lib/jsr173_1.0_api.jar
web.war/WEB-INF/lib/mvutil.jar
web.war/WEB-INF/lib/xdb.jar
web.war/WEB-INF/adf-faces-config.xml
web.war/WEB-INF/orion-web.xml

Also Recursively delete the following directory:
MW_HOME/user_projects/domains/bifoundation_domain/servers/bi_server1/tmp/_WL_user/mapviewer_11.1.1

Finally Restart the Managed Server.


Managed Server not starting after Upgrade

After you upgrade from Release 11.1.1.3, you might find that the Managed Server for Oracle Business Intelligence encounters issues. For example, the Managed Server might not start or might time out.

Error messages include:
out-of-memory error message related to "'PermGen Space" in bi_server1-diagnostics.log

Root cause:
Incorrect Java memory settings.

workaround:

You must edit a file called setOBIDomainEnv.cmd on Windows or setOBIDomainEnv.sh on UNIX. Ensure that you do not edit the similarly named setDomainEnv.cmd and setDomainEnv.sh files. The specifications in the setOBIDomainEnv file overwrite those in the setDomainEnv file.
  1. Change to the following directory and locate the setup script (setOBIDomainEnv.cmd or setOBIDomainEnv.sh) for the Managed Server environment:
    MW_HOME\user_projects\domains\bifoundation_domain\bin\
  2. Make a backup copy of the setOBIDomainEnv file.
  3. Open the setOBIDomainEnv file for editing in a text editor.
  4. Locate the following line:
    MEM_ARGS="-Xms256m -Xmx1024m -XX:MaxPermSize=256m"
    and replace it with this text:
    MEM_ARGS="-Xms256m -Xmx1024m -XX:MaxPermSize=512m"
  5. Save the changes and close the file.
  6. Restart the Node Manager and the Managed Server.
  7. Rerun the Configuration Assistant to update the Oracle BI Domain.
  8. Perform these steps for each Managed Server in the cluster.

Users are unable to log in with their valid user names and passwords


Issue : Users are unable to log in with their valid user names and passwords

Bifoundation_domain.log Output shows the following:


###<DATE> <Error> <oracle.wsm.resources.enforcement> <Machine_Name> <bi_server1>
<[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'>
<<anonymous>> <> <> <1273244079442> <WSM-07607> <Failure in execution of assertion
{http://schemas.oracle.com/ws/2006/01/securitypolicy}wss-username-token executor
class
oracle.wsm.security.policy.scenario.executor.WssUsernameTokenScenarioExecutor.>
####<DATE> <Error> <oracle.wsm.resources.enforcement> <Machine_Name> <bi_server1>
<[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'>
<<anonymous>> <> <> <1273244079442> <WSM-07602> <Failure in WS-Policy Execution
due to exception.>
####<07-might-2010 15:54:39 o'clock BST> <Error>
<oracle.wsm.resources.enforcement> <ukp79330> <bi_server1> <[ACTIVE]
ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'>
<<anonymous>> <> <> <1273244079442> <WSM-07501> <Failure in Oracle WSM Agent
processRequest, category=security, function=agent.function.service,
application=bimiddleware#11.1.1.2.0, composite=null, modelObj=SecurityService,


Root Cause: If using Oracle Business Intelligence as a data store, BI Publisher establishes system communication with it as BISystemUser. If you change the BISystemUser password in the identity store administrative interface, you also must change the password in the credential store (oracle.bi.system credential map). This applies if you have created a custom application role to take the place of the default BISystemUser. Components will be unable to communicate with each other if the credentials are out-of-sync.

Root Cause One Liner : BISystemUser Credentials Become Out-of Sync.

Resolution: Resetting the BISystemUser Password.

From Fusion Middleware Control target navigation pane, expand the farm, then expand WebLogic Domain, and select bifoundation_domain.
  • From the WebLogic Domain menu, select Security, then Credentials.
  • Open the oracle.bi.system credential map, select system.user and click Edit.
    This screenshot or diagram is described in surrounding text.

  • In the Edit Key dialog, enter BISystemUser (or name you selected) in the User Name field. In the Password field, enter the trusted user's password that is contained in the authentication provider (for example, Oracle Internet Directory, Active Directory).
    Entering BISystemUser credentials in the Edit Key dialog.
  • Click OK.



 

OBIEE 11.1.1.7.1 EXCEL 2007+ Download Error


I was attempted to export to excel 2007 and got a popup saying...
There was an error processing your download. Please check with your administrator' comes up.



Steps to Fix


Step-1:


Make sure that the following paramerters are given in the instance config file.


<Views>

<Pivot>

<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control-->

<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>

<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control-->

<DefaultRowsDisplayedInDownload>650000</DefaultRowsDisplayedInDownload>

<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control-->

  <DisableAutoPreview>false</DisableAutoPreview>

  <MaxVisibleColumns>50000</MaxVisibleColumns>

  <MaxVisiblePages>10000</MaxVisiblePages>

  <MaxVisibleRows>500000</MaxVisibleRows>

  <MaxCells>400000</MaxCells>

  <MaxVisibleSections>55000</MaxVisibleSections>

</Pivot>

<Table>

<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control-->

<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>

<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control-->

  <DefaultRowsDisplayedInDownload>650000</DefaultRowsDisplayedInDownload>

  <MaxVisiblePages>10000</MaxVisiblePages>

  <MaxVisibleRows>500000</MaxVisibleRows>

  <MaxCells>400000</MaxCells>

  <MaxVisibleSections>55000</MaxVisibleSections>

</Table>

<Charts>

  <MaxVisibleColumns>50000</MaxVisibleColumns>

  <MaxVisiblePages>10000</MaxVisiblePages>

  <MaxVisibleRows>100000</MaxVisibleRows>

  <MaxVisibleSections>55000</MaxVisibleSections>

  <JavaHostReadLimitInKB>10240</JavaHostReadLimitInKB>

</Charts>

<Cube>

  <CubeMaxRecords>10000000</CubeMaxRecords>

  <CubeMaxPopulatedCells>100000000</CubeMaxPopulatedCells>

</Cube>

</Views>


Step 2:


Open <INSTANCE_HOME>\config\OracleBIJavaHostComponent\coreapplication_obijh1\config.xml, search for:


<XMLP>

<InputStreamLimitInKB>8192</InputStreamLimitInKB>

</XMLP>


* Replace 8192 with 0 and restart the OPMN processes.


0 means that this limit is deactivated. If this solves the issue and you would like to limit the maximum input size (in kilobytes) for requests that are sent to the JavaHost service, then gradually increase the parameter's value until you can export correctly.


Note: It is HIGHLY recommended that you do not leave it unlimited except for testing purposes as it acts as a "governor" for machine resources.


Additionally be carefull to change the InputStreamLimitInKB in the XMLP tag, as there is another one under the DVT tag



Step 3:


1. Take a back-up copy of opmn.xml located in the directory:


<INSTANCE_HOME>/config/OPMN/opmn


·         Open opmn.xml


·         Find the OracleBIJavaHostComponent parameter:


<process-type id="OracleBIJavaHostComponent" module-id="CUSTOM">

<module-data>

<category id="start-parameters">

<data id="start-executable" value="$ORACLE_HOME/jdk/bin/java"/>

<data id="start-args" value="-server -Xmx1024M -Djava.security.manager=default -DXDO_FONT_DIR=$ORACLE_HOME/common/fonts -Djava.security.policy=$ORACLE_INSTANCE/config/$COMPONENT_TYPE/$COMPONENT_NAME/java.policy

-Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration –


·         Change the heap size to 4096M.

·         Save the changes.


Then re-start the OBIEE components in Enterprise Manager.