FAQ   Discoverer   Administrator     
       
          A collection of bugs, boojums and Oracle oopsies!  

 

 

 

Can’t create EUL due to failure of tablespace grant in 10.1.2.1

 

Q: I’m trying to create an EUL with OracleBI Discoverer 10.1.2.1 and an 11g database.  I’m connected as SYSTEM and right at the end of the wizard I get a “Cannot grant quote on tablespace” error?

 

This is a bug, not in creating the EUL, but in creating a new Oracle database user.  If you select the “Create a new user” option during EUL creation then after selecting default and temporary tablespaces on the “Create EUL Wizard: Step 2” screen and pressing “Finish” you’ll get the error:

 

*  ORA-30041: Cannot grant quota on the tablespace

 

When you exit Administrator you’ll find that the user has been created, but has not been granted any privileges (if you try to log onto Discoverer Administrator with the new user you’ll get a “user has not CREATE SESSION privilege” error message).

 

The workaround is simply to create the user and grant the necessary privileges first within SQL*Plus.  Then, when creating a new EUL, select the “Select an existing user” option.

 

 

Can’t create automated summaries in Discoverer Administrator 10.1.2.1

 

Q: I’m trying to create an automated summary with the wizard but the option is greyed out.  I’ve run “eulasm.sql” as suggested in the Administrator help to give the account all the summary grants and privileges, but it still doesn’t work?

 

This is a common problem.  It arises in part due to missing information in the Discoverer Administrator help and in part to an unhelpful installation script.  In the Discoverer Administrator help you are asked to run script

 

*  <discoverer home>\discoverer\util\eulasm.sql

 

in order to grant the privileges needed for automated summary management.  However, there is an extra privilege required if automated summary management is to become available, and an additional three privileges if warnings are to be eliminated.

 

A grant of “select on v_$parameter” is needed for automated summary management to work.  This grant is not mentioned in the Discoverer Administrator help.  While the grant is included in file “eulasm.sql”, it’s quite likely to fail in practice.  The problem is that help does not state that script “eulasm.sql” must be run from the SYS account.  If you run it from, say, SYSTEM then while all the other privileges will be granted “select on v_$parameter” will not.  And because, the script sets terminal output to “off” when you run it from SQL*Plus the script will appear to have run correctly even though the grant of “select on v_$parameter” has failed.  The result is that while you’ll be able to create an EUL and to perform most tasks within Discoverer Administrator the option for automated summary management will be greyed out on the Summary Wizard.

 

The best way to confirm that a failure to grant “select on v_$parameter” is the cause of the summary management problem is to select “Help” and then “Database Information” from the Discoverer Administrator menu.  If the pop-up contains the message

 

*  Summary management not available because: SYS.V$PARAMETER not accessible

 

followed by a number of other warnings, then the failure of the grant is the cause of the problem.  To fix it run “eulasm.sql” from the SYS account and log into Discoverer Administrator again.  If you select “Help” and then “Database Information” again the warning message about summary management will have disappeared and the ASM option in the Summary Wizard will now be available.

 

However, there will still be three warnings in the “Database Information” pop-up telling you that V$SQL, V$SESSION, and V$SESSTAT are not accessible, and will cause warnings to be issued during query prediction.  If you add the following three grants to “eulasm.sql”

 

*  grant select on v_$sql to &Username;

*  grant select on v_$session to &Username;

*  grant select on v_$sesstat to &Username;

 

and run the file from SYS, then these warnings will also disappear.

 

Needless to say, this is not the sort of problem that a user trying out the Discoverer Administrator for the first time should have to cope with.