Scribd
Upload
26 views2 pages

Obiee 11G: Refresh User Guids: Patlaf Leave Your Thoughts

This document discusses refreshing user GUIDs in OBIEE 11g after various events like migration, server crash, or partition filling. It may be necessary after these events to sign back into the system. The process requires manually editing configuration files, restarting services, removing the edits, and restarting again. It involves adding a parameter to NQSConfig.INI and an XML tag to instanceconfig.xml, restarting, removing the changes, and restarting again.

Uploaded by

Tariq Ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
26 views2 pages

Obiee 11G: Refresh User Guids: Patlaf Leave Your Thoughts

This document discusses refreshing user GUIDs in OBIEE 11g after various events like migration, server crash, or partition filling. It may be necessary after these events to sign back into the system. The process requires manually editing configuration files, restarting services, removing the edits, and restarting again. It involves adding a parameter to NQSConfig.INI and an XML tag to instanceconfig.xml, restarting, removing the changes, and restarting again.

Uploaded by

Tariq Ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

OBIEE 11G: Refresh user GUIDs

posted on 08/12/2014 by patlaf | Leave your thoughts

You most probably have to refresh the user GUIDs

After a migration from Dev to Prod (or whatever environment)


After a server crash
After the OBIEE partition got full
After having unexplained problems to signing in

This is an expected operation after a migration of the entire catalogue. I dont really understand
why the GUIDs has to be refreshed after a crash (AFAIK, they dont change), but I had to do it
so many times in this situation to be able to log in again.

The task cannot be done using the Weblogic Console neither Weblogic Enterprise Manager. It
requires to manually edit 2 config files on the server, bounce the services, remove the edited
lines from the config and bounce the services again.

Edit NQSConfig.INI

The file is located in the Oracle BI Server config folder:

/usr/local/OracleBI/instances/instance1/config/OracleBIServerComponent/coreapplication_obis
1/NQSConfig.INI

Locate the parameter FMW_UPDATE_ROLE_AND_USER_REF_GUIDS and change


its value to YES
Save and Close the file

Edit instanceconfig.xml

The file is located in the Oracle Presentation Server config folder:

/usr/local/OracleBI/instances/instance1/config/OracleBIPresentationServicesComponent/coreap
plication_obips1/instanceconfig.xml

Locate the XML tag <Catalog>


Add the following tag within the <Catalog>
tag: <UpdateAccountGUIDs>UpdateAndExit</UpdateAccountGUIDs>
Save and Close the file

It should looks like:


<Catalog>
<UpgradeAndExit>false</Upg
<UpdateAccountGUIDs>Upda
</Catalog>

1 <Catalog>
2 <UpgradeAndExit>false</UpgradeAndExit>
3 <UpdateAccountGUIDs>UpdateAndExit<UpdateAccountGUIDs>
4 </Catalog>

Now restart all the services. BI Presentation should fail to start but should not throw errors.

You can now undo all the modifications you made to both config files and restart all the services.
Et voil ! You did refresh the user GUIDs.

You might also like