Saturday, April 11, 2015

WebLogic Server Not Starting in OBIEE 11g

While you were trying to start the WebLogic Server, it shutdown and you are getting the below error message in the nohup.out file.
__________________________________
<Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: Could not obtain an exclusive lock to the embedded LDAP data files directory: /Middleware/user_projects/domains/bifoundation_domain/servers/AdminServer/data/ldap/ldapfiles because another WebLogic Server is already using this directory. Ensure that the first WebLogic Server is completely shutdown and restart the server.>
<Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
__________________________________

Remove EmbeddedLDAP.lok file in the following directory
/opt/app/obi/Middleware/user_projects/domains/bifoundation_domain/servers/bi_server1/data/ldap/ldapfiles

Now, navigate to the following directory and execute the find command as in below.

/opt/app/obi/Middleware/user_projects/domains/bifoundation_domain
bifoundation_domain]$ find . -name "*DAT"
./servers/bi_server1/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT
./servers/bi_server1/data/store/default/_WLS_BI_SERVER1000000.DAT
./servers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT
./servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT

Navigate to those directories and remove the files.

Reason for the above error. If you have used "KILL -9" command to kill any of the servers before you did the starting.




OBIEE 11g Installation Issues - Domain Creation Failure

While you are installing the OBIEE 11g - 11.1.1.7.0 and you are experiencing this below mentioned issue.

BI Configuration - Creating Domain failed.
Error message - Config Action BI Configuration Failed. Configure BI Failed.



When I checked the BI_Server1.log file, I was able to figure out the below error:
_____________________________________________
[ERROR] [] [oracle.as.provisioning] [tid: 14] [ecid: 0000K^xVnRy7i4w5GFS4yf1KIHMh000005,0] [[
oracle.as.provisioning.exception.ASProvWorkflowException: Error Executing workflow.
at oracle.as.provisioning.engine.WorkFlowExecutor._createDomain(WorkFlowExecutor.java:686)
at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:391)
at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
at oracle.as.install.bi.biconfig.standard.StandardWorkFlowExecutor.executeHelper(StandardWorkFlowExecutor.java:31)
at oracle.as.install.bi.biconfig.standard.DomainProvisioningTask.doExecute(DomainProvisioningTask.java:49)
at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:66)
at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:113)
at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:375)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:105)
at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:96)
at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:186)
at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86)
at java.lang.Thread.run(Thread.java:662)
_____________________________________________

When I checked the BI_Server1.out file, I found the below error:
_____________________________________________

Executing Task: Creating Domain
AdminServer port is 7001
trying to connect to server 7001
Creating Weblogic Domain.

The JDK wasn't found in directory /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.55.x86_64.
Please edit the startWebLogic.sh script so that the JAVA_HOME
variable points to the location of your JDK.

CLASSPATH=:/opt/app/obi/Middleware/utils/config/10.3/config-launch.jar::/opt/app/obi/Middleware/wlserver_10.3/common/derby/lib/derbynet.jar:/opt/app/obi/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/opt/app/obi/Middleware/wlserver_10.3/common/derby/lib/derbytools.jar::
oracle.as.provisioning.exception.ASProvWorkflowException: /opt/app/obi/Middleware/wlserver_10.3/common/bin/wlst.sh: line 24: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.55.x86_64/bin/java: No such file or directory
____________________________________________
This confirms that the JDK was not installed on the path. Install Java on the following path
/usr/java/jdk1.7.0_07.

Thursday, April 9, 2015

Unable to Sign into OBIEE 11g Analytics - NQSConfig Syntax Error

When you try to log into Analytics, it throws an error stating - "An error occurred during Authentication. Try again later or contact your system administrator".


Log into Enterprise Manager and see if all the OPMN services are up and running.


One of the services has failed. Check the Presentation Server Log - SAWLOG0.LOG file in the below directory:

/Middleware/instances/instance1/diagnostics/logs/OracleBIPresentationServicesComponent/coreapplication_obips1

