Read Mode of a Query

Hi All,
what is a Query Read Mode or Read Mode of a Query? why it is used and is it have any Seperate
Transaction code? How to check the Read mode of a Query? what is the use of it?
Thanking

Hi Nagar,
On the Query Properties dialog box for the query monitor you can make settings for a BW query with regard to the read mode. You can switch off the default Parallel Processing for queries on a MultiProvider. For queries with virtual characteristics or key figures you are able to activate the use of the cache, which is deactivated by default. If you activate the display of the generation log you are able to display a log in which you can see the reasons why the query in question was generated again. You do this afterwards using the generation log pushbutton.
USE
The read mode determines how the OLAP processor gets data during navigation. You can set the mode in Customizing for an InfoProvider and in the Query Monitor for a query.
u can get the info
[http://help.sap.com/saphelp_nw04/helpdata/en/57/b10022e849774f9961aa179e8763b6/frameset.htm]
Regards,
NR

Similar Messages

How can we send read mode for a query..?

How can we send read mode for a query..?
thanks in advance
regards

Hi Chaudhary.
I am not sure I understand your question correct?
Do you want to set a query to read only so it can not be changed? If so you should be controlling this with authorizations.
Hope it helps.
BR
Stefan

Precautions to be taken while changing the Query read mode in PED system

Dear Experts,
I got a task to change the Query Read mode for more No. of queries in Production system directly itself.
Request you to let me what are the steps to be followed/precautions to be taken while changing the Query Read mode in PED.
one more doubt regarding this.....If i plan to change the Read mode of Query say Q1, how can i come to know weather the Q1 is executing or not executing by that time.
Thanks in advance for valuable response.
Thanks & Regards,
Ramesh - Kumar

Hello,
You can change the query read mode in transaction 'RSRT', here are the steps:
1) Access transaction RSRT and enter the query name
2) Select the 'Properties' option
3) Un-check the 'Info provider' setting next to the 'Read mode' --> This enables you to change the read mode of the query --> Execute
4) Choose the option 'Generate Report' to re-generate the query program
Hope this info helps.
Thanks
Bala

Query Read mode

HI Experts,
What is QueryReadMode? In which Scenario we have to use QueryReadMode?
1.In which situation we have to create Aggregates and how do u know weather the cube has Aggregates or not?
2.In which situation we have to create Indexes and how do u see the indexes bitmap r Btree explain me Briep
3.In which situation we have to do Compression?how can i delete requests and how can i delete records from single request & from Multiple requests based on the fixed value.
4.In which situation we have to create Partitions and how do u know weather the cube has partions or not?
5.4.In which situation we have to create LINE-ITEM Dimentions.
please any body explain me these topics with example...................
what is BW STATISTICS explain me brief......
THANKS IN ADVANCE,
PriyaKodali

