SAP F&R Query:: LATENCY TIMES

Hi I have been trying to understand the working of the F&R Dispatcher and I have some basic queries to which I am yet to get a satisfactory answer. I was wondering if I could get some help on the same. Please find my query below.
1. Could someone please explain as to how should we interpret the LATENCY TIME? What does it exactly mean?
2. I am also not clear as to what the 2 values of latency time mean? For e.g. 2 2; 3 3 and so on!
3. Also, how do I read/ interpret the logs?
4. How do I know if the F&R Dispatcher is running OK?
Thanks in advance!
Vismay Jani

Hi,
From the doc :
1.
Latency Time Settings for the Dispatcher Processes
Each process leaves an update time stamp in the database. The
dispatcher's processes coordinate themselves by checking the update
time information in each other's database. The latency time is added to
the received time. If the result is earlier than the current time, the
process to be checked is assumed to be dead and it will be restarted.
2. explained in 1
3. from transaction /FRE/FRP_DISP_ACT - Activate and Start Dispatcher button log
4. from transaction /FRE/FRP_DISP_ACT - Activate and Start Dispatcher
Thanks,
regards,
Nicolas

Similar Messages

Query execution time

Dear SCN,
I am new to BOBJ Environment. I have created a webi report on top of bex query by using BISC connection. Bex query is build for Vendor Ageing Analysis. My bex query will take very less time to execute the report (max 1 min). But in case of webi is takeing around 5 min when i click on refresh. I have not used any conditions,filters,restrictions are done at webi level all are done at bex level only.
Please let me know techniques to optimize the query execution time in webi. Currently we are in BO 4.0.
Regards,
PRK

Hi Praveen
Go through this document for performance optimization using BICS connection
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0e3c552-e419-3010-1298-b32e6210b58d?QuickLink=index&…

How to run a query several times?

Hi all,
Anyone has a clue for the following situation:
We have made a query (on the web) with several characteristics and key-figures. One of the characteristics has unique values that occurs only once (something like numbers for documents in R/3). The query was build with only one user-input variable based on this characteristic. The query was build especially for printing and fits exactly on a A4-paper.
We would like to give the end-user a tool in which he/she can store several values for the characteristic. On the basis of these stored values the system has to run the query several times.
Something for the Reporting Agent or is there an other solution?
Thanks in advance,
Henk.

hi Henk,
'control query' in few words is to filter data with combination of characteristic value.
http://help.sap.com/saphelp_nw04s/helpdata/en/6e/b5663a5fb46752e10000000a11402f/frameset.htm
Control Query for Pre-calculating Web Templates
Definition
A control query is a help query that you execute before you execute the queries in the Web template, and use the result to parameterize the Web template.
Use
You can specify a control query as significant information in the Reporting Agent settings for a Web template. When you specify a control query, the system does not pre-calculate the Web template itself, but a number of filtered views from the Web template.
We particularly recommend this procedure when wanting to calculate several Web templates only distinguished by their filter values in one swoop.
Using a control query in particular allows you to formulate complex selection criteria for the data to be pre-calculated.
Pre-calculate only the TOP50 customers, whose data is frequently requested, for example.
Structure
A very simple query, which contains exactly those characteristics in the drilldown in the rows according to which the Web template will be filtered, is particularly suitable as a control query. Every row in the table that a control query delivers, subsequently serves as a dynamic filter for the Web template views.
The respective combination of characteristic values is used as a filter for the Web template Data Provider for each table row. The background run produces pre-calculated data records, in actual fact one data record for each table row that delivers a control query.
If a characteristic does not appear in a view, the filter value is ignored.
In addition, you automatically get only those filter value combinations, for which data exists in the InfoCube used to define the control query.
Example
A typical application of this approach for pre-calculating a Web template is with cockpit applications, since they are controlled mainly through selection lists and no real OLAP navigation is necessary.
You can also use a control query for filtering when pre-calculating Crystal reports queries. You can find additional information under Defining Crystal Reports Queries Settings.

To find Query Run-times

Hi guys,
i was trying to compare query run-times with and without BIA using RSRT, however i'm running into hurdles..
the same query when executed twice (without BIA) without using cache is showing different data manager times
i'm surprised how the reason could be
the difference sometimes is very high even the wait times are also sometimes very different
how to arrive at the average run-times are there any tools besides rsrt (i hve no access to statistics queries) but st03 doesnt seem to be of much help
i'm lookin at the fine difference so accurate times are necessary
thanks,
your help will be greatly appreciated

