Tuesday, April 9, 2013

Could not create a system user connection to Oracle BI Server during start-up

 Could not create a system user connection to Oracle BI Server during start-up. Please check the error message and try again

Step 1 : Refresh GUID

a)Check if any error message regarding GUID mismatch is seen in the sawlogn located in
 C:\OBI11g\instances\instance3\diagnostics\logs\OracleBIPresentationServicesComponent\coreapplication_obips1 folder

If yes follow these steps to refresh GUID as documented in Oracle Fusion Middleware Administrator's Guide.

Refresh the User GUIDs

1. Open the NQSConfig.INI file for editing. For more 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 Oracle BI Presentation Server to refresh GUIDs on restart. Edit the file to add the last line in the following instruction.

 <ps:Catalog xmlns:ps="oracle.bi.presentation.services/config/v1.1">

4. From a terminal window, stop and restart the managed processes using the opmnctl parameters stopall and startall. You can use the parameter status to verify process status throughout.

The following components are involved: Oracle BI Presentation Server, Oracle BI Server, Oracle BI Scheduler, Oracle BI Cluster Controller, and Oracle BI JavaHost.

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. Remove, set to none, or comment out the line (see UpgradeAndExit in the following example) added to the instanceconfig.xml file (that instructs Oracle BI Presentation Server to refresh GUIDs on restart).

 <ps:Catalog xmlns:ps="oracle.bi.presentation.services/config/v1.1">

7. Restart the Presentation Server for the instanceconfig.xml file that was updated.

8. Make sure Oracle WebLogic Server and the system components are also running, if they are not running, restart them.

b) Relogin as the problematic user to verify if you still see the “Unable to Sign In” error

Step 2 : Delete user from rpd if present

a)Launch admin tool and open rpd in OFFLINE Mode

b)Click Manage > Identity > Users tab to verify if you see this user present

Note : Normally you will only see list of users when you open rpd in ONLINE mode. Unless 
the users were created manually in rpd, no users should be visible in OFFLINE mode

c)If the user is present, delete this user entry from rpd

d)save rpd and deploy this changed rpd using EM

e)restart OBI Server component

f)relogin as the problematic user to see if you still see “Unable to Sign In” error

Step 3 : Delete the cacheduserinfo file from webcatalog

If Step1 and Step2 does not work, then do the following

Note : In the example below, catalog name is SampleApp and the user who gets “invalid Login” error is Administrator user.

a)Take a backup of your webcatalog

b)Navigate to
c)Delete the files name cacheduserinfo and cacheduserinfo.atr
d)Launch OBIEE and test by logging in as the specific user.

Hope this help's


No comments:

Post a Comment