Scheduled Workbooks and Query Governor TABs Tips

Hi all!
I'm looking for tips for limit my users to improve a Discoverer performance.
Thks!
Fred

Thanks Gianluca!
I wanna set the best values for all options for this TABs.
I had searched in Oracle Documentation and didn't find anything besides limited rows returned.
"Clear this check box for Discoverer to attempt to retrieve all rows in a query. Note that for performance reasons, it is not recommended that you clear this check box when queries might return hundreds of thousands of rows or more."

Similar Messages

Delete WorkBook and Query file from Server .

Dear All Experts .
I dun know i posted in correct places or not .. (correct me if i m wrong) .. i want to ask about the BW Workbook and query.
How we going to remove the remove the workbook or query files from Server ? bc i tried to delete from Analyzer(excel 2007), the file is deleted from the view , but havent delete from the server... So how i going to remove the file from server ?
Thank.

Hello I have the same problem. Can you please tell me how you finaly manage to delete the workbook.
thank's you for advance,
Akiba

Can I share a scheduled workbook?

We have set up scheduled workbooks as the EUL owner, but cannot figure out how the user can access these scheduled reports using their own db id. The user has access to the original report, but does not have the rights to schedule it themselves. Version 10.1.2.1

Hi
If you are using the 10.1.2 Plus version of Discoverer, whether original or patched to 10.1.2.2 or 10.1.2.3 then you can do this.
You simply use Tools | Manage Schedules, pick the existing scheduled workbook and then click the Share button. You can choose which user(s) should have access to the report results.
Best wishes
Michael

Scheduling workbooks in discoverer desktop

I'm trying to figure out how to schedule workbooks to run and export the output to a folder in Discoverer Desktop, I see in many posts that it can be done easily, I just can't figure it out, can anyone help?
I did confirm with my DBA that we do have the DBMS_Job package installed.
When I click on schedule as a user I get the following message:
A workbook cannot be scheduled for the following reason(s) - summary refresh 'job_queue_processes' parameter is 0
I would appreciate any help you can offer.
Thanks,
Janet
email: [email protected]

