Report Tuning

Hello Experts,
I want to your help...Currently i have task to tuning my existing reports...My Manager told me create procedure for that report and stored in backend...when report run just call that procedure...So it will take min. time compared to previous execution report time..
Is it really effective , if we make procedure on backened and call it on report...Is it take really less time...
Eager to know..

Hi,
when doing tuning and specially when moving PLSQL from client to server the best approach is to test and see. In theory it might be faster as you have more power at the backend server but it also depends of what is the PLSQL doing because you could see more network traffic and that will be another performance issue need to have in mind. My suggestion is start with one simple report and see performance at the end you may find that some PLSQL is better at database and other PLSQL at client side.
Hope it helps.
Thanks, RZ

Similar Messages

AWR Report tuning

Hi All,
I have created AWR Report .But i can not anlayse what is the problem in that query which is taking more time to execute from that AWR report.
Can any one give me detail document of the AWR Report Events generated .So, I can analyse from that event where is the problem?
Thanks in advance.

Thanks for your reply
Plan hash value: 3677326586
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | Pstart| Pstop |
| 0 | SELECT STATEMENT | | 3 | 537 | 8018 (1)| 00:01:37 | | |
| 1 | VIEW | VWPREPAIDBALANCEINFORMATION | 3 | 537 | 8018 (1)| 00:01:37 | | |
| 2 | SORT UNIQUE | | 3 | 926 | 8018 (67)| 00:01:37 | | |
| 3 | UNION-ALL | | | | | | | |
| 4 | HASH GROUP BY | | 1 | 252 | 2673 (1)| 00:00:33 | | |
| 5 | NESTED LOOPS SEMI | | 1 | 252 | 2671 (1)| 00:00:33 | | |
|* 6 | HASH JOIN SEMI | | 1 | 218 | 2667 (1)| 00:00:33 | | |
| 7 | PARTITION RANGE ALL | | 583 | 104K| 2035 (1)| 00:00:25 | 1 | 731 |
| 8 | TABLE ACCESS BY LOCAL INDEX ROWID | TBLCDR | 583 | 104K| 2035 (1)| 00:00:25 | 1 | 731 |
|* 9 | INDEX RANGE SCAN | IDX_ACCOUNTID_TBLCDR | 605 | | 1466 (1)| 00:00:18 | 1 | 731 |
|* 10 | TABLE ACCESS FULL | TBLTCUSTOMERPACKAGEHISTORY | 94160 | 3218K| 630 (2)| 00:00:08 | | |
|* 11 | TABLE ACCESS BY INDEX ROWID | TBLMCUSTOMERUSAGEDETAIL | 1 | 34 | 4 (0)| 00:00:01 | | |
|* 12 | INDEX RANGE SCAN | IDX_CUSTOMERID | 3 | | 2 (0)| 00:00:01 | | |
| 13 | HASH GROUP BY | | 1 | 293 | 2669 (1)| 00:00:33 | | |
| 14 | NESTED LOOPS SEMI | | 1 | 293 | 2667 (1)| 00:00:32 | | |
| 15 | NESTED LOOPS | | 1 | 259 | 2663 (1)| 00:00:32 | | |
| 16 | MERGE JOIN CARTESIAN | | 1 | 76 | 630 (2)| 00:00:08 | | |
| 17 | VIEW | index$_join$_006 | 1 | 41 | 1 (100)| 00:00:01 | | |
|* 18 | HASH JOIN | | | | | | | |
| 19 | INDEX FAST FULL SCAN | IDX_PREFIX | 1 | 41 | 0 (0)| 00:00:01 | | |
| 20 | INDEX FAST FULL SCAN | PK_DESTINATION | 1 | 41 | 0 (0)| 00:00:01 | | |
| 21 | BUFFER SORT | | 94160 | 3218K| 630 (2)| 00:00:08 | | |
| 22 | SORT UNIQUE | | 94160 | 3218K| 630 (2)| 00:00:08 | | |
|* 23 | TABLE ACCESS FULL | TBLTCUSTOMERPACKAGEHISTORY | 94160 | 3218K| 630 (2)| 00:00:08 | | |
| 24 | PARTITION RANGE ALL | | 1 | 183 | 2032 (1)| 00:00:25 | 1 | 731 |
|* 25 | TABLE ACCESS BY LOCAL INDEX ROWID | TBLCDR | 1 | 183 | 2032 (1)| 00:00:25 | 1 | 731 |
|* 26 | INDEX RANGE SCAN | IDX_CUSTOEMRID | 605 | | 1463 (1)| 00:00:18 | 1 | 731 |
|* 27 | TABLE ACCESS BY INDEX ROWID | TBLMCUSTOMERUSAGEDETAIL | 1 | 34 | 4 (0)| 00:00:01 | | |
|* 28 | INDEX RANGE SCAN | IDX_CUSTOMERID | 3 | | 2 (0)| 00:00:01 | | |
| 29 | HASH GROUP BY | | 1 | 381 | 2677 (1)| 00:00:33 | | |
|* 30 | FILTER | | | | | | | |
| 31 | NESTED LOOPS ANTI | | 1 | 381 | 2671 (1)| 00:00:33 | | |
|* 32 | HASH JOIN SEMI | | 1 | 347 | 2667 (1)| 00:00:33 | | |
| 33 | PARTITION RANGE ALL | | 583 | 177K| 2035 (1)| 00:00:25 | 1 | 731 |
| 34 | TABLE ACCESS BY LOCAL INDEX ROWID| TBLCDR | 583 | 177K| 2035 (1)| 00:00:25 | 1 | 731 |
|* 35 | INDEX RANGE SCAN | IDX_ACCOUNTID_TBLCDR | 605 | | 1466 (1)| 00:00:18 | 1 | 731 |
|* 36 | TABLE ACCESS FULL | TBLTCUSTOMERPACKAGEHISTORY | 94160 | 3218K| 630 (2)| 00:00:08 | | |
|* 37 | TABLE ACCESS BY INDEX ROWID | TBLMCUSTOMERUSAGEDETAIL | 1 | 34 | 4 (0)| 00:00:01 | | |
|* 38 | INDEX RANGE SCAN | IDX_CUSTOMERID | 3 | | 2 (0)| 00:00:01 | | |
| 39 | NESTED LOOPS | | 1 | 69 | 4 (0)| 00:00:01 | | |
| 40 | TABLE ACCESS BY INDEX ROWID | TBLMDESTINATION | 1 | 41 | 0 (0)| 00:00:01 | | |
|* 41 | INDEX UNIQUE SCAN | PK_DESTINATION | 1 | | 0 (0)| 00:00:01 | | |
|* 42 | TABLE ACCESS BY INDEX ROWID | TBLMCUSTOMERUSAGEDETAIL | 1 | 28 | 4 (0)| 00:00:01 | | |
|* 43 | INDEX RANGE SCAN | IDX_CUSTOMERID | 3 | | 2 (0)| 00:00:01 | | |
-----------------------------------------------------------------------------------------------------------------------------------------

Oracle 10g SQL Tuning Advisor