HI
What is QueryReadMode?
We use the query monitor to test or regenerate queries and query views, and to check or change query properties. With the query monitor you have the option of displaying technical information about queries
Query Properties.
In the Query Properties window of the Query Monitor, we can configure settings for the Read Mode, Cache Mode etc.
The read mode of a query determines how often the OLAP Processor retrieves data from the database during query navigation. The read mode contains three types of read processes:
Read all data (setting A: Query to Read All Data At Once)
Reread the data (setting X: Query to Read Data During Navigation)
Reread the data when expanding a hierarchy (setting H: Query to Read When You Navigate or Expand Hierarchies)
WE USE T-CODE RSRT.
(H) u2013 Query to read, when you read or expand hierarchies: In H mode, the detailed information within the nodes and sub-nodes of a hierarchy are read on demand (i.e., when you expand a hierarchy node). The amount of data transferred to the OLAP processor is the least of all the three categories. The downside is that the number of database reads increases as you keep expanding hierarchy nodes. SAP recommends setting queries to the H read mode. This is based on the empirical evidence of the relative performance of queries set to each of these modes.
(X) u2013 Query to read data during navigation: In this mode, data are requested by the OLAP processor as
dictated by every navigational step. The difference between X mode and H is that in the case of hierarchies, all the data on a leaf level are completely retrieved by the OLAP processor.
(A) u2013 Query to read all data at once: There is only one read process in this mode. When you execute the query in the Business Explorer, all data in the main memory area of the OLAP processor that is needed for all possible navigational steps of this query is read. During navigation, all new navigational states are aggregated and calculated from the data from the main memory.
The read mode Query to be read when you navigate or expand hierarchies significantly improves performance in almost all cases compared to the other two modes. The reason for this is that only the data the user wants to see is requested in this mode.
What Is An Aggregate?
An aggregate stores the dataset of an InfoCube redundantly in a summarized form. In this instance, summarization means the condensing of the original fact table of an Infocube to an aggregate table. This table no longer contains certain characteristics of the Infocube and has been summarized across attributes, or to characteristic values, or a hierarchy level.
The summarization enables you to access the data of an InfoCube quickly when reporting. Aggregates are, therefore, tools for enhancing performance.
Aggregates are created from logical data packets (requests). You can distinguish between the processes of filling and rolling up
http://wiki.sdn.sap.com/wiki/display/BI/Aggregates--SAPBWQueryPerformance
3. In which situation we have to create Indexes and how do u see the indexes bitmap r Btree explain me Briep
Bit map and B-tree index - It is related to Cardinality.
Cardinality means no. of predefined options for perticular Info Object.
e.g *** of person - Male or Female - we have only two options - so it will be considered as Low Cardinality.
Document Number : their can be many document numbers depends on the no. of users. so it is considered as high cardinaltiy
If low cardinality is their, Bit map index is used.
If high cardinalty is their, B tree index is used.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0b28d18-f383-2c10-a780-a52349715b54?QuickLink=index&overridelayout=true
http://help.sap.com/saphelp_erp2004/helpdata/en/cf/21eb47446011d189700000e8322d00/frameset.htm
4. In which situation we have to do Compression?how can i delete requests and how can i delete records from single request & from Multiple requests based on the fixed value.*
Compression improves Performance Tuning as it removes the redundant data. This improvement in the performance can be checked by RSRT and running the query with compression & without compression.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c035d300-b477-2d10-0c92-f858f7f1b575?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c09b7019-4885-2e10-e2b8-fe1fef0643db?QuickLink=index&overridelayout=true
deletion of compressed cube data
Delete compressed request from cube.
5.In which situation we have to create LINE-ITEM Dimentions.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/005f3197-d3da-2e10-1a94-a5c62342f2aa?QuickLink=index&overridelayout=true

Invalid read mode while executing the query

Hi,
I have developed a query based on a cube in MM module.
When I try to execute the query, the following error is being displayed:
Invalid read mode
Message no. BRAIN017
Diagnosis
If queries (often unintentionally) are assigned the read mode "Query to Read All Data at Once", this often results in performance problems. To eliminate this problem, this warning is displayed when you execute a query with this read mode when the query is generated.
Procedure for System Administration
Before you execute the query, repair the read mode:
u2022 You can repair the read mode for this query in the Query Monitor (transaction RSRT1). You can set the read mode for the selected query by choosing Query -> Read Mode.
u2022 If this warning is displayed when you check a query, you need to change the default read mode for new queries in the InfoCube in InfoCube maintenance. In InfoProvider maintenance, choose Environment -> InfoProvider Properties -> Change and make the relevant settings on the Query/Cache tab page.
Please let me know what are the exact setting that I need to do and where.
Thanks in advance.
Will assign points for the solution.
Thanks & Regards.

Hi Ganesh,
You can change the read mode by going to transaction RSRT, entering the query name and then clicking the properties button. A dialog box will then be displayed that allows you to change the read mode.
The question of what's the best read mode for you query depends on the requirements of the query:
If you choose "read all data at once", it will take quite awhile before the first view of the query is shown. This is because it basically reads all data needed for your query (e.g. data for hierarchy nodes etc). However, after the initial view, successive navigations might be a lot faster.
The read mode "Read data during navigation and expansion of hierarchies" is usually the best mode. The initial view will show up in the least amount of time in this mode. However, when the users start to navigate, data will then be read from the database (aggregates, or the main cube tables) or the cache.
The read mode "Read data during navigation" is like the "Read data during navigation and expansion of hierarchies" mode. However, it will also read the data for the hierarchy nodes. Expansions of the hierarchy will therefore be faster in this mode. Of course, there's additional overhead for the initial view.
Hope this helps. Cheers.

