Refresh Global Unique Identifiers (GUIDs)

You do not normally refresh GUIDs in the LDAP directory (identity store users)
between source and target environments, because the LDAP directories that contain
the GUIDs should be fan-out replicas in both the source and the target environments.
Possible scenarios for refreshing are described in the following list:

■Oracle Business Intelligence source servers and target servers are both configured
against the corporate LDAP directory.
There is no need to refresh LDAP GUIDs.
■ Oracle Business Intelligence source servers are configured against a source LDAP
and the target servers against the corporate LDAP, but the source LDAP is a
fan-out replica of the corporate LDAP directory.
There is no need to refresh LDAP GUIDs.
■ Oracle Business Intelligence source servers are configured against a source LDAP
and the target servers against the corporate LDAP, but the source LDAP is not a
fan-out copy of the corporate LDAP directory.
A refresh of the LDAP GUIDs is needed. Follow the procedures in this section.

After changing the directory server that is used as the data source for the
authentication provider, it is best practice to update the user GUIDs. If the same user
name exists in both directory servers (original and new), then the original user GUID
might conflict with the user GUID that is contained in new directory server. A refresh
forces the system to reference the user GUID that is contained in the new directory
server. Authentication errors might result if the GUIDs are not refreshed and the
system detects a mismatch for the user GUID.
The GUIDs that are stored in the Oracle BI Presentation Catalog or in the RPD file can
be resynchronized and refreshed as described in the following procedure. Before you
begin this procedure, ensure that you are familiar with the information in "Manually
Updating Oracle Business Intelligence Configuration Settings Not Normally Managed
by Fusion Middleware Control" in the Oracle Fusion Middleware System Administrator's
Guide for Oracle Business Intelligence Enterprise Edition.
This procedure requires that you manually edit the configuration files to instruct
Oracle BI Server and Oracle BI Presentation Services to refresh the GUIDs on restart.
Once completed, you edit these files to remove the modification. For information
about where to locate Oracle Business Intelligence configuration files, see the section
that describes where configuration files are located, in Oracle Fusion Middleware System
Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

To refresh the user GUIDs:
1. Open the NQSConfig.INI file for editing. For information, see "Where are
Configuration Files Located?" in Oracle Fusion Middleware System Administrator's
Guide for Oracle Business Intelligence Enterprise Edition.
2. Locate the setting FMW_UPDATE_ROLE_AND_USER_REF_GUIDS = NO and
change its value to YES.
3. Modify the instanceconfig.xml file to instruct Presentation Services to refresh
GUIDs on restart. Edit the file and find the following section:
<Catalog>
<UpgradeAndExit>false</UpgradeAndExit>
</Catalog>
Comment out the <UpgradeAndExit> element and add an
<UpdateAccountGUIDs> element in the same section, as shown in the following
example:
<Catalog>
<!--UpgradeAndExit>false</UpgradeAndExit-->
<UpdateAccountGUIDs>UpdateAndExit</UpdateAccountGUIDs>
</Catalog>

4. Stop and restart the managed processes using the opmnctl command with the
parameters stopall and startall. You can use the parameter status to verify
process status throughout.
The following components are involved: Presentation Services, Oracle BI Server,
Oracle BI Scheduler, Oracle BI Cluster Controller, and Oracle BI JavaHost.
For information about using opmnctl commands, see "Using the OPMN
command line to Start and Stop Oracle Business Intelligence System Components"
in Oracle Fusion Middleware System Administrator's Guide for Oracle Business
Intelligence Enterprise Edition.
5. Edit the NQSConfig.INI file to reset the FMW_UPDATE_ROLE_AND_USER_REF_
GUIDS = YES to NO and restart the Oracle BI Servers.
6. Comment out the line added in Step 3 and remove the commenting from the
original line so that it reads as shown in the following example:
<Catalog>
<UpgradeAndExit>false</UpgradeAndExit>
<!--UpdateAccountGUIDs>UpdateAndExit</UpdateAccountGUIDs-->
</Catalog>
7. Restart Presentation Services for the instanceconfig.xml file that was updated.
8. Ensure that Oracle WebLogic Server and the system components are also running.
If they are not running, then restart them.