I am working as a junior DBA. I tried to tune a query using SQL Tuning Advisor that is with DBMS_SQLTUNE.I have created the tuning task successfully with DBMS_SQLTUNE.create_tuning_task.But when i execute the tuning task with EXEC DBMS_SQLTUNE.execute_tuning_task() i got an error like
SQL> EXEC DBMS_SQLTUNE.execute_tuning_task(task_name => 'rep_three');
BEGIN DBMS_SQLTUNE.execute_tuning_task(task_name => 'rep_three'); END;
ERROR at line 1:
ORA-00081: address range [0x60000000000A7D70, 0x60000000000A7D74) is not
readable
ORA-00600: internal error code, arguments: [kesatmGetSqlStats:optCost], [], [],
ORA-06512: at "SYS.PRVT_ADVISOR", line 1624
ORA-06512: at "SYS.DBMS_ADVISOR", line 186
ORA-06512: at "SYS.DBMS_SQLTUNE", line 1008
ORA-06512: at line 1The oracle version is Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bi. The OS is HP-UX. The version is HP-UX B.11.23 U ia64.
I tried to execute DBMS_SQLTUNE as DWH user.I have granted the advisor,DROP ANY SQL PROFILE,ALTER ANY SQL PROFILE,CREATE ANY SQL PROFILE privileges and DBA roles to the DWH user. The way i ran DBMS_SQLTUNE is, first i logged in as DWH user and i tried to execute the query for getting the SQL_ID for the query. For getting the SQL_ID i selected the SQL_ID column value for the DWH user session from v$session.I kept that query executing and meanwhile i opened another session as DWH user and created the tuning task as follows
DECLARE
l_sql_tune_task_id VARCHAR2(100);
BEGIN
l_sql_tune_task_id := DBMS_SQLTUNE.create_tuning_task (
                          sql_id      => 'b65fj39dkkb9v',
                          scope       => DBMS_SQLTUNE.scope_limited,
                          time_limit => 3600,
                          task_name   => 'rep_three',
                          description => 'Report Tuning');
DBMS_OUTPUT.put_line('l_sql_tune_task_id: ' || l_sql_tune_task_id);
END;
/The creation of tuning task was successful.And i executed the tuning task as follows
EXEC DBMS_SQLTUNE.execute_tuning_task(task_name => 'rep_three');The above mentioned errors came when i executed the tuning task.
I am also adding the query which i have tried to tune
select * from dwh.beneficiary_dim BEN_DIM,
                 (Select adr_dp_id,
               adr_account_no,
               ADR_ADDRESS_LINE_1 || ' ' ||
               ADR_ADDRESS_LINE_2 || ' ' ||
               ADR_ADDRESS_LINE_3 || ' ' ||
               ADR_ADDRESS_LINE_4 as ADDRESS,
               adr_pin_code,adr_phone_no,adr_fax_no
          from dwh.beneficiary_address_dim where adr_type_id = 1) PERMANENT_ADD_DIM,
       (Select adr_dp_id,
               adr_account_no,
               ADR_ADDRESS_LINE_1 || ' ' ||
               ADR_ADDRESS_LINE_2 || ' ' ||
               ADR_ADDRESS_LINE_3 || ' ' ||
               ADR_ADDRESS_LINE_4 as ADDRESS,
               adr_pin_code,adr_phone_no,adr_fax_no
          from dwh.beneficiary_address_dim where adr_type_id = 2) BANK_ADD_DIM,
       (Select adr_dp_id,
               adr_account_no,
               ADR_ADDRESS_LINE_1 || ' ' ||
               ADR_ADDRESS_LINE_2 || ' ' ||
               ADR_ADDRESS_LINE_3 || ' ' ||
               ADR_ADDRESS_LINE_4 as ADDRESS,
               adr_pin_code,adr_phone_no,adr_fax_no
          from dwh.beneficiary_address_dim where adr_type_id = 3) NOM_GUARDIAN_ADD_DIM,
       (Select adr_dp_id,
               adr_account_no,
               ADR_ADDRESS_LINE_1 || ' ' ||
               ADR_ADDRESS_LINE_2 || ' ' ||
               ADR_ADDRESS_LINE_3 || ' ' ||
               ADR_ADDRESS_LINE_4 as ADDRESS,
               adr_pin_code,adr_phone_no,adr_fax_no
          from dwh.beneficiary_address_dim where adr_type_id = 4) CORR_ADD_DIM,
       (Select adr_dp_id,
               adr_account_no,
               ADR_ADDRESS_LINE_1 || ' ' ||
               ADR_ADDRESS_LINE_2 || ' ' ||
               ADR_ADDRESS_LINE_3 || ' ' ||
               ADR_ADDRESS_LINE_4 as ADDRESS,
               adr_pin_code,adr_phone_no,adr_fax_no
          from dwh.beneficiary_address_dim where adr_type_id = 6) MINOR_ADDRESS,
                 (Select rp.requestid as requestid,
decode(rp.value,'ALL','ALL','','ALL',decode(substr(rp.value,1,instr(rp.value,'|',1,1)-1),'','ALL',substr(rp.value,1,instr(rp.value,'|',1,1)-1))) as Name,
decode(rp.value,'ALL','ALL','','ALL',decode(substr(rp.value,(instr(rp.value,'|',1,1)+1),((instr(rp.value,'|',1,2))-(instr(rp.value,'|',1,1)+1))),'','ALL',substr(rp.value,(instr(rp.value,'|',1,1)+1),((instr(rp.value,'|',1,2))-(instr(rp.value,'|',1,1)+1))))) as Address,
decode(rp.value,'ALL','ALL','','ALL',decode(substr(rp.value,(instr(rp.value,'|',1,2)+1)),'','ALL',substr(rp.value,(instr(rp.value,'|',1,2)+1)))) as PAN
                  from disadmin.requestparameters rp, disadmin.requestparameters rps, disadmin.reportrequests rr
                 where rp.parameterid = 'CNAS_PARAM_VALUE'
                   and rr.status = 'A'
                   and rp.requestid = rr.id
                   and rp.id = rps.id) P_PARAM_VALUE,
                 (Select rp.requestid as requestid, rp.value as Type
                    from disadmin.requestparameters rp, disadmin.reportrequests rr
                   where rp.parameterid = 'CNAS_NAME_TYPE'
                     and rr.status = 'A'
                     and rp.requestid = rr.id) P_NAME_TYPE,
                 (Select rp.requestid as requestid, rp.value as Addtype
                    from disadmin.requestparameters rp, disadmin.reportrequests rr
                   where rp.parameterid = 'CNAS_ADDRESS_TYPE'
                     and rr.status = 'A'
                     and rp.requestid = rr.id) P_ADDRESS_TYPE
   where ( 1= case when P_NAME_TYPE.Type = 'F' then
               case when BEN_DIM.BDM_FIRST_HOLDER_NAME like DECODE(P_PARAM_VALUE.Name,'ALL','%'||BEN_DIM.BDM_FIRST_HOLDER_NAME||'%','%'||P_PARAM_VALUE.Name||'%')
                         or BEN_DIM.BDM_FIRST_HOLDER_SURNAME like DECODE(P_PARAM_VALUE.Name,'ALL','%'||BEN_DIM.BDM_FIRST_HOLDER_SURNAME||'%','%'||P_PARAM_VALUE.Name||'%')
                    then 1
               else null end
             else
               case when P_NAME_TYPE.Type = 'ALL' then
                 case when (BEN_DIM.BDM_FIRST_HOLDER_NAME like DECODE(P_PARAM_VALUE.Name,'ALL','%'||BEN_DIM.BDM_FIRST_HOLDER_NAME||'%','%'||P_PARAM_VALUE.Name||'%')
                            or BEN_DIM.BDM_FIRST_HOLDER_SURNAME like DECODE(P_PARAM_VALUE.Name,'ALL','%'||BEN_DIM.BDM_FIRST_HOLDER_SURNAME||'%','%'||P_PARAM_VALUE.Name||'%'))
                            and BEN_DIM.BDM_SECOND_HOLDER_NAME like DECODE(P_PARAM_VALUE.Name,'ALL','%'||BEN_DIM.BDM_SECOND_HOLDER_NAME||'%','%'||P_PARAM_VALUE.Name||'%')
                            and BEN_DIM.BDM_THIRD_HOLDER_NAME like DECODE(P_PARAM_VALUE.Name,'ALL','%'||BEN_DIM.BDM_THIRD_HOLDER_NAME||'%','%'||P_PARAM_VALUE.Name||'%')
                      then 1
                 else null end
               else null end
             end )
     and BEN_DIM.BDM_IT_PAN like DECODE(P_PARAM_VALUE.PAN,'ALL','%'||BEN_DIM.BDM_IT_PAN||'%','%'||P_PARAM_VALUE.PAN||'%')
     and (1 = case when P_ADDRESS_TYPE.ADDTYPE = 1 then
                     case when instr(PERMANENT_ADD_DIM.ADDRESS, DECODE(P_PARAM_VALUE.ADDRESS,'ALL',PERMANENT_ADD_DIM.ADDRESS, P_PARAM_VALUE.ADDRESS)) <> 0
                          then 1
                     else null end
                   when P_ADDRESS_TYPE.ADDTYPE = 3 then
                     case when instr(NOM_GUARDIAN_ADD_DIM.ADDRESS, DECODE(P_PARAM_VALUE.ADDRESS,'ALL',NOM_GUARDIAN_ADD_DIM.ADDRESS, P_PARAM_VALUE.ADDRESS)) <> 0
                       then 1
                     else null end
                   when P_ADDRESS_TYPE.ADDTYPE = 4 then
                     case when instr(CORR_ADD_DIM.ADDRESS, DECODE(P_PARAM_VALUE.ADDRESS,'ALL',CORR_ADD_DIM.ADDRESS, P_PARAM_VALUE.ADDRESS)) <> 0
                       then 1
                     else null end
                   when P_ADDRESS_TYPE.ADDTYPE = 6 then
                     case when instr(MINOR_ADDRESS.ADDRESS, DECODE(P_PARAM_VALUE.ADDRESS,'ALL',MINOR_ADDRESS.ADDRESS, P_PARAM_VALUE.ADDRESS)) <> 0
                       then 1
                     else null end
              else null end );The above query also tries to access some tables from another user DISADMIN. Could you please help me in solving this problem while using SQL Tuning Advisor ? I am the only DBA here.