Output from SAWLOG0.LOG:
________________________________
[OBIPS] [ERROR:31] [] [saw.security.odbcuserpopulationimpl.searchidentities] [ecid: 0054nnkvcrx5uXSpICc9yf0004nW000000,0:14470] [tid: 3127040] Error retrieving user/group data from Oracle BI Server's User Population API.
Unable to create a system user connection to BI Server while running user population queries
Odbc driver returned an error (SQLDriverConnectW).
State: HY000.  Code: 10058.  [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred.
[nQSError: 73006] Cannot obtain Oracle BI Servers from either the primary Cluster Controller () or the secondary Cluster Controller () specified for the clustered DSN. (HY000)[[
File:odbcuserpoploaderimpl.cpp
Line:731
Location:
        saw.security.odbcuserpopulationimpl.searchidentities
        saw.security.userpopulationmanagerimpl.searchidentities
        saw.catalog.dirCache.getAllSharedFolders
        saw.CatalogAttributes.cache.cleanup
        saw.taskScheduler.processJob
        taskscheduler
        saw.threads
ecid: 0054nnkvcrx5uXSpICc9yf0004nW000000,0:14470
ThreadID: 3127040

task: Cache/CatalogAttributes
_______________________________________

Check the NQServer.log file in the following link:

/Middleware/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1

Output from NQServer.log:
________________________________________
[OracleBIServerComponent] [ERROR:1] [] [] [ecid: ] [tid: aeb55720]  [nQSError: 26009] File /Middleware/instances/instance1/config/OracleBIServerComponent/coreapplication_obis1/NQSConfig.INI Near Line 311, Near <">: new line in string.
[OracleBIServerComponent] [ERROR:1] [] [] [ecid: ] [tid: bb0b720]  [47012] Syntax error in NQSConfig.ini file.
________________________________________

There is some change done in the NQSConfig file and it is not saved properly.

Make changes in the NQSConfig.INI file in the following directory:

/Middleware/instances/instance1/config/OracleBIServerComponent/coreapplication_obis1

coreapplication_obis1]$ vi NQSConfig.ini

Go to the line number mentioned in the error, in this case Line 311. Check if the correct tags are applied. If not, make the changes, Save and Close the file.

Now, start the OPMN services, it should start. Go to 

/Middleware/instances/instance/bin

bin]$ ./opmnctl  startall


Unable to Sign into OBIEE 11g Analytics

More often, we will encounter this issue. Unable to Log into Analytics... That's the most annoying error and that too when it happens in the Production environment.. As an OBIEE admin, you have to be on your toes...


The above is a very generic issue and there are various factors that contribute to this issue.. You need to get to the core to get your issues resolved.. Remember - "One Size Does Not Fit All!"

I am planning to capture all the errors that is causing issue...

Syntax error in NQSConfig.ini file - Click here to read about the same.

OBIEE 11g Installation Issue - Installer hangs indefinitely

While you were trying to install the OBIEE 11g - 11.1.1.7.0, the installer or configuration wizard hangs indefinitely at the  "Domain Creation" step and no log could be found any where. Not even in the AdminServer.log



Cancel the installer, it is not going to go through.

The following error is logged  in <Oracle_Inventory_Location>/log/install<date-time>.out file:
_______________________________________
Creating a new AdminServer Object ...
AdminServer port is 7001
Starting the domain ...

oracle.as.provisioning.util.ConfigException:
Error while starting the domain.
Cause:
An error occurred while starting the domain.
Action:
See logs for more details.
at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
at oracle.as.provisioning.weblogic.ASDomain.startDomain(ASDomain.java:3172)
.
etc..
.
. at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:83)
at java.lang.Thread.run(Thread.java:619)
Caused by: oracle.as.provisioning.util.ConfigException:
Error while starting the domain.
Cause:
Starting the Admin_Server timed out.
Action:
See logs for more details.
at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
at oracle.as.provisioning.weblogic.ASD
_______________________________________

The AdminServer.log  shows that the AdminServer was started and you find the below comments:
<BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "ASDomain" running in Production Mode>

Resolution:
Navigate to /etc directory and check the hosts file.
/]$ vi /etc/hosts

Issues could be one of the below:

  • The IP mentioned here could be wrong or multiple IPs are mentioned and multiple hostnames are referenced. So the Adminserver gets confused to select which server needs the installation.
  • The file does not have any IP at all.
  • The hostname could be wrong.
  • An IP V6 - IP could have been referenced.