OBIEE 11g to 12c Migration Tool - Unable to login to Administration tool ONLINE? — Oracle Analytics

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

OBIEE 11g to 12c Migration Tool - Unable to login to Administration tool ONLINE?

Received Response
33
Views
3
Comments
chillychin
chillychin Rank 6 - Analytics Lead
edited Aug 13, 2024 5:55PM in Oracle Analytics Cloud and Server

I have recently been working on upgrading our current enviroments (sandbox/dev/qa/prod) from 11g to 12c.

I have successfully migrated our enviroments for sandox/dev and QA but our PROD enviroment seems to be giving me some problems

I followed the exact same steps from the previous enviroments, the same as our PROD enviroment.

But when I try to log into our Administration tool I get an error saying

"Login Failed"

pastedImage_0.png

There is no error codes that I can see.

Prior to migrating the 11g jar file to 12c - On a fresh 12c install I was able to log into the admin tool (although it was blank) but I was still able to log in regardless. Only AFTER migrating the 11g jar file to 12c I hit the error with the admin tool.

I am able to log in to enterprise manager, weblogic console, analytics, basically everywhere else BUT the admin tool (I have not tried the catalog).

I have tried to uninstall, and reinstall my 12c application as I thought something in my install may have been faulty. But I confirmed on a fresh install I was able to log in to the admin tool. It was only AFTER migrating was I not able to log in to the RPD.

I am using a Windows 7 64 bit desktop client tool.

When I test/connect to my PROD enviroment I have no issues

pastedImage_2.png

pastedImage_4.png

I am also able to log in to the RPD in offline mode.

It is ONLY in ONLINE mode I can not log into the RPD with the "Logon Failed"

I am 99% sure my userid/password are correct, as when I intentionally try to put in an incorrect password it gives me a totally different error.

Has anyone at all seen this?

I am at my wits end on this one now....

Answers

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

    Probably because the 11g application role "BI Administrator" was renamed to "BI Service Administrator" in 12c and you lost the necessary rights as a result of that. Basically you're not a member of the right application role anymore and since WLS and EM are not related to application roles they work...

  • Madasamy -Oracle
    Madasamy -Oracle Rank 6 - Analytics Lead

    Can you try to connect to nqcmd once to make sure that the login is successful at the nqsserver level? ( its under DOMAIN_HOME/bitools/bin)

    Ex: ./nqcmd.sh -d AnalyticsWeb -u weblogic -p password

    and check the obis1-diag logs and bi_server1-diag logs for the particular ECID

  • chillychin
    chillychin Rank 6 - Analytics Lead

    Ok, after a lot of digging around and comparing my QA to my PROD environments I actually found two issues total.

    On top of the "Logon Failed" error above, I also had an issue where in BI Publisher the "Administration" link was totally missing when I logged into /xmlpserver

    I went into enterprise manager (EM) and clicked on [Weblogic Domain] -> [Security] -> [Application Policies]

    I selected "obi" under application stripe and noticed that I was missing the "BIAdministrator" part here

    pastedImage_0.png

    I had to recreate the application policy for BIAdministrator and had to add in the permissions as shown here

    pastedImage_1.png

    The description for the permissions can be found here

    https://docs.oracle.com/cd/E28280_01/bi.1111/e10543/install.htm#BIESC771

    I was missing the following 4 permissions

    -oracle.bi.server.manageRepositories

    -oracle.bi.presentation.catalogmanager.manageCatalog

    -oracle.bi.publisher.adminsterServer

    -oracle.bi.scheduler.manageJobs

    After adding these 4 permissions back it seemed to resolve my issues