will the rows really be updated just by using the package?Considering DMLs
SQL> select * from test
2 /
        NO
         1
         2
SQL> ed
Wrote file afiedt.buf
1 DECLARE
2   my_task_name VARCHAR2(30);
3 my_sqltext   CLOB;
4 BEGIN
5 my_sqltext := 'insert into test values (3)';
6 my_task_name := DBMS_SQLTUNE.CREATE_TUNING_TASK(
7   sql_text    => my_sqltext,
8 task_name   => 'my_sql_tuning_task');
9* end;
SQL> /
PL/SQL procedure successfully completed.
SQL> BEGIN
2 DBMS_SQLTUNE.EXECUTE_TUNING_TASK( task_name => 'my_sql_tuning_task' );
3 END;
4 /
PL/SQL procedure successfully completed.
SQL> select * from test
2 /
        NO
         1
         2
SQL> SELECT DBMS_SQLTUNE.REPORT_TUNING_TASK( 'my_sql_tuning_task')
2    FROM DUAL;
DBMS_SQLTUNE.REPORT_TUNING_TASK('MY_SQL_TUNING_TASK')
GENERAL INFORMATION SECTION
Tuning Task Name   : my_sql_tuning_task
Tuning Task Owner : TEST
Scope              : COMPREHENSIVE
Time Limit(seconds): 1800
Completion Status : COMPLETED
Started at         : 03/27/2008 05:16:14
Completed at       : 03/27/2008 05:16:16
DBMS_SQLTUNE.REPORT_TUNING_TASK('MY_SQL_TUNING_TASK')
Schema Name: TEST
SQL ID     : gwkmgmyj9824t
SQL Text   : insert into test values (3)
There are no recommendations to improve the statement.
-------------------------------------------------------------------------------Adith

How to maximize the performance of report service 9i?

I have a report running in Oracle 9iAS report service. The report is invoked from forms by PL/SQL function run_report_object and generated into PDF file. The report is so complex that the RDF file size reaches to 6MB.
Now it takes about 30 seconds to run the report. My form service and report service are installed on same machine which has 2 intel XEON 2G CPU and 4G memory. If i run the report twice at same time, the report jobs are put into a queue and runs one by one, so it take me 60 seconds. I find the CPU loading is about 20% during the report is running, it means the report service did not make the base of CPU.
How can report service process multi jobs at same on a multi CPU machine? What is the best config in report service about engine number?

Hi,
Whenever you start a new Reports Server in 9iAS, by default it starts 1 Reports Engine (rwEng). You can increase the number of engines to 2 for processing the 2 jobs simultaneously. you can do this by using the Oracle Enterprise Manager (via the browser). You can also change the following parameters in the server config file directly
file name: OH/reports/conf/<your_reports_server_name>.conf
<engine id="rwEng" ... initEngine="1" maxEngine="1" minEngine="0" ... >
You can either increase both initEngine and maxEngine to 2, only maxEngine. In the latter case, the second reports engine will be started only when needed.
However, increasing the number of engines will obviously increase the overhead. The optimum value for number of engines depends on your machine, load, response characteristics required, etc. You can test with a few values to arrive at an optimum number.
I would recommend going through the Oracle Reports Tuning whitepaper
http://otn.oracle.com/products/reports/htdocs/getstart/whitepapers/cb_tuning8.pdf
Navneet.

10g reports performance--too much graphics?

Hi everyone,
I hope someone out there can provide some tips or insight into this issue.
I am executing performance testing on certain reports for my work. This report is 4 pages with a total of 7 line graphs (time series with begin and end dates provided by user). Now I realize there are multiple issues here, underlying SQL, report server config, hardware, # CPUs, RAM, etc...
my test server is a windows 2000 server, 3 GB Ram, 1 2.4GHz CPU. all allocated to a VMWare image running the app server/report server. The reports server has the default config except I changed the initEngine to 4, maxEngine to 6, and minEngine to 1. There are 4 users concurrently running reports by invoking a URL via a JSP page.
Most rdf reports that are run come back between 10 to 20 seconds. but this report takes 20 to 70 seconds. I followed the reports tuning section in the documentation. The only thing I can't do at this point is replace my rdf with rep files (long story). The trace file seems to indicate a the vast majority of time (>65%) dedicated to processing images. There doesn't seem to be anything I can do about that or is there?? btw, the SQL takes about 100 milliseconds when I run it in TOAD.
Their white paper on scalability tests a windows box with 1 GB RAM and 1 866MHz CPU and it shows it can scale up to hundreds of users with response time less than 10 seconds! Base on my config above, I should be spitting these reports out in no time! They did not show the report that was being executed. If I created a text only report and kept retrieving from cache then it would be blazing fast also. but that's not the real world scenario for me.
I guess long story short...is there anything I can do to quicken the response time via the reports or reports config or is it just a matter of getting more hardware resources?

