X

Oracle Customer Engineering & Advocacy Lab (CEAL) Blog covers BI Tech, EPM, BI Cloud and EPM Cloud.

Error Connecting to Planning Application from Smartview

When
the OU of a user is changed in the external provider, users can potentially
have issues connecting to Planning applications from Smartview.  However,
users can still log into Planning just not Smartview.

Below are the error
messages found in Smartview, Essbase and Shared Services when the OU of a user
is changed in the external provider and not synced with Essbase security:

· Planning
user connecting to Smartview error:

“Cannot open cube
view.  Essbase error 1054060. Essbase failed to select application
<appname> because user is not completely provisioned by Planning”

· Essbase
application log error:

[Tue Mar 15 12:16:22
2011]Local/ESSBASE0///Error(1054060)

Essbase
failed to select application <application name> because
<user@provider> Directory is not completely provisioned by Planning

· SharedServices_Security_Client
log error:

[….@
Failed to get user with identity @ ldap://GUID=xxxxxxxxxxxxxx?USER. User not
available in configured user directories…. ]

When the OU of a user
is changed in the external provider, perform the following steps to sync the
external provider changes to Essbase security:

1. Export the Essbase
security from Essbase Administration Services (EAS) Console, which can be found
\Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin

2. In the exported
security file, locate each OU user that is having Smartview login issues

3. Perform the following
steps to remove impacted users from Essbase security and then refresh from
Planning:

· Login to MaxL as an
admin user

· Execute command:  display
user <username>;

o Can find each user
name in the security dump file

o Display user command
will give the full user name with provider <username@provider> needed
for the next command to drop

· Execute command:
 drop user <username@provider> from security_file;

· Run another security
dump to be sure users were removed from Essbase

· Run a Planning
security refresh to sync the user back to Essbase

This
should correct the Planning application connection from Smartview login issue
for each user.


Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha