During a recent installation of OBIEE 11.1.1.7.0 on one of my personal machines i have noticed something strange which has not happened to be before. The installation went on to complete successfully and the analytics page popped up as usual, but surprisingly i was not able to login to analytics. Admin Console and Enterprise Manager allowed the weblogic login with out any issues.
Verified all the deployments and was able to see no issues, restarted to see if that fixed the issue. Even the status of all opmn components is Alive.SO then i decided to go on to have a look at the Server log files. As this is something related to Analytics login only usually my first preference is to look at bi_server1.log, bi_server1-diagnostic.log, NQserver.log and sawlog.log files.
I found these below errors in bi_server1-diagnostic.log and NQserver.log
Verified all the deployments and was able to see no issues, restarted to see if that fixed the issue. Even the status of all opmn components is Alive.SO then i decided to go on to have a look at the Server log files. As this is something related to Analytics login only usually my first preference is to look at bi_server1.log, bi_server1-diagnostic.log, NQserver.log and sawlog.log files.
I found these below errors in bi_server1-diagnostic.log and NQserver.log
bi_server1-diagnostic.log
WSM-02557 oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query "/policies/oracle/wss_username_token_service_policy" is queued for later retrieval.
[WSM-02353] [oracle.wsm.resources.policymanager] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId:] [ecid: f2c8df7ec64d12f7:1c25f84e:14402c30fe1:-8000-0000000000001049,0] [APP: wsm-pm] Unable to get the Action Executor.
NQServer.log:
[WSM-02557] oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query "/policies/oracle/no_authentication_service_policy" is queued for later retrieval
When i saw thw Authntication failed message, I directly went into Administration Console to see if have the BISystemUser available as this is quite a famous issue. To my surprise its there however OracleSystemUser is missing from the list. I contacted a friend of mine in Oracle and found that this can be created directly as below.
WSM-02557 oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query "/policies/oracle/wss_username_token_service_policy" is queued for later retrieval.
[WSM-02353] [oracle.wsm.resources.policymanager] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId:
[WSM-02557] oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query "/policies/oracle/no_authentication_service_policy" is queued for later retrieval
[nQSError: 43126] Authentication failed: invalid user/password.
When i saw thw Authntication failed message, I directly went into Administration Console to see if have the BISystemUser available as this is quite a famous issue. To my surprise its there however OracleSystemUser is missing from the list. I contacted a friend of mine in Oracle and found that this can be created directly as below.
- Create a User with the name OracleSystemUser
- Assign OracleSystemGroup to the user created, if group is missing then create one.
- Make sure the OracleSystemRole under "Roles and Policies" --> "Global Roles" has the OracleSystemGroup added to it.
- If OracleSystemRole role is missing create one with "Manage Global Roles" link in "How do I" section on the left.
- Add the OracleSystemGroup manually to Role using "Add Conditions" option.
- Restart the OBIEE services.
This fixed my issue, for some only role is missing and for others user is missing, so this process will fit for both the cases. Hope this helped your case.
No comments:
Post a Comment