Terminate: Invalid read mode

After checking query, system show me the error message - Terminate: Invalid read mode, the detailed information as below, please help to solve this issue. Thanks a lot!
Terminate: Invalid read mode [A017(BRAIN)]
Diagnosis
If queries (often unintentionally) are assigned the read mode "Query to Read All Data at Once", this often results in performance problems. To eliminate this problem, this warning is displayed when you execute a query with this read mode when the query is generated.
System Response
Procedure
Procedure for System Administration
Before you execute the query, repair the read mode:
You can repair the read mode for this query in the Query Monitor (transaction RSRT1). You can set the read mode for the selected query by choosing Query -> Read Mode.
If this warning is displayed when you check a query, you need to change the default read mode for new queries in the InfoCube in InfoCube maintenance. In InfoProvider maintenance, choose Environment ->InfoProvider Properties -> Change and make the relevant settings on the Query/Cache tab page.

Hi,
Goto Tcode - "RSRT ", in that specify the query name and change the Read mode.
After changing this again execute the Query in that RSRT, adn check whether every thing is ok or not....
Assign points if it helps.......

Query read mode change from 'A' to 'H'

Dear All Experts,
       I'm new to optimization Project. I got a task to change the Query read mode from 'A' to 'H" of some queries. I will change it by using T-code RSRT.
My doubt is in which system we will change the settings i.e., directly in Production system or i have to change in Development system and then transportation to remaining systems?
Is there any another option to do this other than RSRT.
        Requesting you all to help me in this cleraly.
Thanks in Advance.
Regards,
Ramesh Kumar

Dear Experts,
        Thanks for your valuable information and my doubt is if I change the settings in Infoprovider level, then all the queries which were built on particular Infoprovider will get changed right?
My task is to change the Query read mode of only some queries of Info Provider but not for all queries in Infoprovider.
Thanks in advance for your valuable assistance.
Regards,
Ramesh-Kumar.

Query read mode-Cache mode

Hi,
Can u explain me the functionalities of the options:
A-Query to read all data at once
X-Query to read data during navigation
H-Query to read when u navigate or expand hierarchies
I am not clear of the diff. bet. the X,H options....
Cache Mode:
0-Cache is Inactive
1-Main memory cache without swapping
2-Main memory cache without swapping
3-Main memory cache with swapping
4-Persistent cache for each application server
5-Persistent cache across each application server
Optimization Mode:
0-Query will be optimised after generation
1-Query optimization with individual periods in days
9-Query optimization inactive
Can u explain these functionalities in detail...
Max.points will be assigned

HI,
PLease check this..
1. Query to be read when you navigate or expand hierarchies (H)
The amount of data transferred from the database to the OLAP processor is the smallest in this mode. However, it has the highest number of read processes.
In the following mode Query to read data during navigation, the data for the fully expanded hierarchy is requested for a hierarchy drilldown. In the Query to be read when you navigate or expand hierarchies mode, the data across the hierarchy is aggregated and transferred to the OLAP processor on the hierarchy level that is the lowest in the start list. When expanding a hierarchy node, the children of this node are then read.
You can improve the performance of queries with large presentation hierarchies by creating aggregates on a middle hierarchy level that is greater or the same as the hierarchy start level.
 2. Query to read data during navigation (X)
The OLAP processor only requests data that is needed for each navigational status of the query in the Business Explorer. The data that is needed is read for each step in the navigation.
In contrast to the Query to be read when you navigate or expand hierarchies mode, presentation hierarchies are always imported completely on a leaf level here.
The OLAP processor can read data from the main memory when the nodes are expanded.
When accessing the database, the best aggregate table is used and, if possible, data is aggregated in the database.
 3. Query to read all data at once (A)
