Hi,

At a very-high level
This could occur in OBIEE 11g because of the design; wherein a GUID was used for the catalog and a UserID for authorization, and they can get out of synch when you rename a user in an authenticator.

There should be My Oracle Support notes that details how to use the Catalog Manager CLI to either rename or forget the account and they will be resync'd. You should have a backup of user content if forgetting the account since references to content will be removed.

The notes may be in the "ARCHIVED" section since OBIEE 11g has been out of Premier Support for many years now and only has sustaining support.

We recommend you migration to Oracle Analytics Server as soon as you are able because as time goes on. It will be difficult to migrate directly from 11.1.1.9 and you will need to make an intermediary upgrade to OBIEE 12.2.1.4 (terminal release of OBIEE).

I understand that you renamed the user in your authenticator (active directory).
What is not clear is that if you used the catalog manager rename command and re-sync'd the GUID's

You likely will see an error similar to this in the log

The GUID (..) for user <USERNAME2> already exists in the catalog with username <USERNAME1>. If this user was renamed in the backend, please use the catalog user management tools to rename this user in the catalog. If the username was not renamed, the catalog has to be cleaned of this GUID.

Where <USERNAME1> represents the previous user name, and <USERNAME2> the new user name.

You can can test a solution like this.

run the Catalog Management Tool with following command:

./runcat.sh -cmd renameAccounts -old <USERNAME1> -new <USERNAME2> -online http://<HOST_IP>:<PORT>/analytics/saw.dll -credentials boot.txt

On Windows use runcat.cmd in place of runcat.sh.

Boot.txt is a "credentials properties file". You can place the file anywhere in the file system where OBIEE can access it. 

Edit the file and add the following content:

login=username
pwd=password

where username is the OBIEE Administration user, and password is the OBIEE Administration user's password.

 

If the above command has any issues, please see the following steps:  


1. ./opmnctl stopproc ias-component=coreapplication_obips1     (stop presentation services)
2. Backup the catalog.
3. Run the runcat command:

./runcat.sh -cmd renameAccounts -old oldusername -new newusername -offline <CATALOG_HOME>

4. ./opmnctl startproc ias-component=coreapplication_obips1     (start presentation services)
5. Have the user verify the login.
6. If that did not work refresh the GUID's and Validate the catalog.
7.  Retest.

If you see this error, but the user has not being renamed in LDAP, you must run a Catalog Validation to remove the GUIDs.  For more information, see Section 17.2.4 Validating the Catalog of the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1).

 

If you need further assistance, you may still log a Service Request even though OBI 11g is under Sustaining Support.

Hi, I understand your concern.

One of the downsides of staying on an older release too long is included in the definition of Sustaining Support, which is the type of Support that OBIEE 11g is under now.

Oracle Business Intelligence Enterprise Edition (OBIEE) Error Correction Support (Doc ID 1664916.1)

Sustaining Support Definition:
<partial snippet>

As program releases under Sustaining Support are no longer fully supported, information and skills regarding those releases may be limited.  The availability of hardware systems to run such program releases may also be limited.

It also does not include the same priority as products under Premier Support, resources are moved and skilled to current updates.

I do agree with you that you clearly stated rename in 'Active Directory' and not users in the Weblogic embedded LDAP, and that you clearly stated you were using OBIEE 11g (11.1.1.9). So, there should not be any questions about Weblogic LDAP or OAS.

There may be Support personnel hired that never worked with that older version, but they do have access to senior resources.

I hope your issue gets resolved, and that you consider migrating to OAC or OAS (which have improved to remove the GUID sync issue in OBI 11g.

Have a great day!