Hi.....
check the following links :
http://help.sap.com/saphelp_nw04s/helpdata/en/43/e3807a6df402d3e10000000a1553f7/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/7c/2bde42fa712b78e10000000a155106/frameset.htm
Another thing :
If you want to use the BI statistics for Query runtimes, you will need the 0TCT_C01 InfoCube, together with the multiprovider 0TCT_MC01.
The queries for the BI statistics to report over query runtimes are all built on the multiprovider.
Besides that, you will need the virtual infoprovider 0TCT_VC01, to be able to report on the latest data. Because you will probably load the statistics each night into the 0TCT_C01 cube, you can report on the latest data using the 0TCT_VC01 virtual cube.
Hope this helps you........
Regards,
Debjani.........
Edited by: Debjani Mukherjee on Sep 13, 2008 8:01 AM

Manage query - run time errors

Hi,
we have one user working at one desktop which receives error "run-time error 5" followed by "401 Automation error" when selecting the manage query wizard proceeding from the BPC Excel action pane.
We only have this at one desktop. Any ideas?
Dries

Hi,
You can check the query run time by using T code RSRT.
1. Go to T code RSRT
2. Give your query name.
3. Click on the "Execute + Debug" tab
4. Various check boxed for Debug options will appear on the screen
5. Under the "Others" node you will find the check box for "Display Statics Data"
6. Check this check box and click on continue.
7. This will execute the query and provide you selection screen if any.
8. Once the query is completely executed, click on "back" button or simply hit F3.
9. This takes you to the "Statistic Data for Query Runtime screen"
10. Here you can take the total of "Duration" column to get the total duration for query execution.
Please refer following link for details:
[http://help.sap.com/saphelp_nw70/helpdata/en/43/e3807a6df402d3e10000000a1553f7/frameset.htm]
Hope this answers your query.
- Geetanjali

How to query latency with HistoryVerbose 0

We're using Transactional Replication in SQL 2008R2 SP2
I'm trying to evaluate whether using a HistoryVerbose setting of 0 on the Log Reader and Distribution agents is a worthwhile modification to make, but still need to know Latency in these agents at periods of time.
I know it's possible to use Windows Performance Monitor and enable a couple of replication counters but I have reason to want to do this in T-SQL.
Tracer Tokens don't give you the answer until the token has finished replicating - it tells you about the problem AFTER the problem's happened.
It's also possible to get Current Latency from the MSDistribution_History and MSLogReader_History tables, but this information isn't recorded when the HistoryVerbose setting is 0.
It's possible to calculate what the latency is going to be based on the agent's transactions per second and the number of pending transactions, but querying these values can be costly on the Distribution database.
So there may not be an answer to this other than Windows Performance Monitor, but has anyone managed to query Latency in a light-weight query which isn't reliant on the logging in MSDistribution_History and MSLogReader_History?
Thank you if anyone can help!
Tim Johnstone Senior Technical Consultant Computacenter (UK) Ltd

Hi Tim,
Does Replication Monitor meet your requirement? For transactional replication, Replication Monitor displays information about the number of transactions in the distribution database that have not yet been distributed to a Subscriber and the estimated time
for distributing these transactions.
If not, I suggest you looking into below links.
They are related to the tracer tokens technology for monitoring replication latency.
How to: Measure Latency and Validate Connections for Transactional Replication (Replication Transact-SQL Programming)
http://technet.microsoft.com/en-us/library/ms147309(v=sql.105).aspx
SQL Server Transactional Replication Latency Monitoring Tool
http://gallery.technet.microsoft.com/scriptcenter/SQL-Server-Transactional-e34ed1e8
Cheers,
Ying

Query Executime time ?

Hello BW Experts,
1) What is the Average Query execution time. I need this information so that we can identity queries where performance tuning is necessary. We want to have some cutoff numbers so that we can start concentrating on couple of queries.
2) What is the worst execution times that the user is okay with.
3) i know the answer for the third question, what is the best execution time. .... in a flash
Suggestions appreciated.
Thanks,
BWer

hi BWer,
check oss note
557870 'FAQ BW Query Performance'
and 567746 'Composite note BW 3.x performance Query and Web'.
and
BW Performance Tuning Knowledge Center - SAP Developer Network (SDN)
Business Intelligence Performance Tuning [original link is broken]
performance docs on query
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3f66ba90-0201-0010-ac8d-b61d8fd9abe9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cccad390-0201-0010-5093-fd9ec8157802
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c8c4d794-0501-0010-a693-918a17e663cc
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/064fed90-0201-0010-13ae-b16fa4dab695
Prakash's weblog
/people/prakash.darji/blog/2006/01/27/query-creation-checklist
/people/prakash.darji/blog/2006/01/26/query-optimization

