Analytics Resources: Insights, Best Practices,

Case Studies and More

close
Written by Shwetank Sheel
on September 04, 2013

I encountered a strange error which I spent almost a full day trying to resolve, so I thought I would save others time in the future by sharing my findings.

The Problem : We have setup functionality to allow URL based actions on a few reports. These are triggered through a dropdown (view selector) which displays an extra column from where the comment can be triggered.

bi_filesystem_problem

In the development environment, these worked fine. However, in the test and production environments, these would randomly pop-up errors saying object not found, or log users out of the Oracle BI system.

The Evidence: On looking through the logs, I was able to identify that the log-off was happening because the BI Server and Presentation server were crashing. After the crash, the Cluster Controller would bring them back up. So to the users, this seemed like a simple logout.
The strange thing, however, was the error message in the log files. Even after setting logging to the Finest level (Turning on logging using EM), this is all I was able to see:

sawlog0.log

[2013-09-02T20:59:34.000+08:00] [OBIPS] [TRACE:1] [] [saw.rpc.server.handleConnection] [ecid: 00iGzlaCOWtFw0zoVS04rz6FX2i1jsmzi000TxK000005,0:27] [tid: 131496] Caught UnexpectedEOF. Probably, client shutting down.[[
File:socketrpcserver.cpp
Line:583
Location:
    saw.rpc.server.handleConnection
    saw.rpc.server.dispatch
    saw.threadpool.socketrpcserver
    saw.threads
ecid: 00iGzlaCOWtFw0zoVS04rz6FX2i1jsmzi000TxK000005,0:27
ThreadID: 131496
]]

nqserver.log

[2013-09-02T20:59:42.000+08:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: 00iGzlYESXcFw0zoVS04rz6FX2i1jsmzi000TbO000000] [tid: 103dc]  [nQSError: 12002] Socket communication error at call=recv: (Number=10054) An existing connection was forcibly closed by the remote host.

The Fix: After investigating in detail all the differences between the Development and UAT / PROD environments, I finally realized that there was a difference in file paths. With iterative testing, I realized that the EOF exception in the SAW log was due to the file path being too long for the Windows filesystem to pass.

To fix this, I used the Microsoft mklink function to create a softlink for the catalog.

Before:

before

After:

after

That fixed the problem.

 

For reference, here are some more details about the environments this test case occurred in are:

OS: Windows Server 2008 R2 (with Service Pack 1)

Oracle Business Intelligence: 11.1.1.6.7 (Build 121219.1259 64-bit)

 

Hope this helps someone save time.

You may also like:

OBIEE 12c Cloud Analytics

Join us at the Modern Finance Experience

Join us on Wednesday 23-Mar at the Marina Bay Sands for the Modern Finance Experience event organized by Oracle. You wil...

OBIEE 12c

OBIEE 12c Baseline Validation Tool

In the real world, the migration between two OBIEE environments is really take time .The last time we did this for a cus...

OBIEE 12c

Steps to upgrade usage tracking when upgrading from OBIEE 11.1.7.1 to OBIEE 11.1.1.9

Recently usage tracking stopped working for one of my clients after upgrading to OBIEE 11.1.1.9 with the NQSERVER log sh...