There is only one read process in this mode. When you execute the query in the Business Explorer, all data in the main memory area of the OLAP processor that is needed for all possible navigational steps of this query is read. During navigation, all new navigational states are aggregated and calculated from the data from the main memory.
The read mode Query to be read when you navigate or expand hierarchies significantly improves performance in almost all cases compared to the other two modes. The reason for this is that only the data the user wants to see is requested in this mode.
Compared to the Query to be read when you navigate or expand hierarchies, the setting Query to read data during navigation only effects performance for queries with presentation hierarchies.
Unlike the other two modes, the setting Query to Read All Data At Once also has an effect on performance for queries with free characteristics. The OLAP processor aggregates on the corresponding query view. For this reason, the aggregation concept, that is, working with pre-aggregated data, is least supported in the Query to read all data at once mode.
We recommend you choose the mode Query to be read when you navigate or expand hierarchies.
Only choose a different read mode in exceptional circumstances. The read mode Query to read all data at once may be of use in the following cases:
 The InfoProvider does not support selection. The OLAP processor reads significantly more data than the query needs anyway.
 1. Cache is Inactive (0)
The cross-transactional cache is deactivated.
The following modes are possible for the active cache: The cross-transactional cache is activated.
 2. Main Memory Cache Without Swapping (1)
The cache data is stored in the main memory. When the cache memory has been exhausted, excess data is removed according to the LRU algorithm, i.e. deleted from the memory. When a query is subsequently requested, the result is read from the InfoProvider once again.
 3. Main Memory Cache with Swapping (2)
The cache data is stored in the main memory. When the caching memory is used up, the excess data is written to a background and can be loaded back into the cache memory when making another request.
After query-relevant data has been loaded again, the background store can no longer be used.
 4. Persistent Cache per Application Server (3)
The cache data is stored persistently as a database table or as a file in a directory attainable from the application server. We recommend that you choose a directory that is proximate to the application server.
When you save the cache data in a database table this puts a strain on the database. However, it is also then quicker to access uncached data in the database. In comparison to storing data in, for example, a star schema (see InfoCube), fewer tables are read and fewer indexes are accessed.
 5. Cross-Application Server Persistent Cache (4)
The cache data is stored persistently as a cross-application server database table or file in a file system in the network, accessed from the application server. In this mode there is no displacement of data and no restriction on memory size. More space is required but this method also saves time.
¡ Database table: Strain is put on the database instance for the table.
¡ File: Strain is put on the network node operating system for the file.
¡ In addition, the application server that calculates the data and network communication has to be taken into account with both storage types.
If you do not make any other settings the OLAP processor determines the optimal initial size of the table SP, that is the memory structure in which data is held and processed in the OLAP processor (see Cache Structure). This is done after the first execution and again after a period of 31 days since the last optimization. It automatically generates a report afterwards.
In the Query Properties dialog box in the Query Monitor you can implement, modify of deactivate this function. Choose one of the following options:
· Query is optimized after generation (0)
· Query optimization with individual periods in days (1) Here you can determine the optimization period yourself.
· Query optimization inactive (9)
Hope this helps..
Bye,
Shashikanth.

Design Studio behaviour according to query read mode property