How to measure query run time and mnitor performance

Hai All,
A simple question. How to measure query run time and mnitor performance? I want to see the parameters like how long it took to execute, how much space it took etc.
Thank you.

hi,
some ways
1. use transaction st03, expert mode.
2. tables rsddstat*
3. install bw statistics (technical content)
there are docs on this, also bi knowledge performance center.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cccad390-0201-0010-5093-fd9ec8157802
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3f66ba90-0201-0010-ac8d-b61d8fd9abe9
BW Performance Tuning Knowledge Center - SAP Developer Network (SDN)
Business Intelligence Performance Tuning [original link is broken]
also take a look
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cccad390-0201-0010-5093-fd9ec8157802
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c8c4d794-0501-0010-a693-918a17e663cc
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/31b6b490-0201-0010-e4b6-a1523327025e
Prakash's weblog on this topic..
/people/prakash.darji/blog/2006/01/27/query-creation-checklist
/people/prakash.darji/blog/2006/01/26/query-optimization
oss note
557870 'FAQ BW Query Performance'
and 567746 'Composite note BW 3.x performance Query and Web'.

How to get Query response Time?

II am on BI 7.0. I ran some queries using RSRT command. I want to find how much time the queries took.
I went to
st03 -> expert mode -> BI system load-> select today / week/month according to the query runtime day
I do not see any Info Providers. Query was on a cube so why no Info Providers.
Does something have to turned on InfoPorvider to show.
When I look in RSDDSTAT_OLAP table, I do see many rows but cannot make any sense. Is there some documentation on how to get total query time from this table?
Is there any other way to get query response time?
Thanks a lot.

HI,
why not use RSRT ? You can add database statistics option in "Execut & Debug" and you get all the runtime metrics of your query
In transaction RSRT, enter the query name and press u2018Execute +Debugu2019.
Selecting u2018Display Statistics Datau2019 .
After executing the query will return a list of the measured metrics.
The event id / text describes the steps (duration in seconds):
"OLAP: Read data" gives the SQL statements repsonse time (ok - because the SAP
application server acts as an Oracle client a little network traffic from the db server is included,
but as far as you not transferring zillions of rows it can be ignored)
But it gives you much more (i.e. if the OLAP cache gets used or not )...
In the "Aggreagate statistcs" you get all the infoproviders involved in that query.
bye
yk

Query runtime vs Query execution time

Hi,
I am trying to find the most executed queries (how often queries are executed) in our BI system.
I got query runtime from Hitlist in st03 Reporting analysis.
could someone tell me if its same as query execution time or where can I check most executed queries or how often are queries executed.
thanks

hi,
I hope you already installed the statistics.
You can get lot of details like which quereis are being used and their history and how many times they executed and by whom , when and also tells DB, OLPA, and Frontend times in ST03N in Expert mode
refer below thread
Re: BEx Query is executed how many times???
also refer help - navigate to BW Statistics MultiProvider Queries
http://help.sap.com/saphelp_nw04s/helpdata/en/44/10cb9a8f345cf9e10000000a155369/frameset.htm
hope it helps u
Thanks
Edited by: Srinivas on Oct 30, 2008 9:42 PM

Rules of thumb for acceptable query response times?

Once I read a statement from SAP which said that users typically tolerate
response times up to 7 seconds. So you should strive to achive this goal.
Unfortunately I cannot remember in which document or webpage this
statement was made. Does anybody happen to have a reference for this rule
or any other SAP rules about the BW query response times?
Regards,
Mark

Share with us the situations where your query is running slow. How many rows are you returning via SQL Commands?
On reports; the maximum row count being returned and/or the pagination scheme can have impact on performance.
Jeff

How can we remove the commas from the Formula value in SAP BW BEx query

Hi All,
How can we remove the commas from the Formula value in SAP BW BEx query
We are using the formula replacing with characteristic.The characteristic value needs to be display as number with out commas.
Regards
Venkat.

Do you want to remove the commas when you run the query on Bex Web or in RSRT?
Regards

Designer support for Subquery against SAP BW Bex Query

BusinessObjects designer has an option in the paramaters window to turn on "Allow Sub-Queries" in a universe that has been created using a olap source. SAP BW BEX Query to be specific. Once turned on, you can build a query and the subquery button and functionality is actually enabled and allows you to build it. When running the query I get an error message "A filter contains a wrong value. You cannot run this query".
Now, I am pretty sure this functionality is not supported on a BW or OLAP source but, I can not find anything definitive from SAP stating that it is not supoorted. So I want to make sure that this is not one of those situations where everyone just says "It's not supported" but really just doesn't know. Does anyone have the official word or link to an SAP statement that this functionality is officially not supported.

