11g Migrated to 12c - Unable to login to Analytics With Weblogic or any user - An error occurred dur — 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

11g Migrated to 12c - Unable to login to Analytics With Weblogic or any user - An error occurred dur

Received Response
11
Views
7
Comments
chillychin
chillychin Rank 6 - Analytics Lead
edited Aug 13, 2024 6:00PM in Oracle Analytics Cloud and Server

So thus far I have been able to successfully install OBIEE 12c, and configure the LDAP for it thanks to a lot of people in this forum.

I was able to log in to 12c with weblogic, as well as some test accounts I had created in the default authenticator. I was also able to log in with an LDAP user.

So everything seemed to be working just fine UNTIL I migrated the 11g exported jar file to 12c.

I am now on the step of using the migration-tool.sh to import my 11g contents into 12c.

I was able to successfully create the jar in 12c, execute it in 11g, then pull the 11g jar into 12c and again run the migration-tool.sh.

I didnt see any major errors (few warnings), but bottom line for everything was that it said that it was "successful"

Now when I try to log in to 12c I am hitting the error

An error occurred during authentication. Try again later or contact your system administrator.

I am using the weblogic user id, and I can log into Weblogic Console, Enterprise Manager and also BI Publisher. I just can not log into analytics.

Has anyone else hit this error?

I tried googling but have not heard of anyone else hitting this error thus far.

Answers

  • Gianni Ceresa
    Gianni Ceresa Mod

    Hi,

    Congrats in migrating your content, hopefully the login is just a "detail"

    Can you check in EM if your weblogic user is still member of any OBIEE application roles?

    The migration also import that part of the security (when run with default settings), so you maybe just got your weblogic account out of the required application roles and by adding it back in you will manage to login ...

    Or can you login at least with one of your LDAP users? (as you did the LDAP setup)

  • chillychin
    chillychin Rank 6 - Analytics Lead

    Hi Gianni

    I do owe you thanks for your guidance on my 12c installation

    I seriously considered that perhaps it was something with my installation along the way that is causing this issue, so I actually did a full reinstall of 12c.

    So I have a fresh out of the box 12c, reconfigured the LDAP, did another import of my 11g enviroment and I am still hitting the below error

    error.jpg

    This is if I use weblogic, or my personal LDAP ID.

    I checked my EM and I see the following

    membership.jpg

    I do see all the application roles from my 11g enviroment in the 12c EM. I did run the migration tool "default". I didnt have any special commands for it.

    Do I need to refresh any GUID's, or is there something else some where I need to refresh?

    From what I can see everything looks right, and everything was working before the final .JAR import. I was able to log in using weblogic and my personal LDAP.

    AFTER the 11g import is when I am experiencing all this.

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

    GUIDs do not exist any more in 12.

    Which exact version was the source? Which precise version was the target?

  • chillychin
    chillychin Rank 6 - Analytics Lead

    The target: OBIEE 12.2.1.2.0 (Build BIPS-20160923092103 64-BIT)

    The source: OBIEE 11.1.1.7.140225 (Build 140209.2017 64-bit)

    I also wanted to note that in 11g, yes I can log in to that system with both weblogic and my LDAP user id no issues.

    Is there any sort of import that I need to do in the WL console?

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

    If only your app roles are missing then you can easily recreated them using WLST in the target env. When stuff liek this happens I don't burden myself with redoing everything. Just fixing the not-working bits.

  • chillychin
    chillychin Rank 6 - Analytics Lead

    I finally figured out what went wrong

    Its two things really that I missed

    1) I had an initialization block that had a checkmark of "Required for Authentication" - When I removed the required for authentication, I was then able to log in. But since this query block was not working, it led me to the second thing

    2) So after having a fresh install of 12c, creating the jar file from 11g and importing it, apparently the import does NOT include moving the TNSNAMES file from the 11g enviroment.

    Silly me, I thought that since Im not changing my source databases, the TNSNAMES file would get imported as well.....long story short I put in the TNSNAMES file from my 11g enviroment into my 12c enviroment then everything worked and I am now able to log in and am going through my reports and validating them

    Thanks for the insight and help!

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner 
    chillychin wrote:2) So after having a fresh install of 12c, creating the jar file from 11g and importing it, apparently the import does NOT include moving the TNSNAMES file from the 11g enviroment.

    ^--- No. Why would it? The documentation precisely states what's contained in the files and what gets moved where. Back-end architecture and infrastructure are apart in all migrations and installations.