hello,
please make sure when you read our scalability whitepaper and compare the results with yours that you also carefully compare the report samples. your report has 7 line graphs and that is, to my knowledge, significantly more than in our test scenario.
since you did not specify the exact version of your installation i assume its 9.0.4. you might want to take a look at the REPORTS_DEFAULT_DISPLAY and REPORTS_GRAPH_DPI settings which have impact on image performance. overall, we are aware, that extensive use of graphs has negative impact on performance and the next release of reports will have improvements in this area.
thanks,
ph.

Errors using DBMS_SQLTUNE Advisors for Oracle 10g

I get errors trying to tune the below query for Oracle 10g using the DBMS_SQLTUNE advisors.
It happens when I wrap either a large block of PL/SQL code that uses bind variables or multiple nested subqueries with multiple JOIN conditions in a SELECT query statement that I wish to tune using the 10g SQLTUNE advisors.
Message was edited by:
benprusinski

Hi, I was trying to use the DBMS_SQLTUNE package to tune my sql statements used in the huge procedure. I can successfully create a task and execute it. But when I run report tuning task, I'm always getting error like the one in below example. Two questions I have now.
1) Is this becuase I'm using bind, but not passing any values?
2) Can I able to use to this package to tune a procedures instead of sql statement?
Example output...
SQL> SELECT DBMS_SQLTUNE.REPORT_TUNING_TASK( 'my_sql_tuning_task3')
2 FROM DUAL;
DBMS_SQLTUNE.REPORT_TUNING_TASK('MY_SQL_TUNING_TASK3')
GENERAL INFORMATION SECTION
Tuning Task Name : my_sql_tuning_task3
Tuning Task Owner : SCOTT
Scope : COMPREHENSIVE
Time Limit(seconds) : 3000
Completion Status : COMPLETED
Started at : 02/26/2009 21:44:41
Completed at : 02/26/2009 21:44:41
Number of Errors : 1
DBMS_SQLTUNE.REPORT_TUNING_TASK('MY_SQL_TUNING_TASK3')
Schema Name: KPRAVEEN
SQL ID : 479831s42xj1n
SQL Text : SELECT a.pdrorn, a.pdrcto, a.pdrlln FROM f4311 a
WHERE a.pddoco = receiptsrcrec.prdoco AND a.pddcto = :2 AND
a.pdkcoo = :3 AND a.pdsfxo = :4 AND a.pdlnid = :5
ERRORS SECTION
SQL>

Help me in Report(RDF) Performance tuning

Hi Viewers,
I need some steps related to report ( RDF) perfomance tune.
here is my following question.
(Q). A report for 100,000+ lines/records is taking 20 hours to run – what steps should be taken to resolve / tune
Thanks in advance.
new

Hello,
Have you followed the "tips" in the documents ?
Oracle® Application Server Reports Services Publishing Reports to the Web
10g Release 2 (10.1.2)
B14048-02
20 Tuning Oracle Reports
http://download-uk.oracle.com/docs/cd/B14099_17/bi.1012/b14048/pbr_tune.htm
Regards

Report running for long time & performance tuning

Hi All,
(1). WebI report is running for long time.so what are the steps i need to check for it ?
(2). Can you tell me about performance tuning in BO ?
please help me.....
Thanks
Kumar

(1). WebI report is running for long time.so what are the steps i need to check for it ?
The first step is to see if the problem lies in the query on the data source or in webi itself. Depending on the data source there are different ways to extract the query and try to run it against the database. Which source does your report uses?
(2). Can you tell me about performance tuning in BO ?
I would recommend to start by reading the administrator's guide. There is a section about how to improve performance.
Regards,
Stratos

Need clear steps for doing performance tuning on SQL Server 2008 R2 (DB Engine, Reporting Services and Integration Services)

We have to inverstigate about a reporting solution where things are getting slow (may be material, database design, network matters).
I have red a lot in MSDN and some books about performance tuning on SQL Server 2008 R2 (or other) but frankly, I feel a little lost in all that stuff
I'am looking for practical steps in order to do the tuning. Someone had like a recipe for that : a success story...
My (brain storm) Methodology should follow these steps:
Resource bottlenecks: CPU, memory, and I/O bottlenecks
tempdb bottlenecks
A slow-running user query : Missing indexes, statistics,...
Use performance counters : there are many, can one give us the list of the most important
how to do fine tuning about SQL Server configuration
SSRS, SSIS configuration ?
And do the recommandations.
Thanks
"there is no Royal Road to Mathematics, in other words, that I have only a very small head and must live with it..."
Edsger W. Dijkstra

Hello,
There is no clear defined step which can be categorized as step by step to performance tuning.Your first goal is to find out cause or drill down to factor causing slowness of SQL server it can be poorly written query ,missing indexes,outdated stats.RAM crunch
CPU crunch so on and so forth.
I generally refer to below doc for SQL server tuning
http://technet.microsoft.com/en-us/library/dd672789(v=sql.100).aspx
For SSIS tuning i refer below doc.
http://technet.microsoft.com/library/Cc966529#ECAA
http://msdn.microsoft.com/en-us/library/ms137622(v=sql.105).aspx
When I face issue i generally look at wait stats ,wait stats give you idea about on what resource query was waiting.
--By Jonathan KehayiasSELECT TOP 10
wait_type ,
max_wait_time_ms wait_time_ms ,
signal_wait_time_ms ,
wait_time_ms - signal_wait_time_ms AS resource_wait_time_ms ,
100.0 * wait_time_ms / SUM(wait_time_ms) OVER ( )
AS percent_total_waits ,
100.0 * signal_wait_time_ms / SUM(signal_wait_time_ms) OVER ( )
AS percent_total_signal_waits ,
100.0 * ( wait_time_ms - signal_wait_time_ms )
/ SUM(wait_time_ms) OVER ( ) AS percent_total_resource_waits
FROM sys.dm_os_wait_stats
WHERE wait_time_ms > 0 -- remove zero wait_time
AND wait_type NOT IN -- filter out additional irrelevant waits
( 'SLEEP_TASK', 'BROKER_TASK_STOP', 'BROKER_TO_FLUSH',
'SQLTRACE_BUFFER_FLUSH','CLR_AUTO_EVENT', 'CLR_MANUAL_EVENT',
'LAZYWRITER_SLEEP', 'SLEEP_SYSTEMTASK', 'SLEEP_BPOOL_FLUSH',
'BROKER_EVENTHANDLER', 'XE_DISPATCHER_WAIT', 'FT_IFTSHC_MUTEX',
'CHECKPOINT_QUEUE', 'FT_IFTS_SCHEDULER_IDLE_WAIT',
'BROKER_TRANSMITTER', 'FT_IFTSHC_MUTEX', 'KSOURCE_WAKEUP',
'LAZYWRITER_SLEEP', 'LOGMGR_QUEUE', 'ONDEMAND_TASK_QUEUE',
'REQUEST_FOR_DEADLOCK_SEARCH', 'XE_TIMER_EVENT', 'BAD_PAGE_PROCESS',
'DBMIRROR_EVENTS_QUEUE', 'BROKER_RECEIVE_WAITFOR',
'PREEMPTIVE_OS_GETPROCADDRESS', 'PREEMPTIVE_OS_AUTHENTICATIONOPS',
'WAITFOR', 'DISPATCHER_QUEUE_SEMAPHORE', 'XE_DISPATCHER_JOIN',
'RESOURCE_QUEUE' )
ORDER BY wait_time_ms DESC
use below link to analyze wait stats
http://www.sqlskills.com/blogs/paul/wait-statistics-or-please-tell-me-where-it-hurts/
HTH
PS: for reporting services you can post in SSRS forum
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Performance tuning of this report