What I would say is, it won't support. The reason could be, as its not support any structure view in universe designer, that means we cannot create any derived tables where we could use sql query.
I believe the same applies here too. Even if you look at LOV defintions in universe, it won't show any query.
So the same applies to reports.
Hope this helps.
Regards
Gowtham

Connecting Crystal Reports to SAP BW BEx query

Post Author: mfrank
CA Forum: Data Connectivity and SQL
We have used Crystal Enterprise 8.5 to connect to an SAP BW BEx query in the past, however we are having some difficulties. Rather than trying to upgrade our old CE system, I've been told that we should be able to connect Crystal Reports (2008?) directly to the BW BEx query. I've been trying to accomplish this, but can't seem to find any drivers that will allow the connectivity. When I try to set up a connection using OLAP, the only two options listed are Hyperion and Microsoft OLAP. I have an old version of Brio Query (now Hyperion, now Oracle) that does show up with a driver for BW, but this doesn't show up in my Crystal options.
Can someone give me some advice as to how to connect Crystal Reports to SAP BW? I realize there are licensing issues with running live data without using Crystal Enterprise (or later BO products), but I'm just looking to print a report to a PDF.
Thanks

Post Author: A Kumar
CA Forum: Data Connectivity and SQL
Hi mfrank,
I am also facing a similar kind of a problem. Did you get any solution to your problem. If yes, kindly let me know.
Thanks
A kumar

Query taking time

We have this query which is taking a long time to execute. From the explain plan what i found out is there is a full table scan going on W_GL_OTHER_F. Please help in identifying the problem area and solutions.
The query is,
select D1.c1 as c1,
     D1.c2 as c2,
     D1.c3 as c3,
     D1.c4 as c4,
     D1.c5 as c5,
     D1.c6 as c6,
     D1.c7 as c7,
     D1.c8 as c8
from
     (select distinct D1.c2 as c1,
               D1.c3 as c2,
               D1.c4 as c3,
               D1.c5 as c4,
               D1.c6 as c5,
               D1.c7 as c6,
               D1.c8 as c7,
               D1.c1 as c8,
               D1.c5 as c9
          from
               (select sum(case when T324628.OTHER_DOC_AMT is null then 0 else T324628.OTHER_DOC_AMT end ) as c1,
                         T91397.GL_ACCOUNT_NUM as c2,
                         T149255.SEGMENT_VAL_CODE as c3,
                         T148908.SEGMENT_VAL_DESC as c4,
                         T148543.HIER4_CODE as c5,
                         T148543.HIER4_NAME as c6,
                         T91707.ACCT_DOC_NUM as c7,
                         T91707.X_LINE_DESCRIPTION as c8
                    from
                         W_GL_OTHER_F T91707 /* Fact_W_GL_OTHER_F */ ,
                         W_GL_ACCOUNT_D T91397 /* Dim_W_GL_ACCOUNT_D */ ,
                         W_STATUS_D T96094 /* Dim_W_STATUS_D_Generic */ ,
                         WC_GL_OTHER_F_MV T324628 /* Fact_WC_GL_OTHER_MV */ ,
                         W_GL_SEGMENT_D T149255 /* Dim_W_GL_SEGMENT_D_Segment1 */ ,
                         W_GL_SEGMENT_D T148937 /* Dim_W_GL_SEGMENT_D_Segment3 */ ,
                         W_HIERARCHY_D T148543 /* Dim_W_HIERARCHY_D_Segment3 */ ,
                         W_GL_SEGMENT_D T148908 /* Dim_W_GL_SEGMENT_D_Segment2 */
                    where ( T91397.ROW_WID = T91707.GL_ACCOUNT_WID and T91707.DOC_STATUS_WID = T96094.ROW_WID and T96094.ROW_WID = T324628.DOC_STATUS_WID and T148543.HIER_CODE = T148937.SEGMENT_LOV_ID and T148543.HIER20_CODE = T148937.SEGMENT_VAL_CODE and T324628.DELETE_FLG = 'N' and T324628.X_CURRENCY_CODE = 'CAD' and T148543.HIER4_CODE <> '00000000000' and T91397.RECON_TYPE_CODE is not null and T91397.ROW_WID = T324628.GL_ACCOUNT_WID and T91397.ACCOUNT_SEG3_CODE = T148937.SEGMENT_VAL_CODE and T91397.ACCOUNT_SEG3_ATTRIB = T148937.SEGMENT_LOV_ID and T91397.ACCOUNT_SEG2_CODE = T148908.SEGMENT_VAL_CODE and T91397.ACCOUNT_SEG2_ATTRIB = T148908.SEGMENT_LOV_ID and T91397.ACCOUNT_SEG1_CODE = T149255.SEGMENT_VAL_CODE and T91397.ACCOUNT_SEG1_ATTRIB = T149255.SEGMENT_LOV_ID and (T96094.W_STATUS_CODE in ('POSTED', 'REVERSED')) and T91397.GL_ACCOUNT_NUM like '%98%' )
                    group by T91397.GL_ACCOUNT_NUM, T91707.ACCT_DOC_NUM, T91707.X_LINE_DESCRIPTION, T148543.HIER4_CODE, T148543.HIER4_NAME, T148908.SEGMENT_VAL_DESC, T149255.SEGMENT_VAL_CODE
               ) D1
     ) D1