Hi Janet
You do not need to have DBA privilegs to schedule workbooks and any user should be able to do this. Here is an article from my notes:
Setting up Workbook Scheduling
The workbook scheduling feature in Discoverer uses native features in the Oracle DBMS, and is therefore only available when running against the Oracle database. This feature uses the same highly scalable and reliable processing procedures ithin the kernel, since the summary management capability and the setup for both features is similar. These procedures use standard packages in the DBMS called DBMS_JOB.
To enable the processing procedures for workbook scheduling in Discoverer, follow these steps:
A. Grant Schedule Workbook Privilege to the user.
B. Confirm that DBMS_JOBS has been installed.
C. Specify result set storage.
D. Set the time period at which the process kicks in.
These procedures are described in the following sections:
A. Grant Schedule Workbook Privilege to the User
The user must be granted the Schedule Workbooks privilege in the Privileges dialog. Connect to the Administration Edition, and grant the Schedule Workbooks privilege in Tools->Privileges dialog.
B. Confirming that DBMS_JOBS is Installed
1. Log onto SQL*Plus as the Administrator, and execute the following SQL statement:
SQL> select * from all_objects where object_name='DBMS_JOB' and
object_type = 'PACKAGE';
If the statement returns no rows, use SVRMGRL to create the necessary packages.
2. From Windows XP or NT, select Start->Run.
3. Type in one of the following:
SVRMGRL
4. When in the DBA facility, type CONNECT INTERNAL.
5. Execute the following SQL statement:
SQL> start <ORACLE_HOME>/rdbms/admin/dbmsjob.sql;
SQL> start <ORACLE_HOME>/rdbms/admin/prvtjob.plb;
C. Specifying Result Set Storage
When a scheduled workbook is run, the results are stored in database tables
within the database. Result set data created as part of the workbook
scheduling process may be stored in one of two areas:
the user's own schema or a centralized schema.
User's Schema
In order to enable workbook scheduling in the user's own database schema,
the user requires the following database privileges:
Create Procedure
Create Table
Create View
To grant these privileges, do the following:
1. Log onto SQL*Plus or SQLDBA as the Database Administrator.
2. Type the following:
SQL> Grant CREATE PROCEDURE to <USER>;
SQL> Grant CREATE TABLE to <USER>;
SQL> Grant CREATE VIEW to <USER>;
SQL> Grant EXECUTE ANY PROCEDURE to <USER>;
SQL> Grant SELECT on SYS.DBMS_JOB to <USER>;
SQL> Grant EXECUTE on SYS.V$_PARAMETER to <USER>;
where <USER> is the userid of the person who is to be allowed to schedule
workbooks.
These privileges must be granted directly to the user and not to a database
role.
Advantages: A database limit can be specified on the maximum amount of data a
user can store in the database. If the result set is stored under the user's
schema, then you keep control over the maximum amount of space one individual
user can fill with result sets. If the user creates a scheduled workbook that
fills that space, it affects only his/her own scheduled workbook.
Disadvantage: The user is required to have the above privileges in the database.
Repository User's Schema
In order to enable workbook scheduling using a centralized repository user's
schema, the SQL script batchusr.sql must be run in SQL*Plus or SQLDBA as a
database administrator (such as, SYSTEM). This script creates a new user that
is granted the above privileges.
In addition, the administrator of the EUL must change the user so that the
Repository User property is pointing to the repository user's schema just
created. The centralized repository user's schema may be customized by the
database administrator for space management purposes and underlying data access.
NOTE: SELECT ANY TABLE access is given by the script batchusr.sql,
but this may be limited provided the repository user's schema is
granted access to the underlying data that will be accessed for
workbook scheduling.
The repository user created will not be able to directly schedule a workbook
through the User Edition.
Advantages: Each user does not need DML procedures to run scheduled workbooks.
Disadvantages: One user can potentially run a scheduled workbook that fills the
available result set space, preventing other scheduled workbooks from running
until it is cleared.
D. Setting the Start Time for Workbook Processing
The workbook processes run within the database on the server, and are
controlled by parameters in the initialization file of the Oracle DBMS
- the INIT<SID>.ORA file.
To limit the number of processing requests that can run simultaneously:
The parameter job_queue_processes specifies the number of concurrent processes to use to process DBMS_JOB. It controls the number of processing requests that can be handled simultaneously. The default value is zero, which means processing requests will not be created. You should set it to a minimum of 2 or more if you have any other applications that use DBMS_JOB.
You need more than one job queue process, because if one job fails for any reason, it may keep getting re-submitted, and thus, prevent everything else in the queue from being completed. If you want to have 10 simultaneous processing requests handled, then you will need to set this to 10.
The INIT<SID>.ORA parameter job_queue_interval is the time in seconds that controls how often the job processes wake up to process pending jobs. The default is 60, which is quite frequent. What you set this to depends on how frequently you want the process to wake up and serve the requests that have been made. Oracle recommends that you update the 60 seconds default to at least 10 minutes (a value of 600).
NOTE: This parameter also affects summary management.
To enable these parameters:
1. Locate the INIT<SID>.ORA file.
For example, on Personal Oracle7 the INIT<SID>.ORA file is held in
<ORACLE_HOME>\database. Its default name is INITORCL.ORA where ORCL is
the <SID> name.
2. Enter 2 lines into the file. For example:
job_queue_processes = 2
job_queue_interval = 600 (equivalent to 10 minutes)
NOTE: The summary management and workbook scheduling features both use this scheduling capability within the Oracle DBMS. The interval you specify and the number of concurrent requests affect both features.

Internal Error - Unable to generate SQL for this Scheduled Workbook

I am encountering the following error when loading the results of a Scheduled Workbook;
Internal Error - Unable to generate SQL for this Scheduled Workbook (If you scheduled this workbook using a previous version of Discoverer, please reschedule and re-open)
This only happens for one of the scheduled workbooks and I am struggling to find an explanation to the problem. There are no reference to database links in the workbook so I can rule that out as a cause.
Does anyone have any suggestions to what might be causing the problem?
Many thanks
Stewart

Hi,
The version is OracleBI Discoverer Plus Version 10.1.2.48.18. Do you think this has anything to do with it?If you are on this version, then you have the recommended patches applied.
Did you try to reschedule the workbook and see if this helps in resolving the issue?
I would suggest you enable server logging as this may help in collecting more details about the error.
Note: 403689.1 - How To Generate Discoverer 10g (10.1.2) Session Server Logs In Text Format
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=403689.1
Regards,
Hussein

Schedule workbook error

I face some problem when trying to schedule workbook, as stated below:
I have a column length change from VARCHAR2(35) to VARCHAR2(100). Now if I try to make "Schedule workbook" we got an error generated in the Discoverer's package, and this error looks like:
“Error:
ORA-12899 value too large for column
"SCH_NP_DIS"."EUL5_B130708054654Q1R1"."BRVC69"
(actual: 36,maximum: 35).”
I found here in one post that I need to delete the scheduled workbook and refresh the EUL.
But I am not sure how to refresh EUL using GUI interface of Discoverer administrator. Could anyone help me by mentioning the steps of EUL refresh. Or is there any other option to get rid of this error?