Hello friends iam attaching my report give the performance tuning for this report to avoid nested endloops. how to do without using nested endloops.
give me the reply urgent.
REPORT ZDEMO9          NO STANDARD PAGE HEADING
                        LINE-SIZE 250
                        LINE-COUNT 22(3).                             .
            TABLES DECLARATION                    *
TABLES : MARA,              "general material data
         MAKT,              "material description
         MARC,              "plant data for material
         VBAP,              "sales document for item data
         EKKO,              "purchasing document header
         EKPO,              "purchasing document item
         KNA1.              "customer master details
            INTERNAL TABLE DECLARATION             *
DATA : BEGIN OF T_MARA OCCURS 0,
       MATNR LIKE MARA-MATNR,
       MTART LIKE MARA-MTART,
       MEINS LIKE MARA-MEINS,
       END OF T_MARA.
DATA : BEGIN OF T_MAKT OCCURS 0,
       MATNR LIKE MAKT-MATNR,
       MAKTX LIKE MAKT-MAKTX,
       SPRAS LIKE MAKT-SPRAS,
       END OF T_MAKT.
DATA : BEGIN OF T_MARC OCCURS 0,
       MATNR LIKE MARC-MATNR,
       WERKS LIKE MARC-WERKS,
       END OF T_MARC.
DATA : BEGIN OF T_KNA1 OCCURS 0,
       KUNNR LIKE KNA1-KUNNR,
       NAME1 LIKE KNA1-NAME1,
       LAND1 LIKE KNA1-LAND1,
       END OF T_KNA1.
DATA : BEGIN OF T_VBAP OCCURS 0,
       MATNR LIKE VBAP-MATNR,
       POSNR LIKE VBAP-POSNR,
       MATKL LIKE VBAP-MATKL,
       VBELN LIKE VBAP-VBELN,
       END OF T_VBAP.
DATA : BEGIN OF T_EKPO OCCURS 0,
       EBELN LIKE EKPO-EBELN,
       EBELP LIKE EKPO-EBELP,
       BUKRS LIKE EKPO-BUKRS,
       WERKS LIKE EKPO-WERKS,
       LGORT LIKE EKPO-LGORT,
       MATNR LIKE EKPO-MATNR,
       MANDT LIKE EKPO-MANDT,
       END OF T_EKPO.
                 FINAL INTERNAL TABLE                *
DATA : BEGIN OF T_FINAL OCCURS 0,
       MATNR LIKE MARA-MATNR,
       MTART LIKE MARA-MTART,
       MEINS LIKE MARA-MEINS,
       WERKS LIKE MARC-WERKS,
       MAKTX LIKE MAKT-MAKTX,
       SPRAS LIKE MAKT-SPRAS,
       VBELN LIKE VBAP-VBELN,
       POSNR LIKE VBAP-POSNR,
       MATKL LIKE VBAP-MATKL,
       EBELN LIKE EKPO-EBELN,
       EBELP LIKE EKPO-EBELP,
       BUKRS LIKE EKPO-BUKRS,
       KUNNR LIKE KNA1-KUNNR,
       LAND1 LIKE KNA1-LAND1,
       NAME1 LIKE KNA1-NAME1,
       LGORT LIKE EKPO-LGORT,
       END OF T_FINAL.
*DATA: BEGIN OF V_matnr OCCURS 0,
       matnr LIKE mara-matnr,
     END OF t_matnr.
data:
      a(32) type c.
a = 'IBT000000000000000001000000000000000050'.
                   SELECTION SCREEN                         *
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
SELECT-OPTIONS : S_BUKRS FOR EKPO-BUKRS,
                 S_KUNNR FOR KNA1-KUNNR,
                 S_WERKS FOR MARC-WERKS,
                 S_MATNR FOR MARA-MATNR obligatory.
SELECTION-SCREEN END OF BLOCK B1.
                 START OF SELECTION                           *
START-OF-SELECTION.
SELECT MATNR mtart meins
          FROM MARA
          INTO CORRESPONDING FIELDS OF TABLE T_MARA
          WHERE MATNR IN S_MATNR.
SELECT MATNR WERKS
          FROM MARC
          INTO CORRESPONDING FIELDS OF TABLE T_MARC
          FOR ALL ENTRIES IN T_MARA
          WHERE MATNR = T_MARA-MATNR
          and werks in s_werks.
select matnr maktx spras
        from makt
        into corresponding fields of table t_makt
        for all entries in t_mara
        where matnr = t_mara-matnr
        and spras = sy-langu.
select matnr posnr matkl vbeln
         from vbap
         into corresponding fields of table t_vbap
         for all entries in t_mara
         where matnr = t_mara-matnr.
select matnr werks bukrs ebeln ebelp lgort
         from ekpo
         into corresponding fields of table t_ekpo
         for all entries in t_mara
         where matnr = t_mara-matnr
         and werks in s_werks.
LOOP AT T_MARA.
    MOVE T_MARA-matnr TO T_FINAL-matnr.
    move t_mara-mtart to t_final-mtart.
    move t_mara-meins to t_final-meins.
    loop at t_marc where matnr eq t_mara-matnr.
      move t_marc-werks to t_final-werks.
      loop at t_makt.
        move t_makt-maktx to t_final-maktx.
        move t_makt-spras to t_final-spras.
        loop at t_vbap.
          move t_vbap-posnr to t_final-posnr.
          move t_vbap-matkl to t_final-matkl.
          move t_vbap-vbeln to t_final-vbeln.
        loop at t_ekpo.
        move t_ekpo-bukrs to t_final-bukrs.
        move t_ekpo-ebeln to t_final-ebeln.
        move t_ekpo-ebelp to t_final-ebelp.
        move t_ekpo-lgort to t_final-lgort.
          append t_final.
        endloop.
      endloop.
    endloop.
endloop.
endloop.
SELECT werks KUNNR LAND1 NAME1
INTO CORRESPONDING FIELDS OF TABLE T_KNA1
FROM KNA1.
WHERE WERKS in s_werks.
loop at t_kna1.
    move t_kna1-kunnr to t_final-kunnr.
    move t_kna1-name1 to t_final-name1.
    move t_kna1-land1 to t_final-land1.
    append t_final.