order by c1, c2, c3, c4, c5, c6, c7The plan is,
PLAN_TABLE_OUTPUT
Plan hash value: 3196636288
| Id | Operation                             | Name                | Rows | Bytes |TempSpc| Cost (%CPU)| Time     | Pstart| Psto
|   0 | SELECT STATEMENT                      |                     |   810K|   306M|       |   266K (1)| 01:20:03 |       |       |
|   1 | HASH GROUP BY                        |                     |   810K|   306M|   320M|   266K (1)| 01:20:03 |       |       |
|* 2 |   HASH JOIN                           |                     |   810K|   306M|    38M|   239K (1)| 01:11:56 |       |       |
|* 3 |    MAT_VIEW ACCESS FULL               | WC_GL_OTHER_F_MV    | 1137K|    40M|       | 9771   (2)| 00:0
|* 4 |    HASH JOIN                          |                     |   531K|   189M|       |   222K (1)| 01:06:38 |       |       |
|   5 |     INLIST ITERATOR                   |                     |       |       |       |            |          |       |       |
|* 6 |      INDEX RANGE SCAN                 | W_STATUS_D_U2       |     4 |    56 |       |     1   (0)| 00:00:01 |
|* 7 |     HASH JOIN                         |                     |   607K|   208M| 8704K|   222K (1)| 01:06:38 |       |       |
|* 8 |      HASH JOIN                        |                     | 40245 | 8214K| 2464K| 10843   (2)| 00:03:16 |       |       |
|   9 |       VIEW                            | index$_join$_007    | 35148 | 2025K|       |   122 (32)| 00:00:03 |       |
|* 10 |        HASH JOIN                      |                     |       |       |       |            |          |       |       |
|* 11 |         HASH JOIN                     |                     |       |       |       |            |          |       |       |
|* 12 |          HASH JOIN                    |                     |       |       |       |            |          |       |       |
| 13 |           BITMAP CONVERSION TO ROWIDS |                     | 35148 | 2025K|       |     1   (0)| 00:00:01 |       |
| 14 |            BITMAP INDEX FULL SCAN     | W_HIERARCHY_D_M2    |       |       |       |            |          |       |
| 15 |           BITMAP CONVERSION TO ROWIDS |                     | 35148 | 2025K|       |    24   (0)| 00:00:01 |       |
| 16 |            BITMAP INDEX FULL SCAN     | W_HIERARCHY_D_M4    |       |       |       |            |          |       |
| 17 |          BITMAP CONVERSION TO ROWIDS |                     | 35148 | 2025K|       |    24   (0)| 00:00:01 |       |
|* 18 |           BITMAP INDEX FULL SCAN      | X_W_HIERARCHY_D_M11 |       |       |       |            |          |       |
| 19 |         BITMAP CONVERSION TO ROWIDS   |                     | 35148 | 2025K|       |    33   (0)| 00:00:01 |       |
| 20 |          BITMAP INDEX FULL SCAN       | X_W_HIERARCHY_D_M12 |       |       |       |            |          |       |
|* 21 |       HASH JOIN                       |                     | 40246 | 5895K| 4096K| 10430   (2)| 00:03:08 |       |
| 22 |        VIEW                           | index$_join$_008    | 65417 | 3321K|       |   197 (14)| 00:00:04 |
|* 23 |         HASH JOIN                     |                     |       |       |       |            |          |       |       |
|* 24 |          HASH JOIN                    |                     |       |       |       |            |          |       |       |
| 25 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 | 3321K|       |     3   (0)| 00:00:01 |       |
| 26 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M1   |       |       |       |            |          |       |
| 27 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 | 3321K|       |    66   (2)| 00:00:02 |       |
| 28 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M2   |       |       |       |            |          |       |
| 29 |          BITMAP CONVERSION TO ROWIDS |                     | 65417 | 3321K|       |   100   (1)| 00:00:02 |       |
| 30 |           BITMAP INDEX FULL SCAN      | W_GL_SEGMENT_D_M3   |       |       |       |            |          |       |
|* 31 |        HASH JOIN                      |                     | 40246 | 3851K|       | 9953   (1)| 00:03:00 |       |       |
| 32 |         VIEW                          | index$_join$_006    | 65417 | 1149K|       |    82 (18)| 00:00:02 |       |
|* 33 |          HASH JOIN                    |                     |       |       |       |            |          |       |       |
| 34 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 | 1149K|       |     3   (0)| 00:00:01 |       |
| 35 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M1   |       |       |       |            |          |       |
| 36 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 | 1149K|       |    66   (2)| 00:00:02 |       |
| 37 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M2   |       |       |       |            |          |       |
|* 38 |         HASH JOIN                     |                     | 40246 | 3144K|       | 9870   (1)| 00:02:58 |       |       |
| 39 |          VIEW                         | index$_join$_005    | 65417 | 1149K|       |    82 (18)| 00:00:02 |       |
|* 40 |           HASH JOIN                   |                     |       |       |       |            |          |       |       |
| 41 |            BITMAP CONVERSION TO ROWIDS|                     | 65417 | 1149K|       |     3   (0)| 00:00:01 |       |
| 42 |             BITMAP INDEX FULL SCAN    | W_GL_SEGMENT_D_M1   |       |       |       |            |          |       |
| 43 |            BITMAP CONVERSION TO ROWIDS|                     | 65417 | 1149K|       |    66   (2)| 00:00:02 |       |
| 44 |             BITMAP INDEX FULL SCAN    | W_GL_SEGMENT_D_M2   |       |       |       |            |          |       |
|* 45 |          TABLE ACCESS FULL            | W_GL_ACCOUNT_D      | 40246 | 2436K|       | 9788   (1)| 00:02:57
| 46 |      PARTITION RANGE ALL              |                     |    11M| 4261M|       |   152K (2)| 00:45:43 |     1 |1048
| 47 |       TABLE ACCESS FULL               | W_GL_OTHER_F        |    11M| 4261M|       |   152K (2)| 00:45:43
Predicate Information (identified by operation id):
   2 - access("T96094"."ROW_WID"="T324628"."DOC_STATUS_WID" AND "T91397"."ROW_WID"="T324628"."GL_ACC
   3 - filter("T324628"."X_CURRENCY_CODE"='CAD' AND "T324628"."DELETE_FLG"='N')
   4 - access("T91707"."DOC_STATUS_WID"="T96094"."ROW_WID")
   6 - access("T96094"."W_STATUS_CODE"='POSTED' OR "T96094"."W_STATUS_CODE"='REVERSED')
   7 - access("T91397"."ROW_WID"="T91707"."GL_ACCOUNT_WID")
   8 - access("T148543"."HIER_CODE"="T148937"."SEGMENT_LOV_ID" AND "T148543"."HIER20_CODE"="T148937"
10 - access(ROWID=ROWID)
11 - access(ROWID=ROWID)
12 - access(ROWID=ROWID)
18 - filter("T148543"."HIER4_CODE"<>'00000000000')
21 - access("T91397"."ACCOUNT_SEG2_CODE"="T148908"."SEGMENT_VAL_CODE" AND
              "T91397"."ACCOUNT_SEG2_ATTRIB"="T148908"."SEGMENT_LOV_ID")
23 - access(ROWID=ROWID)
24 - access(ROWID=ROWID)
31 - access("T91397"."ACCOUNT_SEG3_CODE"="T148937"."SEGMENT_VAL_CODE" AND
              "T91397"."ACCOUNT_SEG3_ATTRIB"="T148937"."SEGMENT_LOV_ID")
33 - access(ROWID=ROWID)
38 - access("T91397"."ACCOUNT_SEG1_CODE"="T149255"."SEGMENT_VAL_CODE" AND
              "T91397"."ACCOUNT_SEG1_ATTRIB"="T149255"."SEGMENT_LOV_ID")
40 - access(ROWID=ROWID)
45 - filter("T91397"."GL_ACCOUNT_NUM" LIKE '%98%' AND "T91397"."RECON_TYPE_CODE" IS NOT NULL)
79 rows selected.

user605926 wrote:
We have this query which is taking a long time to execute. From the explain plan what i found out is there is a full table scan going on W_GL_OTHER_F. Please help in identifying the problem area and solutions.
The plan is,
PLAN_TABLE_OUTPUT
Plan hash value: 3196636288
| Id | Operation                             | Name                | Rows | Bytes |TempSpc| Cost (%CPU)| Time     | Pstart| Psto
|   0 | SELECT STATEMENT                      |                     |   810K|   306M|       |   266K (1)| 01:20:03 |       |       |
|   1 | HASH GROUP BY                        |                     |   810K|   306M|   320M|   266K (1)| 01:20:03 |       |       |
|* 2 |   HASH JOIN                           |                     |   810K|   306M|    38M|   239K (1)| 01:11:56 |       |       |
|* 3 |    MAT_VIEW ACCESS FULL               | WC_GL_OTHER_F_MV    | 1137K|    40M|       | 9771   (2)| 00:0
|* 4 |    HASH JOIN                          |                     |   531K|   189M|       |   222K (1)| 01:06:38 |       |       |
|   5 |     INLIST ITERATOR                   |                     |       |       |       |            |          |       |       |
|* 6 |      INDEX RANGE SCAN                 | W_STATUS_D_U2       |     4 |    56 |       |     1   (0)| 00:00:01 |
|* 7 |     HASH JOIN                         |                     |   607K|   208M| 8704K|   222K (1)| 01:06:38 |       |       |
|* 8 |      HASH JOIN                        |                     | 40245 | 8214K| 2464K| 10843   (2)| 00:03:16 |       |       |
|   9 |       VIEW                            | index$_join$_007    | 35148 | 2025K|       |   122 (32)| 00:00:03 |       |
|* 10 |        HASH JOIN                      |                     |       |       |       |            |          |       |       |
|* 11 |         HASH JOIN                     |                     |       |       |       |            |          |       |       |
|* 12 |          HASH JOIN                    |                     |       |       |       |            |          |       |       |
| 13 |           BITMAP CONVERSION TO ROWIDS |                     | 35148 | 2025K|       |     1   (0)| 00:00:01 |       |
| 14 |            BITMAP INDEX FULL SCAN     | W_HIERARCHY_D_M2    |       |       |       |            |          |       |
| 15 |           BITMAP CONVERSION TO ROWIDS |                     | 35148 | 2025K|       |    24   (0)| 00:00:01 |       |
| 16 |            BITMAP INDEX FULL SCAN     | W_HIERARCHY_D_M4    |       |       |       |            |          |       |
| 17 |          BITMAP CONVERSION TO ROWIDS |                     | 35148 | 2025K|       |    24   (0)| 00:00:01 |       |
|* 18 |           BITMAP INDEX FULL SCAN      | X_W_HIERARCHY_D_M11 |       |       |       |            |          |       |
| 19 |         BITMAP CONVERSION TO ROWIDS   |                     | 35148 | 2025K|       |    33   (0)| 00:00:01 |       |
| 20 |          BITMAP INDEX FULL SCAN       | X_W_HIERARCHY_D_M12 |       |       |       |            |          |       |
|* 21 |       HASH JOIN                       |                     | 40246 | 5895K| 4096K| 10430   (2)| 00:03:08 |       |
| 22 |        VIEW                           | index$_join$_008    | 65417 | 3321K|       |   197 (14)| 00:00:04 |
|* 23 |         HASH JOIN                     |                     |       |       |       |            |          |       |       |
|* 24 |          HASH JOIN                    |                     |       |       |       |            |          |       |       |
| 25 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 | 3321K|       |     3   (0)| 00:00:01 |       |
| 26 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M1   |       |       |       |            |          |       |
| 27 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 | 3321K|       |    66   (2)| 00:00:02 |       |
| 28 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M2   |       |       |       |            |          |       |
| 29 |          BITMAP CONVERSION TO ROWIDS |                     | 65417 | 3321K|       |   100   (1)| 00:00:02 |       |
| 30 |           BITMAP INDEX FULL SCAN      | W_GL_SEGMENT_D_M3   |       |       |       |            |          |       |
|* 31 |        HASH JOIN                      |                     | 40246 | 3851K|       | 9953   (1)| 00:03:00 |       |       |
| 32 |         VIEW                          | index$_join$_006    | 65417 | 1149K|       |    82 (18)| 00:00:02 |       |
|* 33 |          HASH JOIN                    |                     |       |       |       |            |          |       |       |
| 34 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 | 1149K|       |     3   (0)| 00:00:01 |       |
| 35 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M1   |       |       |       |            |          |       |
| 36 |           BITMAP CONVERSION TO ROWIDS |                     | 65417 | 1149K|       |    66   (2)| 00:00:02 |       |
| 37 |            BITMAP INDEX FULL SCAN     | W_GL_SEGMENT_D_M2   |       |       |       |            |          |       |
|* 38 |         HASH JOIN                     |                     | 40246 | 3144K|       | 9870   (1)| 00:02:58 |       |       |
| 39 |          VIEW                         | index$_join$_005    | 65417 | 1149K|       |    82 (18)| 00:00:02 |       |
|* 40 |           HASH JOIN                   |                     |       |       |       |            |          |       |       |
| 41 |            BITMAP CONVERSION TO ROWIDS|                     | 65417 | 1149K|       |     3   (0)| 00:00:01 |       |
| 42 |             BITMAP INDEX FULL SCAN    | W_GL_SEGMENT_D_M1   |       |       |       |            |          |       |
| 43 |            BITMAP CONVERSION TO ROWIDS|                     | 65417 | 1149K|       |    66   (2)| 00:00:02 |       |
| 44 |             BITMAP INDEX FULL SCAN    | W_GL_SEGMENT_D_M2   |       |       |       |            |          |       |
|* 45 |          TABLE ACCESS FULL            | W_GL_ACCOUNT_D      | 40246 | 2436K|       | 9788   (1)| 00:02:57
| 46 |      PARTITION RANGE ALL              |                     |    11M| 4261M|       |   152K (2)| 00:45:43 |     1 |1048
| 47 |       TABLE ACCESS FULL               | W_GL_OTHER_F        |    11M| 4261M|       |   152K (2)| 00:45:43
Predicate Information (identified by operation id):
2 - access("T96094"."ROW_WID"="T324628"."DOC_STATUS_WID" AND "T91397"."ROW_WID"="T324628"."GL_ACC
3 - filter("T324628"."X_CURRENCY_CODE"='CAD' AND "T324628"."DELETE_FLG"='N')
4 - access("T91707"."DOC_STATUS_WID"="T96094"."ROW_WID")
6 - access("T96094"."W_STATUS_CODE"='POSTED' OR "T96094"."W_STATUS_CODE"='REVERSED')
7 - access("T91397"."ROW_WID"="T91707"."GL_ACCOUNT_WID")
8 - access("T148543"."HIER_CODE"="T148937"."SEGMENT_LOV_ID" AND "T148543"."HIER20_CODE"="T148937"
10 - access(ROWID=ROWID)
11 - access(ROWID=ROWID)
12 - access(ROWID=ROWID)
18 - filter("T148543"."HIER4_CODE"<>'00000000000')
21 - access("T91397"."ACCOUNT_SEG2_CODE"="T148908"."SEGMENT_VAL_CODE" AND
"T91397"."ACCOUNT_SEG2_ATTRIB"="T148908"."SEGMENT_LOV_ID")
23 - access(ROWID=ROWID)
24 - access(ROWID=ROWID)
31 - access("T91397"."ACCOUNT_SEG3_CODE"="T148937"."SEGMENT_VAL_CODE" AND
"T91397"."ACCOUNT_SEG3_ATTRIB"="T148937"."SEGMENT_LOV_ID")
33 - access(ROWID=ROWID)
38 - access("T91397"."ACCOUNT_SEG1_CODE"="T149255"."SEGMENT_VAL_CODE" AND
"T91397"."ACCOUNT_SEG1_ATTRIB"="T149255"."SEGMENT_LOV_ID")
40 - access(ROWID=ROWID)
45 - filter("T91397"."GL_ACCOUNT_NUM" LIKE '%98%' AND "T91397"."RECON_TYPE_CODE" IS NOT NULL)
79 rows selected.
You may want to have a look at <a href="HOW TO: Post a SQL statement tuning request - template posting">HOW TO: Post a SQL statement tuning request - template posting</a> to see what more details are needed in order for somebody to provide better answer.
Based on what you have posted so far, you may want to share details of following questions (in addition to details in above link)
1) How much time does the query currently take to execute? How much time do you expect it to take? Also, how are you measuring query execution time?
2) Your plan suggests that the query is expected to return 810K rows. Is this figure close to actual number of records? What are you doing with this huge amount of data?

SAP F&R Query:: LATENCY TIMES

Similar Messages

Maybe you are looking for