Global Unique Identifiers (GUIDs) in OBIEE 11g


Global Unique Identifiers (GUIDs) in OBIEE:

What is GUIDs?
  • In Oracle BI 11g, users are recognized by their Global Unique Identifiers (GUIDs), not by their names
  • GUIDs are identifiers that are completely unique for a given user
  • Using GUIDs to identify users provides a higher level of security because it ensures that data and metadata is uniquely secured for a specific user, independent of the user name
Example Scenario:

1.
2.

3. 
4. 
5.
6. 
 Refreshing GUIDs
  • The GUID feature is there to help secure your OBI environments – especially production.
  • There may however be times when GUIDs become out of sync in and you cannot log in as certain users:
  1. Migrating from WebLogic Embedded LDAP to an alternative identity provider
  2. Deleting users and then recreating them.
  3. Migrating “Production” Presentation Catalog / RPD to the “Development” environment
  • In order to work around this, you can either:
  1. Delete the offending users from the Presentation Catalog and log in again or
  2. Refresh GUIDs (explained overleaf)              
 Regenerating GUIDs :
  • Open up the NQSConfig.ini file for editing:
  • [OBI Home]/config/OracleBIServerComponent/coreapplication_obis1/NQSConfig.ini
  • Set the following parameter within the [SERVER] section:
  • FMW_UPDATE_ROLE_AND_USER_REF_GUIDS = YES;
  • Save the file
  • Open up the instanceconfig.xml file for editing:
  • [OBI Home]/config/OracleBIPresentationServicesComponent/coreapplication_obips1/instanceconfig.xml
  • Add an “UpdateAccountGUIDs” entry to the <Catalog> section as follows:
         <ps:Catalog xmlns:ps="oracle.bi.presentation.services/config/v1.1">
         <ps:UpgradeAndExit>false</ps:UpgradeAndExit>
         <ps:UpdateAccountGUIDs>UpdateAndExit</ps:UpdateAccountGUIDs>
         </ps:Catalog>
  • Save the file
  • Restart Oracle BI System components:
  • $ORACLE_BASE/instances/instance1/bin/opmnctl stopall
  • $ORACLE_BASE/instances/instance1/bin/opmnctl startall


  • To ensure your system is secure once again you must revert the configuration changes!
  • NQSConfig.ini : FMW_UPDATE_ROLE_AND_USER_REF_GUIDS = NO;
  • Instanceconfig.xml : Remove entry for <ps:UpdateAccountGUIDs>
  • Restart Processes : opmnctl stopall / startall
Hope It Helps!!

Thanks,
Shanmugha Bharathy G B

No comments:

Post a Comment