endloop.
"endloop.
loop at t_final.
    write :   4 t_final-matnr,
             20 t_final-mtart,
             28 t_final-meins,
             46 t_final-werks,
             58 t_final-maktx,
             71 t_final-spras,
             78 t_final-posnr,
            100 t_final-matkl,
            115 t_final-vbeln,
            130 t_final-kunnr,
            142 t_final-name1,
            156 t_final-land1,
            168 t_final-bukrs,
            190 t_final-ebeln,
            205 t_final-ebelp,
            208 t_final-lgort.
endloop.
              TOP-OF-PAGE                       *
top-of-page.
uline.
write : /60 'G E N E R A L   D E T A I L S' COLOR 2 INVERSE OFF.
ULINE.
write :/ SY-VLINE,    'MATERIAL'       COLOR 4, "12 SY-VLINE,
        13 SY-VLINE,    'IND SECTOR',
        28 SY-VLINE,    'UNITS',
        43 SY-VLINE,    'PLANT',
        55 SY-VLINE,    'MAT DESC',
        68 SY-VLINE,    'LANGU',
        70 SY-VLINE,    'SALES DOC ITEM',
        95 SY-VLINE,    'MAT GROUP',
       110 SY-VLINE,    'SALES DOC',
       125 SY-VLINE,    'CUST ID',
       140 SY-VLINE,    'NAME',
       155 SY-VLINE,    'COUNTRY',
       165 sy-vline,    'company code',
       205 sy-vline,    'storge loc'.

*& Report YTESTCHA                                                    *
REPORT ytestcha NO STANDARD PAGE HEADING
LINE-SIZE 250
LINE-COUNT 22(3). .
TABLES DECLARATION *
TABLES : mara, "general material data
makt, "material description
marc, "plant data for material
vbap, "sales document for item data
ekko, "purchasing document header
ekpo, "purchasing document item
kna1. "customer master details
INTERNAL TABLE DECLARATION *
*DECLARE TYPES FIRST AND THE INTERNAL TABLES
*DONT USE MATNR LIKE MARA-MATNR ,INSTEAD USE MARA TYPE MATNR WHERE MATNR
*IS THE DATA ELEMENT FOR FIELD MATNR.
TYPES: BEGIN OF ty_mara,
         matnr TYPE matnr,
         mtart TYPE mtart,
         meins TYPE meins,
         kunnr TYPE wettb,
       END OF ty_mara.
TYPES: BEGIN OF ty_makt,
        matnr TYPE matnr,
        maktx TYPE maktx,
        spras TYPE spras,
       END OF ty_makt.
TYPES: BEGIN OF ty_marc,
        matnr TYPE matnr,
        werks TYPE werks_d,
        END OF ty_marc.
TYPES : BEGIN OF ty_kna1,
          kunnr TYPE kunnr,
          name1 TYPE name1_gp,
          land1 TYPE land1_gp,
          END OF ty_kna1.
TYPES: BEGIN OF ty_vbap,
         matnr TYPE matnr,
         posnr TYPE posnr_va,
         matkl TYPE matkl,
         vbeln TYPE vbeln_va,
         END OF ty_vbap.
TYPES: BEGIN OF ty_ekpo,
         ebeln TYPE ebeln,
         ebelp TYPE ebelp,
         bukrs TYPE bukrs,
         werks TYPE werks_d,
         lgort TYPE lgort_d,
         matnr TYPE matnr,
         mandt TYPE mandt,
        END OF ty_ekpo.
DATA:t_mara TYPE TABLE OF ty_mara WITH HEADER LINE,
     t_makt TYPE TABLE OF ty_makt WITH HEADER LINE,
     t_marc TYPE TABLE OF ty_marc WITH HEADER LINE,
     t_kna1 TYPE TABLE OF ty_kna1 WITH HEADER LINE,
     t_vbap TYPE TABLE OF ty_vbap WITH HEADER LINE,
     t_ekpo TYPE TABLE OF ty_ekpo WITH HEADER LINE.
FINAL INTERNAL TABLE *
TYPES: BEGIN OF ty_final,
     matnr TYPE matnr,
     mtart TYPE mtart,
     meins TYPE meins,
     werks TYPE werks_d,
     maktx TYPE maktx,
     spras TYPE spras,
     vbeln TYPE vbeln_va,
     posnr TYPE posnr_va,
     matkl TYPE matkl,
     ebeln TYPE ebeln,
     ebelp TYPE ebelp,
     bukrs TYPE bukrs,
     kunnr TYPE kunnr,
     land1 TYPE land1_gp,
     name1 TYPE name1_gp,
     lgort TYPE lgort_d,
     END OF ty_final.
DATA : t_final TYPE TABLE OF ty_final WITH HEADER LINE.
*DATA: BEGIN OF V_matnr OCCURS 0,
matnr LIKE mara-matnr,
END OF t_matnr.
DATA:
a(32) TYPE c.
a = 'IBT000000000000000001000000000000000050'.
SELECTION SCREEN *
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS : s_bukrs FOR ekpo-bukrs,
                 s_kunnr FOR kna1-kunnr,
                 s_werks FOR marc-werks,
                 s_matnr FOR mara-matnr OBLIGATORY.
SELECTION-SCREEN END OF BLOCK b1.
START OF SELECTION *
START-OF-SELECTION.
*USE SUBROUTINES
*get data
PERFORM get_data.
*populate final table
PERFORM populate_final_table.
END-OF-SELECTION.
*display output
PERFORM display_output.
TOP-OF-PAGE *
TOP-OF-PAGE.
ULINE.
WRITE : /60 'G E N E R A L D E T A I L S' COLOR 2 INVERSE OFF.
ULINE.
WRITE :/ sy-vline, 'MATERIAL' COLOR 4, "12 SY-VLINE,
13 sy-vline, 'IND SECTOR',
28 sy-vline, 'UNITS',
43 sy-vline, 'PLANT',
55 sy-vline, 'MAT DESC',
68 sy-vline, 'LANGU',
70 sy-vline, 'SALES DOC ITEM',
95 sy-vline, 'MAT GROUP',
110 sy-vline, 'SALES DOC',
125 sy-vline, 'CUST ID',
140 sy-vline, 'NAME',
155 sy-vline, 'COUNTRY',
165 sy-vline, 'company code',
205 sy-vline, 'storge loc'.
*&      Form GET_DATA
      text
--> p1        text
<-- p2        text
*TRY TO CLEAR AND REFRESH TABLES BEFORE SELECT
FORM get_data .
CLEAR t_mara.
REFRESH t_mara.
SELECT matnr
         mtart
         meins
         kunnr
         FROM mara
         INTO TABLE t_mara
         WHERE matnr IN s_matnr.
