11g After Changing The Weblogic Admin User Password Cannot Connect In Obiee Answers

11g After Changing The Weblogic Admin User Password Cannot Connect In Obiee Answers (Doc ID 1365210.

11g After Changing The Weblogic Admin User Password Cannot Connect In Obiee Answers (Doc ID 1365210.

Titleimage

Posted by Patrick Hamou on 2017:09:01 17:42:29

APPLIES TO

Business Intelligence Server Enterprise Edition - Version 11.1.1.5.0 [1308] and later
Information in this document applies to any platform.
***Checked for relevance on 12-Sept-2013*** 

SYMPTOMS

After changing the weblogic password, when trying to connect in Answers as the Administrator weblogic, the following error is encountered:

[nQSError: 10131] Open session failed[nQSError: 43113] Message returned from OBIS.
[nQSError: 43126] Authentication failed: invalid user/password.

CHANGES

Two of the default users were missing in the configuration:
BISystemUser
OracleSystemUser

and the OracleSystemGroup group was also missing.

CAUSE

Someone altered the configuration and removed the default users and groups detailed above.

SOLUTION

The following provides 2 ways to resolve this issue:

Option 1:

Recreated BISystemUser and OracleSystemUser in Admin Console.

Recreated OracleSystemGroup.

Added BISystemUser to Administrators group.

Added OracleSystemUser to OracleSystemGroup

In EM console reset the password to BISystemUser in the Credential Store

Recycled Admin server and Managed server and all BI Components.

Added WebLogic back into the BIAdministrator role.

Restart the BI Services and connect in Answers as the Administrator.

 

Option 2:

Step 1 )

> In my realm we have changed user passwords for:

weblogic, OracleSystemUser and  BISystemUser 


STEP 2 )

> Home >bifoundation_domain > Embedded LDAP >

The changes made to the password of user may not always be replicated to the managed server and the managed server may still be expecting the old password ( and can fail the user authentication ). In this case we may have to enable any one of these options ( so that the managed server gets the latest copy of the Admin ldap ) :

-          Master First      OR

-          Refresh Replica at startup.


Step 3)

on  WLST command line:

listCred(map='oracle.bi.enterprise',key='scheduler.schema')

updateCred(map='oracle.bi.enterprise',key='scheduler.schema', user='XXXXXX', password='XXXXXX')

listCred(map='oracle.bi.enterprise',key='scheduler.schema')

listCred(map='oracle.sysman.emas',key='Monitoring.Credentials.oracle_ias_farm.bifoundation_domain')
updateCred(map='oracle.sysman.emas',key='Monitoring.Credentials.oracle_ias_farm.bifoundation_domain', user='weblogic', password='XXXXXX')
listCred(map='oracle.sysman.emas',key='Monitoring.Credentials.oracle_ias_farm.bifoundation_domain')

listCred(map='oracle.bi.system',key='system.user')

updateCred(map='oracle.bi.system',key='system.user', user='BISystemUser', password='XXXXXX')

listCred(map='oracle.bi.system',key='system.user')

Step 4)

Bouncing all the servers; Admin server, Managed server & BIEE services.

Return to Blog