How does Design studio behave according to the Read Mode property set here in SAP : (RSRT transaction, query properties) :
It seems like Business Objects tools (Analysis, Webi, …) don’t behave in the same way according to these properties, even if they all use the BICS protocol. What is Design Studio behavior?
In fact, I’ve tested 2 queries, both with many free characteristics (because I swap dimensions in my charts thanks to scripting), but
one with default values on CALMONTH (12 last months),
one with a customer exit variable that I set with the exact same values (12 last months),
when analysing the behaviour in RSRT I see that choosing the H option will add a where clause to the 1st query, “SQL” seems then identical in
both cases, and statistics are the same (see below). With A option, the 1st query statistics are worse and the 2nd one statistics stay the same.
So knowing if Design Studio takes this option into account is important.
At the beginning, I was expecting that Design Studio would retrieve more data cells with the default values query (all months are retrieved and some kind of local filter is applied to display only the 12 last months) than with the variable query (only the 12 last months areretrieved, no need to apply any additional filter, and if the end user wants some other months then the script has to update the variable, and waiting time would then be worse). I guess it could be true with read mode option set to A.
I know that some answers have been given on this subject, saying that even updating only default values thanks to the filter panel was implying a roundtrip to the back end, but I can only understand this statement if H option is taken into account by Design Studio…
I would like to better understand exactly what is Design Studio behaviour, and if there is any benefit to use variables to set queries filters (filter panel usage is not straightforward then), or if default values and native filter panel usage is ok as it has the exact same consequences on data volumes retrieved, back end roundtrips and query performances.
I guess that the answer depends on the capacity Design Studio has or not to take the Read Mode option into account.
Thanks in advance!

