nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Connection issue with Essbase from OBIEE RPD

Ebin Cherian

Hi All,

Essbase 11.1.2.3.500

OBIEE 12.2.1.1.0

We use OBIEE as reporting tool and connect to Essbase to pull some data via OBIEE rpd. Recently we are receiving below mentioned error in random while running the report. Report ran fine for majority of the users, some users receive this error message randomly. I have attached the screenshot of the Essbase connection pool in OBIEE RPD. Please let me know how to debug this issue.

State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. (HY000)

State: HY000. Code: 43113. [nQSError: 43113] Message returned from OBIS. (HY000)

State: HY000. Code: 43119. [nQSError: 43119] Query Failed: (HY000)

State: HY000. Code: 96002. [nQSError: 96002] Essbase Error: You have been logged out by supervisor [CONSOLE], please login again (HY000)

obis log

[2017-09-18T18:55:31.504+00:00] [OBIS] [NOTIFICATION:1] [] [] [ecid: ] [sik: ssi] [tid: 1360] Connection Pool entry for DSN atl-02, DB name is Ess-Clar, connection pool name is Ess-Clar Connection Pool [[

Properties: description=<<2055318233>> DbGateway Exchange: Ess-Clar.Ess-Clar Connection Pool; producerID=0x2fea0800; requestID=0x39a30007; sessionID=0x39a30000; userName=user1;

]]

[2017-09-18T18:55:31.504+00:00] [OBIS] [ERROR:1] [] [] [ecid: ] [sik: ssi] [tid: 1360] [nQSError: 96002] Essbase Error: You have been logged out by supervisor [CONSOLE], please login again [[

file: server\Query\Execution\DbGateway\DbGatewayEssbaseCAPI\Src\SQXDGEssbaseCAPIConnection.cpp; line: 553

Properties: description=<<2055318233>> DbGateway Exchange: Ess-Clar.Ess-Clar Connection Pool; producerID=0x2fea0800; requestID=0x39a30007; sessionID=0x39a30000; userName=user1;

Essabse Log

[2017-09-18T14:55:31.71-04:00] [ESSBASE0] [NOTIFICATION:16] [TCP-59] [] [ecid: 1498233796338,0] [tid: 988] Connected from [::ffff:192.32.170.189]

[2017-09-18T14:55:31.71-04:00] [ESSBASE0] [WARNING:1] [AGENT-1003] [] [ecid: 1498233796338,0] [tid: 988] Error -1 processing request [Logout] - disconnecting

[2017-09-18T14:55:31.87-04:00] [ESSBASE0] [NOTIFICATION:16] [TCP-59] [] [ecid: 1498233796338,0] [tid: 3924] Connected from [::ffff:192.32.170.189]

[2017-09-18T14:55:31.87-04:00] [ESSBASE0] [WARNING:1] [AGENT-1003] [] [ecid: 1498233796338,0] [tid: 3924] Error -1 processing request [Logout] - disconnecting

Find more posts tagged with

Accepted answers

All comments

[Deleted User]

This can happen when you use connection pooling or just have session keep-alive times which are longer on OBIEE and shorter on Essbase.

Ref MOS Doc ID 1384729.1

Ebin Cherian

Hi Christian,

Thanks for the reply. How can I find the session keep-alive times in OBIEE ? Is it the ClientSessionExpireMinutes in instanceconfig.xml ?

What would be better approach ? Disable connection pooling or increase the session timeout in Essbase ?

Thanks !

[Deleted User]

I wouldn't turn off pooling if you're using connection with a technical account instead of named user accounts. Find out how long sessions are alowed to remain alive on both sides first and then take a decision. Unless you have full control over the systems you'll probably need to talk with the admins as well since normally they aren't super keen on changing such critical settings just like that.

tl;dr - increasing things in the essbase side is better

Ebin Cherian

I monitored the session on essbase side. What I observed is the OBIEE session is terminated on Essbase side after the connection pool timeout.

Ebin Cherian

Also this error occurs to User as soon as he login and run the report.

[Deleted User]

Probably because his request is trying to use an existing connection that OBI has with Essbase but it's actually time out in the meantime

Robert Angel

Hi Ebin,

I know you came here for help, but would you mind answering a question, if you compare a like for like query when using Smart View with the performance that you get running the same query through OBIEE to Essbase what kind of performance do you experience?

The reason I ask is that a number of years back I was on a project with OBIEE / Essbase as a deliverable and reports which would render in short minutes in Smart View took long hours in OBIEE.

I am curious if this was due to the architecture on the project I was on or if this is truly the best performance you can currently get out of the Essbase / OBIEE combination.

At the time I wound up creating an export of data and metadata, recreating it all in an RDBMS with suitable indexing and getting a solution which was exponentially faster and considerably less frustrating to write queries against.

In my mental notebook I have the words Essbase / OBIEE and 'never again' - has the world improved since then or is my experience not representative?

thanks for your comments!

[Deleted User]

At least from my experience I can say: "not representative".

I have done Essbase integration since 10.1.3.2, the first very to support it. Performance was never the killer of the cube outlines and logical models made sense in terms of hypercubes designed for analytical access. If the cubes were extremely sparse and used dynamic calcs all over the place performance was as bad as is to be expected. That said the performance was bad both through OBI and SmartView.

Robert Angel

Thanks, mine might have been a more extreme example as data was coming from HPCM...

Ebin Cherian

Hi Robert,

We don't have any performance issue. The only issue is sometimes when user login, they see the error message as given in the problem description. We have OBIEE connection pool timeout of 5 minute specified. I monitored the essbase session and could see the sessions getting disconnected.

I will try to increase the session timeout limit in Essbase as Christian suggested. I will update the results.