Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

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

OAS 6.4 stuck in signing in, after moving to exadata

Closed
241
Views
27
Comments
paamikumar
paamikumar Rank 2 - Community Beginner
edited Jul 23, 2024 3:26PM in Oracle Analytics Cloud and Server

We recently moved to exadata. In a day at least 3 times, users cannot login in. It shows signing in. There is no crash report.

Best Answer

  • paamikumar
    paamikumar Rank 2 - Community Beginner
    Answer ✓

    Hi Steve,

    Thank you to everyone for all your help.

    We finally fixed the issue. It is quite wierd. One of the connection pools in the rpd was not checked for Enable Connection Pooling. We just tried that. That fixed the issue. Possible exadata was keeping all those sessions and not releasing them. Did not happen in earlier db versions.

    Really, really appreciate all the help.

    Thanks,

    Paami.

«13

Answers

  • SteveF-Oracle
    SteveF-Oracle Mod
    edited Jun 3, 2024 3:11PM

    Hi @paamikumar

    A few comments.

    For moderators, this can be moved to the OAS channel.

    1. OAS 2022 (6.4) has ended Error Correction Support
    Oracle Analytics Server Error Correction Support Policy and Dates (Doc ID 2775561.1)

    It is best if you can start with OAS 2024 (the most current update)

    2. To investigate this further, there needs to be an understanding of your security configuration, and the logs would need to be reviewed.
    It is not clear from the minimal details if there is a failure at authentication, or authorization.

    From what you posted, it appears you moved the RCU database. Details would need to be understood about how the move was complete (i.e. - it should either be a clone of the database, or an out-of-place migration.

    Recommend you review the logs for errors as a start.
    If you have private information, then I recommend sanitizing logs before posting here in the public forum, or filing a service request.

  • paamikumar
    paamikumar Rank 2 - Community Beginner

    Thank you Steve for responding. How do i move to OAS channel.

    For Exadata, its not a clone. we take a final back up after you shutdown your app, and restore that DB to exadata

  • [Deleted User]
    [Deleted User] Rank 7 - Analytics Coach

    I have moved the discussion to the appropriate forum.

  • [Deleted User]
    [Deleted User] Rank 7 - Analytics Coach

    Re. the original question: it's hard to believe that there's nothing in the logs. If this started happening after the DB move then most likely something in your login sequence is tied to / dependent on the database - like initialization blocks marked as "required for authentication" for example.

    Check the log files. One of the components will always raise some kind of complaint to you.

  • SteveF-Oracle
    SteveF-Oracle Mod

    @paamikumar

    From the description, the issue sounds intermittent.
    After the issue occurs, review:

    • bi_server1-diagnostic.log
    • obips1-diagnostic.log
    • sawlogN.log

    How are you remedying the situation? Does it resolve itself over some amount of time? Do you restart a specific component, or the entire stack?

  • paamikumar
    paamikumar Rank 2 - Community Beginner

    Hi Steve,

    We have an SR with Oracle and it is going nowhere. We keep seeing a broken pipe error. Users are stuck in the Signining in screen. For users logged in, and running reports, the system is hung. We are stopping and starting the obis1 and obips1. Today we had to do it 3 times already.

    Loading the log files. Any help is appreciated.

    Thanks,

    Paami

    bi_server1-diagnostic.log
    obis1-diagnostic.log
    sawlog0.log
  • Mostafa Morsy-Oracle
    Mostafa Morsy-Oracle Rank 6 - Analytics Lead

    Please check the following

    1- Do you see Stuck Threads in Weblogic console under the bi_server1 threads ?

    2- do you see a lot of inactive session in DB Side?

    3- Do you have any monitoring Tools installed in same Server as OAS ?

    4- When issue happen do you check nqsserver process if it in hang status , use stack command if you use Linux or check your windows viewer in you using windows

  • SteveF-Oracle
    SteveF-Oracle Mod
    edited Jun 3, 2024 8:16PM

    @paamikumar

    I should have asked if you had an SR open already, can you provide the SR#, so that configuration files can be reviewed for your security configuration.

    I see some errors, but want to check configuration.

  • paamikumar
    paamikumar Rank 2 - Community Beginner

    Hi Steve,

    The SR# is SR 3-36907909631. As per the engineer, all the log files are clear. However, we are seeing "Authn token passed to the ObUserSession constructor is null or invalid." raw_code^201" in our webgate.log file. All the patches are up to date. We are still experiencing the same issue at least 2-3 times a day.

    Thanks for helping us,

    webgate.log

    Paami.

  • Mostafa Morsy-Oracle
    Mostafa Morsy-Oracle Rank 6 - Analytics Lead

    @paamikumar from logs I can see that your NQSserver used to crash till May 6th also I can see some queries taking up to 48 Minutes and you mentioned that issue starts to happen after you migrated your Database to exadata so from all these facts I can conclude that nqsserver go into hang status from time to time which lead to the issue you are facing

    I will recommend the following to narrow down the issue

    1- When issue happen please run the following query in exadata DB

    select count(*),program from gv$session where LAST_CALL_ET > 600

    and status = 'INACTIVE' group by program;

    If you getting a big Number I will recommend that you tune your query execution Time

    edit NQSConfig.INI File you can control the query Time through the following Two Variables

    DEFAULT_DB_MAX_EXEC_TIME = 600;

    MAX_LOGICAL_QUERY_EXEC_TIME = 600;

    Above values are 10 Minutes but you can change based on your longest running query

    Above changes need obis1 to be restarted so it take affect and you can monitor your application

This discussion has been closed.