IF NOT t_mara[] IS INITIAL.
    CLEAR t_marc.
    REFRESH t_marc.
    SELECT matnr
           werks
           FROM marc
           INTO TABLE t_marc
           FOR ALL ENTRIES IN t_mara
           WHERE matnr = t_mara-matnr
                 AND werks IN s_werks.
    CLEAR t_makt.
    REFRESH t_makt.
    SELECT matnr
           maktx
           spras
           FROM makt
           INTO TABLE t_makt
           FOR ALL ENTRIES IN t_mara
           WHERE matnr = t_mara-matnr
           AND spras = sy-langu.
    CLEAR t_vbap.
    REFRESH t_vbap.
    SELECT matnr
           posnr
           matkl
           vbeln
           FROM vbap
           INTO TABLE t_vbap
           FOR ALL ENTRIES IN t_mara
           WHERE matnr = t_mara-matnr.
    CLEAR t_ekpo.
    REFRESH t_ekpo.
    SELECT ebeln
           ebelp
           bukrs
           werks
           lgort
           matnr
           mandt
           FROM ekpo
           INTO TABLE t_ekpo
           FOR ALL ENTRIES IN t_mara
           WHERE matnr = t_mara-matnr
           AND werks IN s_werks.
ENDIF.
CLEAR t_kna1.
REFRESH t_kna1.
SELECT kunnr
         land1
         name1
         INTO TABLE t_kna1
         FROM kna1.
WHERE WERKS in s_werks.
ENDFORM.                    " GET_DATA
*&      Form POPULATE_FINAL_TABLE
      text
--> p1        text
<-- p2        text
FORM populate_final_table .
*AVOID LOOPS AND TRY TO USE READ
CLEAR t_final.
REFRESH t_final.
LOOP AT t_mara.
    MOVE t_mara-matnr TO t_final-matnr.
    MOVE t_mara-mtart TO t_final-mtart.
    MOVE t_mara-meins TO t_final-meins.
    READ TABLE t_marc WITH KEY matnr = t_mara-matnr.
    MOVE t_marc-werks TO t_final-werks.
    READ TABLE t_makt WITH KEY matnr = t_mara-matnr.
    MOVE t_makt-maktx TO t_final-maktx.
    MOVE t_makt-spras TO t_final-spras.
    READ TABLE t_vbap WITH KEY matnr = t_mara-matnr.
    MOVE t_vbap-posnr TO t_final-posnr.
    MOVE t_vbap-matkl TO t_final-matkl.
    MOVE t_vbap-vbeln TO t_final-vbeln.
    READ TABLE t_ekpo WITH KEY matnr = t_mara-matnr.
    MOVE t_ekpo-bukrs TO t_final-bukrs.
    MOVE t_ekpo-ebeln TO t_final-ebeln.
    MOVE t_ekpo-ebelp TO t_final-ebelp.
    MOVE t_ekpo-lgort TO t_final-lgort.
    READ TABLE t_kna1 WITH KEY kunnr = t_mara-kunnr.
    MOVE t_kna1-kunnr TO t_final-kunnr.
    MOVE t_kna1-name1 TO t_final-name1.
    MOVE t_kna1-land1 TO t_final-land1.
    APPEND t_final.
    CLEAR :t_final,t_mara,t_marc,t_makt,t_ekpo,t_vbap.
ENDLOOP.
ENDFORM.                    " POPULATE_FINAL_TABLE
*&      Form DISPLAY_OUTPUT
      text
--> p1        text
<-- p2        text
FORM display_output .
LOOP AT t_final.
    WRITE : 4 t_final-matnr,
    20 t_final-mtart,
    28 t_final-meins,
    46 t_final-werks,
    58 t_final-maktx,
    71 t_final-spras,
    78 t_final-posnr,
    100 t_final-matkl,
    115 t_final-vbeln,
    130 t_final-kunnr,
    142 t_final-name1,
    156 t_final-land1,
    168 t_final-bukrs,
    190 t_final-ebeln,
    205 t_final-ebelp,
    208 t_final-lgort.
ENDLOOP.
ENDFORM.                    " DISPLAY_OUTPUT

Performance Tuning for OBIEE Reports

Hi Experts,
I had a requirement for which i have to end up building a snowflakt model in Physical layer i.e. One Dimension table with Three snowflake tables(Materialized views).
The key point is the Dimension table is used in most of the OOTB reports.
so all the reports use other three snowflakes tables in the Join conditions due to which the reports take longer time than ever like 10 mints.
can anyone suggest good performance tuning tips to tune the reports.
i created some indices on Materialized view columns and and on dimension table columns.
i created the Materialized views with cache Enabled and refreshes only once in 24 hours etc
is there anything i have to improve performance or have to consider re-designing the Physical layer without snowflake
Please Provide valuable suggestions and comments
Thank You
Kumar

Kumar,
Most of the Performance Tuning should be done at the Back End , So calculate all the aggregates in the Repository it self and Create a Fast Refresh for MV and you can also do one thing you can schedule an IBOT to run the report every 1 hour or some thing so that the report data will be cached and when the user runs the report the BI Server extracts the data from Cache
Hope that helps
~Srix

Possible for using profiler for creating workload for Database Engine Tuning Advisor in case of SSRS reports

I have SSRS reports with each 5 parameters. Parameter datasets includes statements like WHERE @CategoryKey
I have 20 tables in SQL Server. We don't have OLAP cube.
I have created SQL Server Profiler trace. I have clicked all reports during process.
I have opened Database Engine Tuning Advisor.
I have selected all tables to Tune.
Tuning options are Indexes/No Partitioning/Keep all existing PDS
Result is following:
14% improvement
10 recommendations (8 statistic for Calender table and 2 index for Calender)
Tuning logs:
S008 exec sp_executesql N' LongSQLStatment including IN (@CategoryKey) Event does not reference any tables
S007 Replaced event exec sp_executesql
My question is that why I did not get any recommendations for other tables that Calender?
Could it be because of SSRS parameters like @CategoryKey?
Is it possible at all to use SQL Server profile for creating workload in case of SSRS reports with parameters?
I have tables and reports like ProductSales, which I suppose should be get indexedbecause of WHERE statements.
I have where statement like Month and Category and Color.

Yes it is possible to capture a trace using profiler, but please provide the t-sql behind your dataset before I can answer your question about the DTA recommandations.
Regards
Rasmus Glibstrup
http://blog.sqlguy.dk

Query for reporting need to be tuned

Hi,
I working on aoracle 10.2.0.4 on solaris platform 32 GB physical memory.This database is being used for both daily transaction and reporting purpose.One of the reporting query taking high time..
SQL> set autotrace traceonly
SQL> select substr(tr_ldt,4,6),tr_di,sum(tr_val) from tr_all
2 where tr_ay_bt>='15-APR-11'
3 group by substr(tr_ldt,4,6),tr_di
4 order by substr(tr_ldt,4,6),tr_di;
Execution Plan
| Id | Operation | Name | Rows | Bytes | Cost |
| 0 | SELECT STATEMENT | | 1488 | 37200 | 198K|
| 1 | SORT GROUP BY | | 1488 | 37200 | 198K|
| 2 | TABLE ACCESS FULL| TR_ALL | 6575K| 156M| 197K|
Statistics
1030 recursive calls
0 db block gets
721737 consistent gets
624840 physical reads
0 redo size
1682 bytes sent via SQL*Net to client
514 bytes received via SQL*Net from client
4 SQL*Net roundtrips to/from client
23 sorts (memory)
0 sorts (disk)
33 rows processed
and i have tried autometic sql tuning...
But the result of tuning task is null. No suggestion.
Can u tell me how can i reduce the time of execution.
1.The wait event involved is *'db file scatter read'*.
I have index on tr_ldt column and bitmap index on tr_di column.
Pls suggest how to tune this query????