Hi Soumen66,
I agree with the methodology you found in this forum to fix this problem:
-delete scheduled workbook (of course the workbook which the scheduled workbook is dependent is not deleted).
-refresh EUL objects which have changed.
With respect to how to refresh an EUL object (e.g. a folder which contains an object which has been modified), one just opens the owning Business Area and right clicks on the folder. Next, select Refresh.
With respect to canceling the existing scheduled workbook, the reason for this is that the scheduling components in the scheduling schema create a view and a table which corresponds with the results set's columns data definition at the time of scheduling.
Patrick

Discovere viewer and scheduled workbook

I scheduled a workbook to run nightly. If I open the report, that belongs the scheduled workbook, in Dis Viewer, why Discoverer re-run the query again??? This defeated the purpose of scheduled workbook.....

Yes. That is what I understanded. But when in a SQLPlus session I captured SQL statements of both unscheduled and scheduled reports and they both run the same SQL statement

How to save Query in a workbook and Role

Hello All
What are this workbook and role?How to save the query into this and how it helps/use us.
can anyone tell about this?
regards
balaji

Hi,
You need to assign a role to a user. WHen this user enters the system s/he will be able to save queries under the role (the button 'Roles' will be seen).
See here an example of working with roles:
Re: How to protect Queries from being modified ?
Best regards,
Eugene
Message was edited by: Eugene Khusainov

Discoverer Viewer and Scheduled workbooks error

Hi
Hope someone can help.
I am scheduling workbooks in Discoverer Plus 10.1.2.48 with the intention of viewing them in viewer.
The report shows itself as running okay in Admin, but when I open the report in Viewer or Plus I get errors including:
ORA-03106 Fatal two task communication error
or
"unable to generate sql for this scheduled workbook"
I suspect they might be retrieving fairly large result sets (10 K rows +)
Please can anyone offer advice on how to resolve this?
Many thanks

Hi Tim
Well just the way the file is put together, like is it using SID= or SERVER=, does it use SERVER=DEDICATED, do you have one ADDRESS= or multiple?
To make sure everything is right, rename both TNSNAMES and SQLNET.ORA files, then suse Net Configuration Assistant to set up a connection. Then compare that with what you have already and make the necessary changes.
I also noticed that Russ has made a posting concerning a similar error. You should take a look. Its either in here on the Discoverer forum.
Best wishes
Michael

Query to find the list of workbooks and worksheets assiciated to those book

Hi Gurus,
Could you help me with the tables / Query to fetch the list of workbooks and associated worksheets names as welll.
Thanks in advance!!
Rgds,
Santosh

Hi Santosh
The whole point of the STATS table is to allow you to query performance, who did what and when. The database itself does not keep such statistics so if you disable Discoverer's method of capturing these you have no way of knowing who did what and when.
Without this it is impossible to say. I would strongly recommend you enable the capturing of statistics.
The reason you cannot directly query a WORKBOOK to determine what WORKSHEETS are associated with it is because that information is stored as binary information and not in SQL format.
Discoverer 10g has the capability of providing detailed information on the EUL. This feature is not offered "out of the box" but can be easily enabled.
The EUL Administrator can enable the feature by completing the following steps (see also MOS Note 556932.1):
1. Log on to SQL*Plus as the Discoverer Administrator on the machine where Discoverer Administration Edition is installed.
2. Execute the EUL5.SQL script found in the *$ORACLE_HOME\discoverer\util* directory. (This script will create the necessary database objects.)
NOTE: If you are using an Oracle Applications mode EUL, you must also run the eul5_apps.sql file in the $ORACLE_HOME\discoverer\util directory. This script must be run as the EUL owner, and not the Oracle Applications SYSADMIN user.
4. Exit SQL*Plus and log on to the Discoverer Administration Edition product (as the EUL Administrator).
5. From the menu bar, select File | Import.
6. Import the EUL5.EEX file from the ORACLE_HOME\discoverer directory. Once the EUL import is complete, a new business area will be created and visible called The Discoverer V5 EUL. This is the business area that provides the details on the EUL.
EUL Management Workbooks for Discoverer Administrators
The EUL5.EEX file also imports four pre-built Discoverer workbooks. These workbooks are automatically saved to the database during the EEX import and can be executed in Discoverer Plus, Viewer or Desktop:
EUL Workbook Management - shows which workbooks are shared with which users. Examine worksheets to find the folders, items, joins and conditions they depend upon.
EUL Access - This Workbook indicates if a current EUL exists in this users schema. It also displays the EUL's in other user schemas that this user can access.
EUL Query Statistics - Find out which workbooks and worksheets are being used by whom. Examine users ad-hoc queries.
Lineage - Hyper Drill from Discoverer to find a folder or Items Lineage in Oracle Warehouse Builder. To enable the Hyper drill, you will first need to run the Lineage.sql script.
The Discoverer Administrator can use the pre-built workbooks or build their own EUL management workbooks by using the Discoverer V5 EUL business area.
Best wishes
Michael