So DS takes this property into account.
If the read mode is set to H, then playing with the filter panel has the same consequences on data read and data transported statistics (safety belt limit statistic too) than the effects BEx variables would have.
So
- If, as I do, you hate the look of the prompts screen
- and/or if you find that using BEx variables is not optimal for filter panel management (because if you use the same datasource for the filter panel as for the chart, values appearing in the filter panel will be filtered according to the BEx variable, then the end user can't select a value out of this restricted context)
- and/or if you can afford a first run of the query with some default values instead (i.e. if your queries are performant)
then I find it more user friendly to offer your end users to bypass this ugly prompts screen and to directly access a beautiful dashboard based on some default values, that may be interesting to them, values that they can change in a second time having access to the whole list of values in the filter panel... Furthermore, it may take the same time, with performant queries, to set the prompts than to run the query with some default values and to change them thanks to the filter panel.

How can a user enter a value in the field which is in read mode.

Hi all,
I am creating a badi for the valuation class.when ever i execute the mm02 transaction.if an invalid valuation class is entered,my error message is poping up.but it is coming in the display mode.i should get the valuation class field in the read mode.
Regards,
charita.

Hi Charita,
Use information message instead of Error message.Then it will not give u that field in non-editable mode.
Reward points if it solves ur query or answer is helpful
Thanks
Chinmay

How to control the number of fields in the Advanced mode in af:query

Hi,
How to control the number of fields in the Advanced mode in <af:query>?
Say i have 20 fields in my table and i created a view criteria with 2 fields. It would work perfectly in Basic mode. But in the Advanced mode all other fields selection is possible on clicking the ADD Fields button. I did not want the client to make a search with all 20 fields. Only 10 fields are to be listed in the Advanced Mode even though there are 20 fields in my table.
How do i control the list of fields in ADDFields button?
Any ideas?
KR

You can uncheck the Querable property of the attributes which you need not show up in the Advanced Mode (but they will not show up in other modes too !) or programatically set the same as mentioned here -
http://adfcodebits.blogspot.com/2010/11/bit-27-setting-view-object-attributes.htmlAlso you can hide the AddFields button as suggested here - http://www.notjustjava.com/2011/12/cool-tips-to-showhide-components-of-the-query-control-of-adf/

Cache mode for specific query

Hello BI guys,
This is Calvin from Korea. We are implementing BI 7.0 and have some severe performance problem. For some queries they don't use cache mode, even though the global cache are used.
When I checked these kind of queries by performance information in RSRT, I got following message,
===================================================
InfoProvider Definition                |
===================================================
ZCOAG0101                             | At Least One InfoProvider Not InfoCube
ZCOAG0101                             | Not All InfoProviders Can Use Aggregates
===================================================
===================================================
Query Definition                        |
===================================================
Read Mode                               | Do Not Read upon Drilling Navigation/ Hierarchy
Query Cannot                           | Use the Cache Reason
Cache Mode                             | Cache Not Used By Query
Cache Update                           | Query Does Not Use Delta Process
Type of SP Grouping for Delta Cache Process | No Provider Partitioning
===================================================
And after run of technical information,
===================================================
Cache-Relevant Data                 |
===================================================
Query Can Use the Cache         | No
Query Generation Time              | 2007.09.17 15:05:31
InfoProvider - Last Data Change | 2007.09.16 21:43:11
Last Load of Exchange Rates     | 2007.07.13 15:01:48
===================================================
Does anybody have ideas for this problem?
Your help will be highly appreciated and get points!
Thanks in advance
Regards,
Worried Calvin

hi Dong Suk Choi ,
the technical information which u have furnished clearly says that the settings
that u have made does not enable the query to use cache.
u can enhance cache by customizing the inforovider or in the transaction rsrt
even if the concerned query does not have required settings u can make them in rsrt tcode.
goto rsrt set the read mode and cache mode as u wish, however default settings would give optimum performance.
and run the query.
in the rsrt screen a push button execute + debug enter that and unmark the check box do not use cache.
hope this helps.
reward points if helpful.
bye.
under properties tab u can give the query settingMessage was edited by:
        Rakesh Elangovan

Read mode for querys

Hi,
I got a problem with a query whose read mode is currently "H".
When the Read mode is H the query is behaving diffrently. The query is being used in a workbook where profit cneter is dispalyed as hierarchy.
During the refresh of that query the nodes at the parent level are displayed whereas the nodes at the leaf level will be blank. If you try collapsing and expanding again the values will be displayed.
If the read mode is "X" then all the values are displayed at both parent level as well as leaf level.
But we are using Read mode as "H" for all the querys but we had no issues with other queries.
Now we got a problem with this query.
Any ideas will be appreciated!!
Thanks

hi Bwer,
To prevent for accidentally deletion of master data, it is set into read mode for the developer. only guys who r designing the bw will usually have authorization to delte.From a company perspective, master data is important and should not be deleted or changed by any unathurosied users. only with valid authorization one can delete/change the master data
where as a cube, one can delete the contents by just deleting the request of the delta load
i hope this clears,
Assigning pts is the way of saying thanks in sdn
regards
ravi

Invalid Read Mode

Hello BW Experts
While running the query I am getting the error invalid read mode. Is it any settings that we could do in the query level or RSRT. Please suggest to get rid of this error.
Thanks,
BWer

hi BWer,
oss note 432596
Change the read mode before you execute the query: You can change the read mode of a specific query using transaction RSRT. Choose Query -> Read mode to set the read mode for a selected query. If this warning message is displayed when you call up a query, you have to change the default read mode for new InfoCube queries in Customizing for BW (Tools > Business Engineer > BW Customizing > SAP Reference IMG ). The default read mode is under the node "BW Customizing Implmentation Guide > Business Information Warehouse > Reporting-Relevant Settings > Set Read Mode for InfoCube
You can also change the read mode for all queries and the default read mode for all InfoCubes using transaction RSRT. Choose Environment -> Repair read mode. This is where you can change all non-allowed read modi to "Subsequenlty read by navigation".

READ MODE for Hierarchies

Hi,
I have a Navigational attribute hierarchy in my query definition. The performance of the hierarchy is really bad after BW upgrade.In RSRT the technical info says
Read Mode : Read During Navigation/Hierarchy Drilldown
Is that possible to change to Read during query load for only this query?
What are the possible way to improve performance of the hierarchy drilldown rederring?
Thank you
Arun

Hi,
There is a setting in SPRO to change the Read mode of the InfoProvider Properties.
What is the impact of changing to 'Query to read all data at once'?
Reporting Agent -
I enabled 'Precalculated Data' for web template read mode. I ran the reporting agent to pre-calculate data.
I am trying to test whether if the data is pre-calcualated then will the improve the performance of the hierarchy.
IMPACT -
1. All th other navigation options are diaslbed, like 'arrow mark' to open web item tray.
2. Hierarchy nodes are not opening.
3. Context menu got disabled
It looks like a complete static report.
Did someone experienced this problem?
Thank you
Arun

Read Mode of a Query

Similar Messages

Maybe you are looking for