See template postings:
[url https://forums.oracle.com/forums/thread.jspa?threadID=863295]How to post a sql tuning request
[url https://forums.oracle.com/forums/thread.jspa?messageID=1812597]When your query takes too long
The wait event involved is 'db file scatter read'.Subject to oracle version, "db file scattered read" is the expected wait event for a FULL TABLE SCAN where the blocks are not in the buffer cache and physical IO is required.
where tr_ay_bt>='15-APR-11'As an aside, never rely on implicit conversions, use TO_DATE('15-APR-2011','DD-MON-YYYY').
It wouldn't make a difference to your full table scan, unless the relevant column was indexed but an implcit datatype conversion was preventing usage thereof.
I have index on tr_ldt column and bitmap index on tr_di column.But the query restricts by TR_AY_BT.
If this is unindexed a full table scan is pretty much inevitable.
In the continued absence of an index, perhaps doing the work in parallel is an option?

Fine Tuning REPORT

Hi,
I want to know about fine tuning a report. One way, I know is to break the query which extracts data from different tables separately and finally joining it using FOR ALL ENTRIES. What are the different methods to fine tune a report.
Please reply with suitabe answers.

Hi
see this
1) Dont use nested select statements
2) If possible use for all entries in addition
3) In the where addition make sure you give all the primary key
4) Use Index for the selection criteria.
5) You can also use inner joins
6) You can try to put the data from the first select statement into an Itab and then in order to select the data from the second table use for all entries in.
7) Use the runtime analysis SE30 and SQL Trace (ST05) to identify the performance and also to identify where the load is heavy, so that you can change the code accordingly
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d0db4c9-0e01-0010-b68f-9b1408d5f234
ABAP performance depends upon various factors and in devicded in three parts:
1. Database
2. ABAP
3. System
Run Any program using SE30 (performance analys) to improve performance refer to tips and trics section of SE30, Always remember that ABAP perfirmance is improved when there is least load on Database.
u can get an interactive grap in SE30 regarding this with a file.
also if u find runtime of parts of codes then use :
Switch on RTA Dynamically within ABAP Code
*To turn runtim analysis on within ABAP code insert the following code
SET RUN TIME ANALYZER ON.
*To turn runtim analysis off within ABAP code insert the following code
SET RUN TIME ANALYZER OFF.
Always check the driver internal tables is not empty, while using FOR ALL ENTRIES
Avoid for all entries in JOINS
Try to avoid joins and use FOR ALL ENTRIES.
Try to restrict the joins to 1 level only ie only for tables
Avoid using Select *.
Avoid having multiple Selects from the same table in the same object.
Try to minimize the number of variables to save memory.
The sequence of fields in 'where clause' must be as per primary/secondary index ( if any)
Avoid creation of index as far as possible
Avoid operators like <>, > , < & like % in where clause conditions
Avoid select/select single statements in loops.
Try to use 'binary search' in READ internal table. Ensure table is sorted before using BINARY SEARCH.
Avoid using aggregate functions (SUM, MAX etc) in selects ( GROUP BY , HAVING,)
Avoid using ORDER BY in selects
Avoid Nested Selects
Avoid Nested Loops of Internal Tables
Try to use FIELD SYMBOLS.
Try to avoid into Corresponding Fields of
Avoid using Select Distinct, Use DELETE ADJACENT
Check the following Links
Re: performance tuning
Re: Performance tuning of program
http://www.sapgenie.com/abap/performance.htm
http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_PerformanceAnalysisTools.asp
check the below link
http://www.sap-img.com/abap/performance-tuning-for-data-selection-statement.htm
See the following link if it's any help:
http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_PerformanceAnalysisTools.asp
Check also http://service.sap.com/performance
and
books like
http://www.sap-press.com/product.cfm?account=&product=H951
http://www.sap-press.com/product.cfm?account=&product=H973
http://www.sap-img.com/abap/more-than-100-abap-interview-faqs.htm
http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_PerformanceAnalysisTools.asp
Performance tuning for Data Selection Statement
http://www.sap-img.com/abap/performance-tuning-for-data-selection-statement.htm
Debugger
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
Run Time Analyser
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617cafe68c11d2b2ab080009b43351/content.htm
SQL trace
http://help.sap.com/saphelp_47x200/helpdata/en/d1/801f7c454211d189710000e8322d00/content.htm
CATT - Computer Aided Testing Too
http://help.sap.com/saphelp_47x200/helpdata/en/b3/410b37233f7c6fe10000009b38f936/frameset.htm
Test Workbench
http://help.sap.com/saphelp_47x200/helpdata/en/a8/157235d0fa8742e10000009b38f889/frameset.htm
Coverage Analyser
http://help.sap.com/saphelp_47x200/helpdata/en/c7/af9a79061a11d4b3d4080009b43351/content.htm
Runtime Monitor
http://help.sap.com/saphelp_47x200/helpdata/en/b5/fa121cc15911d5993d00508b6b8b11/content.htm
Memory Inspector
http://help.sap.com/saphelp_47x200/helpdata/en/a2/e5fc84cc87964cb2c29f584152d74e/content.htm
ECATT - Extended Computer Aided testing tool.
http://help.sap.com/saphelp_47x200/helpdata/en/20/e81c3b84e65e7be10000000a11402f/frameset.htm
Just refer to these links...
performance
Performance
Performance Guide
performance issues...
Performance Tuning
Performance issues
performance tuning
performance tuning
You can go to the transaction SE30 to have the runtime analysis of your program.Also try the transaction SCI , which is SAP Code Inspector.
1 Always check the driver internal tables is not empty, while using FOR ALL ENTRIES
2 Avoid for all entries in JOINS
3 Try to avoid joins and use FOR ALL ENTRIES.
4 Try to restrict the joins to 1 level only ie only for 2 tables
5 Avoid using Select *.
6 Avoid having multiple Selects from the same table in the same object.
7 Try to minimize the number of variables to save memory.
8 The sequence of fields in 'where clause' must be as per primary/secondary index ( if any)
9 Avoid creation of index as far as possible
10 Avoid operators like <>, > , < & like % in where clause conditions
11 Avoid select/select single statements in loops.
12 Try to use 'binary search' in READ internal table. Ensure table is sorted before using BINARY SEARCH.
13 Avoid using aggregate functions (SUM, MAX etc) in selects ( GROUP BY , HAVING,)
14 Avoid using ORDER BY in selects
15 Avoid Nested Selects
16 Avoid Nested Loops of Internal Tables
17 Try to use FIELD SYMBOLS.
18 Try to avoid into Corresponding Fields of
19 Avoid using Select Distinct, Use DELETE ADJACENT.
<b>Reward points for useful Answers</b>
Regards
Anji

Developer Reports 6 Server Tuning

I've successfully installed Oracle Reports 6 Server and it works. However, it takes a while when I access a report (.rdf) from a web browser. I've been reading documentations and played around with some parameters but it still loads slow. Any inputs on tuning this?
Thanks.

I would check your query first.
tune your queries such that they come back really fast then check your
report server performance with running it
from a command line (rwcli60) and see what happens.

Report Tuning

Similar Messages

Maybe you are looking for