Steps to create workbook and need to insert 10 query's in the workbook

Hi,
Please let me know Steps to create workbook and need to insert 10 query's in the workbook.
Thanks,
rajesh b

Hi,
Creating Workbook ---> Open your query --> save it as a new workbook -->provide description for workbook -->If you want more queries into the same workbook then insert related queries into different different sheets by insert query from Tools menu .
Regards
Pcrao.

Query EUL tables: I need a list of Workbooks and thier BA Source Folder.

I'm working with Disco 4, but this should apply to all versions.
How do I link the EUL tables together in a query to get the workbook name and it's source folder in the Business Area?
Example: Table EUL4_Documents has all the Workbooks, and EUL4_OBJS has the Business Area folders. How do I Link these tables together?
Thanks,
Mike

Hi Mike
You cannot do this. The EUL4_Workbooks folder does indeed contain the workbooks but they are stored in a LONG RAW database column that cannot be accessed using standard SQL. So even if you can read he Business Area folders there is no way to link these back to a workbook I'm afraid.
Regards
Michael

Scheduled workbooks can be open via DisPlus/Viewer but not in Desktop

When we schedule reports in Discoverer results can be pulled out only via Discoverer Plus/Viewer, when sthe ame scheduled report is opened via Discoverer desktop we get the following massage:
“The results run for this scheduled workbook can no longer be used because the query has changed. Do you want to query the database now for the new results?”
Does anyone know what the issue is here and how it can be resolved?
OracleBI Discoverer 10g (10.1.2.2)
Oracle Business Intelligence Discoverer Plus 10g (10.1.2.54.25)
Desktop Client 10.1.2.50.05
Discoverer Model - 10.1.2.54.25
Discoverer Server - 10.1.2.54.25
End User Layer - 5.1.1.0.0.0
End User Layer Library - 10.1.2.54.25
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bi

Hi
When you upgraded your Discoverer to 10.1.2.2 did you also apply the patch to upgrade Desktop and Administration?
You would have needed to get hold of the Windows version of the patch then run the software update pointing at the Desktop version.
Also, I've heard of this happening following an upgrade from version 4 to version 10 and there are various notes on My Oracle Support concerning this. The one I was just looking at is note 419794.1
Another area where this can happen is if the worksheet uses code that would generate a fan trap. Note 389906.1 deals with this.
Best wishes
Michael

Deleting the scheduled workbooks that are no longer valid - via script

Hi,
I would like to delete the results of the scheduled workbooks (created by users other than me) with scheduled workbooks status like 'Error while running query" or "Report Expired" or "EUL has changed, reschedule report". From Discoverer Administrator (version: 10.1.2.1) --> Tools --> Manage Scheduled Workbooks --> search by user, I can only delete one scheduled workbook at a time. Is there a way to delete these via a script of some kind?
If any one has a sample script and if you can share here that'd be awesome.
Thanks in advance,
-Esther

Ran into Note:459747.1 from metalink. It has information to identify the scheduled workbook results etc., But according to the note in this note "Note: The tables mentioned here should never be updated or deleted manually."
But the admin tool allows to delete one scheduled workbook result at a time based on the status.
Any information here would be beneficial...
Thanks

Error Scheduling workbooks

Hi All,
I scheduled a report with granting Create Table,View and Procedure Privileges to the user. But it shows
Error: Isufficient Privileges.
I have also installed DBMS_JOB package
What could be the problem?
Thanks in Advance.

Hi agin,
all I can suggest is triple checking that...
In the Disco Admin Tool:
Navigate to your 'Business Area'
From the Top Menu:
1) Tools -> Privileges -> Privileges Tab
2) Select the EUL Owner from the drop down list
3) Scroll down the list of privileges and ensure they are all checked... including the 'Schedule Workbooks' option...
Also - when logged into SQL*Plus as the EUL owner - type in the following command at the prompt...
SQL> desc dbms_job
This should return the package header for the DBMS_JOB package and prove that you can see it. Perhaps even check you ave permissions to execute DBMS_JOB...
Otherwise.... sorry - I've run out of ideas...

Scheduled Workbooks and Query Governor TABs Tips

Similar Messages

Maybe you are looking for