Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

OBIEE 12c Analytics Login performance issue

Received Response
613
Views
15
Comments
3149053
3149053 Rank 1 - Community Starter

Hi,

we have created user credentials in console. it is extremely slow while logging into obiee 12c analytics. it is taking 15 to 40 sec to launch home page.

Can anybody help on this.

Thanks in advance

Pani

«1

Answers

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    What have you looked at so far? What do the logs say? What is your security setup?

    If you don't provide any information we can't help you.

  • Joel
    Joel Rank 8 - Analytics Strategist

    To get any help from here, you'd need to provide some input. Which version of OBIEE? Which Authentication provider?, Which errors do you see in the Presentation Services log files?

  • 3149053
    3149053 Rank 1 - Community Starter

    Thanks for the reply.

    find the below details.

    Version :OBIEE 12.2.1.2.0

    Authentication: DefaultAuthenticator (WebLogic Authentication Provider)

    Presentation service logs: I did not find any error in logs.

    [2018-04-11T07:12:15-04:00] [OBIPS] [NOTIFICATION:1] [] [saw.securitysubsystem.session.logon] [ecid: 53733e77-fa02-40ad-bc66-507549000ecf-000c694b,0:1:1] [tid: 2138507008] [SI-Name: ] [IDD-Name: ] [IDD-GUID: ] [userId: testuser5] User testuser5 logged in (session ID: 10.82.1.5.2709.4orq43k, service instance context: ssi).[[

    File:masterclientsession.cpp

    Line:481

    Location:

    saw.securitysubsystem.session.logon

    saw.securitysubsystem.checkauthentication.runimpl

    saw.threadpool.asynclogon

    saw.threads

    SessionID: 10.82.1.5.2709.4orq43k

    SIKey: ssi

    ]]

    [2018-04-11T07:12:35-04:00] [OBIPS] [WARNING:16] [] [saw.security.odbcuserpopulationimpl.getuser] [ecid: 53733e77-fa02-40ad-bc66-507549000ecf-000c694d,0:1] [tid: 2652841728] [SI-Name: ] [IDD-Name: ] [IDD-GUID: ] [userId: ] UserPopulation: GetUsers took 20 seconds for SQL {call NQSGetUsers('NAME=testuser5','DISPLAY_NAME','ssi')}, with results: 1[[

    File:odbcuserpoploaderimpl.cpp

    Line:411

    Location:

    saw.security.odbcuserpopulationimpl.getuser

    saw.security.userpopulationmanagerimpl.searchidentities

    saw.security.userpopulationmanagerimpl.getaccountdetailsbyid

    saw.subsystem.mrulist.iteminfojson

    saw.httpserver.processrequest

    saw.rpc.server.responder

    saw.rpc.server

    saw.rpc.server.handleConnection

    saw.rpc.server.dispatch

    saw.threadpool.socketrpcserver

    saw.threads

    HttpCommand: BIEEHome

    SessionID: 10.82.1.5.2709.4orq43k

    RemoteIP: 10.82.1.5

    SIKey: ssi

  • How many users do you have there inside?

    How many init blocks are executed at login? (all the session variables init block which aren't delayed)

    UserPopulation: GetUsers took 20 seconds for SQL {call NQSGetUsers('NAME=testuser5','DISPLAY_NAME','ssi')}, with results: 1

    This already tell you where 20 seconds went ...

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    whats you host os abd where is the rcu schema? how long does startup of the whole stack take?

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    which is why a bad rcu setup could be at fault

  • Adam Wickes
    Adam Wickes Rank 6 - Analytics Lead

    We had a similar issue in our setup (12.3) where our init blocks were using connection pools that were connected to Oracle databases using the wrong method.
    I'll find out more details (evading me at the moment) and get back to you in around 10 hours.

    It altered login time from 40 seconds to instantaneous.

    To check if this is your issue, disable all your init blocks from running, and restart.
    Add one block in at a time, restarting each time and you should be able to nail your culprit.

  • Adam Wickes
    Adam Wickes Rank 6 - Analytics Lead

    In addition to my previous post, we found that if our connection pools connected using service names, login time would be approximately 30-60 seconds.
    If we used SID (unique db name) instead, login time would be instant.
    I worked with one of our DBAs for a few days on this to try and work out "why" but couldn't find an answer.

  • 3600975
    3600975 Rank 1 - Community Starter

    but how to do it? i can't change  service name to sid

  • Adam Wickes
    Adam Wickes Rank 6 - Analytics Lead

    Have you tried disabling all of your init blocks, restarting and seeing if your long login time issue persists?
    If login time improves, then turn init blocks on one at a time until you find the culprit.